Quote:
Originally Posted by knottyrope
Did you get the new server or find a workaround?
|
Since I have a Domino Express license (which lets me put Domino on any number of servers as long as I don't use clustering or failover - or so my sales rep says), I found (read "stole from another group") an available server to run SameTime on. I had no Win2K3 Server license available, but no worries - I installed CentOS 5 (repackaged RedHat ES 5), installed Domino for Linux, and prepared to install SameTime 8 for Linux.
Lo and behold, the SameTime for Linux install crapped out with a "This software is incompatible with this operating system" error. Yes, Sametime Linux would not install on Linux. Go figure. After some serious Googling, the workaround for that was to "export SkipOSCheck=true" before starting the install. Worked like a charm. It turns out the install checks the /etc/redhat-release file, so I could have changed the text there just as well.
So now I have SameTime 8 on a CentOS 5 server running Domino 8.0.1. It took a while to get the address book replication working properly, and I had to dig thru the BES Manager menus to find the spot to change the SameTime host name, but we're back on the air. Now I'm working on distributing OS4.5 to the handhelds.
Oh - one other thing I noticed specific to Domino and BES. Our NOC sends out status messages to BlackBerries and cell phones (via SMS). I noticed that after the upgrade to SP4.1.6, some messages were not handled by the BES properly (users got the same red failure message as they got when I shut off PDF processing).
Turns out the error was caused by two new users in the NOC having their Notes database design at v8.0.1, where everyone else's design was still at 7.0.2. The upgraded nsf design impacted the memo template used for the notices, turning the ones destined for BBs into HTML mail and the ones going to cell phones into MMS instead of SMS. It took the better part of five days to figure that mess out.