Funny that Exchange 2003 is fine. :)
*ASB *(My XeeSM Profile) <http://XeeSM.com/AndrewBaker> *Exploiting Technology for Business Advantage...* * * On Wed, Sep 15, 2010 at 1:01 PM, Michael B. Smith <[email protected]>wrote: > Examples of applications that are incompatible with domain rename include, > but are not limited to, the following products: > > - Microsoft Exchange 2000 Server > - Microsoft Exchange Server 2007 > - Microsoft Internet Security and Acceleration (ISA) Server 2004 > - Microsoft Live Communications Server 2005 > - Microsoft Operations Manager 2005 > - Microsoft SharePoint Portal Server 2003 > - Microsoft Systems Management Server (SMS) 2003 > - Microsoft Office Communications Server 2007 > > And Exchange 2010 and MOSS 2007 (and I presume 2010, but I haven’t tried). > > > > http://support.microsoft.com/kb/300684 > > > > Anything that has tight links to AD and/or stores its configuration in SQL > is going to be a bitch to rename. > > > > You have to move everything. > > > > Regards, > > > > Michael B. Smith > > Consultant and Exchange MVP > > http://TheEssentialExchange.com > > > > *From:* Brumbaugh, Luke [mailto:[email protected]] > *Sent:* Wednesday, September 15, 2010 12:48 PM > > *To:* NT System Admin Issues > *Subject:* Renaming a domain > > > > I hate to do this but my exchange guy is chiming in and missing the point. > My company has been renamed several times and I have a sales president that > wants us to change the domain name for the cosmetic of it. My Boss and I > want to rename the domain to a generic name just so we don’t have to worry > about this again. This is not carved in stone, but are investigating cost > and time. > > We have several sql servers, exchange 2007, Office Communicator, Sharepoint > and other generic servers. Single Domain in a single forest. > > > > I proposed I build a new domain/new forest with a complete trust, to the > old domain/forest > > Move servers I can move, with permissions changes etc. > > Build virtuals of new servers to replace the ones that can’t move. > > Then slowly move users and computers to new domain. > > > > I am trying to figure what servers need to be moved and which ones need to > be rebuilt. > > Obviously exchange will have to be rebuilt and mailboxes exported and > reimported. (Good time to upgrade to 2010) > > What other servers can I move over? > > I think I can move SQL if I add the appropriate users to the database accts > and jobs. > > What about OCS? > > Any advice or experience would be appreciated. > > > > > > > > *Luke L. Brumbaugh* > > Network Engineer > > Butler Animal Health Supply > > Ph:(614) 659-1736 > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
