Associating user email when replacing servers and domain and username scheme

Réponse proposée Associating user email when replacing servers and domain and username scheme

  • Friday, May 11, 2012 3:14 PM
     
     
       I need to make old email availible to 500 users from our current Exchange 2010 to a new one, on a new domain, with a different username scheme. Basically there is no similar association with the email addresses. I only see a few options like, manually associate each new user email with an alias (old account), or possibly archiving all old email when we go live in our new system and making that availible to each user. We do not plan to keep the old server online long after the change either.  Any suggestions are welcome.

All Replies

  • Friday, May 11, 2012 3:51 PM
     
     
    We really need more of an explanation to provide guidance. we can't tell if you are migrating from one version of exchange to another. or if you are doing a complete domain migration. Ultimately if this is just about email addresses. And old email with in the same org. then simply migrate it. If that is not the case and you are doing something else let us know so we can provide better assistance.

    Mitch Roberson MCM Exchange 2010|MCITP:Enterprise Server Admin, Messaging 2007, 2010 |MCTS:OCS with Voice Achievement |MCT |MCSE 2000\2003 |MCSE Messaging 2000\2003

  • Friday, May 11, 2012 6:37 PM
     
     

    Both versions are exchange 2010 and we are completely replacing the domain and username schema. So a user account such as Jsmith@coolcasino.com will be associated with SmithJ@greatcasino.com on a completely new server and domain, the new system is at an entirely new facility offsite. Would archiving the email and using PST Capture work for something like this? I have only begun researching this and I have never used PST Capture before.

  • Friday, May 11, 2012 9:02 PM
     
     Proposed Answer
    Actually you can move users between Exchange 2010 organizations now. So I would look into cross forest Migrations. If it is a small number of users then Export to PST and import it back in. And call it good, but generally anything over about 80-100 users I would start looking at a cross forest migration.

    Mitch Roberson MCM Exchange 2010|MCITP:Enterprise Server Admin, Messaging 2007, 2010 |MCTS:OCS with Voice Achievement |MCT |MCSE 2000\2003 |MCSE Messaging 2000\2003

  • Monday, May 14, 2012 5:50 PM
     
     
    Ok thank you for the reply, I will look more into cross forest migration as we will have over 500 accounts. I am uncertain if at all or how long we can have both servers up at the same time so that may pose a problem but I will keep you updated in the near future.
  • Wednesday, May 16, 2012 1:24 PM
     
     
    Well after researching either of these options they don't seem to give me the answer I am looking for. The main problem they don't address is the basis for my question.
       How do I use either of these choices when the usernames are not going to be the same? I can understand scripting this to match and associate names that match on 2 different domains but it certainly seems like I will have to manually associate every persons 2 completely different addresses somehow.