All SCCM 2007 logs at one Place

Client Log Files

The 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.The following table lists and describes the client log files.

Log File Name	Description
CAS	Content Access service. Maintains the local package cache.
CcmExec.log	Records activities of the client and the SMS Agent Host service.
CertificateMaintenance.log	Maintains certificates for Active Directory directory service and management points.
ClientIDManagerStartup.log	Creates and maintains the client GUID.
ClientLocation.log	Site assignment tasks.
ContentTransferManager.log	Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.
DataTransferService.log	Records all BITS communication for policy or package access.
Execmgr.log	Records advertisements that run.
FileBITS.log	Records all SMB package access tasks.
Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs)	Windows Management Instrumentation (WMI) provider for software inventory and file collection.
InventoryAgent.log	Creates discovery data records (DDRs) and hardware and software inventory records.
LocationServices.log	Finds management points and distribution points.
Mifprovider.log	The WMI provider for .MIF files.
Mtrmgr.log	Monitors all software metering processes.
PolicyAgent.log	Requests policies by using the Data Transfer service.
PolicyAgentProvider.log	Records policy changes.
PolicyEvaluator.log	Records new policy settings.
Remctrl.log	Logs when the remote control component (WUSER32) starts.
Scheduler.log	Records schedule tasks for all client operations.
Smscliui.log	Records usage of the Systems Management tool in Control Panel.
StatusAgent.log	Logs status messages that are created by the client components.
SWMTRReportGen.log	Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Site Server Log Files

Most Configuration Manager 2007 site server log files are located in the <InstallationPath>\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. The following table lists and describes the site server log files.

Log File Name	Description
Ccm.log	Client Configuration Manager tasks.
Cidm.log	Records changes to the client settings by the Client Install Data Manager (CIDM).
Colleval.log	Logs when collections are created, changed, and deleted by the Collection Evaluator.
Compsumm.log	Records Component Status Summarizer tasks.
Cscnfsvc.log	Records Courier Sender confirmation service tasks.
Dataldr.log	Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.
Ddm.log	Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.
Despool.log	Records incoming site-to-site communication transfers.
Distmgr.log	Records package creation, compression, delta replication, and information updates.
Hman.log	Records site configuration changes, and publishes site information in Active Directory Domain Services.
Inboxast.log	Records files that are moved from the management point to the corresponding SMS\INBOXES folder.
Inboxmgr.log	Records file maintenance.
Invproc.log	Records the processing of delta MIF files for the Dataloader component from client inventory files.
Mpcontrol.log	Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.
Mpfdm.log	Management point component that moves client files to the corresponding SMS\INBOXES folder.
MPMSI.log	Management point .msi installation log.
MPSetup.log	Records the management point installation wrapper process.
Ntsvrdis.log	Configuration Manager 2007 server discovery.
Offermgr.log	Records advertisement updates.
Offersum.log	Records summarization of advertisement status messages.
Policypv.log	Records updates to the client policies to reflect changes to client settings or advertisements.
Replmgr.log	Records the replication of files between the site server components and the Scheduler component.
Rsetup.log	Reporting point setup log.
Sched.log	Records site-to-site job and package replication.
Sender.log	Records files that are sent to other child and parent sites.
Sinvproc.log	Records client software inventory data processing to the site database in Microsoft SQL Server.
Sitecomp.log	Records maintenance of the installed site components.
Sitectrl.log	Records site setting changes to the Sitectrl.ct0 file.
Sitestat.log	Records the monitoring process of all site systems.
Smsdbmon.log	Records database changes.
Smsexec.log	Records processing of all site server component threads.
Smsprov.log	Records WMI provider access to the site database.
SMSReportingInstall.log	Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.
Srvacct.log	Records the maintenance of accounts when the site uses standard security.
Statmgr.log	Writes all status messages to the database.
Swmproc.log	Processes metering files and maintains settings.

The Admin UI log files are located in <InstallationPath>\AdminUI\. The following table lists and describes the Admin UI log files.

Log File Name	Description
RepairWizard.log	Records errors, warnings, and information about the process of running the Repair Wizard.
ResourceExplorer.log	Records errors, warnings, and information about running the Resource Explorer.
SMSAdminUI.log	Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files

If 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. The following table lists and describes the management point log files.

Log File Name	Description
MP_Ddr.log	Records the conversion of XML.ddr records from clients, and copies them to the site server.
MP_GetAuth.log	Records the status of the site management points.
MP_GetPolicy.log	Records policy information.
MP_Hinv.log	Converts XML hardware inventory records from clients and copies the files to the site server.
MP_Location.log	Records location manager tasks.
MP_Policy.log	Records policy communication.
MP_Relay.log	Copies files that are collected from the client.
MP_Retry.log	Records the hardware inventory retry processes.
MP_Sinv.log	Converts XML hardware inventory records from clients and copies them to the site server.
MP_Status.log	Converts XML.svf status message files from clients and copies them to the site server.

Mobile Device Management Log Files

If mobile device management is enabled in the site hierarchy, mobile device management point log files are generally stored in the <ConfigMgrInstallPath>\LOGS folder on the mobile device management point computer. The following table lists and describes the mobile device management point log files.

Mobile Device Management Point Logs

