currently l need to move a exchange server it's really hard to me.. here is my jobs 1. create a new ms domain 2. move the old exchange server data to a new my problems is how could l move the old exchange server data to the new exchange server without any data lose and remain user mail profile setting .e.g user's calenda setting. after the exchange server is being move .. all user need to do is to change the new exchange setting but remain all their data and setting l hear someone say it's terrible to move exchange server to : 1. new microsoft domain 2. not same computer name as old exchange 3. not the same site name 4. not the same organization name but l face above 4 changes.. how could l do that..???????

Before moving your exchange server, I advsie you to type the registration letter first. It is really terriable. Below is my experience and it is workabe for one server of one organization: 1. Backup all data. 2. config all client to use personal folder and get all e-mail from server to HD. 3. Write down all settings in current server 4. If it is possible, keep all current HD. 5. Rebuild the new server 6. Connect all current client to the new server. 7. Config the DNS Since all e-mail messages are transfer to users' PC, there is no data loss.

With all you are trying to configure you have no choice but to extract all the data from both the IS and if you need it the DS. You do not say how big the databases are or how many users you have. But I would consider using EXmerge (Back office resource kit, or better still the new version that comes with Exchange 2000), all it does is create PST files for all mailboxes but its very versitile and means you can do it all at once from the server without the users mucking it up. If you Directory is not to complicated ie lots of DL etc then I would just use the IS/DS consistnacy checker which will look at the IS and create DS entries for all mailboxes it finds. Your only other problem is that none of the "Primary NT accounts" associated with the mailboxs will be valid for the new domain so you either have to corect them manually or export the directory from the Exchange admin console to txt and amend the entries with "find and replace" then import it and the accounts should also work. One pion to remember is using pst will mean you loose the benefit of "single instance" storage, ie one mail sent to 50 uses was stored once, once you export you will have 50 copies and a larger IS database will be the result so space will need to be considered. The configure your clients, you could use the NEWPROF utility to create these when the users logon.

With all you are trying to configure you have no choice but to extract all the data from both the IS and if you need it the DS. You do not say how big the databases are or how many users you have. But I would consider using EXmerge (Back office resource kit, or better still the new version that comes with Exchange 2000), all it does is create PST files for all mailboxes but its very versitile and means you can do it all at once from the server without the users mucking it up. If you Directory is not to complicated ie lots of DL etc then I would just use the IS/DS consistnacy checker which will look at the IS and create DS entries for all mailboxes it finds. Your only other problem is that none of the "Primary NT accounts" associated with the mailboxs will be valid for the new domain so you either have to corect them manually or export the directory from the Exchange admin console to txt and amend the entries with "find and replace" then import it and the accounts should also work. One pion to remember is using pst will mean you loose the benefit of "single instance" storage, ie one mail sent to 50 uses was stored once, once you export you will have 50 copies and a larger IS database will be the result so space will need to be considered. Then configure your clients, you could use the NEWPROF utility to create these when the users logon.

Moving Exchange isn't that bad..... Think about this option. Build new server and connect it to the Domain with a different name and I.P. When you install Exchange, you will be asked if you want to join the same organization as the other one. Say yes. You can then replicate the mailboxes over to the new server. You can also change your Proxy Server here if the mail server is your Proxy server. Copy the directories and make your sites in Management Console. After you move everything over, disconnect the old server from the organization. Take the new server and give it the old Exchange server name and I.P. and you are done. You will have no data loss and as you move the mailboxes, make sure that you go into the mailbox and state that the new server is the home server. After you change names, change the name for home server as well. I know this works for I had to do it.

Speaking of terrible, I have a "merger" issue. Now have two seperate Exchange Organizations, is there a way to connect them i.e. via the IMC? Any way at all without moving the server? Also, for now is there a way to share GAL's between the two Org's? Thanks