Earlier, in Part One, we installed Group Chat Server and now it is time to install the administrative tools. I have already done this a few times and ran into some oddities, that hopefully I can help you not run into!
In this instance, I am installing the tools on my OCS Standard pool server (which is also my group chat server) We can begin by running the 'AdminSetup' installer.
The installer will warn you if you do not already have MS Visual C++ redistributable installed. If you run their installer of this, do note, you will be cleaning up the root of your C drive.
Icky. Easy enough to clean up though. Once this is installed, its easy to click through all the defaults and complete the Admin tool console install.
Once installed, we can launch the Admin tools console. The "proper" name doesn't fit in the start menu, really.
So I attempt to logon:
I see "Connected to OCS server" and then I get this:
"Cannot sign in because of a problem with the chat room service. If the problem persists, please contact your system administrator"
Time to not trust Automatic Configuration. I will come back to this in the client deployment some more, but for the admin console, a manual configuration is OK.
Choosing Edit Accounts here, I made a new Account and used the below settings:
I then chose the Domain.com account and signed in without error. In the screen above, the Host is my OCS std pool, the domain.com is my AD FQDN and note the capitalization on Administrator to match my SIP URI.
Now that I am in the tool - lets create a test channel and set it up.
File>New>Chat Room brings up this dialog:
This gave an error. Channel names cannot have spaces. I removed this moving forward.
Once the room is created you need to add members to the channel. Since this is a lab domain, I decided to add my members to the Root of the server. In a production environment, I would likely be much more careful about security.
Now, Part 3 will come soon, and discuss the client installation, but I will give a brief preview here as the client is obviously needed to test this.
Here, you can see presence integration.
That's all for now. Check back soon for the client deployment, which I hope to include GPO settings to configure the client as well.