Cumulative Update 1 for Microsoft System Center Service Manager 2010 is available for download at the Microsoft Download website. This cumulative update is a rollup of fixes for System Center Service Manager 2010. This cumulative update is also a prerequisite for Service Manager Authoring Tool 1.0 Release Candidate. Additionally, this cumulative update contains a fix for a problem in which out-of-box workflows are run multiple times.

This cumulative update applies to the following Service Manager components:

• Service Manager Management Server (SM Server)
• Data Warehouse Management Server (DW Server)
• Self-Service Portal
• ServiceManager Console

You can apply this cumulative update to these components. However, if the Self-Service Portal or the Service Manager Console is running on a system that has an English language locale, you do not have to apply this cumulative update on that system. The fixes for the Self-Service Portal and for the Service Manager Console are only for systems that have non-English language locales.

For all the details and a download link see the following Knowledge Base article:

KB983572 - Description of Cumulative Update 1 for System Center Service Manager 2010

J.C. Hornbeck | System Center Knowledge Engineer

Symptom

A package cannot be updated successfully on a Branch DP (BDP) and the Peerdpagent.log shows the following:

Package ABC00001 in state 'DownloadComplete'. 6/9/2010 11:42:55 AM 3800 (0x0ED8)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of PDPHashMismatchEvent
{
ClientID = "GUID:00354A37-DA07-43CA-A8F3-A45203669D2D";
DateTime = "20100609184258.503000+000";
MachineName = "ComputerName";
PackageID = "ABC00001";
ProcessID = 2068;
SiteCode = "ABC";
SourceVersion = 2;
ThreadID = 3384;
};
6/9/2010 11:42:58 AM 3384 (0x0D38)
Successfully submitted event to the Status Agent. 6/9/2010 11:42:58 AM 3384 (0x0D38)
Package ABC00001 in state 'HostingIncomplete'. 6/9/2010 11:42:58 AM 3384 (0x0D38)

Every indication is that this is hash mismatch, however, testing shows that the hash matches, and the directory contents are exactly the same on the Source, DP, and BDP, the only indication of the hash mismatch is in the peerdpagent.log

Also note that the package does complete downloading, even though it shows the PDPHashMismatchEvent and HostingIncomplete status.

Cause

This can occur if there is a trailing backslash on the share name path of the package properties.

Resolution

Remove the trailing back slash on the share name path on the package properties or do not use a trailing back slash during package creation.
If you are changing this after the package has already been created, update the Branch DP and this should resolve this issue. This problem seems to affect only Branch Distribution Points, not regular Distribution Points.

Clifton Hughes | Senior System Center Support Engineer

In a Microsoft Systems Management Server 2003 or Microsoft System Center Configuration Manager 2007 site hierarchy, each site must be able to communicate with its parent site and all of its child sites. This communications capability is one of the features that enables the product to scale to levels necessary to make it an Enterprise-wide solution.

Communication between sites is accomplished by using the Server Message Block (SMB) protocol (TCP/IP port 445) and is independent of the SMS 2003 security mode (Standard Security mode or Advanced Security mode) or the Configuration Manager 2007 site mode (native mode or mixed mode).

For sites to communicate, they must have a connectivity system (LAN protocols, RAS, or SNA Server) installed and configured according to the connectivity system's product documentation on all site servers in the SMS 2003 or Configuration Manager 2007 hierarchy. Then, for each site in the hierarchy, you must configure the site-to-site communications by creating and configuring the required addresses and senders.

SMS 2003 and Configuration Manager 2007 sites communicate using package routing. During package routing, communications are passed up and down a hierarchy from site to site. This means that a site needs addresses only for its parent site and child sites, but not for other upper-level, lower-level, or sibling sites.

Most of the individual SMS 2003 and Configuration Manager components use site-to-site communications to replicate data objects between sites. At times it is necessary to know at their deepest levels the functional details of the components and the data flow paths involved in site-to-site communications in order to effectively troubleshoot other components. This document explains these details and illustrates the data flow paths of these components. This information can help you to resolve issues more quickly and efficiently.

