Transcript Johan Arwidmark Chief Technical Architect [email protected] WCL319 Complete an evaluation on CommNet and enter to win!

Johan Arwidmark
Chief Technical Architect
[email protected]
WCL319
Complete an
evaluation on
CommNet and
enter to win!
Agenda
Debugging SCCM 2007
Windows Setup Logs
Following a SCCM 2007 OS Deployment
The deployment process
Join domain issues
PXE booting issues
Windows PE 2.1
Debugging SCCM 2007
Use the TRACE32 Utility to read log files
Works in WinPE too
Logs
Bare Metal - Logs are initially stored in
X:\Windows\Temp
Refresh – Logs are initially stored in
C:\Windows\System32\CCM\Logs
Key Log file is smsts.log
Add Command Shell via F8 to the boot image
Windows Setup Logs
Device Drivers issues
XP / 2003 – Setupapi.log
Vista / 2008 - Setupapi.dev.log
Other Setup issues
Setupact.log
Setuperr.log
Following the white rabbit Deployment
Johan Arwidmark
Chief Technical Architect
TrueSec
Go With the Flow...
TechNet – Configuration Manager
Document Library
Troubleshooting Operating System Deployment
Log Files
Monitoring
Common issues
Additional Troubleshooting Docs in MDT 2008
Download documentation from
www.microsoft.com/deployment
ZTI with SCCM 2007
The Deployment Process
Johan Arwidmark
Senior Executive Consultant
TrueSec
Join Domain issues
Verify AD Permissions
Create / Delete computers
Update existing computers
For both XP and Vista
Examine C:\Windows\Debug\Netsetup.log
Solving Join Domain Issues
Johan Arwidmark
Senior Executive Consultant
TrueSec
PXE Issues
PXE Boot Requirements
Upgrade BIOS
DHCP Configuration
DHCP and WDS on the same server
Configure WDS not to listen on port 67
Allow it to configure the 60 PXE option
DHCP and WDS on different Subnets
Configure IP Helpers
SCCM and WDS Integration
Installation steps
1. Install the WDS role
2. Run wdsutil.exe /initialize
/reminst:D:\RemoteInstall after install
3. Add the PXE Service Point (PSP)
4. Distribute BOTH x86 and x64 boot images
to the PSP DP
5. DHCP Option 60 needed if the PSP is a
DHCP server
Solving PXE issues
Johan Arwidmark
Senior Executive Consultant
TrueSec
Windows PE 2.1 Considerations
Memory
WinPE requires 512 MB RAM
Drivers
Use monolithic version of two-tier drivers
Filesystem ”converted” into RAW
The Windows PE Uberbug
Configure Scratchspace
Windows PE 2.1 Logs
WPEinit.log
Setupapi.dev.log
Solving Windows PE Issues
Johan Arwidmark
Senior Executive Consultant
TrueSec
Resources
Free Tutorials and Training Videos
www.deploymentcd.com
Blogs on Windows Deployment
www.deployvista.com
www.myitforum.com
http://blogs.technet.com/msdeployment
http://blogs.technet.com/deploymentguys
http://blogs.technet.com/mniehaus
Track Resources
Key Microsoft Sites
System Center on Microsoft.com: http://www.microsoft.com/systemcenter
System Center on TechNet: http://technet.microsoft.com/systemcenter/
Virtualization on Microsoft.com: http://www.microsoft.com/virtualization
Community Resources
System Center Team Blog: http://blogs.technet.com/systemcenter
System Center Central: http://www.systemcentercentral.com
System Center Community: http://www.myITforum.com
System Center on TechNet Edge: http://edge.technet.com/systemcenter
System Center on Twitter: http://twitter.com/system_center
Virtualization Feed: http://www.virtualizationfeed.com
System Center Influencers Program: Content, connections, and resources
for influencers in the System Center Community. For information, contact
[email protected]
Resources
www.microsoft.com/teched
www.microsoft.com/learning
Sessions On-Demand & Community
Microsoft Certification & Training Resources
http://microsoft.com/technet
http://microsoft.com/msdn
Resources for IT Professionals
Resources for Developers
www.microsoft.com/learning
Microsoft Certification and Training Resources
© 2009 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should
not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS,
IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.