These notes fill in the steps, notes and gotchas, not in the ShoreTel Implementing Guide.
Run Builder:
- Make sure the JRE has been renamed to jre.exe.
- Make sure to rename your 2008 Server DVD to WindowsServer2008.iso
(Otherwise, the script might not recognize it, even though it's supposed to get any iso and check.)
- Inside, the lf-fastvm-8591.pkg folder, verify the fast-vm.props file is the ShoreTel one.
- Don't change the Workgroup name like you normally would after the first boot. (We did change the IP address though to fixed the 2nd time completely through below during the VMware Tools install - that was a good "safe" time.).
(Check the Status screen, it might be still installing the features. But you don't see anything happening in the VM console.)
- The installing % for the Windows Server OS takes about 45 minutes.
- The installing of VMware Tools takes about 10 minutes. (Most of the time appears to be a reboot.)
- The installing of the server's services "features" and configuration takes over 30 minutes.
("Application Server", "AS-Ent-Services" feature, "SMTP-Server", "Web-Ftp-Publishing", "Web-ASP", "Web-CGI", "Web-Includes", "FS-FileServer", "Web-Server", "AS-Web-Support", "MSFTPSVC", Post-VM Creation Script, VM settings, etc.)
- If you get stuck at 0% for over 5 minutes, you're dead. Don't wait any longer. However, don't uninstall either, you'll just end up with multiple ShoreWare Server VMs which then cause a name conflict upon subsequent installs.
- If you did uninstall Run, then also kill the Virtual Machines folder's ShoreWare Server files (lf-virtualization/filesystem/var/lib/vmware/Virtual Machines). Then do a normal install of Run, the VMware 2 add-on, and then Run Builder again.
Instead, leave Foundations alone, and jump-start the dead vm:
1. Open up the VMware Web Access client:
http://<ip>:8333
2. Remove the ShoreWare Server from inventory but LEAVE the files.
3. Add the Virtual Machine back into inventory. Verify the two CD/DVD drives and the Floppy have images assigned. See image:
4. Click the Play button.
5. Open up the console and wait.
6. After the first reboot, switch back to watching the features install.
Lotus Foundations Application Environment for UC2 (UCC NVS) Package:
- This one is as simple as it should be. Simply install it on the Software Update page and wait for the installation incomplete message.
(which is a good message in this case)
- Takes about 5 minutes. Proceed to the ShoreTel specific package below.
ShoreTel for IBM Lotus Foundations Package (e.g. autoinstall/lfreach-shoretel-8939.pkg)
Go to the status page, and wait/watch the install status for the add-on:
- Wait for SW.zip to unzip. (almost 10 mins)
- Wait for msiexec for ShareWare (0-45 seconds of 20 minutes - this one says so)
- Wait for ShoreWare Server moved files (45-585 seconds of 20 mins)
- Wait for Changed root password (585 seconds)
- Wait for Upgraded database (585-615 seconds)
- Wait for Created MySQL root account (615-645 seconds)
- Wait for Changed CDR update status (645-680 seconds)
- Wait for ShoreWare installed (Windows reboot...)
The add-on will display the reminder:
- You will not see the CTI services as in the Guide. Instead, you will see an appropriate reminder on the status screen.
- "Reminder: new ShoreWare version may require switch and phone firmware upgrade"
Your not done, keep waiting...
- As you will see the message that the CTSA is installing and then installed.
- As you will see the message that the Launch STCOMM is installing and afterwards that its script files are being removed.
- As you will see the message that its Pushing the Endpoint files to Windows.
- Keep waiting until you see that "All components are installed successfully". (Final time was under 40 minutes.)
Once the ShoreTel add-on completes, the Lotus Reach ST server will put a message that it is rebooting.
- Wait another 5 minutes for the Server not running message to go away.
Now, per the Guide, reboot the whole Foundations server so that the ShoreTel Server VM can take over CPU 4 (3 in the GUI since the number starts with 0).
- Click the Reboot button at the bottom of the Status page and wait another 5 minutes for the VM to shutdown and the Foundations server to reboot.
Besides documented setup, there is:
1. Need to give ShoreWare VM static IP.
- When you change the IP address, leave in the DHCP address and add the new static one. Otherwise, you'll get annoying messages that you cannot update the configuration.
(That you are not an admin.)
- Change it in the web administration to the new address.
(Administration --> Application Servers --> HQ --> Edit IP address field, test ping, and save.)
- This also seems to cause issue with 3 tasks which spike and stay spiked as part of the errors, we ended up reinstalling from Run up to fix and simply changed IP address as soon as the VM was built and we could login (while it was copy install packages).
2. Need to change its Workgroup
- Don't change the VM's hostname, that is hardcoded. You are stuck with what you got, which isn't bad.
- Adding the DNS suffix seems to be safe.
- Do reboot.
Logins:
Director web interface: admin and changeme
VM administrator: Chang3Me
previous page
|