Thanks. I will give this a try. This may be sufficient from an end user's standpoint.
-Andy From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, September 15, 2010 11:48 AM To: MS-Exchange Admin Issues Subject: RE: Changing domain name Sure. You can create a new userPrincipalName suffix that matches the email domain, assign that to each user (easy to do in PowerShell) and have them log in with their email address, just like they do in OWA. Here is some code to help: # # userPrincipalName processing routines # # Michael B. Smith # mich...@smithcons.com # April 6, 2009 # [int]$ADS_PROPERTY_CLEAR = 1 [int]$ADS_PROPERTY_UPDATE = 2 [int]$ADS_PROPERTY_APPEND = 3 [int]$ADS_PROPERTY_DELETE = 4 function get-ConfigurationPartition { $rootdse = [ADSI]"LDAP://RootDSE" $configNC = $rootdse.ConfigurationNamingContext $rootdse = $null $partition = [ADSI]("LDAP://CN=Partitions," + $configNC) return $partition } function get-UPN { $config = get-ConfigurationPartition $suffix = $config.uPNSuffixes $config = $null return $suffix } function test-UPN([string]$upn) { $suffixes = get-UPN if (!$suffixes) { return $false } if (($suffixes -is [System.String]) -and ($suffixes -eq $upn)) { return $true } foreach ($suffix in $suffixes) { if ($suffix -eq $upn) { return $true } } return $false } function new-UPN([string]$upn) { if (test-UPN $upn) { write-error "$upn already exists" } else { $config = get-ConfigurationPartition $config.PutEx($ADS_PROPERTY_APPEND, "uPNSuffixes", @($upn)) $config.SetInfo() $config = $null } } function remove-UPN([string]$upn) { if (test-UPN $upn) { $config = get-ConfigurationPartition $config.PutEx($ADS_PROPERTY_DELETE, "uPNSuffixes", @($upn)) $config.SetInfo() $config = $null } else { write-error "$upn doesn't exist" } } Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Leedy, Andy [mailto:ale...@butlerschein.com] Sent: Wednesday, September 15, 2010 11:37 AM To: MS-Exchange Admin Issues Subject: RE: Changing domain name The real problem is with computer logins. We need to change the computer login from... oldcompany\user to newcompany\user or use u...@emailaddress. Because when everyone in the company logs in they see the old company name as the domain name. Thus the request to change it. I know OWA can be changed to use u...@emaildomain instead of domain\user. The servers can remain in the old domain because it is transparent to the user. Is there a simple solution to this (change user logins) without moving everything to new forest? -Andy From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Wednesday, September 15, 2010 11:20 AM To: MS-Exchange Admin Issues Subject: RE: Changing domain name I gotta ask - what is the business driver for this? Whose budget is this coming out of? This will cause enormous business disruption for very little (zero) added value. I've got a client, about 7.5K seats, whose forest was named in 1996 (NT 4). Six mergers ago. The entity by which the forest was named hasn't existed in 5 years. But to move over 7,000 desktop/laptops and 250 servers into a new forest? Not gonna happen. I have moved smaller clients using both native and third-party tools. But typically that only happens because of a divestiture and they are legally obligated to remove all usage of a given name from their environment. I'm not aware of any whitepapers on MSFT's site. You might take a look at the ADMT subsite (the MSFT 'free' tool). And on Quest and NetWrix sites for the tools they have for this purpose. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Brumbaugh, Luke [mailto:luke.brumba...@butlerschein.com] Sent: Wednesday, September 15, 2010 11:09 AM To: MS-Exchange Admin Issues Subject: RE: Changing domain name OK that's what I need to know, so I need to build a virtual system, move users and once completed rebuild old physical server. So what are my steps, is there a white paper? So far my plan is a complete trust, move a few test users over, and set permissions groups etc. then slowly take servers from old domain and add to new. Rebuild the ones that need to be, or virtualize or whatever. I need a plan and an estimated cost, then I start to budget for it. From: Don Ely [mailto:don....@gmail.com] Sent: Wednesday, September 15, 2010 11:02 AM To: MS-Exchange Admin Issues Subject: Re: Changing domain name Read the last part... You start with a fresh forest and Exchange environment and you migrate everything over... That means users, computers, mailboxes, etc... On Wed, Sep 15, 2010 at 7:59 AM, Brumbaugh, Luke <luke.brumba...@butlerschein.com<mailto:luke.brumba...@butlerschein.com>> wrote: Yes you probably did. But not doing it is not an option, what do I have to do to get it done. From: Don Ely [mailto:don....@gmail.com<mailto:don....@gmail.com>] Sent: Wednesday, September 15, 2010 10:57 AM To: MS-Exchange Admin Issues Subject: Re: Changing domain name /Deja Vu Didn't we just go through this yesterday? Or was that another list? It's not supported, it doesn't work, start over from scratch and migrate if you really want to change things... /Deja Vu On Wed, Sep 15, 2010 at 7:53 AM, Brumbaugh, Luke <luke.brumba...@butlerschein.com<mailto:luke.brumba...@butlerschein.com>> wrote: My company has changed names several times. My boss and I have been asked to change the netbios domain name so that it matches. We want to go one better to rename the domain to a generic domain name, so that if and when the company changes names again, we won't have to go through this again. We have an exchange 2007 system, with 2 mail servers and 2 hubs. What are my options to rename the exchange server? Do I have to rebuild? TIA Luke L. Brumbaugh Network Engineer Butler Animal Health Supply Ph:(614) 659-1736 ********************************************************************** CONFIDENTIALITY NOTICE - The information transmitted in this message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy all copies of this document. Thank you. Butler Schein Animal Health ********************************************************************** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe exchangelist ********************************************************************** CONFIDENTIALITY NOTICE - The information transmitted in this message is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and destroy all copies of this document. Thank you. Butler Schein Animal Health ********************************************************************** --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe exchangelist
