You are on page 1of 21

System Center 2012 R2

Configuration Manager Operating


System Deployment

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

Microsoft Confidential

Launching Command Prompt in Windows PE


Boot images can be modified to include command-line support
Pressing F8 during the Windows Pre-installation Environment (Windows PE) phase in the OSD process
launches a command prompt
Benefits of command prompt:
o Review log files
o Map network drive(s)
o Test drivers for Windows PE using drvload

o Use of administrative tasks/tools (Diskpart, check files/status)


o Prevent automatic reboot

Microsoft Confidential

Enabling Command-Line Support


Configured in the Customization tab of the boot image

Microsoft Confidential

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 no


Configuration Manager Client
installed

%temp%\SMSTSLog\

In operating system: With task


sequence running

<CCMInstallDir>\Logs\SMSTSLog\

In operating system: Task sequence <CCMInstallDir>\Logs\


completed

Microsoft Confidential

Admin Console Logs


CreateTSMedia.log
o Provides information about task sequence media when it is created. This log is generated on the computer running

the Configuration Manager administration console


o Location: <ConfigMgrInstallationPath>\AdminConsole\AdminUILog (may include ProgramFiles(x86) if installed on
64-bit OS)

TaskSequenceProvider.log
o Provides information about task sequences when they are imported, exported, created, or edited
o Location: <ConfigMgrInstallationPath>\logs

Microsoft Confidential

Driver Management Logs


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

o Location: <ConfigMgrInstallationPath>\Logs

MP_DriverMgr.log
o Provides information about the System Center 2012 Configuration Manager management point when it responds

to a request from the Auto Apply Driver task sequence action


o Generated on the System Center 2012 Configuration Manager management point
o Location: %ProgramFiles%\SMS_CCM\Logs (by default)

Microsoft Confidential

Preboot Execution Environment (PXE) Logs


DISTMGR.log
o Provides information about enabling the PXE feature

o Location: <ConfigMgrInstallationPath>\logs

SMSPXE.log
o Provides information about the Configuration Manager PXE feature, PXE requests, and PXE availability
o Location on site server: ..\SMS_CCM\logs
o On remote distribution point: ..\sms\logs

MP_ClientID.log
o Provides information about the Configuration Manager management point when it responds to client ID requests

from boot media or PXE


o This log is generated on the Configuration Manager management point
o Location: <ConfigMgrInstallationPath>\SMS_CCM\Logs

Microsoft Confidential

State Migration Point Logs


SMSSMPSetup.log
o Provides information about the state migration point and is generated when the state migration point site server

has been created


o Location: <ConfigMgrInstallationPath>\logs

Smpmgr.log
o Provides information about the results of state migration point health checks and configuration changes
o Location: <ConfigMgrInstallationPath>\logs

SmpIsapi.log
o Provides information about the state migration point responses to client requests
o Location: %ProgramFiles%\SMS_CCM\Logs (by default)

Microsoft Confidential

User State Migration Tool (USMT) Logs


Loadstate.log
o Details on loading user state data

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

Scanstate.log
o Details on capturing user state data
o Location: (on client) %windir%\ccm\logs

Microsoft Confidential

10

Windows Setup Log Files


SetupApi.Dev.log
Device installation information is logged to aid in debugging device driver(s) installation on Windows Vista or newer

SetupApi.log
Device installation information is logged to aid in debugging device driver(s) installation on Windows XP

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 0 bytes in size if no
errors occurred during installation)

Location of these log files:


o %windir% (Windows Server 2003/Windows XP)
o %windir%\Panther (Windows Vista or newer)

Microsoft Confidential

11

Additional Setup Logs


Cbs.log
o Location: %WINDIR%\logs\cbs

o Shows results of Deployment Image Servicing and Management (DISM) commands to inject drivers, language

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 Services (WSUS), or

Configuration Manager Software Update Point

Microsoft Confidential

12

Task Sequence Error Codes


As deployment runs, errors are stored in:
o SMSTS.log

o Reported to management point

Determine description of error codes by


o Reviewing SMSTS.log in CMTrace.exe
o TechNet site: Troubleshooting Operating System Deployment Using Custom Error Codes (Listed in Appendix A)

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

Microsoft Confidential

13

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 progress
o Task Sequence: Deployment status
o Task Sequence: Deployments
o Task Sequence: Progress
o Task Sequence: References

Microsoft Confidential

14

Sample Task Sequence Report

Microsoft Confidential

15

Determining Errors through Log Snippets

Microsoft Confidential

16

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 certificate
o 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?

Microsoft Confidential

17

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 WDS
o Internet Information Services (IIS) logs

Microsoft Confidential

18

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 point

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,3)

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,5)

An invalid image file name extension has been specified.

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,1)

Timeout waiting for Plug and Play (PNP) to finish initialization


Microsoft Confidential

19

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 site

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,2)

Certificates for the default management point are not available

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,3)

Package {0} is not available on the specified distribution points

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,4)

Invalid password for media certificate

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,5)

The media certificate does not have an associated private key

MAKE_HRESULT(SEVERITY_ERROR,FACILITY_ITF,6)

The certification authoritys certificate has not been set for this site

Microsoft Confidential

20