Modifying default boot image

I need to edit default x86 boot image and add one address to host file.
In default directory: \Program Files\Microsoft Configuration Manager\OSD\boot\i386 I see two wim files. Boot.PS100002.wim and boot.wim. What is the one that is used with PXE?

This was a test. I had a problem with multicast (giving error 0x80091007 = hash error) when trying multicast in different vlan than
where configmgr server resides. Multicast was working fine in same vlan as confimgr server.
In problematic vlan only fqdn resolves to configmgr server, not short name. When I add ConfigMgr server to WinPE host file, then multicast
starts to work.

Similar Messages

Modify existing boot image

Hello everyone
How can I modify an existing Netboot or Netinstall image?
ex. I have a 10.4.4 image with apps which I want to upgrade it to 10.4.6 and add some apps.
Do I have to create the image again?
Thanks
Kostas

No, on your NetBoot server open System Image Utility and go into "Images", in here you see listed all the images in your /Library/NetBoot/NetBootSP0/ directory. You should be able to select the one you want to image and add packages in the contents pane. It should also give you the option of backing up your image before it applies the changes.

Default or custom boot image

Hi to everyone. Currently I am in a process of learning SCCM 2012 R2, having experience in working with MDT & WDS. I want to perform capturing of reference virtual Windows 7 machine image and to deploy it later to bare-metal virtual machine. In order
to do this I have to create task sequence media and while creating it I have to choose boot image. Since I have to "inject" vmxnet3 network drivers into boot image before using it for creation of task sequence media, what is recommended practice
- doing so with default boot image (for example x64 flavour of it) or adding Windows 7 boot image into SCCM and injecting these drivers into it? In MDT I did not have any default boot images so I had to add them from Windows 7 installation media and inject
these network drivers into them.

No consequence. As Darrick says IT Admins often add their own custom images. However that is not essential. If you're just learning keep it simple.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Boot image question

I have a boot image that calls a wim file called Mh100002.wim. I injected some NIC drivers into this .wim file. When I updated the wim with NIC drives it created a new file called mh1000002.mg100002.wim. I right click
on my boot image, pick Data Source and I choose this new .wim file mh1000002.mg100002.wim. I point my task sequence to use this boot image. I update content to all DPs with this new Boot image. When I F12 a machine it connects to the correct
DP but it uses mh1000002.wim. Why? How come it does not use the updated .wim called mh1000002.mg100002.wim ?
mqh7

Your data source is the original bits. Say you have default boot image
[Boot Image (x64)] with PackageID of PS100005 where the source is here:
\\MY-SCCM-SITE.my.domain.com\SMS_ABC\osd\boot\x64\boot.wim.
When you inject drivers into it, SCCM recompiles it and saves new wim file as boot.{SiteName}{PackageID}.wim. In your task sequence you attach the “boot image package” of say [Boot Image (x64)], but SCCM will actually use the newly created wim file.
Now, I am assuming you are PXE booting correct? There is a twist when you PXE boot. SCCM uses the boot image to PXE boot that is tied the most recently deployed task sequence on the target collection.
For example if you create a TS and the appropriate media tied to it and deploy it to the “unknown” computers collection, and then a colleague comes in behind you and creates and new task sequence with different media attached to it and deploys it the “unknown”
computers collection that boot image will get used instead.
Hope this helps!
Cheers!
--Tony

Netboot : boot image - default user settings

Hello
So far I have successfully created from installation DVDs a netboot boot image and customized/modified it so that I can use it for all users created on the MacOSX Server.
Now for some details I was not able to resolve them. I can not persistently set some computer preferences/settings assigned to the administrator like timezone, ntp-server etc. on the client.
Also I have noticed, that after booting from the netboot image, the client has for the login window an US keyboard layout but should have in our case a swiss-german layout, because otherwise our users can not enter correctly their login passwords, especially if they use some some special characters in their passwords. Is there any way to set this this on the netboot image or in the clients nvram ?
Many thanks in advance, André Müller

/System/Library/User Template is where all of these are stored. You will have enable the root login account and log in to it in order to make changes to that folder with the GUI.
Changing anything in the System folder is always a bit unreliable, though. Apple might release a software update that will undo any of the changes.
If you really are managing 850+ Macs, you should look into getting OS X Server. OS X Server has the tools you need to set up custom templates for new users, without having to muck in the System folder.

Can I modify jumpstart server boot image to support another LAN card?

I tried to install Solaris 9 from jumpstart server. However, Solaris 9 does not support my on-board LAN Card. As a result, I try to install Solaris 10 beta 55 from jumpstart server. It is a good news to me that Solaris 10 beta 55 does support "Intel 82801DB PRO/100 VE Ethernet". The installation is successfull. However, there is a problem when I install Windows XP on another DOS partition. I have no idea why the installation of MS Windows XP will crash the Solaris 10 beta 55 partition. Durning boot process in Solaris 10, There are a lot of Solaris partition errors. It is not a good idea to install Solaris 10 until the release comes out.
I think that it should be possible to modify Solaris 9 jumpstart server so that I can use Solaris 10 beta cd to kick up LAN driver and call Solaris 9 jumpstart server to install the OS.

