Archive

Archive for July, 2011

Using Powershell to enable users for Lync and Exchange Unified Messaging

July 14, 2011 Leave a comment

This document provides the Lync and Exchange Powershell commands for the following:
1. Enable a user for Lync
2. Enterprise voice
3. Assign a Tel URI
4. Enable for Exchange UM
Please note that in order to
• To perform steps 1, 2 and 3 the administrator should be logged on to one of the Lync Front End servers so they can access the Lync Management Shell
• To perform step 4, the administrator will need to have Exchange Admin rights
• To repeat these steps the user mi6hq\james_bond should be removed from AD. This will remove them from Lync and Exchange.
• If a user is already enabled for Lync and Enterprise Voice the steps that follow enabling for Lync and Enterprise Voice can also be used, (e.g. to set the LineURI).
• These steps can also be performed from the Lync Control Panel and the Exchange Management Console, (UM enablement).
The following example commands are based on the following information:
• A test user with the SAMAccountname of mi6hq\james_bond has been created with an Exchange 2007 mailbox (if enabling for Lync and UM).
• AD credentials of user to enable for Lync: mi6hq\james_bond
• User’s AD Display Name: “James Bond”
• Requested SIP address: james_bond@mi6.gov
• Requested Tel URI: +17176061007
• Current PBX Phone number: 717 606 1007
• Requested Exchange UM voice mail extension: 101007
• Requested initial Exchange UM PIN: 101007

Steps to complete the above requirements:
• Logon to a Lync Front End server and open a Lync Management Shell session
o Enable user for Lync: enable-csuser –identity “james bond” –registrarpool mi6hqlyncpool.hq.mi6.local –sipaddress “sip:james_bond@mi6.gov”
o Enable for Enterprise voice: set-csuser –identity “james bond” –enterprisevoiceenabled $true
o Optional: This step is only necessary if the user should be able to receive calls from the PSTN via the PBX PBX:
 Set Tel URI: set-csuser –identity “james bond” –lineuri “tel:+17176061007”
o Set User’s Lync DialPlan: grant-csdialplan –identity “james bond” –policyname “lancasterumhq.mi6.local”

• Enable user for UM: (Must be run from Exchange Management Shell)
enable-ummailbox -identity james_bond@mi6.gov –extensions 101007 -ummailboxpolicy lancaserumhq -pin 101007 –SIPResourceIdentifier james_bond@mi6.gov

Categories: Uncategorized

Lync Common Area Phones Quickstart

July 8, 2011 Leave a comment

Overview

One of the new features in Lync 2010 that was not supported in OCS 2007 R2 is the ability to deploy what are known as “Common Area Phones”. These are phones that you might find in the lobby of business that are used for guests. Unlike other Lync phones, Common Area Phones do not allow the entry of a username and password to logon to the network.

Background

Unfortunately the Microsoft documentation for quickly setting up a Common Area Phone can be a bit challenging. This is especially true if you are in a situation that you would like to quickly configure and set up a Lync environment to use a Common Area Phone, (e.g. Lync pilot or when providing knowledge transfer to clients).

Purpose:

This document provides the steps necessary to quickly enable a Lync infrastructure to support the use of Common Area Phones.

General Steps:

There are 4 general steps to enabling the use of Common Area Phones:

• Add support for Lync Common Area Phones to the environments Windows based DHCP configuration.
• Enable PIN authorization support in Lync
• Create an AD SIP enabled contact record that is utilized by the Common Area Phone to login to the network
• Set a PIN for the Common Area Phone that is entered to initially use the phone for Lync

Detailed Steps:

Let’s suppose you have a Polycom CX500 phone. This phone can only connect to a Lync infrastructure using a PIN and only has an Ethernet connection, (i.e. no USB plug).

The steps below are intended to be utilized for the purpose of quickly connecting and testing Common Area Phones. There are plenty of complexities that can be taken advantage of, (i.e. dialing restrictions) that are not covered in this document. Please refer to the “Microsoft Lync Server 2010 Client and Device Deployment Guide” for further details.

Sample environment:

• AD Forest name: numa.us
• Lync Pool name: lyncpool.numa.us
• NTP time server already enabled.
• CX500 waiting to be configured in the “Building Main Lobby”
• Phone number to assign: 208 555 7000
• The following OU exists in AD: ou=phones,dc=numa,dc=us

Perform the following steps:

• DHCP Configuration
o Copy the program dhcputil.exe from C:\Program Files\Common Files\Microsoft Lync Server 2010 to a location accessible from your DHCP server
o Logon to your DHCP server
o Execute this command: dhcputil –sipserver lyncpool.numa.us runconfigscript
 This will add all the entries needed for DHCP to support a Common Area Phone
• Enable PIN authorization for Lync by typing the following Lync Management Shell (PS) cmdlet: set-cswebserviceconfiguration –identity Global –usepinauth $true
• Create a new SIP enabled contact record in AD that will be used by the Common Area Phone to logon to Lync
o New-CsCommonAreaPhone -LineUri “tel:+12085557000” -RegistrarPool “lyncpool.numa.us” -OU “OU=Phones,DC=numa,DC=us” -Description “Building Main Lobby” -DisplayName “Building Main Lobby” -DisplayNumber “1 (208) 555-7000”
• Set a PIN for the contact record created above that is enter when initially connecting the phone to the network:
o Set-csclientpin –identity “Building Main Lobby” –pin 1234

Now power up the CX500 and when prompted enter the pin value “1234”. The phone will then connect and login to Lync.

Categories: Uncategorized Tags: