Duplicate Computers after Upgrading to R2
Hello
Ever since upgrading to R2 I have two entries for every new computer I deploy. The way I deploy computers is:
- Start a PXE boot on the new computer and pause it once the MAC address is displayed
- Go to SCCM console and use the Import Computer Information wizard to enter the computer name and MAC address and add it to my OS Deploy collection.
- Resume the PXE boot on the new computer.
This procedure used to work fine with SP1 but since R2 I end up with two computers after the task sequence completes, one with a client and one without.
Does anyone know why this happens and is there a fix for it?
January 29th, 2014 5:41pm
Why don't you use Unknown computer support and place a popup for asking computer name when the computer boots up? No need to jump back and forth with the computer and ConfigMgr console.
January 29th, 2014 10:25pm
Seems the client has not picked up the identity from Site server at Setup Windows and ConfigMgr step. Please post the log file smsts.log here. I will analyze it.
January 30th, 2014 5:00am
Thanks Narco
I tried applying the same TS I've always used to Unknown Computers and it did produce only one computer but for some reason, when it starts it sits there for three minutes telling me it's going to start. I also tired setting the OSDComputerName variable
as per these instructions (it won't let me insert the link to windows-noob) but I was never prompted to enter a name. I've read that it is because I have the deployment set as Required. I will try again tomorrow with a new deployment set as Avalaible.
I have to wait until tomorrow because that's how long it will take for the applications to install even though I have set business hours from 5:00 am to 6:00 am with no days selected, and I have manually run the Application Deployment Evaluation
Cycle, but that's an issue for another topic.
- Edited by
therearenouniquenamesleft
14 hours 49 minutes ago
January 30th, 2014 4:26pm
Thanks Jake
The smsts.log file contains only this line
Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\Logs
January 30th, 2014 4:28pm
Thanks Narco
I tried applying the same TS I've always used to Unknown Computers and it did produce only one computer but for some reason, when it starts it sits there for three minutes telling me it's going to start. I also tired setting the OSDComputerName variable
as per these instructions (it won't let me insert the link to windows-noob) but I was never prompted to enter a name. I've read that it is because I have the deployment set as Required. I will try again tomorrow with a new deployment set as Avalaible.
I have to wait until tomorrow because that's how long it will take for the applications to install even though I have set business hours from 5:00 am to 6:00 am with no days selected, and I have manually run the Application Deployment Evaluation
Cycle, but that's an issue for another topic.
- Edited by
therearenouniquenamesleft
Thursday, January 30, 2014 9:30 PM
January 31st, 2014 12:25am
MS did change how the Discovery methods Works but that was in SP1.
On your duplicate records, what agents have created or updated each record
February 4th, 2014 2:18am