Knuckledragger’s Treehouse

Getting Cisco Call Manager 4.0x to run under VMware is fairly easy if you have half a day to kill and a lot of patience.

You’ll need to build a clean Windows 2000 Server virtual machine capable of 512MB of RAM minimum with 2 SCSI drives. I typically choose the LSI Logic SCSI controller with Windows 2000 which has proven very stable. The first virtual drive should be sized to 6GB minimum and the second drive should be at least 2GB.

Visit the Download Center at the LSI Logic support website and download the LSI20320-R SCSI Adapter drivers. Unpack the .zip file to your host drive. Also unpack the .zip files inside the original .zip file.

Copy the LSI Logic drivers either to a floppy or make a floppy image to attach to the virtual machine.

Follow the normal Windows 2000 Server installation procedures, and remember to hit F6 during the first boot to add the LSI Logic mass storage drivers, or you’ll get an error that no drives were found.

During the network phase of the install, give the server a static IP address. I typically run DHCP, WINS and DNS on the Cisco Call Manager server, so I point the DNS and WINS entries at the IP address I assign the server. If you have another WINS or DNS server, feel free to enter those addresses instead.

When prompted to select which options to install, select the following (If an option isn’t listed, make sure it is unchecked):

Remember to select Remote Administration mode for Terminal services when prompted during the installation.

After the server completes the final reboot, login and perform a search on Google or another search engine for the file MSJAVX86.EXE. This is the Microsoft Java Virtual Machine. It is required for the DC Directory installation phase. If you fail to install it now, you won’t find out until 40 minutes into the actual Cisco Call Manager installation that DC Directory cannot extend it’s schema. This file is no longer supplied, maintained or available from Microsoft directly.

Add the following keys and values to the Windows registry via RegEdit or RegEdt32:

Reconfigure the CD-ROM drive as drive E:

Partition and format the second SCSI drive as drive D:

Run the Cisco OS 2.6 Upgrade and reboot the server when requested - you should see 2 phases during the Express Install

Once the installation has completed and the server has been rebooted, rerun the Cisco OS 2.6 Upgrade. This time you will see 3 phases. If you fail to run this upgrade twice, the Cisco Call Manager installation may complete successfully, but services and additional installation options (i.e., BAT, CAR, etc.) will not run correctly.

After completing the second run of the Cisco OS 2.6 Upgrade, run the Cisco OS 2.6 SR5 Update and reboot the server when requested.

Open System Properties (right-click My computer, then properties or System in Control Panel) and select the Network Properties tab. Click the Properties button and then the More button. Enter the DNS domain name for the server. Click on OK a few times and reboot the server when requested.

If you are installing WINS, DNS or DHCP, configure these services.

Run the Cisco Call Manager installation from the first CD and follow the normal Cisco Call Manager installation procedures.

After the Cisco Call Manager reboots the server, you should have a functioning Cisco Call Manager server.

NOTE: If you installed Cisco Call Manager 4.01, also install the Cisco Call Manager 4.02a Update, as well as the Cisco Call Manager 4.02a SR1 Update. The SR1 update resolves a number of issues, including a problem that affects running TAPS and the Auto Attendant on the Cisco Call Manager server if you decide to use those options. TAPS in 4.02a without the patch fails to upload the TAPS.aef script into the repository if you install Extended Services 3.5(1) or 3.5(2).

This entry was posted on Sunday, June 13th, 2004 at 19:46:31 and is filed under Technology. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.