SCCM 2007 R2: Installation in Windows Server 2008 - SCCM Installation

Before we are able to install SCCM 2007 R2 on the operating system platform Windows Server 2008 and to have Active Directory integration we need to fulfill some pre-requisites. Following are the pre-requisites for SCCM 2007 R2: §  Active Directory Schema has to be extended; §  SCCM System Management Container has to be created in Active Directory; §  Microsoft Remote Differential Compression feature has to be installed; §  WebDAV has to be installed and configured in IIS; §  BITS Server Extensions feature has to be installed; §  WSUS Server 3.0 SP1 has to be installed. 1. Installation Pre-Requisites for SCCM 2007 R2  In this part we are going to full fill the pre-requirements for installation of SCCM 2007 R2 1.1 Extend the Active Directory Schema This task can only be executed whilst logged on with a user account that is member of the "Schema Admins” group in Active Directory. The account “Domain Admin” is member of this group. Place the installation medium for SCCM 2007 SP1 and open a Windows Explorer. Follow the path to: %CD-ROM%\Z:\SMSSETUP\BIN\I386 In this location you will find the file: EXTADSCH.exe Start the extension of the Active Directory by double clicking the file "EXTADSCH.exe” When the DOS Box disappears the extending part is done. Verify the extension by opening the file: C:\ ExtADSch.log If the actions was successful the .log file should contain the lines: Successfully extended the Active Directory Schema 1.2 Create the Systems Management Container in Active Directory For creating the System Management Container we need to be logged on to an Active Directory Domain Controller or need to have to "Remote Administration Tools" installed. On a Domain Controller open the ADSI Edit snap-in. §  Browse to the following location: Domain\DC\CN=System §  Right click the container “System” and select the option: System\New\Object The  "Create Object Wizard” appears. In the “Create Object” wizard select the option: Container Click on à Next §  Enter the following values: Value:                  System Management Click on à Next Click à Finish The “System Management “container is now created. 1.2.1 Permissions on the System Management Container To have SCCM being able to access the created container we need to change the permissions in this container. §  Open the “Active Directory Users and Computers” snap-in. §  Click on the menu option "View" and select “Advanced Features”. The "System" OU will now be visible. §  Open the “System” OU and browse to “System Management” §  Right click the “System Management” container and select the option: Properties Select the tab “Security” §  Click on à Add §  Click on à Object Types §  Select the following “Object Types”: (X)          Computers (X)          Users Click on à OK §  Click on à Advanced §  Click on à Find Now Select the accounts of: §  SCCM-Admin §  %SCCM Server Account% Click on à OK Click on à OK §  Grant the following permissions to the two selected accounts: §  Read §  Write §  Create All Child Objects §  Delete All Child Objects Click on à Advanced Select the account “SCCM-Admin” and click à Edit Select the following options: Apply to:             This object and all descendant objects (X)          Apply these permissions to object and/or containers within this container Click on à OK Repeat these steps for the account “%SCCM Server Account%” Click on à OK    Click on à OK to save the changes. Now we have finished the creation of the System Management Container and setting the correct permissions, 1.3 Installation of Windows Server 2008 feature Remote Differential Compression Logon to the SCCM Server to be and open the “Server Manager” snap-in. Select the "Features” option. §  Click on à Add Features §  Select the option: (X)          Remote Differential Compression Click on à Next Click on à Install Click on à Close when the installation is finished 1.4 Installation of the WebDAV extensions for IIS The WebDAV extensions for IIS Server are not available in Windows Server 2008. You have to download the installation files separately and install them.     Download §  Start the installation by double clicking on the file:     webdav_x86_rtw.msi §  The installation wizard appears Select the option: (X)          I accept the terms in the License Agreement Click on à Install Click on à Finish when the installation is done. 1.4.1 Configuration of the WebDAV extensions in IIS Server Manager To configure the WebDAV extensions for use with SCCM 2007 R2 follow the instructions in Microsoft's TechNet Document: http://technet.microsoft.com/en-us/library/cc431377.aspx 1.5 Installation of Windows Server 2008 BITS Extensions feature Logon to the SCCM Server to be and open the “Server Manager” snap-in and select the option “Features” §  Click on à Add Features §  Select the option: (X)          BITS Server Extensions An additional feature component installation screen appears. §  Click on à Add Required Role Services §  Click on à Next §  Click on à Next §  Click on à Next §  Click on à Install 1.6 Installation of WSUS Server 3.0 SP1 In this part of the article I will describe the installation of WSUS Server 3.0 SP1. WSUS Server 3.0 SP1 is being used by SCCM to deploy Windows Updates to managed systems. Also we will install update Kb954960 for WSUS Server 3.0 SP1. This update adds the latest product information which can be downloaded from the Microsoft Website. The installation source for WSUS Server 3.0 SP1 can be downloaded here   §  Start the installation of WSUS Server 3.0 SP1 by double clicking the file:     WSUSSetup_30SP1_x86.exe §  The installation wizard appears: §  Click on à Next §  In the screen that appears select the option: (X)         Full server installation including Administration Console Click on à Next §  In the screen that appears select the option: (X)         I accept the terms of the License agreement Click on à Next §  In the screen that appears select the option: (X)         Store updates locally Location:     D:\WSUS\ Click à Next §  In the sreen that appears select the option: (X)         Use an existing database server in this computer Click on à Next Click on à Next §  In the screen that appears select the option: (X)         Create a Windows Server Update Services 3.0 SP1 Web site This is because the “default website” will be used by SCCM 2007 R2 Click on à Next Click on à Next Click on à Finish The configuration wizard for WSUS Server 3.0 SP1 appears automatically   §  Click on à Cancel To stop the wizard. Configuration of WSUS Server will be done from the SCCM Console. 1.6.1 Installation WSUS Server 3.0 SP1 update Kb954960 This update can be downloaded from the Microsoft Website:     Download Start the installation by double clicking on the file:     WSUS_30SP1_KB954960_x86.exe The installation wizard appears: §  Click on à OK  Reboot the Server to initialize components 2. Installation SCCM 2007 SP1 In this part of the article I will describe the installation of Microsoft SCCM 2007 SP1. After this installation the update SCCM 2007 R2 will be installed. Make sure that the server is connected to the internet as during the installation updates are downloaded from the Microsoft Website. §  Place the installation medium for SCCM 2007 SP1. The installation wizard will appear: §  Click on à Run the prerequisite checker §  In the screen that appears enter the following values: (X)         Primary Site SQL Server and instance, if applicable:                                %SCCM Server name% SDK Server:                                                                                      %SCCM Server name% Management point computer FQDN on the internet:   %SCCM Server name%. Domain name Click on à OK If the server passes all pre-requisites for installation of SCCM 2007 R2 close the pre-requisites check and restart the installation 2.2 Installation SCCM 2007 SP1 From the Welcome Screen select the option: §  Click on à Install\Configuration Manager 2007 SP1 The installation wizard appears: §  Click on à Next §  In the screen that appears select the option: (X)         Install a Configuration Manager site server Click on à Next §  From the screen that appears select the option: (X)         I accept the license terms Click on à Next §  From the screen that appears select the option: (X)         Custom Settings Click on à Next §  From the screen that appears select the option: (X)         Primary Site Click on à Next §  From the screen that appears select the option: (X)         No, I don’t want to participate right now Click on à Next §  From the screen that appears enter the license key if none is present and click on à Next §  From the screen that appears enter the following value: Installation path:      D:\Microsoft Configuration Manager Click on à Next §  From the screen that appears enter the following values: Site Code:                          001 Site name:                         %Site name% Click on à Next §  From the screen that appears select the option: (X)         Configuration Manager Mixed Mode Click on à Next §  From the screen that appears select the option: (X)         Software Inventory (X)         Hardware Inventory (X)         Advertised programs (X)         Software Updates (X)         Software metering (X)         Desired configuration management (X)         Remote tools Click on à Next §  From the screen that appears enter the values: SQL  Server and Instance, if applicable:               %SCCM Server name% ConfigMgr site database:                                           SCCMDB Click on à Next §  From the screen that appears enter the correct value if not already entered: Enter the appropriate location for the provider:                              %SCCM Servername% Click on à Next §  From the screen that appears select the following options: (X)         Install a management point %SCCM Server name%.%domain name% Click on à Next §  From the screen that appears select the option: (X)         Use default port (80) Click on à Next §  From the screen that appears select the option: (X)         Check for updates and download newer versions to an alternate path Click on à Next §  From the screen that appears enter the values: Alternate path:                               D:\Temp\SCCM Updates Note:     Make sure this path exists and/or create it in the background before clicking next Click on à Next Updates are downloaded from the Microsoft website. Click on à OK Click on à Next Click on à Begin Install §  After the installation has completed verify if all components have installed succesfully. If so Click on à Next §  Click on à Finish This concludes the installation of SCCM Server 2007 SP1. Now continue with the installation of R2 2.3 Installation SCCM 2007 R2 In this part I will describe the installation of SCCM 2007 R2. The R2 additions of SCCM 2007 is an update to the already installed version SCCM 2007 SP1. Start the installation by double clicking the file: §  Installation media\Splash.hta The installation wizard appears:   §  Click on à Install\Configuration Manager 2007 R2 §  Click on à Next §  From the screen that appears select the option: (X)         I accept the license agreement Click on à Next §  From the screen that appears enter the correct values for: Name: Organization: Enter the license key of not already entered en click on à Next §  From the screen that appears click on àNext §  After the completion of the installation click on à Finish

