Windows Admin Blog: ConfigMgr Setup

Showing posts with label ConfigMgr Setup. Show all posts

SCCM 2007 Quiz Application from Microsoft

The System Center Configuration Manager 2007 User Assistance team has created a set of quizzes to help you assess your understanding of the dependencies and requirements for key features of Configuration Manager. These quizzes help to raise your level of awareness of the some of the nuances of these features before you configure and use them.

Read more about SCCM 2007 Quiz Application from Microsoft .

Troubleshooting SCCM Client Push Installation issues

We come across many issues with SCCM client push installation and sometimes it takes lot of time to find a clue about the causes of the issues. Microsoft has recently releases a KB article which covers all possible solutions related to SCCM client push installation.

Here is the URL: http://support.microsoft.com/default.aspx?scid=kb;EN-US;925282

The ConfigMgr Advanced Client rejected the site server signing certificate

Error messgae “The ConfigMgr Advanced Client rejected the site server signing certificate to a trust-related failure (0x800b0109)” is showing up on few clients which are failing to install the certificate from the enterprise root CA.

Solution :
Compare the following registry values between a working and a failing client. If the values are different, replace the values on the bad machine with those from the good machine and re-install the client:

X64 – HKLM\Software\WOW6432Node\Microsoft\CCM\Security
X86 – HKLM\Software\Microsoft\CCM\Security
Keys - AllowedRootCAHashCode, Signing Certificate.

This may be helpful as well: Renewing or Changing the Site Server Signing Certificate

This posting is provided “AS IS” with no warranties and confers no rights.

Upgrading WSUS3.0 SP1 to WSUS 3.0 SP2 on SUP in a SCCM 2007 site

Step 1: Upgrade the Windows Update Agent on client computers

1. Download the latest version of WU Agent from http://support.microsoft.com/kb/949104

2. Create a Software Package from the new installer of WU.

3. Distribute this package to all existing clients in a phased manner. Target computers must be rebooted after installing the new WU agent.

4. Optionally we can create a collection that populate computers with older version of WU agent as mentioned here: http://technet.microsoft.com/en-us/library/bb932139.aspx , so that we get to know how many clients need the latest version of WU agent.

Step 2: Upgrade the WSUS server on Software Update Point

1. Download and install new version of Report Viewer from: http://www.microsoft.com/downloads/details.aspx?familyid=BB196D5D-76C2-4A0E-9458-267D22B6AAC6&displaylang=en

2. Download WSUS3.0 SP2 setup from http://www.microsoft.com/downloads/details.aspx?FamilyID=A206AE20-2695-436C-9578-3403A7D46E40&displaylang=en .

3. Take a snapshot of SUP (INSMS01/HQSMS01) from VMware client.

4. Run WSUS30-KB972455-x86.exe on SUP site system.

Note: Check the WSUSSetup.log file in “C:\DOCUME~1\username\LOCALS~1\Temp\2” folder to see installation progress .

5. At the end of the setup, one configuration wizard will open which needs to closed by clicking “Cancel” button.

6. Restart following services on Site Server:

- SMS_EXECUTIVE

- SMS_SITE_COMPONENT_MANAGER

- Update Services

7. Check the WSUSCtrl.log on the Site Server for the health status of WSUS server (SUP).

The Configuration Manager 2007 SuperFlows

SCCM SuperFlow is dynamic and interactive content model that provides you with detailed steps that you can use to understand and prepare for functions of SCCM 2007 such as OSD, Software update management, Client Installation and Assignment,Backup and Recovery etc.

You can find more details and download the Super Flows here:

Site Mode is unknown

Publish the site in AD as follows:

In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / <site code> - <site name>.
Right-click <site code> - <site name>, and click Properties.
On the Advanced tab of site properties, select the Publish this site in Active Directory Domain Services check box.

Fatal Error : Setup failed to install SMS Provider

Here are some pointers to resolve the issue:

-SPN registration for the SQL server is not done
-you have permission or other Kerberos issues with your machine accounts
-you don't have Domain Admin rights (it was one of the requirements from client) for sccm service account
-SCCM server is not the member of local administrators group of SQL server( in case of remote SQL server)
-SQL server instance may not necessarily be using the default port of 1433.

For more info check this out: http://blogs.technet.com/mkleef/archive/2007/07/19/getting-sccm-2007-rc1-to-install-and-work-properly.aspx

SMS_MPCONTROL_MANAGER error: management point is not resonding to HTTP requests.

Symptom:
After upgrading to Configuration Manager 2007 Service Pack 2, the SMS Agent Host service started to crash and at times failed to start. This was causing failure status messages associated with the Management Point.

Cause:
The SMS Agent Host can impact the Management Point services.

Resolution:
Uninstalled the ConfigMgr client from the Site Server.
Uninstalled the Management Point role and then rebooted the site server.
Reinstalled the Management Point role.
Reinstalled the SMS client.

Programs and Ports Required by Configuration Manager 2007

The following Configuration Manager 2007 features require exceptions to be made on the Windows Firewall:

Queries

If you are running the Configuration Manager console on a computer running Windows Firewall, queries will fail the first time they are run.
After failing to run the first time, the operating system displays a dialog box asking if you want to unblock statview.exe. If you unblock statview.exe, future queries will run without errors. You can also manually add statview.exe to the list of programs and services on the Exceptions tab of the Windows Firewall prior to running a query.

Client Push Installation

In order to successfully use client push to install the Configuration Manager 2007 client, you must add the following as exceptions to the Windows Firewall:

File and Printer Sharing
Windows Management Instrumentation (WMI)

Client Installation using Group Policy

In order to successfully use Group Policy to install the Configuration Manager 2007 client, you must add File and Printer Sharing as an exception to the Windows Firewall.

Client Requests

In order for client computers to communicate with Configuration Manager 2007 site systems, you must add the following as exceptions to the Windows Firewall:
TCP Port 80 (for HTTP communication)
TCP Port 443 (for HTTPS communication)
Network Access Protection In order for client computers to successfully communicate with the system health validator point, you need to allow the following ports:

UDP 67 and UDP 68 for DHCP
TCP 80/443 for IPSec

Remote Control

In order to use the remote tools features of Configuration Manager 2007, you need to allow the following ports:

TCP port 2701
TCP port 2702
TCP port 135

Remote Assistance and Remote Desktop

To enable Remote Assistance to be initiated from the SMS Administrator console, add both the custom program helpsvc.exe and the custom port TCP 135 to the list of permitted programs and services in Windows Firewall on the client computer. Also, Windows Firewall must be configured to permit Remote Assistance and Remote Desktop. If a user initiates a request for Remote Assistance from that computer, Windows Firewall will automatically be configured to permit Remote Assistance and Remote Desktop.

Windows Event Viewer, Windows Performance Monitor and Windows Diagnostics

To enable Windows event viewer, Windows performance monitor and Windows diagnostics to be accessed from the Configuration Manager console, you must enable File and Printer Sharing as an exception on the Windows Firewall.

More info: http://technet.microsoft.com/en-us/library/bb632618.aspx and http://technet.microsoft.com/en-us/library/bb694088.aspx

How Configuration Manager Backup Uses the Volume Shadow Copy Service

In this article Jeff Gilbert from Microsoft has provided very useful information about Volume Shadow Copy feature of Windows Server 2003 and its uses in backing up ConfigMgr database.
Here is the link of the article.