Migrating/Upgrading from Unity 3.0(4) to Unity 4.0(5)

[hamdodger]

I am planning a migration from Unity 3.0(4) to Unity 4.0(5). My plan is to build out the 4.0(5) server in parallel to the current 3.0(4) server, upgrade the 3.0(4) server to whatever version of 3.x has the same database structure as 4.x, and then exporting the data from the 3.x server and then importing it into the 4.0(5) server using the latest version of BAT.

I have a few questions before I begin this process:

1. Is what I'm proposing a viable solution?

2. Will I need to upgrade the TSP's on my Call Managers (version 3.3(4)sr2, to the latest version?

3. Does it matter that the new Unity server will have a different host name,

than the current server, if I export/import the database using DiRT? I seem to remember there being a feature in DiRT that allowed you to not include the hostname column when importing.

4. Currently we have to point all Unity users through our Exchange 2000 Server (we have one 2000 and one 2003 server in our mail topology) since Unity 3.x can't directly connect to mailboxes on Exchange 2003. So our

"fix" for now has been modifying the Subscriber table to point Unity through the Exchange 2000 server, even for mailboxes that are on the Exchange 2003 server in the same routing table. So the question here is, once I migrate

Unity to Exchange 2003, and import the current database, is there a tool that

can do a directory walkthrough and properly update the Subscriber table in

Unity 4.x to properly associate each user's account with the correct server location of their mailbox?

[Hin Lee]

1) Not viable. You cannot export a 3.x database into 4.x. You will have to upgrade the 3.x to 4.0(5) then do a DiRT backup. Finally do a DiRT Restore to the new server. Please review this chapter Upgrading Cisco Unity 3.x Software to the Shipping Version http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_upgrade_guides_chapter09186a0080205a78.html

2) Not sure what tsp version you are running, but when you install Unity4.0(5), you will get TSP 8.0(1b) which is compatible with CCM 3.x

3) If you used DiRT tool, servername does not matter.

4) If you are upgrading to Cisco Unity 4.0 because it supports Exchange 2003, you must upgrade to Cisco Unity version 4.0(3) or later before you run Exchange 2003 Forestprep. Otherwise, the changes that Forestprep makes to Active Directory will cause Cisco Unity to stop functioning. http://www.cisco.com/en/US/products/sw/voicesw/ps2237/prod_system_requirements_hardware09186a0080117617.html#wp283756

When you do the DiRT restore, Unity will "see" that the accounts exists and will use the existing ones. Unity will not create new windows accounts nor exchange mailboxes.

[hamdodger]

In regards to issue 4, I have already run ForestPrep for Exchange 2003 on my domain. The way I got around having to upgrade Unity to 4.x at that time was that I still have an Exchange 2000 bridgehead server in my network, so I modify the Subscriber table to use that server as the "faux" mailbox server for the domain. That way Unity can still deliver messages to the Exchange 2003 server in the same routing group.

So if I do a DiRT export and import to the new server, after upgrading to Unity 4.0(5), is there a tool that will do a step through the directory to remap user accounts to their corect mail store (which are mostly all located on the Exchange 2003 Server now).