You can use a "prestart command". It can be configured in the properties of each boot image, 'customization' tab.
Torsten Meringer | http://www.mssccmfaq.de

Client getting an IP lease on the 64-bit LiteTouch boot image, but not the 32-bit version.

MDT 2012 U1. No problem with PXE booting so WDS is not the issue.
The NIC in question is the Intel I217-LM, which resides on both the new Dell Optiplex 9020 and the Latitude E7440. I downloaded the Dell drivers and then the Intel drivers and imported them into the WindowsPE drivers folder in the workbench. Updated
the boot images to make sure the new drivers were injected. Both yielded the same result. I can do everything I need to do when booting to the 64-bit LiteTouchPE_x64.wim boot image, but not the 32-bit version. When booting to the 32-bit
version, I get no IP configuration info at all.
When looking at the drivers in MDT, I see only one difference: the supported OS versions. The 64-bit driver supports 6.1, 6.1.1, and 6.2. The 32-bit driver supports only 6.1.1 and 6.2. Not sure if that's the issue.
Tried using drvload within 32-bit WinPE to manually inject the NIC driver. Still no luck. Ipconfig yields no configuration at all.
If I can't get these machines to boot to the 32-bit boot images, I can't deploy 32-bit images, unless there's a way of which I'm unaware.
EDIT: A little extra background. My WindowsPE folder has two subfolders called x86 and x64. Obviously, 32-bit drivers go into the x86 folder and 64-bit drivers go into the x64 folder. Then in the properties of the deployment share a
selection profile is selected which points to the architecture-specific folders.

Specifically what do you see when you are in WinPE, press the F8 button, and run ipconfig.
1. ipconfig shows no network adapters (see:
http://myitforum.com/cs2/blogs/rpedersen/clip_image002_53DA17D4.jpg ). This means you still have not loaded the correct device drivers, check the c:\windows\system32\wpeinit.log file.
2. ipconfig shows an "autoconfiguration IPv4 Address" with a netmastk of 255.255.0.0. This means that the client did not get an IP address from the DHCP server. Double check the connection between the client and the DHCP server.
3. ipconfig shows a correct address. There is no problem. :^)
Keith Garner - keithga.wordpress.com
I get the first result. Absolutely no network adapters, which I assumed indicated no appropriate device driver.
This is the result of the wpeinit.log from the machine booting to the 32-bit boot image:
Info WPEINIT is processing the unattend file [X:\unattend.xml]
Info Spent 1747ms initializing removable media before unattend search
Info ==== Initializing Display Settings ====
Info Setting display resolution 1024x768x32@60: 0x00000000
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Computer Name ====
Info Generating a random computer name
Info No computer name specified, generating a random name.
Info Renaming computer to MININT-TFRU2BT.
Info Acquired profiling mutex
Info Service winmgmt disable: 0x00000000
Info Service winmgmt stop: 0x00000000
Info Service winmgmt enable: 0x00000000
Info Released profiling mutex
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Virtual Memory Paging File ====
Info No WinPE page file setting specified
Info STATUS: SUCCESS (0x00000001)
Info ==== Initializing Optional Components ====
Info WinPE optional component 'Microsoft-WinPE-HTA' is present
Info WinPE optional component 'Microsoft-WinPE-MDAC' is present
Info WinPE optional component 'Microsoft-WinPE-WMI' is present
Info WinPE optional component 'Microsoft-WinPE-WSH' is present
Info STATUS: SUCCESS (0x00000000)
Info ==== Initializing Network Access and Applying Configuration ====
Info No EnableNetwork unattend setting was specified; the default action for this context is to enable networking support.
Info Acquired profiling mutex
Info Install MS_MSCLIENT: 0x0004a020
Info Install MS_NETBIOS: 0x0004a020
Info Install MS_SMB: 0x0004a020
Info Install MS_TCPIP6: 0x0004a020
Info Install MS_TCPIP: 0x0004a020
Info Service dhcp start: 0x00000000
Info Service lmhosts start: 0x00000000
Info Service ikeext start: 0x00000000
Info Service mpssvc start: 0x00000000
Info Released profiling mutex
Info Spent 749ms installing network components
Info Spent 1669ms installing network drivers
Error QueryAdapterStatus: no adapters found.
Info Spent 0ms confirming network initialization; status 0x80004005
Info WaitForNetworkToInitialize failed; ignoring error
Info STATUS: SUCCESS (0x003d0001)
Info ==== Applying Firewall Settings ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Executing Synchronous User-Provided Commands ====
Info Parsing RunSynchronousCommand: 1 entries
Info Command 0: 0x00000000
Info Successfully executed command 'wscript.exe X:\Deploy\Scripts\LiteTouch.wsf' (exit code 0x00000000)
Info STATUS: SUCCESS (0x00000000)
Info ==== Executing Asynchronous User-Provided Commands ====
Info STATUS: SUCCESS (0x00000001)
Info ==== Applying Shutdown Settings ====
Info No shutdown setting was specified
Info STATUS: SUCCESS (0x00000001)
At first I thought the first bolded section might be relevant, but when I booted to the x64 boot image, which works fine, I get the same message in its wpeinit.log file. The only difference between the two log files is that the x64 boot image actually
shows successful installation of a driver where the second bolded section is.

