Within the NET gateways there is a current bug which affects SNMP triggers for error/crash reporting.
If your gateway is running version 2.1.x version the console wont allow you to delete or amend the default entry within the SNMP portal. OR is some cases I’ve have seen it allow you to amend it but then not actually work as expected. The workaround to this is to simply leave the default entry in the portal and just add another entry detailing your requirements.
At the time of writing NET are aware of this minor bug, and when 2.2.x is released in a month or so’s time this will be resolved. Using the link below keep an eye on the NET/Sonos site for the release of 2.2
This one is a interesting one. Again following a health check on a clients site for Lync 2010, i came across this little issue with Lync 2010 and Silverlight and thought i should blog about it as it seems the issue/resolution its not as well known as i first thought.
Symptoms of this issue is when you are administering Lync 2010 via the Lync control panel, silverlight will crash giving you a very basic crash error. (see below).
Reasons for this error, or should i say the crashing is still unknown and it logged with Microsoft. I expect Lync 2010 will be patched to resolve this.
Remove Silverlight 5.x and install Silverlight 4.x
At the time of writing Lync 2010 October CU7 has been released and the issue still exists with silverlight 5.x
Having been onsite recently with a client who unexpectedly had a split brain DNS, and also the client did not host one of the domain zones interally i thought it would be good to provide information on how you set up DNS entries so that the Lync client automatically logs on negating the need for a manual configuration of the client.
Over the last couple of days ive been hearing more about the Lync basic client which in truth is a cut down version the Lync 2013 client. Surprisingly though it does weigh in at a hefty 271mb of download.