In an organisation where you may have hundreds or thousands of AD accounts it will not be unusual to come across incidents where user’s accounts are unexpectedly locked out.
This is where the Microsoft Account Lockout and Management Tools will come in handy to help us figure out (i) which device caused the account lockout and (ii) the current lock out state of a given user account.
Recently I was tasked with converting iSCSI connected disks on Windows Servers to a new SAN. With this migration it was decided that we should convert the disks to native ESXi VMDK format.
It is not possible to storage-vMotion the iSCSI disks without doing some work first (see below) as the hypervisor does not see the iSCSI disks as they are essentially remote disks.
In this article are some ideas you could potentially use to convert the iSCSI disks to VMDK.
You could use the VMware vCenter Converter tool to migrate the disks to VMDK. This will involve some down time.
Another option which you could potentially do without any down time is to:
This was a difficult driver to find so I have made it available on my blog so others in the future don’t have to go through the same hassle of finding it (it’s not even possible to download it from the Atheros website).
The driver is designed for Windows 8.1 32/64bit but I am using it just fine on Windows 10.
Driver version: 10.0.0.308
Driver date: 11/12/2014
I’ve had my Nexus 5 for almost a year now and as always with technology, I’m starting to get bored of the stock Android feel. After doing a bit of research in to the many different Android ROMs available for the Nexus 5, I thought I would go ahead and give the Cataclysm 5.1 ROM a try. It has a lot of positive reviews and is very close (in terms of UI) to the stock Android experience which is always a plus.
In this short article I will go through a step-by-step approach as to how I went about replacing my stock Nexus 5 Lollipop with the Cataclysm 5.1.1 ROM.
The Cisco IronPort virtual edition has been out for about a year now. It’s still not quite as mature as we would like for it to be; for example, it lacks support for Hyper-V, modifying the CPU core allocation to meet peak performance demands, etc.
One of the unsupported ‘configurations’ is virtual machine snapshots.
This is what I was advised by a TAC engineer:
“The software was written for physical hardware, and operations such as snapping an image and reloading it at a later point in time, is not supported.
Our appliances often have files open, and taking a snapshot while a file is being written, can leave you with a worthless snapshot, that can’t be executed. And thats only one of the problems you may encounter
…
I can confirm it is not supported, but nevertheless it will probably work when the machine is completely shut down. It will probably fail when the machine was ‘powered on’. There are no power states like pause or standby which would take the filesystem into a state that would be safe for a snapshot.
I can confirm, no problem if version mismatch due to a revert. A “revert” of the machine (CLI> revert) also results in such a mismatch, but this is automatically resolved.”
So as you can see, snapshotting your ESA isn’t technically supported HOWEVER if you follow the basic steps below you shouldn’t have any issues.