Inbox Folders in Configuration Manager 2007

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

You can monitor inbox folders on a Microsoft System Center Configuration Manager 2007 site to help troubleshoot problems with different components. This article lists some of the Configuration Manager 2007 inbox folders.
You should periodically examine the Configuration Manager 2007 inbox folders for a backlog of files that wait to be processed. The inbox folders temporarily store files before they are processed to the site database or transferred to another site or site component. A backlog of files can indicate that a component is not running or is experiencing a problem. For example, when the Microsoft SQL Server database runs out of space, a backlog of files occurs until the files are processed to the site database.

Inbox Folders

\Auth

This folder and its subfolders are used by Configuration Manager 2007 sites, management points, and clients. Configuration Manager 2007 uses these folders to temporarily store hardware, software, and discovery data records (.ddr files).

\Auth\dataldr.box

This folder stores .mif files that represent hardware inventory data for Configuration Manager 2007 client computers. This folder also stores IDMIF files for custom architectures. A backlog of files can indicate problems accessing the site database. Examine the status messages for the Inventory Data Loader for possible problems. You can also examine the Dataldr.log file for errors or additional information.

\Auth\dataldr.box\process

This folder stores .mif files that are in process. A backlog of files can indicate problems accessing the site database. Examine the status messages for the Inventory Data Loader for possible problems. You can also examine the Dataldr.log file for errors or additional information.

