Pam Assivero 5.Jun.14 01:37 PM a Web browser Sametime Standard 8.5.2 IFR1 Windows
I've posted on this off and on over the past several months as I gather information to do this. However, we're now there and I'm trying to figure out the best way to go about moving ST and whether or not to upgrade.
Presently we have Sametime Classic Meeting server running on Domino 8.5.3FP3 on Windows 2003 on a physical server. We've begun our ND9 upgrades and have already moved our two main mail server, as well as our Traveler/iNotes server to ND9, all on Win2008R2n 64-bit, all in virtual environments. My next server is the Sametime server.
My build information is:
Sat Nov 5 19:45:01 EDT 2011
Date=Sat Nov 5 19:45:01 EDT 2011
I know that Classic Meetings are not available in ST9. We really only use the server at this time for chat and meetings. We don't have any audio/video functionality due to bandwidth.
I see two possible scenarios.
1. Install the same version of Domino and Sametime on the Win2008 VM and don't upgrade.
2. Bite the bullet and upgrade to ST9 on Domino 9.0.1 as the rest of our servers.
Starting with scenario #2, what are the minimum components I require to run ST9 allowing for possible changes in corporate needs and moving to allow audio/video. And is there any documentation for this setup.
If I stay with scenario #1, what's the easiest way to go about doing this. I know that ST is a 32-bit application but it can be installed on a 64-bit OS. Could I copy the entire data folder over to the new server, maintaining the folder paths, and then install Domino, and install ST? I did something similar when moving our Traveler server as per IBM documentation. I would have to take staddin out of the Tasks line in the notes.ini in order to bring up Domino before installing Sametime and let that run for a little bit. Then install Sametime and keep fingers crossed that it will work.
I usually rebuild my servers using a temporary server ID and then when I'm ready to move it into production, update the server ID, notes.ini, IP address and host name.