Boot image, Install pending after driver injection
Hi, We have an SCCM 2007R2 environment with 3 secondary sites. Today i've updated the boot image with a new driver, and some how the boot.wim was corrupt. To resolve the problem at the primary site i've removed the boot.<packageID>.WIM from \\Server\SMSPXEIMAGES$, \\server\SMSPKGE$, \\server\SMS_SITE\OSD\boot\x64 And updated the DP's again. Right now the primary site has Source Version 29 installed All the secondary sites have on Source version 24 Install Pending. (yes, tried it a couple of times) I tried to resolve it on the secondary sites by removing the file from same locations as the primary site, but that didn't help. When I remove the secondary site server from the list of DP's and after a while add it again, it is again telling me Install Pending for source version 24. What is the best way the get the boot.wim distributed to the secondary sites again? Kind regards, Dennis
June 10th, 2011 11:39am

instead of updating the boot image to the dp's have you tried refreshing it ? My step by step SCCM Guides I'm on Twitter > ncbrady
Free Windows Admin Tool Kit Click here and download it now
June 10th, 2011 5:47pm

Hi Niall, What exactly do you mean with refreshing it? When I select Update Distribution Pionts, it will update the boot.wim with the drivers i have selected. I see no other refresh option then refreshing the screen. One of the secondary site is now reporting to have Source Version 29 installed (which is the latest), I managed to do so by editing the DP's for the boot image and deselecting that site. Waited a couple of minutes to get the change replicated, then deleted everything i could find of the package ID on that site server. Then added the site to the list of distributed sites. It reported that source version 24 is Install Pending. Now (next morning) it tells me the latest is installed on this site server. If you could clarify refreshing the boot image i will try that on Tuesday, otherwise i will try the steps above on the other secondary sites. Kind regards, Dennis
June 11th, 2011 3:33am

Hi, You can right click on the distribution point node of a Package you will get an option to Update Distribution points. If you open the node and right click on an individual DP you will get an option to refresh the package on that distribution point. When you update the DP, Configuration Manager builds a new, complete compressed package file and a delta compressed package file. The delta file is then copied to the distribution points. The version of the package is incremented every time the package is updated. When you refresh package data, the package is copied from the compressed version on the site server but not updated from the original source. Refreshing the package does not increment the package version. Take this Technet document as a reference: http://technet.microsoft.com/en-us/library/bb892806.aspx Thanks
Free Windows Admin Tool Kit Click here and download it now
June 13th, 2011 5:52am

Go to secondary site , seach for packageID and rename all files related to package ico nal and pkg . Go to package and select update all DP with newer version.
June 13th, 2011 2:02pm

Refreshed the remaining DP's about 30 minutes ago. No success yet. The last thing i did on Friday was removing all files with the packageID from one of the secondary DP's after that i've updated the DP and now it seems like that resolved it. by coincidence these are the same steps as RIX78 described. First thing in the morning I will check if refreshing resolved it, otherwise i will delete the files from the remaining DP's Dennis
Free Windows Admin Tool Kit Click here and download it now
June 13th, 2011 2:36pm

Refreshed the remaining DP's about 30 minutes ago. No success yet. The last thing i did on Friday was removing all files with the packageID from one of the secondary DP's after that i've updated the DP and now it seems like that resolved it. by coincidence these are the same steps as RIX78 described. First thing in the morning I will check if refreshing resolved it, otherwise i will delete the files from the remaining DP's Dennis
June 13th, 2011 2:36pm

I removed all files that include the PackageId and refreshed the DP, but it is still reporting Source version 24 Install Pending. On the DP itself the following files are created: inboxes\pkginfo.box\PackageId.NAL inboxes\distmgr.box\PackageId.PKG inboxes\pkginfo.box\PackageId.PKG inboxes\distmgr.box\PackageId.PKN And one folder: inboxes\pkginfo.box\PackageId ICO Every time i refresh the contents of the folders the last modified date is updated to the current time. Any ideas?
Free Windows Admin Tool Kit Click here and download it now
June 15th, 2011 8:40am

Do not do refresh. Try , Update all DP with new version of source files and make sure in package property , Always obtain files from source directory option is set.
June 15th, 2011 12:45pm

Problem is resolved now. Tried to refresh a couple of times yesterday without any success. The files looked like this on the secondary: inboxes\pkginfo.box\PackageId.NAL inboxes\distmgr.box\PackageId.PKG inboxes\pkginfo.box\PackageId.PKG inboxes\distmgr.box\PackageId.PKN And one folder: inboxes\pkginfo.box\PackageId ICO Then updated the DP's and new source verson is succesfully send to all DP's In the end I think it was resolved by the following steps: 1.) Remove all files that contain the PackageId int the filename 2.) Update DP (so no refresh)
Free Windows Admin Tool Kit Click here and download it now
June 17th, 2011 2:12am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics