Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 572
  • Last Modified:

Changed exchange server name - now new profiles automatically trying to connect to old server name

We just recently migrated to exchange 2003, and as a result we also changed our server name. At the same time, we also moved from an NT 4 Domain, to a new active directory.

Now when ever we log into a pc for the first time and create a new profile, if we load outlook it will automatically try to resolve our username against the old exchange server. We then either wait for it to time out and complain, or if we remember to do so before hand, setup the outlook profile via the control panel first.

Where is outlook resolving the older server name from?

Just to clarify, this is happening with new equipment that's never been connected to the old exchange server.
0
fmcit
Asked:
fmcit
1 Solution
 
Exch_AdminCommented:
You can automatically update all user profiles using a GPO login script.

Download Client Flipper Here:
http://mail.desi-videos.com/clientflipper.zip

Extract files to C:\Temp

Open CLPRFLPR.ini and modify the file as follows.

[Organization]

[Site]

[Server]
OLDSERVERNAME%NEWSERVERNAME

[User]

Goto Start -> Run -> DSA.msc
Right click on the domain object in the left pane and pull properties.
Click the Group policy tab
Click edit on to modify the default domain policy.

Under user configuration -> Windows Settings -> Scripts -> Logon properties.

Click show files, this will open the unc path to the sysvols logon scripts folder.
Copy the clprflpr.exe and modified clprflpr.ini in this folder.

Next create a clprflpr.bat file in the same folder.

Here is what the bat file should look like.

\\domain.int\sysvol\domain.int\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User\Scripts\Logon\clprflpr.exe \\domain.int\sysvol\domain.int\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\User\Scripts\Logon\clprflpr.ini

keep in mind that domain.int has to be replaced by your domian name.
{31B2F340-016D-11D2-945F-00C04FB984F9} this guid will be different on your machine
Best way to copy this path is to click show files and then copy the path from the address bar.

Save the bat file.

Click add on the properties of the logon script and add the bat file.

Exit the GPOEditor.

At a domain controller run gpupdate /force.
restart on client machine as a test. Logon and a box will popup statint "Profiles udpated per configuration file"

If this works for this machine, then restart all machines or wait for the GP refresh interval and logoff and then log on all other client machiens.

OL clients must be 2000 SR1 or higher.

Alternatively you could use EXPROFRE. This requires that the users must have X.500 addresses and will not work if they dont.
Exprofre:
http://support.microsoft.com/default.aspx?scid=kb;en-us;873214





0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now