RE: Sametime Complete small deployment Ben Williams 20.Mar.15 06:36 AM Lotus Notes Sametime Standard 9.0Linux
They have a Community server so you need to firstly install DB2 and then the SSC and register the current Community server with the SSC. Hold on, if they have a community server and no SSC or DB2 then they are running a version older than 9 so probably 8.5x. You will need to upgrade the Community server to 9.
Now you can decide what you want to do.
I don't see why you would need to cluster the CM for 100 users. If you cluster a single component and the Community server dies then you don't have HA.
You should expand on what use cases they have. They have chat at the moment, what do they want to achieve next? There's no problem deploying in stages but you need to understand what each component offers otherwise you cannot plan accordingly.
For example. Do they want to have AV point to point and are not interested in multiway? Do they want multiway AV but not in the context of a meeting? Do they want AV in a meeting with screen sharing and presentations which comes from meetings? Do they want to be able to use mobile devices?
You haven't mentioned whether this is going to be a production server or whether the customer expects this to function "properly" as opposed to being a demo system.
For 100 users I wonder whether this is over kill. You are going to need a number of hosts to provide them with a smoothly running service. Is the time and thus cost to them worth it? Can they not continue to use Sametime 220.127.116.11 for chat removing the need for an SSC and DB2?
Sametime 18.104.22.168 has a lower foot print as there is no stipulation for two servers (VMGR and VMCU) to run on their own hosts meaning colocation is easier and the footprint is lower BUT you miss out on some nice AV features and it won't be future proofed.
Personally I'd be looking for use cases to justify ST9. If there aren't any justifications then maybe they should stick with what they have?