CallManager on Non-MCS Equipment

Awesome! I was just about to set up CM on an old box myself.
Sean

It runs on Windows 2K standard (non-advanced server), which is what the CallManager image is designed for.

Spoke too soon - Image loaded fine on VPC, but hangs on "Starting Windows".. Even in safe mode. Back to the drawing board.. Anyone else trying to get this to work on VPC/Virtual Server?

Excellent - thanks Steve for testing it out!

I managed to get a CM working on a generic PC with the instructions from the very first post. Mine too failed to re-boot, but then after turning it off and on several times it started the instalation again and I had no problems after that. It does however seam un-reliable. Needs re-booting several time a week due to services just stopping such as the CM TFTP service etc. I only use it in a lab environment to test so this isn't too big an issue. Anybody had similar experiences?
Does anybody have a copy of the latest CM?

First, thanks for the post. I've successfully loaded CCM on other machines using the reg hack, but they were never stable enough to even test with. But this way seems to be working so far. I've gotten it to work on a Dell Optiplex 520. I did have to make some changes though. I was getting caught up with the raid drives as Eric was.
Further down in the BAt file find the line ":IBMX345" the line below it calls batch file that determines the raid driver needed. Comment out that line by adding "REM". Worked for me.
Rich

Tim - The GX240 was actually the test machine I used to pull this off. It works great ;).

PANICKED!! Sorry, I was able to get it to work when I changed the autoexec to 7820. However, now it asks for disk 5?? Anyway, I will keep plugging away at it. (My cd set does not have a disk 5 - go figure) lol

Was the driver of the machine you were installing to blank, or did it already have an OS installed... I seem to hang each time after it says Please Wait While the Assisted Install loads...

Many thanks for this, I have created the floppy boot disk as described but looking on the floppy there is no autoexex.bat, could you tell me what I need to put in the file along with set XIMAGE=x345
goto IBMx345
Regards

A couple things - First, That's great info on stopping it from checking on the raid hardware. Thanks Eric!
Second - The OS install disks I used to test this are 2000.2.4 disks, which I then upgrade to the latest by the standard upgrade patches from Cisco.com. I have installed from these disks on MS Virtual PC, and a generic Athlon 64 machine I just built, which had a single 80 gig IDE drive in it (so yes, you can do it without a raid).
Keep in mind, theres a bunch of OS images - Cisco built one for each type of hardware the software is SUPPOSED to run on. Depending on what hardware you choose (ie, which "set" and "goto" you add into the autoexec.bat), it will tell you to insert the right CD (or DVD in the case of some of the disks, like disk 3 in my set).
The biggest trick is to find (by trial and error) an image that has a disk controller driver installed that is at least minimally compatible with the hardware you have, or at the very least, will allow it to boot, so that you can install the proper driver. In my case, during the first boot, it found several hardware devices (sound card, video adapter, game port, etc) that didn't have drivers loaded in the original image from the Cisco CDs. I just kept clicking "cancel" as quick as I could, so that the image load process would continue. After the image was loaded, and I could log into the machine, I loaded my drivers.
One other hint - I found that my load would fail if I didn't have power management enabled in the bios. I dont know if this is a definite, but it seemed consistent to me. All I can say is try all the installs 'till you get one working..
Anyone got a hint for getting one working on VMWare? I've done VPC, but I haven't tried VMWARE yet, and I need to do so soon...
Thanks, and good luck!
-Steve

Can you post you autoexec so I can compare with mine, I can not stop it searching for a Raid
Martyn

I'm having the same problem as Steve had, windows starts to load but then hangs at the starting windows screen and I can not even boot into safe mode
Any Ideas anyone
Martyn

Spoke too soon ... after the install, and during Win2K bootup, I get the BSOD with INACCESSIBLE_BOOT_DEVICE ... My goal is to install CCM 4.1(3) on a DL320 with SCSI/RAID drives instead of the IDE setup which Cisco typically installs based on the 7825 platform. I switched the autoexec.bat to load the 7835H03 image, though I got the same thing.
Any suggestions? Thanks,
joe

