OCS Management on Steroids

PowerPack Main Tree ScreenShotIf you have Office Communications Server 2007 there’s a new must have tool for you: OCS powerpack for PowerGUI just posted by Curtis Johnstone: it is free, totally based on PowerShell (you can see the PowerShell code behind each and every node, link, or action), and has a lot of functionality not present in the native OCS MMC. Just see the console tree screenshot to the left!

Here’s a quick walkthough of the key features of the pack:

View and Provision OCS settings on users:

  • View all AD details for OCS users
  • Use canned filters to quickly view which users are enabled /disabled for key OCS functionality.
  • Enable/Disable key OCS functionality (e.g. Public IM)
  • Email OCS Assigned and Unassigned Users

Remotely View key Edge settings (from an OCS Administrative Tool or Front-End computer), including:

  • Internal and External Edge server settings
  • Federated Partners and Federated Public IM Network Settings
  • Can use Alternate Credentials to access Edge role

Easily access and view all OCS Global Settings in one location, including:

  • Pools,
  • Enterprise Voice and Meeting Settings and Policies,
  • Location Profiles,
  • Normalization Rules,
  • Archive,
  • CDR,
  • Federation.

On any local OCS machine:

  • View and Control OCS Services
  • View OCS specific Event Log Errors and Warnings
  • Provision Address Book settings that not available in the OCS Administrative console

And a few more screenshots to keep you excited:

Global Settings

  • Allows the administrator to see key UC and Enterprise Voice Global Settings in customizable views.
  • Can easily generate reports through PowerGUI

Global Meeting Policies


  • Allows quick customizable views and reporting of OCS enabled users and all pertinent OCS properties.
  • Default Filters to quickly see which users are provisioning for certain OCS features (e.g. Federation, Public IM, etc…)
  • Additional links to get Voice, Meeting and AD details for any user(s).
  • Actions are available to provision basic OCS features (e.g. Remote Access, Public IM, …)

OCS Users Management

Edge and Federation

  • Easily see all important edge and federation configuration settings in one tree.
  • All internal and external IP addresses and ports are shown.
  • All federation settings including partners and remote edge server peers.
  • Avoids having to remote into the Edge server and start the Edge server Administrative console to see this information.
  • Certificate information to be added in the future.

OCS Public IM Management


  • See which servers and their corresponding roles are installed in your OCS deployment.
  • For the local OCS Server (soon to be any OCS server), see OCS specific Service information and Event Log information and take actions.
  • View Address Book settings and take actions that are not available through the native OCS Administration console.

Installed OCS Server Roles:

Installed OCS Server Roles

OCS Specific Services and Event Log Entries and Actions:

OCS Specific Services and Event Log Entries and Actions

Address Book Information and Actions:

Address Book Information and Actions

This is the most amazing example of the community work I have ever seen. Curtis took the PowerShell scripts which James O’Neill and others created for the Microsoft® Office Communications Server 2007 Resource Kit companion CD, enhanced them, plugged them into PowerGUI and made them available for everyone else to use (and enhance further ;))

You can download the OCS PowerPack here. By the way, please do leave your comments for Curtis at the powerpack page – I know he is anxious to hear some feedback!

Tags: , , ,


14 Responses to “OCS Management on Steroids”

  1. 2 jason November 10, 2008 at 3:51 pm

    this is cool, but I just need a simple line to enable a user during creation (I have an existing creation script, but now we want to roll out OCS). Can anyone help?

  2. 3 Dmitry Sotnikov November 10, 2008 at 9:32 pm


    I think there are 3 options for you here:

    A. Find the actions in the pack which do what you need and simply look up their PowerShell code (by clicking Properties or by clicking the PowerShell Code tab after you execute them.)

    B. Ask Curtis who (unlike myself) is an OCS guru: http://blog.insideocs.com/

    C. Ask in the forums at http://powergui.org


  1. 1 Damien Caro's Blog : Administration d'OCS Trackback on June 24, 2008 at 7:55 am
  2. 2 Kevin LE COGUIC » Blog Archive » Administration d’OCS en PowerShell Trackback on June 24, 2008 at 9:00 am
  3. 3 LCSKid : PowerShell for OCS 2007 Trackback on July 23, 2008 at 5:30 pm
  4. 4 Way cool - powergui console for ocs « JC’s Blog-O-Gibberish Trackback on July 24, 2008 at 5:31 pm
  5. 5 OCS 2007 PowerGUI PowerPack Updated « Inside OCS Trackback on August 25, 2008 at 2:52 am
  6. 6 OCS blog by Curtis « Dmitry’s PowerBlog: PowerShell and beyond Trackback on August 25, 2008 at 8:39 am
  7. 7 OCS & PowerGui : UnifiedCommunications.nl Trackback on September 14, 2008 at 8:05 am
  8. 8 OCS & PowerShell webcast « Dmitry’s PowerBlog: PowerShell and beyond Trackback on January 19, 2009 at 3:51 pm
  9. 9 Vote for OCS PowerPack « Dmitry’s PowerBlog: PowerShell and beyond Trackback on February 6, 2009 at 9:23 am
  10. 10 Nathan's Exchange Blog : PowerShell tools for Active Directory Trackback on August 9, 2009 at 9:32 am
  11. 11 OCS 2007 PowerGUI PowerPack Updated « Inside OCS Trackback on October 24, 2009 at 4:09 am

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

My Recent Tweets


The posts on this blog are provided “as is” with no warranties and confer no rights. The opinions expressed on this site are mine and mine alone, and do not necessarily represent those of my employer - WSO2 or anyone else for that matter. All trademarks acknowledged.

© 2007-2014 Dmitry Sotnikov

June 2008

%d bloggers like this: