We have understand before OSD Troubleshooting which step and area we have to focus now let consider each of the flow has any error to figure out and what could be work around.
Issue:
When performing a deployment via System Center Configuration Manager OSD on a client PC, the client PC may boot into WinPE but within a few seconds it automatically reboots and does not perform the Task Sequence advertised to the PC, or it does not give the option to select a Task Sequence advertised for that PC. Examining the SMSTS.log obtained from X:\Windows\Temp when the Command Support option is enabled, we see the following error message:
If booting from PXE:
Failed to download pxe variable file. Code(0x00000001) TSPxe PxeGetPxeData failed with 0x80004005 TSPxe
If booting from boot media (CD/DVD/USB Flash Drive):
Error. Received 0x80072ee7 from WinHttpSendRequest. TSMBootstrap
unknown host (gethostbyname failed) TSMBootstrap
hr, HRESULT=80072ee7 (e:\nts_sms_fre\sms\framework\osdmessaging\libsmsmessaging.cpp,7714) TSMBootstrap
sending with winhttp failed; 80072ee7 TSMBootstrap
Will retry in 6 second(s) TSMBootstrap
or
Failed to find a valid network adapter. Please ensure that this machine has a network adapter and appropiate network drivers.
Unspecified error (Error: 80004005; Source: Windows) TSMBootstrap
Failed to find a valid network adapter.
For more information, please contact your system administrator or helpdesk operator. TSMBootstrap
Cause:
These errors may be caused by no network connectivity on the client PC, usually caused by no network drivers for the PC being loaded into the WinPE Boot Image.
Resolution:
To resolve this issue make sure that the following actions are taken:
-
Load Windows 32-bit drivers into the x86 Boot Image
-
Load Windows 64-bit drivers into the x64 Boot Image
-
Make sure network cable is plugged into the Client PC
To Check Network Connectivity:
-
Make sure that "Enable command support" is enabled in the Boot Image
-
Attempt the deployment
-
When the WinPE desktop appears and you see the Microsoft System Center Configuration Manager wallpaper, hit F8 to open the command prompt window
-
In the command prompt window, type IPCONFIG
Results of IPCONFIG:
-
If you only see the title "Windows IP Configuration", then there probably are no NIC drivers loaded in WinPE. Load the proper NIC drivers into the WinPE Boot Images (see additional notes and tips below).
-
If you see additional information, including IP information, but it may say "Media Disconnected" and the IP is either 0.0.0.0 or 169.x.x.x, then the NIC drivers are probably loaded correctly in WinPE, but there is no network connectivity to the network port on the client PC. Check cables and connections and make sure there is network connectivity to the port.
Additional Information:
Notes & Tips When Loading Drivers Into The WinPE Boot Images:
-
Make sure that ONLY 32-bit drivers are loaded into the x86 Boot Image and that ONLY 64-bit drivers are loaded into the x64 Boot Image.
-
Only load NIC and Mass Storage Drivers into a Boot Image. No other drivers (audio, chipset, video, etc.) should be necessary and may only cause problems.
-
If not needed, do not load any NIC drivers labeled as "Virtual" as they tend to cause problems. Usually they are not necessary as long as the normal NIC driver is loaded.
Issue:
PXE-E51: No DHCP or proxy DHCP offers were received.
Cause:
These errors may be caused because of Following Reasons:
-
Your DHCP server isn't working
-
If you use DHCP reservations you may have made a mistake entering the MAC address of this machine.
-
You don't have a DHCP pool set up for this subnet, or the pool has no free addresses.
-
Your DHCP server is on a different subnet and you haven't set up an IP forwarder or DHCP Relay agent.
-
The network cable or port is broken.
Resolution:
To resolve this issue make sure that the following Steps are taken:
-
Check DHCP Server configuration.
-
Check MAC address of the system.
-
Call Technician if Network port or cable is not working.
-
Check if there's no DHCP reservation/ or DHCP pool is exhausted.
Issue:
PXE-E55: Proxy DHCP service did not reply to request on port 4011
Cause:
This error may be caused suggests either firewall or routing issue.
Resolution:
To resolve this issue make sure that the following actions are taken:
-
Check the firewall settings allow 4011 UDP through.
-
If the client and the PXE Service Point are on different subnets, check that the traffic is being forwarded from the client subnet to the PXE Service Point.
Issue:
The machine fails to connect to the TFTP server or fails to get the boot file from the share service
PXE-E32 TFTP Open Timeout error
Cause:
This error is received when the WDS and SCCM PXE service Point are not in sync or WDS has been configured manually.
Resolution:
The PXE service point needs to be reinstalled
Step:
-
Remove all the packages from PXE distribution point.
-
Delete the PXE role.
-
Reinstall the PXE service point again.
Issue:
PXE-E3B: TFTP error file not found.
Check the SMSBoot folder in the reminst share on the PXE Service Point. There should be 3 folders in the SMSBoot folder - ia64, x64 and x86. Each folder should contain some boot files. This Error comes up if any of the file is missing.
Cause:
This error can be caused by a number of things- updating drivers in the default OSD Boot Images, restarting the server hosting the PXE Service Point or just a botched PXE Service Point install.
Resolution:
To resolve this issue make sure that the following actions are taken:
-
Stop the WDS Service
-
Delete (or move) the folder %temp%\PXEBootFiles
-
Start the WDS Service
-
If this doesn't work it might be a more fundamental problem with the PXE Service Point. Remove the role from the server, restart the server hosting the PXE Service Point and Add the role back.
Issue:
Error:-The machine has not been registered in a build.
Cause:
The machine does not have a Task Sequence advertised to it.
Check smspxe.log, you should see an error such as
ProcessDatabaseReply: No Advertisement found in Db for device 05/03/2011 08:51:36 10368 (0x2880)
Resolution:
Create a collection, advertise a Task Sequence to that collection and add your machine to the collection.
OR
Check the below settings:
Has the correct MAC address
The account exists in a collection that has a TS advertised to it, and that the computer account has this advertisement advertised to it.
The advertisement is configured to 'make this TS available to boot media and PXE
The computer object is not obsolete and I have cleared any PXE advertisements associated with the account.
Issue:
Error: - The machine has been recently registered in a build collection, but the server takes some time (up to an hour) to process this information.
Cause:
This can be commonly seen when someone PXE boots the machine to write down the MAC address. If he/she then creates a new computer object based on the MAC address, he/she needs to wait an hour before the WDS service will look up the database again. He/she can see this happening in the smspxe.log with an entry such as
MAC=FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF:FF SMBIOS GUID=00000000-0000-0000-0000-000000000000 > Device not found in the database. 25/04/2012 15:18:46 8552 (0x2168).
In this scenario, the deployment process fails. On the client side, the computer tries to restart from the local hard disk instead of from the Pre-Boot Execution Environment (PXE) image.
Resolution:
To resolve this issue make sure that the following actions are taken:
-
Create a REG_DWORD value at HKLM\SOFTWARE\Microsoft\SMS\PXE\CacheExpire...or on a 64-bit server at...HKLM\SOFTWARE\Wow6432Node\Microsoft\SMS\PXE\CacheExpire.
-
Set the value of CacheExpire to the value you want in seconds - a value of 600 would be a timeout of 10 minutes. On a SCCM site, setting the value to be 0 will actually set the timeout to 3600 seconds (back to the 1 hour timeout).
-
Stopping and restarting the WDS service can flush out the cache.
Issue:
Error: - The SMBIOS Guid of the machine is not unique
Cause:
If swapped out some motherboards and not flashed the BIOS correctly.
Resolution:
Checking of Error:
-
To find out which machines have duplicate SMBIOS guids , run this report-SELECT SMBIOS_GUID0, COUNT(SMBIOS_GUID0) AS Count FROM v_R_System .GROUP BY SMBIOS_GUID0, Active0, Client0, Obsolete0 HAVING (Active0 = 1) AND (Client0 = 1) AND (Obsolete0 = 0) AND (COUNT(SMBIOS_GUID0) > 1)
-
Use the following report to pull out the names of the machines with duplicate SMBIOS Guids-SELECT SMBIOS_GUID0, Name0 FROM v_R_System .WHERE SMBIOS_GUID0= '00000000-0000-0000-0000-000000000000'-where 00000000-0000-0000-0000-000000000000 is the GUID that was identified in the previous report.
The only way to solve this problem is to flash the BIOS on the affected workstation to set a unique SMBIOS guid. Contact the PC vendor for the tool to do this.
Issue:
File: \Boot\BCD Status: 0xc000000f.
Info: An error occurred while attempting to read the boot configuration data.
Cause:
This does look like a bcd error,this error comes due to invalid computer object, i.e the \Boot\BCD file is missing or damaged or No Bootmgr (Windows Boot Manager that accesses BCD store) is present.
Resolution:
-
Reinstall PXE and WDS
-
Install PXE point and WDS with a account who had Domain Admins right
-
Add IP helper address for PXE server.
Issue:
The SMS PXE Service Point does not have a boot image matching the processor architecture of the PXE booting device.
Cause:
Only using 32-bit boot images when you have 64-bit machines in your environment.
Resolution:
If your workstation is 64-bit, then you need the 64-bit boot files available - Even if only 32 bit Windows is deployed, and a 32-bit boot image is used, then also the 64-bit boot files are a mandate as they are extracted from the boot image and used during the initial PXE process, so if they're missing, we won't be able to PXE boot a 64-bit machine.
We have understand PXE boot and other scenario, Let understand WIN PE
Many Problem, One Place solutions.
Thanks & Regards,
Haresh Hirani
Email: [email protected], [email protected]
Facebook https://www.facebook.com/Hiraniconfigmgr-120189361980772/
Follow us: https://www.linkedin.com/in/hiraniconfigmgr
Twitter: https://twitter.com/hiraniconfigmgr
X
0 Comments
No Comments