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

SCCM 2007 - Removing "Assigned" Status and Configuration From Servers

Good Afternoon Everyone -

Our company uses a 3rd party company to help us manage some of our larger servers.  Even though we have the say of what happens, they make sure to keep these select servers up to date, monitored, and repairing any issues.  Our company uses SCCM 2007 to manage the servers we control as well as approx 1000 workstations.  The 3rd party company currently uses SMS, but is in the process of upgrading to SCCM.

About a month ago, our SCCM server somehow (accidentally) automatically installed it's client onto a couple of these 3rd party managed servers.  Because of this, these servers are no longer communicating with that company's SMS server.  I ran a few scripts and tried a few things to remove the client which were partially successful.  Still, though, when they try to push / install their client to the server, it says it is managed by ours still.

Problem:  The problem is that our SCCM console still lists these servers as "Assigned" (actually has Yes underneath their listings in collections.)  As you can see in the screenshot link, the client is not installed, though.  We think this is the problem, yet do not know how to correct it.

Please let me know what I need to do to get this corrected.  It must be done as soon as possible.  If you have any questions, please let me know. - Thanks!!!
1 Solution
Are the Servers in the your SCCM Boundaries?
Make sure the Boundaries for the Servers do not match - This should remove the "Assinged" Flag.

How is your site and those configured? AD extended and published? Server Locator Points? How are the Clients configured?
BzowKAuthor Commented:
Thanks! - Someone just posted the same thing on TechNet's forums. The only problem is that I'm having trouble creating new boundaries.  I just created a new question pertaining to this.  Please take a look - but  - you'll still get points for this one too.

Ensure their servers are not within your ConfigMgr boundaries.
On the servers, run: 'ccmclean.exe' (MS util to remove client).  Delete: %WINDIR%\smscfg.ini and reboot.

ccmclean.exe is available in the 'sms 2003 toolkit 2'.  It works for the ConfigMgr 2007 client.
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

Cloud Class® Course: Amazon Web Services - Basic

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

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