As a Consultant

Finally found some time to play around with DSC on 2012 R2 and with the release of Windows Management Framework 4 , I can finally play with 2008 R2, Windows 7 and Windows 8 clients (if you upgrade to 8.1). As always with new releases of the Management Framework, some server configurations/applications do not play nicely with the new framework: System Center 2012 Configuration Manager ( not including SP1) System Center Virtual Machine Manager 2008 R2 (including SP1) Microsoft Exchange Server 2013 , Microsoft Exchange Server 2010 and Microsoft Exchange Server 2007 Microsoft SharePoint 2013 and M icrosoft SharePoint 2010 Windows Small Business Server 2011 Standard Please also note that .Net 4.5 is required before you install the Framework, otherwise the Framework installation will actually silently fail. As I previously wrote, if you were hoping for support for Windows Server 2008 support, you are not getting it. You will have to fall back to Windows Management Fram...

Lately I have been working in SCOM with SNMP devices. Needless to say I have learned some new tricks I would like to share with you. Firstly you may have run into the dreaded "No response SNMP" message in Network Devices Pending Management in the SCOM console. First thing that jumps out is network connectivity, however I have seen cases that that is not the issue. Based upon my experience the message is very generic and could have several causes: 1. Network connectivity Firewall (on the SCOM server or one of the SCOM servers that is a member of the resourcepool specified in the discovery rule) or between the SCOM-server and the SNMP device. 2. SNMP-device configuration The target SNMP device needs to enable the whole system MIB/OID-tree to be discoverable in SCOM. If any of the following OIDs are missing, you will not be able to discover the device: 1.3.6.1.2.1.1.1.0 --> system.sysDescr 1.3.6.1.2.1.1.2.0 --> system.sysObjectID 1.3.6.1.2.1.1.4.0 --...