Boot Image properties...tabs missing

I updated our SCCM system to R2 yesterday...today when I went in to edit a boot image I no longer see the "drivers" tab...it seems like there are other tabs missing as well, just can't remember. Don't know how to add drivers to a boot image
now.
Server 2008 R2
SCCM 2012 R2

This is a common problem. It came up on the forum yesterday as well.
http://social.technet.microsoft.com/Forums/en-US/a42ab116-63f1-431b-a42c-f31f2bdf0896/upgrade-to-sccm-r2-have-to-recreate-boot-image-and-ts?forum=configmanagergeneral
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Similar Messages

Image Processor Tab Missing in New Adobe Bridge CC 2014

In the new Bridge CC you used to have a TAB under tools called Photoshop which you could run the script Image Processor for easily processing jpegs. What has happened to this and is their maybe a new way of processing jpegs to lo-res that I dont know about from tiff or jpeg or does my bridge have a problem?
I have attached a image grab from my bridge that shows that the tab is not there. I know that you can access image processor directly from Photoshop, but they used to always be linked.

No, it is still in Bridge CC.
Did you uninstall Photoshop CC after installing Photoshop CC 2014? If so, that may have removed some of the Bridge integration scripts by mistake. Re-installing Photoshop CC 2014 should replace the scripts.
and it should give the image processor tab back

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

How to identifiy Faulty Driver in Boot Image (Reverse Engineering of Adding a Driver to Boot Image)

Hello SCCM'lovers
I'm having a new EliteBook 820 G2 here which Fails PXE boot due to a false corrupted
Intel Advanced Network Service Virtual Adapter-Driver.
The PROBLEM now is how to determine under Boot Images - Properties - Drivers ... the correct one.
(see pic)
Over the months, I injected different ones. smsts.log indicates me that this driver is the problem but how can I reverse engineer it to find the correct version/timestamp whatever it on my DP

in theory at least there is a way.
The driver loading in windows will select the best driver based on the PNP-id, version of driver, if it's signed and so on.
you can find the PNP deviceID for that hardware on a installed system by looking in device manager.
After that you can follow the same rules that the system uses to determine which driver it would load by reading the inf files for each driver.
Would it be faster to just create a new one - most likely.
I also would recommend that you create a dedicated driver folder and category in SCCM for WinPE and only add the drivers you need. I prefer to use Original vendor drivers here (aka nicdrivers straight from Intel instead of DELL or HP or ... repackaged
versions

SCCM 2012 RTM to SP1 to R2 Boot Images Migration What steps to be consider

We are Migrating SCCm 2012 to SP1 then to R2…
My question would be specific to Boot images.
We are in RTM edition, we have different boot images got created by our Imaging guys, These boot Images also have network/mass storage drivers are added along with some WINPE Back Group screen wallpaper, when cross checked the boot image properties. And
finally these the Boot Images are distributed to all the required distribution points.
Help me to understand what are the action steps to be taken now? In the process of RTM to SP1 and R2
HunBoy Started learning from this page

From RTM to SP1, the upgrade process will upgrade your WinPE 3.x boot images to WinPE 4.0 (if it can). From SP1 to R2, the upgrade process will not upgrade your boot images but will instead create new ones. Only WinPE 5.0 and WinPE 3.1 boot images are supported
by R2 -- the 3.1 boot images are meant for supporting XP since WInPE 5.0 doesn't support XP (God help you if you're still on XP though).
Thus, you need to get your "imaging" guys to create new WinPE 5.0 boot images.
Jason | http://blog.configmgrftw.com

How to load a boot image to cisco aironet 1140 series after missing boot image

