Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, April 18, 2012 7:55 AM
When re-deploying a workstation that has failed, the "Unknown" workstation in "Devices" just stays there.
In other words it is now "known" (as the instance "Unknown"), but not a member of any collection, so it will not be offered any installation.
WHAT to do?
To reproduce the problem, add a TS to "All Unknown Computers".
Boot up an unknown PC and just select the TS to use. Then the "Unknown" device will appear in Devices.
Turn off the PC and try PXE booting it again... NoGo.
Now the reason I ask is that we will have maby 20-60 deployments per day.
Of course we can delete it manually but the technicians actually deploying, does not have access to the SCCM concole and I would very much appreciate if I don't have to go in every other day to manually delete "Unknown" devices.
Also the tecs will start hating the system right away if they have to wait a number of hours every time something fails....
Any ideas will be appreciated enormously :-)
Kind Regards
Thomas Ehler
Systems Administrator
Client platform
Aarhus University
Denmark
All replies (13)
Friday, April 20, 2012 5:25 AM | 5 votes
Thomas,
Workarround:
Add a query rule to the Collection that grabs new computers where the System Resource “Unknown Computer” property = “1”
Source: http://verbalprocessor.com/2012/04/06/unknown-computer-bug-in-configuration-manager-2012/
Ronni Pedersen | Configuration Manager MVP | Blog: http://www.ronnipedersen.com/ | Twitter @ronnipedersen
Monday, April 23, 2012 8:40 AM
yeah, this is really annoying...
surely because the error messages states: PXE-E53 no boot filename received
I will check if this can be solved via a maintenance task or something
hope to see a fix quickly
Monday, April 23, 2012 7:28 PM
An option that I used in 2007 is to advertise the task sequence to all systems but limit it to run only on a specified platform that you do not have in your environment. This is a little risky because if you forget to limit it, you can cause issues. But, it definitly worked when having the unknown/known computer OSD issue. Using this method, you can reimage any computer. It keeps all computers available for OSD from PXE and boot media. Make sure to password protect both the boot media and PXE! I have not done this yet in ConfigMgr 2012.
Wednesday, April 25, 2012 3:08 PM
I'm experincing the same issue. As i was typing my response here i came across this article explaining it.
The Unknown computer entries are from your OSD, when using uknown computer support the client is named unknown until Windows is setup and have the correct name. You can identofy these objects by using the MAC address.
Try changing the setting to approve all computers, as they during OSD connects without being members in the domain to start with, can also have with DNS suffix in DHCP, DNS Scaveneging e.t.c, I have seen this before.
Regards,
Jörgen
Wednesday, May 23, 2012 5:18 PM
Hello everyone,
I usually deploy OS using All Unknown Computers. But I just found that the collect is empty now. It should have x86 and x64 unknow computers inside but I dont know why they are gone. I searched somewhere and I found a query to get back:
select SMS_R_UNKNOWNSYSTEM.ResourceID,SMS_R_UNKNOWNSYSTEM.ResourceType,SMS_R_UNKNOWNSYSTEM.Name,SMS_R_UNKNOWNSYSTEM.Name,SMS_R_UNKNOWNSYSTEM.Name from SMS_R_UnknownSystem where Decommissioned = "0"
I tried to create query rule and put this in and update, refresh some times but nothing happen...
How can I get back the built in All Unknown Computers collect?
Thanks a lot everyone
Le Nhut Minh PwC Vietname Limited.
Monday, September 24, 2012 5:58 PM
It is a bug
http://www.windows-noob.com/forums/index.php?/topic/6189-unknown-computer-device-created-during-osd/
Wednesday, September 26, 2012 7:45 AM
I got around this by adding dynamic query to OSD collection, which adds all new unknow records to my OSD collection. All Task Sequences are deployed to OSD collection.
Thursday, October 11, 2012 3:56 PM
An option that I used in 2007 is to advertise the task sequence to all systems but limit it to run only on a specified platform that you do not have in your environment. This is a little risky because if you forget to limit it, you can cause issues. But, it definitly worked when having the unknown/known computer OSD issue. Using this method, you can reimage any computer. It keeps all computers available for OSD from PXE and boot media.
Mavtech can you please explain specifically how you did this?
Thursday, October 11, 2012 6:35 PM
An option that I used in 2007 is to advertise the task sequence to all systems but limit it to run only on a specified platform that you do not have in your environment. This is a little risky because if you forget to limit it, you can cause issues. But, it definitly worked when having the unknown/known computer OSD issue. Using this method, you can reimage any computer. It keeps all computers available for OSD from PXE and boot media.
Mavtech can you please explain specifically how you did this?
I recently did this in 2012. It works the same the same way as in 2007. Right click the Task Sequence and go to Advanced. In the bottom pane, select Run only on the specified client platforms. Then, select an OS that does not exist in your environment. In 2007, we would select Windows 2000. In 2012, most companies can use Vista. Once this is set, deploy the TS out to All Systems. All of your systems will see the policy. But, they will not let it be available due to this restriction. It will still be listed in the TS Manager using boot media and PXE. This method works great. But, if you deploy a TS without limiting it, your users will get an OSD pop up.
Thursday, November 1, 2012 8:27 PM
Can you please share a syntax of that query?
Thank you.
Sunday, November 4, 2012 7:13 PM
Im experiencing the same issue in SCCM2012, i think it's a not bug, maybe it need a developpement change,
I explain my case:
1) I deploy my master on my DP, and i advertise the Task Sequence to All Systems
2) The new computer boot on PXE and the image gone done (new client appear in the console)
But if i want to re-image the computer, i have a pxe error : 53, bot image not found. I must do follow this steps:
1) Delete the computer on the console
2) Clear the PXE deployment on the collection
3) Re-advertise the TS on the collection
And the computer boot !!
Is there a (better) solution to correct this problem ?
Thanks you
Tuesday, February 5, 2013 11:34 PM | 1 vote
To clear PXE advertisement for unknown machines you need to clear PXE advertisement on the collection the unknown machine is part of - ie All System. Deleting the "unknown" object doesn't remove it from the Last-PXEAdvertisement table which means you won't be able to PXE boot it again. Alternatively delete all the records from the last pxe advertisement table in SCCM DB.
If for any reason your deployment fails before TS takes over (ie during downloading the boot image) you have no other choice but to remove the machine from this table otherwise it won't budge! This behaviour is completely different comparing to SCCM 2k7
Wednesday, February 6, 2013 10:55 AM | 2 votes
Can you please share a syntax of that query?
Thank you.
select SMS_R_System.Name from SMS_R_System where SMS_R_System.Name like "%unknown%"