Target Audience

This document is intended for customers who need detailed knowledge in order to trace the replication flow of data objects between sites in SMS 2003 or Configuration Manager 2007.

Click here to download the entire document.

Terry McKinney | System Center Support Escalation Engineer

This one isn't necessarily support related but if any of you are in the Seattle area here's a really cool opportunity for you. 

Microsoft User Research is in need of Seattle area IT Professionals of larger organizations of at least 500 PC’s and 16 servers for a research study.

This study will run Thursday, July 22 through Tuesday, July 27, and will be two hours long on the Microsoft campus in Redmond. For those who participate, we can offer you a choice of Microsoft technical hardware or software in appreciation for your time.

If interested, please respond to uccoord@microsoft.com with the subject of “SMS/SCCM” and the following information:

1.) Name/Phone Number

2.) Job Title/Company

3.) How many PC’s are in your company?

4.) How many servers are in your company?

5.) Do you use SMS 2003 or System Center Configuration Manager 2007 at least weekly?

If you’d like to sign up for future Microsoft User Research studies (especially if outside the Puget Sound area) please visit http://www.microsoft.com/usability/itpro.htm

J.C. Hornbeck | System Center Knowledge Engineer

Symptoms

When using the Opalis Integration Server "Log Purge" functionality either scheduled or directly from the Opalis Integration Server Client via the "Purge Now..." button, the purge operation either times out and does not complete or returns an exception.

Cause

The Log Purge functionality has a hard coded timeout value to complete the execution of the SQL queries that are being called.  If this timeout period expires, then the log purging operation does not complete successfully.

Resolution

Log Purge functionality has three options:

1. Keep last x number of records
2. Keep last y number of days.
3. If records are older than y number of days, keep last x number of records.

These three options dictate how the stored procedure “sp_CustomLogCleanup” is called.  To call the stored procedure in a manner that mimics the Log Purge functionality (but without the hardcoded timeout) you can execute one of the following three scripts in SQL Management Studio where @XEntries is the number of entries to keep and @YDays is the number of days to either keep entries or the number of days to determine when entries should be processed:

Option #1

DECLARE @Completed bit
SET @Completed = 0
WHILE @Completed = 0 EXEC sp_CustomLogCleanup @Completed OUTPUT, @FilterType=1,@XEntries=1000

Option #2

DECLARE @Completed bit
SET @Completed = 0
WHILE @Completed = 0 EXEC sp_CustomLogCleanup @Completed OUTPUT, @FilterType=2,@YDays=7

Option #3

DECLARE @Completed bit
SET @Completed = 0
WHILE @Completed = 0 EXEC sp_CustomLogCleanup @Completed OUTPUT, @FilterType=3,@XEntries=1000,@YDays=7

For more information and all the details of this issue see the following new Knowledge Base article:

KB2290555 - Opalis Integration Server Log Purge times out or returns an exception

J.C. Hornbeck | System Center Knowledge Engineer

Our very own Steve Rachui published another great post over on his blog, this time about using the Windows Server 2008 R2 Direct Access feature to manage Internet based clients of System Center Configuration Manager 2007:

"Do you have internet based clients that you want to manage?  Does the idea of switching to SCCM native mode to manage those client make you nervous?  Do you have Windows 2008 R2 servers in your environment and are the internet systems you want to manage running Windows 7 (Enterprise or Ultimate) or Windows Server 2008 R2?  If you said yes to all of these questions then you might just be interested in taking a look at Direct Access (DA)."

To read Steve's excellent blog post see the following link:

Direct Access – SCCM – Managing internet clients

J.C. Hornbeck | System Center Knowledge Engineer

Looks like the folks on the System Center Essentials product team blog just posted some great information on how to use the Essentials Server Migration Advisor tool to move from an x86 version of System Center Essentials 2007 SP1 to System Center Essentials 2010 without losing any of your data:

