Save your credentials for VIServer connections
Don’t put your credentials into the PowerCLI scripts! There is an option to store your credentials on the Host.
Don’t put your credentials into the PowerCLI scripts! There is an option to store your credentials on the Host.
Everybody knows this warning. Now I show you how to change the vCenter Certificate to avoid this ugly page.
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.
Do you also have some concerns before updating your vCenter? For sure we all have a Plan and a Plan B, Plan C …, but there is always someting you didn’t considered or expected. I would like to show you my Upgrade from 5.5 U3b to 6.0 U2.
I just want to know how much space does your vCenter DB consume and what are your biggest tables?