November 18th, 2011
johnr
Came across this issue at two different customers whilst demoing the cool dashboard functionality. The health status graphics are not shown for any objects either inserted, reconciled, linked to new or exported Visio diagram.
Visio 2010 Add-in for System Center Operations Manager 2007 R2 can be downloaded from here if you haven’t already tried it http://www.microsoft.com/download/en/details.aspx?id=26228

It appears that Service Pack 1 for Office\Visio 2010 breaks the add-in for Operations Manager, the symptoms include;
- The Operations Manager add-in loads on the ribbon without a prompt
- The Add Status button doesn’t work
- Health State data graphics are not shown
- Visio can crash on closing
Currently I’m not aware of a method to fix it with SP1 installed, instead run Visio as RTM. Most media comes SP1 integrated so to remove the updates simply delete the content from the update folder in the Visio installation media, this will install Visio as RTM.

Any pages created previously will still not work but newly created or exported will now show the health status correctly.
John Riseam
System Center Consultant
Risual Ltd
November 14th, 2011
neilc
“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