Lync is dominating on Twitter #Lync #UCOMS #Avaya #no1

Ok, for you that don’t know so much about Twitter, its an online social networking and microblogging service that enables its users to send and read text-based posts of up to 140 characters, informally known as “tweets”.

And there are certain channels in there like #Lync for example and there are #UCOMS (we used #UC before, but it’s a pretty large university so there were lots of non technical talk in there so we decided to switch to #UCOMS) and then there are #Microsoft #Avaya #Cisco and so on, you get the idea.

The thing is that Lync is totally in domination when we look at quality posts on Twitter, its blogs, tweets, news, autotweets, and really a lot of discussion on twitter with the topic of Lync.

Lync is also the nr1 topic in #UCOMS and even the most posts in #Avaya are also dedicated to Lync somehow, the #Cisco channel is full of junk but there aren’t so much Lync stuff there but not much good action either, well the conclusion of this is that Microsoft really has a great community and I enjoy it a lot, that’s probably thanks to the people posting in #Lync that got me hooked on twitter from the start. So thanks to you all

@matthewlandis

Thomas

Ari Protheroe

Tom Arbuthnot

Duncan Blake

Microsoft Lync Team

alexlewis

Chris Norman

SwissUC

Adam Jacobs

Tom Laciano

Justin Morris

Tom Kisner

Daryl Hunter

Ståle Hansen

Mike Sheridan

Kevin Kieller

Pat Richard

John A Cook

Babul A. Mukherjee

Ken Lasko

Ok I got tiered of copy pasting but there are a lot more people that also should get credits if it weren’t that I have to write some more on that Office 365 lab starting tomorrow….

Lync PowerShell tip #7 – #Lync

get-help New-CsMobilityPolicy –full

This will give some interesting reading IF you have deployed CU4 that got released today (or yday)

Lync 2010 Mobile is a client application that enables users to run Microsoft Lync 2010 on their mobile phones. Call via Work provides a way for users to make calls on their mobile phone and yet have it appear as though the call originated from their work phone number instead of their mobile phone number. Users who have been enabled for Call via Work can achieve this either by dialing directly from their mobile phone or by using the dial-out conferencing option. With dial-out conferencing, a user effectively asks the Microsoft Lync Server 2010 Mobility Service server to make a call for them. The server will set up the call, and then call the user back on their mobile phone. After the user has answered, the server will then dial the party being called.

Both of these capabilities – the ability to run Lync 2010 Mobile and the ability to use Call via Work – are managed using mobility policies. When youinstall Microsoft Lync Server 2010, you will have a single, global mobility policy that applies to all your users. However, administrators can use the New-CsMobilityPolicy cmdlet to create custom policies at either the site or the per-user scope.

Other than a description of the policy, mobility policies have only two properties. The first, EnableOutsideVoice, determines whether or not Call via Work is enabled; the second, EnableMobility, determines whether or not users are allowed to use Lync Mobile. Both of these properties must be set to true before a user can take advantage of Call via Work. If EnableMobility is set to True and EnableOutsideVoice is set to False, the user can run Microsoft Lync Mobile but will not be able to use Call via Work. If EnableMobility is set to False and EnableOutsideVoice is set to True the user will not be able to run Microsoft Lync Mobile. In turn, that means that the user will not be able to use Call via Work, regardless of the value of the EnableOutsideVoice property.

Note that users must also be enabled for Enterprise Voice before they can use Lync 2010 Mobile. To use Call via Work, users must be managed by a voice policy that allows simultaneous ringing.Who can run this cmdlet: By default, members of the following groups are authorized to run the New-CsMobilityPolicy cmdlet locally: RTCUniversalServerAdmins. To return a list of all the role-based access control (RBAC) roles this cmdlet has been assigned to (including any custom RBAC roles you have
created yourself), run the following command from the Windows PowerShell prompt:

Get-CsAdminRole | Where-Object {$_.Cmdlets -match “New-CsMobilityPolicy”}

Lync PowerShell tip: 6 #Lync #Exchange #PowerShell

All credit for this tip should be directed to @patrichard that runs the blog http://www.ehloworld.com/

Get-mailbox | Set-mailbox -MailTip “This looks like a message that would be better to send in Lync!”

What this one does is to create a internal MailTip for all messages that are sent to internal recipients. Making it look something like this

image

