Post Setup SCCM 2007 Configuration Check List

Here is the Microsoft recommended Post installation check lists for Native & Mixed Mode

 

 

Post Setup Configuration Checklist - Mixed Mode
Task
Configure a management point
Note
The management point role can be assigned during setup, or assigned post setup. Only one default management point is required for each Configuration Manager 2007 primary site hosting intranet based clients.
Configure Site Boundaries
Determine if you need a server locator point
Configure your fallback status point and reporting point
Install Configuration Manager 2007 Clients
Configure Configuration Manager Client Agent Settings
Post Setup Configuration Checklist - Native Mode
Task
Configure a management point
Note
The management point role can be assigned during setup, or assigned post setup. Only one default management point is required for each Configuration Manager 2007 primary site hosting intranet based clients.
Configure Site Boundaries
Deploy a Web server certificate to your site systems
Determine if you need a server locator point
Configure your fallback status point and reporting point
Deploy authentication certificates to all clients and the management point
Install Configuration Manager 2007 Clients
Configure Configuration Manager Client Agent Settings

 

Enjoy,

Paddy

Decommissioning Sites Work Flow

Decommissioning Sites Work Flow

 

 

 

Enjoy,

Paddy

Predefined Maintenance Task Schedules

Predefined Maintenance Task Schedules

The following table displays the predefined maintenance tasks and their default schedules.

Maintenance Task	Enabled by default	Default schedule
Backup ConfigMgr Site Server	No	None.
Clear Install Flag	No	Sunday between midnight and 5:00 A.M.
Delete Aged Client Access License Data	No	Saturday between midnight and 5:00 A.M.
Delete Aged Collected Files	Yes	Saturday between midnight and 5:00 A.M.
Delete Aged Computer Association Data	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Configuration Management Data	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Discovery Data	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Inventory History	Yes	Saturday, between midnight and 5:00 A.M.
Delete Aged Software Metering Data	Yes	Daily, between midnight and 5:00 A.M.
Delete Aged Software Metering Summary Data	Yes	Sunday between midnight and 5:00 A.M.
Delete Aged Status Messages	Yes	Daily, between midnight and 5:00 A.M.
Delete Inactive Client Discovery	No	Saturday between midnight and 5:00 A.M.
Delete Obsolete Client Discovery Data	No	Saturday between midnight and 5:00 A.M.
Monitor Keys	Yes	Sunday, between midnight and 5:00 A.M.
Rebuild Indexes	Yes	Sunday, between midnight and 5:00 A.M.
Summarize Client Access License Weekly Usage Data	No	Saturday between midnight and 5:00 A.M.
Summarize Software Metering File Usage Data	Yes	Daily, between midnight and 5:00 A.M.
Summarize Software Metering Monthly Usage Data	Yes	Daily, between midnight and 5:00 A.M.

 

 

Enjoy,

Paddy

WQL Query list reboot date timestamp X Days

WQL Query to list all of the machines that have a reboot date timestamp of more than x Day's

Select

Sms_R_System.Name,

Sms_G_System_Operating_System.LastBootUpTime

From SMS_R_System

Inner Join Sms_G_System_Operating_System

On Sms_G_System_Operating_System.ResourceId = Sms_R_System.ResourceId

Where DatePart(DD,Sms_G_System_Operating_System.LastBootUpTime) >= X

Enjoy,

Paddy

Move the SMS Provider

How to Move the SMS Provider

The SMS Provider is a component of Configuration Manager 2007 primary sites and is used by Configuration Manager consoles to access site database information from the SQL Server hosting the site database.

The SMS Provider is a dynamic-link library file (smsprov.dll) and is installed or moved by running Configuration Manager 2007 Setup. You can install the SMS Provider on the primary site server computer, the computer hosting the site database server, or another computer not hosting the primary site or site database. A server class operating system is required to install the SMS Provider on a computer other than the site server or site database server computers.

Important
Installing the SMS Provider on a virtual SQL Server cluster instance is not supported. You can move the SMS Provider after setup has completed to a different server computer system by starting Configuration Manager Setup from the Start menu (if the SMS Provider is installed on the primary site server) or from the Configuration Manager installation media.

To move the SMS Provider using the Start menu

1. Close any open Configuration Manager console connections to the site server.

2. On the primary site server computer, click Start, click All Programs, click Microsoft System Center, click Configuration Manager 2007, and click ConfigMgr Setup, or navigate to the .\bin\i386 directory of the Configuration Manager 2007 installation media and double-click Setup.exe.

3. Click Next on the Configuration Manager Setup Wizard Welcome page.

4. Click Perform site maintenance or reset this site on the Configuration Manager Setup Wizard Setup Options page.

