SCCM Errors

Leo
Leo used Ask the Experts™
on
I have few SCCM erros, trying to tackle them one by one,the first error i am getting is Creating a Task Sequence Media through USB, when it goes to fourth step in which have to select a Task Sequence, its blank, i have attached picture for reference.
SCCMError.jpg
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Mike TLeading Engineer

Commented:
Hi,


Where is the your task-sequence? Is it in "Build"?

Mike
LeoSnr Network Eng

Author

Commented:
yes
Mike TLeading Engineer

Commented:
So when you browse what is shown in build? Your screenshot shows the root only.
The only reason is either you're not looking in the right folder or you have disable the task-sequence. Or you have not created a deployment for the TS at all!

Mike
Fundamentals of JavaScript

Learn the fundamentals of the popular programming language JavaScript so that you can explore the realm of web development.

LeoSnr Network Eng

Author

Commented:
I have attached screenshot for the Build, should i deploy or distribute the sequence to Distribtion points?
LeoSnr Network Eng

Author

Commented:
Mike TLeading Engineer

Commented:
Hi,

OK, do both. Distribute first, wait for the DP to get to 100% and then deploy it to a collection.

Mike
LeoSnr Network Eng

Author

Commented:
If I choose to distribute to collection, i am getting the option to deploy to all Users and Groups, i have attached the screenshot.
LeoSnr Network Eng

Author

Commented:
Mike TLeading Engineer

Commented:
You need to choose devices in the wizard in the top left corner drop-down box.
LeoSnr Network Eng

Author

Commented:
Under Devices, there are different folders for each Site, but all of them are empty.
Mike TLeading Engineer

Commented:
You need to create your device collection first. Given this sounds experimental I strongly advise you to read up on all this too. There are plenty of good books but the best is by Kent Agerlund.

You need to create a new device collection and set the limiting collection to All Desktops and Servers. Never, ever, *ever* use anything bigger in scope to limit your collections. That way lies disaster because it will make your collection utterly unlimited. Stick to all desktops and servers.
Then add ONE machine as a direct member. You will need to update the collection and click refresh too. It's quirky I know but wait until it says 1 member. Then you are ready to deploy your TS to it.

Mike
LeoSnr Network Eng

Author

Commented:
Thanks, is there any link on what you said, which i can follow step by step....
Mike TLeading Engineer
Commented:
Hi,
There's no single link because it's a few steps of different things:

Collections:
https://blog.thesysadmins.co.uk/sccm-2012-creating-device-collections.html

Deploy TS - not a step-by-step but scroll to the end for the overview
https://technet.microsoft.com/en-us/library/hh967540.aspx


Mike
LeoSnr Network Eng

Author

Commented:
Apologies for late reply, i was away....
i have created the new collection, it shows all the workstations of our site. So should i distribute content to this new collection?
Mike TLeading Engineer

Commented:
Yes please.
LeoSnr Network Eng

Author

Commented:
thanks, i redistributed, and these are the errors iam getting now :-(

  Error: Boot image to update:
•      Microsoft Windows PE (x86)
 
  Error: Actions to perform:
•      Add ConfigMgr binaries
•      Set scratch space
•      Disable Windows PE command line support
•      Add drivers
 
  Success: Drivers that will be included:
•      Intel(R) Wireless Bluetooth(R) 4.0 + HS Adapter
•      Bluetooth Server
•      Intel(R) HD Graphics
•      HP HD Webcam
•      UoIP Hub
•      Standard 101/102-Key or Microsoft Natural PS/2 Keyboard with HP QLB
•      IDT High Definition Audio CODEC
•      Intel WiDi Audio Device
•      Intel(R) Display Audio
•      Synaptics PS/2 Port TouchPad
•      Realtek PCIE CardReader
•      Intel(R) Dual Band Wireless-AC 3160
•      Intel(R) Active Management Technology - SOL
•      Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
•      HP Mobile Data Protection Sensor
•      Intel(R) 8 Series Thermal - 9C24
•      Intel(R) 8 Series Thermal - 9C24
•      Intel(R) 8 Series Thermal - 9C24
•      Intel(R) 8 Series Thermal - 9C24
•      Intel(R) Smart Connect Technology Device
•      IWD Bus Enumerator
•      PCI bus
•      Synaptics SMBus Driver
•      Intel(R) 8 Series USB Enhanced Host Controller #1 - 9C26
•      Intel(R) USB 3.0 eXtensible Host Controller
•      Intel(R) USB 3.0 Root Hub
•      Intel(R) USB 3.0 Root Hub
•      Intel(R) USB 3.0 Root Hub
•      Intel(R) Ethernet Connection I217-LM
•      Intel(R) Ethernet Connection I217-LM
•      Intel(R) Ethernet Connection I217-LM
•      Intel(R) Ethernet Connection I217-LM
 
 Optional components:
•      Scripting (WinPE-Scripting)
•      Startup (WinPE-SecureStartup)
•      Setup (WinPE-Setup)
•      Network (WinPE-WDS-Tools)
•      Scripting (WinPE-WMI)
 
  Error: Failed to import the following drivers:
•      Validity Sensor (VFS495) - Failed to inject a ConfigMgr driver into the mounted WIM file
 
  Error: The wizard detected the following problems when updating the boot image.
•      Failed to inject a ConfigMgr driver into the mounted WIM file
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=\"TT100081\"";
•      ProviderName = "WinMgmt";
•      StatusCode = 2147749889;
Leading Engineer
Commented:
OK, those all look like boot.wim errors. If so, you've made a fundamental mistake. You only need all the drivers if your main OS. The boot wim rarely needs extra drivers. If it does only ever look at storage (disk) and network drivers.
Out of the list I can only see one you need: Intel(R) Ethernet Connection I217-LM

Please remove ALL the others from your boot wim. Also set the scratch space back to 32. It is self adjusting these days.

The validity sensor of for the fingerprint sensor. You can import that for the main OS stage where it will work fine. You don't need the "app" it comes with.

The other gotcha is architecture. Make sure you only use a 32-bit boot WIM and 32-bit drivers for that *even if deploying a 64-bit OS. Delete the 64-bit drivers from the boot staging area. Hint make two folders for your drivers: Boot driver & OS drivers, and organise them. Clearly the boot DIR only needs a few drivers in it  but your OS will need lots. Organise by Vendor\Model\x32\Category. When your company buys another model, you won't be caught out and get in a mess.

Sort the boot WIM, and then try the distribution again and let us know.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial