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 to copy Outlook Personal Folders (PSTs) during XP to Win 7 Migration using USMT 4.0 Hardlinking

 

By default, USMT 4.0 migrates PST files that are linked to a user’s Outlook profile. This is done through internal USMT functions named SetPstPathInMapiStruct and UpdateMvBinaryMapiStruct which is called from within migapp.xml.
What this means is that PST files which are simply stored on the drive but not actually connected to Outlook will not migrate by default when using /i:migapp.cml and /i:migdocs.xml. It’s very possible a user is keeping those around for archive purposes, though. In the example below, the user has a copy of a PST in a c:\psts folder that is not attached to the Outlook profile. They also have a PST created by Outlook Auto-Archive.

In order to migrate those PST files we need to follow these steps:
1.Create a custom XML file
Here is a sample that will gather all PST files from all fixed drives:
<?xml version="1.0" encoding="utf-8" ?>
<migration urlid="http://www.microsoft.com/migration/1.0/migxmlext/pst%22>
  <component type="Documents" context="UserAndSystem">
    <displayName>All PST migrated from all fixed drives, regardless of location</displayName>
    <role role="Data">
      <rules>
        <include>
          <objectSet>
            <script>MigXmlHelper.GenerateDrivePatterns ("* [*.pst]", "Fixed")</script>
          </objectSet>
        </include>
      </rules>
    </role>
  </component>
</migration>
Paste that into Notepad and save as PST.XML into your USMT folder and C:\Windows\System32 folder of the target Windows XP machine

2.Add a command  switch /i:pst.xml in TS variable  “OSDMigrateAdditionalCaptureOptionsscanstate” :

Automatic SCCM Site Discovery Unsuccessful

We have to make sure  that:
1. Extend Active Directory Schema
2. Publish site information in Active Directory
  http://technet.microsoft.com/en-us/library/bb680711.aspx
3. Boundary shouldn’t overlap

SCCM PXE boot - "File not found"

Solution1:
On Server which is hosting WDS service
1: Stop the WDS service.
2: Delete C:\WINDOWS\TEMP\PXEBootFiles\Windows
3: Start the WDS service.

Solution 2:
1. Uninstall PSP role from SCCM console
2. Stop the WDS service
3: Delete C:\WINDOWS\TEMP\PXEBootFiles\Windows
4: Start the WDS service.
5. Install PSP role

BSOD with error 0x0000007B while deploying XP

Most probably this issue comes when we do not use proper storage driver in the task sequence.
Here is resolution that works most of the time:
http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/7a0c4e85-d7c1-4cea-b827-54a72f265895

Solution: Webex is not working on windows 7

After deploying the Windows 7 64 bit Enterprise version we had 1 issue where Webex was not working properly.
It was freezing, very slow and display was poor. One of my colleague found 2 work around to fix the problem:

1.Add one registry key( MTU ) at this path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces

Now look for the folder in which your IP address and other network related info is  visible:

Now create a new “QWORD(64 bit) value”  or “DWORD (32 bit) value, name it  “Mtu” and give it a decimal value of  value of 1500.

 

2.Set the value of  registry key “EnablePMTUDiscovery” (at  HKLM\System\CurrentControlSet\Services\Tcpip\Parameters\) to 1

I hope this will be helpful to someone.

Reboot Coordinator prevents a System Center Configuration Manager 2007 Service Pack 1-based client computer from restarting because it incorrectly concludes that a job is running

System Center Configuration Manager 2007 Service Pack 1 (SP1) will not restart the client computer automatically. It prevents pending important updates from being installed successfully on these computers.
More investigation indicates that the value of the following registry key is greater than 0 on the affected client computers:
HKEY_LOCAL_MACHINE\Software\Microsoft\Sms\Mobile Client\Reboot Management\JobCounter

Microsoft has released a hot fix for that issue.

http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=970635&amp;kbln=en-us

To Manually resolve the issue follow this:

1. Stop the SMS Agent Host (CcmExec.exe) service on a System Center Configuration Manager 2007 SP1 client computer.
2. Location the following registry subkey and change its value to 0:
   HKEY_LOCAL_MACHINE\Software\Microsoft\Sms\Mobile Client\Reboot Management\JobCounter
3. Start the SMS Agent Host (ccmExec.exe) service on the client computer.

More details: http://support.microsoft.com/kb/970635