9/9/2011 - The script in this posting has been updated to handle assigning a new machine name during the deployment.
[Today’s post comes from Minfang Lv ]
This post describes how and when you might see duplicate records when you use unknown computer support with Active Directory Delta-Discovery in Configuration Manager 2007 R3, what problems you might see, and some suggested workarounds.
Unknown computer support is an operating system deployment feature that was introduced in Configuration Manager 2007 R2. It allows you to find unmanaged computers so that you can install an operating system on them, and optionally, install the Configuration Manager client:
http://technet.microsoft.com/en-us/library/cc431374.aspx . Active Directory Delta Discovery is a new feature in Configuration Manager 2007 R3 that enhances the discovery capabilities of the product by discovering only new or changed resources in Active Directory Domain Services instead of performing a full discovery cycle: http://technet.microsoft.com/en-us/library/ff977086.aspx .
If you use these two features at the same time, you might see duplicate records for the unknown computer in Configuration Manager database. In this scenario, you will see two records in the Configuration Manager console that have the same name of the computer that installed an operating system by using unknown computer support: One record shows that it is a client and assigned; the other record shows that it is not a client and not assigned.
The Technical Details
When you install an operating system by using unknown computer support, the following processes happen:
If the DDR is created (number 3) after the computer installs (number 4), you won’t see a duplicate record because Configuration Manager has enough information to merge the Active Directory DDR with the computer record. However, if the DDR is created before the computer installs and registers (in the order listed above), Configuration Manager cannot match and merge the two records, which results in the duplicate record.
This problem is a timing issue, which has always existed in the product. However, the introduction of Active Directory Delta Discovery in Configuration Manager 2007 R3 means that you are now more likely to see the duplicate records.
There are two potential issues as a result of this problem:
Use one of the two workarounds for Configuration Manager 2007 R3:
Use the following steps:
A. In the Configuration Manager console, navigate to System Center Configuration Manager / Site Database / Site Management / < site name > / Site Settings / Status Filter Rules .
B. Right-click Status Filter Rules , click New , and then click New Status Filter Rule .
C. On the General page of the New Status Filter Rule Wizard , specify a name for the new status filter rule and configure the following for the message-matching criteria:
D. On the Actions page of the New Status Filter Rule Wizard , specify the following action:
Disclaimer: These are sample scripts that use the Configuration Manager 207 SDK. Make sure that you test your scripts in a test environment before you run them on a production network.
call cscript c:DeleteDuplicatedRecord.vbs %1 %2 %3
-- Minfang Lv