RE: 2003-2007 migration with a twist
Hmm, that's too bad. I'm in the same boat here. Our move day is scheduled for next weekend and I only found out about this Friday. It sounds like I'll have a good job for an intern for a while. Thanks for the info. ...Tim From: Jim Holmgren [mailto:jholmg...@xlhealth.com] Sent: Tuesday, June 15, 2010 6:58 AM To: MS-Exchange Admin Issues Subject: RE: 2003-2007 migration with a twist Went through this at my former employer, only we were going from our Ex 2007 environment to their Ex 2003. We did a pretty thorough evaluation of the Quest tools - they are VERY nice and don't seem to miss anything. Not cheap, but money was not the primary concern in this case. Our problem was time-to-implementation. When a vacant suit says "do it now" because he/she can't see another vacant suit's calendar - you don't get a lot of time to work with scheduling professional services from Quest. Our sales rep told me that they will not sell the product without Prof Services, and they needed 2-3 weeks to get someone on site, so We went with Plan B which is not as elegant and involves the users more heavily, but still works. In the end, it probably took the same amount of time, but a whole lot more work to do it the way we did, but we had to give the empty suits some warm fuzzy feelings that we were getting on it "right away". Good times...good times. Jim Jim Holmgren Manager of Server Engineering XLHealth Corporation The Warehouse at Camden Yards 351 West Camden Street, Suite 100 Baltimore, MD 21201 410.625.2200 (main) 443.524.8573 (direct) 443-506.2400 (cell) www.xlhealth.com From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Monday, June 14, 2010 5:37 PM To: MS-Exchange Admin Issues Subject: RE: 2003-2007 migration with a twist Well, if you want it to be "perfect", you should look at the quest tool. If you just are concerned about the data, use Outlook 2007+ and export the PFs to a PST on the "far side" and import them on the "near side". Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Tim Evans [mailto:tev...@sparling.com] Sent: Monday, June 14, 2010 11:42 AM To: MS-Exchange Admin Issues Subject: 2003-2007 migration with a twist We have an all Exchange 2007SP2 environment. We are acquiring a company with an Exchange 2003 (unknown SP) environment. My plan is to create user accounts in our domain for all the users and use exmerge/powershell to move their mailboxes into our domain. My problem is that they have a bunch of public folders with data that we need to bring over. So far, I've found that exmerge won't work on public folders. It looks like the inter-org replication tool may do what I need. Does anyone have any comments/suggestions on the best way to handle this? Is there anything else I need to think about to migrate this properly? Will their free/busy info propagate in our organization when I import their calendar data? Thanks for any ideas. ...Tim CONFIDENTIALITY NOTICE: This email, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or protected health information. Under the Federal Law (HIPAA), the intended recipient is obligated to keep this information secure and confidential. Any disclosure to third parties without authorization from the member of as permitted by law is prohibited and punishable under Federal Law. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. NOTA DE CONFIDENCIALIDAD: Este mensaje incluyendo cualquier anejo es para uso exclusivo del (los) destinatario (s) y puede incluir informaci?n confidencial y/o informaci?n de salud protegida. La Ley Federal (HIPAA) establece que el destinatario est? obligado a mantener la informaci?n confidencial y sequra. HIPAA proh?be y castiga cualquier divulgaci?n a terceras personas sin autorizaci?n del afiliado o permitido por ley. Si usted no es el destinatario, redirija esta mensaje al remitente, y destruye cualquier copia existente del mensaje original.
RE: 2003-2007 migration with a twist
The Quest tools are "Feature Rich" but they have their fair share of technical issues. Chuck Robinson ___ Solutions Architect MCITP:EA, Messaging / MCSE: Messaging EMC Consulting Mobile: 973-865-0394 chuck.robin...@emc.com<mailto:chuck.robin...@emc.com> www.emc.com/consulting<http://www.emc.com/consulting> Transforming Information Into Business Results From: Jim Holmgren [mailto:jholmg...@xlhealth.com] Sent: Tuesday, June 15, 2010 9:58 AM To: MS-Exchange Admin Issues Subject: RE: 2003-2007 migration with a twist Went through this at my former employer, only we were going from our Ex 2007 environment to their Ex 2003. We did a pretty thorough evaluation of the Quest tools - they are VERY nice and don't seem to miss anything. Not cheap, but money was not the primary concern in this case. Our problem was time-to-implementation. When a vacant suit says "do it now" because he/she can't see another vacant suit's calendar - you don't get a lot of time to work with scheduling professional services from Quest. Our sales rep told me that they will not sell the product without Prof Services, and they needed 2-3 weeks to get someone on site, so We went with Plan B which is not as elegant and involves the users more heavily, but still works. In the end, it probably took the same amount of time, but a whole lot more work to do it the way we did, but we had to give the empty suits some warm fuzzy feelings that we were getting on it "right away". Good times...good times. Jim Jim Holmgren Manager of Server Engineering XLHealth Corporation The Warehouse at Camden Yards 351 West Camden Street, Suite 100 Baltimore, MD 21201 410.625.2200 (main) 443.524.8573 (direct) 443-506.2400 (cell) www.xlhealth.com From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Monday, June 14, 2010 5:37 PM To: MS-Exchange Admin Issues Subject: RE: 2003-2007 migration with a twist Well, if you want it to be "perfect", you should look at the quest tool. If you just are concerned about the data, use Outlook 2007+ and export the PFs to a PST on the "far side" and import them on the "near side". Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Tim Evans [mailto:tev...@sparling.com] Sent: Monday, June 14, 2010 11:42 AM To: MS-Exchange Admin Issues Subject: 2003-2007 migration with a twist We have an all Exchange 2007SP2 environment. We are acquiring a company with an Exchange 2003 (unknown SP) environment. My plan is to create user accounts in our domain for all the users and use exmerge/powershell to move their mailboxes into our domain. My problem is that they have a bunch of public folders with data that we need to bring over. So far, I've found that exmerge won't work on public folders. It looks like the inter-org replication tool may do what I need. Does anyone have any comments/suggestions on the best way to handle this? Is there anything else I need to think about to migrate this properly? Will their free/busy info propagate in our organization when I import their calendar data? Thanks for any ideas. ...Tim CONFIDENTIALITY NOTICE: This email, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or protected health information. Under the Federal Law (HIPAA), the intended recipient is obligated to keep this information secure and confidential. Any disclosure to third parties without authorization from the member of as permitted by law is prohibited and punishable under Federal Law. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. NOTA DE CONFIDENCIALIDAD: Este mensaje incluyendo cualquier anejo es para uso exclusivo del (los) destinatario (s) y puede incluir informaci?n confidencial y/o informaci?n de salud protegida. La Ley Federal (HIPAA) establece que el destinatario est? obligado a mantener la informaci?n confidencial y sequra. HIPAA proh?be y castiga cualquier divulgaci?n a terceras personas sin autorizaci?n del afiliado o permitido por ley. Si usted no es el destinatario, redirija esta mensaje al remitente, y destruye cualquier copia existente del mensaje original.
RE: 2003-2007 migration with a twist
Went through this at my former employer, only we were going from our Ex 2007 environment to their Ex 2003. We did a pretty thorough evaluation of the Quest tools - they are VERY nice and don't seem to miss anything. Not cheap, but money was not the primary concern in this case. Our problem was time-to-implementation. When a vacant suit says "do it now" because he/she can't see another vacant suit's calendar - you don't get a lot of time to work with scheduling professional services from Quest. Our sales rep told me that they will not sell the product without Prof Services, and they needed 2-3 weeks to get someone on site, so We went with Plan B which is not as elegant and involves the users more heavily, but still works. In the end, it probably took the same amount of time, but a whole lot more work to do it the way we did, but we had to give the empty suits some warm fuzzy feelings that we were getting on it "right away". Good times...good times. Jim Jim Holmgren Manager of Server Engineering XLHealth Corporation The Warehouse at Camden Yards 351 West Camden Street, Suite 100 Baltimore, MD 21201 410.625.2200 (main) 443.524.8573 (direct) 443-506.2400 (cell) www.xlhealth.com From: Michael B. Smith [mailto:mich...@smithcons.com] Sent: Monday, June 14, 2010 5:37 PM To: MS-Exchange Admin Issues Subject: RE: 2003-2007 migration with a twist Well, if you want it to be "perfect", you should look at the quest tool. If you just are concerned about the data, use Outlook 2007+ and export the PFs to a PST on the "far side" and import them on the "near side". Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Tim Evans [mailto:tev...@sparling.com] Sent: Monday, June 14, 2010 11:42 AM To: MS-Exchange Admin Issues Subject: 2003-2007 migration with a twist We have an all Exchange 2007SP2 environment. We are acquiring a company with an Exchange 2003 (unknown SP) environment. My plan is to create user accounts in our domain for all the users and use exmerge/powershell to move their mailboxes into our domain. My problem is that they have a bunch of public folders with data that we need to bring over. So far, I've found that exmerge won't work on public folders. It looks like the inter-org replication tool may do what I need. Does anyone have any comments/suggestions on the best way to handle this? Is there anything else I need to think about to migrate this properly? Will their free/busy info propagate in our organization when I import their calendar data? Thanks for any ideas. ...Tim CONFIDENTIALITY NOTICE: This email, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and/or protected health information. Under the Federal Law (HIPAA), the intended recipient is obligated to keep this information secure and confidential. Any disclosure to third parties without authorization from the member of as permitted by law is prohibited and punishable under Federal Law. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. NOTA DE CONFIDENCIALIDAD: Este facsímile, incluyendo lo adjunto, es para el uso exclusivo del destinatario(s) y puede contener información confidencial y/o información protegida de salud. En virtud de la Ley Federal (HIPAA), el destinatario tiene la obligación de mantener esta información segura y confidencial. Cualquier divulgación a terceros sin la autorización de los miembros de lo permitido por la ley está prohibido y penado en virtud de la Ley Federal. Si usted no es el destinatario, por favor, póngase en contacto con el remitente por teléfono y destruir todas las copias del mensaje original
RE: 2003-2007 migration with a twist
Well, if you want it to be "perfect", you should look at the quest tool. If you just are concerned about the data, use Outlook 2007+ and export the PFs to a PST on the "far side" and import them on the "near side". Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Tim Evans [mailto:tev...@sparling.com] Sent: Monday, June 14, 2010 11:42 AM To: MS-Exchange Admin Issues Subject: 2003-2007 migration with a twist We have an all Exchange 2007SP2 environment. We are acquiring a company with an Exchange 2003 (unknown SP) environment. My plan is to create user accounts in our domain for all the users and use exmerge/powershell to move their mailboxes into our domain. My problem is that they have a bunch of public folders with data that we need to bring over. So far, I've found that exmerge won't work on public folders. It looks like the inter-org replication tool may do what I need. Does anyone have any comments/suggestions on the best way to handle this? Is there anything else I need to think about to migrate this properly? Will their free/busy info propagate in our organization when I import their calendar data? Thanks for any ideas. ...Tim
