By reading through this thread and following the links posted in it.
I see you’ve posted before about vRealize Operations, make use of it.
By reading through this thread and following the links posted in it.
I see you’ve posted before about vRealize Operations, make use of it.
I added it to the script as the first command after ForEach and it still shows them all.
Clear-Variable -name esx
Clear-Variable -name esxhosts
Clear-Variable -name esxcli
$esxhosts = Get-VMHost
Foreach ($esx in $esxhosts){
$esxcli.storage.core.adapter.rescan.Invoke(@{all=$true})
$esxcli = Get-EsxCli -VMHost $esx.Name -V2
Write-Host $esx.Name
$esxcli.storage.core.device.detached.list.Invoke()
}
That line should go after the Get-EsxCli line.
Could you also check if you see that LUN as a greyed-out entry in the Web Client after the detach?
That entry should disappear after a rescan of the HBA
I wrote follow super metric actually I need this output but
{Cluster Compute Resource: Memory|Total Capacity (KB), depth=1}-({Cluster Compute Resource: Memory|Consumed (KB), depth=1}+{Cluster Compute Resource: Memory|Reserved Capacity (KB), depth=1})
but show follow error :
Cannot convert aggregated result to number.
How can get output from this super metric with GB instead of KB ?
Check your versions here: VMware Knowledge Base
Thanks RobertMesropyan appreciate your help, I believe the transformation was the key element I missed. This will do nicely...glad to see this finally get in the product!
I think if you have many configuration and modification on the vsphere infrastructure, like creating vsphere distributed switches, host profiles, content library and so on, I think it's better to choose upgrade instead of new installation to avoid risks of any downtime, orphaning objects or lose of vCenter related components. Especially VMware put an option of migration from windows-based vCenter server to the appliance-mode in the VCSA installation console.
Until you can upgrade the vCenter in any form of deployment (even with the external PSC), it's better to choose it and avoid clean setup
One more thing RobertMesropyan . Any idea how I can filter the view to show only vms created last 24 hours? The filter options seem to be limited to epoch time?
Always you have a little more changing and customization operations in the CLI/Shell environment (especially via the using the esxcfg / esxcli) in front of vsphere client/ web client, but after all you should know exactly each one of TCP/IP stacks are used for which operation:
This is solved in Shrink an APFS virtual disk
Unfortunately, it failed. Suggestions for next steps?
I moved the line to below the Get-EsxCli, ran the script and received the same result.
I logged into the web client the device was there and grayed out and showed detached.
I scanned the storage from the Web Client and it still appears in Storage Devices.
Once I remove the device from the storage array it disappears in the gui but not the script.
Thanks for all your help with this.
It is working but when I run the script there are more and more entries which makes it harder to distinguish what is detached.
PS C:\EQR\Detach Datastore> C:\EQR\Detach Datastore\checkdetachAllHosts.ps1
true
eqresxi09.mydomain.com
DeviceUID State
--------- -----
naa.60000970000196800291533030303231 off
naa.60000970000196800291533030303236 off
naa.60000970000196800291533030303241 off
naa.60000970000196800291533030303242 off
naa.60000970000196800291533030303434 off
naa.60000970000196800291533030303435 off
naa.60000970000196800291533030303537 off
naa.60000970000196800291533030303832 off
naa.60000970000197901057533030303243 off
naa.60000970000197901057533030303336 off
naa.60000970000197901057533030303337 off
true
eqresxi15.mydomain.com
naa.60000970000196800291533030303231 off
naa.60000970000196800291533030303236 off
naa.60000970000196800291533030303241 off
naa.60000970000196800291533030303242 off
naa.60000970000196800291533030303434 off
naa.60000970000196800291533030303435 off
naa.60000970000196800291533030303537 off
naa.60000970000196800291533030303832 off
naa.60000970000197901057533030303243 off
naa.60000970000197901057533030303336 off
naa.60000970000197901057533030303337 off
true
eqresxi03.mydomain.com
naa.60000970000196800291533030303231 off
naa.60000970000196800291533030303236 off
naa.60000970000196800291533030303241 off
naa.60000970000196800291533030303242 off
naa.60000970000196800291533030303434 off
naa.60000970000196800291533030303435 off
naa.60000970000196800291533030303537 off
naa.60000970000196800291533030303832 off
naa.60000970000197901057533030303243 off
naa.60000970000197901057533030303336 off
naa.60000970000197901057533030303337 off
true
eqresxi04.mydomain.com
naa.60000970000196800291533030303231 off
naa.60000970000196800291533030303236 off
naa.60000970000196800291533030303241 off
naa.60000970000196800291533030303242 off
naa.60000970000196800291533030303434 off
naa.60000970000196800291533030303435 off
naa.60000970000196800291533030303537 off
naa.60000970000196800291533030303832 off
naa.60000970000197901057533030303243 off
naa.60000970000197901057533030303336 off
naa.60000970000197901057533030303337 off
albogadocmeg Unfortunately, filtering by different transformations is not supported yet. Existing filtering based on raw last values.
Hi, same error here on a new installation.
Any info will be appreciated.
VM'de cs:Go açmaya çalıştığım zaman "your graphics hardware does not support all features needed to run this game" hatasını alıyorum.
Sanırım ekran kartı driverları ile alakalı. Fakat VMlere driver yüklemesi yapılamıyorum. Bu hatayı nasıl çözebilirim ? Normal bilgisayarda karşısına bu hata çıkan insanlar ekran kartı güncelleyerek sorunu çözmüşler. Aldığım performans umrumda değil. Sadece VMlerde cs:goyu çalıştırmak istiyorum.
I would suggest the following steps from here:
Firstly, Run Disk First Aid on your host, just to make sure that there is no filesystem problem on your host which is creating or exacerbating the problem.
I would also try using vmware-vdiskmanager to check the integrity of the virtual hard disk. To do this, launch Terminal and run the following command:
/Applications/VMware\ Fusion.app/Contents/Library/vmware-vdiskmanager -R /Users/allenbirnbach/Documents/El\ Capitan-Birnbach.vmwarevm/Virtual\ Disk.vmdk
Hopefully it will report no problems – or at least report that it repaired any problems which were present.
If either of the above steps reported that any problems were corrected, try booting the virtual machine back into the Recovery Environment and run Disk Utility and Disk First Aid again.
If that still fails, we might be down to creating a new macOS virtual machine, attaching the existing virtual hard disk to the new VM, and using the Migration Assistant in the guest to transfer over any recoverable data from the old hard disk.
Thanks,
--
Darius
Hi again RickShu,
Please ignore my original question about getting a corruption on the running of VMware Fusion 11.5.3. I obviously entered the code suggested by you incorrectly.
However, I still have a problem.
I'm trying to recover, using a Windows 10 Pro repair disk, from an image backup written on a USB connected expansion hard drives. I have actually written the backup to two drives as was having trouble with firstly a Seagate Expansion Portable drive and now a Western Digital My Passport drive.
The VMware is running on a MacBook Pro (mid 2015) under Mojave 10.14.6.
Using a Windows 10 Pro repair disk I get all the way through the recovery process to the point where Windows looks for the image copy I wish to use for the recovery.
I have tried using both drives on different trials and they are recognised by Fusion in Settings. I have requested that the drive I am using be connected to Windows.
I have modified the VM vmx file with the line of code you suggested. However Windows cannot find the drives. If I connect either drive to Windows under normal boot conditions, they do appear under Disk Management and Explorer so I believe the expansion disks are OK.
Can you offer any further suggestions?
Thanks again
Phil
There are lots of possible reasons for a delay during power-on. Can you post (as an attachment in this thread) the vmware.log file from inside the VM's directory? Or review the log file yourself and look at the timestamps at the start of each line. Look for any place where the time jumps ahead by more than a few seconds, and look at the lines immediately before and after that jump, and that might give you some ideas about what is causing the delay.
Thanks,
--
Darius
Hi basic2004!
It's cool to hear that the Sound Blaster 16 MIDI support is being used. I am curious about what you are using it for.
The chances of getting user-interface support for selecting a host MIDI device is almost zero, sorry. I'm just working on these Sound Blaster 16 enhancements in my spare time – i.e. weekends! – and I am definitely not a user-interface engineer.
There's a small chance I could add a .vmx file option to control the default host MIDI output device, but even that is going to be very far down my priority list.
It might be more productive to follow up the host issue with the MIDI mapper defaults... It might be as "simple" as incorrect permissions on a registry key used to store the MIDI mapper configuration. If it seems to be a defect in Windows itself (perhaps try running Windows in a VM and see if you can reproduce it!) then perhaps report it to Microsoft.
Thanks,
--
Darius
RickShu,
P.S. The Seagate data is written under NTFS and the WD data is written under ExFat. I tried both to see if this was causing a problem but as I expected it made no difference.
regards
Phil