Let's Collaborate Like it's 2005 - Cisco Unity 4.0(3)

This time, we're going to be setting up Cisco Unity 4.0(3). If you are following along at home (why would you subject yourself to this???), I've posted the entire disk set over at archive.org. Also, you're going to want to reference the Installation Guide (and you probably want to pay a little closer attention than I did in my new video). I definitely feel like I probably added some additional pain to myself.

The general process is this (if on VMware):
  • Create a Windows 2000 Server Virtual Machine (you can find the ISOs on archive.org)
  • Install KB835732 (required for VMware Tools)
  • Install VMware Tools
  • Run the "Cisco Unity System Preparation Assistant" (cuspa\cuspa.vbs on the Unity Service Packs CD 1)
  • Install SQL Management Tools if using MSDE
  • Set IP Address, join Domain
  • Install Exchange Management Tools
  • Extend AD Schema (ADSchemaSetup\ADSchemaSetup.exe on Cisco Unity CD 1)
  • Create any OUs and additional Mailbox Stores that you need
  • Create and configure Unity Accounts (UnityInstall, UnityAdmin, UnityDirSync, UnityMsgStoreSync)
  • Run the "Cisco Unity Permissions Wizard" (Utilities\PermissionsWizard\PermissionsWizard.exe on Cisco Unity CD 1)
  • Set Exchange Permissions
  • Install Microsoft Certificate Services
  • Install Unity (Setup.exe on Cisco Unity CD 1)
    • Configure CallManager Hunt Groups/Route Lists/Route Patterns and VoiceMail settings. See the Integration Guide here.
  • Installing Cisco Unity 4.0(3) Service Release 1
  • Installing the Microsoft Updates Recommended
  • Configure SSL
(don't consider this an exhaustive list, I'm sure I've missed a bunch of things - please utilize the Installation Guide linked above)

Obviously we are going to skip all of the virus scanning and hardening steps. This is Windows 2000, after all. I don't think there is enough security in the world to keep you safe from bad things. So, make sure to limit access to your environment, and don't do anything too crazy.

Comments

Post a Comment

Popular posts from this blog

Installing Cisco CallManager 4.1(3) on VMware in 2025

Getting Creative Again – and Reinstalling 2005 in 2025 It’s certainly been a while—and a lot has changed in my life. But I’ve been wanting to get back into more creative projects, especially the kind that mix creativity with something deeply technical. This one definitely checks both boxes. Get ready to Collaborate like it's 2005! Please check out my YouTube video . Installing Cisco CallManager 4.1(3) on VMware in 2025 When I first had this idea, I figured it would be a quick weekend project—knock it out in a couple of days and move on. Many months later, I can finally call it a success. The Classic Method (That No Longer Works) Historically, you'd follow a guide like this one to install CallManager 4.x. It relied on: Installing vanilla Windows 2000 Server Modifying the registry to bypass hardware checks Applying Cisco OS update files like win-OS-Upgrade-K9.2000-2-6sr4.exe But in 2025? These Cisco OS update files have vanished from the internet. Despite...
Read more

Retro Lab Design and Configuration

Image
I covered some of this in my last video , but I can include more of the boring details here. Let's start with the overall topology - for context "Nexion" is my retro ISP, and Pinnacle Dataworks is my first retro customer: Full configurations are referenced at the bottom of this post. My goal for Pinnacle Dataworks was to build a network that could have existed in 2005, and I got somewhat close. According to this press release , the Cisco 3825 router was scheduled to begin shipping in October 2004. The IOS version is slightly too new, dated in 2006, but I couldn't find a version that included voice features that had a 2005 (or earlier) date on it. The 3524-PWR switch had been announced in 2000, so it was well established by this point. And running a software version from 2004 works for me. I've since procured a slightly more time-relevant device since then, but this will do for now. In terms of phones, I'm rocking the 7940, which was also announced in 2000, ...
Read more

Why is Cisco Licensing so terrible?

Well, it's been a while since I've written anything here. Since my last post, a lot of things have happened. One of those things perfectly illustrates a poorly thought out aspect of Cisco Licensing, especially for Unified Communications running on VMware. I've believed forever that using the Primary DNS and NTP servers as part of the License MAC generation was a bad idea, but I never really thought about how unpleasant it could be. I recently traveled to Brazil to deploy our UC-on-UCS environment there, and built out all of the servers. When I first arrived onsite, I contacted our systems team and requested they send me the DNS/NTP information that I would need to use for the build (and licensing). They sent me the information without any hassle, which was a huge bonus. Fast forward, installation is done, I'm back home, and I set up RTMT. Low and behold, I'm getting alarms that the Primary NTP server is inaccessible. Hmmm, that's odd, but sure enough, I can...
Read more