\Auth\ddm.box

This folder temporarily stores .ddr files after a client or server agent generates a discovery record. Examine the status messages for the Discovery Data Manager (DDM) for possible problems. You can also examine the Ddm.log file for errors or additional information.

\Auth\ddm.box\BAD_DDRS

This folder stores .ddr files that are corrupted. A backlog of files can indicate a network corruption problem or a problem with the DDM. Configuration Manager 2007 automatically deletes .ddr files that are older than 25 hours. Examine the status messages for the Discover Data Manager component for possible problems. You can also examine the Ddm.log file for errors or additional information.

\Auth\sinv.box

This folder stores client software inventory files (.sic and .sid files) that are copied from the management point. A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received. Examine the status messages for the Software Inventory Processor for possible problems. You can also examine the Sinvproc.log file for errors or additional information.

\Auth\sinv.box\Orphans

This folder stores hardware and software inventory that cannot be processed. Inventory files that are moved to this folder are retried later. A backlog of files can indicate problems with specific clients, with management points, or with the network that could cause data corruption. Examine status messages for the Software Inventory Processor for possible problems. You can also examine the Sinvproc.log file for errors or additional information.

\Auth\statesys.box

This folder stores information related to state messages. For more information about state message backlogs, see Troubleshooting State Message Backlogs.

\Compsumm.box

This folder contains component status summary messages from child sites. A backlog of files can indicate that the Component Status Summarizer cannot process the volume of messages. Examine status messages for the Component Status Summarizer for possible problems. You can also examine the Compsumm.log file for errors or additional information.

\Dataldr.box

This folder stores .mif files that represent hardware inventory data for Configuration Manager 2007 client computers. This folder also stores IDMIF files for custom architectures. A backlog of files can indicate problems accessing the Systems Management Server (SMS) database. Examine status messages for the Inventory Data Loader for possible problems. You can also examine the Dataldr.log file for errors or additional information.

\Dataldr.box\Badmifs

