SMS2003部署及troubleshooting

http://struggle.blog.51cto.com/333093/79354
详解SMS2003部署Windows 2003

http://www.winsvr.org/info/info.php?sessid=&infoid=32&page=1
SMS 2003安装配置系列之一:SMS 2003主站点安装指南



http://www.ixpub.net/archiver/tid-658413.html
解读SMS2003日志文件

http://www.microsoft.com/technet/sms/2003/library/techfaq/tfaq03.mspx#EWEAC
Clients Frequently Asked Questions


http://www.ixpub.net/thread-658378-1-7.html
如何解决在 Systems Management Server 2003 高级客户端推送安装问题


http://www.microsoft.com/technet/scriptcenter/guide/sas_roa_overview.mspx?mfr=true
Microsoft Windows 2000 Scripting Guide


http://technet.microsoft.com/en-us/library/cc179974%28TechNet.10%29.aspx
Scripting in SMS


http://support.microsoft.com/kb/883620
You cannot install Advanced Client when your Systems Management Server 2003 does not use Active Directory or when the schema for Active Directory has not been extended


http://support.microsoft.com/kb/925282
How to troubleshoot Advanced Client Push Installation issues in Systems Management Server 2003

http://www.tek-tips.com/viewthread.cfm?qid=1151166&page=1
解决sms客户端无法安装的问题，如何检查DC之间的复制是否成功。


http://technet.microsoft.com/en-us/library/cc181833%28TechNet.10%29.aspx
technet resource: Systems Management Server 2003

Force SCCM client to check advertisements

System ManagementCustomize SMS Using Local Policies
http://technet.microsoft.com/en-us/magazine/2006.09.customizesms.aspx

Force Task Sequence Execution without Advertisement
http://social.technet.microsoft.com/Forums/en-US/configmgrsdk/thread/298b32f6-746c-473a-b7ce-6bb51cfe1270/

Force SCCM Client to Check for New Advertisements
http://social.technet.microsoft.com/Forums/en-US/configmgrswdist/thread/a1066dfb-a71e-4e52-b7b7-c225ea0935a4/

Control SCCM client actions by scripting

The Advanced Client, is scriptable. You can use the CPApplet locally on the client or you can use WMI to do things remotely. On thing you'll often need is the triggering of an action. There are loads of samples in this forum meanwhile how to do it. Here is an overview of the actions available and their respective ScheduledMessageIDs which you will need to trigger them remotely.
(From http://www.myitforum.com/articles/8/view.asp?id=6757)
Hardware Inventory Cycle
CPApplet Name: Hardware Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000001}

Software Inventory Cycle
CPApplet Name: Software Inventory Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000002}

Discovery Data Collection Cycle
CPApplet Name: Discovery Data Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000003}

File Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000010}

ID MIF Collection Cycle
CPApplet Name: Standard File Collection Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000011}

Machine Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate Machine Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000021} RequestAssignments Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000022} Evaluate Policy Resource Type=’Machine’
The Machine Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context with no corresponding Client Actions.
ScheduledMessageID: {00000000-0000-0000-0000-00000040} CleanupPolicy Resource Type=’Machine’
ScheduledMessageID: {00000000-0000-0000-0000-00000042} ValidateAssignments Resource Type=’Machine’

User Policy Retrieval & Evaluation Cycle
CPApplet Name: Request & Evaluate User Policy
ScheduledMessageID: {00000000-0000-0000-0000-00000026} RequestAssignments Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000027} Evaluate Policy Resource Type=’User’
The User Policy Retrieval & Evaluation Cycle consists of these two actions! There are two more Scheduled Messages in this context.
ScheduledMessageID: {00000000-0000-0000-0000-00000041} CleanupPolicy Resource Type=’User’
ScheduledMessageID: {00000000-0000-0000-0000-00000043} ValidateAssignments Resource Type=’User’

Software Metering Usage Report Cycle
CPApplet Name: Software Metering Usage Report Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000031}

