I have huge headache. We are thinking of upgrading our Exchange server to MS Exchange 2000 Server. I have printed out around 4 thick folders with various TechNet/KB docs (btw, I've compiled it all to a 20mb PDF. If anyone wants it, leave your e-mail address, and i'll send u an URL to DL from).

Now to the headache. I've found out that even a simple thing as "forklifting" users between servers can be a read pain, and you almost always end up having some trouble with synchronization, clientupdates to servers etc etc. I'm afraid i'll only end up with alot of warnings and errors if I choose this way...

So I thought (and was also actually recommended) that the absolutely easiest and "clean" way to do this was to:

1. Export the user's mail, contact list, and calendar to a *.pst on their own machines.
2. Generate a PRF to implement the new Exchange server in the client's Outlook (perhaps even the generation of a new mailbox for the user if a backup *.pst is found could be automated?).
3. Import the *.pst to their new account.

No servermigration problems, no sync problems, and *much* less work, I believe? and as a bonus, you get a *clean* server installation.

Anyone around here with experience? I've seen some good *.PRF examples. But is it possible to fully automate a full *.pst backup of all client Outlook data (and perhaps also generate new mailbox's)?

This way, I could just throw the old Exchange server out the window (and then run after it, jump on it, and perhaps even drive over it a couple of times ), and start off *fresh* with a new one.

[ 08 August 2001: Message edited by: sonnytoft ]

Automating this with KiX should be a piece of cake now, I believe

sorry

Here is a snippet of code that may help you. If you are doing this en massse, then you should be able to use this to the first ELSE portion of the IF Statement. If you want, I can change it over for you.
http://kixtart.org/cgi-bin/ultimatebb.cgi?ubb=get_topic&f=2&t=001861

sonnytoft - Thanks for the insight on the e-mail tools. I have passed these along to our e-mail Admin as we are in the process of moving about 360 mailboxes to another server about 3000 miles (4800 km) away.

Thanks!

- Kent

Well, i'll have to look into this a bit later, right now i'm having huge troubles with "them" (consultants) having installed a BDC during my vacation (leaving absolutely NO documentation what so ever..), and clients are have problems loggin in (the script "hangs" during logon (if the new BDC is taken as the NETLOGON server), I think it ha something to do with loadbalancing, I dunno, but it's really annoying.. :/

Anyways, thanks! I'll check back later when i'm not swamped..

Just an FYI
Don't forget that rule sets exist on the current Exchange server for your users. Many are server based, while some are client based. If you just throw out the old server (so to speak) you will be impacting your users more then you think. What about any custom forms created?, etc... The client does not hold and control all of the customizations.

Well, I was merely expressing my feelings for the old mailserver This was the first time i've ever done this though. It never went out the window, but it was for sure near sometimes :P

anyways, all of my clients are now on the new server, and what's left is the Internet Mail Service Connector, and the good 'ol Schedule+ error...

Little over a year ago, I had to do a very similar thing.

I had to move everyone to a new exchange server. Since I wanted least amount of impact on the users. I brought the new server on-line and connected it to the existing Exchange site, The new server gets all of its information from the old server.

Then over a period of a couple of days, I would move users from the old server to the new server using the move user tool. For windows outlook users this move was seamless since outlook will automatically adjust to point to the new server. I also moved all public folders and made sure that everything was working off of the new server, IMC and any other service that the old server might have been running.

Once everything was moved and running ok, I shutdown the old server... waited a few weeks for any complaints, and then removed the old server from the site.

Bryce

That is exactly what has been done. The Internet Mail Connect service is still running on the old server though. That is what is left (together with the Schedule+ service). Got any tips for moving/reinstalling the Internet Connect Service on the new server (i've heard this can be troublesome, but i've never done this before, so...?

None of this is kix related so if you want, send me an email Bryce@isorg.net

Bryce

with that some info was corrupted in our exchangeserver and I had to upgrade it to SP4 (before excsrvr5.5sp3).
well, the installation did not complete. the problem that were there is gone but now there are no outgoing mail from our site!!!
here I'm sitting, playing with backup and SP's...
exchange really isn't fun in these situations!