Preventing Lync Server 2010 certificate expiration

Problem Description:

A Lync Server Certificate is about to expire in a few days:

·         An expired certificate will cause the Lync Server 2010 services to not start

·         An expired certificate may communication between Lync Server 2010 Server roles to fail

 

More details:

There are two way to locate information about the certificate that is associated with the Lync Server 2010 server

Method 1: Using Lync Server Deployment Wizard

Note You can also request a certificate from an internal CA, or assign an existing certificate from this wizard.

1.      Launch the Lync Server Deployment Wizard from the Windows Start menu on the Lync Server 2010 server

2.      Click on “Install or Update Lync Server System”

3.      Click run on Step 3: Request, Install or Assign Certificates

4.      Use the Certificate Wizard to view all the certificates that are installed for the Lync Server 2010 server

Method 2: Using Lync Management Shell

Use the PowerShell cmdlet Get-CsCertificate to locate information about the certificate associated with the Lync Server 2010 server

Note To view all properties on the certificate objects returned to see the SAN’s. Use with a "Get-CsCertificate | fl –property * cmdlet

For more information on Get-CsCertificate cmdlet please refer the following technet document
Get-CsCertificate

To request a certificate using the Lync Management Shell use the Request-CsCertificate cmdlet

For more information on Request-CsCertificate cmdlet please refer the following technet document
Request-CsCertificate

To import a certificate using Lync Management Shell use the Import-CsCertificate cmdlet

For more information on Import-CsCertificate cmdlet please refer the following technet document
Import-CsCertificate

To assign a certificate using Lync Management Shell use the Set-CsCertificate cmdlet

For more information on Set-CsCertificate cmdlet please refer the following technet document
Set-CsCertificate

Checking the User Profile Sync permissions – SharePoint 2010

When configuring the User Profile Sync in SharePoint, you would have certainly read up Spence Harbar’s post on configuring the User Profile Sync. If you haven’t, then here’s a link you should definitely bookmark:

http://www.harbar.net/articles/sp2010ups.aspx

Spence has by far the most comprehensive guide on configuring the UPS. If you read and understand the above post, you won’t go wrong with UPS configuration.
The aim of this post was to talk about a little less known script to check to see if your UPS permissions are set correctly.

The script is called PowerShell Administration Library for SharePoint – “Administration.ps1″ by Tobias Lekman.

You can a few handy functions. Really worth checking it out.

Since we are talking about User Profile, I want to draw your attention to an interesting function called Check-Replicatechanges. It’s as simple as loading up the PowerShell script and run a Check-Replicatechanges DOMAIN\UPSServiceAcc and it does a check on the specified User Profile Sync account to see if it has permissions fit for Forefront Identity Manager to perform its magic.

This tool is very handy if your AD infrastructure is run by another team and you don’t have Domain Admin permissions.

http://lekman.codeplex.com/releases/view/65930

Curtsey: www.jeremytaylor.net.

There was an error in callback

Problem Description:

When you search for user accounts using "Browse" People-Picker icon, the following error message may occur and the user accounts may not be resolved

Error Message:

"There was an error in callback".

Probable cause:

This issue normally happens if WSS_WPG group does not have any permissions on this registry key "HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure".

By default, WSS_WPG group has FULL control access to the above mentioned registry key.

This particular key contains a binary value called AppCredentialKey – it is used to encrypt/decrypt the data passed by PeoplePicker-SearchADForests. This key is created using setapppassword command and used in one way trust relationships. Application pool accounts need at least read access to the above mentioned registry key for successful People Picker behavior.

Resolution

1)      Check WSS_WPG group permissions and confirm whether the application pool account of the web application present in that group 

2)      Later check the registry key - "HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure" and identify permissions allocated for WSS_WPG group in the Permissions window of the registry key.

3)      If WSS_WPG group does not present in Permissions window, add the 'WSS_WPG' group with read or full control permissions.  

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues. Thank you.

SharePoint Connections

SharePoint Connections will help corporations get more out of SharePoint. 

Fall 2012 SharePoint Connections is your independent, technical conference, offering you the latest information about SharePoint 2013 as well as how to use SharePoint 2010 and earlier SharePoint versions to their fullest potential. Our SharePoint experts teach you the latest SharePoint technical knowledge and how to apply it to your situation. 

At SharePoint Connections, Microsoft SharePoint MVPs and SharePoint technical trainers interact with you and your peers, members of the SharePoint community, in workshops and one on one. You'll learn from experts who will teach you techniques to make SharePoint work in the real world. And you'll get your questions answered and come away with knowledge that will benefit your company, your coworkers, and yourself. 

Who will be speaking at SharePoint Connections? Experienced technical presenters, who have taken SharePoint apart, studied it thoroughly, used it in the real world, and figured out how it works. We choose speakers based on their SharePoint expertise, their technical knowledge about administration or development issues, and their ability to explain what they know so you understand it. 

Don't miss SharePoint Connections if you are a SharePoint admin or developer who needs technical information and real-world help with SharePoint's many challenges, including

• Administering SharePoint
• Developing for SharePoint
• Customizing and integrating SharePoint into your business
• Fine-tuning your deployment
• Making SharePoint work for your end-users' needs
• Plus SQL Server and SharePoint, SharePoint and Visual Studio, SharePoint performance, search in SharePoint, SharePoint social features, and so much more!

Use one of the two ways to register today!

Online Registration or Phone 203-400-6121

Courtesy:  https://www.devconnections.com

Reference:http://www.devconnections.com/shows/fall2012/default.aspx?s=192&CID=EM092712SPProM1&utm_source=penton&utm_medium=email&utm_campaign=PromoInt_CON_CM_F12_SP_SPPro_092712

Your client does not support opening this list with Windows Explorer

Few days before, one of my clients reported an issue in which he is not able to open the document library in explorer view. One thing I would like to highlight here is that the resolution of this issue varies from OS to OS (OS: Operation System) so that’s why I have mentioned the machine configuration in the next point.

Machine configuration:
Operating System: Windows Vista
Explorer Version: IE 8.0
Office Version: Office 2010

Error Message:
Your client does not support opening this list with Windows Explorer

Checks to be followed:

Start / Restart Web Client Service

1)      Open the "Run" prompt (key combination Start+R)

2)      Type services.msc and press Enter.

3)      Locate Web Client service

4)      Make sure your service startup mode is set to automatic (right click it, select "Properties", and under "General" tab select "Automatic" from the "Startup Type" dropdown"

5)      Start the service or restart it if it’s already running.

Auto-detection of proxy
the way to turn this off is in Internet Explorer:

1)      In Tools select Internet options.

2)      Select Connections tab

3)      Click Lan settings button

4)      Under Automatic configuration clear the automatically detect settings checkbox.

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you.