Thursday 30 January 2014

Installation of Trusted Application on Lync Server




Microsoft Lync 2010 is not a version that can be used to sign in to the server




If a client reports us above issue, then check if that user has any client version policy


This confirms us that user is unable to login to his client as client version policy is blocking the user to login to Lync.

To fix the issue

Either you remove the client version policy which is blocking the client. 
(Or) Inform the user to upgrade the Lync Client

Monday 27 January 2014

Configuring On-premises Lync Server 2010 Integration with Exchange Online

To configure On-Premises Lync Server 2010 integration with Exchange Online, you need to perform below steps

Login to Lync Front End Server and open Lync Management Shell:

Configure the Edge Server for federation
Set-CsAccessEdgeConfiguration -AllowFederatedUsers $True

Configure a Hosting Provider on the Edge Server
New-CsHostingProvider -Identity "Exchange Online" -Enabled $True -EnabledSharedAddressSpace $True -HostOCSUsers $False -ProxyFqdn "exam.um.outlook.com" -IsLocal $False -VerificationLevel UseSourceVerification

Create a DNS SRV Record for Integration with Hosted Exchange
If you already have the DNS SRV record in place, have to verify the same, Run the mentioned command in cmd: nslookup <EdgePool.domain.com>

Update Central Management Store
Invoke-CsManagementStoreReplicationStatus

Verify the replication of the updated Central Management Store
Get-CsManagementStoreReplicationStatus

To check the changes were applied on Edge Server run the following cmdlet:
Get-CsHostingProvider -LocalStore


Thursday 23 January 2014

Enable Desktop Sharing for a Lync User

To Enable Desktop Sharing to a Lync User, You need to apply a Conferencing Policy to a user


You can run the below command to enable Desktop Sharing for a Lync User

Set-CsConferencingPolicy -Identity Global -EnableAppDesktopSharing Desktop



If user need to share only a single application instead of entire desktop, run the below command

Set-CsConferencingPolicy -Identity Global -EnableAppDesktopSharing SingleApplication

If you want user shouldn't share the Desktop or a Program, run the below command

Set-CsConferencingPolicy -Identity Global -EnableAppDesktopSharing None

If user wants to share the Desktop & Program from their Lync Clients, then enable both Desktop and Application Sharing under Participant Policy from the Conferencing Policy

From Lync Control Panel - Click Conferencing - Edit the Conferencing Policy (Global) - From the Drop Down of Participant Policy select Enable application and desktop sharing - Click Commit

Reference

Tuesday 21 January 2014

DC Promo error: The local administrator account becomes the domain administrator

The local administrator account becomes the domain administrator error when running dcpromo
When trying to promote a Windows Server 2008 R2 X64 server to a domain controller of a new forest i obtained the following error which stopped the promotion of the system:

To resolve this error, open a command prompt as administrator and execute the following command: net user Administrator /passwordreq:yes *

Saturday 18 January 2014

Prevent the usage of lync clients with versions lower than specific build



  1. Login to the Lync Control Panel
  2. Go to Clients
  3. Go to Client Version Policy Tab
  4. Based on the requirement scope, you need to create a New Client Version Rule
Available Scopes:
  • Global (Applies for all Lync Users)
  • Site Policy (Applies to available site in the infrastructure)
  • Pool Policy (Applies to available Registrar)
  • User Policy (Which can be applied per User)
  1. If you need to create a client version policy for a user, then Click New under Client Version Policy and click User Policy
  2. Provide Name (Blocking a Lync Client Version) and Description (Block)
  1. Click New Client Version Rules
  1. Provide the details in the New Client Version Rule
User Agent: OC
Major Version: 15
Minor Version: 0
Build: 4420
Update: *
Comparison operation: Older than
Action: Block
  1. Click Ok
  2. Click Commit
  1. Under Client Version Policy we will see the newly created user policy
  1. Go to Users in Lync Control Panel & Click Properties and select Blocking a Lync Client Version
  1. Click Commit
  2. Now you have successfully applied the Client Version Policy
Note: Once User Sign Out and Sign in Back, Client Version Policy will be applied

Friday 3 January 2014

Cannot Sign in to Lync

When user receives below error



Ensure to check user SIP address (Sign in Address) in Lync Client
Ensure user is providing the correct user name along with domain name
Ensure the password is correct, Clear the stale credentials from the credentials manager
Ensure User account is not locked in AD

Once everything is verified & corrected, user will be able to successfully login to his lync client

Thursday 2 January 2014

Multiple Lync Users unable to save instant message conversations in my email Conversation History folder

If multiple user says that in their lync client below two options are greyed out and unable to check the two options
  • Save Instant message conversations in my email Conversation History folder
  • Save call logs in my email Conversation History folder
To fix the issue you need to find the Client Policy applied for the user

From Lync PowerShell, execute the below command

Get-CsUser -Identity "SamAccountName" | Select DisplayName, ClientPolicy

You will get the output for User Display Name and the Client Policy

To enable the two options in Lync Client, execute the below command

Set-CsClientPolicy –Identity PolicyName –EnableIMAutoArchiving $true–EnableCallLogAutoArchiving $true