availity
asked on
SCCM + OSD Deployment Computer not Registered with Configuration Manager
I am running SCCM 2007 SP2
I am trying to image machine from SCCM. I can successfully image a machine when I advertise my TS to the "All Unknown computers" collection.
When I stop the advertisement to the unknown computer collection I am unable to image via OSD and recieve a message "The computer is not registered with the configuration manager site"
I am booting from a flash drive where I selected "Create Task Sequence Media" and then selected "Bootable Media" Flash Drive. I have tried it with and without unknown computer support checked. With and without a password and I use the self signed certificate. I am using the generic X64 boot media and the same dist point that I used when "unknown Computers" worked.
What I have Done.
1. I have created a new collection "Bare Metal"
2. I have imported the computer from the "Computer Association" area inputing the correct MAC and GUID while also adding it to the "Bare Metal" collection.
3. I have verified I see my machine in the "Bare Metal" collection and that it's MAC and GUID match the computer.
4. I have right clicked my machine in the "Bare Metal" collection and verified I see my OS deployment TS advertised to the machine.
5. I have enabled command line support an verfied I recieve an IP and that I can piin my dist point.
6. I have looked in the smsts.log file and I see where it sends my MAC to SCCM and that it is the correct MAC.
7. I have verified that the computer is showing up in the "Unprovisioned Computers" area of OSD.
From what I have read it seems this should be all I need to do however I still recieve the error in the title of this thread.
I am trying to image machine from SCCM. I can successfully image a machine when I advertise my TS to the "All Unknown computers" collection.
When I stop the advertisement to the unknown computer collection I am unable to image via OSD and recieve a message "The computer is not registered with the configuration manager site"
I am booting from a flash drive where I selected "Create Task Sequence Media" and then selected "Bootable Media" Flash Drive. I have tried it with and without unknown computer support checked. With and without a password and I use the self signed certificate. I am using the generic X64 boot media and the same dist point that I used when "unknown Computers" worked.
What I have Done.
1. I have created a new collection "Bare Metal"
2. I have imported the computer from the "Computer Association" area inputing the correct MAC and GUID while also adding it to the "Bare Metal" collection.
3. I have verified I see my machine in the "Bare Metal" collection and that it's MAC and GUID match the computer.
4. I have right clicked my machine in the "Bare Metal" collection and verified I see my OS deployment TS advertised to the machine.
5. I have enabled command line support an verfied I recieve an IP and that I can piin my dist point.
6. I have looked in the smsts.log file and I see where it sends my MAC to SCCM and that it is the correct MAC.
7. I have verified that the computer is showing up in the "Unprovisioned Computers" area of OSD.
From what I have read it seems this should be all I need to do however I still recieve the error in the title of this thread.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Kindly note that If you are initiating a task sequence using USB media you must leave the USB media attached until you have successfully started the full operating system.
Only for your reference, please check the following link:
http://technet.microsoft.com/en-us/library/bb632725.aspx
Check also:
How to Deploy an Operating System Image to a New Computer Using Boot Media
http://technet.microsoft.com/en-us/library/bb694215.aspx
How to Deploy an Operating System Image to an Offline Computer
http://technet.microsoft.com/en-us/library/bb681017.aspx
If you still have the same issue, please let me.
Only for your reference, please check the following link:
http://technet.microsoft.com/en-us/library/bb632725.aspx
Check also:
How to Deploy an Operating System Image to a New Computer Using Boot Media
http://technet.microsoft.com/en-us/library/bb694215.aspx
How to Deploy an Operating System Image to an Offline Computer
http://technet.microsoft.com/en-us/library/bb681017.aspx
If you still have the same issue, please let me.
ASKER
Well it looks like I am working now but not sure what fixed it. I went and deleted the machine under "Unprovisioned Computers" and then the task sequence was listed as an option so I think maybe the machine cant be listed in "Unprovisioned Computers".
Please check the following:
1- Go to the SCCM database server and open the SQL query with below command to verify which machine use the MAC Address “00:17:42:3D:1B:13” (in this sample):
Select * from v_GS_NETWORK_ADAPTER where MACAddress0 = ‘00:17:42:3D:1B:13’
2- Then based on the SQL query result, delete this machine from the SCCM Admin console.
3- Then re-run the SCCM OSD TS on the target machine which have the MAC Address “00:17:42:3D:1B:13” again.
If the issue persists, we need to enable SCCM logging under WinPE to further investigate this issue. During the deployment, all relevant information is recorded in smsts.log. While in Windows PE the log file is stored in the windows temp directory on the RAM-disk (typically x:\windows\temp\smstslog)
To enable the access to smsts.log while in WinPE, Open the boot image’s properties dialog. On the Windows PE tab check the “Enable command support (testing only)” option Update the boot image on the distribution points. Rebuild any media that uses the boot image (e.g. capture media, boot media, or stand-alone media). When a task sequence is running in Windows PE you can open a command shell by pressing F8. As long as the command-shell is open the task sequence will not reboot the machine. This will give you a chance to verify network connectivity, diagnose driver issues, and view/copy the log files.
Remember that you need to enable the option in both x86 and x64 boot images, then you have to update the distribution point which contains the boot image.
Once the problem occurs under the WinPE mode, collect me the smsts.log from the problematic compute
Please send the log to me
1- Go to the SCCM database server and open the SQL query with below command to verify which machine use the MAC Address “00:17:42:3D:1B:13” (in this sample):
Select * from v_GS_NETWORK_ADAPTER where MACAddress0 = ‘00:17:42:3D:1B:13’
2- Then based on the SQL query result, delete this machine from the SCCM Admin console.
3- Then re-run the SCCM OSD TS on the target machine which have the MAC Address “00:17:42:3D:1B:13” again.
If the issue persists, we need to enable SCCM logging under WinPE to further investigate this issue. During the deployment, all relevant information is recorded in smsts.log. While in Windows PE the log file is stored in the windows temp directory on the RAM-disk (typically x:\windows\temp\smstslog)
To enable the access to smsts.log while in WinPE, Open the boot image’s properties dialog. On the Windows PE tab check the “Enable command support (testing only)” option Update the boot image on the distribution points. Rebuild any media that uses the boot image (e.g. capture media, boot media, or stand-alone media). When a task sequence is running in Windows PE you can open a command shell by pressing F8. As long as the command-shell is open the task sequence will not reboot the machine. This will give you a chance to verify network connectivity, diagnose driver issues, and view/copy the log files.
Remember that you need to enable the option in both x86 and x64 boot images, then you have to update the distribution point which contains the boot image.
Once the problem occurs under the WinPE mode, collect me the smsts.log from the problematic compute
Please send the log to me
ASKER