Last week I promised some help for those of us studying for Lync Server certification. So, let’s return to a Lync Server topic as useful as it is complex: PowerShell Cmdlets.
I was using the same methods I used for my last exam – reading forum threads, doing practice tests, the usual stuff. After a while, I could tell that cmdlets are referenced more frequently (at least from what I can remember) in the 2013 exams.
I admit, I don’t use cmdlets as often as I should. They’re a great timesaver. And they pack a lot of power. Which is why certification exams ask you about them!
So with that in mind, I’m blogging up a reference for a few cmdlets I think are important to know. Four, in fact, that appeared more than once in my studies. Let’s start with Set-CsUser.
This cmdlet lets you modify a user’s account properties. As you can imagine, this makes it VERY powerful. Which is why you must be a RTCUniversalUserAdmins group member to use it.
With its parameters, you can set:
- If a user is enabled or disabled
- What their Identity is
- If the user can make audio/video calls or not
- Whether Enterprise Voice is enabled
- What their Lync phone number is
- If they have a private line (this is new in 2013, so make sure you know about private lines!)
- What the user’s SIP address is
- And a couple more!
This allows you to set parameters for an existing conferencing policy. It helps you govern what tools are available for Conferencing users.
One such parameter is “EnableDataCollaboration”. It’s a typical True/False. But what it allows/disallows is important.
“Set-CsConferencingPolicy –Identity global –EnableDataCollaboration $True” lets conference participants use the Whiteboard, share PowerPoint, or conduct a poll.
“Set-CsConferencingPolicy –Identity global –EnableDataCollaboration $False” prevents conference participants from using the Whiteboard, sharing PowerPoint, or conducting a poll.
New-CsVoicePolicy and Grant-CsVoicePolicy
You likely remember these from Lync Server 2010. They create (New) and assign (Grant) a voice policy to users or groups.
New: has as many parameters as Set-CsUser, almost as powerful. You’re creating a policy to enforce things like:
- Allowing call forwarding, PSTN routing or Simultaneous Ring
- Enabling Call Park, Delegation, Malicious Call Tracing or Team Call
- Setting a PSTN Usage (phone route for the voice policy) or a Voice Deployment Mode.
And there’s still more parameters you can use with New-CsVoicePolicy.
Grant-CsVoicePolicy is, as you’d expect, less complex. Its few parameters focus on making sure you have the right policy assigned to the right users. I mention it for two reasons:
1. It’s the natural partner for New-CsVoicePolicy.
2. Using a cmdlet to grant voice policies is faster than assigning them in the Management Console. One cmdlet entry when you have new users, and done.
Even though they aren’t new to 2013, these cmdlets are still valuable to Lync Server user management. Thus they should be expected in certification.
Not studying for Lync Server 2013 certification? It still pays to know the ins & outs of cmdlets like these. They can save an admin some time, over & over!
Next week: The two types of Response Group management (and when to use them).