You read about the 2010 release and are excited about the virtualization features in the new version. You purchase the 2010 version of SCE and run back to your office to do the install. When you launch the install, you see the support for upgrading your existing Essentials 2007 sp1 install. You starting the upgrade process and before long, you have deployed the new version of Essentials.

You go to add the virtualization component and get a message telling you that your x86 system does not support this component. Luckily you have another server that does meet the system requirements for the Essentials 2010 virtualization component… but you don’t want to lose all the data you have on your existing Essentials server… you just need better hardware and a newer OS.

We have anticipated this scenario and have provided a solution in the resource kit that can be leveraged to solve this issue. In the resource kit, there is a tool called MigrationAdvisor.exe. The migration advisor is a wizard which will allow you to migrate your existing Essentials 2010 data from one server to another server with the same FQDN. Here is how it works…

For all the details see How do I move from SCE2007 on x86 to SCE2010 on x64.

J.C. Hornbeck | System Center Knowledge Engineer

This article outlines the connectivity requirements for the various Opalis Integration Server components to interact with each other.  If firewalls exist between the various components, rules may need to be introduced in your environment in order to allow the components to communicate.

The core components of an Opalis Integration Server implementation are:

• Microsoft SQL Server
• Opalis Integration Server Management Server
• Opalis Integration Server Action Server
• Opalis Integration Server Client
• Opalis Integration Server Operator Console
• Opalis Integration Server Remote Trigger

Microsoft SQL Server

The configured TCP port for the desired Microsoft SQL Server instance must be accessible to the following Opalis Integration Server components:

• Opalis Integration Server Management Server
• Opalis Integration Server Action Server
• Opalis Integration Server Operator Console

By default, Microsoft SQL Server's default instance listens on TCP port 1433 however this can be changed by following the instructions in the Knowledge Base article below:

823938  How to configure an instance of SQL Server to listen on a specific TCP port or dynamic port

Opalis Integration Server Management Server

The Opalis Integration Server Management Server is a DCOM server which is exposed through the normal Windows Remote Procedure Call (RPC) interface.  This will require that TCP port 135 and dynamic ephemeral ports are accessible by the following Opalis Integration Server components:

• Opalis Integration Server Client

Remote Procedure Call (RPC) can be configured to limit the number of ephemeral ports that are exposed for the purposes of working with firewalls by leveraging the following Knowledge Base article:

154596  How to configure RPC dynamic port allocation to work with firewalls

Opalis Integration Server Operator Console

The Opalis Integration Server Operator Console is a web server that by default listens on TCP port 5314 which must be accessible by the following Opalis Integration Server components:

• Opalis Integration Server Remote Trigger

• Web Clients (e.g. Microsoft Internet Explorer)

Deploying Opalis Integration Server Components

Using the Opalis Integration Server Deployment Manager that is installed with the Opalis Integration Server Management Server requires the ability to access the computer where the Opalis Integration Server component(s) are to be installed via SMB/CIFS.  As a result, TCP ports 135, 139 and 445 must be accessible on the target computer from the Opalis Integration Server Management Server.

For the latest information see the following Knowledge Base article:

KB2299893 - Overview of Opalis Integration Server connectivity requirements

J.C. Hornbeck | System Center Knowledge Engineer

When using System Center Configuration Manager 2007 some clients may be assigned to the incorrect sitecode.  You may also see entries similar to those below in the locationservices.log file:

DhcpGetOriginalSubnetMask entry point not supported.

Current AD site of machine is ADSite1

This client might be within the boundaries of more than one site - AD SiteCode search matched 2 entries

The client will be assigned to the first valid site

LSGetAssignedSiteFromAD : Trying to Assign to the Site <P04>

LSVerifySiteVersion : Verifying Site Version for <P04>

LSGetSiteVersionFromAD : Successfully retrieved version '4.00.6221.0000' for site 'P04'

LSVerifySiteVersion : Verified Client Version '4.00.6221.1000' is not greater than Site Version '4.00.6221.0000'. Client can be assigned to site <P04>.

