I have moved a few test users using ADMT (Migrated roaming profiles, SID history etc which completed with no errors) and then moved there mailboxes using the Exchange Migration wizard.
I thought that having moved the mailbox and logged on in the new domain Outlook automatically should find the new exchange server. This is not happening. Worse If I try to manually change the Outlook Profile to look for the New Exchange server I get an error message. "The Name could not be resolved. The Name could not be matched to a name in the address list." Have I missed something basic? Kevan ________________________________ From: Carl Houseman [mailto:[EMAIL PROTECTED] Sent: 23 July 2008 19:02 To: MS-Exchange Admin Issues Subject: RE: Exchange server 2003 migration to a new Exchange 2003 server in a new organization. Oops, yes pfmigrate is not the right tool. You could use this: http://support.microsoft.com/kb/238573 Or just use Outlook against old server copy the PF's from server to a PST, then in a different profile against the new server, copy from PSTs to the server. Carl From: Kevan Dickinson [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2008 11:53 AM To: MS-Exchange Admin Issues Subject: RE: Exchange server 2003 migration to a new Exchange 2003 server in a new organization. Carl. Thank you for your reply. Is pfmigrate going to work between exchange servers in different organizations? All the documents I have found so far talk about moving public folders between servers in the same organization. We don't have a front end Exchange server at the moment, but it would be a good use for the old Exchange server once we have migrated everyone off of it. Kevan ________________________________ From: Carl Houseman [mailto:[EMAIL PROTECTED] Sent: 23 July 2008 15:58 To: MS-Exchange Admin Issues Subject: RE: Exchange server 2003 migration to a new Exchange 2003 server in a new organization. Well for moving mailboxes there's the "Exchange migration wizard". Google that and you'll get some documentation. For moving public folders, "pfmigrate" is your google keyword. RPC over https: If you have a FE server for your current org, you'd uninstall it from the current org and re-install it to the new org, now you've got RPC over https into the new org. Of course this could potentially allow RPC over https for any mailboxes, not just the ones at your location, so get approval from the parent company before doing this. Not using a FE server? Shame on you. Generally speaking an OWA server has access to any mailbox in the org. If you want to reduce across-the-pond WAN traffic, you use the aforementioned FE server for OWA access as well. Carl From: Kevan Dickinson [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 23, 2008 10:15 AM To: MS-Exchange Admin Issues Subject: RE: Exchange server 2003 migration to a new Exchange 2003 server in a new organization. Hi Unfortunately although they are a larger company with more IT staff and more users than we have. (About 500 compared to our 200), they have no more experience of doing this than I have. I am working with them to do this migration. So any thoughts or tips to point me at the correct documentation would be helpful. I can find plenty of information about adding a new exchange server to an existing organization and migrating users from one server to another but not so much information regarding a cross forest migration. Regards Kevan ________________________________ From: Carl Houseman [mailto:[EMAIL PROTECTED] Sent: 22 July 2008 19:30 To: MS-Exchange Admin Issues Subject: RE: Exchange server 2003 migration to a new Exchange 2003 server in a new organization. Have you asked these questions of the mail admins at the new parent company? Certainly if they are requiring you to use their org, they should be able to answer them and their answers would likely be more accurate than ours, particularly if they are a larger company and have done this before. Carl From: Kevan Dickinson [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 22, 2008 1:08 PM To: MS-Exchange Admin Issues Subject: Exchange server 2003 migration to a new Exchange 2003 server in a new organization. Hi Our company has recently merged with another and I need to migrate all our users from our current Exchange 2003 SP2 server to a new Exchange 2003 SP2 server in the Exchange organization of our parent company. All the user accounts in our current domain are to be migrated to a new child domain in the Parent company domain and the new exchange server is in this child domain. We have created a 2 way trust between our Forest and the parent Company Forest and I can move user accounts using the Active Directory Migration Tool. My question is what is the best way to move the user mailboxes and Public Folders?. This migration will probably be done over a number of days so how can I ensure that migrated users can still connect to OWA and use http over RCP. At present the parent company exchange Organization does not use http over RCP. Will I be able to let the users on my new exchange server which is in the parent organization use HTTP over RCP still? The parent company does use OWA and has a front end Exchange Server for this purpose. If I give my migrated users the url for this OWA server will they be able to connect to there mailbox on the new server? It is envisaged that external email will still come in and out of our exchange server directly over our Internet connection and not be routed in via the parent company exchange server. We are connected to the parent company which is in the US via a MPLS connection. Is there anything in particular that I should look out for that may catch me out. Any help and documentation appreciated. Regards Kevan Dickinson NSF-CMI Hanborough Business Park, Long Hanborough, Oxford, OX29 8SJ, UK T:+44 01993 885661 E:[EMAIL PROTECTED] W:www.nsf-cmi.com ************************************************************************ ******** ***Disclaimer*** The contents of this Email may be privileged and are confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Should you wish to use Email as a mode of communication, NSF-CMi Ltd and its subsidiaries are unable to guarantee the security of Email content outside of our own computer systems. This footnote also confirms that this Email message has been checked by MailMarshal for the presence of computer viruses. Whilst we run anti-virus software, you are solely responsible for ensuring that any Email or attachment you receive is virus free. We disclaim any liability for any damage you suffer as a consequence of receiving any virus. NSF-CMi Ltd Registered in England No: 1899857 Registered Office 4th Floor, 35 New Bridge Street, London, EC4V 6BW ************************************************************************ ********** ******************************************************************************** ***Disclaimer*** The contents of this Email may be privileged and are confidential. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Should you wish to use Email as a mode of communication, NSF-CMi Ltd and its subsidiaries are unable to guarantee the security of Email content outside of our own computer systems. This footnote also confirms that this Email message has been checked by MailMarshal for the presence of computer viruses. Whilst we run anti-virus software, you are solely responsible for ensuring that any Email or attachment you receive is virus free. We disclaim any liability for any damage you suffer as a consequence of receiving any virus. NSF-CMi Ltd Registered in England No: 1899857 Registered Office 4th Floor, 35 New Bridge Street, London, EC4V 6BW ********************************************************************************** ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