Hi all,
I need a solution for this. When i switch my cisco aironet 1140 , it s blinking with red light .and gives a message "no boot image to load".
When i tried next time, by pressing escape it shows this message that i have mentioned below.
ap:
ap:
using eeprom values
WRDTR,CLKTR: 0x83000800 0x40000000
RQDC ,RFDC : 0x80000035 0x00000208
using ÿÿÿÿ ddr static values from serial eeprom
ddr init done
Running Normal Memtest...
Passed.
IOS Bootloader - Starting system.
FLASH CHIP: Numonyx P33
Checking for Over Erased blocks
Xmodem file system is available.
DDR values used from system serial eeprom.
WRDTR,CLKTR: 0x83000800, 0x40000000
RQDC, RFDC : 0x80000035, 0x00000208
PCIE0: link is up.
PCIE0: VC0 is active
PCIE1: link is NOT up.
PCIE1 port 1 not initialized
PCIEx: initialization done
flashfs[0]: 1 files, 1 directories
flashfs[0]: 0 orphaned files, 0 orphaned directories
flashfs[0]: Total bytes: 32385024
flashfs[0]: Bytes used: 1536
flashfs[0]: Bytes available: 32383488
flashfs[0]: flashfs fsck took 16 seconds.
Reading cookie from system serial eeprom...Done
Base Ethernet MAC address: 28:94:0f:d6:c8:62
Ethernet speed is 100 Mb - FULL duplex
The system is unable to boot automatically because there
are no bootable files.
C1140 Boot Loader (C1140-BOOT-M) Version 12.4(23c)JA3, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Compiled Tue 18-Oct-11 14:51 by prod_rel_team
ap:
So , now my question is how to load the boot image ? From where will we get this ? OR
I m also having another Cisco aironet 1140 , Can i get bootimage from that . Kindly let me know the solution from genius ?

Take a look at this link as it should have the info you need
https://supportforums.cisco.com/docs/DOC-14636
Sent from Cisco Technical Support iPhone App

Property missing in Node Properties tab

Hi,
I have created a Boolean Local Node property 'DoNotModify' with default value 'FALSE' and assigned it to a Property Category 'Accounts', but when i open the hierarchy and check the node properties in the 'Accounts' category the property is not showing up. I then wrote a property query on the same property and this is returning all the nodes in the hierarchy. So this means that the property has been created correctly, but why am i not able to see it in the Node Properties tab?? Please help. I am working in version 11.1.2.1.
Thanks,
Krishna
Edited by: 903463 on Jun 24, 2012 11:45 PM

Krishna,
You need to assign the new property to an appropriate node type of the hierarchy else you will not be able to view the properties.
If you still want to validate, click "Show all properties". This will available in later patches of 11.1.2.1. Not sure whih patch are you in of 11.1.2.1

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.

Boot Image French

Hi
I need to boot image in "French".
I view this:
http://www.petervanderwoude.nl/post/how-to-change-the-language-in-windows-pe-via-configmgr-2012/
I change 1031 for 1036, i check in <ConfigMgrInstallFolder>\OSD\bin\x64\0000040c\tsres.dll is present (OK).
I go to "Boot Images (x64), "properties", "Customization" tab.
Check "Enable prestart command", in comand line "cscript.exe SetSMSTSLanguageFolder.vbs /LocaleID:1036" and check "Includes files for the prestart command", Source Directory
\\ServerName\share (Full control, Everyone)
Update Distribution Point
But when i start deployment all in Eglish
Thanks

It's really nothing more than the steps outlined in that specific post. The only thing I can say is to double check everything. Make sure to save the script and test it and make sure to use the folder in which you saved the script is used with the
Includes files for the prestart command. After applying those changes simply update the distribution point(s) and it should create the updated boot image.
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Can't Find the Reflections parameter in my Properties Tab

So to do some basic reflections with a standard png image in Motion 4 I need to create a floor by rotating a color solid generator on its X-axis right. Then I just select that color solid layer in the layers tab, go to the properties tab of the inspector and check the Reflections parameter. Only there is no reflections parameter in my Properties tab, only the "Casts Reflections" parameter under Blending. I'm missing the Lighting and Shadows parameters in the Properties Tab also. I must be missing something major here right? Thanks,
Jagr

