When setting up a new vRealize Operations 6.6 environment (using the vRealize Operations Manager Initial Setup wizard) the password is not accepted despite apparently meeting the complexity requirements.
The criteria stated are that passwords must:
- Be at least eight characters long
- Be different from your username
- Contain lowercase, uppercase, numeric, and non-alphanumeric characters
It appears that full stop and question mark do not count as the “non-alphanumeric” characters required.
Choose another password which includes a different, acceptable, non-alphanumeric character such as the exclamation mark.
A quick PowerCLI one liner to locate VMs with thick-provisioned disks attached.
VM $_ )
.StorageFormat -Contains "Thick"}
When using a GoPro Session Action camera it’s important to ensure that an approved MicroSD card is used. As this short video demonstrates, this really makes a difference to the performance. Two 32GB SanDisk MicroSD Cards, the first is the “Ultra” brand and the second the “Extreme” model which is listed on the approved card list. With the “Ultra” card it takes 30 seconds from the button being pressed to the camera starting to record. This is cut to just 2 seconds when using the “Extreme” card. Continue reading
With a list of Surnames in a text file I wanted to see how many start with A, how many with B, and so on. This is my PowerShell solution:
(Get-Content .\surnames.txt).Substring(0,1).ToUpper() |
Sort-Object | Group-Object |Select-Object Name, Count
Example Input (surnames.txt file):
- The VMware vSphere ESXi UNMAP command doesn’t release space on some or all volumes on a Dell EqualLogic SAN array running v8 firmware (may apply to other versions too). Using the following command in an SSH session to a 6.0u2 host (again, will apply to other versions):
esxcli storage vmfs unmap –l MYVOLUMENAME
- The volumes are VMFS5 (and always have been- they haven’t been upgraded from VMFS3).
- Replication is enabled for the volumes that won’t rethin.
UNMAP doesn’t work on the EqualLogic when Replication is enabled. It doesn’t return an error to the SSH session, and the temporary rethinning file is still created, but the disk is not thinned.
Disable replication on the volume, re-thin the volume using the UNMAP command, then re-configure replication. Unfortunately this means the entire volume must be re-copied to the replication partner and this may impact bandwidth usage and replication schedules on larger volumes.