there's a section in there for the process of upgrading from 2.x to 4.x. The short story is you use FullDBExport to get the Unity data (most of it anyway, check out the help for FullDBExport for a full run down on what's backed up and what's not) out. You then do a new, fresh installation of Unity 4.x in whatever environement you want (i.e. into a 2K install). Then you run the FullDBImport and it'll find you're users by their mail alias during restore and you should be fine.
the install guide has more detail, of course, but that's the process in a nut shell.
Re: Upgrade path from Unity 2.4.6 and E55 to Unity 4.x and Excha
Kinda the same question here, I've looked at the install guide link listed above but I'm unclear on a point or two.
I have a customer running Unity VM 2.46.135 on a Win2k box w/ Exchange 5.5 and AD. The want to go to VM 4.0(2). It as if I can just patch the OS and Exchange, install MSDE, FullDBExport, and install 4.0(2). The guide lists uninstalling 2.46 only in a UM scenario. Is this correct?
Also, any real advantage to upgrading to Exchange 2k at the same time? The customer has about 200 users total and a CM 3.3 cluster. Thanks in advance.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.