-Click the 2D/3D toggle on the right side of the group layer.
or
-Select the group and go to the Inspector, Group Tab and change the type to 3D.
The Light, Shadow and Reflections options only appear when the object is part of a 3D group.

Issues with Boot Images & PXE Booting Since SP1 Install

Good Afternoon All -
I recently updated to SP1, had some issues, but they got resolved. Now, though, I'm having an issue booting to PXE as well as updating any boot images created
before SP1 was installed. Booting to USB Bootable media using a newly created boot image seems to work fine.
Boot Images
When I update my DPs for any of my boot images in SCCM, they fail and i get the below error:
Error: The wizard detected the following problems when updating the boot image.
• Failed to install required components into the boot image
The SMS Provider reported an error.: ConfigMgr Error Object:
instance of SMS_ExtendedStatus
• Description = "Failed to insert OSD binaries into the WIM file";
• ErrorCode = 2152205056;
• File = "e:\\nts_sccm_release\\sms\\siteserver\\sdk_provider\\smsprov\\sspbootimagepackage.cpp";
• Line = 4566;
• ObjectInfo = "CSspBootImagePackage::PreRefreshPkgSrcHook";
• Operation = "ExecMethod";
• ParameterInfo = "SMS_BootImagePackage.PackageID=\"BBS0012F\"";
• ProviderName = "WinMgmt";
• StatusCode = 2147749889;
I've even gone as far as removing all drivers from the boot image, but still get the same message. I was able to create a couple of
new MDT boot images which seem to work fine, though. I am not sure which log file is for boot images, but nothing appeared in distmgr.log.
PXE Booting Issue
After trying many things, I removed PXE config from my site and uninstalled WDS then started all over again. Here's what I did and my results. Please tell me what I'm missing...
After uninstall & server reboot, I enabled PXE + every option in DP tab in SCCM
It automatically installed WDS (same server) and added the two boot images I had checked for PXE use. one x64 and one x86.
I checked my DHCP Scope whose values hadn't changed sine it worked (that I know of). They are:
Option #66: 192.168.20.37 (SCCM Server/DP/PXE)
Option #67 \boot\x86\wdsnbp.com. I've tried \boot\x86\pxeboot.com as well as each of these with x64.
When I PXE boot from a workstation, I receive an IP, a bit of info, then it goes to Contacting Server.... When trying one of the boot files above, I was prompted for F12, but receved a blue screen with error. When trying all other boot files,
they just hang at Contacting Server until they timeout.
I looked at SMSPXE.log and found something interesting...
The IDs for the two boot images I have assigned to PXE are ABC003B3 & ABC00B36. In the smspxe.log, though, it keeps repeating "could not find boot image ABC0012F! 12F does exist and is a boot image,
but not the one I want to use by any means and does not have PXE checked.
I went ahead and checked 12F, updated DPs (which failed - see above); unchecked it; then updated the DPs again. PXEBoot.log showed that it was trying to remove the 12F files from RemoteInstall which was a good sign. I then restarted the WDS service
and tried PXE booting again. Yet again, it failed and was still looking for 12F.
Any suggestions / Ideas??? Thanks!
UPDATE 1
I just changed option #67 to \smsboot\x86\pxeboot.com then restarted the WDS service. I booted to PXE and this time was asked to hit F12. I did so and it looked as if it would work.
Instead, I got a blue screen with the following error:
Recovery
Your PC needs to be repaired
The boot configuration disk contains errors or is missing
file: boot\BCD
Error Code: 0x000000f
I think that it's the same error as before, but is blue instead of black due to new Win8ADK perhaps. Thanks
Ben K.

