Thursday, 8 June 2017

Setting the local to English United Kingdom using PowerShell

Setting the local to English United Kingdom using PowerShell

Set-Culture en-GB
Set-WinSystemLocale en-GB
Set-WinHomeLocation -GeoId 242

Set-WinUserLanguageList en-GB

Thursday, 20 April 2017

Resetting lost ESXi password

Works on ESXi 6.0

If you have access to vCenter..

# Just so it contains one or more VMHost objects.
# To reset all ESXi host passwords use
# $vmhosts = Get-VMHost

Connect-VICenter -Server 

$NewCredential = Get-Credential -UserName "root" -Message "Enter an existing ESXi username (not vCenter), and what you want their password to be reset to."

Foreach ($vmhost in $vmhosts) {
    $esxcli = get-esxcli -vmhost $vmhost -v2 #Gain access to ESXCLI on the host.
    $esxcliargs = $esxcli.system.account.set.CreateArgs() #Get Parameter list (Arguments)
    $ = $NewCredential.UserName #Specify the user to reset
    $esxcliargs.password = $NewCredential.GetNetworkCredential().Password #Specify the new password
    $esxcliargs.passwordconfirmation = $NewCredential.GetNetworkCredential().Password
    Write-Host ("Resetting password for: " + $vmhost) #Debug line so admin can see what's happening.
    $esxcli.system.account.set.Invoke($esxcliargs) #Run command, if returns "true" it was successful.

Friday, 7 April 2017

Removing all the crap from Windows 10

A great write up on how to remove all the detritus Microsoft installs onto Windows 10 OOB 

Wednesday, 5 April 2017

For the device-specific module (DSM) named Microsoft DSM, versions do not match between node

I was asked by a customer to introduce a new Hyper-V 2012 R2 core mode node into an existing cluster.
As always I checked the existing nodes for Windows updates and patched the new node accordingly. The Add node menu item was using in the failover cluster manager and all tests had been selected. Quickly the validation failed with the error below.

Upon closer inspection we can see that the Microsoft DSM version doesn't match! So Windows update was used to check for missing updates, but both nodes showed no updates available.

I used PowerShell to compare the MSDSM.SYS files on both systems, and as we can see below the FilePrivatePart is newer.

I Googled about to find out if there was a hotfix that might have updated the MSDSM.SYS file but no joy.

In the end we narrowed it down to the fact that the March preview update has updated the file. After rolling this out to all cluster nodes the validation passed and the new node was added.

Tuesday, 3 January 2017

Dell Storage Manager Virtual Appliance - The provided manifest file is invalid

When deploying the Dell Storage Manager Virtual Appliance  DSM VirtualAppliance- into a VMware vSphere 6.x platform, you see the error:

The provided manifest file is invalid: Invalid OVF manifest entry:

A work around to this is to download 7 Zip and extract the OVA to c:\Temp folder. Then download the OVAtool from VMware:

C:\Program Files\VMware\VMware OVF Tool>ovftool.exe  "c:\Temp\DSMBuildVM-" "c:\Temp\DSMBuildVM-"

The manifest validates
Opening OVA target: DSM.ova
Writing OVA package: DSM.ova
Transfer Completed
 - No manifest entry found for: 'DSMBuildVM-'.
 - File is missing from the manifest: 'DSMBuildVM-'.

Completed successfully.

Now when you try to deploy the OVA is should go through.