best practices for removing parent server?

[wallst32]

I have a parent server I would like to retire. The problem is there are still some clients attached to it that I cannot move because they are not always online.

Also, there were some client systems in a lab that had not been powered on for over 1 month. After turning them on, they appeared on the client list. I was under the impression once you were attached to a parent, your system would not be removed from the list unless done administratively.

Any suggestions? Thanks.

 

[Stiddy]

you have to move all of the systems to a new parent server before you take down the server. Or, you could just take it down and use the internal audit capabilites within the SSC console to find unprotected systems.

HTH - Stiddy