Update 4
Sorry to make this the longest post ever :)
I just read that others with this error checked DISM.log. I did so when running a DP update for the boot image and got the below errors:
2013-01-11 16:27:04, Info DISM DISM Provider Store: PID=1636 TID=5104 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
2013-01-11 16:27:07, Info CBS Failed to find a matching version for servicing stack: C:\Windows\TEMP\BootImages\{DADCFE01-3557-4058-99CC-2A15EDF905AF}\mount\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7600.16385_none_655452efe0fb810b\
[HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-01-11 16:27:07, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2013-01-11 16:27:07, Warning DISM DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\MsiProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-01-11 16:27:07, Warning DISM DISM Provider Store: PID=4104 Failed to Load the provider: C:\Windows\TEMP\0555ABC5-006D-4C3F-B79F-EA0E723FA971\TransmogProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
2013-01-11 16:27:07, Error DISM DISM Package Manager: PID=4104 The package WinPE-Scripting-Package is not applicable to the image. - CPackageManagerCLIHandler::Private_ProcessPackageChange
2013-01-11 16:27:08, Info DISM DISM Package Manager: PID=4104 Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error
2013-01-11 16:27:08, Info CBS Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Windows/TEMP/BootImages/{DADCFE01-3557-4058-99CC-2A15EDF905AF}/mount/Windows/System32/config/SOFTWARE,
the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
(The above one appears 8 times - almost in a row)
2013-01-11 16:27:08, Error DISM DISM Package Manager: PID=4104 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081e)
Help! Thanks :)
Ben K.

Upgrade to SCCM R2 have to recreate boot image and TS

Wanna ask, I have upgraded from my SCCM from SP1 CU3 to R2. But i noticed that in boot image, the WinPE tab is missing thus i cannot include the network driver. Anyway that i can make the tab reappear again? Net says have to recreate the boot image and TS...
http://www.deploymentresearch.com/Research/tabid/62/EntryId/117/A-Geeks-Guide-for-upgrading-to-ConfigMgr-2012-R2-and-MDT-2013.aspx

This often happens after R2 upgrade. If your boot image does not have 6.3.9600 version then you will not be able to manipulate it using the R2 console. You don't need MDT to create a new one though (this new version).
You can use dism. See here. It's very easy. I had to do it yesterday.
http://www.niallbrady.com/2013/10/09/how-can-i-manually-add-winpe-5-boot-images-to-system-center-2012-configuration-manager-sp1-cu3/
http://myitforum.com/myitforumwp/2013/08/01/how-to-create-configmgr-2012-boot-images-from-scratch/
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

Boot image changes being overwritten

I'll try to lay out the steps we've taken to recreate this problem.
We have two boot images (x64 and x86) in our Configuration Manager.
We recently deployed some new hardware and had to update the drivers that are part of these boot images.
After adding the drivers to the library, then updating the PXE image to include the driver, we do a "Distribute Content," wait about 15 minutes then use the "Update Distribution Points." Once everything syncs up among the DPs, we can
PXE boot to the image, it loads the correct driver, and we're off and running.
However, something happens overnight that causes this boot image to be overwritten, and the drivers are then backed out of the boot image altogether, leaving us at square one.
Is there some sort of default process that System Center has built in that causes it to revert back to an earlier version? What log files/settings should I be looking into?
TIA

The Data Source tab of the properties page for the boot image has a place for updating the DPs on a schedule...however
that shouldn't remove the drivers.
You are correct - ours are syncing every morning at 3AM.
Is content validation set on a schedule for the Distribution Point(s) in question?
Yes, we have 9 DPs and they do content validation on varying days.
Could it be that our changes are somehow considered to be "invalid" and the content validation check
is rolling back our changes? If so, how would we go about making our changes "valid" going forward?
We are working on tweaking the boot image and trying to streamline our imaging process as much as possible,
but we would rather work WITH System Center instead of fighting her the entire way....
I'll check that log file later tonight or tomorrow, but it looks like it doesn't have anything but the last 2 hours of data in it...

Do I need to use a boot image? 6509 / Sup2T Quad / VSS