This folder stores corrupted .mif files for hardware inventory or custom IDMIF files. A backlog of files can indicate a bad custom MIF file or that a client computer cannot transfer the file correctly. Configuration Manager 2007 automatically deletes all files in the \Badmifs folder that are older than 14 days. Examine status messages for the Inventory Data Loader for possible problems. You can also examine the Dataldr.log file for errors or additional information.

\Ddm.box

This folder temporarily stores discovery data records (.ddr files) after a client or server agent generates a discovery record. Examine status messages for the Discovery Data Manager (DDM) for possible problems. You can also examine the Ddm.log file for errors or additional information.

\Ddm.box\BAD_DDRS

This folder stores .ddr files that are corrupted. A backlog of files can indicate a network corruption problem or a problem with the DDM. Configuration Manager 2007 automatically deletes .ddr files that are older than 25 hours. Examine status messages for the DDM for possible problems. You can also examine the Ddm.log file for errors or additional information.

\Despoolr.box\Receive

This folder stores the data that is received from a child site or a parent site. Typically, files are processed and moved as soon as Configuration Manager 2007 receives the instruction file (.ins file). Examine status messages for the Despooler for possible problems. You can also examine the Despool.log file for errors or additional information.

\Inventry.box

This folder temporarily stores hardware inventory files from management points after clients transfer their hardware inventory to the management point. The Inventory Processor converts the .nhm file to a binary .mif file and then moves the file to the \Dataldr.box folder. Examine status messages for the Inventory Processor for possible problems. You can also examine the Invproc.log file for errors or additional information.

\OfferSum.box

This folder receives summarization messages (.sum files) for advertisements from child sites and processes the files to the site database. A backlog of files can indicate a performance problem that is caused by a large number of messages. Examine status messages for the Offer Status Summarizer for possible problems. You can also examine the Offersum.log file for errors or additional information.

\policypv.box

This folder temporarily stores policy changes for the Configuration Manager 2007 components. Whenever the policy of Configuration Manager 2007 components change, a notification file appears in this inbox, causing the policy provider to regenerate the policies. A backlog of files in the policypv.box folder indicates that the policy provider component is not running. The policy provider component might not be able to read the site control file, or the component cannot write to the database. You can examine the Policypv.log in the \Logs folder on the site server for errors or additional information.

\Replmgr.box\Incoming

This folder receives files from the SMS despooler after processing files from other SMS sites. The SMS Replication Manager determines whether the file is transaction-oriented and then verifies that the serial numbers are correct. If the file is not transaction-oriented, no additional verification is performed. The Replication Manager transfers the file to the recipient component for final processing. Examine status messages for the Replication Manager for possible problems. You can also examine the Replmgr.log file for errors or additional information.

\Replmgr.box\Outbound

This folder temporarily stores files that are destined for another site. This folder also contains three outbox subfolders that correspond to the priority of the files. For example, this folder can contain \High, \Low, and \Normal folders. When the Replication Manager detects files in one of the outbound directories, the Replication Manager waits for additional files before moving the files to the \Process subfolder and then to the \Ready subfolder. Examine status messages for the Replication Manager for possible problems. You can also examine the Replmgr.log file for errors or additional information.

\Replmgr.box\Ready

This folder stores files that are compressed for transmission to remote sites. The files are moved to the Scheduler for transmission. A backlog of files can indicate that the Scheduler is backlogged or is already processing files of the same priority. In this scenario, the Scheduler has to wait for the transmission to complete. Examine status messages for the Replication Manager for possible problems. You can also examine the Replmgr.log file for errors or additional information.

\Schedule.box

This folder stores mini-job files (.job files) that were created by the Replication Manager. The Scheduler turns the .job files into Sender jobs. A backlog of files can indicate that the Sender cannot connect to or cannot transfer data to another site. A backlog can also indicate that the Scheduler cannot process the mini-job files because files are missing from the \Schedule.box\Uid folder. Examine status messages for the Scheduler for possible problems. You can also examine the Sched.log file for errors or additional information.

\Schedule.box\Outboxes

This folder contains the outbox folders for each installed sender. In the sender's outbox folder, you can find send request files (.srq files) or send request status files (.srs files). A backlog of .srq files indicates that the sender cannot process the number of jobs scheduled for that sender or that the sender cannot connect to or transfer data to another site. Examine status messages for the Scheduler for possible problems. You can also examine the Sched.log file for errors or additional information. Also examine the sender log file (Sender.log) for any errors when it tries to communicate to the remote site.