Executing Task LSRefreshLocationsTask

Note that in the example above, the client should have been assigned to site P01 but was instead assigned to site P04.

Cause

This can occur if Active Directory references more than one site with the same site boundary. 

Resolution

Remove or correct the site that contains objects using the same boundaries.  To identify sites using the same boundaries, run ldifde -f output.txt from a command prompt and search the text file for the related boundary (ADSite1 in the example above).

More Information

In many cases this situation occurs because a site is deleted instead of being deinstalled.  Doing this leaves the AD objects behind which results in a duplicate boundary if another site is later added that contains the boundary used in the previously deleted site.

How to Verify Site Information is Published to Active Directory Domain Services: http://technet.microsoft.com/en-us/library/bb693614.aspx

How to Publish Configuration Manager Site Information to Active Directory Domain Services: http://technet.microsoft.com/en-us/library/bb680711.aspx

How to Stop Publishing Site Information to Active Directory Domain Services: http://technet.microsoft.com/en-us/library/bb680429.aspx

For the latest version of this article see the following Knowledge Base article:

KB2002059 - Some clients may be assigned to the wrong sitecode in System Center Configuration Manager 2007

J.C. Hornbeck | System Center Knowledge Engineer

Looks like the folks on the System Center Essentials product team blog just posted some great information on how to use the UpdatePublisherCert.exe tool to replace the existing System Center Essentials 2007 (SCE 2007) certificate with a new certificate for use with System Center Essentials 2010 (SCE 2010).  If you are planning an upgrade any time soon you'll want to give this one a quick read:

Essentials 2010  uses a certificate for signing locally published content. The released version of System Center Essentials 2010 is designed to use an updated type of certificate. Use the UpdatePublisherCert.exe tool to replace the existing certificate with a new certificate.

The UpdatePublisherCert.exe tool performs the following tasks:

1. Save the current policy configuration

2. Uninstall the current policy

3. Delete certificates from the certificate store

4. Delete certificates from the system

5. Reconfigure the policy and generate new certificates

6. Resign all locally published software and update packages.

To continue reading see How to update Essentials certificates

J.C. Hornbeck | System Center Knowledge Engineer

By default, the "Enable BitLocker" task of a System Center Configuration Manager 2007 Task Sequence defaults to an encryption method and cipher strength of "AES 128-bit with Diffuser". However, the "Enable BitLocker" task does not have any way of changing from the default encryption method and cipher strength to any of the other options:

AES 256-bit with Diffuser
AES 128-bit
AES 256-bit

Normally the BitLocker encryption method and cipher strength is controlled by Group Policy. This policy can be found in the Group Policy Editor (gpedit.msc) under the following node:

Computer Configuration --> Administrative Templates --> Windows Components --> BitLocker Drive Encryption

and under the following policy:

Choose drive encryption method and cipher strength (Windows 7 and Windows Server 2008 R2)
Configure encryption method (Windows Vista and Windows Server 2008)

The default setting in Windows for the BitLocker encryption method and cipher strength is "AES 128-bit with Diffuser". This setting can be changed using the above policy, however when running a ConfigMgr 2007 Task Sequence a policy that changes the default encryption method and cipher strength may have not been applied by the time that the "Enable BitLocker" task runs.

To ensure that the "Enable BitLocker" task encrypts the drive at the proper encryption method and cipher strength, add a "Run Command Line" task to the Task Sequence that sets the BitLocker encryption method and cipher strength correctly via a registry entry:

1. In the ConfigMgr 2007 Admin console, navigate to the "Computer Management" --> "Operating System Deployment" --> "Task Sequences" node.

2. Right click on the affected Task Sequence and choose "Edit".

3. Click on the task immediately BEFORE the "Enable BitLocker" task.

4. Click on "Add" --> "General" --> "Run Command Line". This should add a "Run Command Line" task immediately before the "Enable BitLocker" task.

5. In the newly created "Run Command Line" task:

• In the "Name:" text box, enter:

Set BitLocker Encryption Method and Cipher Strength

