GalNeb, Same environment and same issue. The fix was a combination of things: The AD accounts for both your 2016 jumpboxes, your vCenter and PSC must be set to allow for Kerberos authentica...
See more...
GalNeb, Same environment and same issue. The fix was a combination of things: The AD accounts for both your 2016 jumpboxes, your vCenter and PSC must be set to allow for Kerberos authentication encryption in AD. This is also required for your service/user accounts. The user accounts are easy to do. All you have to do for them is open up the account properties and click on the account tab. In the Account options scroll down and click the boxes for "This account supports Kerberos AES 128bit encryption." and "This account supports Kerberos AES 256 bit encryption." That's it for the users. The AD accounts need to be done with powershell Below is the check script and the fix script: Check: Get-ADComputer -filter * -SearchBase "OU="your OU",DC="Your domain path"" -Properties msDS-SupportedEncryptionTypes,KerberosEncryptionType | select Name,msDS-SupportedEncryption TypesKerberosEncryptionType | sort msDS-SupportedEncryptionTypes | FT The output will list the computer objects in your OU and their Kerberos Encryption type. When you create a computer account manually this creates a blank value in this field so you have to run the bottom command to set them to AES 128 and AES 256 Set-ADComputer -Identity "YourComputerName" -Replace @{"msDS-SupportedEncryptionTypes"="24"} I'm sure LucD could come up with a script for multiple systems. If you set the above value to "28" then that will forcefully include AES128, AES 256 and RC4. "24 is just the AES 128 and 256. You need to make sure you make this change to the jumpbox and the vCenter and PSC appliance AD computer accounts. Hope this helps. It was the fix for our stuff.
The release notes said to update vCenter to Update 3b FIRST then to update the hosts. What this did to me was isolate my hosts from vCenter, left them running but no way into them. Couldn't use t...
See more...
The release notes said to update vCenter to Update 3b FIRST then to update the hosts. What this did to me was isolate my hosts from vCenter, left them running but no way into them. Couldn't use the VI Client, SSH or iLo until I rebooted the hosts with the running VM's on them (causing them to crash obviously). Anyone else experience this? I can't find anything from VMware.. Although in another environment we have vCenter 5.5 Update 3a is managing an ESXi 5.5 3b host without any issues.. Did they just get this backwards? I've been finding issues contradictory statements in the release notes as of late. I wish I could've stayed on 4.1. 5.5 has been really buggy and unpredictable. If anyone has come across this and found a better solution then please hit me up. Thanks!
I've always been under the impression that it will have some impact on performance but I can't seem to find anything about it anywhere. In my environment I can't afford to do anything that would ...
See more...
I've always been under the impression that it will have some impact on performance but I can't seem to find anything about it anywhere. In my environment I can't afford to do anything that would impact performance. What are your opinions and do you have any hard data that you could point me to that will confirm or debunk this?
All, For security we are required to write zero our VM HD's when decommissioning them. I would like to use a PowerCLI script to do this. The only way I know to do this is by logging into th...
See more...
All, For security we are required to write zero our VM HD's when decommissioning them. I would like to use a PowerCLI script to do this. The only way I know to do this is by logging into the host and running vmkfstools -w [path to vmdk file]. Unfortunately, I have to wait until one drive is done before I can start on another. If there is a simpler way within the CLI or if anyone has a script that would be helpful. Thanks!
LucD, I appreciate the response. I will attempt to piece something together and see if I can get something going. I'll post the results here. Thanks for the help!
All, I've tried to automate migration from E1000 to vmxnet3 on some a 2008 R2 x64 test server. It allows me to go the following successfully: Get-VM <VM Name> | Get-NetworkAdapter | Set-Ne...
See more...
All, I've tried to automate migration from E1000 to vmxnet3 on some a 2008 R2 x64 test server. It allows me to go the following successfully: Get-VM <VM Name> | Get-NetworkAdapter | Set-NetworkAdapter -type "vmxnet3" However, when I check the device manager in the OS it still shows as E1000.. It does keep IP config but when I try to vMotion from one host to another or Storage vMotion to another datastore it fails at 78% With the following error: "A general system error occured: Source detected that the destination failed to resume." A reboot of the VM does nothing until I cange it back to E1000 in powershell. It works when the VM is powered down but the IP config is dumped. I can't find anything on the KB or in the forums that helps and I've seen some other "fancier" scripts out there that migrate NICs, paravirtual, and HW upgrade but I dont need all that and the scripts are too cumbersome to try and manipulate to my environment. Any input would be appreciated! Thanks!
All, I'm running a 4.1 infrastructure in 4 different locations and I needed a tool to tell me the following: - VM Names - Power State (On or Off) - VM Hardware Version - VMware too...
See more...
All, I'm running a 4.1 infrastructure in 4 different locations and I needed a tool to tell me the following: - VM Names - Power State (On or Off) - VM Hardware Version - VMware tools current or out of date - ISO Path - Connection state of the CD Drive - Remote Device (This tells me if a VM's CD Drive is set to Emulate IDE instead of the revommended Passthrough IDE) - Network Adapter Type - Datastore - Snapshot Name - Snapshot Size MB - Snapshot Description Just wanted to share.. Save as .ps1 and run from the ISE. Hit me up if you have any questions.
This is what I'm running from the ISE. (Ignore my Set-PowerCLIConfiguration. I plan to use this script for multiple vCenter Servers..) But it still only places and empty .csv in the -path no erro...
See more...
This is what I'm running from the ISE. (Ignore my Set-PowerCLIConfiguration. I plan to use this script for multiple vCenter Servers..) But it still only places and empty .csv in the -path no errors are thrown. Add-PSSnapin VMware.VimAutomation.Core -erroraction SilentlyContinue Set-PowerCLIConfiguration -DefaultVIServerMode Multiple -Confirm:$false connect-viserver 'vCenter' -WarningAction SilentlyContinue | out-null Get-VM | Get-Annotation | Select @{N="VM";E={$_.AnnotatedEntity.Name}},Name,Value | Export-Csv -Path $env:userprofile\desktop\VMAnnotations.csv -NoTypeInformation -UseCulture Set-PowerCLIConfiguration -DefaultVIServerMode Single -Confirm:$false Sorry I don't know how to paste the code properly in the forum...
All, I'm looking for a way to priortize a startup and shutdown of VM's and ESXi 4.1 hosts in the event of a datacenter outage, leaving the host that is running my vCenter vm powered on. I wan...
See more...
All, I'm looking for a way to priortize a startup and shutdown of VM's and ESXi 4.1 hosts in the event of a datacenter outage, leaving the host that is running my vCenter vm powered on. I want to be able to shut the guests down gracefully in an order of my choosing, as well as power them back up (after powering the hosts on manually). I'm looking to use the annotations field in the vm's summary tab as a piece to determine the priority of their shutdown and startup. So, for example, If I priortize my vm's by Group 1; Group 2; Group 3 and have the Script scan the annotations field of the vm's determine which group to shutdown first and which to shutdown last and vise versa for startups. If you have a simpler idea of how to do this then please advise! Thanks again for your expertise and assistance!