Part 8 is the first post of the Operating System Deployment section. It describes an important configuration of the Config Mgr Boot images and the method of enabling PXE support on the Distribution Point.
1. Boot Image - command line support
Browse to the boot images and check their properties
Tick the box the enable command support. This will allow you to press the F8 key while in Windows PE to open a command prompt. This is essential while developing an Operating System Deployment solution
Now distribute the Boot Images (both x64 and x86)
2. PXE Support
Browse to the server roles and right click the Distribution Point
Choose Properties
Select PXE tab. Tick all the boxes to enable PXE support. It is important that you choose a complex password.
Windows Deployment Services is installed automatically as part of this process (if you have not already added the role as a prerequisite). See the RemoteInstall folders populating with system files as shown above. Note that if these folders remain empty you will not be able to PXE boot your computers.
Good Post Thank you ....
ReplyDeletethis is more useful for me
ReplyDeleteThank for your article, there is a little mistake, it's not F5 but F8
ReplyDeleteWell spotted. I've changed that now
ReplyDeleteI have an error when I try to create task sequence ("media") in test environment. I add the Boot image and the Distribution Point then I get:
ReplyDelete"The boot image is not currently available on the selected distribution point. Select a different distribution point or try again later."
What is missing?
Adding task sequence:
ReplyDelete"The boot image is not currently available on the selected distribution point. Select a different distribution point or try again later."
Why is it?
Sounds like you haven't distributed your boot images to your Distribution Point.
ReplyDeleteVerify in Monitoring > Distribution Status > Content Status
In Content Status:
ReplyDeleteSoftware Type Targeted Size (MB) Compliance
Boot Image (x64) Boot Image 1 0,0 0,0%
Boot Image (x86) Boot Image 1 0,0 0,0%
Configuration Manager Client Package Package 1 0,0 0,0%
Configuration Manager Client Up.Pack Package 1 0,0 0,0%
In "View Status" at "Error" tab it appears:
"Failed to access the source folder for content."
Which folder access right is false?
You've obviously got some kind of permissions issue. Look at the properties of any of the above - boot images or packages. Check the source location and check the permissions of these folders. Can you browse to them etc?
ReplyDeleteCheck the distmgr.log file for errors.
ReplyDeleteC:\Program Files\Microsoft Configuration Manager\OSD\boot\i386\boot.W1200003.wim
ReplyDeleteThis users has full control access rights for that file:
SYSTEM
SMS_SiteSystemToSiteServerConnection_SMSProv_W12
Administrator
Which users need have access rights yet?
In Asset message is:
ReplyDelete"possible cause: Distribution Manager does not have sufficient rights to the source directory...
possible cause: theres is not enough disk space..."
There is 14GB free disk space in virtual machine drive. Is it enough?
In distmgr.log:
ReplyDelete# -------------------------------------------------------------------------------------------
Failed to find a valid drive on the distribution point ["Display=\\W2012SYSCENTER.w12.local\"]MSWNET:["SMS_SITE=W12"]\\W2012SYSCENTER.w12.local\ $$<11-29-2013 10:10:52.454-60>
# -------------------------------------------------------------------------------------------
What does it mean? What is missing?
You've taken this error out of context so it's not very helpful. There must be more in the distmgr.log file.
ReplyDeleteHi Gerry
ReplyDeleteMy Windows Deployment service is not starting. I tried uninstalling and reinstalling the WDS. Installed the WDS separately. Went inside the WDS console and gave the GC details. Gave the WDS service domain admin permission but still no luck. Could you please help me out.
Regards
Suraj
WDS is leveraged by SCCM to provide Operating System Deployment. You should not configure WDS in any way. SCCM will do that for you.
DeleteI suggest you uninstall WDS again (also disable PXE on the DP). You will have to reboot.
Now reinstall WDS and if the service does not start you should examine the event logs to figure out why.
Thankyou Gerry for the info
ReplyDeleteAs you had told i uninstalled the Disabled the PXE from DP the automatically the WDS role is also removed. After that i deleted the remote install folder and restarted the machine and installed the WDS again and looked whether the service has started but the same issue. The WDS service is not starting.
OK Suraj. As you know, when you uninstall WDS you have to do some clean up. You have already deleted the RemoteInstall folder. However you also have to look in C:\Windows\Temp folder. Are there any Boot or PXE related folders there? You have to delete them also.
DeleteIncidentally you haven't explained how you got to this point. Is this an upgrade or new build and what version of ConfigMgr are you using?
Suraj, does the RemoteInstall folder get created when you reinstall WDS.
DeleteIf not try running this command:
wdsutil /initialize-server /REMINST:e:\remoteinstall
(note that you may not be using e: drive - choose your own drive letter)
By the way. this method is NOT supported by Microsoft.
DeleteHi Gerry - for some reason I only have an x64 image in my images. Not sure how this happened, how can I get both x86 and x64 added above, so I can enable PXE on both?
ReplyDeleteThanks. Great great series by the way! Thank you so much.
You're welcome. See here for re-creating boot images
ReplyDeletehttp://www.gerryhampsoncm.blogspot.ie/2014/02/configmgr-2012-create-new-boot-images.html
Gerry - what if you already have PXE options 66/67 enable on your network?
ReplyDeleteThe folders you mention in the last step I can't seem to even find. I'm running R2 and perhaps that's the issue, but WDS is installed. Is the path different in R2?
ReplyDeleteWhen WDS is installed it creates a folder called RemoteInstall. This is the default WDS Share (shared as REMINST)
DeleteHi Gerry,
ReplyDeleteI have installed a SCCM 2012 R2, following all your previous blogs.
Configured PXE enable on DP and boot imaged and distributed on DP.
Now I'm trying to configure OSD. I added a Win8.1 boot and OS image in sccm console. then I distributed them to DP. But it is a day now still it is showing In progress in Distribution status in monitoring pane. Is there any more configuration to be done which is why the OS images and boot images are taking so long to show 100% compliance.
Also wanted to know, I've installed Hotfix for SCCM 2012R2. If i Enable PXE on DP, would it create any problem in WDS services now??
Thanks in advance.
Jose
You should review the distmgr.log file for errors. That is not normal.
DeleteI don't understand the last part. You say you've already enabled PXE.
Really good post Gerry...helped me a lot
ReplyDeleteThanks for all the help Gerry!
ReplyDeleteI'm stuck on distributing the images. I have no distribution points to choose from, but I do show a DP in the administration tab. I must be missing something.
Thanks
If there are no DPs to choose from that would mean that the image has already been distributed. Check Distribution Status under Monitoring node.
DeleteBoth images are there. I'm pretty new at this and must have completed more than I realized. Your tutorials have been a huge help toward making this work. Thanks again!
DeleteNo bother Scott. Glad to help.
DeleteHello Gerry,
ReplyDeleteYour guide helped me a lot.
Although, I have a small query: Is it possible to remove the PXE password in DP properties once enabled?
Is there a particular process I would need to follow to perform this change other than just removing it.
Will the remote install folder be created once again after this change?
I have currently deployed SCCM in a test environment and will be moving it soon to a live setup.
Hence want to be a little cautious.
Thanking you in advance.
You can remove this password with no effect on the folders. I wouldn't advise doing this though. PXE should be protected to avoid computers being rebuilt in error or by unauthorised users.
DeleteHello Gerry,
DeleteThank you for the confirmation.
I have come across another issue wherein the local administrator password is not being used from the unattend.xml(answer file) and also if i mention it on the apply windows settings during OSD.
I would like to automate the process of using the local administrator password towards the end of OSD.
Could you guide me on how could I achieve this. Your views are much appreciated.
Thank you.
I don't understand why this task sequence step would give you difficulty, I've never had an issue with it. What actually happens? Is the local administrator account remaining disabled (which is the default)?
DeleteI have captured an image from a computer this time leaving the administrator password blank. However, while deploying the task sequence, after SCCM applies the image, I still get a prompt that the password or username is incorrect despite the fact that the administrator password is blank. When I hit enter on the password prompt, I am able to successfully login and task sequence processes successfully. I am not sure what password is Windows using here when the Administrator password is blank.
DeleteConfigMgr won't capture the local administrator password. Actually, by default, Sysprep disables the local administrator account. You set this password when you configure the task sequence
DeleteThe image has been captured in audit mode without any local administrator password set. In the answer file, at the audit user pass, I am sysprepping the machine into oobe mode. This all works well, the only issue lies before entering the Audit user pass, I need to hit enter on the Administrator password prompt but as the password is blank, Windows should be able to login automatically but instead it displays that the username or password is incorrect. If I hit enter at that prompt, it works well and proceeds with the task sequence. Is it possible to automate this step?
DeleteThank you for your help.
Hello Gerry,
DeleteGot this issue resolved by removing the Specialize and Audit system pass in the answer file, Windows did not seem to take that too well. Thank you for your input.
Good. I'm glad you got it resolved.
DeleteHello Gerry
ReplyDeleteI have an image that works just fine but when I pushed to encrypted laptop (Symantec Endpoint) it get kicked of after WinPE process.
Do you know anything about it and guide
In my experience this can be very difficult to automate. As the drive is encrypted ConfigMgr cannot partition it and the task sequence fails. Some vendors claim to provide support for this but it's difficult to implement. The only certain way to be successful is to decrypt the drive first.
DeleteHi Gerry,
ReplyDeleteI noticed that you wrote about installing WDS but do not configure when installing IIS. This caused a lot of issue with SCCM as WDS wont start and was not able to deploy OS.I had to find out somewhere online that when you enable PXE,WDS is installed automatically. Can you remove the WDS from the list when installing IIS as it was very confusing since SCCM automatically installs it. That creates more problems. I am not sure if with SP1 you need to install WDS manually but it works for me without installing WDS in the R2 version.
Hi Gerry,
ReplyDeleteI have uploaded Win 7 Boot image,but i can't see Customization Tab in properties to enable command line support.
Regards,
Chithiravel.S
Have you upgraded ConfigMgr? If so you can't modify down-level boot images. You have to either
Delete1. maintain the boot images on another system (perhaps a standalone MDT) OR
2. Create new boot images (see the link below for how to do this)
http://www.gerryhampsoncm.blogspot.ie/2014/02/configmgr-2012-create-new-boot-images.html
Hi I'm having problems with my deployments, running a deployment to an desktop is just fine. Whan I deploy a laptop everything runs fine but after deploying an restarting the portable wont start and gives error 0xc000000f. winload.exe is missing. What can be the problem? the tasksequence is the same
ReplyDeleteGerry, We added a new distribution point at a local office. Updated dhcp, setup server in boundary groups etc, normal tasks. When we attempt to pxe boot, we get the "0xc0000001 A required device isn't connected or can't be accessed." I've adjusted the dp's RamDiskTFTPBlockSize to different number with no luck. We updated the boot wim, drivers, and distributed the content to the dp, with no luck. We can Image a vmware machine at our datacenter but not in the local office. Any areas we should check? Thank you in advance.
ReplyDeleteDoes the network boot try to connect to the local WDS server? You will be able to see the IP address.
Delete