Re: Exchange Server rename and Outlook profiles

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Bob Williamson (Osm3um_at_news.postalias)
Date: 03/10/05 

Date: Thu, 10 Mar 2005 09:02:52 -0800

Thanks for your reply, additional info is below.
Bob

It is fairly interesting as the profiles lists exchange.domain.local, there
is no DNS zone for domain.local, yet my users are functioning. There are
some problems being reported which may or may not be related to this issue.

Exprofre gave me numerous errors like:

Profile unresolved server = "mail.domain.local" NOTE: Old exchange 2000
server prior to Exchange 2003 migration and prior to domain rename.
Profile home server name FQDN = "exchange.domain.local" NOTE: Current
Exchange server before domain rename.

Also:

Error: f:\df7408\deployment\src\autoprof\ad.cxx(222):
CActiveDirectory::SearchForTheUserProfile()
 "The users mailbox has not been migrated or the profile update has already
been run."

 HRESULT=0x5012

With regard to your questions see inline below:
> 1. What's the edition of your Exchange server, 2000/2003? Domain rename
> operations are not supported in an AD that includes an Exchange 2000
> deployment, which applies to both 2000 AD and 2003 AD. See:
>
> 822590 Exchange System Attendant does not start after you rename a Windows
> http://support.microsoft.com/?id=822590

Network is W2K3 native with Exchange 2003 SP1 and Exchaneg is functioning
fine.

> 2. If you are using Exchange 2003 SP1, would you let me know your detail
> steps of renaming the domain name? Have you referred to this KB article?
>
> Supplemental steps for using the Exchange Server Domain Rename Fixup tool
> together with the Windows Server 2003 domain rename tools
> http://support.microsoft.com/?id=842116
>
> Note: SP1 of Exchange 2003 must be applied before rename the domain.

Yes I went through all additional steps for the Exchange portion.
Everything is working fine INCLUDING my users Outlook to Exchange link.

>
> 3. If all the steps are correct, this problem may be caused by the Outlook
> profile which still holds the old server name. You can use exprofre to
> update the client profile. And I am afraid group policy is no avail to
> improve this situation. About more information of exprofre utility, please
> refer to:
>
> How to use the Exchange Profile Update tool
> http://support.microsoft.com/?id=873214

I tried using exprofre as described, on my local machine and it did not
work. See commenst above

Relevant Pages

  • Re: Exchange 2 Domains
    ... server in the child domain, if thats ok?, ... don't have Exchange in the picture yet. ... Yes....but you don't want a user in one location dragging a roaming profile ...
    (microsoft.public.exchange.setup)
  • Re: PRF and profile import problems
    ... I unchecked that option and let it build the PRF file and I ... The PRF file will put in all of the Exchange proxy information, BUT, it ... still keeps the old server name. ... it to replace the current information in the profile and then insert the new ...
    (microsoft.public.outlook.installation)
  • Re: OT: Terminal server and Outlook 2003
    ... How to use the Exchange Profile Update tool ... to download the tool and extract it on the TS server. ... >launch Outlook you get server cannot be found. ... >log in to each users' profile to make the above change. ...
    (microsoft.public.windows.server.sbs)
  • Re: Real-world trouble renaming 2003 domain?
    ... Exchange and Outlook you need to change the outlook profile to point to the ... new exchange server DNS name. ... If for some reason the domain rename screws up your forest, ... which also hosts some file shares, one webserver cluster (IIS and Apache ...
    (microsoft.public.windows.server.active_directory)
  • Re: Exchange 2 Domains
    ... approx 50 PC's and no exchange. ... The Site B that is merging with site A will be getting a new server ... VPN between two compatible firewalls/routers would be a good thing. ... profile over a WAN link, even if the profile is small. ...
    (microsoft.public.exchange.setup)