Log File Name	Description
DmClientHealth.log	Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.
DmClientRegistration.log	Records registration requests from and responses to the mobile device client in Native mode.
DmpDatastore.log	Records all the site database connections and queries made by the Device Management Point.
DmpDiscovery.log	Records all the discovery data from the mobile device clients on the Device Management Point.
DmpFileCollection.log	Records mobile device file collection data from mobile device clients on the Device Management Point.
DmpHardware.log	Records hardware inventory data from mobile device clients on the Device Management Point.
DmpIsapi.log	Records mobile device communication data from device clients on the Device Management Point.
dmpMSI.log	Records the MSI data for Device Management Point setup.
DMPSetup.log	Records the mobile device management setup process.
DmpSoftware.log	Records mobile device software distribution data from mobile device clients on the Device Management Point.
DmpStatus.log	Records mobile device status messages data from mobile device clients on the Device Management Point.
FspIsapi.log	Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Management Client Logs

For the locations of log files on managed mobile devices and on computers that are used to deploy the mobile device client, see How to Configure Logging for Windows Mobile and Windows CE Devices. The following table lists and describes the mobile device management client log files.

Log File Name	Description
DmCertEnroll.log	Records certificate enrollment data on mobile device clients.
DMCertResp.htm (in \temp)	Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.
DmClientSetup.log	Records client setup data on mobile device clients.
DmClientXfer.log	Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.
DmCommonInstaller.log	Records client transfer file installation for setting up mobile device client transfer files on client computers.
DmInstaller.log	Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.
DmInvExtension.log	Records Inventory Extension file installation for setting up Inventory Extension files on client computers.
DmSvc.log	Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

The following table lists and describes the operating system deployment log files.

Log File Name	Description
CCMSetup.log	Provides information about client-based operating system actions.
CreateTSMedia.log	Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.
DriverCatalog.log	Provides information about device drivers that have been imported into the driver catalog.
MP_ClientIDManager.log	Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.
MP_DriverManager.log	Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.
MP_Location.log	Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.
Pxecontrol.log	Provides information about the PXE Control Manager.
PXEMsi.log	Provides information about the PXE service point and is generated when the PXE service point site server has been created.
PXESetup.log	Provides information about the PXE service point and is generated when the PXE service point site server has been created.
Setupact.log Setupapi.log Setuperr.log	Provide information about Windows Sysprep and setup logs.
SmpIsapi.log	Provides information about the state migration point Configuration Manager 2007 client request responses.
Smpmgr.log	Provides information about the results of state migration point health checks and configuration changes.
SmpMSI.log	Provides information about the state migration point and is generated when the state migration point site server has been created.
Smsprov.log	Provides information about the SMS provider.
Smspxe.log	Provides information about the Configuration Manager 2007 PXE service point.
SMSSMPSetup.log	Provides information about the state migration point and is generated when the state migration point site server has been created.
Smsts.log	General location for all operating system deployment and task sequence log events.Log file location:·         If task sequence completes when running in the full operating system with a Configuration Manager 2007 client installed on the computer: <CCM Install Dir>\logs·         If task sequence completes when running in the full operating system with no Configuration Manager 2007 client installed on the computer: %temp%\SMSTSLOG·         If task sequence completes when running in WindowsPE: <largest fixed partition>\SMSTSLOG Note <CCM Install Dir> is %windir%\system32\ccm\logs for most Configuration Manager 2007 clients and is <Configuration Manager 2007 installation drive>\SMS_CCM for the Configuration Manager 2007 site server. For 64-bit operating systems, it is %windir%\SysWOW64\ccm\logs.
TaskSequenceProvider.log	Provides information about task sequences when they are imported, exported, or edited.
USMT Log loadstate.log	Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.
USMT Log scanstate.log	Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

By 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 following table lists and describes the Network Access Protection log files.

Log File Name	Description
Ccmcca.log	Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.
CIAgent.log	Tracks the process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details on installing the software updates required for compliance.
locationservices.log	Used by other Configuration Manager features (for example, information about the client's assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.
SDMAgent.log	Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.
SMSSha.log	The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

The System Health Validator point log files are located in %systemdrive%\SMSSHV\SMS_SHV\Logs, and they are listed and described in the following table.

Log File Name	Description
Ccmperf.log	Contains information about the initialization of the System Health Validator point performance counters.
SmsSHV.log	The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.
SmsSHVADCacheClient.log	Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.
SmsSHVCacheStore.log	Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.
SmsSHVRegistrySettings.log	Records any dynamic changes to the System Health Validator component configuration while the service is running.
SmsSHVQuarValidator.log	Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Setup information for the System Health Validator point can be found in a setup log file, described in the following table, on the computer running the Network Policy Server.

Log File Name	Description
<ConfigMgrInstallationPath>\Logs\SMSSHVSetup.log	Records the success or failure (with failure reason) of installing the System Health Validator point.

Desired Configuration Management Log Files

By 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.

Log File Name	Description
ciagent.log	Provides information about downloading, storing, and accessing assigned configuration baselines.
dcmagent.log	Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.
discovery.log	Provides detailed information about the Service Modeling Language (SML) processes.
sdmagent.log	Provides information about downloading, storing, and accessing configuration item content.
sdmdiscagent.log	Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files

The Configuration Manager 2007 site server log files related to Wake On LAN are located in the folder <ConfigMgrInstallationPath>\Logs on the site server. There are no client-side log files for Wake On LAN. The following table lists and describes the Wake On LAN log files.

Log File Name	Description
Wolmgr.log	Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.
WolCmgr.log	Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

The Configuration Manager 2007 site server log files are found, by default, in <InstallationPath>\Logs. The following table lists and describes the software updates site server log files.

Log File Name	Description
ciamgr.log	Provides information about the addition, deletion, and modification of software update configuration items.
distmgr.log	Provides information about the replication of software update deployment packages.
objreplmgr.log	Provides information about the replication of software updates notification files from a parent to child sites.
PatchDownloader.log	Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server. Note On 64-bit operating systems and on 32-bit operating systems with no Configuration Manager 2007 installed, PatchDownloader.log is created in the server logs directory. On 32-bit operating systems, if the Configuration Manager 2007 client is installed, PatchDownloader.log is created in the client logs directory.
replmgr.log	Provides information about the process for replicating files between sites.
smsdbmon.log	Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.
SUPSetup	Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.
WCM.log	Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.
WSUSCtrl.log	Provides information about the configuration, database connectivity, and health of the WSUS server for the site.
wsyncmgr.log	Provides information about the software updates synchronization process.

WSUS Server Log Files

By default, the log files for WSUS running on the software update point site system role are found in %ProgramFiles%\Update Services\LogFiles. The following table lists and describes the WSUS server log files.

Log File Name	Description
Change.log	Provides information about the WSUS server database information that has changed.
SoftwareDistribution.log	Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

By default, the Configuration Manager 2007 client computer log files 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 following table lists and describes the software updates client computer log files.

Log File Name	Description
CAS.log	Provides information about the process of downloading software updates to the local cache and cache management.
CIAgent.log	Provides information about processing configuration items, including software updates.
LocationServices.log	Provides information about the location of the WSUS server when a scan is initiated on the client.
PatchDownloader.log	Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.
PolicyAgent.log	Provides information about the process for downloading, compiling, and deleting policies on client computers.
PolicyEvaluator	Provides information about the process for evaluating policies on client computers, including policies from software updates.
RebootCoordinator.log	Provides information about the process for coordinating system restarts on client computers after software update installations.
ScanAgent.log	Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.
ScanWrapper	Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.
SdmAgent.log	Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.
ServiceWindowManager.log	Provides information about the process for evaluating configured maintenance windows.
smscliUI.log	Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.
SmsWusHandler	Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.
StateMessage.log	Provides information about when software updates state messages are created and sent to the management point.
UpdatesDeployment.log	Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.
UpdatesHandler.log	Provides information about software update compliance scanning and about the download and installation of software updates on the client.
UpdatesStore.log	Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.
WUAHandler.log	Provides information about when the Windows Update Agent on the client searches for software updates.
WUSSyncXML.log	Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File

By default, the Windows Update Agent log file is found on the Configuration Manager Client computer in %windir%. The following table provides the log file name and description.

Log File Name	Description
WindowsUpdate.log	Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components.

-------------------
Thanks,
http://paddymaddy.blogspot.com/

Configuration Manager Site Supported Configurations

 

 

Primary Site Server

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Enterprise Edition SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Secondary Site Server

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Management Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

State Migration Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Distribution Point

Windows Server 2003 Web Edition SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter and Storage Server Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Distribution Point - Branch DP Role Only

Windows XP Professional Service Pack 2

Windows XP Professional for 64-bit Systems

Windows Vista Business, Enterprise and Ultimate Editions

 

Reporting Point

Windows Server 2003 Standard Edition SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Server Locator Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Site Database Server

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Software Update Point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Fallback status point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

PXE service point

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

 

Configuration Manager Console

Windows XP Professional Service Pack 2

Windows XP Professional x64

Windows Vista Business, Enterprise and Ultimate Editions

Windows Server 2003 Web Edition SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1

Windows Server 2003 Standard and Enterprise Editions with SP 1 x64

Windows Server 2003 Datacenter and Storage Server Edition SP 1

Windows Server 2003 R2 Standard and Enterprise Editions

SCCM 2007 Mobile Device Clients Supported

SCCM 2007 Clients as Mobile Device Client's

 

 

Windows CE 4.2 (ARM processor only)

Windows CE 5.0 (ARM and x86 processors)

Windows Mobile 5.0 Smartphone

Windows Mobile 6 Classic

Windows Mobile 6 Professional

Windows Mobile 6 Standard

Windows Mobile for Pocket PC 2003

Windows Mobile for Pocket PC 2003 Second Edition

Windows Mobile for Pocket PC 5.0

Windows Mobile for Pocket PC Phone Edition 2003

Windows Mobile for Pocket PC Phone Edition 2003 Second Edition

Windows Mobile for Pocket PC Phone Edition 5.0

Windows Mobile Smartphone 2003

Let play a Game with SCCM 2007; Quize on SCCM 2007 ; SCCM 2007 Games

Here is the Microsoft Link...

 

 

http://www.microsoft.com/downloads/details.aspx?familyid=B9FB478A-EC98-47F2-B31E-57443A8AE88F&displaylang=en

 

 

The following quizzes are available:

Configuration Manager 2007 Client Installation Quiz
Configuration Manager 2007 Client Management Quiz
Configuration Manager 2007 Client Site Assignment Quiz
Configuration Manager 2007 Desired Configuration Management Quiz
Configuration Manager 2007 Internet-Based Client Management Quiz
Configuration Manager 2007 Native Mode Quiz
Configuration Manager 2007 Network Access Protection Quiz
Configuration Manager 2007 Wake On LAN Quiz
New! - Configuration Manager 2007 Software Updates Operations Quiz
New! - Configuration Manager 2007 OSDeployment Quiz
New! - Configuration Manager 2007 What's New Quiz
New! - Configuration Manager 2007 Software Updates Configuration Quiz
New! - Configuration Manager 2007 Mobile Device Management Quiz
New! - Configuration Manager 2007 Fundamentals Quiz
New! - Configuration Manager 2007 Client Roaming Quiz
New! - Configuration Manager 2007 Software Updates Interop Quiz
New! - Configuration Manager 2007 Setup Quiz
New! - Configuration Manager 2007 Software Distribution Quiz

 

 

Enjoy,

Paddy

Management Point (MP) Logs

 

 

MP_Ddr	Records the conversion of XML.ddr records from clients, and copies them to the site server.
MP_GetAuth	Records the status of the site management points.
MP_GetPolicy	Records policy information.
MP_Hinv	Converts XML hardware inventory records from clients and copies the files to the site server.
MP_Location	Records location manager tasks.
MP_Policy	Records policy communication.
MP_Relay	Copies files that are collected from the client.
MP_Retry	Records the hardware inventory retry processes.
MP_Sinv	Converts XML hardware inventory records from clients and copies them to the site server.
MP_Status	Converts XML.svf status message files from clients and copies them to the site server.

SCCM 2007 Client To Site Communication Ports

 

 

 

 

Service	Port	Description
Client Request-HTTP (TCP)	80	(default) Client Requests-HTTP (TCP)
Client Request-HTTPS (TCP)	443	(default) Client Requests-HTTPS (TCP)

 

 

By default the HTTP port is set to Port 80 and the HTTPS port is set to Port 443 and as mentioned above can be modified or changed to reflect your infrastructures needs.

 

The ports can also be modified using the PortSwitch VBS script included on the installation media in the Tools\PortConfiguration directory folder using the following syntax to change the HTTP Port number:

 

 

The following g Registry key holds the information for the HTTP and HTTPS ports:

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM

HttpPort=dword:Decimal Value

HttpsPort=dword:Decimal Value

SCCM Ports are configurable & some are not

 

 

Configurable Ports

 

Client to internet (as proxy server settings)

Client to reporting point

Client to site system

Software update point to internet (Proxy server settings)

Software update point to WSUS server

 

UnConfigurable Ports

 

Configuration Manager 2007 console to SMS Provider

Configuration Manager 2007 console to the Internet

Site server to site database server

Site server to site system

Site system to site database server

Site to site (Primary-to-primary or primary-to-secondary)

SQL Query To Find Unhealthy Machines

SQL Query:

 

Select Distinct

Name 'Machine Name',

LastUser 'Last Logged On User',

WasOnline,

LastPingResult State,

Classification Status

From ClientHealthResults

 

Where LastPingResult Is Not Null

And Classification = 'UnHealthy'

RoboCopy VBS Script

VBS script with source and destination folder input dialog boxes as well as hard coding the RoboCopy command line switches opposed to issuing the commands from the command prompt

 

 

 

Set objShell = CreateObject("Wscript.Shell")

 

objSource = InputBox("Enter Source")

objDestination = InputBox("Enter Destination")

 

objCommand = "RoboCopy.Exe " & Chr(34) & objSource & Chr(34) & " " & Chr(34) & objDestination & Chr(34) & " /e /r:1 /w:2"

objShell.Run(objCommand)

 

MsgBox "Done"

What's New in Configuration Manager 2007

Some aspects of Configuration Manager 2007 have changed very little since SMS 2003, while some have changed a lot. Also, several new features have been added and some features have been removed.

The following features are new to Configuration Manager 2007:

• Desired configuration management
  
• Network Access Protection for Configuration Manager
  
• Wake On LAN
  

The following features were previously available only in Feature Packs but are now incorporated into the core product:

• Mobile device management
  
• Operating system deployment
  
• Transfer site settings wizard
  
• Manage site accounts tool (MSAC)
  
• Asset Intelligence
  

The following features have changed significantly from SMS 2003:

• Backup and recovery
  
• Software updates
  

The following features have been improved but still function very much as they did in SMS 2003:

• The administrator console
  
• Collections
  
• Software distribution
  
• Software metering
  
• Remote tools
  

The following features either have not changed or have minor changes:

• Discovery
  
• Inventory
  
• Queries
  
• Reporting
  

The basic site infrastructure has not changed. You still have primary sites and secondary sites, although the new feature for software distribution called the branch distribution point might remove the need to create some child sites in your hierarchy. Site-to-site communication is still configured using senders and addresses; however, in Configuration Manager 2007 senders can be installed only on primary or secondary site server systems. Configuration Manager 2007 now supports hosting the site database on a clustered SQL Server virtual instance as well as SQL Server 2005 named instances. Several new server roles have been added to support new features.

In SMS 2003 you had two types of clients, but in Configuration Manager 2007 you have only one client type, which is similar to the SMS 2003 Advanced Client. Some of the client deployment methods have changed and some methods have been removed. A new method, software update point client installation, allows you to leverage your software update infrastructure to deploy Configuration Manager 2007 clients.

In SMS 2003 you had two security modes, but in Configuration Manager 2007 you have the equivalent of SMS 2003 advanced security. However, you now have two site modes: Configuration Manager 2007 native mode and Configuration Manager 2007 mixed mode. Although site modes are not at all related to the SMS 2003 security modes, they do involve the security of your Configuration Manager 2007 environment. Native mode is a requirement to support Internet-based client management, a new feature that allows you to manage clients that do not have a direct connection to your site.

In SMS 2003, the site server's local subnet is automatically used as the site boundary for the site during setup. In Configuration Manager 2007, there is no default boundary created during setup, and you must manually create the boundary for a site when setup has completed. In SMS 2003, there are site boundaries and roaming boundaries, but in Configuration Manager 2007, there is only one type of boundary and it is equivalent to SMS 2003 roaming boundaries. Computers are assigned as clients to Configuration Manager 2007 sites according to the site boundaries you configure in the Configuration Manager console. Boundaries can now be defined by IP subnets, Active Directory site names, IPv6 Prefix, or IP ranges.

In SMS 2003, roaming boundaries were either local or remote roaming boundaries. When creating Configuration Manager 2007 boundaries, you instead decide whether the boundary will be used for either a slow or unreliable or a fast (LAN) network connection. During upgrade, any existing remote roaming boundaries will become slow boundaries and any local roaming boundaries will become fast (LAN) boundaries.

In SMS 2003, you could not upgrade from the evaluation version of the product to the full version. Configuration Manager 2007 now supports upgrading from the evaluation version. When upgrading an evaluation version, whether it is SMS 2003 or Configuration Manager 2007, an entire setup process must be completed using the new installation source files.

In SMS 2003, the client push installation method properties used when installing clients have the default site code set to Auto. In Configuration Manager 2007, the default site code used when installing clients using the client push installation method is set to the site code of the primary site.

In Configuration Manager 2007, state messages are sent by Configuration Manager 2007 clients using a new messaging system built into the product that allows clients to send "checkpoints" of important changes of state. State messages are not the same as status messages; whereas status messages provide information about component behavior and data flow, state messages provide a snapshot of the state of a process at a specific time.

Configuration Manager 2007 also includes support for fully qualified domain names (FQDNs) and IPv6.

 

can be find more from.....http://technet.microsoft.com/hi-in/library/bb680807(en-us).aspx

Thanks,

Pavan Kumar

Status Check for Wake On Lan

On Error Resume Next

Const wbemFlagReturnImmediately = &h10
Const wbemFlagForwardOnly = &h20

arrComputers = Array("ComputerName")
For Each strComputer In arrComputers
   WScript.Echo
   WScript.Echo "=========================================="
   WScript.Echo "Computer: " & strComputer
   WScript.Echo "=========================================="

   Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\WMI")
   Set colItems = objWMIService.ExecQuery("SELECT * FROM MSNdis_DeviceWakeOnMagicPacketOnly", "WQL", _
                                          wbemFlagReturnImmediately + wbemFlagForwardOnly)

   For Each objItem In colItems
      WScript.Echo "Active: " & objItem.Active
      WScript.Echo "EnableWakeOnMagicPacketOnly: " & objItem.EnableWakeOnMagicPacketOnly
      WScript.Echo "InstanceName: " & objItem.InstanceName
      ''WScript.Echo   " **Computer" & strComputer & "  WOL Settings Failed to Retrive"
     
   Next
Next

Dell recommend using SMS WOL BIOS Settings remote Enable

Dell recommend using SMS and Dell OpenManage Client Instrumentation (OMCI).  However, this requires WMI scripting which may be prevented if security lockdown settings prevent such scripts from running.

Pros: Exposes the Dell BIOS to WMI and therefore enables almost any modification to be made by running VB script.  It also means SMS hardware inventory can then report upon  BIOS settings by extending the SMS_DEF.MOF.

Cons: Requires agent software to be run on the client.

The Dell Client Configuration Utility (DCCU) can be used as an alternative to the OMCI client to create stand-alone executables that can output configuration settings ('Get Values') to an XML file and/or configure BIOS settings ('Set Values'), including enabling WOL.

Pros: Leaves not footprint on the client

Cons: An executable file needs to be created for every action you want to perform against the BIOS; meaning heavier network utilization.

BiosConfigUtility.exe

HP provides a number of tools based on HP Client Management Interface (CMI).  The exception is HP System Software Manager (SSM) which includes a bundled utility called BiosConfigUtility.exe that modifies BIOS settings through a text-based file format, which can be used independently of SSM.   HP says a future version of HP SSM will leverage HP CMI on 32-bit and 64-bit platforms.

Modify the DNS Server Search Order for a Network Adapter

Modify the DNS Server Search Order for a Network Adapter

Configures a TCP/IP-bound network adapter to use two DNS servers: 192.168.1.100 and 192.168.1.200. Note that even if a computer only uses one DNS server, the IP address of that server must still be passed to the SetDNSServerSearchOrder method as an array (in that case, an array with only one element).  and more Scripts can be found here

On Error Resume Next  strComputer = "." Set objWMIService = GetObject("winmgmts:" _     & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")  Set colNetCards = objWMIService.ExecQuery _     ("Select * From Win32_NetworkAdapterConfiguration Where IPEnabled = True")  For Each objNetCard in colNetCards     arrDNSServers = Array("192.168.1.100", "192.168.1.200")     objNetCard.SetDNSServerSearchOrder(arrDNSServers) Next 

SCCM Agent Related Exe file

SCCM Agent Related Exe file

 

 

 

 

ccmdump.exe
CcmExec.exe
ccmrepair.exe
CcmRestart.exe
OSDBitLocker.exe
OSDDiskPart.exe
OSDJoin.exe
OsdMigrateUserState.exe
OSDNetSettings.exe
OSDPrepareOS.exe
OSDPrepareSmsClient.exe
OSDSetupWindows.exe
OSDSmpClient.exe
OSDWinSettings.exe
SCCMNativeModeReadiness.exe
smsboot.exe
SMSCliUI.exe
SmsClrHost.exe
smsnetuse.exe
smsswd.exe
tsenv.exe
TSInstallSWUpdate.exe
TSLauncher.exe
TSManager.exe
TSMBootstrap.exe
TsProgressUI.exe
VAppLauncher.exe
VAppCollector.exe
RCLaunch.exe-Remote Control launch
RCServer.exe-Remote Control Server
clicore.exe

What's new in Windows Vista Service Pack 1 (SP1)

Improvements in reliability

Windows Vista SP1 includes improvements that address many of the most common reasons for which Windows stops responding. Many of the reliability improvements in SP1 are in response to issues that customers reported by using the Windows Error Reporting tool.

Other reliability improvements in Windows Vista SP1 include improvements in wireless computer-to-computer (ad hoc) connections, better peer-to-peer connections, such as using Windows Meeting Space, and many more.

Top of page

Improvements in performance

Windows Vista SP1 includes many changes that can improve your computer's speed and performance. Here are some of the areas that are improved:

•	Faster copying or extracting files from a compressed mode.
•	Better use of network bandwidth when browsing file shares over a network.
•	Improved performance from Windows ReadyBoost in reducing the time it takes for Windows to wake up from Hibernate and Standby power modes.
•	Better power consumption when your computer screen is idle for a long time.
•	Improved logon experience when using a corporate computer, such as a laptop, outside of the corporate network.
•	Faster opening of large image files.

 

Improvements in security

You can now use BitLocker to encrypt multiple partitions on your computer's hard disk, rather than just a single partition. Note that BitLocker is only available in Windows Vista Enterprise and Windows Vista Ultimate.

 

Changes to search

SP1 includes an important change to the way desktop search works in Windows Vista. You can now select a default desktop search service, similar to the way you can select a default search service for web browsers and media players. With SP1, you can now get to your preferred search results from within the Start menu and Windows Explorer.

 

Changes in memory (RAM) reporting

SP1 also changes how the random access memory (RAM) that is installed in your computer is reported. Before SP1, the amount of memory reported was equal to the amount of memory that Windows was able to use. In SP1, the amount of memory reported is the amount of memory that is actually installed on your computer. If you have 4 gigabytes (GB) of memory installed, you'll now see 4 GB of memory reported by features such as System or Performance Information and Tools in Control Panel. This change can only happen if your computer's basic input/output system (BIOS) is capable of displaying that much RAM.

 

Advanced information

If you are an IT professional or an advanced user and want additional detailed information about SP1, you can find the release notes, the SP1 deployment guide, and other information at the Windows Vista Service Pack 1 Resources page on the Microsoft TechNet website.

Query Criterion Values

String Values

You must specify the exact string that the query will use to evaluate the expression — do not use quotation marks unless they are part of the string. For relational operators that perform LIKE comparisons ("is like" or "is not like"), you can use wildcard characters within the string. You can use the following wildcards.

Wildcard	Description
%	Any string of zero or more characters
_ (underscore)	Any single character
[]	Any single character within the range or set (for example [a-f] or [abcdef])
[^]	Any single character not within the specified range (for example [^a-f] or [^abcdef])

Date and Time Values

You must enter a date that the query can use to evaluate the expression. This value must be entered according to the units that are specified by the date and time operator. For example, if you use the "year is after" operator, you would enter the year by using four digits (for example, 2002).

When you write queries by using Configuration Manager 2007 Query Builder, you can express the date and time in any valid SQL format. For more information, see the SQL Server documentation.

Prerequisites for Asset Intelligence :- SMS_def.mof 9 Modification Prerequisites for Asset Intelligence

Prerequisites for Asset Intelligence

 

The Asset Intelligence feature in Configuration Manager 2007 has both external dependencies and dependencies within the product that should be considered when implementing Asset Intelligence or attempting to view Asset Intelligence report information.

The prerequisites for Asset Intelligence in Configuration Manager 2007 include the following:

• Client agent prerequisites
  
• Hardware inventory file modification prerequisites
  
• Site maintenance task prerequisites
  
• Windows event log setting prerequisites
  

Client Agent Prerequisites

The Asset Intelligence reports depend on client information obtained through client hardware and software inventory reports.

To obtain the information necessary for all Asset Intelligence reports, the following client agents must be enabled:

• Hardware inventory client agent
  
• Software metering client agent
  

Hardware Inventory Client Agent Dependencies

To collect inventory data required for some Asset Intelligence reports, the hardware inventory client agent must be enabled. In addition, some hardware inventory reporting classes must be enabled in the SMS_DEF.mof file on the primary site server computer.

For information about enabling the Hardware Inventory Client Agent, see How to Configure Hardware Inventory for a Site.

Software Metering Client Agent Dependencies

A number of Asset Intelligence software reports depend on the software metering client agent for data. For information about enabling the software metering client agent, see How to Configure Software Inventory for a Site.

The following Asset Intelligence reports depend on the software metering client agent to provide data:

• Software 07A - Recently Used Executables by Number of Computers
  
• Software 07B - Computers that Recently Used a Specified Executable
  
• Software 07C - Recently Used Executables on a Specific Computer
  
• Software 08A - Recently Used Executables by Number of Users
  
• Software 08B - Users that Recently Used a Specified Executable
  
• Software 08C - Recently Used Executables by a Specified User
  

Hardware Inventory File Modification Prerequisites

Important file modification prerequisites apply to the Configuration.mof file and to the SMS_def.mof file.

For more information about the Configuration.mof file, see About MOF Files Used by Hardware Inventory.

For more information about editing the Configuration.mof file, see How to Extend Hardware Inventory Using the Configuration.mof File.

Configuration.mof File Modification Prerequisites

Client Access License (CAL) data collection must be enabled in the Configuration.mof hardware inventory data class file to provide data for the Asset Intelligence Client Access License reports. To enable CAL data collection, the Configuration.mof file must be edited and associated maintenance tasks must be enabled. In addition, computer security policies must be configured to audit Success logon events. For more information about enabling success event logging, see How to Enable Success Logon Event Logging.

For more information about Asset Intelligence CAL data reports, see About Client Access License Reports .

For more information about the maintenance tasks that must be enabled to support the Asset Intelligence CAL reports, see the "Site Maintenance Task Prerequisites" section in this topic.

To enable data collection for CAL data, the CCM_CALTrackConfig WMI data class must be edited in the Configuration.mof file to configure the following required settings.

Note
The Configuration.mof file is located on the primary site server computer in the <ConfigMgr installation directory> \ Inboxes \ clifiles.src \ hinv directory.

CALCollectionType

The CALCollectionType parameter controls whether CALs are tracked for devices, users, or both. To enable CAL data collection, the CALCollectionType parameter value must be changed from the default value of 0 to a value that specifies the type of data to be collected. The CALCollectionType parameter can be set to one of the values described in the following table.

Parameter Setting	Setting Description
0	Data collection disabled
1	User CAL collection only
2	Device CAL collection only
3	All CAL collection enabled

Note
If you want to enable CAL data collection on more than one Configuration Manager 2007 or Configuration Manager 2007 SP1 primary site, the Configuration.mof file for each site must be edited.

CALCollectionFrequencyDays

A single server can be accessed regularly by thousands of users and devices. Creating a record in the Configuration Manager site database for each connection could result in high network bandwidth usage. Polling for which users or devices access the server on a weekly basis is adequate for tracking CAL usage. The CALCollectionFrequencyDays parameter value controls the frequency, in days, of CAL data collection. The default value is 7 days, but a value between 0 and 90 days can be specified. Setting this parameter to 0 causes polling to be run based on the CALCollectionFrequencyMinutes parameter.

CALCollectionFrequencyMinutes

When the CALCollectionFrequencyDays parameter setting is set to 0, polling occurs based on the CALCollectionFrequencyMinutes parameter setting. The CALCollectionFrequencyMinutes parameter setting controls the frequency, in minutes, of CAL data collection. A value between 1 and 1,440 minutes can be specified.

Note
Polling for CAL information too frequently in large sites can result in a significant network impact.

CALCollectionTimeWindow

Current Microsoft licensing models allow for CALs to be reassigned every 90 days. The CALCollectionTimeWindow parameter reflects this licensing model. If the model is changed, this parameter can be adjusted to agree with the new licensing model. The default is 90 days, but a value between 1 and 365 days can be specified.

CALSupportedWindowsVersions

To limit polling to servers, this parameter lists the operating system versions that are polled for client access information. This parameter setting should not be modified. Modification of this setting will result in inaccurate CAL counts. The default value is "5.0,5.2,6.0."

SMS_def.mof Modification Prerequisites

The following hardware inventory reporting classes in the SMS_def.mof file can be enabled to support Asset Intelligence reporting requirements:

Note
The SMS_def.mof file is located on the primary site server computer at <ConfigMgr installation directory> \ Inboxes \ clifiles.src \ hinv directory.

1. SMS_SystemConsoleUsage
2. SMS_SystemConsoleUser
   
3. SMS_InstalledSoftware
   
4. SMS_AutoStartSoftware
   
5. SMS_BrowserHelperObject
   
6. SMS_InstalledExecutable
   
7. SMS_SoftwareShortcut
   
8. SoftwareLicensingService
   
9. SoftwareLicensingProduct
   
   
   For more information about hardware inventory reporting classes used by Asset Intelligence, see Hardware Inventory Reporting Classes Required for Asset Intelligence Reports.

Site Maintenance Task Prerequisites

Two site maintenance tasks are associated with CAL information stored in the site database:

• Delete Aged Client Access License Data Properties
  
• Summarize Client Access License Weekly Usage Data
  

For information about enabling and scheduling site maintenance tasks, see How To Schedule a Site Maintenance Task

Delete Aged Client Access License Data

The Delete Aged Client Access License Data maintenance task is not necessary for data collection, but it should be enabled to prevent the accumulation of unnecessary data stored in the site database. The purpose of this task is to periodically delete aged CAL data from the site database that is no longer needed.

For more information, see Delete Aged Client Access License Data Task Overview.

Summarize Client Access License Weekly Usage Data

The Summarize Client Access License Weekly Usage Data task establishes summaries of usage over time and directly supports the Asset Intelligence license management report: License 11A - Historical Client Access License (CAL) Utilization.

The CAL data that is collected from client hardware inventory reports represents a single computer at a single point in time. To have meaningful reports, it is necessary to periodically gather these points together into summaries that are stored and used for the purpose of tracking usage trends over time.

For more information, see Summarize Client Access License Weekly Usage Data Task Overview.

Windows Event Log Setting Prerequisites

Four Asset Intelligence reports display information gathered from the Windows security event logs on client computers. If the security event log settings are not set correctly, these reports will contain no data, even if the appropriate hardware inventory reporting class is enabled.

The following Asset Intelligence reports rely on collected Windows security event log information:

• Hardware 3A - Primary Computer Users
  
• Hardware 3B - Computers for a Specific Primary Console User
  
• Hardware 4A - Shared (Multi-user) Computers
  
• Hardware 5A - Console Users on a Specific Computer
  

To enable the hardware inventory client agent to inventory the information required to support these reports, you must first modify the Windows security event log settings on clients to log all Success logon events, as well as enable the SMS_SystemConsoleUser SMS_def.mof reporting class. For more information about modifying security event log settings to log all Success logon events, see How to Enable Success Logon Event Logging.

Note
The SMS_SystemConsoleUser SMS_def.mof reporting class will retain successful logon data for only the previous 90 days of the security event log, regardless of the length of the log. If the security event log has fewer than 90 days of data, the entire log is read.

Disk Space Threshold Registry Key

Disk SpaceThreshold

By default Windows sends an administrative alert when the amount of free space remaining on a hard disk drive falls below 10 percent. This percentage can be configured using this setting.

Open your registry and find the key below.

Create a new DWORD value called "DiskSpaceThreshold" and set it to the percentage of free disk space remaining before an alert is sent.

Restart Windows for the change to take effect.

 

Registry Settings
System Key: [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\
Parameters]
Value Name: DiskSpaceThreshold
Data Type: REG_DWORD (DWORD Value)
Value Data: 0 - 99 percent (Default is 10)

 

Configuring SLP / MP in WINS

Configuring SLP in WINS

To manually configure the SMS 2003 Server Locator Point (SLP) server in WINS, type the following from a command prompt:

C:\>netsh <enter>
NETSH>wins <enter>
WINS>server <enter>
WINS SERVER>add name Name=SMS_SLP endchar=1A rectype=0 ip={xxx.xxx.xxx.xxx}
(NOTE: Replace x's with IP address of server acting as SLP)

Command completed successfully.
(This will appear if you used the proper syntax.)

This can also be configured in one simple command (all on one line) as follows:
wins server \\SERVERNAME add name Name=SMS_SLP endchar=1a rectype=0 ip={xxx.xxx.xxx.xxx}

To verify the SLP entry in WINS:

WINS SERVER>show name Name=SMS_SLP endchar=1A

Name : SMS_SLP [1Ah]
NodeType : 1
State : ACTIVE
Expiration Date : Infinite
Type of Rec : UNIQUE
Version No : 0 1bc1
RecordType : STATIC
IP Address : xxx.xxx.xxx.xxx
Command completed successfully.

Configuring MP in WINS
To manually configure the SMS 2003 Management Point (MP) in WINS, type:

WINS SERVER>add name Name=SMS_MP endchar=1A rectype=0 ip={xxx.xxx.xxx.xxx}
(NOTE: Replace x's with IP address of server acting as SLP)

Command completed successfully.
(This will appear if you used the proper syntax.)

To verify the MP entry in WINS:
WINS SERVER>show name Name=SMS_MP endchar=1A

Name : SMS_MP [1Ah]
NodeType : 1
State : ACTIVE
Expiration Date : Infinite
Type of Rec : UNIQUE
Version No : 0 1bc2
RecordType : STATIC
IP Address : xxx.xxx.xxx.xxx
Command completed successfully.

When finished, type:
WINS SERVER> exit <enter>
C:\>

Everything was going really well with the newest version of SMS 2003, including an average software distribution success rate of more than 95%. About a month later, when hardware became available, another primary site was configured at our Disaster Recovery location, including a separate server to act as a Central Site for both primary sites.

Problems Arise
From this point, strange things began to happen. Some of our SMS 2003 Advanced Clients were not even receiving configured advertisements and our success rate dipped as low as 60% successful.

Thanks to Michael Niehaus's expertise, the syntax for configuring a Management Point in WINS is slightly different if all the SMS sites in the hierarchy share the same WINS database!!!

Configure Multiple MPs in one WINS Database
To configure multiple SMS 2003 Management Points (MP) in WINS that share the same database, follow this syntax:

add name Name=MP_<sitecode> endchar=1A rectype=0 ip={xxx.xxx.xxx.xxx}
(NOTE: Replace x's with IP address of server acting as SLP)

To verify the MP entry in WINS:

show name Name=MP_<sitecode> endchar=1A

Enjoy,

Paddy