Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Unity 4.0(2) upgrade to 7.0

Status
Not open for further replies.

hardy99

Technical User
Nov 14, 2008
1
US
We are currenlty running Unity 4.0(2) on a standalone VM server with Exchange installed on box and a Domain Controller in it's own domain. I do not have the 4.0(2) unity install DVD's.

I have new hardware and will be installing Unity 7 on the new hardware. I will be using the current Exchange servers for the company and will be integrating into the company's main domain. I will be running two unity servers running active/passive mode on version 7.

How can I migrate the data user's vm's and many call handler's over to the new 7.0 installed boxes? How would I map the user's on the new server using the company's active directory because the names will be different than the 4.02 server username's and mailboxes. How can I move the call handler's over?

 

This is the only tool I know that can migrate from Unity 4.0 to a newer version. HOWEVER, it only works on Unity 4.05 and above. You would have to upgrade your VM system up to that level for the tool to work.
But due to all your changes, I think the best thing for you to do is build the new servers from scratch. Import all your Exchange Users to the new box (Bulk Import Tool)so they have the correct UserID's, etc. As for the stored Vmails, give your Users access to both old and new servers for a couple weeks to let them handle the old messages. If necessary, you possibly could connect to the old server through Outlook and give them 'email' access to the old files. It will be a pain but I think you'll be better off.
 
I agree with pndscm. Even with Cobra tool your user aliases are different so you have an issue there as it won't restore correctly.
You need to consider this as a voice mail forklift as you are going from a voice mail only solution to unified, even though it is the same product line.

Have the users access both voice mails for a couple of weeks and then turn it off. If someone on thte higher up HAS to have their messages restored extract the waive files from the old exchange server manually and email them afterwards.

Build it all manually, call handlers and all, use the old greetings to save you time. Set the expectations to the users up front so there is no confusion as what they need to do after the conversion.



 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top