A Microsoft Outlook email forum. Outlook Banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Outlook Banter forum » Microsoft Outlook Email Newsgroups » Outlook - Installation
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Need Client Migration Ideas



 
 
Thread Tools Search this Thread Display Modes
  #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
  #2  
Old June 3rd 07, 04:47 PM posted to microsoft.public.outlook.installation
Roady [MVP]
external usenet poster
 
Posts: 2,620
Default Need Client Migration Ideas

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
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----

"booker@mgt" wrote in message
...
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


  #3  
Old June 4th 07, 09:53 PM posted to microsoft.public.outlook.installation
booker@mgt
external usenet poster
 
Posts: 18
Default Need Client Migration Ideas

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 [MVP]" wrote:

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
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----

"booker@mgt" wrote in message
...
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



  #4  
Old June 19th 07, 08:47 PM posted to microsoft.public.outlook.installation
booker@mgt
external usenet poster
 
Posts: 18
Default Need Client Migration Ideas

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 [MVP]" wrote:

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
http://www.howto-outlook.com/
Outlook FAQ, HowTo, Downloads, Add-Ins and more

-----

"booker@mgt" wrote in message
...
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



 




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Any Ideas? Aaron-McLeod Outlook - General Queries 2 October 17th 06 10:12 PM
Some Very Good Ideas Sylvia M Outlook Express 1 September 17th 06 01:30 AM
How do I associate one client with another? client to accountant Buzz Bennett Outlook - Using Contacts 0 September 7th 06 11:35 PM
Calendar won't add or delete - any ideas? BobInOlympia1960 Outlook - Calandaring 1 May 30th 06 04:09 AM
Need appointment colors brighter. Ideas? Arlene Outlook - Calandaring 2 March 16th 06 05:40 PM


All times are GMT +1. The time now is 03:53 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.Search Engine Friendly URLs by vBSEO 2.4.0
Copyright ©2004-2025 Outlook Banter.
The comments are property of their posters.