Troubleshooting OSD Configuration Manager

8/10/2019 Troubleshooting OSD Configuration Manager

1/21


2/21

Microsoft Confidential

OSD Troubleshooting Essentials

Use of F8 for launching Command Prompt in Windows PE

CMTrace utility included in boot images

Key Log files to capture/investigate Examining logs and State Messages via Configuration Manager reporting

OSD Error Codes


3/21


4/21


5/21


Task Sequence Log

SMSTS.log: Primary log file for all OSDs and task sequence events

Deployment Phase SMSTS.log Location

When running in Windows PE X:\Windows\Temp\SMSTSLog\

In full operating system with noConfiguration Manager Clientinstalled

%temp%\SMSTSLog\

In operating system: With task

sequence running

\Logs\SMSTSLog\

In operating system: Task sequencecompleted

\Logs\


6/21


7/21


Driver Management Logs

DriverCatalog.log

o Provides information about device drivers that have been imported into the driver catalog

o Location: \Logs

MP_DriverMgr.logo Provides information about the System Center 2012 Configuration Manager management point

to a request from theAuto Apply Driver task sequence action

o Generated on the System Center 2012 Configuration Manager management point

o Location: %ProgramFiles%\SMS_CCM\Logs (by default)


8/21


9/21


State Migration Point Logs

SMSSMPSetup.log

o Provides information about the state migration point and is generated when the state migrationhas been created

o

Location: \logs Smpmgr.log

o Provides information about the results of state migration point health checks and configuration

o Location: \logs

SmpIsapi.log

o Provides information about the state migration point responses to client requests

o Location: %ProgramFiles%\SMS_CCM\Logs (by default)


10/21


User State Migration Tool (USMT) Logs

Loadstate.log

o Details on loading user state data

o Location: (on client) %windir%\ccm\logs

Scanstate.logo Details on capturing user state data

o Location: (on client) %windir%\ccm\logs


11/21


Windows Setup Log Files

SetupApi.Dev.log

Device installation information is logged to aid in debugging device driver(s) installation on Windo

SetupApi.log

Device installation information is logged to aid in debugging device driver(s) installation on Windo

SetupAct.log

Contains information about Windows setup and mini-setup actions

SetupErr.log

Contains a list of errors that occurred during installation and their severity (this log file should be 0errors occurred during installation)

Location of these log files:

o %windir% (Windows Server 2003/Windows XP)

o %windir%\Panther (Windows Vista or newer)


12/21


Additional Setup Logs

Cbs.log

o Location: %WINDIR%\logs\cbs

o Shows results of Deployment Image Servicing and Management (DISM) commands to inject driv

packs, security updates, etc. during the operating system installation process Netsetup.log

o Location: %WINDIR%\Debug

o Useful when troubleshooting domain join issues

WindowsUpdate.log

o Location: %WINDIR%

o Useful for detecting issues installing updates from Windows Update, Windows Server Update SeConfiguration Manager Software Update Point


13/21


Task Sequence Error Codes

As deployment runs, errors are stored in:

o SMSTS.log

o Reported to management point

Determine description of error codes byo Reviewing SMSTS.log in CMTrace.exe

o TechNet site: Troubleshooting Operating System Deployment Using Custom Error Codes (Listed in http://technet.microsoft.com/en-us/library/bb735886.aspx

o Product help file/online product help and forums
http://technet.microsoft.com/en-us/library/bb735886.aspxhttp://technet.microsoft.com/en-us/library/bb735886.aspx


14/21


Monitoring Deployments using Reports

Task sequence progress can be monitored through the reporting services point

Four categories of reports exist for summarized and individual task sequence progresso Task Sequence: Deployment status

o Task Sequence: Deployments

o Task Sequence: Progress

o Task Sequence: References


15/21


Sample Task Sequence Report


16/21


Determining Errors through Log Snippets


17/21


Common PXE Issues

Several items to check/configure:

o PXE/Windows Deployment Services (WDS) set up correctly

o WDS server service running

o Expired PXE certificateo Boot images on distribution point

o Are boot images of both architecture types available on PXE enabled distribution point?

o Boot files present in RemoteInstall directory

o Unknown computer object viewed in Devices with same Media Access Control (MAC) address

o Network Considerations (Virtual Local Area Networks (VLANs)/IP Helpers)

o Task sequence deployed correctly?

o Duplicate System Management BIOS (SMBIOS) GUID or MAC Address

o PXE cache expiration timing

o Clear required PXE deployments needed

o Is the machine configured to boot from network?

o Is the machine known/unknown to Configuration Manager?

o Is the task sequence deployment limited to Configuration Manager clients only?


18/21


Check PXE/WDS Availability

Verify PXE server health via the logs:

o SMSPXE.log: Track activity of the PXE server

o WDS logging: C:\Windows\Debug\tracing\WDSServer.log

o Enable logging in WDSo Internet Information Services (IIS) logs


19/21


Appendix A: Task Sequence Error Codes

Error Code Description

0x80040001 Could not get the client GUID

0x80040101 Network access account is not set

0x80040102 No content location returned for the given package

0x80040103 Could not access package content in the distribution po

0x80040104 Could not find reference program policy

0x80040105 Could not find CCM_ClientAgentConfig raw policy

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) An invalid image capture path has been specified

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) An invalid image file name extension has been specified


MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) Image capture path is too long


MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Timeout waiting for Plug and Play (PNP) to finish initializ


20/21


Appendix A: Task Sequence Error Codes (continued)

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Task sequence failed in Windows PE

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) An invalid network adapter index has been specified

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) Sysprep is not installed

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Sysprep is invalid

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3) Invalid System Partition

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) Machine is joined to a domain

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5) Machine is domain controller

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1) A default management point has not been assigned for this si

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2) Certificates for the default management point are not availab

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3) Package {0} is not available on the specified distribution point

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4) Invalid password for media certificate

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5) The media certif icate does not have an associated private key

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,6) The certification authoritys certificate has not been set for this


21/21

Documents

Troubleshooting OSD Configuration Manager