The Realm of the Verbal Processor

Jarvis's Ramblings

Unknown Computer Bug–Final Update

Over the weekend I got a final update on the Unknown Computer “bug” in Configuration Manager 2012 that I wrote about recently. This time the update came from John Vintzel who for those who don’t already know him is a Senior Program Manager on the Configuration Manager product team. Basic gist of the update is that they will evaluate a change in this behavior for a future release.

In my opinion (which based on conversations I’ve had I know is shared by many others), this is a necessary change. There should not be a requirement to delete an object when a system doesn’t even begin the task sequence…or when it fails early in the process. A few options for how this could be changed:

  1. Don’t create the Unknown object at all. (I’m guessing there is a reason behind why it exists though.)
  2. Create the object after the system becomes a manageable object. (probably the same as #1 though)
  3. Have logic built into the task sequence process that automatically removed the “unknown” object from the database if the Task Sequence fails before the system becomes a manageable object.

May 7, 2012 - Posted by | ConfigMgr 2012

1 Comment »

  1. I wrote a powershell script to delete these. You could use task manager to schedule it to run every 5 – 10 mins

    $sitename = “”
    $computername = “unknown”
    $resID = Get-WmiObject -query “select resourceID from sms_r_system where name like `’$computername`'” -Namespace “root\sms\site_$sitename”
    $resID | measure-object
    $resID | foreach-object {
    $comp = [wmi]”\\.\root\sms\site_$($sitename):sms_r_system.resourceID=$($_.ResourceId)”


    Comment by mrmogz | December 21, 2012

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: