If there is one thing in Group Chat that is similar to OCS, it's definitely the icons. If you were not aware, the Group Chat functionality was an acquisition of a company named Parlano in the summer of 2007. Because of this, the integration with the rest of OCS R2 isnt quite where I would expect it to be. I expect in future SP's and versions this will become more tightly integrated.
A note, on Group Chat pre-requisites. I did this install on my existing standard pool which is not recommended. It should be on a separate server.
This is a screenshot of the IIS features I have installed. I have not yet found any article on group chat pre-requisites on a fresh server. I will need to do this soon and update this post.
I will review OCS 2007 R2 Group Chat in three or possibly four parts.
- Server Installation
- Administation Installation and configuration
- Client deployment
- Usage, recomendations
Lets dig in with the Server Setup.exe. I wish that this was more OCS integrated from the start. We begin with a VERY non MS DOS window. This launches the Group Chat Server install, that looks and feels familiar.
From there, Accept terms, enter user/company, choose features… two choices, Chat Server and Compliance Service. Both install by default.
Get a warning about MSMQ not being installed. This might be due to my eval install rather than real standard. Either way, if you plan on using Group Chat, or archiving/monitoring, you need MSMQ.
And then…. I am removing backup files:
And I did this twice to be sure. Yep, that's a window popping under to install. And "Server configuration" with a new icon. Of course, these are the pains of integrating Parlano, whom Microsoft acquired only 2 years ago.
Choose server and DB name:
Note here: You do need to manually create this Database.
Next screen, you can choose a different DB for compliance (likely policy recommended)
I chose the same for technical ease.
It's around this point I noticed the menu on the left gave no knowledge of how many steps remained. Not a big deal, but would be nice to see that the list has a start and a finish.
Here is where we set our Super Users:
Enter your OCS pool name, then choose Browse to select the MTLS cert to use.
The next few screens, I am setting a few service accounts up. For simplicity, I used my Domain Admin account for most of these. In a production environment, I would ABSOLUTELY have separate accounts for these.
For some reason, the browse button on this dialog was not working for me. Not a big deal. This should be a UNC path. I made it on the same machine for my instance.
I did not delve into the Compliance Adapters at all.
Next screen was Web Service Settings. Same deal on the UNC share:
Final Overview before hitting Install:
When you hit Finish, you will be alerted if any of the service accounts are granted the log on locally or log on as a service right.
Then we flip back to the MS installer and we are done!
Once this is installed - you will only have the OCS R2 Group Chat icon in your administrative tools.
Launching this allows you to view status of services and stop/start them as well as modify the service accounts.
I am not yet sure why the Web Service is listed as stopped. The W3SVC is running in the Services control panel, however.
Within this, File - Configure Server Settings allow you to modify pretty much ANY of the settings you specified in the installation. I am not going to review each of these, as I think it would be repetitive.
Next up - the Administrative Tool!