I'm curious about boot loader images and if or why I should use one.
I've got a 6509 VSS setup running right now with no bootloader variable and no boot image.
SHEC-VSS#sh boot
BOOT variable =
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102
Standby BOOT variable =
Standby CONFIG_FILE variable =
Standby BOOTLDR variable =
Standby Configuration register is 0x2102
SWITCH-VSS#sh ver
Cisco IOS Software, s2t54 Software (s2t54-ADVIPSERVICESK9-M), Version 15.1(2)SY2, RELEASE SOFTWARE (fc3)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2014 by Cisco Systems, Inc.
Compiled Wed 26-Feb-14 16:03 by prod_rel_team
ROM: System Bootstrap, Version 12.2(50r)SYS3, RELEASE SOFTWARE (fc1)
SHEC-VSS uptime is 16 weeks, 3 days, 21 hours, 10 minutes
Uptime for this control processor is 16 weeks, 3 days, 21 hours, 10 minutes
System returned to ROM by power on
System restarted at 13:56:56 CDT Fri May 16 2014
System image file is "bootdisk:s2t54-advipservicesk9-mz.SPA.151-2.SY2.bin"
Last reload reason: power-on
I'm about to set up a nearly identical VSS pair for another facility.
I just downloaded the latest SY3 version of IOS for the new pair, and there is a boot image available:
s2t54-boot-mz.SPA.151-2.SY3.bin
I just don't know why I would want or need that. Can anyone explain? I'm not a newbie by any means, but I just don't know why I'd need it. Right now, in the bootdisk: volume, I just have my IOS image: s2t54-advipservicesk9-mz.SPA.151-2.SY2.bin That was all that was in there before, but now that I'm building this new pair, I copied s2t54-advipservicesk9-mz.SPA.151-2.SY3.bin onto the same volume.
I understand that if I set a boot variable I can tell it to boot from one image or the other, but what does the BOOTLDR variable do for me. If I were to set the BOOTLDR variable to bootdisk:/s2t54-boot-mz.SPA.151-2.SY3.bin then what does that do for me? Right now, if I reboot, (until I added that 2nd image) it will just boot the only image in that directory with no issue.
What am I missing? Do I need to upgrade or use this boot image for anything?
Thanks for any tips you can provide!
Tim

Tim,
In simple terms, the bootldr file is the helper file to load the IOS.
The BOOTLDR environment variable specifies the Flash file system and filename that contains the boot loader image required to load system software.
The variable defines the primary Cisco IOS image that will load the final image from another source.
we need to set the BOOTLDR environment variable to specify the Flash device and filename of the boot loader image.
For Old version of IOS, there is a requirement of boot loader image to boot up the IOS image.
But for the latest version of IOS, no need for boot loader image.
Below are few things happen when the device boots:-
1. The router initially boots into ROMMON (this is your bootstrap code, which you can see in the show version command).
2. Then the router loads into the bootloader code (this is the bootloadr code, which you see in show version). This bootloader code is just an intermediate step between the ROMMON mode and the IOS mode.
3. The router then boots into the IOS mode from the bootloadr mode.
So if you do not mention the bootloadr specifically by giving the "boot bootloadr" command, the router will assume the bootloadr to be in bootflash of the device and try to boot it from there. If you mention the "boot bootloadr flash:...." command, then the router will look for the bootloadr in the flash (instead of the bootflash). Thats the only difference.
However, in both cases, if you have a valid IOS to boot into, then the router will come up without a problem, irrespective of the fact whether bootloadr image is in bootflash or flash.
HTH
REgards
Inayath
*Plz dont forget to rate if this info is helpfull.

Unable to import Windows 7 boot images

When we installed our SCCM 2012 server, no boot images appear to have been created. I have since upgraded to R2, and added CU3, and there are still no boot images available. I would like to add boot images for Windows 7 x64 but so far have been
completely unsuccessful. I have tried creating images with MDT on the server, and they will not import. I have also created them with WAIK 3.0 with the WAIK 3.1 Supplement from a Windows 7 machine, and those will also not import. In every situation I
receive the following error: The specified UNS path does not contain a valid WIM file or you do not have permission to access it. Specify a valid path. This occurs if I try to import from a share on the sccm server, or from a share on
another computer. The permissions on the share are set at Everyone--full control share permission, and NTFS permissions are set to give the system account, the computer account and domain admins full control. The SMSProv.log file shows the
following error on each failed attempt: Failed to get the image property from the source WIM file due to error 80070002. I have read everything I can find and tried everything that people are mentioning that has fixed the problem for them, and so far
no success. I feel like I must be missing something, but I'm not sure where else to look. Any suggestions will be most appreciated!

