We previously captured our image from a reference computer and imported the wim file to Config Mgr. Part 11 describes the process of creating the Operating System Deployment Task Sequence and deploying it to "Unknown Computers"
1. Create task sequence
Navigate to Software Library/Overview/Operating Systems
Right Click Task Sequences and select Create Task Sequence
Choose to install an existing image
Name the TS and choose boot image
Enter local administrator password
Enter domain and OU details
Choose Config Mgr client package
Now right click the TS and select Edit to configure some further options
Browse to Partition Disk 0 task
Double click to open each volume and make the required changes. Increase the default size of the boot partition and enter a variable name. We will use this to ensure that the correct image gets deployed to the correct volume
Remember we examined the properties of our captured image at the end of Part 2. Image 2-2 contains the operating system. We now apply 2-2 to OSPART
Apply 1-1 to BOOTPART
Recall Part 9 where we discussed drivers and driver packages. We now add driver packages for each computer model that we require.
(Add/Drivers/Apply Driver Package)
(Note that when I specifically use Driver Packages for the various models I then disable the "Auto" Apply Device Drivers step in the TS).
Create WMI query so that the TS can determine which model is being built. We only want the correct driver package to be installed
Select *
from Win32_ComputerSystem where Model like '%Optiplex 780%'
If you don't know the exact model name you can find it by using the following command at a command prompt:
wmic ComputerSystem Get Model
Test the query for syntax errors
Add/General/Run Command Line
Activate Windows
cscript.exe C:\Windows\System32\slmgr.vbs /ato
Add/General/Run Command Line
Activate Office
cscript.exe c:\"Program Files"\"Microsoft Office"\Office14\ospp.vbs /act
2. Deploy Task Sequence to Unknown Computers
"Unknown Computers" in a notional concept in Config Mgr which allows you to deploy task sequences to new computers (a new computer is one whose MAC address is not yet recorded in Config Mgr database).
If you wish to rebuild an existing computer you must first delete it from Config Mgr (make a "known computer" unknown).
Right click TS and choose Deploy
Choose All Unknown Computers
Make "Available" rather than required. Make sure you make available to PXE
Dear,
ReplyDeletegoing into the final step of deployment i get this error = 0x80070057
I have no idea how or why.. Followed every step of your tutorial.
Regards,
Ben
DeleteHi This looks like an issue I have been wrestling with for sometime.
SCCM 2012 sp1
MDT 2012 Integration
I am using UDI Wizard along wth customsettings.ini
Goal:
I want to have users get the UDI wizard and choose the settings like what OU they want the computer to go into during the task sequence.
I then want the computer name to be based on the OU that has been chosen eg:
If the user picks Eastern Regions in the UDI Wizard then during the taks sequence the name of the computer will be be based on the OU that the computer is put int for example - EASw7L-%serial%
I need help understand how to setup the variables using OSDDomainOUName if needed and what step to use this in the Join Domain vs Apply Network Settings.
We can do a remote connection so you can see whats going on if that will make things easier.
Thanks for any help with this!
Have you created Boundary Groups, added your site systems and ticked "Use this Boundary Group for site assignment"
ReplyDeletehttp://www.gerryhampsonsccm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part-6.html
Gerry! You made my life much easie with this post!
ReplyDeleteESPECIALLY the part about WMI query that uses single quotes, NOT double quotes, like SCCM 2007. I was getting so depressed trying to figure out why my old queries were not working!!
THANK YOU!
Hi Gerry,
ReplyDeleteAfter deploying WIN 7 OS to "Unknown computers" group, and i was trying install WIN 7 on a client, but i am getting stuck with the below error:
"Failed to Run Task Sequence
An error occurred while retrieving policy for this computer(0x80004005)"
Please help me to resolve the error
Note: I have installed SCCM Server (along with AD,DHCP,WDS) and client in VMWare EsXi Server
Hi Aji,
ReplyDeleteHave you enabled command (F8) support for your boot images? If not you should do so now. If so, you need to retrieve the SMSTS.log file.
You will find this log here - x:\windows\temp\smstslog\smsts.log
When the TS fails open the command prompt using F8 and map a drive to a file share somewhere. Copy the SMSTS.log file to that location so that you can read it.
You should see what your problem is in that log file.
Thanks for your support Gerry.
DeleteNo worries Aji
ReplyDeleteHi Gerry,
ReplyDeleteCan you please elaborate about this comment you made on this page? I am not able to find out where we saw the properties of the images as you mentioned!
"Remember we examined the properties of our captured image at the end of Part 2. Image 2-2 contains the operating system. We now apply 2-2 to OSPART"
Thanks.
Select the image you previously imported and right click, choose Properties. Select the Images tab.
ReplyDeleteSee the drop-down arrow showing 1-1. You are looking at the properties of 1-1. Now select 2-2 and examine the properties. Note the size of the image and the fact that this one contains the OS.
Thanks Gerry, I haved Faced Error (0x80004005) in OSD , which is solved by editing Task Sequence as suggested by you. OS part and Bootpart and also added Auto Apply Drivers under Apply device drivers
ReplyDelete0x80004005 = Unspecified error
ReplyDeleteThis is too generic to be of any use. You will have to review the the SMSTS.log file.
You will find this log here - x:\windows\temp\smstslog\smsts.log
Gerry
this is a really poor article, and NOT the right way to do OSD.
ReplyDeleteA statement like that is not very helpful if you don't elaborate.
ReplyDeleteHello,
ReplyDeleteThis is a great guide, really helped me out. My question is I only have 3 different PC models that I'm deploying. Do I need to create driver packages or is it enough just to import them and let the Apply Drivers step do the rest.
Thanks
Thanks
Thanks a lot. Appreciate the comment. I much prefer to create specific driver packages for each model and control them using a wmi query. I like to have control over the drivers.
ReplyDeleteGerry,
ReplyDeleteI'm looking at your instructions here and have a question with regards to drivers. If you still have the step "Apply Device Drivers" in the TS, which is of type "Auto Apply Drivers", what is the reason for adding the model specific packages? Unless the "Apply Device Drivers" step is limited to specific categories of drivers. or am I not understanding this step correctly?
Thanks,
Paul
PS: This is series is a great help tool to me for my SCCM implementation!
You're absolutely right Paul. When you use the "Apply Driver Package" step you can disable or delete the "Auto Apply Drivers" step. I have neglected to mention that above. You have to be a little careful though when you use this method. You need to ensure that you have a driver package for each model.
ReplyDeleteI'm being able to deploy the OS but always install in unit D:, what should I change so the OS installation remains in C unit?
ReplyDeleteSorry for the delay in responding. I've been on vacation.
ReplyDeleteThis is a known issue but does not happen if you have followed my steps for capturing and deploying the image. It normally happens if you have imported the install.wim file from the Windows 7 DVD.
To solve it you need to add a Task Sequence variable to your task sequence (the step before the Apply Operating System task).
Enter the Task Variable name OSDPreserveDriveLetter and set its value to FALSE.
Hi, i'm a french boy .
ReplyDeleteYour procedure is very interesting but i've got an issue at the step apply operating system just after dowloading the os.wim.
The error code is 0x800704D3 and I don't find anything on it.
Could you help me?
Thanks
0x800704D3 = The request was aborted.
DeleteI've seen it before where a WIM file downloads to about 75% and fails like this. It's a tricky one to troubleshoot and often involves you having to re-capture the image.
Is this happening on all hardware?
We keep getting the following:
ReplyDeleteWIM error:C:\_SMSTaskSequence\TSEnv.dat. Permissions on the requested may be configured incorrectly.
Access is denied. (Error: 80070005; Source: Windows) ApplyOperatingSystem 2/11/2014 9:10:41 PM 1392 (0x0570)
WIMApplyImage( hVolumeImage, const_cast(pathTargetVolume.c_str()), WIM_FLAG_VERIFY), HRESULT=80070005 (e:\qfe\nts\sms\framework\tscore\wimfile.cpp,657) ApplyOperatingSystem 2/11/2014 9:10:42 PM 1392 (0x0570)
Unable to apply (0x80070005) ApplyOperatingSystem 2/11/2014 9:10:42 PM 1392 (0x0570)
Installation of image 1 in package NYE00018 failed to complete.. Permissions on the requested may be configured incorrectly.
Access is denied. (Error: 80070005; Source: Windows) ApplyOperatingSystem 2/11/2014 9:10:42 PM 1392 (0x0570)
Any thoughts would be most appreciated..
-Gene
Have you configured a Network Access account Gene?
DeleteHi,
ReplyDeletefirst of all - that is really a nice guide.
During my OSD I got the following error at the end of the step "Apply Operating System":
Writing configuration information to D:\Windows\panther\unattend\unattend.xml ApplyOperatingSystem 17.02.2014 15:35:05 1364 (0x0554)
!shFile.null(), HRESULT=80070005 (e:\nts_sccm_release\sms\framework\osdcore\smiinterface.cpp,903) ApplyOperatingSystem 17.02.2014 15:35:05 1364 (0x0554)
Failed to open file "D:\Windows\panther\unattend\unattend.xml" (0x80070005)
ApplyOperatingSystem 17.02.2014 15:35:05 1364 (0x0554)
m_pSMIInterface->saveToFile( m_sAnswerFile ), HRESULT=80070005 (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,606) ApplyOperatingSystem 17.02.2014 15:35:05 1364 (0x0554)
sysprepFile->Save(), HRESULT=80070005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,880) ApplyOperatingSystem 17.02.2014 15:35:05 1364 (0x0554)
InitConfigFile(), HRESULT=80070005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,1852) ApplyOperatingSystem 17.02.2014 15:35:05 1364 (0x0554)
Configure(), HRESULT=80070005 (e:\nts_sccm_release\sms\client\osdeployment\applyos\installimage.cpp,2028) ApplyOperatingSystem 17.02.2014 15:35:05 1364 (0x0554)
Installation of image 2 in package SR10000D failed to complete.. Permissions on the requested may be configured incorrectly.
Access is denied. (Error: 80070005; Source: Windows) ApplyOperatingSystem 17.02.2014 15:35:05 1364 (0x0554)
I really do not understand why this error occur. I have configured a Network Access account but why do I get this "Access Denied" issue?
For any ideas I would be very thankful.
- Tobias
Are you using a customized unattend.xml file?
DeleteDoes the Panther folder exist?
How have you created your WIM and task sequence?
No, I did not create or edit the unattend.xml file.
DeleteYes, the Folder exists, I opened a command line in my task sequence and tried to access the unattend.xml file where I got as well the "Access Denied Error".
I installed a completly new Windows 7 Professional x64 and installed all Windows Updates. After that I captured the Installation with my capture.iso which I created as you described here in the guide. The task sequence is also created on that way.
Is there any option, where I can choose the account which should be used for the task sequence?
In the school district I am working with we are trying to get remote imaging working.
ReplyDeleteI have a task sequence all set and it works great. The question I have is, is there a way to just select one machine from the SCCM console and assign the TS to it? I cant find any way to do this.
I can assign the TS to a device collection and it will run fine, but we don't want users doing this. So we would like to be able to just select one device and assign the TS without making a new collection or anything every time. Is this possible?
Unfortunately not William. Task sequences are deployed to collections, not devices.
DeleteThat's what I was afraid of, I just couldn't find any way to do it. I have deployed it to a test collection and it works well but as soon as i run it I can not rerun it.
DeleteIs there a way to clear the "Installed" status of the task sequence so It can be rerun? Or am I missing a setting when deploying it that will allow me to rerun the task sequence? ( Not at a set time I know I can with a required deployment).
Hopefully this is doable.
I always do this by deploying task sequences to "Unknown Computers". If I need to rebuild a computer I just delete it from the ConfigMgr console first (so that it becomes Unknown). This strategy works well.
DeleteRemoving the computer from the config manager should longer allow a remote connection.
ReplyDeleteSo if I understand you correctly you assign a required TS to unknown computers via PXE?
I apologize just trying to make sure I understand, my head hurts ha ha been working on all of this for a long time now...
No, I make my task sequences available to Unknown computers. Then I choose the one I want.
DeleteI apologize I assumed without trying. As long as you are already remoted in, you will stay in the problem occurs when I refresh the machine to get the deployments it brings the machine back into the configuration manager. Once this happens the machine is no longer Unknown... obviously I am doing something wrong.
ReplyDeleteYes, we are talking about two different scenarios. For Unknown Computer support you turn off the computer and then remove the entry from ConfigMgr. The computer is then Unknown.
DeleteTurn the computer on and press F12 to continue (this assumes that someone is at the remote site to do this).
You cannot implement this strategy in the context of the OS.
That's what I figured, so basically I can not reinstall the same task sequence remotely if it already is listed as installed. Which it will be because its will be the same task sequence...
DeleteI found a way around it in case anyone else needs it.
ReplyDeleteIf you assign the TS to a collection, make it required but set the date far into the future. (I put it as far as it would go, 2033). Set the TS to rerun always. Lastly select allow TS to be run independently of assignment.
This will allow you to install the TS as many times as you need. Of course in 20 years if you have anything in the collection it will reimage, unless you change it of course.
From here you can decide how you want to use it. For us we are going to assign our Images to a premade empty collection and place the workstation in when we need to image it. This is because we do not want our Staff/Students to accidently/Purposely reimage the machine when it is not needed.
I have successfully reimaged a machine using the same TS 3 times so this will work.
My only gripe is overly simplistic at best. This whole process needs more than 50 megs of ram to run? Geez. Even seeing some errors with just 1 gig of ram. No errors when using 2 gig or more. It is cool that so many options can be made for custom setups but sad to see it can not be just a 2 step process. 1 offer image. 2 boot from sccm enabled thumb drive to get image.
ReplyDeleteAlso SCCM does not like it when the cmos battery is dead. I know I know a properly run pc should have a working cmos battery at any and all times but geez the little things get in the way. #ohwell
Gerry - when do you say "Double click to open each volume and make the required changes." - what are the required changes, and how would I know what is required here?
ReplyDeleteRead on for the changes.
DeleteTo follow up that last question, you continue to say "Increase the default size of the boot partition and enter a variable name. We will use this to ensure that the correct image gets deployed to the correct volume". Can you clarify the logic behind this? A bit unclear as to why this is done. Thank you!
ReplyDeleteYou have two partitions - one is 300MB and the other could be 80GB. You have two images - boot image and OS image. If you apply the OS image to the 300MB partition there will not be enough disk space and the task sequence will fail.
DeleteI use variables to define that the boot image is applied to the 300MB partition and the OS image is applied to the larger one. This works every time.
I would like to mirror Anonymous's questions above - what are the recommended changes to the boot partitions and why are they done?
ReplyDeleteAlso - this post seems to be oriented around upgrading/reinstalling a computer that has been discovered - what if it's a new computer that is not yet in AD and needs to be imaged, yet has no IP, AD name, or agent? Is it possible to create a bootable ISO that reaches out to the SCCM server to install from scratch?
Thnx - this series is truly a great help.
See above regarding partitions Jim.
DeleteThat's not correct. I have deployed this task sequence to Unknown computers. That means that I can take a new computer out of the box and network boot. This task sequence will be available.
Hi Gerry - is making "available" rather than "required" essentially making it not force the rebuild, and only executing it when PXE is triggered? Assume PXE needs to be enabled on the DP. But in my case PXE is already enabed on the subnet, so I don't want to enable it on my DP. How else would I trigger this reinstall?
ReplyDeleteWith regards to the account field for office/windows activation - what is this used for - if you leave it blank, what account is used by default? Does it need administrator rights on the local image?
ReplyDeleteAll task sequence steps run under the local system account.
DeleteWhen you create the WMI query above "Select * from Win32_ComputerSystem where Model like '%Optiplex 780%'" - does this naming string have any correlation to the driver "category" or is it purely extracted from the computer hardware itself?
ReplyDeleteI don't understand the question. This is just a standard WMI query - nothing to do with ConfigMgr.
DeleteGreat guide by the way!
ReplyDeleteI have just one difficulty on the task sequence. The "apply drivers" part seems to be only "copying" the drivers to the device but we have to manually click "Update Driver" on the device manager in order to install the drivers. Is there anyway to automate this? Maybe a command line/ps or something?
In my opinion the "Apply Device Drivers" step is not as reliable as using Driver Packages.
DeleteHi Gerry,
DeleteThanks for your quick response. I also did try to use Driver Package but is eems to be just copying the drivers and I need to manually update each and every missing drivers on the device manager. This is for dell latitude 6440.
I've never seen that. I would suggest that you download the drivers again and re-create the package.
DeleteHi Gerry,
ReplyDeleteYou mentioned that you point task sequences to the unknown computer collection. How do you handle OU designation and device naming? Do you have multiple task sequences pointed there with a specific OU or have you customized a TS that searches for variables which then moves the machines into the proper OU? Our company will be using SCCM 2012 for the first time this summer to image 500 new machines and are struggling with a strategy on how to handle naming of the machines and OU assignments for these OUt-of-the-box machines.
Please advise
I normally configure a collection variable to take care of the computer name. You will see this in Part 12 of the guide.
DeleteThere are a number of ways to handle the OU requirement.
1. Single task sequence - manually move to specific OU after deployment.
2. Multiple task sequences
3. UDI (User Driven Interface) provided by MDT integrated task sequence. The admin can select the OU and enter the computer name during deployment
For 500 devices I believe that all three methods are valid.
I am trying to deploy Windows 8.1 through SCCM 2012.Created a operating system and then created a Task sequence and distributed it and then deployed to collection.
ReplyDeleteWhen imaging it comes with an error task sequence failed.I had other task sequences in it like windows 7 ,none of them are working now.
Please help
You haven't given enough information to help. What errors?
DeleteHi, Gerry.
ReplyDeleteThanks for an amazing guide, its best one in the net.
Could you advise where to look if the computer didnt join a domain after deployment.
Thanks again
Thanks Eugene. Sorry for the late response. I've been on vacation. If a computer doesn't join the domain during the task sequence it usually means that it has no network connection. Type ipconfig/all after the build and see. This means that you have to add the NIC driver using a driver package.
DeleteHello Gerry,
ReplyDeleteI would like to thank for the wonderful guide on installing and managing the SCCM 2012 . I've got a small doubt on the Apply driver package step.
You have mentioned that we can manage drivers by using wmi query.
I have got some 4 to 5 models of machines and I would like to Apply driver package task sequence to verify from the list of supported drivers and install the correct drivers in 4 different models. Could you please help me on how could i proceed?
You're welcome. You would create a driver package for each model. Import all the drivers you need and add to the correct driver package. Configure your task sequence with WMI queries so that the correct driver package is added for each model.
DeleteHi Gerry,
ReplyDeleteCould you please help me , default Task sequence Error code and solution.
I'm not sure what you're asking for here Dhilip. Are you referring to the Error Lookup Utility in CMTrace?
DeleteHi Gerry
ReplyDeleteI made A change to one of our Task sequence (added a variable), but I though the next step would be right click and to distribute the content. However when you get to the option to pick the distribution point it is not there. Does it;
A) Automatically update the distribution points (that's why the options are not available)
B) I will have to create a whole new Task sequence distribute and deploy to my unknown collection
PS you stuff is great:)
You have only made a change to a task sequence Anish. There is no "distribute" option. Remember that you didn't have to distribute when you created the TS in the first place. You only distribute content like images, applications and packages.
DeleteHi Gerry many thanks on a great series. I have an issue with enabling the local admin account. In my TS i have it set to enable the local admin account and have set my password however after the OS is deployed the local admin account is disabled. Any help greatly appreciated.
ReplyDeletePerhaps something else is disabling the account - Group Policy maybe?
DeleteHi Gerry a bit more info in regards to my question yesterday about the local admin account being disabled. What i am trying to do with the ts is add the machine to a workgroup, dont install the config manager client, and enable the local admin account with a set password.
ReplyDeleteThanks
Hi Gerry. I want to know that what should be additional requirements/components if want to go with Zero touch way. I have to prepare the exactly same (Capturing and deploy) setup for my company but the requirement is without user intervention (NO F12) and bulk deployment. Your detailed comments would be appreciated. Thanks.
ReplyDeleteAmjad Khan
The only way to have true zero touch is to deploy a task sequence to an existing ConfigMgr client. I would consider pressing F12 to be acceptable and as close to zero touch as you will get. After all don't you have to touch a computer to take it out of a box?
DeleteGerry,
ReplyDeleteFirst, thanks for sharing this information. We are a Dell only shop with about six different models. If I'm setting up OSD with all six driver packages imported will ai be okay using the auto driver setup or do I need to run the WMI script to determine which model is installing?
It really depends what works for you Carlton. "Auto driver" install is perfectly valid as long as it works. I sometimes find that drivers are different but too similar for ConfigMgr to choose the correct one and you have to force the install with driver packages. However both are valid approaches as long as you test. I just prefer to remove the auto step and use driver packages.
Deletehi Gerry, Thanks for all your efforts.
ReplyDeletei get the below error while doing osd, could you please assist,
Error. Received 0x80072ee7 from WinHttpSendRequest. TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
unknown host (gethostbyname failed) TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
hr, HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8936) TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
sending with winhttp failed; 80072ee7 TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
m_pHttpTransport->Send (0, 0, pServerReply, nReplySize), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5568) TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
CCM::SMSMessaging::CLibSMSMPLocation::RequestMPLocation failed; 0x80072ee7 TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
MPLocation.RequestMPLocation (szTrustedRootKey, sIPSubnets.c_str(), sIPAddresses.c_str(), sSiteCode, sAssignedSiteCode, sMP, sMPCertificates, sX86UnknownMachineGUID, sX64UnknownMachineGUID), HRESULT=80072ee7 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9583) TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
CCM::SMSMessaging::GetMPLocation failed; 0x80072ee7 TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
Failed to query http://sql2012.sccmlab.com for MP location TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
New settings: TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
site=,, MP=, ports: http=80,https=443 TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
Set authenticator in transport TSMBootstrap 27-01-2015 14:06:12 1200 (0x04B0)
That's a tricky one. See previous case on TechNet forum
Deletehttps://social.technet.microsoft.com/Forums/en-US/93374f0c-3b35-4691-97c4-c683e1eae41c/sccm-2012-osd-stopping-with-gethostbyname-failed-errors-and-reboots?forum=configmanagerosd
Hello Gerry !
ReplyDeleteWe thank you, because of you. Our system SCCM works perfectly in particular Endpoint ! Thank you for these very good tutorials
You're welcome. Glad to help.
DeleteIt appears that when you format and partition the disk, you have to specify a static size or percentage in the task sequence. Do you know if it's theoretically possible to create a collection variable for the size that can be passed to this task instead? I'd like to have the ability to create custom-sized OS partitions and reserve the remainder for application partitions
ReplyDeleteI don't quite understand the question. By using the built-in task sequence steps you can already create as many partitions as you want (with fixed sizes) and the remainder can be another partition for your apps.
DeleteSorry Mike. I understand what you mean now. I don't believe that you can use collection variables for this but have a look at task sequence variables, in particular OSDParttions.
Deletehttps://technet.microsoft.com/en-us/library/dd252734.aspx
Hi
ReplyDeleteI am unable to get the task sequence loaded. It says ' No task sequence available to this computer. Please adverise atleast one task sequence.....error 80004005.
Please advise
Hi
ReplyDeleteI am unable to get the task sequence loaded. It fails when I hit F8 with the message 'There is no task sequence associated with this computer' ...... error 8000405. Please advise. Thanks
Hi Gerry,
ReplyDeleteI am imaging a brand new Lenovo P500 OOB from manufacturer with Win7. I added the machine to our domain and assigned the TS as available. TS starts reboots into WInPE and after initializing network connections, it reboots again in the loop. I added the network drivers to the boot image, am able to ping the server in WinPE. smsts.log says " Failed to find the source drive where WinPE was booted from...Failed to open PXE registry key. Not a PXE boot.
Any Help is appreciated
Many Thanks
Have a look at this similar problem Surya
Deletehttps://social.technet.microsoft.com/Forums/en-US/4dc92568-2b73-4420-8bad-f04d60f2ce46/failed-to-find-the-source-drive-where-winpe-was-booted-from?forum=configmanagerosd
Hi Gerry,
ReplyDeleteThanks for the prompt reply.. as always. I got through this error by adding the NIC and storage drivers to my boot image. I was succesfully able to deploy the OS. However, up on reboot- i get an error iaStorA.sys is missing or corrupt. I did ensure all the drivers are imported into SCCM and boot image is updated. I tried with and without SATA drivers. still the same issue.
Many Thanks,
Surya
Adding drivers to the boot image is only the first step Surya. You also seem to need storage drivers in a driver package and apply them during the task sequence.
DeleteHi Gerry,
ReplyDeleteThanks for the response. I was able to fix all the driver issues and successfully build the machine. Thanks for your inputs again.
That's good. Glad to help Surya.
DeleteHi Gerry,
ReplyDeleteThanks for these blog articles they have been very helpful, however I am running into an issue with my OSD TS. The TS gets most of the way though the deployment task, it gets the OS installed and says that is installing all the device drivers however it fails out with the following error code: 0x80072ee7. When the system reboots Windows is installed and named correctly by it hasn't been joined to the domain.
When I check the device manager I have found that the NIC's drivers are not being installed but I have deployed them in the TS using a Driver Package, as you show in your guides.
Any help you could give on getting this sorted would be greatly appreciated. I have put a link below to my SMSTS.log if you would like to have a look.
Thanks
https://dl.dropboxusercontent.com/u/3193655/smsts.log
Hi Liam. This is just a NIC driver issue. You need to try an alternative driver. (0x80072ee7 = The server name or address could not be resolved)
DeleteDear Gerry,
ReplyDeletemany thanks to all your explanations, guides and helpful statements.
Nearly everything works fine with your guidelines except the thing with the drive letter for the OS.
I configured the TS as you explained but I have a multicardreader and after the deployment one slot gets D and my real system partition gets E and the other slots get F, G, H.
Do you know what do I have to change so my system partition gets the drive letter C?
Thanks
Lukas
You need to use the OSDPreserveDriveLetter variable. See here
Deletehttp://blogs.technet.com/b/configurationmgr/archive/2014/04/28/how-to-ensure-that-windows-installs-on-c-during-a-system-center-2012-configuration-manager-osd-task-sequence.aspx
Hello Gerry,
Deletethank you for this link.
I tried method 3 because 1 was the one you already described and didn't work for me.
I deployed the TS and started a new deployment to a pc. Then I got an error message that the TS stopped because of error 0x80070057.
I copied the smsts.log to my bootstick an searched for 80070057 but there where only these few lines:
The system reboots automatically after 15 minutes and everything works and the OS-partition has driveletter C. Any idea?
May I ask you 2 other questions:
1. As a result of wmic ComputerSystem Get Model I get "HP Compaq dc7800p Convertible Minitower". Would it be enough for the Select statement to write like '%HP Compaq dc7800p%'?
2. In the TS-section, what is the difference between "Deploy" and "Distribute Content"? Do I have to do both?
Thanks for all your help.
Lukas
1. Yes, that syntax should be OK
Delete2. Distribute content means that you make all the required content available on a Distribution Point. You must do this if you haven't already distributed the content.
Deploy means advertising the TS to a collection of devices (available or required). Yes, you must do this.
I have a Dell 390 and I'm imaging it through SCCM. I get this error anytime I try to install on the 390. All other models image fine. The code is 0x80070057. Can you help me?
ReplyDelete0x80070057 = The parameter is incorrect. It's a bit vague and general but there could be some configuration in the task sequence that doesn't match in some way to the device you have. Is there some major hardware difference with the 390s?
DeleteHi Gerry,
ReplyDeleteFirst off, fantastic tutorials. I am a noob to sccm and this has made getting started so much easier, so thank you. I set up osd per your artical and it is working great for imagining my laptop. Now if I want to add a couple different machines (HP laptops and desktops), do I have to create a new boot image for each or can I still use the default x64 and just add the driver packages to my TS I'm currently using. Thanks again for any help your can provide.
Thanks Christian. Glad to help. No, you don't need additional boot images. You could need additional driver packages as you say. You also may need to import an additional network card driver into the ConfigMgr driver catalog and add this to your existing boot image.
DeleteGerry,
ReplyDeleteGot a question that I was hoping you could shed some insight on. Do you know if there is a way to potentially install storage drivers at the beginning of a task sequence? I have a need to deploy a Windows VM from a Linux host using KVM and it needs to have Red Hat's VirtIO storage drivers installed in order to see the hard drive. My task sequence fails every time at the beginning and the logs point me in the direction of there being no hard drive available.
Do you know if there is an elegant way to do this?
Thanks for any insight at all!
Do we need to add the Mac address to the All UNknown Computers collection to get the UNknown Computers boot through pxe Boot.
ReplyDeleteHere when we tried by pointing the Task Sequence to All UNknown System we are getting No Boot File Found
Currently we are deploying OS by creating seperate collection for respective Sites and adding the MAC address to their respective computer names.
No, you don't. Unknown computers are specifically computers whose MAC address does not exist in the ConfigMgr database.
DeleteGerry,
ReplyDeleteYour blog has really helped provide some great insight on driver injection and other things in sccm that have been not working well for me. I have this issue (time pressing unfortunately) where we are now going to implement the brand new Lenovo M900 tiny's into our environment. We have been a Lenovo house for a long time (X200, X220, T400, T420, T440, T450s - with no issues) but these are totally new with drivers, etc. I finally got the nic drivers injected in the boot image (thanks to your blogs) but i'm having the worst issue finishing because of the USB 3.0 as when windows boots keyboard and mouse wont work. If you could assist i'd appreciate it.
No worries. Glad to help. You need to identify the driver that fixes this problem and add it to a driver package. Add the driver package to your task sequence and use a WMI query like I've shown above.
DeleteGerry,
ReplyDeleteI'm getting the following message when I'm deploying to the new machine:
PXE-32: TFTP open timeout. Please help me, I have no idea how to solve this.
I'm really new to this and my basic knowledge isn't good enough to solve it.
Gerry,
ReplyDeleteI'm using a TS that installs windows 10 and enables bit locker. After everything is done, I'm getting an error when windows tries to boot that says winload.exe is either missing or contains errors. Any ideas here?
This comment has been removed by the author.
ReplyDeleteHi Garry
ReplyDeleteI try to do a deployment but i got an error on one particular machine which is the dell 5510. the error code are as bellow
OSDDiskPart.exe failed: 0x80070490.
I'm trying to to as your suggestion where I want to set the diskpart to the mentioned setting but then when it come to apply data image, I got a bit of confusion. its regarding the 1-1 and 2-2 image. how do you create that and what is that? Pardon me as i am quiet new to this SCCM
Rauf
Hi Gerry,
ReplyDeleteGreat guides and content, this is very helpful. Is your name pronounced with a 'J' or 'G' sound?
When I get to the Summary page on the Create Task Sequence Wizard, I get an 'object reference not set to an instance of an object' error. I have my image and boot images distributed, can't think of what is wrong.
Are you supposed to be using a fresh Windows OS image for this? I'm trying to use an image I captured from a customized VM. (not joined to a domain or anything)
Thank you!
I've seen this error before but it's normally when exporting MDT task sequences, not in a new TS. Have you done anything differently?
DeleteWell I followed your previous guide on capturing the image without any difference, except I used a VMware VM instead of a physical box. I use this same VM as a reference box with Dell ImageAssist without issue
DeleteThe only differences with the guide on this page is that I don't enable an administrator account, don't join to domain, and don't capture user info. Maybe somethings just wrong with our environment somewhere
Got past it Gerry! Turns out I don't get the error when I do it from SCCM on the server itself, but I do get it from the SCCM console on my windows 10 workstation. Strange!
DeleteHi Gerry, Do you know of any issues with SCCM 1606 deployments with windows 10? I'm having issues deploying to new Dell systems. The systems pxe boot fine, partition the drive download and install the os.wim file, install the drivers, reboot to finish install and i get a blue screen with the error:System thread exception not handled. It seems to not know what to do after the reboot to finish the install. I have deployed the same image just fine to a VM. I'm really stuck at this point. Any help would be greatly appreciated!
ReplyDeleteIf the TS works on a VM then this certainly sounds like a driver issue.
DeleteHi Gerry, Very helpful article.
ReplyDeleteI am building environment in VMware workstation where the TS goes fine until it can't join the computer to domain. I read above you mentioned it could be due to NIC card driver, which in VMs in VMware workstation, i think is automatically picked from VMware tools.
Please advise what i could be doing wrong, error i get is, 0x00000032.
NIC drivers are usually not required when you use VMs for testing. It's no harm to try though. Add the driver to a driver package and apply the package during the TS.
DeleteHi Gerry,
ReplyDeleteCan you confirm that if a machine in a domain has been built with SCCM previously, the only way to reimage that same machine is to delete if from sccm? I have been reading lots regarding this and can't get a definitive answer.
Not necessarily. That depends on your solution. If you have deployed your task sequence to Unknown Computers then the computer cannot exist in the ConfigMgr database if you want to re-image, so yes, in this case you have to delete it.
DeleteWe have SCCM 2012 R2, a new OS image out of Windows 10 1803, I need to image 20 PC to Windows 10, previous guy used a USB to boot, and I like to take advantage of PXE and get rid of the USB, shall I just create a new TS or modify the old TS?
ReplyDeleteYou can use the same TS. Just make sure that you've deployed it to PXE clients.
ReplyDelete