Windows Installer Source List Update Cycle
CPApplet Name: MSI Product Source Update Cycle
ScheduledMessageID: {00000000-0000-0000-0000-00000032}

There are a few Scheduled Messages that do not correspond to Client Actions that can be triggered via the GUI.

Refresh default MP
ScheduledMessageID: {00000000-0000-0000-0000-00000023} LSRefreshDefaultMPTask

Refresh Location
ScheduledMessageID: {00000000-0000-0000-0000-00000024} LSRefreshLocationsTask

Timeout Location Service Requests
ScheduledMessageID: {00000000-0000-0000-0000-00000025} LSTimeOutRequestsTask

Manage Certificates
ScheduledMessageID: {00000000-0000-0000-0000-00000051} CertMaintenance

Force SCCM clients to check for new program advertisements

Q: How can I force my SCCM clients to check for new program advertisements?
A: Program advertisements occur as part of the Machine Policy Retrieval & Evaluation cycle action in the SCCM Client.
To force a client to find new programs that are available ahead of the regular discovery phase, perform these steps:
1. Start the Systems Management Control Panel applet (Start, Settings, Control Panel, Configuration Manager).
2. Click the Actions tab.
3. Select "Machine Policy Retrieval & Evaluation Cycle" and click Initiate Action.
4. Close the Systems Management Control Panel applet. Within a few minutes, the new-program advertisements should be visible. Alternatively, you can use the Policy Spy Tool to force a Machine policy retrieval. You can download the Policy Spy Tool at http://www.microsoft.com/smserver/downloads/2003/tools/toolkit.asp.




