• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2811
  • Last Modified:

"this computer is not registered with the configuration manager site" when trying to image

We are getting this error "this computer is not registered with the configuration manager site".  I have created an image and now I am creating a boot disc so that we can simply boot off of the disc and point to the image package to deploy it.

I am not sure if I am doing something wrong when i create the image or when I create the bootable media.

Any help is greatly appreciated.
0
wheelinghd
Asked:
wheelinghd
  • 2
  • 2
  • 2
  • +2
1 Solution
 
PatricckCommented:
0
 
wheelinghdAuthor Commented:
Thanks for the reply.

I had read about having to add the mac address in to a collection.  But I am wondering if there isn't an easier way to image the computer.  If we get 20 plus computers in that need imaged (keep in mind we have 19 sites) isn't there a way to take advantage of SCCM's tasks and the other packages that are already on there with out putting the image on a DVD.  I think having to manually add mac addresses to SCCM is not a good solution.  Maybe for a one off but for a bunch of new systems it seems like there must be another solution

From what the post says you would have to have an image with everything on it (all your applicatins you want).  They don't support any type of hybrid media.  Where the image is on the disc and it would look to the network for the other applications.  But that doesn't seem like a great solution either if you have a large image with alot of packages you want to have installed.
0
 
PatricckCommented:
We had 500 users, and Norton Ghost. It was a great solution.

here can you find informations about it:
http://en.wikipedia.org/wiki/Norton_Ghost
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
wheelinghdAuthor Commented:
We have been using SMS along with Dell's ximage process up until now.  I know they won't be willing to purchase any other product at this point.  I am sure Ghost will work it just isn't an option right now.
0
 
Adam LeinssServer SpecialistCommented:
OSD changed between SMS 2003 and SCCM 2007.  SCCM 2007 has new security features that require you to add the MAC address before it will talk to the PC.

However, there is a solution in SCCM 2007 R2:

http://blogs.technet.com/mniehaus/archive/2008/09/21/configmgr-2007-r2-s-unknown-computer-support.aspx

It adds a collection called "Unprovisioned computers".  It appears you can then advertise task sequences to the collection "All Unknown Computers" and be able to pick this task sequence from the menu.

Instead of using SCCM 2007 to drive the WIM files, I am now using ImageX directly:

http://www.leinss.com/blog/?p=173

A hack?  Yes.  However, it works great.
0
 
U_ManssonCommented:
If you don't have access to SCCM2007 R2 you can easy solve this by using Microsoft Deployment Toolkit 2008, MDT2008. You can download it for free from MS and integrate it with SCCM2007. It will give you a lot of nice features for OSD i SCCM2007 and one of them is OS Depolyment to unknown computers.
0
 
Adam LeinssServer SpecialistCommented:
Unknown computer support/bare metal deployment in SCCM 2007 is a hack plain and simple.   MDT 2008 does include a file called PXEFilter.vbs where you can setup a connection between WDS and SCCM to allow PXE to unknown computers.

Here's a video of how to integrate MDT 2008 w/ SCCM:

http://blogs.technet.com/deploymentguys/archive/2008/03/20/sccm-2007-and-microsoft-deployment-toolkit-video-walkthrough.aspx

As you will see it's highly complicated with many points of failure.  
0
 
KezziCommented:
I'm having a problem with one of our laptops getting the same error during the boot process.  I've added the computer association and its in the correct collection but it still states that its not registered.  I can still use our SMS 2003 build and it installs and is picked up in the correct collections, but using the new SCCM 2007 boot image it fails to retrieve the TS policy because its not registered.  This is the only machine so far I've done that has this problem, the other 20 different models i've done it with worked flawlessly.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now