Unity 4.0(4) and Unity DST files

Erick Bergquist · ‎02-13-2007

Hi,

Just wanted to verify this, as the Unity field notice on this isn't really clear.

For 4.0(4), we would apply the Windows 2000 update from the Unity DST zip file and the tzupdate JRE update only right?

This system has Exchange 2000 offbox , but in a VM only setup so not unified. The notice saids to contact Microsoft for a Exchange patch if determined. Does anyone know if Microsoft has a patch before having customer go get a support contract from microsoft?

If everything is in the same timezone, is there any reason to do anything with exchange even, or just do the JRE update and Windows 2000 update. Then have them do the regular MS update on their offbox exchange server?

sopayne · ‎02-13-2007

Hi,

Using these sources to answer your questions:

From the Field Notice at:

http://www.cisco.com/en/US/customer/products/sw/voicesw/ps2237/products_field_notice09186a00807dcf40.shtml

This is excerpted from the ReadMe file:

Cisco Unity Installation Instructions:

1) For *all* versions of Cisco Unity, install the appropriate Windows patch for the version

running Unity. You may also wish to apply the patch to each domain controller and global catalog server in your forest

that is available to Unity.

2) For each of the specified versions of Unity listed below, do the follow:

4.2(1): double-click the EXE within the folder "\Unity_ES\Unity_4.2(1)" and follow the instructions

4.1(1): open the ReadMe.txt within the folder \Unity_ES\Unity_4.1(1) and follow the instructions

4.0(5): open the ReadMe.txt within the folder \Unity_ES\Unity_4.0(5) and follow the instructions

If you are using Unity version 4.0(4)SR1 or lower, no additional Engineering Special (ES) is necessary as the feature

at risk is not present in those versions.

3) For all versions of Unity 4.0(1) and later, Open the ReadMe.txt within the folder "JRE_time_zone_update" and follow the instructions.

If you are using a version of Unity prior to 4.0(1), Step (3) does not apply to your system

So, (hopefully) to answer your questions, you would:

1) apply the Windows 2000 update from the Unity DST.zip file, specifically the one that's in the folder named "Windows_2000". This assumes that you have Unity installed on a Windows 2000 server. You also need to follow the ReadMe file in the JRE_time_zone_update folder since you have Unity 4.0.4 and that's later than 4.0.1

2) from the Field Notice: "If Unity is used in a voice mail only configuration, there is no need to install the currently available Exchange 2003 patch or Exchange 2000." So, this indicates you do not need to install any Exchange-specific patch. However, if you would like to apply the patch from Microsoft to your off-box Exchange server, you can go to the link provided in the field notice and download the patch. This is the link from the Field Notice that leads you to the download (that I downloaded without having a support contract with Microsoft): http://support.microsoft.com/kb/926666

3) Referencing the previous response, it appears that there's no need to make any updates for vmail-only systems, but you could apply the Microsoft patch referenced in my response #2 above to cover that base.

I hope this helps.

Erick Bergquist · ‎02-13-2007

Right, but from the MS Article, it has the following for Exchange 2000. The MS fix is only available for Exchange 2003.

"Exchange 2000 Server and Exchange Server 5.5

If you are running Exchange 2000 Server, Exchange Server 5.5, or other earlier versions of Exchange Server, contact the Microsoft account manager or the Technical account manager for more information."

And in the cisco unity DST field notice it has "Exchange 2000 support has expired. No patch will be available without a separate Extended Hotfix Service Agreement. A customer would need to purchase this separately from Microsoft."

Not that it is an issue, since it is voice mail only, but I was just curious if anyone knew if MS had a fix under the extended hotfix service or not for Exchange 2000 before I refer people to call MS and see.