Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Unity 2.4.0 and win 2k

We wish to upgrade the unity server to win2000. Will this mess up the Unity software/exchange/other components on the server?<br><br><br>

1 REPLY
Anonymous
N/A

Re: Unity 2.4.0 and win 2k

For the most part upgrading from NT 4.0 to 2000 is reasonably painless. The only real gotcha is if the box is a domain controller, you need to be sure to move the LDAP port off of 389 since Win2K uses this port. This means you also have to point Unity at the same port so you have to make a registry key change.

Also, you don’t want to upgrade from an NT 4.0 PDC to a Win2k member server… Exchange does not like this.

If you’ve used BackOffice to install (which most folks have) you have to be sure to remove the “Microsoft BackOffice server” applet (not all of Back Office!) since this little management console is not happy under Win2K.

Other than that, it’s fairly straight forward. I’ll post QA’s notes on the upgrade testing they did for completeness here. This info should show up in the README file on the 2.4.5 CD…

===========================================

NT PDC to Windows 2000 DC

Before Upgrade
· Run the Add/Remove Programs control panel applet.
· Remove the Microsoft Backoffice Server
· Stop Exchange and Unity services

During Upgrade
. Can choose to make the new domain a new tree or a new child domain. Should not matter which you choose.

After Upgrade
· Open the Phone and Modem control panel applet
· Go to the Drivers tab and click Add
· Select the Dialogic Generation 2 Service Provider (should be the only one)
· Click Properties after it is added
· Make sure that the correct number of channels appear
· Ok out of the dialog boxes and reboot
· Change the LDAP port in the Exchange Administrator.
· Run Exchange Administrator
· Select Site container > Configuration > Protocols > LDAP.
· Set the LDAP port value to 2015.
· Run Regedit and set the following keys:
· HKLM/Software/Active Voice/DalEx/1.00/Server/LDAP Port = 2015
· HKLM/Software/Active Voice/Commserver Setup/1.0/properties/LDAPPortNumber = 2015


NT PDC to Windows 2000 DC to Windows 2000 Member Server

· Not recommended
· Going from a PDC to MS causes you to install as a new domain in Active Directory. Unless you set up another DC in the domain before you demote, Exchange will not start up.
· The reason is that the service account gets killed when the domain goes away (see Microsoft article Q260698 for details). You will need to reinstall Exchange.
· If you add another DC to the domain before demoting, there shouldn't be a problem with demoting the Unity server (this was not tested yet). The other DC will retain the account information, so Exchange should be okay.


NT Member Server to Windows 2000 Member Server

Before Upgrade
· Run the Add/Remove Programs control panel applet.
· Remove the Microsoft Backoffice Server
· Stop Exchange and Unity services

After Upgrade
· Run the Add/Remove Programs control panel applet.
· Remove the Sentinel Security Key Driver
· Reinstall the security key driver from the /securitykey directory of the Unity CD.
· Open the Phone and Modem control panel applet
· Go to the Drivers tab and click Add
· Select the Dialogic Generation 2 Service Provider (should be the only one)
· Click Properties after it is added
· Make sure that the correct number of channels appear
· Ok out of the dialog boxes and reboot


NT Member Server to Windows 2000 Member Server to Windows 2000 Domain Controller

· Follow the steps above in NT Member Server to Windows 2000 Member Server
· Run “DCPROMO” from the command line after you have upgraded to a Windows 2000 member server. This will upgrade you to a domain controller.

During Upgrade to a Domain Controller
· Be sure to become a domain controller in the same domain. If you move to another domain or create a new one, Exchange will not start up (see the explanation in the PDC to DC to MS section above).

After Upgrade
· Open the Phone and Modem control panel applet
· Go to the Drivers tab and click Add
· Select the Dialogic Generation 2 Service Provider (should be the only one)
· Click Properties after it is added
· Make sure that the correct number of channels appear
· Ok out of the dialog boxes and reboot
· Change the LDAP port in the Exchange Administrator.
· Run Exchange Administrator
· Select Site container > Configuration > Protocols > LDAP.
· Set the LDAP port value to 2015.
· Run Regedit and set the following keys:
· HKLM/Software/Active Voice/DalEx/1.00/Server/LDAP Port = 2015
· HKLM/Software/Active Voice/Commserver Setup/1.0/properties/LDAPPortNumber = 2015



Jeff Lindborg
Unity Product Architect
Active Voice
jlindborg@activevoice.com
http://members.home.net/jlindborg

167
Views
0
Helpful
1
Replies
CreatePlease to create content