CallManager install registry hack

[Ryan Haskell]

Hello gang! Does anyone know the registry hack that will allow you to
install Call Manager on a non-Cisco-approved platform? I know there's
one out there, as it was mentioned to me by a Cisco CIPT instructor.
Apparently the Sti install program does a registry check prior to
installation, and if it doesn't find the proper value in the registry
indicating that the platform is a Compaq DL-380 or other approved box,
it kicks you out of the install.

Thanks!
ryan

[Erwin]

Ryan Haskell <ryan_h...@hotmail.com> wrote in
news:e426fc0.02110...@posting.google.com:

I dont know the hack, but you can try running Regmon from
www.sysinternals.com parallel to your install.
Regmon will track all registry actions, maybe it will point you in the right
direction.

Erwin

[Geoff Zinderdine]

If you are installing on non-standard hardware, run the install from the cmd
prompt:

stistage /o

I am not sure this works on later version of Call Mangler, but it does for
3.1
You need to have SQL7 installed before you install it as well.

HTH,

Geoff Zinderdine
CCIE #10410

"Ryan Haskell" <ryan_h...@hotmail.com> wrote in message
news:e426fc0.02110...@posting.google.com...

[Simon Threlfall-Searson]

Building a Cisco Call Manager or Other AVVID System on Non-Cisco 'Blessed'
Hardware

1.. Install Windows 2000 Server or Advanced Server.
2.. Do not make the server a member of the domain, and do not set a
password for the "Administrator" account.
3.. Install Windows 2000 SP1 and the Virtual Memory Patch, located at
http://www.cisco.com/cgi-bin/tablebuild.pl/callmgr
4.. Stop the SNMP service
5.. Add the following registry items (Adjust the Speed and Memory values
for your system:
1.. HKEY_LOCAL_MACHINE\SOFTWARE\CISCO SYSTEMS\MODEL
2.. "Hardware"="MCS7835"
3.. "Memory"="1024"
4.. "Speed"="733"
5.. HKEY_LOCAL_MACHINE\SOFTWARE\SPIRIAN
6.. "ProductKey"=" BTOOVQESCCJUIEBI"
7.. "Deployed"="0000000000000100"
6.. Start the SNMP Service
7.. Install Call Manager (Version <3.1) from CD
8.. If DC Directory Errors
1.. Stop DC Service
2.. Open command prompt
3.. cd c:\dcdsrv\bin
4.. run cleandsa
5.. start DC service
6.. run avvid_cfg XX CCM03YY (XX = CM Server Name, YY = CM Major
Version) (i.e. for CM 3.08, avvid_cfg CMTEST CCM0330)

"Ryan Haskell" <ryan_h...@hotmail.com> wrote in message
news:e426fc0.02110...@posting.google.com...

[Ryan Haskell]

Thanks to all! Works like a charm....

R