Strange, which .Net version do you have installed? Not sure where you got that snippet from, I have no idea where this $StorageDevice object is coming from. Nor do I understand which "totals" you...
See more...
Strange, which .Net version do you have installed? Not sure where you got that snippet from, I have no idea where this $StorageDevice object is coming from. Nor do I understand which "totals" you are after. Does that include all storage types (VMFS, iSCSI, NFS, USB, ...)?
You are having 2 types of output streams. The Verbose stream which can simply avoid by removing the Verbose switch from the Invoke-VMScript cmdlet. The standard output of the cmdlet can be stored...
See more...
You are having 2 types of output streams. The Verbose stream which can simply avoid by removing the Verbose switch from the Invoke-VMScript cmdlet. The standard output of the cmdlet can be stored in a variable (if you need the results later on)
$result = Invoke-VMScript -VM $VmName -ScriptText $cmdDNS1 -GuestUser administrator -GuestPassword xxxxxx
Or you can redirect it to NULL
Invoke-VMScript -VM $VmName -ScriptText $cmdDNS1 -GuestUser administrator -GuestPassword xxxxxx | Out-Null
Tank you LucD You'r right, Have an error to pit to the good Ethernet issue resolve just one more question : is there any way to ignore the output of invoke-vmscript . I mean this output ####...
See more...
Tank you LucD You'r right, Have an error to pit to the good Ethernet issue resolve just one more question : is there any way to ignore the output of invoke-vmscript . I mean this output ########################################################################## VERBOSE: Performing the operation "Invoke-VMScript" on target "win2019". VERBOSE: 11/10/2023 9:31:45 PM Invoke-VMScript Finished execution VM : win2019 ExitCode : 0 ScriptOutput : Uid : /VIServer=vsphere.local\administrator@10.95.53.10:443/VirtualMachine=VirtualMachine-vm-130/VMScriptResult=-841959517_0/ Length : 2 ##########################################################################
So we have VMWare tools pushed to out ESXi hosts using the offline bundle and baseline. What now happens is we get the yellow banner message that VMWare tools is out of date and the offer to update....
See more...
So we have VMWare tools pushed to out ESXi hosts using the offline bundle and baseline. What now happens is we get the yellow banner message that VMWare tools is out of date and the offer to update. If I select that and no advanced option, it works fine and reboots the VM. If, however, I set the advanced options of /s /v "/qn REBOOT=ReallySuppress" then the installer seems to start and think about it a few seconds and stop again and the VM returns to how it was before still showing the banner. On a hunch, I logged into one of the VMs, install the bundled Visual C++ and rebooted and then tried again from the vSphere web interface and this time it worked. I now feel its the Visual C++ but I cannot figure how to deploy it and reboot and then retry the installer and besides it means every VM will need a reboot anyway because Visual C++ forces a reboot. We also tried an SCCM deployment and it works but it does only the tools install. Not the Visual C++ so the Tools version is current wherever we have tested the push those machines don't have the right version of the runtime dependency. I could really use some help here with what has worked for you guys in the past. Thanks.
Hi LucD, I get the error: Add-Type : Cannot add type due to the following exception: Compiler executable file csc.exe cannot be found.. Verify that Microsoft .NET Framework 3.5 is installed. On x6...
See more...
Hi LucD, I get the error: Add-Type : Cannot add type due to the following exception: Compiler executable file csc.exe cannot be found.. Verify that Microsoft .NET Framework 3.5 is installed. On x64-based versions of Windows, you must also install the WOW64 feature. Also, I simply need totals, not what's missing, if that simplifies my request. Thanks again.
Hello, Things could behave differently. Are you experiencing a bottleneck? SSDs are always better than HDDs in terms of performance. The vmdk file runs on one of those types of disks, so it should i...
See more...
Hello, Things could behave differently. Are you experiencing a bottleneck? SSDs are always better than HDDs in terms of performance. The vmdk file runs on one of those types of disks, so it should impact performance. What can affect performance in the data center? By the way, is the host where your vmdk resides full-flash, hybrid-flash, or fully mechanical? You can also manually configure Shares and Limit - IOPS or select a VM storage policy. The storage policies in certain storage environments determine how the virtual machine storage objects are provisioned and allocated within the storage resource to guarantee the required level of service. Reference: https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-resource-management/GUID-7686FEC3-1FAC-4DA7-B698-B808C44E5E96.html Hope this is helpful! Kind regards!
Check the status of the WCP service by SSH onto your vCenter and running service-control --status wcp if it's not started use service-control --start wcp There's also this Dell support KB Dell EMC V...
See more...
Check the status of the WCP service by SSH onto your vCenter and running service-control --status wcp if it's not started use service-control --start wcp There's also this Dell support KB Dell EMC VxRail: ESXi host fails to enter or exit maintenance mode with the Error message: Failed to enter name Namespaces Maintenance mode | Dell UK Which version of vCenter are you running as people have also resolved this issue by upgrading to a later version?
Hello I got this warning output of invoke-vmscript. what this mean and to correct VERBOSE: Performing the operation "Invoke-VMScript" on target "win2019-2". VERBOSE: 11/10/2023 5:16:30 PM Invo...
See more...
Hello I got this warning output of invoke-vmscript. what this mean and to correct VERBOSE: Performing the operation "Invoke-VMScript" on target "win2019-2". VERBOSE: 11/10/2023 5:16:30 PM Invoke-VMScript Finished execution VM : win2019-2 ExitCode : 0 ScriptOutput : The filename, directory name, or volume label syntax is incorrect. The script $cmdIP = "netsh interface ipv4 set address name=`"$Ethernet`" static $newIP 255.255.255.0 $newGateWay" $cmdDNS1 = "netsh interface ipv4 set dns name=`"$Ethernet`" static $DNS" #$vm = Get-VM $hostname Invoke-VMScript -VM $VmName -ScriptText $cmdIP -GuestUser administrator -GuestPassword xxxxxx -Verbose write-host "##########################################################################" write-host "Setting network for $Ethernet in $VmName machine #########################" write-host "##########################################################################" Invoke-VMScript -VM $VmName -ScriptText $cmdDNS1 -GuestUser administrator -GuestPassword xxxxxx -Verbose write-host "##########################################################################" write-host "Setting DNS network for $Ethernet in $VmName machine #####################" write-host "##########################################################################"
Hello This is a bit strange case. You may try conversion of your machine (e.g. install Converter in it and convert 'this local machine') but then select only drive and deselect reconfiguration. A...
See more...
Hello This is a bit strange case. You may try conversion of your machine (e.g. install Converter in it and convert 'this local machine') but then select only drive and deselect reconfiguration. After the cloning completes, run c 'Configure machine' on the cloned VM. And cross fingers HTH, Plamen
Thanks for sending the script. I tried to run it but it errored out, but it got me thinking and I decided to troubleshoot my VMDIR issue. I logged directly into the vCenter and ran these commands: ...
See more...
Thanks for sending the script. I tried to run it but it errored out, but it got me thinking and I decided to troubleshoot my VMDIR issue. I logged directly into the vCenter and ran these commands: cd /usr/lib/vmware-vmdir/bin ./vdcrepadmin -f showservers -h localhost -u administrator ./vdcrepadmin -f showpartners -h localhost -u administrator I found a legacy 7.0.3 vCenter which I had decommissioned long ago, but had not removed it properly. I tried to use Using the cmsso command to unregister vCenter with External PSC or vCenter with Embedded PSC from Single Sign-On (2106736) (vmware.com) to remove it, but that also errored out. I was about to throw in the towel, but instead I pulled the old vCenter out of mothballs and brought it back online. Sure enough, that fixed the VMDIR error when upgrading the second 8.0 vCenter and the upgrade completed successfully. I'll attempt to decommission and unlink this old vCenter properly next. Thanks for the help!
Hello, Sorry, in ESXi 7.x there are three types of TCP/IP stack, the "default" one, the "vMotion" one and the "Provisioning" one, nothing else. Regards, Ferdinando
Relative to OPS, that makes sense. After all, DPU support wasn't introduced until vSphere 8. What about the mirror stack? Do you see that in vSphere 7? Thanks, Joe
Hello jicooper, No, I don't think it's so, the "OPS" TCP/IP stack was absent till the first build of ESXi 8.0, I can tell you that ESXi 7.0U3n it does not feature any "OPS" TCP/IP stack, the same ...
See more...
Hello jicooper, No, I don't think it's so, the "OPS" TCP/IP stack was absent till the first build of ESXi 8.0, I can tell you that ESXi 7.0U3n it does not feature any "OPS" TCP/IP stack, the same way as previous versions of which I still have memory. Regards, Ferdinando
I had this problem as well trying to delete an old VMFSL partition on a 2nd disk. mklabel didn't work for me either. Every time I tried using the partedUtil to remove the partition, i would get an ...
See more...
I had this problem as well trying to delete an old VMFSL partition on a 2nd disk. mklabel didn't work for me either. Every time I tried using the partedUtil to remove the partition, i would get an error pointing to it being ReadOnly. This VMFSL partition was on a 2nd drive in my system and had once had ESXi installed there. I was able to remove all of the other partitions from that drive with partedUtil, just not this one. I found that the process in this article worked for me. https://serverfault.com/questions/1064921/unable-to-delete-partition-2-from-device-dev-disks-naa-50000398b8497b91 Just booted the system to an older ESXi 6.7 install and jumped out from there to run partedUtil. I had tried with a newer ESXi 8.02, but that still held on to the partition. The key was using an install ISO prior to 7.x.
I know this is an ancient thread but I wanted to say thank you to Luc. This still works in 8.0U2. I have been meaning to find a way to export and import our custom roles for ages and finally got arou...
See more...
I know this is an ancient thread but I wanted to say thank you to Luc. This still works in 8.0U2. I have been meaning to find a way to export and import our custom roles for ages and finally got around to it.
so when using upgrade you didn't have intel i350 drivers, or didn't have the Broadcom nic drivers? using install did install the missing "XXX" driver? Worth noting: be sure you are using the la...
See more...
so when using upgrade you didn't have intel i350 drivers, or didn't have the Broadcom nic drivers? using install did install the missing "XXX" driver? Worth noting: be sure you are using the latest esxi 7 installer, not the initial release - use esxi7 U3 version, which has patches fixes and new drivers in it, over the older/initial release 7.0 version.
1. Toggle PCIE device passthrough in the ESXI host 2. Reboot the host 3. Make sure VM is powered off. 4. On the VM you are passing through, first make sure there are no snapshots- if any delete &...
See more...
1. Toggle PCIE device passthrough in the ESXI host 2. Reboot the host 3. Make sure VM is powered off. 4. On the VM you are passing through, first make sure there are no snapshots- if any delete & consolidate all snapshots. Note: you can't have or use snapshots on a VM that has GPU passthrough setup. 5. Disable/uncheck CPU features: IOMMU and hardware assisted virtualization passthrough 6. Reserve memory in the VM (make sure the host has enough free at the time you power on the VM - eg if you have 16GB reserved, the but the host only has 10 Free right now, power on VM will fail). 7. Edit VM hardware config and Add the GPU. 8. power on VM and install the drivers. The basics are covered here in video form here: https://www.youtube.com/watch?v=aFXtUaFjiO4&t=3s CPU: Mem:
