Professional Documents
Culture Documents
Prepared for NY Limited May 2009 on 1. 0 Prepared by Ramesh Oddepally Microland Ltd COMPA Tuesday, 12 Versi
1.1 Software requirements for Installing SCCM 2007 Server .......................................5 1.2 Creation of SCCMService account.............................................................................6 1.3 Creation of SCCM2007 Group:...................................................................................6 2 Extending Active Directory Schema for SCCM 2007.....................................................8 3 Additional Configurations on SCCM servers.................................................................12 4 Installing and Configuring IIS for SCCM 2007..............................................................13 5 Installing SQL 2005.....................................................................................................16 6 Installation and Configuration of SCCM Primary Site Server.........................................17 6.1 Installion of SCCM 2007 Primary Site..................................................................17 6.2 Installation of Winodws Software Update Services 3.0 ...........................................27 7 Configuring SCCM 2007 Site........................................................................................32 7.1 Configuring SCCM Site Configuration ...................................................................32 7.2 Configuring Address................................................................................................35 7.3 Configuring Boundaries...........................................................................................38 7.4 Configuring SCCM Site Settings ............................................................................39 7.5 Configuring Client Agents.....................................................................................45 7.5.1 Configuring Hardware Client Inventory Agents.................................................46 7.5.2 Configuring Software Client Inventory Agents.................................................47 7.5.3 Configuring Remote Tools Client Agents..........................................................48 7.5.4 Configuring Advertised Programs Client Agents...............................................54 7.5.5 Configuring Software Metering Client Agents..................................................56 7.5.6 Configuring Computer Client Agent................................................................56 7.5.7 Software Updates Client Agent.........................................................................58 7.6 Configuring Client Installation Methods...................................................................60 7.7 Component Configuration .....................................................................................63 7.8 Configuring Discovery Methods ...........................................................................68 7.8.1 Configuring Active Directory System Discovery ...............................................69 7.8.2 Configuring Heartbeat Discovery .....................................................................70 7.9 Configuring SCCM Collections.................................................................................72 7.9.1 Creating Query-based membership Collection..................................................72 7.9.2 Creating direct membership Collection.............................................................78 7.10 Performing Hardware & Software Inventory..........................................................85 7.11 Configuring Software Metering..............................................................................91 8 Configuring Software Distribution.................................................................................93 8.1 Software Distribution - Office 2007.........................................................................93 8.1.1 Creation of an Administrative folder ................................................................94 8.1.2 Creation of Package for Office 2007 .................................................................98 8.1.3 Assigning Package to Distribution Point..........................................................103 8.1.4 Creation of Program for Office 2007 Package.................................................105 8.1.5 Creation of Advertisement for office 2007......................................................107 8.2 Software Distribution - File Format Convertor 2007..............................................113 8.2.1 Creation of Package for File Format Convertor 2007.......................................113 8.2.2 Assigning Package to Distribution Point..........................................................118 8.2.3 Creation of Program for File Format Convertor 2007 Package........................120 8.2.4 Creation of Advertisement for File Format Convertor 2007.............................125 9 Patch deployment using SCCM 2007...........................................................................130 9.1 9.2 9.3 9.4 Update Synchronization........................................................................................130 Update List............................................................................................................131 Deployment Template...........................................................................................135 Deploy Software Updates......................................................................................141
Monitoring Software Updates Deployment..............................................................142 9.4.1 Creating Deployment Package........................................................................142 9.4.2 Creating Deployment Management................................................................146 9.4.3 Monitoring Software Updates Deployment......................................................151 9.4.3.1 Evaluation Phase .....................................................................................151 9.4.3.2 Enforcement Phase...................................................................................156 10 Additional SCCM Configuration & Other Details .......................................................162 10.1 10.2 10.3 10.4 10.5 10.6 Deploying SCCM Clients ..................................................................................162 Installing ConfigMgr2007 Toolkit ....................................................................166 Troubleshooting SCCM Client Installation ..........................................................169 Executing SCCM Reports ...................................................................................172 Viewing SCCM Logs ...........................................................................................176 Backing Up SCCM Site .......................................................................................179
11 References .............................................................................................................181
Add the SCCM Service account and the SCCM server ESSHAZCES01 and ESSHAZPRI01 as members
In System Center Configuration Manager 2007, SCCM clients can use Active Directory to locate SCCM resources. Before SCCM clients can query Active Directory for these resources, the Active Directory schema must be extended and the SCCM resource information must be published to Active Directory. Clients running Windows XP, Windows 2000 or Windows Server 2003 will automatically detect the server locator points and management points without generating Windows Internet Name Service (WINS) traffic The Systems Management container must be created and SCCM must be granted full control to the container so that SCCM publishes information to active directory. If SCCM is granted full control to the System container, SCCM can automatically create the System Management container under the System container. If the neccompanyy permissions are not granted, SCCM cannot publish any information to Active Directory, and SCCM clients cannot use features such as automatic site assignment and global roaming. By default, SCCM also generates status error message 4913 until it can successfully publish to Active Directory. To extend the active directory schema, Run the command-line tool ExtADSch prior or post SCCM installation. This ExtADSch.exe can be located in the \SMSSETUP\BIN\I386 folder on the SCCM 2007 CD. The ExtADSch tool results can be found in the ExtADSch.log. These log files are created in the root directory of %system% drive
To verify the Active Directory schema is extended, go to C: drive and open ExtADSch.log file as show below
Active Directory schema extension creates four classes and 10 attributes. The details of which are provided below ManagementpPoint -ServerLocatorPoint -Site -RoamingBoundaryRange MS-SMSMSMSMSSMS SMS SMS
Attribute common names that are implemented and used by SCCM 2007 sites include the following: -Site-Code -Assignment-Site-Code -Site-Boundaries -Default-MP -Device-Management-Point MP-Name -MP-Address -Ranged-IP-Low -Ranged-IP-High MSMSMSMSMSMSMSMSMSSMS SMS SMS SMS SMS SMSSMS SMS SMS
The snapshot below displays the four classes that have been created after extending the active directory schema
On the SCCM server, Select the local SMS Admin groups and add the SCCM2007 group and the SCCM Service account as members in each of the group.
IIS needs to be installed prior to installing SCCM 2007. The following snapshots detail the procedures that are required for configuring IIS. Click on Start < Control Panel and Select Add / Remove Programs Select Application Server and click on details to install the components required under IIS. Click on next.
Select BITS (Background Intelligent Transfer Service) including its extensions or subcomponents and click on Ok as shown.
Next, After installing IIS, Launch IIS manager by going to Start > Programs > Administrative tools > Internet Information Service (IIS) Manager as shown below. Click
on Web Server Extensions in the left pane. The web server extensions with their status are displayed in the right pane as shown below. The following components needs to be allowed under web server components as shown Active Server Pages BITS Server Extensions WebDAV
Install SQL 2005 with Service Pack 2 using Local system account and Windows Authentication. SQL 2005 needs to be installed with the default options.
6.1
In this sub-section, We would be mentioning the procedures applicable for installing SCCM primary sites. Insert the System Center Configuration Manager and go to bin\i386 folder then click on setup.exe which would launch the below setup wizard, click on Next to continue
Select Install a Configure Manager site server and click on next to continue
On the Microsoft Software License Terms, Select I accept these license terms as shown below
Select Primary Site option for Primary Site installation and click on Next to continue
Select No, I do not want to participate right now option as shown below
Select the Destination Folder for Configuration Manager Installation as shown below
Select the applicable Site code and Site name as shown below
Select the Client agents as shown below and click on Next to continue
Type the Management Point as shown below and click on Next to continue
Select the Port Settings as shown below and click on Next to continue
If the Updated Prerequisite Components are already downloaded then select The latest updates have already been downloaded to an alternate path as shown below
Specify the folder name in Updated Prerequisite Component Path as shown below
Select Full server installation including Administration Console as shown below and click on Next to continue
Accept the License Agreement as shown below and click on Next to continue
Select the existing database server in Database Options as show below and click on Next to continue
Select the Web Site Selection as shown below and click on Next to continue
7.1
In this sub-section, The following SCCM site configuration details are explained
Boundaries
Note: This is applicable for Primary site configurations Navigate to Site Hierarchy > SCCM Primary Site Name> Right click the SCCM site as shown below and select properties.
The SCCM site properties page is displayed. The General tab indicates the SCCM site configuration details such as Site Type, Site Server Name, SQL Server Name, Parent Site Details, etc. Click on the Set Parent Site button as displayed below.
The snapshot below indicates that the SCCM site configured is a central site and in case of COMPANY SCCM hierarchy, Hazira would be the central site.
In case of SCCM Primary sites, select the option Report to Parent Site as shown below. Ex In case of primary site servers such as Mahalaxmi then specify the option Report to parent site mentioning the central site (Hazira) server details as shown, click on Ok.
Specify the Primary Site Code details along with the Site Server name for primary sites as mentioned below.
In case of Primary SCCM sites, Specify the site code and site server name details of central site as shown
On the Site Boundaries tab, Specify the site boundaries based on applicable Active Directory Ste, IP Subnets or IP addresses range as displayed below. Boundaries defined on Active Directory Site as shown below
7.4
In this sub-section, The following are the roles which can be configured under SCCM site settings and are explained below
Document: SCCM 2007 Deployment Guide Page 39 of 181
Management Point Distribution Point Server Locator Point Reporting Point. Software Update Point
Note: This is applicable for both Central and primary and site configurations Under the SCCM Site Hierarchy for COMPANY, Go to Site Settings > Site Systems and Click on the SCCM Server name and by default the Management Point, Distribution Point would be displayed in the right pane as shown below
To configure other additional roles right click on Site Systems Server and click on New Role as shown below
Type the FQDN name of the SSCM server and select the remaining options as shown below
We can install multiple roles at one time, so select the applicable roles which needs to Installed as shown below
Select the options as shown below for Server Locator Point and click on Next to continue
Select the options as shown below for Reporting Point and click on Next to continue
Enter the Proxy Settings for Software Update point as shown below and click on Next to continue
Select the option as shown below for Active software update point settings and click on Next to continue
7.5
In this sub-section, We would be configuring client agents. The following client agent configurations are mentioned below Hardware Inventory Client Agent
Software Inventory Client Agent Computer Client Agents Remote Tools Client Agent Advertised Programs Client Agent Software Metering Client Agent Software Update Client Agent
This is required to configure agents for software inventory, hardware inventory at central and primary site servers. Note: This is applicable for all primary site configurations Go to Site Hierarchy > Site Settings, Double Click on Client Agents as shown below. The different client agents are shown in the right pane.
7.5.2
Right click on the Software Inventory Client Agent and select properties. Following configuration need to be done in the Software Inventory Client Agent Enable Software inventory on clients Simple Schedule
7.5.3
Right click on the Remote Tools Client Agent and select properties On the Remote Tools Client Agent properties, Navigate to General Tab and enable the following Options Enable Remote Tools on Clients Clients running Windows 2000 Clients running Windows XP or later
Navigate to Security Tab in Remote Tools client agent and perform the following configuration. On the Security Tab Click use for Remote Client connection. Click Ok and Specify the Windows users account to
Navigate to Notification Tab in Remote Tools client agent and perform the following configuration Select the following options Display a visual indicator Show status icon on taskbar Play a sound Repeatedly during session
Navigate to Advanced Tab in Remote Tools client agent and perform the following configuration Select the following options Configure solicited Remote Assistance settings Level of access allowed
Navigate to Remote Desktop Tab in Remote Tools client agent and perform the following configuration Select the following options Configure Remote Desktop settings Allow permitted viewers to connect using Remote desktop Connection
7.5.4
Right click on the Advertised Programs Client Agent and select properties On the Advertised Programs Client Agent properties, Navigate to General Tab and enable the following options Enable software distribution to Clients New program notification icon
On the Advertised Programs Client Agent properties, Navigate to Notification Tab and enable the following options
7.5.5
Right click on the Software Metering Client Agent and select properties On the Software Metering Client Agent properties, navigate to General Tab and enable Software metering on clients option On the Schedule tab, Specify the schedule based on COMPANYs requirements
7.5.6
Right click on the Computer Client Agent and select properties and configure the following options General Customization Reminders BITS Restart On the Computer Client Agent properties, navigate to General Tab and Click on Set to specify the Network Access Account
Specify the SRHOUSE\backup as the Windows User Account under as displayed below.
Then navigate to Update Installation Tab and specify the settings as shown below
Then navigate to Deployment Re-evolution Tab and specify the settings as shown below
Go to Site Hierarchy > Site Settings, Click on Client Installation Methods in the right pane double click on Client Push Installation and select the following options as shown below
On the Accounts tab of Client Push Installation properties page, specify the respective administrator credentials for your location. In the example below, we have specified Domain admin account of COMPANY, Click on Ok
On the advanced client tab, The Site code should be as shown below
7.7
Component Configuration
In this sub-section, We would be performing the component configuration. This is required for defining the appropriate site servers as management points and for specifying software distribution drive and configuring software updates settings. Note: This is applicable for all primary site configurations Go to Site Hierarchy > Site Settings, Double Click on Component Configurations as shown below. The applicable components under this category are displayed in the right pane.
Right click on Software Distribution option under Component configuration and select properties. On the properties page, Navigate to the General tab and specify the location for stored packages as Drive-E
Right click on Management Point option under Component configuration and select properties. On the properties page, Navigate to the General tab and specify the site server that would be defined as the management point. Ex Site server at COMPANY Mahalaxmi i.e. ESSMAHPRI defined as management point for Mahalaxmi SCCM site
Right click on Software Update Point Component option under Component configuration and select properties. On the properties page, Navigate to the General tab and specify the settings as shown below
Then navigate to the Sync Settings tab and specify the settings as shown below
Then navigate to the Classifications tab and specify the settings as shown below
Set the Sync Schedule as shown below and click on Next to continue
7.8
In this sub-section, We would be configuring discovery methods for SCCM 2007 at COMPANY. This is required because SCCM site databases needs to be populated with resources and information about the network. This is applicable for all primary site configurations
Highlight Active Directory System Discovery in the right pane and select properties. On the Active Directory System Discovery properties page, Ensure that Enable Active Directory System Discovery is selected as shown below. Click on to specify the active directory container or organizational unit. In COMPANY case, specify the OU that represents your respective location and which contains the system resources for that particular location. As shown
Navigate to the Polling Schedule for active directory system properties page and click on schedule button as shown below to define a specific schedule for system discovery purpose. Optionally, if active directory system discovery to be performed immediately then select the checkbox for option Run discovery as soon as possible as shown In the schedule provided below, Active Directory System Discovery is performed every day at 12.00 AM as shown below.
7.8.2 Configuring Heartbeat Discovery Go to Site Hierarchy > Site Settings, Double Click on Discovery Methods Highlight Heartbeat Discovery in the right pane and select properties Select the option Enable Heartbeat Discovery as shown below. Specify the applicable schedule for heartbeat discovery.
7.9.1 Creating Query-based membership Collection In COMPANY there is a SCCM hierarchy with Central and primary sites, so the default collections would be owned and locked by the Central site as shown below and to manage primary site computers we need to collections for each respective location.
The procedure for creating query-based collection for Hazira locations All Windows XP systems is explained below. Right-click on Queries as shown below and select New > Query as shown
Document: SCCM 2007 Deployment Guide Page 72 of 181
Type the applicable collection name as shown below and click on Next to continue
Click on Icon
Type the Query Rule Name and click on Import Query Statement as shown below
Select the applicable Query from the Browse Query list as shown below
Click on OK to continue
7.9.2 Creating direct membership Collection The procedure for creating direct membership based collection is explained below. Right-click on Collections and select New > Collections as shown
Specify the name for the collection to be created and in this case a new collection for office 2007 desktops is being defined as shown below
On the Membership rules tab, Click on the icon to create a new collection as displayed below. Click on the option Update this collection on a schedule to update the new collection.
Resource Class category can consists of options such as System Resource Attribute Name category can consist of the following options as shown below. Click on next.
On the Collection Limiting screen as shown below, specify All Systems as the collection from where the resources can be searched so that these can be added as part of this new collection. Click on next.
Select the applicable computers which would part of the new office 2007 desktop collection as shown below
Click on Close to complete the creation of the new Office 2007 desktop collection. This procedure needs to be followed for creation of any additional collections as required by COMPANY.
The newly created office 2007 desktop collection would displayed as shown below
In case of COMPANY, Specify the time interval that is appropriate for running software and hardware inventory. The schedule for Hardware and Software Inventory may be required to be run earlier than the pre-defined schedule in the following scenarios Software Metering Software Updates (Patch Management)
Software Metering If a new software component has been installed and for which software metering reports are desired then one may require to run the software and hardware inventory for a lesser time interval than originally set, Ex 1 min. Note: - Once the activity has been completed it is advisable to revert back to the original schedule. Else, the hardware and software inventory would keep on executing based on the new schedule defined and this may lead to an increase in network utilization
Software Updates (Patch Management) Prior to deploying software updates, Hardware and Software inventory needs to be executed. This is necessitated to display the software updates installed and in addition the latest updates that are required to be installed on the clients machines.
The procedure for setting time interval for hardware and software inventory is explained below Navigate to Hardware Inventory Client Agent under Site Hierarchy > Site Settings > Client Agents as shown below Right click on Hardware Inventory Client Agent and click on properties as displayed.
On the General tab of Hardware Inventory Client agent properties as displayed, Select the custom schedule option as shown.
On the schedule screen as shown, specify the interval applicable to COMPANYs requirement
Note: - Similar procedure as explained above needs to be followed for defining the schedule interval in case of Software Inventory The software inventory and hardware inventory details can be viewed as shown. Select the appropriate collection for which software and hardware inventory needs to be displayed. Right click on the specific collection and select All Tasks > Start Resource Explorer as displayed below
The details for the last successful software scan is shown as below
On the Software Metering Ruler properties page as displayed, assign a name for the software metering rule to be configured and specify a path for the software program that needs to be metered. The version details are automatically picked once the particular executable for the program is specified. Specify the applicable language option for the program to be installed.
The specified application for software metering would be displayed in the right pane as shown below
Note: - Run the reports under software metering to display the specific details. Refer to reports section for running reports.
Click on Create a new Setup customization file for the following product.
Now the office customization tool will open. On the first tab specify the location where you want to install office. By default it installs in Program files\Microsoft office folder. Also enter the organization name.
On the licensing and user interface tab specify the product key details for completing the creation of Office 2007 MSP file. Accept the license agreement, select display level to None, remove the check mark from the completion notice, select suppress nodal and no cancel as shown in the below figure.
On the Remove previous installations tab click on remove the following earlier versions of Microsoft office programs as shown below.
If you dont want to remove the earlier versions of i.e. Word then double click on Microsoft Office Word. The following windows will popup, remove the check mark from Microsoft Office Word (All versions)
Below figure shows that after removal of the check mark Microsoft Office Word displays Remove None.
On the set feature Installation states drop down on the office components you dont want to install and click on not available. Now you will see a red cross on that component.
Close this window and you will be prompted to save the changes you have made through the customization tool. Name the file as custom.msp and save this .msp file in Updates folder in the Office dump.
Office customization is over and the Custom.msp file is saved in Updates folder as shown below.
Click on browse button to specify the location for Office 2007 administrative folder on the SCCM server containing the MSI files. Alternatively, the administrative folder can also be specified from a machine on COMPANY LAN. In COMPANY case, we have specified the administrative folder on the SCCM server. Click on Browse
Specify the path to the OFFICE12.SMS file under the administrative folder created for Office 2007 as shown below. Click on open to proceed further. Note: Please down load the OFFICE12.sms file from the below URL and copy it to the office2007 folder as shown below http://www.microsoft.com/downloads/details.aspx?FamilyID=590B8EB2-9EDA-441BA972-B38E17883063&displaylang=en
The specified Microsoft Office 2007 package is displayed as shown below. Click on next
Specify the option to always obtain files from the source directory as displayed below. Click on next.
Specify the source directory location as the local drive on SCCM site server. This source directory contains the source files for the package that is being created as shown below. Click on next.
Select the distribution point as shown below and click on Next to continue
8.1.4 Creation of Program for Office 2007 Package To create a program for un-attended installation, go to Package>Program as shown below
Right click on Silent (No UI) from the list of programs and go to properties as shown below
Remove the default command line and specify only the Setup.exe as shown below
On the Advertise to Sub collections page select Advertise the program to members of the specified collection. And click next
On the Advertise Schedule select the Date and Time and Select if and when the Advertisement should expire. Select No, This advertisement does not expire.
On the Assign the Program page select Yes, Assign the Program and select the schedule for the same. Click Next.
Specify the application source folder path and select other details as shown below
Select the Data Access options as shown below and click on Next to continue
Select the Distribution Settings options as shown below and click on Next to continue
Select the Reporting option as shown below and click on Next to continue
To assign a package to the Distribution Point, Go to package and right click on Distribution Point>and click on New Distribution Point as shown below
Type the Program name and Command line as shown below for quiet installation and no restart
Select Whether or not user is logged on option as shown below and click on Next to continue
Type the Advertisement name, then select Package, Program and Collection as shown below
Select the Distribution Points option as shown below and click on Next to continue
Once the synchronization completes all the updates would be displayed in Software updates as shown below
update list instead of manually selecting the set of updates every time a new deployment is created. . Update lists also allow administrators to create update lists with approved updates, and then delegate the responsibility to deploy the update lists. Select the patches which needs to be installed, then click on Update List as shown below
All the selected patches would be displayed under Update List folder as shown below
following deployment properties Collection Display/Time Settings Restart Settings Event Generation Download Settings SCCM 2007 Settings
To create a Template for all Windows XP systems, right click on Deployment Template, and then click on New Deployment Template as shown below
Type the Template Name as shown below and click on Next to continue
Since there is no Microsoft Operations Manager (MOM) server in COMPANY, Select the Event Generation settings as shown below
Since there are no legacy SMS 2003 clients in COMPANY, click on Next to continue
updates to the clients. This sub-section would contain the following two activities: Creating Deployment Package Creating Deployment Management Monitoring Software Updates Deployment
Type the applicable Software Update Deployment name and description as shown below
Select the Data Access settings as shown below and click on Next to continue
To create a Deployment Management right click on selected patches Update List>and click on Deploy Software Updates as shown below
Enter the unique name and detailed description for Deployment Management
The Deployment Management would be display with all the active software updates as shown below
9.4.3
In this sub-section we would describing the procedure for monitoring the status of the software updates deployments. This sub-section would include following two main phases for monitoring the status of the updates deployment. Evaluation Phase Enforcement Phase
In the Configuration Manager console, navigate to System Center Configuration Manager > Site Database > Computer Management >Reporting > Reports>Go to Software Updates - C. Deployment States category as shown below
Right-click States 2 - Evaluation states for a deployment, and then click Run.
Enter the user name and password as shown below and click on OK
In the Deployment ID box, click Values to view a list of possible deployments to choose
Click on Display to view the report. The evaluation states for the deployment are listed with the number of client computers in each state
Click the Report Link icon in the first column on any row to open the States 4 Computers in a specific state for a deployment <secondary> report to display the computer information, the last time a state message was received from the client computer, the evaluation state for the deployment, and the error status if one exists.
Document: SCCM 2007 Deployment Guide Page 154 of 181
If there are errors, click the Report Link icon in the row that contains the error to open
Since there are no errors for the deployment the States 7 - Error status messages for a computer report is blank as shown below
States 1 - Enforcement states for a deployment report summarizes the enforcement state of client computers for a specified deployment. This report provides information about the state for installing the updates in the deployment; for example, downloading the update, installing the update, successfully installed the update, and so on.
States 4 - Computers in a specific state for a deployment <secondary> report can be drilled into to get more information about the client computer within a specified state.
States 7 - Error status messages for a computer can be drilled into to get all error messages for the deployment on the specific computer.
In the Configuration Manager console, navigate to System Center Configuration Manager > Site Database > Computer Management >Reporting > Reports>Go to Software Updates C Deployment States category as shown below
Right-click States 1 - Enforcement states for a deployment, and then click Run.
Enter the user name and password as shown below and click on OK
In the Deployment ID box, click Values to view a list of possible deployments to choose, and then click the deployment. To limit the list, in the Deployment ID text box enter part of the deployment name followed by the percent wildcard and then click Values.
Click Display to view the report. The enforcement states for the deployment are listed with the number of client computers in each state.
Click the Report Link icon in the first column on any row to open the States 4 Computers in a specific state for a deployment <secondary> report to display the computer information, the last time a state message was received from the client computer, the enforcement state for the deployment, and the error status if one exists.
If there are errors, click the Report Link icon in the row that contains the error to open the States 7 - Error status messages for a computer report.
Since there are no errors reported in the enforcement phase of the deployment, the States 7 - Error status messages for a computer report is blank as shown below
10 Additional Details
SCCM
Configuration
&
Other
In this sub-section, the following topics would be covered Deploying SCCM Clients Installing CinfigMgr2007 Toolkit Troubleshooting SCCM Client Installation Executing SCCM Reports Viewing SCCM logs Backing Up SCCM Site Performing Hardware & Software Inventory
On the Welcome page for SCCM Client Push Installation Wizard, Click on next
Select the option Always Install (Repair or Upgrade existing Client) to Install the SCCM Client. Click Next to continue the installation. If you are pushing the SCCM clients on the collections for the first time then you can use this option, IF some of the machines in this collection have already SCCM clients while some dont have SCCM clients installed then you can de-select this option in order to avoid re-installation of SCCM clients on those machines where SCCM clients have already been installed. Alternatively, One can select SCCM clients assigned to a particular site to allow SCCM clients to be installed on machines that are part of the particular SCCM site. Click on next.
The installation of SCCM client can be confirmed by navigating to control panel and one would see the icon of Configuration Manager as shown below
Double click on Configuration Manager Icon to view the SCCM client properties for that particular machine. It includes details such as ConfigMgr Site Code, ConfigMgr Client Version, AD Site Name, Hostname, IP Address details, etc
The SCCM Component details as part of the SCCM client program and their respective status such as Installed / Enabled are displayed.
On the actions tab, One can initiate action manually for a particular category by selecting the particular action and click on initiate action button
On the Advanced tab as shown below, One can discover the SCCM Site details by clicking on the discover button. One needs to be logged in with the domain administrative privileges in order for the site discovery to be successful.
10.2
The SMS Trace is a log viewer that provides a way to easily view and monitor all SCCM logging activity. The SMS trace is part of the ConfigMgr2007 toolkit. The procedure for installing the ConfigMgr2007 toolkit is explained below Note: - The ConfigMgr2007 toolkit provides useful tools to help with the tracking of an SCCM installation and diagnostics of that install and subsequent usage. Download the latest version of ConfigMgr2007 toolkit from http://www.microsoft.com/downloads/details.aspx?FamilyID=948e477e-fd3b-4a09-9015141683c7ad5f&DisplayLang=en Double click on CcmTools.msi to launch the ConfigMgr2007 toolkit installation.
Click on I accept the license agreement to accept the licensing terms and click on next
The SMS Trace utility can be launched from the following path
Windows Firewall Service needs to be disabled on the client desktop Remote Registry service needs to be started on the client desktop Windows Management Instrumentation (WMI) service needs to be started on client desktop Administrator credentials specified during the SCCM client installation such as backup need to be added in the local administrators group on the client computers or should be part of Domain Admin group Admin$ share needs to be accessible on client machine Time specified on the client machine needs to be synchronized with the time server
If a problem with SCCM Client installation still persists then check the CCM logs using SMS Trace as mentioned below Launch SMS Trace by navigating to Programs > ConfigMgr2007 Toolkit > Trace32 as shown
On the SMS Trace screen, Click on open to view the appropriate log files
Specify the appropriate log file to view. In case of SCCM client installation, select CCM log file.
Click on Reports under Site Database > Reporting to display the out-of-box reports available with SCCM 2007. These reports are available for different categories such as Hardware Inventory, Software Inventory, Software Metering, Software Distribution, Software Updates, Software Files, Status Messages, etc.
To run a report, Right click on any particular report under a particular category and click on All Tasks > Run as shown below.
To view the logs or messages, Navigate to System Status under Site Database as shown. Select the appropriate category you want to view the status for. Ex If one wants to view the messages or status for the particular site then click on Site Status under System Status and once can view two categories under site status. These are component system status and site system status. Messages are displayed with the following identifications i.e. Green for normal, Yellow for warnings and Red for critical messages as shown below.
To view a particular message, Right click on the component in the right pane for which messages need to be viewed and select show messages. You are presented with an option to view all messages including errors, warnings and normal status messages or one can view only a particular category such as errors or warnings or all messages. Also, If the old messages needs to be purged then select the option reset counts and select for all or for warnings or errors
Messages specific for that component are displayed as shown below. Double click on a particular message or error to be viewed as shown.
Select the Backup ConfigMgr site server task and right click on that task and go to properties. Ex Backup ConfigMgr Site server task. Right click on that task to launch properties page. The following configuration needs to be done in the Backup ConfigMgr Site Server properties Select the Enable this Task Click on Set Paths and Specify the backup location E.g. C:\SCCMBACKUP Specify the backup schedule time and days
11 References
Following is the list of public references that could be useful in the daily-basis: SCCM 2007 System Center Configuration Manager Server Home http://technet.microsoft.com/en-us/library/bb735860.aspx System Center Configuration Manager 2007 Features http://technet.microsoft.com/en-us/library/bb680550.aspx Desired Configuration Management in Configuration Manager http://technet.microsoft.com/en-us/library/bb693504.aspx System Center Configuration Manager 2007 Configuration Pack http://www.microsoft.com/downloads/details.aspx?familyid=45586F82-18164AEBA0DC-ADE1859820B9&displaylang=en System Center Configuration Configuration Pack Manager 2007 Vulnerability Assessment
http://www.microsoft.com/downloads/details.aspx?FamilyId=FC6989E9-68A343B1-8019-72BC1B9C5FF3&displaylang=en System Center Configuration Manager 2007 Toolkit http://www.microsoft.com/downloads/details.aspx?familyid=948E477E-FD3B4A09-9015-141683C7AD5F&displaylang=en Troubleshooting Configuration Manager 2007 http://technet.microsoft.com/en-us/library/bb632812.aspx