Q: When you distribute sw to user collections what triggers the installation?
A: It is the "User policy retrieval and evaluation cycle" that triggers the installationThe interval of "User policy retrieval and evaluation cycle" is defined in the Computer Client Agent properties on the SCCM server:
(http://technet.microsoft.com/en-us/library/bb693764.aspx)
SCCM console -> site management-> site name XXXX -> site settings -> client agents -> right click

By default it’s 60 minutes.

BDD 2007 - Troubleshooting Database issues

BDD 2007 - Troubleshooting Database issues

(Original from Ben Hunter's blog, check more details from this link:
http://blogs.technet.com/benhunter/archive/2007/07/10/bdd-2007-troubleshooting-database-issues.aspx)

Common issues
The following section details common issues and recommended configurations for each.
Database Rules - Ensure that the appropriate database rules have been created. Database rules are specified using the deployment point rules tab. Configuration database rules can be created manually or using the Configure DB Wizard in the Deployment Workbench.
A typical database section should look similar to the following:
[CSettings]
SQLServer=SERVERNAME
Database=BDDAdminDB
Netlib=DBNMPNTW
SQLShare=logs
Table=ComputerSettings
Parameters=MacAddress
ParameterCondition=OR
The critical components of the database section are:
SQLServer - must specify the SQL server that hosts the BDD configuration database. SQLShare – must be a valid share on the SQL server and the user account (UserID as specified in the rules) must have access rights to that share. If SMS OSD Feature Pack is used for deployment then the SMS Advanced Client installation account will require access rights rather than the user account. Netlib – there are many issues with using TCP/IP sockets based connections so ONLY USE NAMED PIPES (DBNMPNTW).Database connectivity issues – There are a number of issues that can stop the client connecting to the SQL server, these are detailed below:
Ensure that Named Pipes is enabled for remote connectivity on the SQL server, this is not enabled by default. Has the surface area been configured to enable Named Pipes? When using SQL 2005 it is important to ensure that the “Surface area” is configured in such a way that remote connectivity to Named Pipes is allowed. If you have issues accessing the database from the workbench then ensure that you are using Named Pipes. The Deployment Workbench always uses Named Pipes to connect to the database.Security - has the deployment account got the appropriate database rights? The account used will need read rights to the BDD admin database. The account can vary depending on the deployment type:
ZTI – The SMS advanced client installation account. LTI – The user account specified in the rules (bootstrap.ini).SQL instances – If you are connecting to a database instance then this instance must be specified. This value is specified using the Instance field in the deployment workbench

Troubleshooting methods
During the troubleshooting process it is critical that you can easily test the database rules. The following instructions detail how to manually test the database connectivity. The rules specified in the deployment point can be tested without running through the entire BDD build process. Rules are processed using a script called ZTIGather.wsf, this script can be run separately from the other BDD scripts allowing easy testing. The steps below detail the process required to perform manual rule testing. To properly reflect the deployment environment it is important to perform these tests from a client device:
1. Create a folder on the client device and copy the following files from the deployment point to this folder:
ZTIGather.wsf ZTIGather.xml ZTIUtility.vbs CustomSettings.ini 2. Delete C:\MININT directory if it already exists. This folder can also be located at X:\MININT if the C drive is not available.
NOTE: BDD stores configuration and progress information in the MININT folder, if this folder is not removed between tests then the results will be invalid.
3. From the command prompt navigate to the newly created folder and execute the rule processing script using the following command:
"cscript.exe ZTIGather.wsf /debug:true"
The script will then be processed and the results outputted to the command prompt and a log file ( .\MININT\SMSOSD\OSDLOGS\ZTIGather.log)

List of Log Files in Configuration Manager 2007

http://technet.microsoft.com/en-us/library/bb892800.aspx

List of Log Files in Configuration Manager 2007

All the client and site server components in Microsoft System Center Configuration Manager 2007 record process information in individual log files. You can use the information in the client and site server log files to help you troubleshoot issues that might occur in your Configuration Manager 2007 hierarchy.
By default, client and server component logging is turned on in Configuration Manager 2007.
Client Log FilesThe Configuration Manager 2007 client logs are located in one of the following locations:
On computers that serve as management points, the client logs are located in the SMS_CCM\Logs folder.
On all other computers, the client log files are located in the %Windir%\System32\CCM\Logs folder or the %Windir%\SysWOW64\CCM\Logs.

Site Server Log FilesMost Configuration Manager 2007 site server log files are located in the \LOGS folder. Because Configuration Manager 2007 relies heavily on Microsoft Internet Information Services (IIS), you can review the IIS log file for additional errors that relate to client access to the IIS server. The IIS log file is located in the %Windir%\System32\logfiles\W3SVC1 folder on the IIS server.

Management Point Log FilesIf management points are installed in the site hierarchy, management point log files are stored in the SMS_CCM\LOGS folder on the management point computer.

Network Access Protection Log FilesBy default, client log files related to Network Access Protection are found in %windir%\CCM\Logs. For client computers that are also management points, the log files are found in %ProgramFiles%\SMS_CCM\Logs.
The System Health Validator point log files are located in %systemdrive%\SMSSHV\SMS_SHV\Logs.
Desired Configuration Management Log FilesBy default, the Configuration Manager 2007 client computer log files are found in %windir%\System32\CCM\Logs or in %windir%\SysWOW64\CCM\Logs. For client computers that are also management points, the client log files are located in the SMS_CCM\Logs folder. The following table lists and describes these log files.

Wake On LAN Log FilesThe Configuration Manager 2007 site server log files related to Wake On LAN are located in the folder \Logs on the site server.
Software Updates Site Server Log FilesThe Configuration Manager 2007 site server log files are found, by default, in \Logs.
WSUS Server Log FilesBy default, the log files for WSUS running on the software update point site system role are found in %ProgramFiles%\Update Services\LogFiles.
Software Updates Client Computer Log FilesBy default, the Configuration Manager 2007 client computer log files are found in %windir%\CCM\Logs.
Windows Update Agent Log FileBy default, the Windows Update Agent log file is found on the Configuration Manager Client computer in %windir%.
Out of Band Service Point Log FilesThe Configuration Manager 2007 SP1 log files listed in the following table are located in the folder \Logs on the site system server selected to host the out of band service point role.
Out of Band Management Console Log FilesThe Configuration Manager 2007 SP1 log file listed in the following table is located in the folder \AdminUI\AdminUILog on any computer that runs the out of band management console from the Configuration Manager console.

Out of Band Client Computer Log FilesThe Configuration Manager 2007 SP1 log file listed in the following table is located in the folder %windir%\System32\CCM\Logs on workstation computers that are running the Configuration Manager 2007 SP1 client and that are managed out of band.

Troubleshooting Tips for SCCM deployment

http://blogs.technet.com/inside_osd/archive/2007/12/13/troubleshooting-tips.aspx
Inside ConfigMgr 07 Operating System Deployment
Contributed by Brett Flegg

Troubleshooting Tips
The follow is a collection of tips that may be helpful when troubleshooting issues with ConfigMgr 07 Operating System Deployment.

Error Codes
There is no definitive list of error codes that can be returned in a task sequence, because most of the error codes originate from calls to other Windows API functions. The error lookup functionality provided by trace32.exe is a good place to start when trying to figure out what a specific error code means (in trace32.exe, go to Tools / Error Lookup...).

Enable the Debug Shell on your boot image
Boot images have an option to enable a command shell while running in Windows PE. This is turned off by default for security reasons (since it would allow an end user to open a command shell during the re-imaging process) but can be enabled on the “Windows PE” property page.
Open the boot image’s properties dialogOn the Windows PE tab check the “Enable command support (testing only)” optionUpdate the boot image on the distribution pointsRebuild any media that uses the boot image (e.g. capture media, boot media, or stand-alone media)When a task sequence is running in Windows PE you can open a command shell by pressing F8. As long as the command-shell is open the task sequence will not reboot the machine. This will give you a chance to verify network connectivity, diagnose driver issues, and view/copy the log files (see Client Log Files section below).

Client Log Files
All actions in a task sequence log to the smsts.log file. This file is moved around during different stages of an operating system deployment so that it does not interfere with the imaging process.
While in Windows PE the log file is stored in the windows temp directory on the RAM-disk (typically x:\windows\temp\smstslog)While in a full operating system that has a ConfigMgr client installed the log file is located in the smstslog subdirectory under the client logging path (typically %windir%\system32\ccm\logs\smstslog)While in the full operating system that does not have a ConfigMgr client installed the log file is located in the Windows temp directory (typically %windir%\temp\smstslog)When the task sequence completes, the log file is “finalized” to one of the following locations depending on the state of the machine:
If the task sequence finishes in Windows PE the log file is copied to an SMSTSLog directory on the largest available partition.If the task sequence finishes in the full operating system and a ConfigMgr client is installed then the log is copied to the client logging path (typically %windir%\system32\ccm\logs)If the task sequence finishes in the full operating system and there is no ConfigMgr client installed then the log is copied to the Windows temp directory.

Task Sequence Reports
When running, task sequences send status messages back to the server for each step in the task sequence. Included in these status messages are the last 1024 characters of stdout/stderr text from the action. Many times, this information can be used to remotely diagnose a task sequence issue (especially useful if an error has occurred in Windows PE and the debug shell was not enabled). The “History - Specific task sequence advertisements run on a specific computer” report provides a list of these status messages for a specific advertisement and computer and can be opened from the Reports node in the ConfigMgr console.

Create a shortcut using the runas command

A command prompt with administrative credentials:
runas /user: ComputerName\administrator cmd

Computer Management with administrative credentials: runas /user:ComputerName\administrator "mmc %windir%\system32\compmgmt.msc"

Active Directory Users and Computers with domain administrative credentials: runas /user:DomainName\administrator "mmc %windir%\system32\dsa.msc"

Active Directory Users and Computers in another forest: runas /netonly /user:DomainName\UserName"mmc %windir%\system32\dsa.msc"