I managed to get 4.12 working on VIA ITX 800Mhz - very small and neat. It took me about 2 weeks of hacking but it was worth it. It's solid as a rock - I have had it running for over 6 months without a reboot. I also have Unity running on a seperate ITX machine. This hack was truly a nightmare - hacked for 2 weeks 12 hour days. Both are totally stable.
It can be done!

Hi I am stuggling to get this done I am have a acompaq DL360 Server and I cant get it work.
I have dowloaded the fdimage.exe on browsing the dvd disk1 I cant see the bootimg.bin file so I cant create the floppy disk.
I am trying to install 4.2(3)
Any help will be appreciated
Thanks

Harry,
Why do you not share your files with all of us?
Posted by: Harry at September 28, 2006 4:20 PM
I managed to get 4.12 working on VIA ITX 800Mhz - very small and neat. It took me about 2 weeks of hacking but it was worth it. It's solid as a rock - I have had it running for over 6 months without a reboot. I also have Unity running on a seperate ITX machine. This hack was truly a nightmare - hacked for 2 weeks 12 hour days. Both are totally stable.
It can be done!

Hi all,
like Bill and Scott, I too have the DVD disk without the bootimg.bin file. Is there any way to accomplish this trick?
Thanks a lot!

FYI - I stumbled across a site giving instructions on installing Cisco CallManager 4.x in VMWare:
http://www.knuckledragger.net/Network/ccm4vmware.htm

