elihuj's Posts

Oh cool! Thank you LucD! Now when I run this, nothing terrible will happen correct? This will ONLY run the report against whatever I have in the esxihosts.txt file right?
We are looking to get a report of missing patches and such from our hosts. I found this document from bbambalova, and wanted to see if anyone could assist me with it. From what I can tell, right ... See more...
We are looking to get a report of missing patches and such from our hosts. I found this document from bbambalova, and wanted to see if anyone could assist me with it. From what I can tell, right now this script will run against ALL hosts found via the $vmHosts = Get-VMHost variable. We want to be able to run this against a specific set of hosts or even select clusters only; not the entire environment. I have tested with the following: $vmHosts = Get-Content "C:\esxihosts.txt" Within that text file, I have a few hostnames that I'd like to run the report against. When I run the script (ExportCompliance.ps1 $vmHOsts "C:\Reports\"), I get the following error: Cannot process argument transformation on parameter 'inventoryItems'. Cannot convert the "esx1.host.com" value of type "system.String" to type "VMware.VimAutomation.ViCore.Types.V1.Inventory.InventoryItem[]". Is there any way I can set this up to run as I'd like? Or is there a better way to go about accomplishing my goal? Thank you.
Nice, thank you vmroyale!
Our best practice has always been to put hosts into maintenance mode first, and then scan for updates with Update Manager. We are looking at implementing scheduled scans, and the only thing stopp... See more...
Our best practice has always been to put hosts into maintenance mode first, and then scan for updates with Update Manager. We are looking at implementing scheduled scans, and the only thing stopping us is our practice of maintenance mode beforehand. Is this needed? Or are we safely able to scan production hosts with active VM's?
We have three clusters of ESXi 4.1 host servers in our environment. Each host is configured the same, and each host is a part of the same vSphere Management Assistant. I have noticed recently tha... See more...
We have three clusters of ESXi 4.1 host servers in our environment. Each host is configured the same, and each host is a part of the same vSphere Management Assistant. I have noticed recently that on one of the clusters, all of the hosts continue to show the same login errors regarding the vMA. The error messages simply show "Cannot login root@[ip of vma]". I'm pretty confident that this is occurring because we have lockdown mode enabled. When I log into the vMA and connect to the host (that is locked down), it asks for a username. When I input the correct root credentials, I get "Error: Permission to perform this operation was denied". And with a host that does NOT have lockdown mode enabled, I can connect successfully. Is there any reason why I continuously see these login errors for my hosts? I mean literally multiple times a day. It's filling up my logs pretty quickly, and I just want to know why. Any help is appreciated, thank you.
Thanks for the reply Ed. How do you go about profiling your VM's though to see if there are hot folders?
Yes I know! I just can't afford to get a second SSD for redundancy atm. For now regular backups will have to do. Thank you again for your input.
Thanks for the reply Brian. Are there any other special considerations to look at when using an SSD for a datastore? Or is it just plug in and good to go?
I am currentlly using a 7200 rpm Sata II drive for my datastore, and there is a very noticeable lag in access times. In order to increase I/Os I have decided to go with an SSD. I wanted to see if... See more...
I am currentlly using a 7200 rpm Sata II drive for my datastore, and there is a very noticeable lag in access times. In order to increase I/Os I have decided to go with an SSD. I wanted to see if there were any best practices for doing this. Would I be better off replacing the current drive with an SSD and use it as my datastore entirely? Or would using the SSD to store the vm's swapfile only be a better choice? Thank you for any input.