Re: Renaming an Administrative Group?

Paul,

The KB also says shows you how to bring the server back into a supported state, and links to other KBs.

- Although this change appears to be merely cosmetic there are dependencies on the Administrative Group name (as explained in KBs linked from 324606).
- Since tihs isn't user-facing - Administrative Groups are neither seen by users, nor impact administrators. I generally wouldn't recommend changing it.
--
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog

This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------




"Paul Hutchings" <paul@xxxxxxxxxxx> wrote in message news:paul-74628B.19390917062008@xxxxxxxxxxxxxxxxxxxxx
In article <ecAFWiK0IHA.2084@xxxxxxxxxxxxxxxxxxxx>,
"Bharat Suneja [MSFT]" <bsuneja@xxxxxxxxxxxxxxxxxxxx> wrote:

How to use Legacydn.exe to correct Exchange organization names or
Administrative Group names in Exchange Server 2003 or in Exchange 2000
Server
http://support.microsoft.com/kb/324606

--
Bharat Suneja
Microsoft Corporation
blog: exchangepedia.com/blog

This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
----------------------------



"Paul Hutchings" <paul@xxxxxxxxxxx> wrote in message
news:paul-6F5451.18263117062008@xxxxxxxxxxxxxxxxxxxxx
> Surprisingly little on the MSKB.
>
> I have 2 admin groups each with non friendly names that date back to
> Exchange 5.5 and I'd like to change them.
>
> I appreciate and accept that it is only a change in display name, but
> I'd like to double-check if there is any "bad stuff" likely to happen > by
> doing a "right-click/rename" in System Manager?
>
> cheers,
> Paul

Bharat,

That KB articles says:

"Note We support using the Legacydn.exe tool only in a lab environment.
The tool works only in an environment that uses a single domain
controller. "

This is a production environment, with three domain controllers and two
sites/admin groups.

It doesn't really explain the purpose of the "simple" rename option in
Exchange System Manager?

.

Relevant Pages

  • Re: Exchange 2007 does not resolve the second SMTP address
    ... Please do not send email directly to this alias. ... I made the change on the server, ... drop mail for non-existent recipients needs to ... > We were looking at how secure our Exchange server was, ...
    (microsoft.public.exchange.connectivity)
  • 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: removing exchange 2003 objects once exchange 2007 is in place
    ... Was EXCHANGE\0ADEL your Ex 2003 server? ... Also for the first error did you move your public folder hiearchy? ... On your Exchange 2003 or Exchange 2000 server, ... Exchange 2000 administrative group to the Exchange 2007 administrative ...
    (microsoft.public.exchange.admin)
  • Re: Active directory connector error prevents install
    ... Please do not send email directly to this alias. ... >>server as a front end exchange server in an exchange 2000 ... >>version before you can upgrade microsoft exchange. ...
    (microsoft.public.exchange.setup)
  • Re: POP 3 wont start.
    ... Please do not send email directly to this alias. ... > it is running Server 2003 standard edition. ... >>The "Exchange is currently in recovery mode" message ... >>> "Exchange is currently in recovery mode. ...
    (microsoft.public.exchange.misc)