• In the "Command line:" text box, enter in one of the following registry commands depending on the encryption method and cipher strength desired:

AES 256-bit with Diffuser
reg add HKLM\SOFTWARE\Policies\Microsoft\FVE /v EncryptionMethod  /t REG_DWORD /d 2 /f

AES 128-bit
reg add HKLM\SOFTWARE\Policies\Microsoft\FVE /v EncryptionMethod  /t REG_DWORD /d 3 /f

AES 256-bit
reg add HKLM\SOFTWARE\Policies\Microsoft\FVE /v EncryptionMethod  /t REG_DWORD /d 4 /f

6. Click on the "OK" or "Apply" button to save the Task Sequence.

After the "Enable BitLocker" step has run and BitLocker has been enabled, the encryption method and cipher strength applied can be checked by running the following command at an elevated command prompt after the Task Sequence has completed:

Manage-bde –status <Drive_Letter>

where <Drive_Letter> is the drive letter of the disk where BitLocker was enabled (without the brackets <>). For example, to check the encryption method and cipher strength on the C: drive, run the command:

Manage-bde –status c:

The above command can also be used to check the current progress of the drive encryption and/or if the encryption has been completed on the drive.

Frank Rojas | System Center Support Escalation Engineer

When attempting to add an Install Software item in a System Center Configuration Manager 2007 Task Sequence, the Program drop-down list under Install a single application may be empty.  Clicking Apply results in a Task Sequence Editor Please select a program dialog and the item cannot be saved.

This behavior may occur if Allow users to interact with this program is selected on the Environment tab of the program's properties dialog.  Since the Task Sequence always executes in the system context, it is not possible to use this option.  In some rare cases, there may be problems with the objects properties in WMI that may need to be modified directly as well.  The resolution section below covers both cases.

Resolution

In most cases, unchecking Allow users to interact with this program from the program's properties dialog will resolve this issue.  This setting is located in the Configuration Manager Console under Site Database\Computer Management\Software Distribution\Packages\<Package Name>\Programs\<Program Name>\Properties.  Once the selection has been unchecked, return to the Task Sequence editor and click on Browse... to re-select the package.

If unchecking the Allow users to interact with this program option does not resolve the issue, or if the setting is already unchecked, you may need to manually edit the object for the package in WMI.  Use these steps to resolve this issue:

1. Click Start, Run, then type wbemtest.
2. Click Connect and type root\sms\site_<SITECODE> in the Namespace field (where <SITECODE> is the 3-letter site code of your site).  Click Connect.
3. Click on Query... and type select * from SMS_Program.  Click Apply.
4. In the Query Result dialog, double-click the entry for the package you are trying to add.
5. In the Properties list, locate ProgramFlags  and double-click on it to bring up the editor.
6. Record the current value and then replace it with 135307264.
7. Click on Save Property.  This will close the dialog.
8. Click on Save Object to close the package entry.
9. In the Task Sequence editor, click on the Browse... button, select any other package, click OK, then click Browse... again and navigate to the package you wish to deploy.

Mark Stanfill | System Center Senior Support Escalation Engineer

After completing this lab, you will be better able to install and configure System Center Configuration Manager 2007 Dashboard, create and Customize Data sets, and control access and configure Data Displays in System Center Configuration Manager Dashboard.

For all the details and to register click here.

J.C. Hornbeck | System Center Knowledge Engineer

When using System Center Essentials 2010, the Web recorder bar does may display in Internet Explorer when attempting to record a browser session as part of creating a Web Application monitor.  This can happen if Internet Explorer is opening in 32-bit (x86) mode rather than 64-bit (x64) mode.

To work around this issue you can follow these steps:

1. Open the web application editor.

2. Hit “Start Capture”.  This will launch Internet Explorer in 32 bit mode.  Close this browser.

3. From the start menu, run Internet Explorer (64-bit).

4. The web recorder will appear.  If not, choose View -> Explorer Bars -> Web Recorder.

For more information see the following new Knowledge Base article:

