Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Thu, 15 May 2008 17:47:32 +0100,    group: microsoft.public.exchange.admin        back       


Installing Exchange 2003 and Migration Questions   
I have a server to configure for a remote office.  The rights and 
wrongs of a local server vs. cached mode to one side, it¹s sat in our 
workshop and I need to start building it up tomorrow :-)

It needs to be a Domain Controller (and presumably a Global Catalogue?) 
through the fact that it authenticates users in that AD site.

I¹ve done some digging and the issues I can find are:

Shutdown can take a long time if you don¹t stop the SA (and therefore 
Exchange services) first. You can¹t demote the DC back to a member 
server Exchange will only use that DC/GC server.

Their existing server is 5.5 and is part of our Exchange Organization 
but is in its own Site.

We went to 2003 at our site some time back, so the ADC has been running 
since and agreements are in place to/from their existing server.

My understanding is that I can "simply" join the new 2003 box to their 
Exchange site, move all the mailboxes and Public Folders, do the steps 
to remove the 5.5 directory replication and site connectors and remove 
the 5.5 box and the ADC (not too sure what order those last 2 are done 
in?), then I can go native and move their new server into our 
Administrative Group?

Finally, since our Administrative Group is called "Our Site Name", I'd 
like to have a new one called "Default Administrative Group" (or 
whatever) - is there any more to it than creating a new AG and moving 
both servers into it?

It's been a few years since I've had to actually install/build an 
Exchange box so I'd like a bit of a sanity check please.

Thanks in advance
date: Thu, 15 May 2008 17:47:32 +0100   author:   Usenet se

Re: Installing Exchange 2003 and Migration Questions   
Usenet <usenet@nospam.please> wrote:

>I have a server to configure for a remote office.  The rights and 
>wrongs of a local server vs. cached mode to one side, it¹s sat in our 
>workshop and I need to start building it up tomorrow :-)
>
>It needs to be a Domain Controller (and presumably a Global Catalogue?) 
>through the fact that it authenticates users in that AD site.
>
>I¹ve done some digging and the issues I can find are:
>
>Shutdown can take a long time if you don¹t stop the SA (and therefore 
>Exchange services) first. You can¹t demote the DC back to a member 
>server Exchange will only use that DC/GC server.
>
>Their existing server is 5.5 and is part of our Exchange Organization 
>but is in its own Site.
>
>We went to 2003 at our site some time back, so the ADC has been running 
>since and agreements are in place to/from their existing server.
>
>My understanding is that I can "simply" join the new 2003 box to their 
>Exchange site, move all the mailboxes and Public Folders, do the steps 
>to remove the 5.5 directory replication and site connectors and remove 
>the 5.5 box and the ADC (not too sure what order those last 2 are done 
>in?), then I can go native and move their new server into our 
>Administrative Group?

Up to the point where you said "move the server" you were okay. You
can't move a server between administrative groups without breaking
things. You can put the servers in the same /routing/ group, though.

>Finally, since our Administrative Group is called "Our Site Name", I'd 
>like to have a new one called "Default Administrative Group" (or 
>whatever) - is there any more to it than creating a new AG and moving 
>both servers into it?

Yes. There's a lot of things that are linked to legacyExchangeDN
property values.

-- 
Rich Matheisen
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Don't send mail to this address mailto:h.pott@getronics.com
Or to these, either: mailto:h.pott@pinkroccade.com mailto:melvin.mcphucknuckle@getronics.com mailto:melvin.mcphucknuckle@pinkroccade.com
date: Thu, 15 May 2008 18:18:16 -0400   author:   Rich Matheisen [MVP]

Re: Installing Exchange 2003 and Migration Questions   
In article ,
 "Rich Matheisen [MVP]"  wrote:

> Up to the point where you said "move the server" you were okay. You
> can't move a server between administrative groups without breaking
> things. You can put the servers in the same /routing/ group, though.

Thanks for pointing that out Rich, I'd got confused somewhere down the 
line into thinking you could do that.

Sounds like it's a vmware swing server in their Exchange site to get rid 
of the 5.5 box and go native, then once native I can move their 
mailboxes/public folders onto the proper server.

Cheers!
date: Fri, 16 May 2008 17:06:57 +0100   author:   Usenet se

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us