You have all these users in Active Directory, how do you enable them for Communications Server? Read this article to find out.
You can’t manage Communications Server without managing the users who are using it. (Yes, you can manage parts of it, but definitely not all of it.) This article explains how to retrieve user information from Activie Directory.
You can retrieve Active Directory and Microsoft Communications Server "14" user account information by using the Filter and LdapFilter parameters. But if you’ve worked with Windows PowerShell much, you know that you can do a significant amount of filtering with the Where-Object cmdlet. So why all the filtering with LdapFilter and Filter? This article explains why.
You may never have imagined just how easy it could be to manage administrator privelages. Or maybe you did. The Microsoft Communications Server team certainly did, and RBAC is the result. Take a look at this introduction to see.
Keeping track of the status of a lot of contacts can be a bit trying on a system. It might be a good idea to limit the celebrity status of some of your users by limiting the number of contacts they can have at once.
In this article you’ll find out how to set telephony options in Communications Server PowerShell. The PowerShell options don’t quite map to the Communications Server Control Panel options, so this isn’t quite a simple as it might seem. But – for the most part – we make it seem pretty simple.
You probably have more than 21 things on your list of things you need to do today. Well, make room for one more: read the list of 21 User Information Commands to Run Before You Die.
If you're brand new to Windows PowerShell v 2.0, this is the place to start.
It's one thing to modify settings in Microsoft Communications Server by changing property values. It's a whole other thing to do that with properties that can contain multiple values. But don't worry, we've got it covered here.
Find out what the most commonly-asked questions (or least what we think the most commonly-asked questions will be) are about Microsoft Commmunications Server "14" PowerShell.
This may come as a shock to you (or maybe just a relief), but Communications Server “14” doesn’t use Group Policy to manage user policies. Instead Communications Server defines its own policies, which can be applied to specific users. This article explains how to do that.
There are over 500 cmdlets for managing Communications Server. (Yes, you read that right, over 500!). That may seem like a lot, but for a product as powerful as this one you pretty much need 500 cmdlets. But with all those cmdlets, how in the world do you find the ones you need for a particular task? Read this article and you’ll find out.