2012 r2 dc lsass.exe crash

Crashing lsass.exe on your shiny 2012r2 DC? It’s a known bug according to PSS. You have three choices. a) use a different DC to rename things. b) turn of all auditing on the DC (seriously) c) apply a hotfix that you can only get from PSS.

Personally, I’ve gone for option “a”. We need the auditing and option c had a number of “it’s your fault if it breaks” warning attached to it that scared me a little. I’ll await the real patch which apparently will be “soon”. THough that’s in Microsoft Minutes so don’ hold your breath….

MK 900 and D7100

I’ve had this flash for some time now, and whilst initially impressed I’m getting slowly more disappointed with it. It seems to consistantly underexpose photos. I’ve no idea why. There are certain combinations of having the cameras ISO on auto and matrix metering enabled where the flash will fire but it always seems to be at 1/128. Changing the iso to manaul (and keeping all the settings the same) fixes it. How does that make a difference? Another fix is to enable spot metering. I’m very confused. It seems most problematioc in contrasty areas or when I focus on something that is black. I can’t recommend this flash unfortunately. I’m now looking for another. I seem to keep spending £100 or so on flashes that arent perfect. MAybe I should bite the bullet and just get the sb910…

DFM missing statistics

Had the issue recently where the DFM would stop reporting statistics on all of our volumes on some controllers. After spending an eternity digging around it seems that if you enable debug logging on the dfm you will see an error returned by the controller that it has run out of memory. You can increase it but please check this burt first http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=472940

To increase the memory from the default of 262144 do “options perf.dblade_zapi.buf_limit and select a higher number (in bytes). Try 307200 (300k) first then slowly increase it if you have no joy.

snapdrive issues with 2003 servers and esxi 5.5

“vmdk is larger than the maximum size supported by datastore”

[SnapDrive Error]: Please specify valid VMFS datastore name. (SnapDrive Error Code: 0xc0041033)

 

Have a read of this:

http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=600206

Create a new vmfs5 datastore and then add the key listed in the article. No need to restart snapdrive. snapdrive will then use that as the file to back the RDM when it does a verification.

Snapdrive Underlying connection was closed VCenter 5 / 5.5

It seems that a 2003 server doesn’t support the new SSL options that are enabled in the VC with 5.5 (and maybe earlier).

Try changing the following (taken from the release notes, which you’ve already read? 😉 :

  • On the vCenter Server host machine, reduce the implied security by allowing the server to communicate using weak cipher suites. To do this, include the following section in the vCenter Server vpxd.cfg file, located c:\Programdata\VMware\VMware VirtualCenter:
    <config>
    ...
    <vmacore>
    ...
    <ssl>
    ...
    <cipherList>ALL</cipherList>
    ...
    </ssl>
    ...
    </vmacore>
    ...
    </config>

restart the vcenter service and it should now hopefully work.