Uninstalled and reinstalled ADK--no improvement.
Every time I try to import a boot image, the SMSProv log shows this:
~ $$<SMS Provider><01-21-2015 15:30:43.623+300><thread=7084 (0x1BAC)>
CExtUserContext::EnterThread : User=COP\reistg Sid=0x01050000000000051500000010DFF9978E4D14F2AFDA7FC15A0C0000 Caching IWbemContextPtr=000000385D804E50 in Process 0xd80 (3456)~ $$<SMS Provider><01-21-2015 15:30:43.623+300><thread=7084
(0x1BAC)>
Context: SMSAppName=Configuration Manager Administrator console~ $$<SMS Provider><01-21-2015 15:30:43.623+300><thread=7084 (0x1BAC)>
Context: MachineName=xxx.xxxx.xxx~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: UserName=COP\reistg~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: ObjectLockContext=1316ccc7-f4be-40c3-9b9e-c34dd1028080~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: ApplicationName=Microsoft.ConfigurationManagement.exe~ $$<SMS Provider><01-21-2015 15:30:43.624+300><thread=7084 (0x1BAC)>
Context: ApplicationVersion=5.0.7804.1400~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: LocaleID=MS\0x409~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: __ProviderArchitecture=32 ~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: __RequiredArchitecture=0 (Bool)~ $$<SMS Provider><01-21-2015 15:30:43.625+300><thread=7084 (0x1BAC)>
Context: __ClientPreferredLanguages=en-US,en~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
Context: __CorrelationId={2F91BBB1-35A9-0008-97BC-912FA935D001}~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
Context: __GroupOperationId=13101 ~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
CExtUserContext : Set ThreadLocaleID OK to: 1033~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
CSspClassManager::PreCallAction, dbname=CM_COP~ $$<SMS Provider><01-21-2015 15:30:43.626+300><thread=7084 (0x1BAC)>
PutInstanceAsync SMS_BootImagePackage~ $$<SMS Provider><01-21-2015 15:30:43.627+300><thread=7084 (0x1BAC)>
CExtProviderClassObject::DoPutInstanceInstance~ $$<SMS Provider><01-21-2015 15:30:43.627+300><thread=7084 (0x1BAC)>
GetStorage : doing Loggin due to aged out context~ $$<SMS Provider><01-21-2015 15:30:43.627+300><thread=7084 (0x1BAC)>
************ WBEM Missing property TransformAnalysisDate~ $$<SMS Provider><01-21-2015 15:30:43.645+300><thread=7084 (0x1BAC)>
************ WBEM Missing property TransformReadiness~ $$<SMS Provider><01-21-2015 15:30:43.645+300><thread=7084 (0x1BAC)>
~*~*~e:\qfe\nts\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3634) : Failed to read image property from the source WIM file due to error 80070002~*~*~ $$<SMS Provider><01-21-2015 15:30:43.669+300><thread=7084 (0x1BAC)>
~*~*~Failed to read image property from the source WIM file due to error 80070002 ~*~*~ $$<SMS Provider><01-21-2015 15:30:43.669+300><thread=7084 (0x1BAC)>
Auditing: User COP\reistg called an audited method of an instance of class SMS_BootImagePackage.~ $$<SMS Provider><01-21-2015 15:30:43.669+300><thread=7084 (0x1BAC)>
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=1568689744~ $$<SMS Provider><01-21-2015 15:30:43.678+300><thread=7084 (0x1BAC)>

Boot Image properties...tabs missing

Similar Messages

Maybe you are looking for