“Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.”

Have recently been on an engagement where we have had to perform an in place upgrade from Windows 2008 R2 Standard edition to Windows 2008 R2 Enterprise edition whilst Exchange 2010 was installed to facilitate the addition of a DAG.

All went well but the above error was received when we launched the Exchange MC. After a bit of head scratching I realised that the WinRM IIS component wasn’t selected anymore???? Added the feature and all started working again, magic.

Good luck

NeilC

We Recently found a bug in the Lync client which stops the Audio Selection Button being displayed if users are not EV enabled.

http://support.microsoft.com/kb/2616187

Working with MS to see if we can get a fix. Will post any further developments.

I have found cases where the CA server do not include SAN names on certs requests.

Below is the command to enable an internal CA so that it allows the issuance of alternative names on a cert request. If this is not set and you
request a cert it will just ignore the alternative names when it issues the cert.

For SAN Certificate usage:
Activate the possibility to request SAN certificates with this CA

net stop certsvc

certutil -setreg policy\EditFlags +EDITF_ATTRIBUTESUBJECTALTNAME2

net start certsvc

When users upload documents etc to their meetings that are hosted by Lync, the files are uploaded to the Lync File store. One question that seems to come up a lot when designing Lync solutions for security sensitive customers is “Is the file store cleaned out regularly?”

The files remain on the file store until they are deleted by the meeting organiser or they are cleaned out by Lync after the meeting. The default time period for this automated clean out is 15 days after the meeting. However, this is configurable in the Conferencing Configuration using the ContentGracePeriod attribute.

Note: The following commands assume you only have the default “Global” collection of conferencing settings configured. If you have more than this, you should use the –Identity attribute to specify the collection you want to view/amend.

To view the current setting, open the Lync Management Shell and view the ContentGracePeriod attribute using this command:

Get-CsConferencingConfiguration

To change the value, use this command:

Set-CsConferencingConfiguration -ContentGracePeriod <value>

where <value> is the time period after the meeting that you want content to be deleted. This can be set to any value between 30 minutes (00:30:00) and 180 days (180.00:00:00). The default value is 15 days (15.00:00:00).

BrianC

When deploying the FIM Portal the page is built on WSS 3.0. You may notice that after deploying the Portal you are just displayed by the default WSS 3.0 page when browsing locally or remotely.

When you deploy the FIM Service and FIM Portal it actually installs two .wsp’s which style the SharePoint site in accordance to the FIM Portal functionality. Sometimes after initial installation these features are not enabled by default. To enable them navigate to Central Administration > Site Actions > Site Settings > Site Features and select Activate on both ILM2 Pages and FIM Password Reset Pages

You should then be able to navigate to the url locally and remotely and see the normal FIM Portal page

Hope this helps some headaches as there arent too many pointers as to why this happens

Thanks,

Ash

I came across the following error message recently whilst troubleshooting an SCCM Distribution Point;

————————————————————————————————————————–
There was an error while performing this operation.

Details:
Filename: \\?\C:\inetpub\wwwroot\web.config
Line number: <LineNumber>
Error:  Cannot add duplicate collection entry of type ‘<XXX>‘ with unique key attribute ‘<YYY>‘ set to ‘<ZZZ>‘.
————————————————————————————————————————–

Client’s were downloading packages via SMB rather than over HTTP which prompted me to check if WebDAV had been configured… upon clicking on the WebDAV feature configuration page the error appeared.

Turns out this was quite a simple fix – WebDAV had been configured at the Server Level, rather than at the Site level which a) resulted in this error and b) seemingly broke WebDAV and was the cause of the issue with the DP. Simply delete the configuration at the Server Level, and set your configuration at the site level.

Thanks
SteveH

This is a great blog entry from the Microsoft UC Group Team
who have summarised the past year with Lync. It includes links to some
excellent content and makes for interesting reading when comparing Lync to
other vendor’s offerings.

http://blogs.technet.com/b/uc/archive/2011/09/23/lync-gets-people-talking.aspx

Great post!

BrianC

This article was pointed out to me by a customer that has this exact issue whilst using FUS – Thanks Matthew

Thought it was definitely worth a re-blog here:

Communicator/Lync issues with “Fast User Switching” on Windows 7

During work on OCS 2007 R2 and Lync projects, I have come across some strange behaviour on Communicator and Lync, this behaviour has only been noticed with computers accessed by more than one person – Often “Common Area PC”

Problem/Issue:
When a user is logged on to a computer and has locked the computer and a new users logs into the same computer by using “Switch User” functionality, the new user are having problems using Communicator/Lync for any type of Audio calls.

If the user try to do a PSTN call there is a constant dial tone in the background and the call will eventually terminate.
If the user try to join a A/V Conference, there is no audio and the conference call will end.

Solution:
Microsoft has confirmed – in mail – that there is an issue with FUS (Fast User Switching) and Communicator/Lync.
They have also done some investigation on this, but the change has been consider to large for the current available clients.

Work Around:
Since this problem/issue mostly occurs at “Common Area PC”, often meeting room pc, there is possible to turn off FUS on those computers. This can be done in GPO.

Another workaround would be to create a trigger that trigger’s on “Computer Lock” and terminates the Communicator process. The same trigger will trigger’s on “Computer Unlock” and restart the Communicator process.
This is probably NOT the best approach, but it will “solve” the problem.

My customer is simply going to get all users to logoff rather than switch when hot-desking which is more manageable given their environment.

Thanks to Trond Egil Gjelsvik-Bakke for the original blog!

Good luck

NeilC

I was asked how to check that Lync Schema upgrade was successful. Hopefully the following information is useful:

Use the following cmdlet to verify that schema preparation ran to completion:
• Get-CsAdServerSchema

This cmdlet returns a value of Schema_Version_State_Current if the schema prep was successful.

If you want to go a step further:
In ADSIedit, under the Schema Container, look for the ms-RTC-SIP-SchemaVersion attribute. Opening the properties, look for the rangeUpper attribute. Check the list below for the correct value for your environment:

• LCS 2005 – 1006
• OCS 2007 R1 – 1007
• OCS 2007 R2 – 1008
• Lync Server 2010 – 1100

For Lync, the rangeLower value should be 14.

Checking that the ms-RTC-SIP-SchemaVersion values on each DC is what is expected, confirms that the changes have replicated around your AD.

To confirm that AD replication has occured, you can use the following command:

• repadmin /replsummary

This shows the AD replication state and relative health of the forest.

BrianC

The following blog handily contains a link to all of Microsoft’s recently updated documentation around Lync2010.

http://www.leedesmond.com/weblog/?p=760

Good work!

NeilC