SCCM 2012 R2 Boot Image issues after R2 upgrade

So I upgraded our upgraded System Center 2012 SP1 environment to R2. The main component that was affected was Confiuration Manager but you have to do it in a specific order so I had to do SCORCH, SCSM and SCOM first. I wanted to have it to R2 before we had it proliferated to all of our offices. It was pretty seamless and we actually saw improvements in package the reliability of package distribution to low bandwidth, high latency sites. This was what I was hoping, although it still is not perfect at these sites but it IS an improvement and given the environment's WAN limitation I can't complain.

Problem: error setting property (transformanalysisdate) 0x80041002

Anyhow after the upgrade I needed to add some drivers to a boot image we use for OSD deployment. That is where I found the issue. I could not customize the boot wim. the only tabs I had were the General, Content Locations, Security, Data Source, Data Access and Distribution Settings. I was missing Images, Drivers, Customizations and Optional Components. I also tried to redistribute it but that failed with a similar error as below.

I decided I would try to create a new boot image so I tried to create a new boot image using the "X:\Program Files\Microsoft Configuration Manager\OSD\boot\x64\boot.wim" file but it failed with the following error:

Error: Data Source Information

Source location: \\Server.Domain.com\SMS_XXX \OSD\boot\x64\boot.wim

Boot Image: 1 - Microsoft Windows PE (x64)

 

Error: Package Information

• Name: boot

 

Error: Errors

• The specified file can not be imported. Make sure the file is not read only and you have read and write access to it.

I verified all permissions and every thing was fine. So next I renamed the boot.wim to boot.wim.old and copied the winpe.wim from "X:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us" to my "X:\Program Files\Microsoft Configuration Manager\OSD\boot\x64" folder named it boot.wim and tried again. but no luck. I took a look in the SMSProv.log and saw the following:

CExtUserContext :: EnterThread : User=domain\username Sid= 0x0A65BE15D7A1D0300 Caching IWbemContextPtr= 0000000006ADFE40 in Process 0x8f4 (2292)    Context: SMSAppName=Configuration Manager Administrator console                SMS Provider   
Context: MachineName=Pri-SiteServer.Domain.com  SMS Provider    
Context: UserName=domain\username         SMS Provider     
Context: ObjectLockContext= cf3c2d48-8c9a-4b59-93e1-f83458812730    SMS Provider     
Context: ApplicationName= Microsoft. ConfigurationManagement.exe  SMS Provider     
Context: ApplicationVersion=5.0.7958.1000         SMS Provider     
Context: LocaleID=MS\0x409     SMS Provider     
Context: __ProviderArchitecture=32      SMS Provider     
Context: __RequiredArchitecture=0 (Bool)          SMS Provider     
Context: __ClientPreferredLanguages=en-US,en             SMS Provider     
Context: __CorrelationId= {01B09C58-F800-0003-7EE6-879D5CFACE01}   SMS Provider     
Context: __GroupOperationId=61690    SMS Provider     
CExtUserContext : Set ThreadLocaleID OK to: 1033           SMS Provider     
CSspClassManager::PreCallAction, dbname=SCCM_XXDB                SMS Provider     
User Context: domain\username       SMS Provider     
GetObjectAsync : SMS_BootImagePackage. PackageID= "XXX0000X"        SMS Provider    
Requested class =SMS_BootImagePackage         SMS Provider     
Requested num keys=1                SMS Provider     
Error setting property (TransformAnalysisDate) 0x80041002!       SMS Provider     
Error setting property (TransformReadiness) 0x80041002!            SMS Provider     
CExtUserContext :: LeaveThread : Releasing IWbemContextPtr= 112066112           SMS Provider     
SMS Provider     

Before I did my upgrade I pulled our environment into my test lab so I went back to that to do my testing and playing so I would not cause a bigger problem. I found in the lab Which I used to develop the upgrade plan, I had the exact same issue. I did some goggling but did not really find anything on this issue.

My thoughts were that I needed to uninstall and reinstall Window AIK and then bring the new boot image in.

After talking to some people from Microsoft I work with, who in turned talked to some other people I discovered that I was almost right.

Solution

Here is What I did to get it workin in both the lab and production:

1. Uninstall Windows AIK 8.1
2. Make exceptions in SCEP on the Primary Site Server for the locations that I have the wim files (both in the Windows AIK and the OSD directory).
3. install Windows AIK 8.1
4. recopy winpe.wim from "X:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us" to "X:\Program Files\Microsoft Configuration Manager\OSD\boot\x64". 
5. Rename winpe.wim to boot.wim. 
6. I also copied it to and replaced the boot.xxx0000x.wim file.
7. I still did not have the tabs, but I was able to redistribute which was a step in the right direction.
8. I created a new boot Image using:
    X:\Program Files\Microsoft Configuration Manager\OSD\boot\x64\boot.wim" 
   as the source file and added my drivers. That worked. 

While I was not able to re use my existing boot image, I was able to create a new working image that works just as good. problem solved.