Re: I think I messed up big time... v.Delete Administrative Groups

I have the cluster environment back up and I am the point of
re-installation where it has automatically detected that the server
existed and is not allowing me to change the Administrative Group. So,
should I proceed with the install, put it back as it was, then attempt
an uninstall?

You don't have to go through all that. Since it was not in production,
just whack the server and admin group from ADSIEDIT and re-run your
Exchange setup and it should not complain about it already existing.

James Chong

dataspike@xxxxxxxxx wrote:
James,

Thanks for the link, however I do not want to remove Exchange from the
entire AD environment. I just want to remove the instance of the
"Mountain View" Administrative Group and the "USMTV-MX" server.

I have the cluster environment back up and I am the point of
re-installation where it has automatically detected that the server
existed and is not allowing me to change the Administrative Group. So,
should I proceed with the install, put it back as it was, then attempt
an uninstall?

So, that I can remove the server "correctly" from the environment, and
then hopefully it will allow me to "correctly" remove the "Mountain
View" Administrative Group?

Thanks,
Chris


James Chong wrote:
Since it was not in production just run Exchange with the update.exe
/removeorg. This will remove all Exchange configuration context from AD
and you can start fresh.


http://support.microsoft.com/?kbid=273298

James Chong

dataspike@xxxxxxxxx wrote:
James, thanks for your suggestions.

I have zero data from the previous install, as I mentioned this was not
in a production environment, yet. So, no systemstate available.

So, should I just delete the server and Administrative Group using
ADSIEdit? Or can I reinstall, allow it to detect the server already
"exists" and then, will it allow me to specify a new Administrative
Group?

So, in short, based on the attached Image, my ultimate goal is to
remove the "Mountain View" Administrative Group and place the server
"USMTV-MX" into the "First Administrative Group"

<a href="http://www.dataspike.org/adsi/Untitled-1.jpg";
target="_blank"><img src="http://www.dataspike.org/adsi/Untitled-1.jpg";
width="428" height="333"></a>

URL in case the image doesn't appear:
http://www.dataspike.org/adsi/Untitled-1.jpg

Thanks again for your help, and I go in for training in two weeks. :-)

Chris


James Chong wrote:
My biggest concern was bringing
the server up with the same name when it already "exists".

Yes the systemstate and /disasterrecovery switch would take care of
this like piece in a puzzle. If you do not have the system state or do
not do the /disasterrecovery method then yes when you try to install
Exchange, it will tell you that it already exists.

James Chong

.

Relevant Pages

  • Re: Restore exchange problem.
    ... Install only the Exchange System Manager. ... > Installed a new DC and a new Exchnage server in a seperate domain. ... > But I need another Administrative group so it's like my Production ...
    (microsoft.public.exchange.admin)
  • Re: Delegate Control?
    ... To install servers in a new Administrative Group, ... you cannot move a server across Administrative ... You would need to install a new server in a new Administrative Group, ... admin or preferably a security group. ...
    (microsoft.public.exchange.admin)
  • Re: administrative groups??
    ... fortunately there are no mailboxes - it was a clean new install. ... I keep it from going back into the first administrative group. ... > server and reinstall the server into the admin group of your choice. ...
    (microsoft.public.exchange.admin)
  • Re: How to specify an exchange 2003 as remote bridgehead?
    ... We are also planning a year to go to Exchange 2007. ... I think with an administrative group with only RGs, ... Exchange server to their own RG. ... In the Routing Groups container, ...
    (microsoft.public.exchange.admin)
  • Re: Renaming an Administrative Group?
    ... The KB also says shows you how to bring the server back into a supported state, ... Although this change appears to be merely cosmetic there are dependencies on the Administrative Group name. ... Please do not send email directly to this alias. ... Administrative Group names in Exchange Server 2003 or in Exchange 2000 ...
    (microsoft.public.exchange.admin)