Dear all,
i use OS Version 2000 2.7a hardware detection CD ,after run "fdimage d:\bootimg.bin a:",I got file autoexec.bat:
@ECHO OFF
REM
REM Cisco MCS Build Process Boot-CD #1
REM
REM Last Modified On: 12/10/2004
REM
REM version: 1036 (move ServeRAID driver and config off this diskette)
REM version: 1035 (Added X346NoHT.exe to disable HTT on X346)
REM version: 1034 (IBM X345 using different ServeRAID firmware)
REM version: 1033 (Added support for 7835H04, 7835I02, 7845H03, 7845I02)
REM version: 1032 (Switched to new IBM hwdetect.exe and clini.exe utils)
REM version: 1031 (Updated for OS 2000.2.6)
REM version: 1030 (Added support for ServeRAID 6i and 7845I01)
REM version: 1029 (Added 7815I-2, 7825H-2, 7835H-3, 7845H-2 detection)
REM version: 1028 (removed unused files)
REM version: 1027 (Added support for X345, 867031X)
REM version: 1026 (Added support for model # 84793AX for 7815)
REM version: 1025 (Added support for Proliant 400 same as PS-720)
REM version: 1024 (Added partinfo back for X330's and sticfg for X330 -11Y detection)
REM version: 1023 (Added support for 7845)
REM version: 1022 (Changed partinfo to fdisk for x200 support)
REM version: 1021 (1018 and 1019 were not provided by Spirian. Added in 783G support)
REM version: 1020 (Added support for x200 changed all detection) eburgess
REM Version: 1017 (Added support for X342 and X33A)
REM Version: 1016 (Skips PCICFG on X340)
REM Version: 1015 (Added support for ServeRAID controller 4Lx)
REM Version: 1014 (removed MCS references)
REM Version: 1013 (IBM RAID Firmware Update Support2)
cls
set CDROM=S
set EXPAND=YES
SET DIRCMD=/O:N
set LglDrv=27 * 26 Z 25 Y 24 X 23 W 22 V 21 U 20 T 19 S 18 R 17 Q 16 P 15
set LglDrv=%LglDrv% O 14 N 13 M 12 L 11 K 10 J 9 I 8 H 7 G 6 F 5 E 4 D 3 C
echo PLEASE WAIT AS BOOT PROCESS COMPLETES
call setramd.bat %LglDrv%
set LglDrv=
set CDROM=S
set EXPAND=YES
set temp=%RAMD%:\
path=%RAMD%:\;a:\;%CDROM%:\;s:\win95;s:\win95\system;%RAMD%:\extract;
%RAMD%:
md encrpt
md win95
md Extract
copy s:\win95\*.dat %RAMD%:\win95\*.*
copy s:\win95\*.da0 %RAMD%:\win95\*.*
copy s:\win95\MCSboot.exe %RAMD%:\win95\*.*
copy s:\win95\mscom*.ocx %RAMD%:\win95\*.*
rem unrem the following for testing and put your MCSboot.exe on the a: disk
rem copy a:\mcsboot.exe %RAMD%:\win95\*.*
copy s:\win95\*.ini %RAMD%:\win95\*.*
copy s:\win95\eula.txt %RAMD%:\win95\eula.txt
copy s:\win95\ciscoe.txt %RAMD%:\win95\ciscoe.txt
copy s:\tools\wait4cd.bat %RAMD%:\wait4cd.bat
copy s:\tools\waitcd.exe %RAMD%:\waitcd.exe
copy s:\tools\cdgrab.exe %RAMD%:\cdgrab.exe
copy s:\tools\msgbox.exe %RAMD%:\msgbox.exe
rem copy s:\tools\restart.exe %RAMD%:\restart.exe
copy s:\tools\x340.txt %RAMD%:\x340.txt
copy s:\tools\halt.exe %RAMD%:\halt.exe
copy s:\tools\biosupg.txt %RAMD%:\biosupg.txt
rem copy s:\win95\command.com %RAMD%:\command.com
copy a:\command.com %RAMD%:\command.com
copy s:\tools\reboot.com %RAMD%:\reboot.com
copy s:\win95\restart.bat %RAMD%:\restart.bat
REM copy s:\tools\sysinfo.exe %RAMD%:\sysinfo.exe
REM copy s:\tools\syschk.exe %RAMD%:\syschk.exe
copy s:\tools\sticfg.exe %RAMD%:\sticfg.exe
copy s:\tools\sticfg.log %RAMD%:\sticfg.log
copy s:\tools\hwdetect.exe %RAMD%:\hwdetect.exe
copy s:\tools\clini.exe %RAMD%:\clini.exe
REM this is an HP Util named reboot.exe renamed to not conflict with reboot.com
copy s:\tools\reboot4.exe %RAMD%:\reboot4.exe
SET COMSPEC=%RAMD%:\COMMAND.COM
cls
if exist %RAMD%:\win95\mcsboot.exe goto CONTINUE
goto BADHW
:CONTINUE
SET XIMAGE=BADHW
:tools
s:
cd \tools
cls
echo =======================================
echo RUNNING HARDWARE DETECTION . . .
echo =======================================
REM CompaqDetect
REM Systype is a Compaq utility from their SmartStart Scripting Toolkit.
REM Ssstksys.ini contains the BIOS to error level setting for each Compaq Server.
REM Ssstksys.ini was edited to remove all not supported Compaq's.
REM Remember to put errorlevel in descending order.
REM 28 = PL1600 (MCS-7830)
REM 41 = PS720 (MCS-7820/22)
REM 50 = DL380 (MCS-7835-733/1000)
REM 63 = DL320 (MCS-7825-800/1133)
REM 68 = DL380G2 (MCS-7835-1266, MCS-7845-1400)
REM 80 = DL380G3 (MCS-7835H-2.4 / 3.0, MCS-7845H-2.4 /3.0)
REM 83 = DL320G2 (MCS-7825H-2.2 / 3.0)
REM 90 = DL380G4 (MCS-7835-H1, MCS-7845-H1)
REM 255 = Not Compaq Hardware
s:\tools\systype s:\tools\ssstksys.ini
if errorlevel 255 goto IBMDetect
if errorlevel 91 goto IBMDetect
if errorlevel 90 goto DL380G4
if errorlevel 83 set XIMAGE=7825H02
if errorlevel 83 goto 7825H02
if errorlevel 80 goto DL380G3
if errorlevel 68 goto OLDSrv
if errorlevel 63 goto OLDSrv
if errorlevel 50 goto OLDSrv
if errorlevel 42 goto OLDSrv
if errorlevel 41 goto OLDSrv
if errorlevel 28 goto OLDSrv
cls
echo =======================================
echo RUNNING HARDWARE DETECTION . . .
echo =======================================
:IBMDetect
REM Sysinfo.exe was provided by IBM
REM This is used to get the Model number
REM XTYPE = the 7 digit Machine Type / Model
REM XTYPE2 = the 4 digit Macine Type
REM OLD OS 2000.2.4 method
REM %RAMD%:
REM sysinfo >sysinfo.out
REM syschk sysinfo.out
REM Call sysinfo.bat
REM IBM Scripting Toolkit method
%RAMD%:
hwdetect.exe /i >%RAMD%:\hwdetect.txt
clini.exe %RAMD%:\hwdetect.txt /s:System /i:Machine_Type /e:XTYPE2 /b:%RAMD%:\IBMhw1.bat
clini.exe %RAMD%:\hwdetect.txt /s:System /i:Model_Number /e:MODEL /b:%RAMD%:\IBMhw2.bat
clini.exe %RAMD%:\hwdetect.txt /s:System /i:Active_Processors /e:XPROCESSORS /b:%RAMD%:\IBMhw3.bat
clini.exe %RAMD%:\hwdetect.txt /s:System /i:Processor_Speed_MHz.0 /e:CPUSPEED /b:%RAMD%:\IBMhw4.bat
Call IBMhw1.bat
Call IBMhw2.bat
Call IBMhw3.bat
Call IBMhw4.bat
SET XTYPE=%XTYPE2%%MODEL%
if "%XTYPE%"=="847931X" goto OLDSrv
if "%XTYPE%"=="84793AX" goto OLDSrv
if "%XTYPE%"=="867431X" goto OLDSrv
if "%XTYPE%"=="865411Y" goto OLDSrv
if "%XTYPE%"=="865431Y" goto OLDSrv
if "%XTYPE%"=="865441Y" goto OLDSrv
if "%XTYPE%"=="865451Y" goto OLDSrv
if "%XTYPE%"=="86561RY" goto OLDSrv
if "%XTYPE%"=="86566RY" goto OLDSrv
if "%XTYPE%"=="86694RX" goto OLDSrv
if "%XTYPE2%"=="8480" SET XIMAGE=7815I02
if "%XTYPE2%"=="8480" goto 7815I02
if "%XTYPE2%"=="8482" SET XIMAGE=7815I03
if "%XTYPE2%"=="8482" goto 7815I03
if "%XTYPE2%"=="8670" goto IBMX345
if "%XTYPE2%"=="8836" SET XIMAGE=7825I01
if "%XTYPE2%"=="8836" goto 7825I01
if "%XTYPE2%"=="8840" goto IBMX346
goto BADHW
REM ==============================================
REM HP Servers
REM ==============================================
:7825H02
call s:\tools\7825cfg.bat
copy s:\tools\conrep.exe %RAMD%:\conrep.exe /Y
copy s:\tools\HTT_OFF.cfg %RAMD%:\HTT_OFF.cfg /Y
%RAMD%:\conrep /L %RAMD%:\HTT_OFF.cfg
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK
:DL380G3
%RAMD%:\sticfg CPU_COUNT
REM Disable HTT
copy s:\tools\conrep.exe %RAMD%:\conrep.exe /Y
copy s:\tools\HTT_OFF.cfg %RAMD%:\HTT_OFF.cfg /Y
%RAMD%:\conrep /L %RAMD%:\HTT_OFF.cfg
IF "%XCPUCNT%"=="2" goto 7845H02
goto 7835H03
:7835H03
Set XIMAGE=7835H03
call s:\tools\783GRcfg.bat
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK
:7845H02
Set XIMAGE=7845H02
call s:\tools\7845Rcfg.bat
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK
:DL380G4
%RAMD%:\sticfg CPU_COUNT
REM Disable HTT
copy s:\tools\conrep.exe %RAMD%:\conrep.exe /Y
copy s:\tools\HTT_OFF.cfg %RAMD%:\HTT_OFF.cfg /Y
%RAMD%:\conrep /L %RAMD%:\HTT_OFF.cfg
IF "%XCPUCNT%"=="2" goto 7845H03
goto 7835H04
:7835H04
Set XIMAGE=7835H04
call s:\tools\783GRcfg.bat
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK
:7845H03
Set XIMAGE=7845H03
call s:\tools\7845Rcfg.bat
rem copy machine specific system.ini file
copy s:\win95\system.cpq %RAMD%:\win95\system.ini
goto FDISK
REM ==============================================
REM IBM Servers
REM ==============================================
:7815I02
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK
:7815I03
call S:\tools\HTT306.bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto PARTINFO
:7825I01
IF "%CPUSPEED%"=="3400" goto BADHW
call S:\tools\HTT306.bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto PARTINFO
:IBMX345
REM Disable HTT
a:\IBMNoHT.exe
IF "%XPROCESSORS%"=="2" goto 7845I01
Set XIMAGE=X345
Call s:\tools\IBMRAID7.Bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK
:7845I01
Set XIMAGE=7845I01
Call s:\tools\IBMRAID7.Bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK
:IBMX346
REM Disable HTT
a:\X346NoHT.exe
IF "%XPROCESSORS%"=="2" goto 7845I02
Set XIMAGE=7835I02
Call s:\tools\IBMRAID.Bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK
:7845I02
Set XIMAGE=7845I02
Call s:\tools\IBMRAID.Bat
s:\tools\stistate.exe
copy s:\win95\system.ibm %RAMD%:\win95\system.ini
goto FDISK
REM ==============================================
REM Get Partition information
REM ==============================================
:FDISK
REM Used to determine the state of the hard drive based on the partitions.
s:\tools\fdisk.exe /info /tech > %RAMD%:\part.txt
s:\tools\fdskpart.exe
cls
goto COMMON
:PARTINFO
REM IBM X330, X206, and X306 do not work correctly with fdisk still using partinfo
REM They run extrememly slow and do not load the Win95 shell or run Drive Image Pro.
REM Used to determine the state of the hard drive based on the partitions.
s:\tools\partinfo.exe > %RAMD%:\part.txt
s:\tools\stipart.exe
cls
goto COMMON
:COMMON
a:\smartdrv.exe %RAMD%+ s 1024 1024
MsgBox "PLEASE WAIT AS THE CISCO SERVER" "AUTOMATED SETUP CONTINUES TO LOAD"
%RAMD%:
goto end
REM ==============================================
REM Error Messages
REM ==============================================
:HALT
%RAMD%:\cdgrab e s > nul
%RAMD%:\stinocad
%RAMD%:\MsgBox /T:%RAMD%:\Hwout.txt /w /B:BLUE /F:WHITE
%RAMD%:\halt.exe
:OLDSrv
cls
copy a:\OLDSrv.bat %RAMD%:\OLDSrv.bat
cls
set comspec=%RAMD%:\command.com
cls
call %RAMD%:\OldSrv.bat
:BADHW
cls
copy a:\end.bat %RAMD%:\end.bat
cls
set comspec=%RAMD%:\command.com
cls
call %RAMD%:\end.bat
:end
I try "set XIMAGE=x345 goto IBMx345","SET XIMAGE=7815 goto IBM7815" and "set XIMAGE=7830 goto CPQ7830",and all three methods
do not work.
Would you pls tell me how to change the above autoexec.bat file?
very thanks your help!!

Hi all
Was anyone successful in installing CCME 5 on non Cisco hardware?
Thanks
Bruno

I'm trying to install 4.1(3) under VMWare, ... I was able to get around the RAID error by commenting out the "Call s:\tools\IBMRAID7.Bat" line.
I had to manually partition the VMWare partition - used fdisk.exe which the CCM install has conveniently located in the CDROM's tools\ directory.
Problem now ~ I can get to where the GUI comes up and asks if you want to continue ... Then a small blue window pops up saying "preparing base image" and the install hangs.
Wondering if maybe I need to format the VMWare partition before attempting the install??? Will try that next.
It's painfully slow waiting for the GUI to come up ... the "Cisco Systems Empowering the Internet Generation" graphic stays up for about 20 minutes.
Thanks in advance,
Joe

Hi All,
Well I have been getting the opposite with regards to VMware. First off, I have configured the image as IDE, so at this time I don't need to worry about SCSI drivers and a-like.
When I get into the MCSboot with no partitions configured I get the blue windows, where it hangs and stops responding, but when I have configured partitions and formatted them it hangs as it boots win95 and doesn't even get to the MCSboot.
What would really help is if someone could acquire the drive.ini file from a working install of a flat build or even a complete build. I am thinking this is the main crocks of the problem as this is the file used to tell MCSboot how to configure the partitions or even how they are configured. But I might be pissing into the wind here!
If anyone could do this for me and needs help, please let me know. It only needs someone to put command.com at the end of the autoexec.bat file and copy the drive.ini from the Ram disc.
Many thanks,

HERE IT IS >>> The WORKING VMWARE INSTALLATION INSTRUCTIONS!!! WOOHOO!!!
Step 1: Download a Windows utility called FDIMAGE.EXE. This is typically used to create floppy boot disks from disk images for BSD/Linux. I've attached it ... Rename the file to fdimage.exe
Step 2: Pop in in the CallManager Hardware Detect CD-ROM (Disk 1) into your PC
Step 3: Put in a blank floppy disk
Step 4: Open a command prompt and type "fdimage d:\bootimg.bin a:" this copies the boot image from the CD-ROM to the floppy disk
Step 5: On the floppy disk, edit the autoexec.bat file (I'm having flashbacks to the MS-DOS days)
Step 6: Find the line in the autoexec.bat file that says "s:\tools\systype s:\tools\sssksys.ini" This line is right before the boot process does the hardware check to see what sort of server you have
Step 7: Hit enter after the above line and add the following two lines:
set XIMAGE=x345
goto IBMx345
Step 8: Add a REM statement to the IBMRAID7.Bat line under the Set Ximage=X345
Set XIMAGE=X345
REM Call s:\tools\IBMRAID7.Bat
Step 9: Save the file
Step 10: Using the CD Burning software of your choice (I used Nero version 6), use the extracted contents of the BOOTIMG.BIN (on the floppy you just created) to create a new bootable Hardware Detect CD.
Step 10a: Copy the contents of the Hardware Detect CD to a folder on your hard drive. DO NOT COPY THE BOOTIMG.BIN FILE!!! We're going to use the modified files extracted from the original BOOTIMG.BIN in step 4, and burn those back onto the new CD-ROM. Here's what the directory should look like ...
Arco (directory)
Erase (directory)
Extract (directory)
Images (directory)
Raidbio7 (directory)
Raidbios (directory)
Tools (directory)
Win95 (directory)
2000_2_7 (filename)
Bootcat.bin (filename)
Remove CD.
Step 10b: Insert blank CD-ROM. Make sure that the boot floppy created in Step 4 (with the new autoexec.bat) is in the floppy drive.
Step 10c: Start Nero, and under "New Compilation" select CD-ROM (Boot). Under the "Boot" Tab, "Source of boot image data" make sure to select "Bootable logical drive (must fit on the CD!)" Under the drop down, make sure that your floppy drive is selected "A:\1.44MB"
Step 10d: On the left side of the screen, click "New"
Step 10e: Nero will now bring up a split screen, with the right side showing the contents of your computer, and the left side showing the contents of the CDROM. Double click on the folder you created in step 10a. Drag the contents of the folder (not the folder itself!) over to the CD-ROM
Don't worry - You won't see the BOOTIMG files here as this point. You should see all of the folders, and two files listed in Step 10a Under the "ISO1" on the left side of the screen.
Step 10f: Select Recorder, Burn this Compilation. Under "Action" make sure that "Write" and "Finalize CD" are selected. Click on Burn.
As long as your floppy disk created in Step 4, with the new autoexec.bat from Step 5 is in the floppy drive, Nero will begin copying the boot files from the floppy back onto the new blank CD. Once that part is complete, Nero will then copy the contents of the original CD off of your hard disk from the folder created in Step 10a.
Once this is complete you will no longer need the boot floppy. This will DRAMATICALLY speed up the installation process, vice using the floppy.
Step 11: Create a new Virtual Machine in VMWare.
Step 11a: For Virtual Machine Configuration, select "Custom". For Guest Operating System select "Microsoft Windows" and version select (believe me on this one) Windows 95.
The install shell that Cisco uses for the Hardware detect CD runs on a stripped down version of Win 95, and if you select Win2K, the install will hang.
Select next, and provide whatever VM Name and location you desire.
Select next, and uncheck "Make this VM Private" ... unless you want it private.
Select next, and Run this VM as user that powers on the virtual machine. The assumption is that you will power it up with Admin Rights, and this requires no change.
Select next and number of processors = 1
Select next and set "Memory for this VM" as 1024 MB. Very Important for CCM 4.1(3)
Select next and select "Use Bridged Networking" (default)
Select next and leave I/O Adapter Types set to ATAPI and BusLogic
Select next and "Create New Virtual Disk"
Select Next and "Virtual Disk Type" is IDE (NOT SCSI)
Select Next and Disk Capacity - Assign a MINIMUM of 8GB. Select Allocate Disk Space now for optimal performance.
Select Next - Disk File - Enter in a descriptive name for the VM files. CCMPUB.vmdk or whatever ... It will default to Windows 95.vmdk, so I suggest changing it.
Select Finish
Step 12: Insert the newly created bootable CD-ROM from Step 10f. Start the VM. Follow the wizard to blow the Windows 2000 image onto the non-MCS machine. It will prompt you for the OS Disk 3 (I'm using DVDs - it's DVD #3 of the OS install for me). You will need a DVD Drive for this ... Once the install detects the DVD, you'll get the "Power Quest Drive Image Pro" application, and the OS will be imaged on to the VM.
DANGER WILL ROBINSON!!!
After the windows install appears to be complete, you will be given a "Found New Hardware" box. DO NOT CLICK INSTALL NOW!!! CLICK CANCEL. DO NOT CLICK "Reboot Now" when prompted by the "Windows has finished installing new devices" dialog box.
WAIT WAIT WAIT until the OS Install completes the "Writing System Configuration" and it will reboot the VM all by itself.
Step 13: After Windows comes online, login and install VM tools. This will install the appropriate video and NIC drivers.
Step 14: Pop in the Cisco CallManager CDs and proceed as normal! This rocks!
Of course, this is only in a lab environment. The great Cisco powers that be would definitely frown upon a TAC support call from a Cisco 4.1(3) CallManager running on a VM Instance.
Start to finish, once you have the new Hardware Detect CD from Step 10, The VM Install took me about 2 1/2 hours ... the longest part being the actual CallManager CD1 & CD2 install.

Hi Mark
Thanks for the detailed explanation above
I wonder if you can help
I got to the stage 12 too insert OS disk 3,I inserted the second disk which is a DVD and it wont have it just says wrong media and ejects it.
I am installing version 4.1(3) on a HP DL360G3 and the disks I have are OS CD1 2000 2.7 and OS DVD2 2000 2.7
Please any ideas on how I can get this installed?
Cheers
Chays