5. Select Modify SMS Provider configuration on the Configuration Manager Setup Wizard Site Maintenance page.

6. Enter the appropriate installation location for the SMS Provider on the Configuration Manager Setup Wizard SMS Provider Settings Modification page.

7. Configuration Manager Setup performs the SMS Provider reinstallation process.

Enjoy,

Paddy

How to Upgrade Clients Using Software Distribution in Configuration Manager

How to Upgrade Clients Using Software Distribution in Configuration Manager

You can use Configuration Manager 2007 software distribution to upgrade the client software on computers in your enterprise. A package definition file is supplied with Configuration Manager 2007 which populates the package properties with commonly used values. You can customize the behavior of the client installation by specifying additional command line properties.

Note
Software distribution can only be used to upgrade the client software. It cannot be used for new client installations.

When you have created the package, you can use software distribution to advertise it to collections of computers on your Configuration Manager 2007 site.

Important

Microsoft Background Intelligent Transfer Service (BITS) is a prerequisite for client installation. When BITS is installed on client computers a restart is generally required. If BITS is being installed during client installation (by CCMSetup.exe), then the client installation will not complete until the computer is restarted. For this reason, it is recommended that you pre-deploy BITS on client computers before you install or upgrade the Configuration Manager 2007 client.

Use this procedure to create a Configuration Manager 2007 package which can be distributed to computers to upgrade the client software:

To create a Configuration Manager Package containing the client software:

1. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Software Distribution / Packages.

2. Right click the Packages node, click New and then click Package From Definition.

3. On the Welcome page of the Create Package from Definition Wizard, click Next to Continue.

4. On the Package Definition page of the Create Package from Definition Wizard, select Microsoft from the Publisher drop-down list, select Configuration Manager Client Upgrade from the Package Definition list and then click Next.

5. On the Source Files page of the Create Package from Definition Wizard, select Always obtain files from a source directory and then click Next.

6. On the Source Directory page of the Create Package from Definition Wizard, select Network path (UNC Name) and enter the network path to the computer and folder containing the Configuration Manager 2007 client installation files.

   Note
   The computer on which the Configuration Manager 2007 advertisement runs must have access to this network location. If it does not have access then the installation will fail.

7. To continue, click Next.

8. Click Finish to close the Create Package from Definition Wizard.

9. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Computer Management / Software Distribution / Packages / Microsoft Configuration Manager Client Upgrade 4.0 ALL / Programs.

10. Right-click the program Advanced Client Silent Upgrade and then click Properties.

11. In the Advanced Client Silent Upgrade Dialog box, make any required changes or additions to the setup properties in the Command Line field and then click OK. The default installation properties are /noservice SMSSITECODE=AUTO.

12. Copy the package to all required Configuration Manager 2007 distribution points.

    Note
    You should specify the name of the site fallback status point if one has been defined using the client.msi property FSP=<fallback status point name>. For a list of all installation properties, see About Configuration Manager Client Installation Properties.

    Important
    If any installation properties are specified after the CCMSetup.exe command, the client will not search Active Directory for additional installation properties.   Enjoy, PaddyMaddy

How to Manually Publish the Default Management Point to DNS

Publish the default management point to DNS

 

If your DNS servers do not support automatic updates but do support service location records, and you want to publish the Configuration Manager 2007 default management point to DNS, you can manually publish the default management point. To accomplish this, you must manually specify the service location resource record (SRV RR) in DNS.

Configuration Manager 2007 supports RFC 2782 for service location records, which have the following format:

_Service._Proto.Name TTL Class SRV Priority Weight Port Target

For guidance on entering this DNS record for a site's default management point, follow this procedure.

To manually publish the default management point to DNS

1. In the Configuration Manager console, specify the intranet FQDNs of site systems.

2. In DNS, configure the DNS zone for the site's default management point, and enter host (A) records for the intranet FQDNs of the site systems.

3. Enter an SRV record with the following fields:

   • _Service: Enter _mssms_mp_<sitecode>, where <sitecode> is the management point's site code.
     
   • ._Proto: Specify ._tcp.
     
   • .Name: Enter the DNS suffix of the management point, for example contoso.com.
     
   • TTL: Enter 14400, which is four hours.
     
   • Class: Specify IN (in accordance with RFC 1035).
     
   • Priority: This field is not used because there is only one management point published for each site.
     
   • Weight: This field is not used because there is only one management point published for each site.
     
   • Port: Enter the port configured for Configuration Manager 2007 client requests, for example 80 for a mixed mode site and 443 for a native mode site.
     
   • Target: Enter the intranet fully qualified domain name specified for the site system configured with the default management point site role.

Enjoy,

PaddyMaddy