OSD – DHCP Configuration
-
On DC1, open DHCP server> Unser 192.168.255.0 Scope>Scope options>Configure options
-
Select 066 Boot Server Host Name and input Deployment NIC IP Address for sccm1.vmlab.local
-
Select 067 Bootfile Name and input string value to SMSBoot\x64\wdsnbp.com
-
After reconfigured the DHCP scope will be shown as below
- Repeat the above steps from 1 to 4 on Server options (the reason is why)
Reference (MS Best Practice): System Center Configuration Manager Troubleshooting the PXE service Point and WDS http://blogs.technet.com/b/configurationmgr/archive/2011/01/05/troubleshooting-the-pxe-service-point-and-wds-in-configuration-manager-2007.aspx
Set Computer Name
-
Go to Assets and Compliance>Overview>Device Collections>All Unknown Computers> Properties
-
Go to Collection Variables Tab> Add new value
-
OSDComputerName and uncheck the option
OSD test with an unknown computer
-
On VMs and Templates>VCP5>Sccm>New Virtual Machine
-
Typical
-
Name it
-
Select Cluster
-
Storage
-
Guest OS
-
Select 192.168.255- Port Group and VMXNET3 Adapter
-
15GB HDD and Thin Provision disk
- Finish to create a VM
-
After creating the VM, Edit Settings>Options>Advanced>Boot Options>check on Force BIOS Setup option
-
Power on the VM and open Console view>Go to BOOT Menu on BIOS>set Network Boot from VMware VMXNET3 on top order
-
Exit to Save
-
Press F12
- It has an error out PXE-M0F Exiting PXE Rom
so that I go back to DHCP Scope on DC1 -
Under Server options in this time, add 066 and 067 as described early.
- Restart DHCP Server service
-
And retry and it works now
-
Type Password
-
Select a task sequence to proceed
-
Select OSD Computer Name and Next
-
Failed to locate boot File
-
Update Distribution Point on WS2K12R2 Image which is the image ID of P010000B
-
Now I confirmed Distribution Point
- Restart Windows Deployment Services Server service on sccm1
- Go back to the VM Console, and click Cancel to try again
-
It works now
-
But, It fails due to the following error again
-
According to the research, I need to grab smsts.log
Reference site where to get the log
http://sccmguy.com/2011/03/29/where-is-the-smsts-log-located/
Reference site to troubleshooting with the log
http://blogs.technet.com/b/configurationmgr/archive/2009/12/17/how-to-properly-set-up-a-task-sequence-to-deploy-windows-7-images-captured-via-an-sccm-2007-capture-cd.aspx
-
Press F8 to open Command prompt to collect smsts.log
-
Go to X:\Windows\Temp\SMSTSLog\ directory and map z:\ drive to \\sccm1\logs directory to copy.
-
Open the log that shows it is due to not enough space I setup on my test VM.
Failed to run the action: Apply Operating System.
There is not enough space on the disk. (Error: 80070070; Source: Windows) TSManager 5/20/2014 4:04:41 PM 724 (0x02D4)
-
I added 5 GB Additional to make 20 GB HARD Drive Space.
-
Restart the server and try deployment task sequence again and it worked in this time without any further issues
-
It is joined to the domain and moved to the correct OU
Update created wim Image
*DISM (Deployment Image Servicing and Management): using DISM command to mount and unmounts a wim image
-
Create a folder on C:\DISMMount
-
Check where my current wim image is located. Go to Operating System Images>select an image (WS2K12R2.wim)>Properties>Data Source Tab
-
Make a copy
-
Open Command Prompt (Admin)
-
To mount a wim image, run command as dism /mount-wim /wimfile:C:\images\ws2k12r2.wim /index:2 /mountdir:C:\DISMMount
-
Go to C:\DISMMount\ and you can make any changes.
-
Create a New Folder and named it DISM Test
-
To unmounts, run command as dism /unmount-wim /mountdir:C:\DISMMount /commit
-
Now the C:\DISMMount\ folder should be empty now.
-
Go to Operating System Images>WS2K12R2>Properties>Images Tab> click Reload
-
OK to continue to update change
Verify the update
-
Go to Assets and Compliance>Overview>Devices> Delete Minint-SO28FGP
-
Go to SCCM_OS_TEST_Client VM console, and Reboot
-
Press F12 at PXE boot menu
-
Deploy Windows Server 2012 R2 Standard Image on the VM again
-
Log on to the server and check C:\DISM Test folder