KB2379524 - The Web recorder bar does not display in Internet Explorer when attempting to record a browser session as part of creating a Web Application monitor in System Center Essentials 2010

J.C. Hornbeck | System Center Knowledge Engineer

Steve Rachui has another great Configuration Manager post over on his blog, this time about how to create a web page that allows OSD users to setup imaging themselves without having to use the System Center Configuration Manager 2007 console:

OSD is a powerful imaging tool but setting up systems to be imaged may require a user have access to the SCCM console.  This often means that the SCCM staff gets assigned the task of imaging.  Wouldn’t it be cool if the OSD users could setup imaging themselves without having to use the SCCM console?  Yeah, I thought so too. 

I have just completed building a sample web page that allows users to choose their own imaging scenarios. 

For all the details see OS Imaging via Web Page.

J.C. Hornbeck | System Center Knowledge Engineer

Coming from the System Center Configuration Manager documentation team is news that the Configuration Manager documentation library (http://technet.microsoft.com/en-us/library/bb680651.aspx) has been updated on the Web and the latest content on the Web has Updated: August 1, 2010 at the top of the topic.

This month they've been focusing on the Configuration Manager 2007 R3 content including an update to the existing documentation that clarifies a support statement around branch distribution points.  They've also been republishing topics that contain links that don't work and "Note" or "Important" icons that don't display correctly. 

For all the details see Announcement: Configuration Manager Documentation Library Update for August 2010.

J.C. Hornbeck | System Center Knowledge Engineer

Microsoft Configuration Manager 2007 setup on Windows Server 2008 may fail to proceed with the following error message:

Web-based Distributed Authoring and Versioning (WebDAV) is required for the management point and distribution point site system roles. If you have selected to install a site role requiring WebDAV, and it is not enabled, this rule will fail. Web-based Distributed Authoring and Versioning (WebDAV) is not enabled and/or IIS 6 WMI compatibility component for IIS7 is not installed on the computer specified for management point installation or setup was unable to verify remote IIS settings because IIS common components were not installed on the site server computer. ConfigMgr requires WebDAV to be installed and enabled in Internet Information Services (IIS) for management point site systems. Setup cannot continue.

This occurs even if the steps from How to Configure Windows Server 2008 for Site Systems article has been followed.

This can occur if WebDAV has been configured at the global level rather than at the default web site level.  Even if the settings are the same at both levels, setup requires that only the individual web site settings are configured.  Configuring the same settings at both levels will not allow setup to proceed, since global settings in this case are not written to the <webdav> section of the default web site in ApplicationHost.config (since they are effectively the same, there is no reason to write them twice).

To resolve this issue and allow ConfigMgr 2007 setup to complete follow the steps below:

1. Click on Start, click on All Programs, Click on Administrative Tools and then click on Internet Information Services (IIS) Manager.
2. Highlight the entry on the left-hand pane for your servername (SERVERNAME (DOMAIN\user)).
3. Double-click on WebDAV Authoring Rules.
4. Delete any rules that appear.
5. Highlight your Default Web Site (or ConfigMgr 2007 web site) and edit the WebDAV settings at that level as explained in this article:  http://technet.microsoft.com/en-us/library/cc431377.aspx

For all the details and the latest version of this document please see the following new Knowledge Base article:

KB2378924 -  System Center Configuration Manager 2007 prerequisites checker reports WebDAV settings are incorrect

J.C. Hornbeck | System Center Knowledge Engineer

Microsoft System Center Configuration Manager 2007 backups may fail if other VSS-aware backup software is scheduled to run concurrently.  In this scenario, the Smsbkup.log will show entries similar to the following:

Deleting E:\SMSbackup\SiteServer\SMSServer\inboxes\auth\statesys.box\incoming, FAILED, Win32 Error = 145
Deleting E:\SMSBackup\SiteServer\SMSServer\inboxes\auth\ddm.box, FAILED, Win32 Error = 145
Deleting E:\SCCMBackup\Backup, FAILED, Win32 Error = 145
Failed to delete the contents of the backup folder. Error Code = 0x0 SMS_SITE_BACKUP
Error: Deleting the existing files in the backup location failed... SMS_SITE_BACKUP
SMS site backup failed. Please see previous errors. SMS_SITE_BACKUP
SMS site backup service is stopping. SMS_SITE_BACKUP

These errors can occur if the Volume Shadow Copy Service (VSS) provider is in use by another process.  Configuration Manager Backup expects to have exclusive access to these resources when performing a backup.

To prevent these errors, configure Configuration Manager Backup to start at a time outside the window for other backup jobs on the server.  The schedule for this can be found in the Configuration Manager Console under Site Management -> Site Code -> Site Settings -> Site Maintenance -> Tasks -> Backup ConfigMgr Site Server.

For all the details and the latest version of this document please see the following new Knowledge Base article:

KB2387913 - System Center Configuration Manager 2007 backups fail with Win32 Error = 145

J.C. Hornbeck | System Center Knowledge Engineer

Just a quick heads up that our very own System Center Configuration Manager Support Engineer Vinay Pamnani recently published a great post about how to add a known/unknown computer to a specified collection during OS Deployment.  If you haven't seen you'll probably want to check it out:

Have you ever wondered why a ConfigMgr client takes a long time to run the advertised programs after you deploy this client using ConfigMgr OSD? Well, this is because as soon as the machine is imaged, it gets added to the ‘All Systems’ collection and gets the advertisements/policies that are targeted to the All Systems collection. But what if your advertisements are not targeted to the default All Systems collection, and instead are targeted to a custom query based collection? In that case, the newly imaged machine doesn’t get added to the custom collection until it sends the inventory AND the collection updates based on its schedule and finds the machines that fulfill the query condition to add the machine(s) to the collection, and in turn triggering the creation of policies for these clients. Until this happens, there are no Advertisements for this newly imaged client to run(unless of course, they were targeted to the All Systems collection). This is why you may notice a delay of up to 24 hours or more until you see the newly imaged clients processing all the Advertisements that you expect them to execute.

To read more and see the solution visit the following:

http://blogs.msdn.com/b/vinpa/archive/2010/09/01/how-to-add-a-known-unknown-computer-to-a-specified-collection-during-os-deployment.aspx

J.C. Hornbeck | System Center Knowledge Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

When attempting to install a Configuration Manager 2007 Management Point (MP) on Windows Server 2008, the install may fail with the following errors:

MPMSI.LOG
[13:52:07] Enabling BITS
[13:52:08] @@ERR:25006
MSI (s) (DC!FC) [13:52:08:085]: Product: SMS Management Point -- Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming
The error code is 800CC801

Error 25006. Setup was unable to create the Internet virtual directory CCM_Incoming
The error code is 800CC801
CustomAction CcmCreateIISVirtualDirectories returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

MPSETUP.LOG
<08-27-2010 13:43:26> Installing E:\Program Files (x86)\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="E:\Program Files (x86)\SMS_CCM" CCMSERVERDATAROOT="E:\Program Files (x86)\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<08-27-2010 13:51:30> mp.msi exited with return code: 1603
<08-27-2010 13:51:30> Backing up E:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log to E:\Program Files (x86)\Microsoft Configuration Manager\logs\mpMSI.log.LastError
<08-27-2010 13:51:30> Fatal MSI Error - mp.msi could not be installed.

Note that the failures are observed on Standard, Enterprise, x86, and x64 versions.  The failures are observed in the following circumstances:

• After performing a site repair of a site server running on Windows 2008 with a local MP already installed
• Initial install of an MP on a machine running Windows 2008
• After removing and attempting to reinstall an MP on a machine running Windows 2008

Resolution

As of right now, the easiest way to resolve this issue is to remove and reinstall the BITS component.  If the ConfigMgr 2007 Management Point role was already installed then it will also be necessary to remove and reinstall that role once you've done the same with BITS.

Hope this helps,

Terry McKinney | System Center Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis