Migrate to VCSA Stumbling Blocks
I would like to show you my stumbling blocks when migrating to VCSA.
I would like to show you my stumbling blocks when migrating to VCSA.
I would like to encourage you to report your bugs with the smiley at the top right corner.
A few days ago vSphere 6.0 Update 3 was announced. Beside the bugfixes and security updates there is a feature I would like to turn out.
Recently I had to upgrade from vCenter 6.0 U2 to 6.0 U2a because of this WebClient Bug (KB 2144934) But there are many stumbling blocks I would like to inform you about!
You have to look at the Modules in PowerCLI 6.5. When you wrote your Scripts with the PowerShell ISE you had to load the PSSnapins before. In 6.5 there are no longer PSSnapins! Now there are only Modules!
Everybody knows this warning. Now I show you how to change the vCenter Certificate to avoid this ugly page.
Last week I saw the new vSphere 6.5 at VMworld 2016 (EU). I’m very happy with the upcoming features. Some of them are extremely cool and some are overdue.
In times like these, where daily security leaks are published, it’s time to check some basics. Run the following PowerCLI Script to see if the SSH-Service is running and disable it! #List Hosts into Array $arr = @() $arr = (Get-VMHost * | Foreach {($_ | Get-VMHostService | Where { $_.Key -eq “TSM-SSH”})} | select VMHost,Label,Policy,Running | Sort VMHost) #Filter running SSH or Enabled $sshOn = $arr | Where-Object { ($_.Running -eq “True”) -or ($_.Policy -eq “on”) } #If SSH on ->…
Take a look at the first bugs i saw within 10 Minutes on vCenter 6.
Cleanup your DB before the upgrade is not a “must” but this is a good moment.