How to set the default boot kernel in /etc/default/grub or /etc/grub.d

and without messing with /boot/grub/grub.cfg ?
I need this so that new kernels show up but do not change the default boot kernel
Is there a way to do it by file name instead of position within the menuentry / submenu list?
I found some ubuntu and fedora sugestions but all by position, none by name
AND how to set the kdump kernel as the default?
Arch is putting this kernel under a submenu - would this pose problems for setting it as the default?
Last edited by Sanjeev K Sharma (2015-04-06 12:59:22)

Sanjeev K Sharma wrote:
and without messing with /boot/grub/grub.cfg ?
I need this so that new kernels show up but do not change the default boot kernel
Is there a way to do it by file name instead of position within the menuentry / submenu list?
I found some ubuntu and fedora sugestions but all by position, none by name
AND how to set the kdump kernel as the default?
Arch is putting this kernel under a submenu - would this pose problems for setting it as the default?
In /etc/default/grub you can use the name of your entry you wish to use as default
GRUB_DEFAULT='Arch Linux, with Linux core repo kernel'
You can tell grub to stop using submenus by doing:
GRUB_DISABLE_SUBMENU=y
Or you can just make a purely custom menuentry in /etc/grub.d/40_custom if you'd like:
menuentry "Other Linux" {
linux <KERNEL IMAGE HERE>
initrd <INITRD IMAGE HERE>
EDIT: /etc/grub/default -> /etc/default/grub
Last edited by Slabity (2015-04-07 11:16:22)

Cisco 6500 with SUP 720 - Invalid boot Image

Diagnostic sanity check on the 6500 reports Invalid boot image "bootdisk:<output omitted>
The boot statement on the 6500 is :-
boot system bootdisk:<filename.bin> and the 6500 boots fine.
Please advise.
Thank You.

Hi ,
I have found bug which is internally found by cisco.The bug is CSCsc98471 and following are details of bug .
The command "show diagnostic sanity" checks amongst other things, if the current bootstring is matching pointing to an existing file.
Since ION bootstring format has been extended (assuming an installed image) this check fails although the bootstring is correct.
Can be easily reproduced by entering the "show diagnostic sanity" command.
6500-6#show diagnostic sanity
Pinging default gateway 172.26.197.33
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.26.197.33, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Could not verify boot image "sup-bootdisk:/newsys/s72033/base/s72033-adventerprisek9_wan_dbg-vm," specified in the boot string.
6500-6#show bootvar
BOOT variable = sup-bootdisk:/newsys/s72033/base/s72033-adventerprisek9_wan_dbg-vm,12;
6500-6#dir sup-bootflash:/newsys/s72033/base/
Directory of sup-bootdisk:/newsys/s72033/base/
84 -rwx 1375696 Jan 5 2006 20:51:24 -08:00 imf.tar
85 -rwx 12873200 Jan 5 2006 20:51:22 -08:00 s72033-adventerprisek9_wan_dbg-vm
It is found in 12.2(18.09.20)SX3.39.
*** open a TAC case so that the same bug is fixed in 12.2(18)SXF4.
Hope it helps you.Plz rate it.
Thanks,
satish

R2 upgrade and custome boot images

Hi Guys
What happens to the custom boot images after the upgrade to R2 from SP1? There are some boot images customised to be able to connect to 802.1x secured wired network and I was wondering what will happen to them after upgrade?

They're not gone after the upgrade so there's nothing to re-import thus yes you can still use them although boot images based on WinPE 4.0 are not technically supported in R2 (though they should work). You won't be able to add drivers to them or
maintain them in the console either. You should put in the effort to customize WinPE 5.0 based boot images for the long run though.
Also note that Win8 won't be supported anymore after October of this year (http://support.microsoft.com/lifecycle/search/default.aspx?alpha=Windows+8&Filter=FilterNO&wa=wsignin1.0) so
you should plan to move to Win 8.1 Update ASAP for your deployments.
Jason | http://blog.configmgrftw.com

2 questions - missing boot image, create mdt task sequence button missing

I'm learning SCCM 2012. I am watching a training video and the instructor shows a "Create MDT Task Sequence" button at the top of his ribbon bar when going into Task Sequence. I do not have this button - where did it go? I am
using 2012 SP1.
All I see is "Create Task Sequence" and "Create Task Sequence Media" but not "Create MDT Task Sequence".
Also - I only have an x86 boot image, and no x64. How do I get this into my inventory?
Thank you
Nathan

"Create MDT Task Sequence" will be visible after you install MDT and integrate it to SCCM.
MDT is different product and not part of default SCCM installation.
You can integrate MDT to SCCM to create advanced Task Sequence if the default is not suitable for your needs.
Integrate MDT to SCCM.
MDT latest version is 2013:
http://www.microsoft.com/en-us/download/details.aspx?id=40796
For creating x64 boot image:
http://social.technet.microsoft.com/Forums/en-US/a3877a66-d35c-49ca-95c5-1c02d1611f2f/default-x64-boot-image-not-created-during-sccm-2012-setup
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.

Modify default installation path of WindowsApps

Modify default installation path of WindowsApps
First explain, I am a Chinese Windows user, my English fighting is only 5（very poor）.Then I will try to use some simple English to tell you my problem.
I use the method used in windows8 to modify default installation path of WindowsApps,but defeated.
Why I want to modify default installation path of WindowsApps?
Because when I installed software that is suitable for the traditional model, my C disc had only 10GB space.
I think Win8.1 is perfect.And I like the traditional mode and Metro interface.(I heard Win9 can’t use two modes at the same time,but I think simultaneous use of two modes the operation is very nice.)
The method used in windows8:
First,Enter WinPE,create a file that is the mirror image of WindowsApps in D disc.
Then,Enter Win8.1,make User get thechanges to the “Appx” folder under theregistry.
Last,Amended registry master key of “packageRoot”as “D:/WindowsApps”
This operation can be completed in Win8,but default in Win8.1.
So,could you tell me how to modify default installation path of WindowsApps?
If it’s impossible ,I hope Microsoft team could solve it.

In my opinion it's a bad idea to change this, as most software is set to install on drive C: and not all of it may be using the proper CSIDL system calls to get the locations.
You can be sure the majority of testing is done with applications installing in the system default location on C:.
A much better idea is to save a few Yuan and buy a much larger SSD for the system drive, then use the default drive C: locations for the operating system and installed programs.
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

PE Boot image broke

I was trying add this driver to my PE image and after 3 hours it said it couldn't apply it and now every time I try to view properties on the PE I get errors and I can't see ANY of the previous drivers and had added. I did make a copy of the boot.P010002.wim
but when I point to that I get the same errors, what do I do, I need to restore the previous image?? I SCCM 2007 I could just remove the bad driver but can't now.
http://www.dell.com/support/home/us/en/04/Drivers/DriversDetails?driverId=D6FX1&fileId=3299660477&osCode=WB64A&productCode=precision-m3800-workstation&languageCode=EN&categoryId=NI
HELP
ConfigMgr Error Object:
instance of __ExtendedStatus
Description = "[42000][191][Microsoft][SQL Server Native Client 11.0][SQL Server]Some part of your SQL statement is nested too deeply. Rewrite the query or break it up into smaller queries.";
Operation = "ExecQuery";
ParameterInfo = "SELECT CI_ID,CI_UniqueID,LocalizedDisplayName FROM SMS_Driver WHERE CI_ID = 16825009 OR CI_ID = 16825025 OR CI_ID = 16825026 OR CI_ID = 16825044 OR CI_ID = 16825045 OR CI_ID = 16825046 OR CI_ID = 16825047 OR CI_ID = 16825052 OR CI_ID
= 16825053 OR CI_ID = 16825055 OR CI_ID = 16825056 OR CI_ID = 16825130 OR CI_ID = 16825131 OR CI_ID = 16825132 OR CI_ID = 16825133 OR CI_ID = 16825154 OR CI_ID = 16825398 OR CI_ID = 16825399 OR CI_ID = 16825400 OR CI_ID = 16825483 OR CI_ID = 16825484 OR CI_ID
= 16825485 OR CI_ID = 16825548 OR CI_ID = 16825549 OR CI_ID = 16825550 OR CI_ID = 16825555 OR CI_ID = 16825557 OR CI_ID = 16825558 OR CI_ID = 16825560 OR CI_ID = 16825561 OR CI_ID = 16825563 OR CI_ID = 16825564 OR CI_ID = 16825565 OR CI_ID = 16825567 OR CI_ID
= 16825568 OR CI_ID = 16825569 OR CI_ID = 16825600 OR CI_ID = 16825601 OR CI_ID = 16825602 OR CI_ID = 16825603 OR CI_ID = 16825604 OR CI_ID = 16825605 OR CI_ID = 16825902 OR CI_ID = 16825903 OR CI_ID = 16825905 OR CI_ID = 16825906 OR CI_ID = 16825914 OR CI_ID
= 16825969 OR CI_ID = 16826022 OR CI_ID = 16826044 OR CI_ID = 16826045 OR CI_ID = 16826047 OR CI_ID = 16826059 OR CI_ID = 16826060 OR CI_ID = 16826062 OR CI_ID = 16826063 OR CI_ID = 16826263 OR CI_ID = 16826264 OR CI_ID = 16826265 OR CI_ID = 16826266 OR CI_ID
= 16826267 OR CI_ID = 16826268 OR CI_ID = 16826269 OR CI_ID = 16826323 OR CI_ID = 16826324 OR CI_ID = 16826902 OR CI_ID = 16826903 OR CI_ID = 16826904 OR CI_ID = 16826905 OR CI_ID = 16826906 OR CI_ID = 16826907 OR CI_ID = 16826908 OR CI_ID = 16826909 OR CI_ID
= 16826910 OR CI_ID = 16826911 OR CI_ID = 16826912 OR CI_ID = 16826913 OR CI_ID = 16826914 OR CI_ID = 16826915 OR CI_ID = 16826916 OR CI_ID = 16826917 OR CI_ID = 16826918 OR CI_ID = 16826919 OR CI_ID = 16826920 OR CI_ID = 16826921 OR CI_ID = 16826922 OR CI_ID
= 16826923 OR CI_ID = 16826924 OR CI_ID = 16826925 OR CI_ID = 16826926 OR CI_ID = 16826934 OR CI_ID = 16826935 OR CI_ID = 16826936 OR CI_ID = 16826957 OR CI_ID = 16826958 OR CI_ID = 16826959 OR CI_ID = 16826960 OR CI_ID = 16826961 OR CI_ID = 16826962 OR CI_ID
= 16826963 OR CI_ID = 16826964 OR CI_ID = 16826965 OR CI_ID = 16826966 OR CI_ID = 16826967 OR CI_ID = 16826968 OR CI_ID = 16826969 OR CI_ID = 16826970 OR CI_ID = 16826971 OR CI_ID = 16826972 OR CI_ID = 16826973 OR CI_ID = 16826974 OR CI_ID = 16826975 OR CI_ID
= 16826976 OR CI_ID = 16826977 OR CI_ID = 16826978 OR CI_ID = 16826979 OR CI_ID = 16826980 OR CI_ID = 16826981 OR CI_ID = 16826982 OR CI_ID = 16826983 OR CI_ID = 16827019 OR CI_ID = 16827021 OR CI_ID = 16827164 OR CI_ID = 16827165 OR CI_ID = 16827166 OR CI_ID
= 16827167 OR CI_ID = 16827168 OR CI_ID = 16827170 OR CI_ID = 16827180 OR CI_ID = 16827181 OR CI_ID = 16827182 OR CI_ID = 16827183 OR CI_ID = 16827265 OR CI_ID = 16827266 OR CI_ID = 16827267 OR CI_ID = 16827268 OR CI_ID = 16827269 OR CI_ID = 16827270 OR CI_ID
= 16827271 OR CI_ID = 16827272 OR CI_ID = 16827273 OR CI_ID = 16827274 OR CI_ID = 16827275 OR CI_ID = 16827276 OR CI_ID = 16827277 OR CI_ID = 16827278 OR CI_ID = 16827279 OR CI_ID = 16827280 OR CI_ID = 16827281 OR CI_ID = 16827282 OR CI_ID = 16827283 OR CI_ID
= 16827284 OR CI_ID = 16827285 OR CI_ID = 16827286 OR CI_ID = 16827287 OR CI_ID = 16827288 OR CI_ID = 16827289 OR CI_ID = 16827290 OR CI_ID = 16827291 OR CI_ID = 16827292 OR CI_ID = 16827293 OR CI_ID = 16827294 OR CI_ID = 16827295 OR CI_ID = 16827296 OR CI_ID
= 16827297 OR CI_ID = 16827298 OR CI_ID = 16827299 OR CI_ID = 16827300 OR CI_ID = 16827301 OR CI_ID = 16827302 OR CI_ID = 16827303 OR CI_ID = 16827304 OR CI_ID = 16827308 OR CI_ID = 16827310 OR CI_ID = 16887181 OR CI_ID = 16887182 OR CI_ID = 16887183 OR CI_ID
= 16887184 OR CI_ID = 16887185 OR CI_ID = 16887186 OR CI_ID = 16887187 OR CI_ID = 16887188 OR CI_ID = 16887189 OR CI_ID = 16887190 OR CI_ID = 16887191 OR CI_ID = 16887192 OR CI_ID = 16887193 OR CI_ID = 16887194 OR CI_ID = 16887210 OR CI_ID = 16887211 OR CI_ID
= 16887212 OR CI_ID = 16887213 OR CI_ID = 16887214 OR CI_ID = 16887215 OR CI_ID = 16887216 OR CI_ID = 16887217 OR CI_ID = 16887218 OR CI_ID = 16887219 OR CI_ID = 16887220 OR CI_ID = 16887221 OR CI_ID = 16887222 OR CI_ID = 16887223 OR CI_ID = 16887224 OR CI_ID
= 16887225 OR CI_ID = 16901659 OR CI_ID = 16901660 OR CI_ID = 17024972 OR CI_ID = 17024973 OR CI_ID = 17024974 OR CI_ID = 17024975 OR CI_ID = 17024976 OR CI_ID = 17024977 OR CI_ID = 17024978 OR CI_ID = 17024979 OR CI_ID = 17024980 OR CI_ID = 17024981 OR CI_ID
= 17024982 OR CI_ID = 17024983 OR CI_ID = 17027382 OR CI_ID = 17027383 OR CI_ID = 17133063 OR CI_ID = 17133064 OR CI_ID = 17133065 OR CI_ID = 17133066 OR CI_ID = 17133067 OR CI_ID = 17133068 OR CI_ID = 17133069 OR CI_ID = 17133070 OR CI_ID = 17133071 OR CI_ID
= 17133072 OR CI_ID = 17133073 OR CI_ID = 17133074 OR CI_ID = 17133075 OR CI_ID = 17133076 OR CI_ID = 17133077 OR CI_ID = 17133078 OR CI_ID = 17133079 OR CI_ID = 17133080 OR CI_ID = 17133081 OR CI_ID = 17133082 OR CI_ID = 17133083 OR CI_ID = 17133084 OR CI_ID
= 17133085 OR CI_ID = 17133086 OR CI_ID = 17133087 OR CI_ID = 17133088 OR CI_ID = 17133089 OR CI_ID = 17133090 OR CI_ID = 17133091 OR CI_ID = 17133092 OR CI_ID = 17133093 OR CI_ID = 17133094 OR CI_ID = 17133095 OR CI_ID = 17133096 OR CI_ID = 17133097 OR CI_ID
= 17133098 OR CI_ID = 17133099 OR CI_ID = 17133100 OR CI_ID = 17133101 OR CI_ID = 17133102 OR CI_ID = 17133103 OR CI_ID = 17133104 OR CI_ID = 17133105 OR CI_ID = 17133106 OR CI_ID = 17133107 OR CI_ID = 17133108 OR CI_ID = 17133109 OR CI_ID = 17133110 OR CI_ID
= 17133111 OR CI_ID = 17133112 OR CI_ID = 17133113 OR CI_ID = 17133114 OR CI_ID = 17133115 OR CI_ID = 17133116 OR CI_ID = 17133117 OR CI_ID = 17133118 OR CI_ID = 17133119 OR CI_ID = 17133120 OR CI_ID = 17133121 OR CI_ID = 17133122 OR CI_ID = 17133123 OR CI_ID
= 17133124 OR CI_ID = 17133125 OR CI_ID = 17133126 OR CI_ID = 17133127 OR CI_ID = 17133128 OR CI_ID = 17133129 OR CI_ID = 17133130 OR CI_ID = 17133131 OR CI_ID = 17133132 OR CI_ID = 17133133 OR CI_ID = 17133134 OR CI_ID = 17133135 OR CI_ID = 17133136 OR CI_ID
= 17133137 OR CI_ID = 17133138 OR CI_ID = 17133139 OR CI_ID = 17133140 OR CI_ID = 17133141 OR CI_ID = 17133142 OR CI_ID = 17133143 OR CI_ID = 17133144 OR CI_ID = 17133145 OR CI_ID = 17133146 OR CI_ID = 17133147 OR CI_ID = 17133148 OR CI_ID = 17133149 OR CI_ID
= 17133150 OR CI_ID = 17133151 OR CI_ID = 17133152 OR CI_ID = 17133153 OR CI_ID = 17133154 OR CI_ID = 17133155 OR CI_ID = 17133156 OR CI_ID = 17133157 OR CI_ID = 17133158 OR CI_ID = 17133159 OR CI_ID = 17133160 OR CI_ID = 17133161 OR CI_ID = 17133162 OR CI_ID
= 17133163 OR CI_ID = 17133164 OR CI_ID = 17133165 OR CI_ID = 17133166 OR CI_ID = 17133167 OR CI_ID = 17133168 OR CI_ID = 17133169 OR CI_ID = 17133170 OR CI_ID = 17133171 OR CI_ID = 17133172 OR CI_ID = 17133173 OR CI_ID = 17133174 OR CI_ID = 17133175 OR CI_ID
= 17133176 OR CI_ID = 17133177 OR CI_ID = 17133178 OR CI_ID = 17133179 OR CI_ID = 17133180 OR CI_ID = 17133181 OR CI_ID = 17133182 OR CI_ID = 17133183 OR CI_ID = 17133184 OR CI_ID = 17133185 OR CI_ID = 17133186 OR CI_ID = 17133187 OR CI_ID = 17133188 OR CI_ID
= 17133189 OR CI_ID = 17133190 OR CI_ID = 17133191 OR CI_ID = 17133192 OR CI_ID = 17133193 OR CI_ID = 17133194 OR CI_ID = 17133195 OR CI_ID = 17133196 OR CI_ID = 17133197 OR CI_ID = 17133198 OR CI_ID = 17133199 OR CI_ID = 17133200 OR CI_ID = 17133201 OR CI_ID
= 17133202 OR CI_ID = 17133203 OR CI_ID = 17133204 OR CI_ID = 17133205 OR CI_ID = 17133206 OR CI_ID = 17133207 OR CI_ID = 17133208 OR CI_ID = 17133209 OR CI_ID = 17133210 OR CI_ID = 17133211 OR CI_ID = 17133212 OR CI_ID = 17133213 OR CI_ID = 17133214 OR CI_ID
= 17133215 OR CI_ID = 17133216 OR CI_ID = 17133217 OR CI_ID = 17133218 OR CI_ID = 17133219 OR CI_ID = 17133220 OR CI_ID = 17133221 OR CI_ID = 17133222 OR CI_ID = 17133223 OR CI_ID = 17133224 OR CI_ID = 17133225 OR CI_ID = 17133226 OR CI_ID = 17133227 OR CI_ID
= 17133228 OR CI_ID = 17133229 OR CI_ID = 17133230 OR CI_ID = 17133231 OR CI_ID = 17133232 OR CI_ID = 17133233 OR CI_ID = 17133234 OR CI_ID = 17133235 OR CI_ID = 17133236 OR CI_ID = 17133237 OR CI_ID = 17133238 OR CI_ID = 17133239 OR CI_ID = 17133240 OR CI_ID
= 17133241 OR CI_ID = 17133242 OR CI_ID = 17133243 OR CI_ID = 17133244 OR CI_ID = 17133245 OR CI_ID = 17133246 OR CI_ID = 17133247 OR CI_ID = 17133248 OR CI_ID = 17133249 OR CI_ID = 17133250 OR CI_ID = 17133251 OR CI_ID = 17133252 OR CI_ID = 17133253 OR CI_ID
= 17133254 OR CI_ID = 17133255 OR CI_ID = 17133256 OR CI_ID = 17133257 OR CI_ID = 17133258 OR CI_ID = 17133259 OR CI_ID = 17133260 OR CI_ID = 17133261 OR CI_ID = 17133262 OR CI_ID = 17133263 OR CI_ID = 17133264 OR CI_ID = 17133265 OR CI_ID = 17133266 OR CI_ID
= 17133267 OR CI_ID = 17133268 OR CI_ID = 17133269 OR CI_ID = 17133270 OR CI_ID = 17133271 OR CI_ID = 17133272 OR CI_ID = 17133273 OR CI_ID = 17133274 OR CI_ID = 17133275 OR CI_ID = 17133276 OR CI_ID = 17133277 OR CI_ID = 17133278 OR CI_ID = 17133279 OR CI_ID
= 17133280 OR CI_ID = 17133281 OR CI_ID = 17133282 OR CI_ID = 17133283 OR CI_ID = 17133284 OR CI_ID = 17133285 OR CI_ID = 17133286 OR CI_ID = 17133287 OR CI_ID = 17133288 OR CI_ID = 17133289 OR CI_ID = 17133290 OR CI_ID = 17133291 OR CI_ID = 17133292 OR CI_ID
= 17133293 OR CI_ID = 17133294 OR CI_ID = 17133295 OR CI_ID = 17133296 OR CI_ID = 17133297 OR CI_ID = 17133298 OR CI_ID = 17133299 OR CI_ID = 17133300 OR CI_ID = 17133301 OR CI_ID = 17133302 OR CI_ID = 17133303 OR CI_ID = 17133304 OR CI_ID = 17133305 OR CI_ID
= 17133306 OR CI_ID = 17133307 OR CI_ID = 17133308 OR CI_ID = 17133309 OR CI_ID = 17133310 OR CI_ID = 17133311 OR CI_ID = 17133312 OR CI_ID = 17133313 OR CI_ID = 17133314 OR CI_ID = 17133315 OR CI_ID = 17133316 OR CI_ID = 17133317 OR CI_ID = 17133318 OR CI_ID
= 17133319 OR CI_ID = 17133320 OR CI_ID = 17133321 OR CI_ID = 17133322 OR CI_ID = 17133323 OR CI_ID = 17133324 OR CI_ID = 17133325 OR CI_ID = 17133326 OR CI_ID = 17133327 OR CI_ID = 17133328 OR CI_ID = 17133329 OR CI_ID = 17133330 OR CI_ID = 17133331 OR CI_ID
= 17133332 OR CI_ID = 17133333 OR CI_ID = 17133334 OR CI_ID = 17133335 OR CI_ID = 17133336 OR CI_ID = 17133337 OR CI_ID = 17133338 OR CI_ID = 17133339 OR CI_ID = 17133340 OR CI_ID = 17133341 OR CI_ID = 17133342 OR CI_ID = 17133343 OR CI_ID = 17133344 OR CI_ID
= 17133345 OR CI_ID = 17133346 OR CI_ID = 17133347 OR CI_ID = 17133348 OR CI_ID = 17133349 OR CI_ID = 17133350 OR CI_ID = 17133351 OR CI_ID = 17133515 OR CI_ID = 17133791 OR CI_ID = 17133966 OR CI_ID = 17133967 OR CI_ID = 17133968 OR CI_ID = 17133969 OR CI_ID
= 17133970 OR CI_ID = 17133971 OR CI_ID = 17133972 OR CI_ID = 17133973 OR CI_ID = 17133974 OR CI_ID = 17133975 OR CI_ID = 17133976 OR CI_ID = 17133977 OR CI_ID = 17133978 OR CI_ID = 17133979 OR CI_ID = 17133980 OR CI_ID = 17133981 OR CI_ID = 17133982 OR CI_ID
= 17133983 OR CI_ID = 17133984 OR CI_ID = 17133985 OR CI_ID = 17133986 OR CI_ID = 17133987 OR CI_ID = 17133988 OR CI_ID = 17133989 OR CI_ID = 17134012 OR CI_ID = 17134013 OR CI_ID = 17134014 OR CI_ID = 17134015 OR CI_ID = 17134016 OR CI_ID = 17134017 OR CI_ID
= 17134018 OR CI_ID = 17134019 OR CI_ID = 17134020 OR CI_ID = 17134021 OR CI_ID = 17134022 OR CI_ID = 17134023 OR CI_ID = 17134024 OR CI_ID = 17134025 OR CI_ID = 17134026 OR CI_ID = 17134027 OR CI_ID = 17134028 OR CI_ID = 17134029 OR CI_ID = 17134030 OR CI_ID
= 17134031 OR CI_ID = 17134032 OR CI_ID = 17134033 OR CI_ID = 17134034 OR CI_ID = 17134035 OR CI_ID = 17134036 OR CI_ID = 17134037 OR CI_ID = 17134038 OR CI_ID = 17134039 OR CI_ID = 17134040 OR CI_ID = 17134041 OR CI_ID = 17134042 OR CI_ID = 17134043 OR CI_ID
= 17134044 OR CI_ID = 17134045 OR CI_ID = 17134046 OR CI_ID = 17134047 OR CI_ID = 17134048 OR CI_ID = 17134049 OR CI_ID = 17134050 OR CI_ID = 17134051 OR CI_ID = 17134052 OR CI_ID = 17134053 OR CI_ID = 17134054 OR CI_ID = 17134055 OR CI_ID = 17134056 OR CI_ID
= 17134057 OR CI_ID = 17134058 OR CI_ID = 17134059 OR CI_ID = 17134060 OR CI_ID = 17134061 OR CI_ID = 17134062 OR CI_ID = 17134063 OR CI_ID = 17134064 OR CI_ID = 17134065 OR CI_ID = 17134066 OR CI_ID = 17134067 OR CI_ID = 17134068 OR CI_ID = 17134069 OR CI_ID
= 17134070 OR CI_ID = 17134071 OR CI_ID = 17134072 OR CI_ID = 17134073 OR CI_ID = 17134074 OR CI_ID = 17134075 OR CI_ID = 17134076 OR CI_ID = 17134077 OR CI_ID = 17134078 OR CI_ID = 17134079 OR CI_ID = 17134080 OR CI_ID = 17134081 OR CI_ID = 17134082";
ProviderName = "WinMgmt";
StatusCode = 2147749889;
Error Code:
Failed
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException
The SMS Provider reported an error.
Stack Trace:
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
   at Microsoft.ConfigurationManagement.ManagementProvider.QueryProcessorBase.ProcessQuery(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
System.Management.ManagementException
Generic failure
Stack Trace:
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()
   at Microsoft.ConfigurationManagement.ManagementProvider.QueryProcessorBase.ProcessQuery(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)

The boot.wim should still be default, the one with the package id is created based on that boot image. If you don't like to do it in the same location, you can simply copy it to a different location and use it from there.
I wouldn't know how to troubleshoot this particular issue, as you're not able to edit the boot image anymore. You can also create a CSS ticket (with Microsoft), but probably recreating the boot image is much faster then solving the issue.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Set a fullscreen Boot image

Hi,
I know that I can change the boot image by simply replacing the file BootLogo.png into another one with the image I want to appear at the startup screen.
But I want this image to be fullscreen size, and I cannot do that, as I don't know where or how to configure it.
So, how do I set a boot image as fullscreen?

Something funny is happening here!
Before testing something (I'll say later) I would say the things below:
>>
Maybe I haven't expressed myself properly.
I don't want to change the login background picture, I want to change the boot picture (the gray apple that appears at the startup, when you turn on your mac) and its size.
That gray apple file (BootLogo.png) is located at the same place as the DefaultDesktop.jpg file is. See image below.
The point is that I don't know how to change the boot picture size (to fullscreen, for example).
<<
But just after writing all that, I've thought that this file (BootLogo.png) could habe been created by BootXChanger. So then, I opened that program and set the boot image to the default (the gray apple), deleted that .png file and restarted the computer.
I noticed that the original gray apple appeared at the startup (boot) screen without troubles and that the BootLogo.png file hadn't been restored (as if the OS did not need that file).
After that, I opened the BootXChanger.app to change the boot image again and the BootLogo.png file reappeared.
So, now, I have 2 questions:
- the original one; how do I set a fullscreen boot image?
- and; if the BootLogo.png file doesn't exist, how do I change the boot image without having BootXChanger?

Changing bios boot image

Are there any tools in order to change the bios boot image. I would like to change the default image for a custom one.
My motherboard is a MSI MS-7071 (PM8M2-V)
Thanks
Paul

hi there, welcome to forum.
if you are talking about custom logos,(if not explain better what you have try to do) have a look here: https://forum-en.msi.com/index.php?topic=103944.msg764287#msg764287
but remember any BIOS modifycation has to use at own risk.

Modifying default boot image

Similar Messages

Maybe you are looking for