TacoSauce's Posts

Hi dwchan, We experience the same in our nested test environment. Did you succeeded to find a solution?
Hi, I just took a look on the Content Pack Marketplace of our Log Insight environment. It mentioned 4 updates available, so I upgraded the VMware NSX vsphere, VMware -vSAN and VMware vRops 6.7... See more...
Hi, I just took a look on the Content Pack Marketplace of our Log Insight environment. It mentioned 4 updates available, so I upgraded the VMware NSX vsphere, VMware -vSAN and VMware vRops 6.7+ content packs successfully, the upgrade of the VMware -vSpere 8.0 content pack was not succesful. The GUI throw this error: I uninstalled the previous Content Pack v4.6 we used and made a second attempt. Unfortunately the same result. Has anyone a solution for this problem?
There is an official KB now regarding the high memory usage metrics: VMware Knowledge Base
This is also the feedback which I got from GSS: Would you mind follow recommendation from release notes in VROPS 6.7  and shee how it goes please? https://docs.vmware.com/en/vRealize-Oper... See more...
This is also the feedback which I got from GSS: Would you mind follow recommendation from release notes in VROPS 6.7  and shee how it goes please? https://docs.vmware.com/en/vRealize-Operations-Manager/6.7/rn/vRealize-Operations-Manager-67.html Note: If interested in the older Memory|Usage (%) metric of virtual machines, which was based on active memory, use the Memory|Guest Active Memory (%) replacement metric. This out of the box metric is disabled and first needs to be enabled in the corresponding policy of a virtual machine.
Yep, you're right. GSS noticed me about this KB this week, which solved the issue. VMware Knowledge Base Thnx
The Update manager does work in the vSphere web client but when I open it in the H5 client I get the following error: com.vmware.vim.vmomi.core.exception.CertificateValidationException: Serv... See more...
The Update manager does work in the vSphere web client but when I open it in the H5 client I get the following error: com.vmware.vim.vmomi.core.exception.CertificateValidationException: Server certificate assertion not verified and thumbprint not matched I already renewed all certificates and restarted the vcsa but that didn't solve the issue.
Thnx! Now I understand your answer!
Hi Luc, Thanks for your reply, sorry but I don't understand your answer. I thought that when you get a Depreciation Warning, other means of accomplishing the task are preferred? So is there ... See more...
Hi Luc, Thanks for your reply, sorry but I don't understand your answer. I thought that when you get a Depreciation Warning, other means of accomplishing the task are preferred? So is there another cmdlet for applying permissions or in other words what's wrong with my script?
I use PowerCLI to set permissions on Windows vm's in our environment. I've found the "New-VIPermission" cmdlet, but when I use this cmdlet I get some warnings. When a run this code: I get t... See more...
I use PowerCLI to set permissions on Windows vm's in our environment. I've found the "New-VIPermission" cmdlet, but when I use this cmdlet I get some warnings. When a run this code: I get these warnings: WARNING: Parameter 'Entity' is obsolete. This parameter no longer accepts multiple values. WARNING: Parameter 'Principal' is obsolete. This parameter no longer accepts multiple values. I use a cmdlet which is documented in the VMware vSphere 6.0 Documentation Center, so what's the issue? With regards, Wouter
Zach, you're explanation seems logical and I hope it's the true . Maybe VMware can clarify this in future KB documentation. Cheers, Wouter
Hi Zach, thanks for your quick reply. You suggest that everyone who's using vsan or an other kind of datastore is having this issue? with regards, Wouter
Hi, Today I noticed the space utilization graph of our VSAN Datastore. When I looked at the figures I was surprised!  Why is the "Other" File Type over the 5TB and our biggest consumer of our ... See more...
Hi, Today I noticed the space utilization graph of our VSAN Datastore. When I looked at the figures I was surprised!  Why is the "Other" File Type over the 5TB and our biggest consumer of our VSAN datastore??? There's no backup data or ISO's on our VSAN and when I browse the datastore I doesn't find any strange files c.q. directories. Does anyone has an explanation for this? With regards, Wouter
In our VSAN POC environment we figured out that we have to keep 40% free hdd disk space, to get a green Passed limit check after 1 additional host failure in the VSAN Health Plugin: N... See more...
In our VSAN POC environment we figured out that we have to keep 40% free hdd disk space, to get a green Passed limit check after 1 additional host failure in the VSAN Health Plugin: Now I am wondering if there is some kind of a policy when the threshold of 40% is hit it isn't possible for other users to deploy, clone or snapshot in our VSAN Cluster? With regards, Wouter
Hi Jon, VMware vCenter 5.5.0 Build 1750787. Our esxi hosts run esxi version 5.5.0,2143827 With regards, Wouter
For management purposes I want to know when some colleague renames a VM in our environment. For this purpose I use a default vcenter alarm which triggers on the event "VM renamed". The alarm tri... See more...
For management purposes I want to know when some colleague renames a VM in our environment. For this purpose I use a default vcenter alarm which triggers on the event "VM renamed". The alarm triggers when someone manually renames a VM but the alarm is also triggered when a drs action is completed by the system. Al least that's what I see in the task/event pane. When I look in the tasks pane I see a couple of seconds before the alarm is triggered the task "DRS migrated VMx from Host X to Host Y in Cluster X". Why triggers this event the "Renaming" alarm? Cheers, Wouter
Okay, I will give it a try. I will give a response next week..
Hi Luc, Thnx for your quick reply! Here's a screenshot of the csv file, (notepad++  "Show All Characters" selected) And here is the output from the PowerShell Console:
Hi, I've a lot of test vm's which are bullying our central storage. Now I've found the perfect script from Luc D which imports data from a csv file and then limits the disks. Unfortunately I... See more...
Hi, I've a lot of test vm's which are bullying our central storage. Now I've found the perfect script from Luc D which imports data from a csv file and then limits the disks. Unfortunately I get red errors when I fire it up: Get-VM : Cannot validate argument on parameter 'Name'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. At H:\PowerCLI\VmIOPSLimit.ps1:13 char:22 +   $vm = Get-VM -Name $group.Name +                      ~~~~~~~~~~~     + CategoryInfo          : InvalidData: (:) [Get-VM], ParameterBindingValidationException     + FullyQualifiedErrorId : ParameterArgumentValidationError,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetVM You cannot call a method on a null-valued expression. At H:\PowerCLI\VmIOPSLimit.ps1:23 char:3 +   $vm.ExtensionData.ReconfigVM_Task($spec) +   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : InvalidOperation: (:) [], RuntimeException     + FullyQualifiedErrorId : InvokeMethodOnNull Can someone help me out? Here's the script from Luc D. which I found on the powercli community: foreach($group in (Import-Csv C:\vmiopslimit.csv -UseCulture | Group-Object -Property vmName)){   $vm = Get-VM -Name $group.Name   $spec = New-Object VMware.Vim.VirtualMachineConfigSpec   $vm.ExtensionData.Config.Hardware.Device |  where {$_ -is [VMware.Vim.VirtualDisk]} | %{     $dev = New-Object VMware.Vim.VirtualDeviceConfigSpec     $dev.Operation = "edit"     $dev.Device = $_     $label = $_.DeviceInfo.Label     $dev.Device.StorageIOAllocation.Limit = $group.Group | where {$_.Harddisk -eq $label} | Select -ExpandProperty IOPSLimit     $spec.DeviceChange += $dev   }   $vm.ExtensionData.ReconfigVM_Task($spec) } The CSV file should look like this "vmName","harddisk","IOPSLimit" "VM1","Hard disk 1","50" "VM1","Hard disk 2","75" "VM2","Hard disk 1","75" "VM3","Hard disk 1","35" "VM3","Hard disk 2","55" "VM3","Hard disk 3","65"
After upgrading to vSphere 5.1, I am not able to add my scripts to the cronjob of my ESXi nodes. In vSphere 5.01 I was able to create persistent cronjobs by adding the following code to /etc/r... See more...
After upgrading to vSphere 5.1, I am not able to add my scripts to the cronjob of my ESXi nodes. In vSphere 5.01 I was able to create persistent cronjobs by adding the following code to /etc/rc.local: /bin/kill $(cat /var/run/crond.pid) echo '1    0    *   *   *   /sbin/script1.sh' >> /var/spool/cron/crontabs/root echo '2    0    *   *   *   /sbin/script2.sh' >> /var/spool/cron/crontabs/root /bin/busybox crond This worked fine, the scripts were automatically scheduled and were persistent after a reboot. After the upgrade I'm not able to schedule my scripts anymore. I've adjusted the above code and wrote it to the /etc/rc.local.d/local.sh file: /bin/kill $(cat /var/run/crond.pid) echo "1    0    *   *   *   /sbin/script1_ssh.sh" >> /var/spool/cron/crontabs/root echo "2    0    *   *   *   /sbin/script2_file.sh" >> /var/spool/cron/crontabs/root /usr/lib/vmware/busybox/bin/busybox crond After a reboot the /var/spool/cron/crontabs/root file isn't updated anymore!!!! Can someone help me out? Cheers
Thnx Andreas, I managed the limits succesfully.