Dirsync for x64 servers in #Office365

Ok so put on your party hats and lets celebrate

image

Because it looks like 64 bit support for Dirsync just sneaked out from the farm.

 

Upgrading from 32-bit directory synchronization tool

(From http://community.office365.com/en-us/w/sso/555.aspx )

To upgrade your 32-bit installation of the directory synchronization tool, you must first uninstall it, and then install the 64-bit tool on a new computer.

Although the 32-bit instance of the directory synchronization tool is removed, the overall state of the objects in your on-premises and cloud directories, respectively, is preserved. When you install and configure your 64-bit instance of the directory synchronization tool, it finds and matches objects in the cloud with on-premises objects. However, the 64-bit instance of the tool will not find and match objects in the cloud if on-premises object deletions occurred when the 32-bit instance of the directory synchronization tool was offline.

Therefore, you must minimize changes to your on-premises objects during the upgrade to the 64-bit instance of the directory synchronization tool.

  1. On the computer on which the Directory Synchronization tool is installed, open the Control Panel, select Add and Remove Programs, and then uninstall the Directory Synchronization tool.

    noteNote:

    If a synchronization session is in progress, a warning message appears when you try to remove the Directory Synchronization tool. If you receive this warning, wait until synchronization is complete, and then repeat this step.

  2. Install the 64-bit version of the Directory Synchronization tool installation file on another computer. To do this, sign in to the Office 365 portal, click Admin in the header, click Users under Management in the left pane, click Set up in the Users pane, select Windows 64-bit version, and then click the Download button for step 4: Install and configure the Directory Synchronization tool.
  3. On the last page of the installation program, select Start Configuration Wizard now, and then click Finish.
    The Microsoft Online Services Directory Configuration Wizard starts.

Lync PowerShell tip: 5

Todays PowerShell tip is to use | Out-GridView

To enable it you will have to add the PowerShell Integrated Scripting Environment (ISE)

Import-Module ServerManager
Add-Windowsfeature PowerShell-ISE

image

Bonus tip of the day: Try Get-CsWindowsService | Out-GridView and you will see the current activity of your Lync Server services

Lync PowerShell tip: 4

Get-CsWebServiceConfiguration -Filter “site:*” | Set-CsWebServiceConfiguration -MaxValidityPeriodHours 72

What this does is to turn down the validation time on the certificate that Lync client uses to log on to the Lync Server from the default of 6 months to 3 days.

Its actually possible to extract certificates with the private key and then import them on an different computer and then log-on as the owner of the certificate. So to completely disable a user you will also need to disable their certificates.

Running the Disable-CsUser cmdlet deletes user data. So if you need to maintain any user data, do not use this cmdlet. Instead use Set-CSUser -Enabled $false -Identity <userIdentity> to disable all Lync functionality (not just certificate authentication), but still retain the user data.
You can also use the Revoke-CsClientCertificate to prevent client access.

http://technet.microsoft.com/en-us/library/gg398396.aspx

http://technet.microsoft.com/en-us/library/gg195642.aspx

Lync PowerShell tip: 3

New-CsCallParkOrbit -Identity “CallPark” -NumberRangeStart 400 -NumberRangeEnd 499 -CallParkService ApplicationServer:pool01.litwareinc.com

Used mainly in two scenarios, first is when I receive a call that is not for me (lets say its for Sofia) and she is out on the factory floor or in a big shop or something like that, then I can just send this call to the parking and call a Snom PA1 (connected to some speakers) and say “Sofia you got a call on line 431” and she could walk up to a common area phone and pic the call up. You have all heard it before…

The second would be when information workers have laptop computers and are seated in a open floor, they got a call that is somewhat private or something and if they took the computer out from the docking station it would loose network and the call would be disconnected, so they could either forward the call to a mobile or to a call parking and then walk to a  phone room with a common area phone and pic it up.

Lync PowerShell Tip:1

This will (hopefully) be a new series on the blog with some one-liners that I use in my daily work as a consultant installing Lync Servers.

Set-CsConferenceDisclaimer -Header “Litwareinc.com Online Conference” -Body “Important note: This is a private system for invited attendees only, Conferencing proceedings can be recorded and archived.”

Now when a Lync client joins the meeting they will first see this screen
image

And it will look something like this when the web clients enter
image

http://technet.microsoft.com/en-us/library/gg398776.aspx