So the folder you mentioned seems not to exist. I did find the modules in:

~/.local/share/powershell/Modules

This is what I'm running into now:

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: Import-Module : The specified module 'VMware.VimAutomation.sdk' was not loaded because no valid module file was found in any module directory.

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: At line:2 char:1

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: + Import-Module -Name 'VMware.VimAutomation.sdk'

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: + CategoryInfo          : ResourceUnavailable: (VMware.VimAutomation.sdk:String) [Import-Module], FileNotFoundException

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]:

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: Import-Module : The required module 'VMware.VimAutomation.Sdk' is not loaded. Load the module or remove the module from 'RequiredModules' in the file '/usr/local/share/powershell/Modules/VMware.PowerCLI/11.4.0.14413515/VMware.Po

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: At line:3 char:1

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: + Import-Module -Name 'VMware.PowerCLI'

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: + CategoryInfo          : ResourceUnavailable: (/usr/local/share/po\u2026Mware.PowerCLI.psd1:String) [Import-Module], MissingMemberException

Oct 20 23:23:26 cec-esxi-mgmt pwsh[6701]: + FullyQualifiedErrorId : Modules_InvalidManifest,Microsoft.PowerShell.Commands.ImportModuleCommand

I noticed that the folder location that it is using for the  VMware.PowerCLI is a root location and not a user location. The VMware.VimAutomation.sdk is installed but its in a user location and not a root location. I copied them over from the user location to root location via basic cp command:

ls /usr/local/share/powershell/Modules/

VMware.DeployAutomation        VMware.VimAutomation.Core        VMware.VimAutomation.Srm

VMware.ImageBuilder            VMware.VimAutomation.Hcx          VMware.VimAutomation.Storage

VMware.PowerCLI                VMware.VimAutomation.HorizonView  VMware.VimAutomation.StorageUtility

VMware.Vim                    VMware.VimAutomation.License      VMware.VimAutomation.Vds

VMware.VimAutomation.Cis.Core  VMware.VimAutomation.Nsxt        VMware.VimAutomation.Vmc

VMware.VimAutomation.Cloud    VMware.VimAutomation.Sdk          VMware.VimAutomation.vROps

VMware.VimAutomation.Common    VMware.VimAutomation.Security    VMware.VumAutomation

(before this only VMware.PowerCLI and a few others were there.)

I ran it again and came up with this:

 

Oct 20 23:47:54 esxi-mgmt systemd[1]: Started "ESXI  Snapshot management".

Oct 20 23:47:54 esxi-mgmt powershell[6797]: (6.2.3:1:80) [Perftrack_ConsoleStartupStart:PowershellCons

Oct 20 23:47:54 esxi-mgmt powershell[6797]: (6.2.3:7:80) [NamedPipeIPC_ServerListenerStarted:NamedPipe

Oct 20 23:47:54 esxi-mgmt powershell[6797]: (6.2.3:1:80) [Perftrack_ConsoleStartupStop:PowershellConso

Oct 20 23:47:55 esxi-mgmt pwsh[6797]: The type initializer for 'VMware.VimAutomation.ViCore.Util10.Set

Oct 20 23:47:55 esxi-mgmt pwsh[6797]: At /usr/local/share/powershell/Modules/VMware.VimAutomation.Sdk/

Oct 20 23:47:55 esxi-mgmt pwsh[6797]: + if ([VMware.VimAutomation.ViCore.Util10.SettingsManager]::Part

Oct 20 23:47:55 esxi-mgmt pwsh[6797]: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:47:55 esxi-mgmt pwsh[6797]: + CategoryInfo          : OperationStopped: (:) [], TypeInitiali

Oct 20 23:47:55 esxi-mgmt pwsh[6797]: + FullyQualifiedErrorId : System.TypeInitializationException

Oct 20 23:47:55 esxi-mgmt pwsh[6797]: 

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: Import-Module : The type initializer for 'VMware.VimAutomation.S

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: At line:3 char:1

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + Import-Module -Name 'VMware.PowerCLI'

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + CategoryInfo          : OperationStopped: (:) [Import-Module],

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + FullyQualifiedErrorId : System.TypeInitializationException,Mic

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: 

Oct 20 23:47:56 esxi-mgmt powershell[6797]: (6.2.3:9:80) [Provider_Health:ExecutePipeline.Exception.Wa

Fully Qualified Error ID = InitializeDefaultDrivesExceptio

 

Provider name = VimInventory

                                               

 

Context:

        Severity = Warning

        Host Name = ConsoleHost

        Host Version = 6.2.3

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pws

        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

        Pipeline ID = 43

        Command Name =

                                                        Command Type =

        Script Name =

        Command Path =

        Sequence Number = 215

        User = esxi-mgmt\root

        Connected User =

        Shell ID = Microsoft.PowerShell

 

 

User Data:

Oct 20 23:47:56 esxi-mgmt powershell[6797]: (6.2.3:9:80) [Provider_Health:ExecutePipeline.Exception.Wa

Fully Qualified Error ID = InitializeDefaultDrivesExceptio

 

Provider name = VimInventory

                                               

 

Context:

        Severity = Warning

                                                        Host Name = ConsoleHost

        Host Version = 6.2.3

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pws

        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

        Pipeline ID = 43

        Command Name =

                                                        Command Type =

        Script Name =

        Command Path =

        Sequence Number = 216

        User = esxi-mgmt\root

        Connected User =

        Shell ID = Microsoft.PowerShell

 

 

User Data:

Oct 20 23:47:56 esxi-mgmt powershell[6797]: (6.2.3:9:80) [Provider_Health:ExecutePipeline.Exception.Wa

Fully Qualified Error ID = InitializeDefaultDrivesExceptio

 

Provider name = VimDatastore

 

 

Context:

                                                        Severity = Warning

        Host Name = ConsoleHost

        Host Version = 6.2.3

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pws

                                                        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

        Pipeline ID = 43

                                                        Command Name =

        Command Type =

        Script Name =

        Command Path =

        Sequence Number = 217

        User = esxi-mgmt\root

        Connected User =

                                                        Shell ID = Microsoft.PowerShell

 

 

User Data:

Oct 20 23:47:56 esxi-mgmt powershell[6797]: (6.2.3:9:80) [Provider_Health:ExecutePipeline.Exception.Wa

Fully Qualified Error ID = InitializeDefaultDrivesExceptio

 

                                                Provider name = VimDatastore

 

 

Context:

        Severity = Warning

        Host Name = ConsoleHost

        Host Version = 6.2.3

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pws

                                                        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

        Pipeline ID = 43

                                                        Command Name =

        Command Type =

        Script Name =

        Command Path =

        Sequence Number = 218

        User = esxi-mgmt\root

        Connected User =

                                                        Shell ID = Microsoft.PowerShell

 

 

User Data:

Oct 20 23:47:56 esxi-mgmt powershell[6797]: (6.2.3:9:80) [Command_Health:ExecutePipeline.Exception.War

Fully Qualified Error ID = System.TypeInitializationExcept

 

 

Context:

        Severity = Warning

                                                        Host Name = ConsoleHost

        Host Version = 6.2.3

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pws

        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

        Pipeline ID = 1

        Command Name = Connect-VIServer

        Command Type = Cmdlet

        Script Name =

        Command Path =

        Sequence Number = 222

        User = esxi-mgmt\root

        Connected User =

        Shell ID = Microsoft.PowerShell

                                               

 

User Data:

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: Connect-VIServer : The type initializer for 'VMware.VimAutomatio

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: At line:4 char:1

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + Connect-VIServer -Server 9.3.254.14 -User root -Password pinkz

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + CategoryInfo          : NotSpecified: (:) [Connect-VIServer],

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + FullyQualifiedErrorId : System.TypeInitializationException,VMw

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: 

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: New-Snapshot : Cannot process argument transformation on paramet

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: At line:6 char:18

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + New-Snapshot -VM pkgs-mirror -Name "-snapshot-$d

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: +                  ~~~~~~~~~~~~~~~

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + CategoryInfo          : InvalidData: (:) [New-Snapshot], Param

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + FullyQualifiedErrorId : ParameterArgumentTransformationError,V

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: 

Oct 20 23:47:56 esxi-mgmt powershell[6797]: (6.2.3:9:80) [Command_Health:ExecutePipeline.Exception.War

Fully Qualified Error ID = System.TypeInitializationExcept

                                               

 

Context:

        Severity = Warning

        Host Name = ConsoleHost

        Host Version = 6.2.3

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pws

        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

                                                        Pipeline ID = 1

        Command Name = Get-VM

        Command Type = Cmdlet

        Script Name =

        Command Path =

        Sequence Number = 263

        User = esxi-mgmt\root

                                                        Connected User =

        Shell ID = Microsoft.PowerShell

 

 

User Data:

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: Get-VM : The type initializer for 'VMware.VimAutomation.Sdk.Inte

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: At line:7 char:1

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + Get-VM pkgs-mirror | Get-Snapshot |

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + ~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + CategoryInfo          : NotSpecified: (:) [Get-VM], TypeInitia

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + FullyQualifiedErrorId : System.TypeInitializationException,VMw

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: 

lines 639-661/661 (END)

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pws

        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

        Pipeline ID = 1

        Command Name = Get-VM

        Command Type = Cmdlet

        Script Name =

        Command Path =

        Sequence Number = 263

        User = esxi-mgmt\root

        Connected User =

        Shell ID = Microsoft.PowerShell

 

 

User Data:

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: Get-VM : The type initializer for 'VMware.VimAutomation.Sdk.Inte

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: At line:7 char:1

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + Get-VM pkgs-mirror | Get-Snapshot |

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + ~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + CategoryInfo          : NotSpecified: (:) [Get-VM], TypeInitia

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + FullyQualifiedErrorId : System.TypeInitializationException,VMw

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: 

~

lines 639-661/661 (END)

 

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pwsh.dll /home/user/scripts/mirror/-snapshots

                                                        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

        Pipeline ID = 1

                                                        Command Name = Get-VM

        Command Type = Cmdlet

        Script Name =

        Command Path =

        Sequence Number = 263

        User = esxi-mgmt\root

        Connected User =

                                                        Shell ID = Microsoft.PowerShell

 

 

User Data:

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: Get-VM : The type initializer for 'VMware.VimAutomation.Sdk.Interop.V1.CoreServiceFactory' threw an exception.

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: At line:7 char:1

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + Get-VM pkgs-mirror | Get-Snapshot |

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + ~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + CategoryInfo          : NotSpecified: (:) [Get-VM], TypeInitializationException

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + FullyQualifiedErrorId : System.TypeInitializationException,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetVM

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: 

~

lines 639-661/661 (END)

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pwsh.dll /home/user/scripts/mirror/-snapshots

        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

        Pipeline ID = 1

        Command Name = Get-VM

        Command Type = Cmdlet

        Script Name =

                                                        Command Path =

        Sequence Number = 263

        User = esxi-mgmt\root

                                                        Connected User =

        Shell ID = Microsoft.PowerShell

 

 

                                                User Data:

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: Get-VM : The type initializer for 'VMware.VimAutomation.Sdk.Interop.V1.CoreServiceFactory' threw an exception.

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: At line:7 char:1

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + Get-VM pkgs-mirror | Get-Snapshot |

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + ~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + CategoryInfo          : NotSpecified: (:) [Get-VM], TypeInitializationException

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + FullyQualifiedErrorId : System.TypeInitializationException,VMware.VimAutomation.ViCore.Cmdlets.Commands.GetVM

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: 

~

lines 639-661/661 (END)

        Host ID = 30ac0891-3fbd-48b9-91e6-547a3fae12ff

        Host Application = /opt/microsoft/powershell/6/pws

        Engine Version = 6.2.3

        Runspace ID = 70caa35c-dcb5-4277-9705-93215de3db06

        Pipeline ID = 1

        Command Name = Get-VM

        Command Type = Cmdlet

        Script Name =

        Command Path =

        Sequence Number = 263

                                                        User = esxi-mgmt\root

        Connected User =

        Shell ID = Microsoft.PowerShell

 

 

User Data:

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: Get-VM : The type initializer for 'VMware.VimAutomation.Sdk.Inte

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: At line:7 char:1

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + Get-VM pkgs-mirror | Get-Snapshot |

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + ~~~~~~~~~~~~~~~~~~~~~~

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + CategoryInfo          : NotSpecified: (:) [Get-VM], TypeInitia

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: + FullyQualifiedErrorId : System.TypeInitializationException,VMw

Oct 20 23:47:56 esxi-mgmt pwsh[6797]: 

I'm kind of confused as to whats happening but it seems like when its run under the script via systemctl or cron it is attempting to execute via root and there seems to be a huge mismatch of module locations between a local user and the root user.

I think I finally fixed it, after realizing the path discrepancies between the local user and root when executing powershell, I decided to use a non sudo crontab -e - so basically just a crontab -e instead of sudo crontab -e as to keep pathing all under the local user and it executed and created the snapshot as intended.

Thanks for your help all!

I met this error and failed to open my ubuntu in VM.

I adopted VM player Version 15

My logs are attached.

I found some vmdk filesize are zero? Does it mean my OS crashed?

Could somebody point out the root cause?

HI everyone,

i've tried to exclude subdomains in the Horizon View Admin and Client as mentioned in the following article:

https://www.vmadmin.co.uk/resources/53-view/386-exclude-remove-domain-in-vmware-view-administrator-client-and-html-acces…

My problem is, that the subdomains won't disappear neither in the Horizon View Administrator nor the Horizon VIew Client.

Any idea?

Thanks for helping me out with this.

Thanks for the note regarding the loudness.
3 Supermicro Nodes sounds good ;-)

We are  now on version 6.5 u3C

I'm currently setting up an environment with FSLogix Office Containers and DEM (Horizon 7.9).

Played a short time with FSLogic Profile containers also, but they grew too big. I also don't like the idea of loosing my profiles when the VHDX gets corrupted one way or another (Office Containers don't contain critical data, they can be recovered easily)

It works very nice for the time being. Only issue I'm trying to figure out at this time is the activation of Office 365 ProPlus. It worked fine when I had the Profile Containers, but since I ditched them and used DEM, I always need to reenter my password for the activation (account is remembered, but password not)

Have to say I'm very excited about the outlook cache and search index that is working flawless on our non-persistent desktop pools with Office Containers (Server 2019 & Office 365)

Plan is to go live in the next 2 months...

Regards,

Michiel

Buongiorno

Ho questo problema: ho aggiornato vCenter alla versione Update 3, ma quando effettuo il login mi appare la pagina bianca con il simbolo del caricamento che ruota all'infinito e non si carica la pagina di vCenter (vedi immagine)

Qualcuno ha qualche suggerimento, considerando che accedo a vCenter sia con IP_address:5480 che con SSH

Grazie e buon lavoro

Hi everyone,

Need help to achieve following scenario

I have 3 hosts with vSAN Configured with RAID0 PFTT0, having enough space so that RAID1 can be applied on those VMs which need performance & Availability.

Is it possible to make 2 vSAN disc groups within vSAN

Apply RAID1 policy on all VMs with PFTT=1

& after this configuration perform storage vMotion to a DAS/ or local HDDs for all those VMs which only require capacity & can manage availability by themself.

Then evacuate some discs from vSAN & make RAID0/JBOD from physical controller (model: HPE p816i-a sr)

Then perform storage vMotion back to local RAID0 volume again.

Final Shape of environment:

Now, high performance VMs are running on vSAN with 2 DGs configured, discs pass-through via same controller. SPBM = RAID1 & PFTT=1

          Other VMs running on local RAID0 datastore (RAID0 configured via same RAID Controller)

Is it doable?

Regards,

Moaz Anjum

Hi,

I got log from VDM client log.

Ciao a tutti

ho un server hp proliant dl380 g5 , con un controller smart array P400

Vorrei poter gestire volumi logici e stato dischi da un esxi 5.5

è possibile ?

grazie

Hi all,

Thank you, SR has been created, will keep you updated here.

I don't think it's possible to remove Child-Domains if the parent is still added. I have removed all of my Tree-Domains from the list of domains that have been shown in the VMware Horizon View login pages, by running the VDMADMIN command, but if any domain is still included, all of its Sub-Domains will be listed.

Did I understand correctly, that to remove NSX components manually is bad idea and better is to restore installed version and then upgrade it to current?

Parece que voce não é o unico, achei algumas soluções:

https://www.tenforums.com/virtualization/141820-vmware-workstation-pro-cant-run-windows-message.html

(SOLVED) VMware Workstation Pro Can't Run On Windows - version 1903 update - [Problem Fixed] - YouTube

(Solved) vmware workstation not working on windows 10 Latest 19 Oct 2019 - YouTube

Veja tambem:

Workstation pro not working on windows 1903

If you restart the management agent or reboot the ESXi, your problem will be corrected.But you need to consolidate snapshots immediately.

Don't be afraid, it won't be a problem.