\Schedule.box\Requests

This folder stores the initial send request files before the Scheduler transfers the files to a sender. This folder also stores send request files that are returned when the sender cannot connect to the target site. Examine status messages for the Scheduler for possible problems. You can also examine the Sched.log file for errors or additional information. Also examine the sender log file (Sender.log) for any errors when it tries to communicate to the remote site.

\Schedule.box\Tosend

This folder stores package and instruction files before they are transferred to another site. Package and instruction files start with .p00 and .i00 file name extensions, and the file name extensions increment numerically. The files are removed after the sender has copied the files to the remote site. A backlog of files can indicate that many send requests are not completed or that the Scheduler has not yet deleted the files. Examine status messages for the Scheduler for possible problems. You can also examine the Sched.log file for errors or additional information. Also examine the sender log file (Sender.log) for any errors when it tries to communicate to the remote site.

\Sinv.box

This folder stores client software inventory files (.sic and .sid files) that are copied from the management point. A backlog of files can indicate that the Software Inventory Processor cannot connect to the site database or that too many files were received. Examine status messages for the Software Inventory Processor for possible problems. You can also examine the Sinvproc.log file for errors or additional information.

\Sinv.box\BadSinv

This folder stores corrupted software inventory files. A backlog of files can indicate problems with specific clients, with management points, or with the network, causing data corruption. Make sure that there is not a backlog of zero-byte files in this folder. If zero-byte files exist, manually delete them. Examine status messages for the Software Inventory Processor for possible problems. You can also examine the Sinvproc.log file for errors or additional information.

\SiteStat.Box

This folder receives summarization messages (.sum files) for site system status from child sites before the files are processed to the SMS site database. A backlog of files can indicate a performance problem. Examine status messages for the Site System Status Summarizer for possible problems. You can also examine the Sitestat.log file for errors or additional information.

\Statmgr.box\Futureq

This folder stores status messages (.svf files) from remote systems (clients or site systems) if the date and time of the message is in the future compared to the site server's clock. The Status Manager does not process these messages until the computer clock matches the date and time when the status message was created. The date and time when the status message was created might be different from the date and time stamp of the file. A backlog of files can indicate that some site systems' clocks are not synchronized with the site server. Examine status messages for the Status Manager for possible problems. You can also examine the Statmgr.log file for errors or additional information.

\Statmgr.box\Queue

This folder receives status messages from SMS Executive components on the site server if the in-memory queue is not available. A backlog of files can indicate a problem with the Status Manager or that the component is trying to process too many messages. Examine status messages for the Status Manager for possible problems. You can also examine the Statmgr.log file for errors or additional information.

\Statmgr.box\Retry

This folder stores status messages that could not be processed to the site database. A backlog of files can indicate problems with the connection to the computer that is running SQL Server. Examine status messages for the Status Manager for possible problems. You can also examine the Statmgr.log file for errors or additional information.

\Statmgr.box\Statmsgs

This folder stores status messages from site systems and from Configuration Manager 2007 clients before the messages are processed by the Status Manager. A backlog of files can indicate a problem with the Status Manager or that the Status Manager is trying to process too many messages. Examine status messages for the Status Manager for possible problems. You can also examine the Statmgr.log file for errors or additional information.

\swmproc.box

This folder and its subfolders are used to temporarily store software metering information from Configuration Manager 2007 clients. A backlog of .sum and .sur files can indicate that the Software Metering Processor component cannot connect to the SMS database. Examine the status messages for the Software Metering Processor component for possible problems. You can also examine the Swmproc.log file for errors or additional information.

Query to determine 32 or 64 bit Operating System

SMS_G_System_COMPUTER_SYSTEM.SystemType which returns “x64-based PC”or “X86-based PC”.

Query to find all Windows 7 – x64

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = "x64-based PC" and SMS_G_System_OPERATING_SYSTEM.Caption like "Microsoft Windows 7%"

And the query for Windows 7 -x86
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_OPERATING_SYSTEM on SMS_G_System_OPERATING_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = "X86-based PC" and SMS_G_System_OPERATING_SYSTEM.Caption like "Microsoft Windows 7%"