Configuration Manager

Published on January 18th, 2015 | by Christian Fosund

0

1E Nomad: *.bcd does not exist in ccmcache

Here is tip if you ever experience that you get this error in your CreateBCD.log:

error boot.HQ10000C.bcd does not exist in ccmcache, ensure the T/S deployment is configured to ‘Download all content locally before starting task sequence’

C:\Programdata\1E\PXELite\CreateBCD.log

image

 

The error message can be somewhat confusing, but what need to do is to update your boot image with the tool UpdateBootImage.exe located on the PXE Central site server under:

Here is an example on how to use it, make sure to run it under an elevated command prompt:

C:\Program Files (x86)\1E\PXE Lite\Bin\i386

UpdateBootImage.exe -ProviderName=CM01.fosund.com -SiteCode=HQ1 -DistributionPoints=CM01.fosund.com
-BootImageID=HQ10000C -ManagementPoints=SMSTSLocationMPs="http://CM01.fosund.com*http://CM01.fosund.com"
-WimFileName="\\CM01\Sources$\OSD\Boot Images\FOS Boot Image x64\boot.wim"

 

image

 

After running the UpdateBootImage.exe,  remember to update distribution points in the Configuration Manager Console

Its also worth mentioning that in the documentation it states that the winpe image needs be named boot.wim.
So if you have an wim image that its named winpe.wim or something else, you rename it.

 

For more information visit the official product documentation for PXE Everywhere (needs login)
http://help.1e.com/display/PXE23/Creating+a+PXE+boot+image+on+ConfigMgr+2012

Tags: , , , ,


About the Author

Christian is a senior consultant and MCT, specialized in the products System Center Configuration Manager and Microsoft Deployment Toolkit, and has been responsible for design and implementation of complex environments, spread geographically throughout the world. He’s also experienced in third party solutions like 1E Nomad that can make implementations more valuable and profitable in an efficient manner.



Leave a Reply

Back to Top ↑