View Single Post
  #1  
Old June 1st 07, 11:04 PM posted to microsoft.public.outlook.installation
booker@mgt
external usenet poster
 
Posts: 18
Default Need Client Migration Ideas

Here is what I am trying to accomplish. In my environment, I have Outlook
2003 configured to connect via RPC over http to a set of Settings.

I am changing the entire back end. Without having to manually go to each
machine to change the settings, what are some of the ways I may be able to
accomplish this task

i.e Visual Studio (Visual Basic) Script to create/change profiles
i.e Registry changes for settings inside Outlook profile

Where are the profile settings kept.


Again, as an example of what I am trying to do, the current environment is
similar to the following
Profile: EXCHANGE

Server name: exchange.mail.com
Username: xxx

Exchange URL(http) settings
Testmail.domain1.com

SSL connection
Msstd:testmail.domain1.com

On Fast/Slow networks connect with http first, then tcp/ip

Basic Authentication




What I want to do is run a script, or something, that will take the profile
called Exchange and change the following settings:

Server name: Diffexchange.mail.edu
Username: xxx

Exchange URL(http) settings
Newmail.newdomain2.edu

SSL connection:
Msstd:newmail.newdomain2.edu


Etc ,etc

Any ideas on the best way to do that.

My second alternative is to just create a brand new profile with the new
settings.

Any help would be appreciated.

On the back end, the new mailboxes will already be populated. We are
migrating the mailboxes onto the new server and new domain
Ads