Need Client Migration Ideas

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

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
 
If you use the "move mailbox" procedure there is nothing extra that you have
to configure on the client level. Upon first starting Outlook after the move
Outlook will connect the old server and the old server will "tell" Outlook
that the mailbox has been moved and redirects to the new server. Your
Outlook settings will be automatically updated then.
 
Unfortunately, there will not bw a Trust between the two Exchange
organizations, however there will be teporary cooperation to copy over all of
the mailboxes. I believe, a move mailbox requires a trust if it is two
different forests/exchange organizations, correct?



Roady said:
If you use the "move mailbox" procedure there is nothing extra that you have
to configure on the client level. Upon first starting Outlook after the move
Outlook will connect the old server and the old server will "tell" Outlook
that the mailbox has been moved and redirects to the new server. Your
Outlook settings will be automatically updated then.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----

booker@mgt said:
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
Click to expand...
Click to expand...
 
Can the move mailbox procedure be used in an enironment where the two
exchange servers are in two different organizations/forest, with no trust?

Roady said:
If you use the "move mailbox" procedure there is nothing extra that you have
to configure on the client level. Upon first starting Outlook after the move
Outlook will connect the old server and the old server will "tell" Outlook
that the mailbox has been moved and redirects to the new server. Your
Outlook settings will be automatically updated then.

--
Robert Sparnaaij [MVP-Outlook]
Coauthor, Configuring Microsoft Outlook 2003


-----

booker@mgt said:
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
Click to expand...
Click to expand...
 
Back
Top