PowerCli/Start-transcript bug

[MichaelRyom]

Hi

I have an old script(from 2020, running monthly as a windows schedule task) which seems to be failing recently (less than 6 month ago). Checking the log showed an (almost) empty log file.

In this script I'm using the powershell command start-transcript, to catch output and errors. A lazy mans logging.

But it seems that with one of the recent PowerCli version, PowerCli breaks the Start-transcript command for some reason.

Running the below code as a schedule task (using an AD user, which is local admin)

 

Start-Transcript -Path "C:\temp\test.log" -Append -Force
import-module VMware.PowerCli -force
Write-host "Hallo World!"
Stop-Transcript

 

Output

 

**********************
Windows PowerShell transcript start
Start time: 20220518103905
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx (Microsoft Windows NT 10.0.17763.0)
Host Application: powershell.exe -file C:\scripts\repository\Scheduled Scripts\Capcity Report\test.ps1
Process ID: 27140
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
**********************
Windows PowerShell transcript end
End time: 20220518103913
**********************

 

Note no "Hallo World!"

If I run this code instead the same way as above

 

import-module VMware.PowerCli -force
Start-Transcript -Path "C:\temp\test.log" -Append -Force
Write-host "Hallo World!"
Stop-Transcript

 

Output

 

**********************
Windows PowerShell transcript start
Start time: 20220518104935
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx(Microsoft Windows NT 10.0.17763.0)
Host Application: powershell.exe -file C:\scripts\repository\Scheduled Scripts\Capcity Report\test.ps1
Process ID: 20956
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
Hallo World!
**********************
Windows PowerShell transcript end
End time: 20220518104935
**********************

 

 Note "Hallo World!" is now in the output.

So it seems to be a bug in PowerCli, when modules are being loaded. I first noticed this issue when just running a command ( $cred = Get-VICredentialStoreItem -File $TokenFilePath ) and then did the testing with import-module, which seems to produce the same result.

Running this first script manually (in a powershell console) produces this result in the log file

 

**********************
Windows PowerShell transcript start
Start time: 20220518105520
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx(Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Process ID: 21748
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
PS C:\Users\xxx> import-module VMware.PowerCli -force
**********************
Windows PowerShell transcript end
End time: 20220518105528
**********************

 

and here is the output in the console

 

PS C:\Users\xxx> Start-Transcript -Path "C:\temp\test.log" -Append -Force
Transcript started, output file is C:\temp\test.log
PS C:\Users\xxx> import-module VMware.PowerCli -force
          Welcome to VMware PowerCLI!

Log in to a vCenter Server or ESX host:              Connect-VIServer
To find out what commands are available, type:       Get-VICommand
To show searchable help for all PowerCLI commands:   Get-PowerCLIHelp
Once you've connected, display all virtual machines: Get-VM
If you need more help, visit the PowerCLI community: Get-PowerCLICommunity

       Copyright (C) VMware, Inc. All rights reserved.


PS C:\Users\xxx> Write-host "Hallo World!"
Hallo World!
PS C:\Users\xxx> Stop-Transcript
Stop-Transcript : An error occurred stopping transcription: The host is not currently
transcribing.
At line:1 char:1
+ Stop-Transcript
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Stop-Transcript], PSInvalidOperationExc
   eption
    + FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.StopTranscriptC
   ommand

PS C:\Users\xxx>

 

Which seems to agree with me on the fact that something inside PowerCli module is stopping/failing the transcript commandlet.

Can anyone reproduce this?

PowerCLI Version
----------------
VMware.PowerCLI 12.6.0 build 19610541
---------------
Component Versions
---------------
VMware Common PowerCLI Component 12.6 build 19600917
VMware Cis Core PowerCLI Component PowerCLI Component 12.6 build 19601368
VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 12.6 build 19601570

[LucD]

Just a quick question, why do you explicitly import modules?
If the modules are in one of the directories listed in $env: PSModulePath there is no need for that.

Also, importing VMware.PowerCLI, implicit or explicit, generates a number of verbose message (where they inform you about the CEIP).
This might cause the transcript issues.
Perhaps try piping the Import-Module to Out-Null

[MichaelRyom]

Hi Luc

I don't explicitly import the module, only here to show case the issue. The original commandlet I used where is failed is Get-VICredentialStoreItem, but also Connect-OMServer does it and others (and here I do not import the module - The orginal script is more than 2000 lines of code so not something I can or will share here ). That is why I started testing with import-module.

The VMware.PowerCli module(s) are in path $env: PSModulePath.

CEIP was been disabled for all users, so that should not be an issue and havn't been before.

Testing with "import-module VMware.PowerCli -force | Out-Null" does not work, same issue.

 

My laptop is running PowerCli 12.0.5 19195797 and the problem does not seem to be in this version.

[LucD]

In which PowerCLI version do you see the problem then?

[MichaelRyom]

PowerCLI Version
----------------
VMware.PowerCLI 12.6.0 build 19610541
---------------
Component Versions
---------------
VMware Common PowerCLI Component 12.6 build 19600917
VMware Cis Core PowerCLI Component PowerCLI Component 12.6 build 19601368
VMware VimAutomation VICore Commands PowerCLI Component PowerCLI Component 12.6 build 19601570

[LucD]

As additional info, the Start-Transcript cmdlet is notorious for mssing output.
See for example #Issue10994 on the PowerShell repository.

I'm not sure if what you are seeing is caused by PowerCLI, I sooner suspect the type of output some PowerCLI modules produce when loaded might confuse the Start-TRanscript

[CLRYN]

I have the exact same error on multible Windows computers. I think it started after a Windows patch some months ago. 

[MichaelRyom]

Okay, interesting. Will update my laptop which is window 11 and powercli 12.5 to 12.6 to see what is does then.

[MichaelRyom]

I have upgraded an tested on 12.6 on Windows 11 and it works here

Do you have any idea to which windows update that might be at fault?

[LucD]

Looking back at the beginning of this thread, I noticed that where it fails PowerShell is called with 

C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

Could the one that works perhaps have picked up

%SystemRoot%\syswow64\WindowsPowerShell\v1.0\powershell.exe

 Would that make a difference?

[MichaelRyom]

Nice catch Luc

But still no luck

**********************
Windows PowerShell transcript start
Start time: 20220519072841
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx(Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\syswow64\WindowsPowerShell\v1.0\powershell.exe
Process ID: 2648
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
PS C:\Windows\syswow64\WindowsPowerShell\v1.0> import-module VMware.PowerCli -force | Out-Null
**********************
Windows PowerShell transcript end
End time: 20220519072849
**********************

[MichaelRyom]

Just to make sure you understand why I say it's a PowerCli issue. Here you can see me loading a non VMware module and you can see it working as expected.

**********************
Windows PowerShell transcript start
Start time: 20220519084317
Username: xxx\xxx
RunAs User: xxx\xxx
Configuration Name: 
Machine: xxx (Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Process ID: 5696
PSVersion: 5.1.17763.2803
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2803
BuildVersion: 10.0.17763.2803
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\temp\test.log
PS C:\Users\xxx> import-module ActiveDirectory
PS C:\Users\xxx> Write-host "Hallo World!"
Hallo World!
PS C:\Users\xxx> Stop-Transcript
**********************
Windows PowerShell transcript end
End time: 20220519084321
**********************

 

[LucD]

I understand, but I'm still somewhat convinced it is the unhealthy habit of the PowerCLI modules to show those messages when the modules are loaded.
Most other modules don't do that.
Combine that with a new "flaw" in Start-Transcript, and I suspect it might be a combination of the two.

Btw, I have asked ages ago to remove those messages.
See Eliminate, or provide option with | VMware PowerCLI (aha.io)

[MichaelRyom]

Thanks Luc.

We have another way of logging today internally, so I will just migrate the script to that way of logging instead of using transcript

 

Thanks for everybody's help. Think I will leave it at that

[Tocano]

Just to confirm, this still appears to be an issue in 12.7

We just upgraded from 12.3 and have begun to encounter this very issue.

Right after the line:

VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\12.7.0.20067789\net45\VMware.VimAutomation.Common.ps1'.
**********************
Windows PowerShell transcript end
End time: 20220719084406
**********************

We are now explicitly loading the VMware.VimAutomation.Common module in the profile, before we start our script transcript, in order to avoid this issue.

[Atanas Dimitrov Atanasov]

I was not able to reproduce this.

Can you try to edit that file and see if this changes anything - '...\Modules\VMware.VimAutomation.Common\12.7.0.20067789\net45\VMware.VimAutomation.Common.ps1'?

(use the location from where you load the module from).

For example make it empty first and see if that changes anything - if it does, try to remove sections of it until you find what is making the difference.

[Tocano]

Thank you for the follow up. 

Steps to reproduce:

1. Launch powershell 5.1 console with empty profile (no autoloading modules)
2. > $VerbosePreference = "Continue"
3. > Start-Transcript -Path "C:\temp\$(Get-Date -format "yyyy-MM-dd")_Transcript.log
4. > Get-Process
5. > Import-Module VMware.PowerCLI

If you open the transcript file, you'll notice that it begins logging lines, but at some point during the middle of that import process, it stops logging and closes the transcript file properly with a Windows PowerShell transcript end and an End time.


As for your troubleshooting suggestion, that was a good idea. And initially, when I opened VMware.VimAutomation.Common.ps1 and commented out the content, and relaunched a new console, the transcript would progress, but still end - just this time at like VMware.VimAutomation.Cis.Core.ps1.  When I edited that file and commented out the content, it would progress to VMware.VimAutomation.Core.ps1. And commenting that one resulted in the transcript ending at VMware.VimAutomation.ViCore.Cmdlets.dll - and since I don't know how to edit a dll, that's where I stalled.

This is starting to feel like a line involving ending a running debugging transcript was accidentally left in a function of the compiled code and is getting called at the conclusion of each (or at least many) modules.

Thanks again for your suggestions. I'm still open to any troubleshooting recommendations.

Thank you.

 

Edit: Easier steps:

1. Launch powershell 5.1 console with empty profile (no autoloading modules)
2. > $VerbosePreference = "Continue"
3. > Start-Transcript -Path "C:\temp\$(Get-Date -format "yyyy-MM-dd")_Transcript.log
4. > Measure-Command {Get-VM} 

This will end in an error, but will import less modules and you'll still be able to see the log be stopped and closed prematurely. 

[Atanas Dimitrov Atanasov]

The output for me in the .log file is exactly the same as what I see in the console.

What is the value of $PSVersionTable where you reproduced this? I tested this on Windows 11 (10.0.22000.653) and Window 10 (10.0.19041.1682), what version is the OS where you run this?

[Tocano]

That's strange. 

PS > (Get-WmiObject -class Win32_OperatingSystem).Caption
Microsoft Windows Server 2019 Datacenter

PS > [System.Environment]::OSVersion.Version

Major Minor Build Revision
----- ----- ----- --------
10 0 17763 0

PS > $PSVersionTable

Name Value
---- -----
PSVersion 5.1.17763.2931
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.2931
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

PS > Get-Module -ListAvailable VMware.PowerCLI |ft -AutoSize
VERBOSE: Populating RepositorySourceLocation property for module VMware.PowerCLI.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCLI\12.7.0.20091289\VMware.PowerCLI.ps1'.


Directory: C:\Program Files\WindowsPowerShell\Modules


ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Manifest 12.7.0.20091289 VMware.PowerCLI

 

All of our servers experience this behavior. I'll have to try some wider testing. 

Thank you.

[Atanas Dimitrov Atanasov]

Can you try with PowerShell Core?

[Tocano]

That does appear to have a difference.

PS5 stops and closes the transcript.

PS7 does not and works as expected. 

It's unfortunate that PS7 isn't a viable option for us in this environment.

 

[tonypags]

I have this same issue. I was trying to find the change I made before this started happening to several of my VMWare scripts running from task scheduler on windows 2012. It's most definitely a VMWare module problem, but damned as I am, cannot trace the source (the source code is in DLLs, above my paygrade). VMWare module has lots of quirks, it's slow and bloated, etc. 

I finally figured that it's not any command that's doing it, but rather the import-module activity. Much appreciation to folks on this thread for nudging me in the right direction. 

NB: I have a unique config for my environments. My profile does create a generic transcript when a session starts. But also, all of my production scripts have a transcript block at the top to restart and rename the transcript file to match the script name.

So for my case, I have an opportunity to restart the transcript AFTER the script is executed. This is key for this workaround: I added a #Requires statement to the top of my script to load the module immediately when the script is called. Then my script logic restarts the transcript for me.

#Requires -Modules VMware.VimAutomation.Core, OtherModuelsToo, Etc

[MichaelRyom]

Hi again

So I'm back, someone broke part of out environment, so I'm in need of Start-Transcript to find where things break

 

Some more facts - This seems to be a Windows Server issue only.

The issue is confirmed on 4 different Windows servers at 3 different companies - On Windows 2016 and 2019. Client OS'es doesn't seem to be affected Windows 10 and 11 tested no issues.

This is what I run to reproduce this issue:

 

 

$DebugPreference = "Continue"
$VerbosePreference = "Continue"
Start-Transcript
[Environment]::OSVersion
$PSVersiontable
Import-Module VMware.PowerCli -Verbose -Debug
Stop-Transcript

 

 

 

Output from transcript file:

Server1:

 

 

**********************
Windows PowerShell transcript start
Start time: 20230302110207
Username: ARK\Administrator
RunAs User: ARK\Administrator
Configuration Name: 
Machine: ARK (Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Process ID: 5352
PSVersion: 5.1.17763.3770
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.3770
BuildVersion: 10.0.17763.3770
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\Users\Administrator\Documents\PowerShell_transcript.ARK.Jjn8QiIV.20230302110207.txt
PS C:\Users\Administrator> [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.17763.0 Microsoft Windows NT 10.0.17763.0


PS C:\Users\Administrator> $PSVersiontable

Name                           Value
----                           -----
PSVersion                      5.1.17763.3770
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.3770
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PS C:\Users\Administrator> Import-Module VMware.PowerCli -Verbose -Debug
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCli.psd1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
WARNING: Please consider joining the VMware Customer Experience Improvement Program, so you can help us make PowerCLI a better product. You can join using the following command:

Set-PowerCLIConfiguration -Scope User -ParticipateInCEIP $true

VMware's Customer Experience Improvement Program ("CEIP") provides VMware with information that enables VMware to improve its products and services, to fix problems, and to advise you on how best to deploy and use our products.  As part of the CEIP, VMware collects technical information about your organization’s use of VMware products and services on a regular basis in association with your organization’s VMware license key(s).  This information does not personally identify any individual.

For more details: type "help about_ceip" to see the related help article.

To disable this warning and set your preference use the following command and restart PowerShell: 
Set-PowerCLIConfiguration -Scope User -ParticipateInCEIP $true or $false.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Exporting variable 'CustomInitScriptName'.
VERBOSE: Exporting variable 'currentDir'.
VERBOSE: Exporting variable 'CustomInitScript'.
VERBOSE: Exporting variable 'productShortName'.
VERBOSE: Exporting variable 'existsCustomInitScript'.
VERBOSE: Exporting variable 'message'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Importing variable 'currentDir'.
VERBOSE: Importing variable 'CustomInitScript'.
VERBOSE: Importing variable 'CustomInitScriptName'.
VERBOSE: Importing variable 'existsCustomInitScript'.
VERBOSE: Importing variable 'message'.
VERBOSE: Importing variable 'productShortName'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
**********************
Windows PowerShell transcript end
End time: 20230302110216
**********************

 

 

 

 

Server2:

 

 

**********************
Windows PowerShell transcript start
Start time: 20230302105923
Username: XXX\YYY
RunAs User: XXX\YYY
Configuration Name: 
Machine: ZZZ (Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Process ID: 17412
PSVersion: 5.1.17763.2931
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.2931
BuildVersion: 10.0.17763.2931
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\Users\YYY\Documents\PowerShell_transcript.ZZZ.9SGkAOUl.20230302105923.txt
PS C:\Users\YYY> [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.17763.0 Microsoft Windows NT 10.0.17763.0


PS C:\Users\YYY> $PSVersiontable

Name                           Value
----                           -----
PSVersion                      5.1.17763.2931
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.2931
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PS C:\Users\YYY> Import-Module VMware.PowerCli -Verbose -Debug
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCli.psd1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Exporting variable 'CustomInitScriptName'.
VERBOSE: Exporting variable 'currentDir'.
VERBOSE: Exporting variable 'CustomInitScript'.
VERBOSE: Exporting variable 'productShortName'.
VERBOSE: Exporting variable 'existsCustomInitScript'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Importing variable 'currentDir'.
VERBOSE: Importing variable 'CustomInitScript'.
VERBOSE: Importing variable 'CustomInitScriptName'.
VERBOSE: Importing variable 'existsCustomInitScript'.
VERBOSE: Importing variable 'productShortName'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
**********************
Windows PowerShell transcript end
End time: 20230302110007
**********************

 

 

 

Server3:

 

 

**********************
Windows PowerShell transcript start
Start time: 20230302111138
Username: XXX\YYY
RunAs User: XXX\YYY
Configuration Name: 
Machine: ZZZ (Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Process ID: 58108
PSVersion: 5.1.17763.3770
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.3770
BuildVersion: 10.0.17763.3770
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\Users\YYY\Documents\PowerShell_transcript.ZZZ.efnmiwVI.20230302111138.txt
PS C:\Users\YYY> [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.17763.0 Microsoft Windows NT 10.0.17763.0


PS C:\Users\YYY> $PSVersiontable

Name                           Value
----                           -----
PSVersion                      5.1.17763.3770
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.3770
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PS C:\Users\YYY> Import-Module VMware.PowerCli -Verbose -Debug
VERBOSE: Loading module from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCli.psd1'.
VERBOSE: Loading module from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading module from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
VERBOSE: Loading module from path 'C:\Users\YYY\Documents\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Exporting variable 'CustomInitScriptName'.
VERBOSE: Exporting variable 'currentDir'.
VERBOSE: Exporting variable 'CustomInitScript'.
VERBOSE: Exporting variable 'productShortName'.
VERBOSE: Exporting variable 'existsCustomInitScript'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Importing variable 'currentDir'.
VERBOSE: Importing variable 'CustomInitScript'.
VERBOSE: Importing variable 'CustomInitScriptName'.
VERBOSE: Importing variable 'existsCustomInitScript'.
VERBOSE: Importing variable 'productShortName'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
**********************
Windows PowerShell transcript end
End time: 20230302111154
**********************

 

 

 

Server3, but with set to: $VerbosePreference = "SilentlyContinue" - The output is a bit different and the console output can be copy/pasted ( were as with verbose, the output to console is way to long )

 

 

**********************
Windows PowerShell transcript start
Start time: 20230302112546
Username: XXX\ZZZ
RunAs User: XXX\ZZZ
Configuration Name: 
Machine: YYY (Microsoft Windows NT 10.0.17763.0)
Host Application: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Process ID: 75112
PSVersion: 5.1.17763.3770
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.3770
BuildVersion: 10.0.17763.3770
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
**********************
Transcript started, output file is C:\Users\ZZZ\Documents\PowerShell_transcript.YYY.wiyqAN+1.20230302112546.txt
PS C:\Users\ZZZ> [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.17763.0 Microsoft Windows NT 10.0.17763.0


PS C:\Users\ZZZ> $PSVersiontable

Name                           Value
----                           -----
PSVersion                      5.1.17763.3770
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.3770
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PS C:\Users\ZZZ> Import-Module VMware.PowerCli -Verbose -Debug
VERBOSE: Loading module from path 'C:\Users\ZZZ\Documents\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCli.psd1'.
**********************
Windows PowerShell transcript end
End time: 20230302112602
**********************

 

 

And the console output to match the above transcript:

 

 

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\ZZZ> $DebugPreference = "Continue"
PS C:\Users\ZZZ> $VerbosePreference = "SilentlyContinue"
PS C:\Users\ZZZ> Start-Transcript
Transcript started, output file is C:\Users\ZZZ\Documents\PowerShell_transcript.YYY.wiyqAN+1.20230302112546.txt
PS C:\Users\ZZZ> [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.17763.0 Microsoft Windows NT 10.0.17763.0


PS C:\Users\ZZZ> $PSVersiontable

Name                           Value
----                           -----
PSVersion                      5.1.17763.3770
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.3770
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PS C:\Users\ZZZ> Import-Module VMware.PowerCli -Verbose -Debug
VERBOSE: Loading module from path 'C:\Users\ZZZ\Documents\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCli.psd1'.
DEBUG:
using System;
using System.Collections.Generic;
using System.Net;
using System.Net.Security;
using System.Security.Cryptography.X509Certificates;
using System.Text;

public static class CustomCertificatesValidator {
    private static List<string> _cachedCertificates;
    private static StringBuilder _log;

    public static void Initialize() {
        _cachedCertificates = new List<string>();
        _log = new StringBuilder();

        _log.AppendLine("Creating Certificates list");
    }

    public static string GetDebugLog() {
        string debugLog = _log.ToString().Trim();
        _log.Clear();

        return debugLog;
    }

    public static void AddCertificateToCache(string certificateThumbprint) {
        if (string.IsNullOrEmpty(certificateThumbprint)) {
            _log.AppendLine("No certificate specified");
        } else if (_cachedCertificates.Contains(certificateThumbprint)) {
            _log.Append("Certificate ");
            _log.Append(certificateThumbprint);
            _log.AppendLine(" is already added");
        } else {
            _log.Append("Adding certificate with thumbprint ");
            _log.Append(certificateThumbprint);
            _log.AppendLine(" to list of certificates");

            _cachedCertificates.Add(certificateThumbprint);
        }
    }

    public static bool RemoveCertificateFromCache(string certificateThumbprint) {
        bool result = false;

        if (string.IsNullOrEmpty(certificateThumbprint)) {
            _log.AppendLine("No certificate specified");
        } else if (!_cachedCertificates.Contains(certificateThumbprint)) {
            _log.Append("Certificate ");
            _log.Append(certificateThumbprint);
            _log.AppendLine(" is not present in the list of certificates");
        } else {
            _log.Append("Removing certificate with thumbprint ");
            _log.Append(certificateThumbprint);
            _log.AppendLine(" from list of certificates");

            result = _cachedCertificates.Remove(certificateThumbprint);
        }

        return result;
    }

    public static bool ValidateRemoteHostCertificate(
        object sender,
        X509Certificate certificate,
        X509Chain chain,
        SslPolicyErrors sslPolicyErrors) {

        _log.AppendLine("Invoking CustomCertificatesValidator.ValidateRemoteHostCertificate");
        if (certificate == null) {
            throw new ArgumentNullException("certificate");
        }

        var certificate2 = certificate as X509Certificate2 ?? new X509Certificate2(certificate);

        if (_cachedCertificates.Contains(certificate2.Thumbprint)) {
            _log.Append("Skipping certificate checks for certificate with thumbprint ");
            _log.AppendLine(certificate2.Thumbprint);

            return true;
        } else {
            _log.AppendLine("Validating Remote Host Certificate from Ssl Policy errors");
            return (sslPolicyErrors == SslPolicyErrors.None);
        }
    }

    public static RemoteCertificateValidationCallback GetDelegate() {
        _log.AppendLine("Calling CustomCertificatesValidator.ValidateRemoteHostCertificate");
        return new RemoteCertificateValidationCallback(CustomCertificatesValidator.ValidateRemoteHostCertificate);
    }
}
DEBUG: Importing file: Configuration
DEBUG: Importing file: ApiClient
DEBUG:
using System;
public class InvocationException : Exception {
    object _serverError;
    public InvocationException(Exception exception, object serverError) : base(exception.Message, exception) {
        _serverError = serverError;
    }

    public object ServerError {
        get {
            return _serverError;
        }
    }

    public InvocationException(string message, Exception exception, object serverError) : base(message, exception) {
        _serverError = serverError;
    }
}
DEBUG: Importing file: Get-CommonParameters
DEBUG: Importing file: HttpSignatureAuth
DEBUG: Importing file: Out-DebugParameter
DEBUG: Importing file: PowerShellCmdletsExtensions
DEBUG: Importing file: vSphereConfiguration
DEBUG: Importing file: vSphereApiClient
DEBUG:
using System;
using System.Management.Automation;
using System.Management.Automation.Runspaces;

public class vSphereConnectionToServerConfigurationArgumentTransformationAttribute : ArgumentTransformationAttribute {
    private const string VIConnectionToServerConfigurationScript = @"
        param (
            [Parameter(Mandatory)]
            [object]
            $InputData
        )

        $Result = $null

        if ($null -ne $InputData -and $null -ne ($InputData.GetType().GetInterfaces() | Where-Object -FilterScript { $_.Name -eq 'CisSession' })) {
            $ServerConfiguration = Get-vSphereServerConfiguration | Where-Object -FilterScript { $_.Server -eq $InputData.Name -and $_.PowerCLIConnection -eq $InputData }
            if ($null -ne $ServerConfiguration) {
                $Result = $ServerConfiguration
            } else {
                $Result = New-vSphereServerConfiguration -VIConnection $InputData -NotDefault:$true
            }
        }

        $Result
    ";

    public override object Transform(EngineIntrinsics engineIntrinsics, object inputData) {
        object serverConfiguration = inputData;

        try {
            var results = engineIntrinsics.InvokeCommand.InvokeScript(VIConnectionToServerConfigurationScript, false, PipelineResultTypes.None, null, inputData);
            if (results.Count > 0 && results[0] != null) {
                serverConfiguration = results[0];
            }
        }
        catch (RuntimeException e) {
            engineIntrinsics.Host.UI.WriteErrorLine(e.Message);
        }

        return serverConfiguration;
    }
}
DEBUG: Importing file: CommonAPITranslation
DEBUG: Importing file: InputTransformation
DEBUG: Importing file: vSphereRestApiTranslation
DEBUG: Importing file: HealthApi
DEBUG: Importing file: HealthCheckSettingsApi
DEBUG: Importing file: LocalAccountsApi
DEBUG: Importing file: MonitoringApi
DEBUG: Importing file: NetworkingApi
DEBUG: Importing file: NtpApi
DEBUG: Importing file: RecoveryApi
DEBUG: Importing file: ServicesApi
DEBUG: Importing file: ShutdownApi
DEBUG: Importing file: SupportBundleApi
DEBUG: Importing file: TimesyncApi
DEBUG: Importing file: UpdateApi
DEBUG: Importing file: HealthCheckSettingsUpdateSpec
DEBUG: Importing file: LocalAccountsConfig
DEBUG: Importing file: LocalAccountsCreateRequestBody
DEBUG: Importing file: LocalAccountsUpdateConfig
DEBUG: Importing file: NetworkingChangeSpec
DEBUG: Importing file: NetworkingDnsServersDNSServerConfig
DEBUG: Importing file: NetworkingInterfacesIpv4Config
DEBUG: Importing file: NetworkingInterfacesIpv6Address
DEBUG: Importing file: NetworkingInterfacesIpv6Config
DEBUG: Importing file: NetworkingUpdateSpec
DEBUG: Importing file: NtpSetRequestBody
DEBUG: Importing file: NtpTestRequestBody
DEBUG: Importing file: ShutdownPoweroffRequestBody
DEBUG: Importing file: ShutdownRebootRequestBody
DEBUG: Importing file: SupportBundleCreateSpec
DEBUG: Importing file: TimesyncSetRequestBody
DEBUG: Importing file: ConsolecliApi
DEBUG: Importing file: DcuiApi
DEBUG: Importing file: ShellApi
DEBUG: Importing file: SshApi
DEBUG: Importing file: AccessConsolecliSetRequestBody
DEBUG: Importing file: AccessDcuiSetRequestBody
DEBUG: Importing file: AccessShellShellConfig
DEBUG: Importing file: AccessSshSetRequestBody
DEBUG: Importing file: ApplmgmtApi
DEBUG: Importing file: DatabaseApi
DEBUG: Importing file: DatabasestorageApi
DEBUG: Importing file: LoadApi
DEBUG: Importing file: MemApi
DEBUG: Importing file: SoftwarepackagesApi
DEBUG: Importing file: StorageApi
DEBUG: Importing file: SwapApi
DEBUG: Importing file: SystemApi
DEBUG: Importing file: ConfigsApi
DEBUG: Importing file: InfraprofileConfigsImportProfileSpec
DEBUG: Importing file: InfraprofileConfigsProfilesSpec
DEBUG: Importing file: PolicyApi
DEBUG: Importing file: LocalAccountsPolicyInfo
DEBUG: Importing file: ForwardingApi
DEBUG: Importing file: LoggingForwardingConfig
DEBUG: Importing file: LoggingForwardingSetRequestBody
DEBUG: Importing file: LoggingForwardingTestRequestBody
DEBUG: Importing file: DomainsApi
DEBUG: Importing file: HostnameApi
DEBUG: Importing file: InboundApi
DEBUG: Importing file: InterfacesApi
DEBUG: Importing file: Ipv4Api
DEBUG: Importing file: Ipv6Api
DEBUG: Importing file: NoProxyApi
DEBUG: Importing file: ProxyApi
DEBUG: Importing file: ServersApi
DEBUG: Importing file: NetworkingDnsDomainsAddRequestBody
DEBUG: Importing file: NetworkingDnsDomainsSetRequestBody
DEBUG: Importing file: NetworkingDnsHostnameSetRequestBody
DEBUG: Importing file: NetworkingDnsHostnameTestRequestBody
DEBUG: Importing file: NetworkingDnsServersAddRequestBody
DEBUG: Importing file: NetworkingDnsServersDNSServerConfig
DEBUG: Importing file: NetworkingDnsServersTestRequestBody
DEBUG: Importing file: NetworkingFirewallInboundRule
DEBUG: Importing file: NetworkingFirewallInboundSetRequestBody
DEBUG: Importing file: NetworkingInterfacesIpv4Config
DEBUG: Importing file: NetworkingInterfacesIpv6Address
DEBUG: Importing file: NetworkingInterfacesIpv6Config
DEBUG: Importing file: NetworkingNoProxySetRequestBody
DEBUG: Importing file: NetworkingProxyConfig
DEBUG: Importing file: NetworkingProxyTestRequestBody
DEBUG: Importing file: ArchiveApi
DEBUG: Importing file: BackupApi
DEBUG: Importing file: DetailsApi
DEBUG: Importing file: JobApi
DEBUG: Importing file: PartsApi
DEBUG: Importing file: RestoreApi
DEBUG: Importing file: SchedulesApi
DEBUG: Importing file: SystemNameApi
DEBUG: Importing file: RecoveryBackupBackupRequest
DEBUG: Importing file: RecoveryBackupJobBackupRequest
DEBUG: Importing file: RecoveryBackupLocationSpec
DEBUG: Importing file: RecoveryBackupSchedulesCreateRequestBody
DEBUG: Importing file: RecoveryBackupSchedulesCreateSpec
DEBUG: Importing file: RecoveryBackupSchedulesRecurrenceInfo
DEBUG: Importing file: RecoveryBackupSchedulesRetentionInfo
DEBUG: Importing file: RecoveryBackupSchedulesRunRequestBody
DEBUG: Importing file: RecoveryBackupSchedulesUpdateSpec
DEBUG: Importing file: RecoveryBackupSystemNameArchiveFilterSpec
DEBUG: Importing file: RecoveryBackupSystemNameArchiveListRequestBody
DEBUG: Importing file: RecoveryReconciliationJobCreateSpec
DEBUG: Importing file: RecoveryRestoreJobRestoreRequest
DEBUG: Importing file: RecoveryRestoreRestoreRequest
DEBUG: Importing file: ComponentsApi
DEBUG: Importing file: GlobalFipsApi
DEBUG: Importing file: StorageApi
DEBUG: Importing file: TimeApi
DEBUG: Importing file: TimezoneApi
DEBUG: Importing file: UptimeApi
DEBUG: Importing file: VersionApi
DEBUG: Importing file: SystemSecurityGlobalFipsUpdateSpec
DEBUG: Importing file: SystemTimeTimezoneSetRequestBody
DEBUG: Importing file: PendingApi
DEBUG: Importing file: PolicyApi
DEBUG: Importing file: StagedApi
DEBUG: Importing file: UpdatePendingInstallRequestBody
DEBUG: Importing file: UpdatePendingStageAndInstallRequestBody
DEBUG: Importing file: UpdatePendingValidateRequestBody
DEBUG: Importing file: UpdatePolicyConfig
DEBUG: Importing file: UpdatePolicyTime
DEBUG: Importing file: SessionApi
DEBUG: Importing file: TasksApi
DEBUG: Importing file: StdDynamicID
DEBUG: Importing file: TasksFilterSpec
DEBUG: Importing file: TasksGetSpec
DEBUG: Importing file: TasksListRequestBody
DEBUG: Importing file: CategoryApi
DEBUG: Importing file: TagApi
DEBUG: Importing file: TagAssociationApi
DEBUG: Importing file: StdDynamicID
DEBUG: Importing file: TaggingCategoryAddToUsedByRequestBody
DEBUG: Importing file: TaggingCategoryCreateSpec
DEBUG: Importing file: TaggingCategoryListUsedCategoriesRequestBody
DEBUG: Importing file: TaggingCategoryRemoveFromUsedByRequestBody
DEBUG: Importing file: TaggingCategoryUpdateSpec
DEBUG: Importing file: TaggingTagAddToUsedByRequestBody
DEBUG: Importing file: TaggingTagAssociationAttachMultipleTagsToObjectRequestBody
DEBUG: Importing file: TaggingTagAssociationAttachRequestBody
DEBUG: Importing file: TaggingTagAssociationAttachTagToMultipleObjectsRequestBody
DEBUG: Importing file: TaggingTagAssociationDetachMultipleTagsFromObjectRequestBody
DEBUG: Importing file: TaggingTagAssociationDetachRequestBody
DEBUG: Importing file: TaggingTagAssociationDetachTagFromMultipleObjectsRequestBody
DEBUG: Importing file: TaggingTagAssociationListAttachableTagsRequestBody
DEBUG: Importing file: TaggingTagAssociationListAttachedObjectsOnTagsRequestBody
DEBUG: Importing file: TaggingTagAssociationListAttachedTagsOnObjectsRequestBody
DEBUG: Importing file: TaggingTagAssociationListAttachedTagsRequestBody
DEBUG: Importing file: TaggingTagCreateSpec
DEBUG: Importing file: TaggingTagListTagsForCategoryRequestBody
DEBUG: Importing file: TaggingTagListUsedTagsRequestBody
DEBUG: Importing file: TaggingTagRemoveFromUsedByRequestBody
DEBUG: Importing file: TaggingTagUpdateSpec
DEBUG: Importing file: ConfigurationApi
DEBUG: Importing file: LibraryApi
DEBUG: Importing file: LocalLibraryApi
DEBUG: Importing file: SecurityPoliciesApi
DEBUG: Importing file: SubscribedLibraryApi
DEBUG: Importing file: TrustedCertificatesApi
DEBUG: Importing file: TypeApi
DEBUG: Importing file: ConfigurationModel
DEBUG: Importing file: LibraryFindSpec
DEBUG: Importing file: LibraryModel
DEBUG: Importing file: LibraryOptimizationInfo
DEBUG: Importing file: LibraryPublishInfo
DEBUG: Importing file: LibrarySourceInfo
DEBUG: Importing file: LibraryStorageBacking
DEBUG: Importing file: LibrarySubscriptionInfo
DEBUG: Importing file: LocalLibraryDestinationSpec
DEBUG: Importing file: LocalLibraryPublishRequestBody
DEBUG: Importing file: SubscribedLibraryProbeRequestBody
DEBUG: Importing file: TrustedCertificatesCreateSpec
DEBUG: Importing file: ChangesApi
DEBUG: Importing file: DownloadSessionApi
DEBUG: Importing file: FileApi
DEBUG: Importing file: ItemApi
DEBUG: Importing file: StorageApi
DEBUG: Importing file: SubscribedItemApi
DEBUG: Importing file: SubscriptionsApi
DEBUG: Importing file: UpdateSessionApi
DEBUG: Importing file: LibraryItemCertificateVerificationInfo
DEBUG: Importing file: LibraryItemDestinationSpec
DEBUG: Importing file: LibraryItemDownloadSessionFailRequestBody
DEBUG: Importing file: LibraryItemDownloadsessionFilePrepareRequestBody
DEBUG: Importing file: LibraryItemDownloadSessionKeepAliveRequestBody
DEBUG: Importing file: LibraryItemDownloadSessionModel
DEBUG: Importing file: LibraryItemFileChecksumInfo
DEBUG: Importing file: LibraryItemFindSpec
DEBUG: Importing file: LibraryItemModel
DEBUG: Importing file: LibraryItemPublishRequestBody
DEBUG: Importing file: LibraryItemTransferEndpoint
DEBUG: Importing file: LibraryItemUpdatesessionCertificateInfo
DEBUG: Importing file: LibraryItemUpdateSessionFailRequestBody
DEBUG: Importing file: LibraryItemUpdatesessionFileAddSpec
DEBUG: Importing file: LibraryItemUpdateSessionKeepAliveRequestBody
DEBUG: Importing file: LibraryItemUpdateSessionModel
DEBUG: Importing file: LibraryItemUpdatesessionPreviewInfo
DEBUG: Importing file: LibraryItemUpdatesessionPreviewWarningInfo
DEBUG: Importing file: LibraryItemUpdatesessionWarningBehavior
DEBUG: Importing file: LibraryStorageBacking
DEBUG: Importing file: LibrarySubscribedItemSyncRequestBody
DEBUG: Importing file: LibrarySubscriptionsCreateSpec
DEBUG: Importing file: LibrarySubscriptionsCreateSpecNewSubscribedLibrary
DEBUG: Importing file: LibrarySubscriptionsCreateSpecPlacement
DEBUG: Importing file: LibrarySubscriptionsCreateSpecSubscribedLibrary
DEBUG: Importing file: LibrarySubscriptionsCreateSpecVcenter
DEBUG: Importing file: LibrarySubscriptionsUpdateSpec
DEBUG: Importing file: LibrarySubscriptionsUpdateSpecPlacement
DEBUG: Importing file: LibrarySubscriptionsUpdateSpecVcenter
DEBUG: Importing file: StdLocalizableMessage
DEBUG: Importing file: StdLocalizationParam
DEBUG: Importing file: StdNestedLocalizableMessage
DEBUG: Importing file: CompatibilityDataApi
DEBUG: Importing file: CompatibilityReleasesApi
DEBUG: Importing file: CompatibilityReportApi
DEBUG: Importing file: ReportsApi
DEBUG: Importing file: HclHostsCompatibilityReportSpec
DEBUG: Importing file: InstalledComponentsApi
DEBUG: Importing file: SoftwareApi
DEBUG: Importing file: HostsSoftwareHostCredentials
DEBUG: Importing file: AddOnApi
DEBUG: Importing file: AddOnsApi
DEBUG: Importing file: ApplyApi
DEBUG: Importing file: ApplyImpactApi
DEBUG: Importing file: BaseImageApi
DEBUG: Importing file: BaseImagesApi
DEBUG: Importing file: CommitsApi
DEBUG: Importing file: ComplianceApi
DEBUG: Importing file: ComplianceStatusApi
DEBUG: Importing file: ComponentsApi
DEBUG: Importing file: ConfigurationApi
DEBUG: Importing file: ContentApi
DEBUG: Importing file: DepotOverridesApi
DEBUG: Importing file: DepotsApi
DEBUG: Importing file: DetailsApi
DEBUG: Importing file: DraftsApi
DEBUG: Importing file: EffectiveApi
DEBUG: Importing file: EffectiveComponentsApi
DEBUG: Importing file: HardwareCompatibilityApi
DEBUG: Importing file: HardwareSupportApi
DEBUG: Importing file: LastApplyResultApi
DEBUG: Importing file: LastCheckResultApi
DEBUG: Importing file: LastComplianceResultApi
DEBUG: Importing file: LastPrecheckResultApi
DEBUG: Importing file: ManagersApi
DEBUG: Importing file: OfflineApi
DEBUG: Importing file: OnlineApi
DEBUG: Importing file: PackagesApi
DEBUG: Importing file: RecentTasksApi
DEBUG: Importing file: RecommendationsApi
DEBUG: Importing file: SchemaApi
DEBUG: Importing file: SoftwareApi
DEBUG: Importing file: SolutionsApi
DEBUG: Importing file: SyncScheduleApi
DEBUG: Importing file: TransitionApi
DEBUG: Importing file: UmdsApi
DEBUG: Importing file: VcgEntriesApi
DEBUG: Importing file: VersionsApi
DEBUG: Importing file: SettingsAddOnSpec
DEBUG: Importing file: SettingsBaseImageSpec
DEBUG: Importing file: SettingsClustersConfigurationApplySpec
DEBUG: Importing file: SettingsClustersConfigurationImportSpec
DEBUG: Importing file: SettingsClustersDepotOverridesDepot
DEBUG: Importing file: SettingsClustersEnablementConfigurationTransitionFileSpec
DEBUG: Importing file: SettingsClustersEnablementSoftwareCheckSpec
DEBUG: Importing file: SettingsClustersEnablementSoftwareEnableSpec
DEBUG: Importing file: SettingsClustersPoliciesApplyConfiguredPolicySpec
DEBUG: Importing file: SettingsClustersPoliciesApplyEffectiveEffectivePolicySpec
DEBUG: Importing file: SettingsClustersPoliciesApplyEffectiveFailureAction
DEBUG: Importing file: SettingsClustersPoliciesApplyEffectiveParallelRemediationAction
DEBUG: Importing file: SettingsClustersPoliciesApplyFailureAction
DEBUG: Importing file: SettingsClustersPoliciesApplyParallelRemediationAction
DEBUG: Importing file: SettingsClustersSoftwareApplySpec
DEBUG: Importing file: SettingsClustersSoftwareCheckSpec
DEBUG: Importing file: SettingsClustersSoftwareDraftsCommitSpec
DEBUG: Importing file: SettingsClustersSoftwareDraftsImportSpec
DEBUG: Importing file: SettingsClustersSoftwareDraftsSoftwareComponentsUpdateSpec
DEBUG: Importing file: SettingsClustersSoftwareExportSpec
DEBUG: Importing file: SettingsClustersSoftwareRecommendationsFilterSpec
DEBUG: Importing file: SettingsClustersSoftwareReportsHardwareCompatibilityStorageDeviceOverridesComplianceStatusKey
DEBUG: Importing file: SettingsClustersSoftwareReportsHardwareCompatibilityStorageDeviceOverridesComplianceStatusReclassificationSpec
DEBUG: Importing file: SettingsClustersSoftwareReportsHardwareCompatibilityStorageDeviceOverridesComplianceStatusUpdateSpec
DEBUG: Importing file: SettingsClustersSoftwareReportsHardwareCompatibilityStorageDeviceOverridesVcgEntriesKey
DEBUG: Importing file: SettingsClustersSoftwareReportsHardwareCompatibilityStorageDeviceOverridesVcgEntriesProductSelectionSpec
DEBUG: Importing file: SettingsClustersSoftwareReportsHardwareCompatibilityStorageDeviceOverridesVcgEntriesUpdateSpec
DEBUG: Importing file: SettingsClustersSoftwareStageSpec
DEBUG: Importing file: SettingsDefaultsClustersPoliciesApplyConfiguredPolicySpec
DEBUG: Importing file: SettingsDefaultsClustersPoliciesApplyFailureAction
DEBUG: Importing file: SettingsDefaultsClustersPoliciesApplyParallelRemediationAction
DEBUG: Importing file: SettingsDefaultsHostsPoliciesApplyConfiguredPolicySpec
DEBUG: Importing file: SettingsDefaultsHostsPoliciesApplyFailureAction
DEBUG: Importing file: SettingsDepotsOfflineConnectionSpec
DEBUG: Importing file: SettingsDepotsOfflineCreateSpec
DEBUG: Importing file: SettingsDepotsOfflineHostCredentials
DEBUG: Importing file: SettingsDepotsOnlineCreateSpec
DEBUG: Importing file: SettingsDepotsOnlineUpdateSpec
DEBUG: Importing file: SettingsDepotsSyncScheduleSchedule
DEBUG: Importing file: SettingsDepotsSyncScheduleSpec
DEBUG: Importing file: SettingsDepotsUmdsSetSpec
DEBUG: Importing file: SettingsDepotsUmdsUpdateSpec
DEBUG: Importing file: SettingsHardwareSupportPackageSpec
DEBUG: Importing file: SettingsHardwareSupportSpec
DEBUG: Importing file: SettingsHostsEnablementSoftwareCheckSpec
DEBUG: Importing file: SettingsHostsEnablementSoftwareEnableSpec
DEBUG: Importing file: SettingsHostsPoliciesApplyConfiguredPolicySpec
DEBUG: Importing file: SettingsHostsPoliciesApplyFailureAction
DEBUG: Importing file: SettingsHostsSoftwareApplySpec
DEBUG: Importing file: SettingsHostsSoftwareCheckSpec
DEBUG: Importing file: SettingsHostsSoftwareDraftsCommitSpec
DEBUG: Importing file: SettingsHostsSoftwareDraftsImportSpec
DEBUG: Importing file: SettingsHostsSoftwareDraftsSoftwareComponentsUpdateSpec
DEBUG: Importing file: SettingsHostsSoftwareExportSpec
DEBUG: Importing file: SettingsHostsSoftwareStageSpec
DEBUG: Importing file: SettingsSolutionComponentSpec
DEBUG: Importing file: SettingsSolutionSpec
DEBUG: Importing file: CommandApi
DEBUG: Importing file: ComponentApi
DEBUG: Importing file: EnumerationApi
DEBUG: Importing file: ModelApi
DEBUG: Importing file: NamespaceApi
DEBUG: Importing file: OperationApi
DEBUG: Importing file: PackageApi
DEBUG: Importing file: ResourceApi
DEBUG: Importing file: ServiceApi
DEBUG: Importing file: StructureApi
DEBUG: Importing file: MetadataCliCommandGetRequestBody
DEBUG: Importing file: MetadataCliCommandIdentity
DEBUG: Importing file: MetadataCliNamespaceGetRequestBody
DEBUG: Importing file: MetadataCliNamespaceIdentity
DEBUG: Importing file: ClusterApi
DEBUG: Importing file: DatacenterApi
DEBUG: Importing file: DatastoreApi
DEBUG: Importing file: DeploymentApi
DEBUG: Importing file: FolderApi
DEBUG: Importing file: HostApi
DEBUG: Importing file: NetworkApi
DEBUG: Importing file: ResourcePoolApi
DEBUG: Importing file: VmApi
DEBUG: Importing file: DatacenterCreateSpec
DEBUG: Importing file: HostCreateSpec
DEBUG: Importing file: ResourcePoolCreateSpec
DEBUG: Importing file: ResourcePoolResourceAllocationCreateSpec
DEBUG: Importing file: ResourcePoolResourceAllocationUpdateSpec
DEBUG: Importing file: ResourcePoolSharesInfo
DEBUG: Importing file: ResourcePoolUpdateSpec
DEBUG: Importing file: VMClonePlacementSpec
DEBUG: Importing file: VMCloneSpec
DEBUG: Importing file: VMCreateSpec
DEBUG: Importing file: VMDiskCloneSpec
DEBUG: Importing file: VMDiskRelocateSpec
DEBUG: Importing file: VMGuestCustomizationSpec
DEBUG: Importing file: VmHardwareAdapterNvmeCreateSpec
DEBUG: Importing file: VmHardwareAdapterSataCreateSpec
DEBUG: Importing file: VmHardwareAdapterScsiCreateSpec
DEBUG: Importing file: VmHardwareBootCreateSpec
DEBUG: Importing file: VmHardwareBootDeviceEntryCreateSpec
DEBUG: Importing file: VmHardwareCdromBackingSpec
DEBUG: Importing file: VmHardwareCdromCreateSpec
DEBUG: Importing file: VmHardwareCpuUpdateSpec
DEBUG: Importing file: VmHardwareDiskBackingSpec
DEBUG: Importing file: VmHardwareDiskCreateSpec
DEBUG: Importing file: VmHardwareDiskStoragePolicySpec
DEBUG: Importing file: VmHardwareDiskVmdkCreateSpec
DEBUG: Importing file: VmHardwareEthernetBackingSpec
DEBUG: Importing file: VmHardwareEthernetCreateSpec
DEBUG: Importing file: VmHardwareEthernetUpdateSpec
DEBUG: Importing file: VmHardwareFloppyBackingSpec
DEBUG: Importing file: VmHardwareFloppyCreateSpec
DEBUG: Importing file: VmHardwareIdeAddressSpec
DEBUG: Importing file: VmHardwareMemoryUpdateSpec
DEBUG: Importing file: VmHardwareNvmeAddressSpec
DEBUG: Importing file: VmHardwareParallelBackingSpec
DEBUG: Importing file: VmHardwareParallelCreateSpec
DEBUG: Importing file: VmHardwareParallelUpdateSpec
DEBUG: Importing file: VmHardwareSataAddressSpec
DEBUG: Importing file: VmHardwareScsiAddressSpec
DEBUG: Importing file: VmHardwareSerialBackingSpec
DEBUG: Importing file: VmHardwareSerialCreateSpec
DEBUG: Importing file: VmHardwareSerialUpdateSpec
DEBUG: Importing file: VMInstantClonePlacementSpec
DEBUG: Importing file: VMInstantCloneSpec
DEBUG: Importing file: VMPlacementSpec
DEBUG: Importing file: VMRegisterPlacementSpec
DEBUG: Importing file: VMRegisterSpec
DEBUG: Importing file: VMRelocatePlacementSpec
DEBUG: Importing file: VMRelocateSpec
DEBUG: Importing file: VMStoragePolicySpec
DEBUG: Importing file: TokenApi
DEBUG: Importing file: SigningCertificateApi
DEBUG: Importing file: TlsApi
DEBUG: Importing file: TlsCsrApi
DEBUG: Importing file: TrustedRootChainsApi
DEBUG: Importing file: VmcaRootApi
DEBUG: Importing file: CertificateManagementVcenterSigningCertificateRefreshRequestBody
DEBUG: Importing file: CertificateManagementVcenterSigningCertificateSetSpec
DEBUG: Importing file: CertificateManagementVcenterTlsCsrSpec
DEBUG: Importing file: CertificateManagementVcenterTlsRenewRequestBody
DEBUG: Importing file: CertificateManagementVcenterTlsReplaceSpec
DEBUG: Importing file: CertificateManagementVcenterTlsSpec
DEBUG: Importing file: CertificateManagementVcenterTrustedRootChainsCreateSpec
DEBUG: Importing file: CertificateManagementVcenterVmcaRootCreateSpec
DEBUG: Importing file: CertificateManagementX509CertChain
DEBUG: Importing file: HarborApi
DEBUG: Importing file: HealthApi
DEBUG: Importing file: ProjectsApi
DEBUG: Importing file: ContentRegistriesHarborCreateSpec
DEBUG: Importing file: ContentRegistriesHarborGarbageCollection
DEBUG: Importing file: ContentRegistriesHarborProjectsCreateSpec
DEBUG: Importing file: ContentRegistriesHarborStorageSpec
DEBUG: Importing file: DefaultPolicyApi
DEBUG: Importing file: ActiveDirectoryApi
DEBUG: Importing file: ImportHistoryApi
DEBUG: Importing file: InstallApi
DEBUG: Importing file: MigrateApi
DEBUG: Importing file: QuestionApi
DEBUG: Importing file: RemotePscApi
DEBUG: Importing file: ReplicatedApi
DEBUG: Importing file: StandaloneApi
DEBUG: Importing file: ThumbprintApi
DEBUG: Importing file: UpgradeApi
DEBUG: Importing file: DeploymentHistoryMigrationSpec
DEBUG: Importing file: DeploymentImportHistoryCreateSpec
DEBUG: Importing file: DeploymentInstallInstallSpec
DEBUG: Importing file: DeploymentInstallVcsaEmbeddedSpec
DEBUG: Importing file: DeploymentLocationSpec
DEBUG: Importing file: DeploymentMigrateActiveDirectoryCheckSpec
DEBUG: Importing file: DeploymentMigrateActiveDirectorySpec
DEBUG: Importing file: DeploymentMigrateMigrateSpec
DEBUG: Importing file: DeploymentMigrateMigrationAssistantSpec
DEBUG: Importing file: DeploymentMigratePscSpec
DEBUG: Importing file: DeploymentMigrateSourceVcWindows
DEBUG: Importing file: DeploymentMigrateVcsaEmbeddedSpec
DEBUG: Importing file: DeploymentQuestionAnswerSpec
DEBUG: Importing file: DeploymentRemotePscSpec
DEBUG: Importing file: DeploymentReplicatedPscSpec
DEBUG: Importing file: DeploymentReplicatedSpec
DEBUG: Importing file: DeploymentStandalonePscSpec
DEBUG: Importing file: DeploymentStandaloneSpec
DEBUG: Importing file: DeploymentUpgradePscSpec
DEBUG: Importing file: DeploymentUpgradeSourceApplianceSpec
DEBUG: Importing file: DeploymentUpgradeUpgradeSpec
DEBUG: Importing file: DeploymentUpgradeVcsaEmbeddedSpec
DEBUG: Importing file: CustomizationSpecsApi
DEBUG: Importing file: GuestAdapterMapping
DEBUG: Importing file: GuestCloudConfiguration
DEBUG: Importing file: GuestCloudinitConfiguration
DEBUG: Importing file: GuestConfigurationSpec
DEBUG: Importing file: GuestCustomizationSpec
DEBUG: Importing file: GuestCustomizationSpecsCreateSpec
DEBUG: Importing file: GuestCustomizationSpecsExportRequestBody
DEBUG: Importing file: GuestCustomizationSpecsImportSpecificationRequestBody
DEBUG: Importing file: GuestCustomizationSpecsSpec
DEBUG: Importing file: GuestDomain
DEBUG: Importing file: GuestGlobalDNSSettings
DEBUG: Importing file: GuestGuiUnattended
DEBUG: Importing file: GuestHostnameGenerator
DEBUG: Importing file: GuestIPSettings
DEBUG: Importing file: GuestIpv4
DEBUG: Importing file: GuestIpv6
DEBUG: Importing file: GuestIpv6Address
DEBUG: Importing file: GuestLinuxConfiguration
DEBUG: Importing file: GuestUserData
DEBUG: Importing file: GuestWindowsConfiguration
DEBUG: Importing file: GuestWindowsNetworkAdapterSettings
DEBUG: Importing file: GuestWindowsSysprep
DEBUG: Importing file: ProvidersApi
DEBUG: Importing file: CertificateManagementX509CertChain
DEBUG: Importing file: IdentityProvidersActiveDirectoryOverLdap
DEBUG: Importing file: IdentityProvidersCreateSpec
DEBUG: Importing file: IdentityProvidersOauth2CreateSpec
DEBUG: Importing file: IdentityProvidersOauth2UpdateSpec
DEBUG: Importing file: IdentityProvidersOidcCreateSpec
DEBUG: Importing file: IdentityProvidersOidcUpdateSpec
DEBUG: Importing file: IdentityProvidersUpdateSpec
DEBUG: Importing file: DatastoreApi
DEBUG: Importing file: NetworkApi
DEBUG: Importing file: ImageApi
DEBUG: Importing file: IsoImageMountRequestBody
DEBUG: Importing file: IsoImageUnmountRequestBody
DEBUG: Importing file: AssociatedProductsApi
DEBUG: Importing file: InteropReportApi
DEBUG: Importing file: PendingApi
DEBUG: Importing file: PrecheckReportApi
DEBUG: Importing file: ProductCatalogApi
DEBUG: Importing file: ReportsApi
DEBUG: Importing file: LcmDiscoveryAssociatedProductsCreateSpec
DEBUG: Importing file: LcmDiscoveryAssociatedProductsUpdateSpec
DEBUG: Importing file: LcmDiscoveryInteropReportSpec
DEBUG: Importing file: ClusterAvailableVersionsApi
DEBUG: Importing file: ClusterCompatibilityApi
DEBUG: Importing file: ClustersApi
DEBUG: Importing file: ClusterSizeInfoApi
DEBUG: Importing file: ClusterSupervisorServicesApi
DEBUG: Importing file: CompatibilityApi
DEBUG: Importing file: ConditionsApi
DEBUG: Importing file: DistributedSwitchCompatibilityApi
DEBUG: Importing file: DistributedSwitchesApi
DEBUG: Importing file: EdgeClusterCompatibilityApi
DEBUG: Importing file: EdgesApi
DEBUG: Importing file: HostsConfigApi
DEBUG: Importing file: LoadBalancersApi
DEBUG: Importing file: NamespaceResourceOptionsApi
DEBUG: Importing file: NetworksApi
DEBUG: Importing file: NsxTier0GatewayApi
DEBUG: Importing file: ProfilesApi
DEBUG: Importing file: ProvidersApi
DEBUG: Importing file: SummaryApi
DEBUG: Importing file: SupervisorsApi
DEBUG: Importing file: SupervisorServicesApi
DEBUG: Importing file: SupportBundleApi
DEBUG: Importing file: TimeSeriesApi
DEBUG: Importing file: TopologyApi
DEBUG: Importing file: VersionsApi
DEBUG: Importing file: VirtualMachineClassesApi
DEBUG: Importing file: NamespaceManagementClustersEnableSpec
DEBUG: Importing file: NamespaceManagementClustersImageRegistry
DEBUG: Importing file: NamespaceManagementClustersImageStorageSpec
DEBUG: Importing file: NamespaceManagementClustersIpv4Range
DEBUG: Importing file: NamespaceManagementClustersNCPClusterNetworkEnableSpec
DEBUG: Importing file: NamespaceManagementClustersNCPClusterNetworkSetSpec
DEBUG: Importing file: NamespaceManagementClustersNCPClusterNetworkUpdateSpec
DEBUG: Importing file: NamespaceManagementClustersNetworkSpec
DEBUG: Importing file: NamespaceManagementClustersSetSpec
DEBUG: Importing file: NamespaceManagementClustersUpdateSpec
DEBUG: Importing file: NamespaceManagementClustersWorkloadNetworksEnableSpec
DEBUG: Importing file: NamespaceManagementCNSFileConfig
DEBUG: Importing file: NamespaceManagementIPRange
DEBUG: Importing file: NamespaceManagementIpv4Cidr
DEBUG: Importing file: NamespaceManagementLoadBalancersAviConfigCreateSpec
DEBUG: Importing file: NamespaceManagementLoadBalancersAviConfigSetSpec
DEBUG: Importing file: NamespaceManagementLoadBalancersAviConfigUpdateSpec
DEBUG: Importing file: NamespaceManagementLoadBalancersConfigSpec
DEBUG: Importing file: NamespaceManagementLoadBalancersHAProxyConfigCreateSpec
DEBUG: Importing file: NamespaceManagementLoadBalancersHAProxyConfigSetSpec
DEBUG: Importing file: NamespaceManagementLoadBalancersHAProxyConfigUpdateSpec
DEBUG: Importing file: NamespaceManagementLoadBalancersServer
DEBUG: Importing file: NamespaceManagementLoadBalancersSetSpec
DEBUG: Importing file: NamespaceManagementLoadBalancersUpdateSpec
DEBUG: Importing file: NamespaceManagementNetworksCreateSpec
DEBUG: Importing file: NamespaceManagementNetworksEdgesEdge
DEBUG: Importing file: NamespaceManagementNetworksEdgesHAProxyConfig
DEBUG: Importing file: NamespaceManagementNetworksEdgesNSXAdvancedLBConfig
DEBUG: Importing file: NamespaceManagementNetworksEdgesNSXConfig
DEBUG: Importing file: NamespaceManagementNetworksEdgesServer
DEBUG: Importing file: NamespaceManagementNetworksIPAssignment
DEBUG: Importing file: NamespaceManagementNetworksIPManagement
DEBUG: Importing file: NamespaceManagementNetworksIPRange
DEBUG: Importing file: NamespaceManagementNetworksNsxDistributedSwitchesFilterSpec
DEBUG: Importing file: NamespaceManagementNetworksNsxEdgesFilterSpec
DEBUG: Importing file: NamespaceManagementNetworksNsxNetworkCreateSpec
DEBUG: Importing file: NamespaceManagementNetworksNsxNetworkSetSpec
DEBUG: Importing file: NamespaceManagementNetworksNsxNetworkUpdateSpec
DEBUG: Importing file: NamespaceManagementNetworksServiceDNS
DEBUG: Importing file: NamespaceManagementNetworksServiceNTP
DEBUG: Importing file: NamespaceManagementNetworksServices
DEBUG: Importing file: NamespaceManagementNetworksSetSpec
DEBUG: Importing file: NamespaceManagementNetworksUpdateSpec
DEBUG: Importing file: NamespaceManagementNetworksVsphereDVPGNetworkCreateSpec
DEBUG: Importing file: NamespaceManagementNetworksVsphereDVPGNetworkSetSpec
DEBUG: Importing file: NamespaceManagementNetworksVsphereDVPGNetworkUpdateSpec
DEBUG: Importing file: NamespaceManagementProxyConfiguration
DEBUG: Importing file: NamespaceManagementSoftwareClustersUpgradeSpec
DEBUG: Importing file: NamespaceManagementStatsTimeSeriesPodIdentifier
DEBUG: Importing file: NamespaceManagementStorageProfilesFilterSpec
DEBUG: Importing file: NamespaceManagementSupervisorsCNSFileConfig
DEBUG: Importing file: NamespaceManagementSupervisorsControlPlane
DEBUG: Importing file: NamespaceManagementSupervisorsEnableOnComputeClusterSpec
DEBUG: Importing file: NamespaceManagementSupervisorsEnableOnZonesSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesCarvelCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesCheckContentRequestBody
DEBUG: Importing file: NamespaceManagementSupervisorServicesClusterSupervisorServicesCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesClusterSupervisorServicesSetSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesContentCheckSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesCustomCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesUpdateSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesVersionsCarvelCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesVersionsCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesVersionsCustomCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesVersionsVsphereCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorServicesVsphereCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorsIdentityProvidersCreateSpec
DEBUG: Importing file: NamespaceManagementSupervisorsIdentityProvidersSetSpec
DEBUG: Importing file: NamespaceManagementSupervisorsIdentityProvidersUpdateSpec
DEBUG: Importing file: NamespaceManagementSupervisorsImageRegistry
DEBUG: Importing file: NamespaceManagementSupervisorsImageSyncConfig
DEBUG: Importing file: NamespaceManagementSupervisorsKubeAPIServerOptions
DEBUG: Importing file: NamespaceManagementSupervisorsKubeAPIServerSecurity
DEBUG: Importing file: NamespaceManagementSupervisorsNetworksManagementNetwork
DEBUG: Importing file: NamespaceManagementSupervisorsNetworksManagementNetworkBacking
DEBUG: Importing file: NamespaceManagementSupervisorsNetworksManagementProxyConfiguration
DEBUG: Importing file: NamespaceManagementSupervisorsNetworksWorkloadNetwork
DEBUG: Importing file: NamespaceManagementSupervisorsNetworksWorkloadNsxNetwork
DEBUG: Importing file: NamespaceManagementSupervisorsNetworksWorkloadVSphereNetwork
DEBUG: Importing file: NamespaceManagementSupervisorsWorkloads
DEBUG: Importing file: NamespaceManagementSupervisorsWorkloadsStorageConfig
DEBUG: Importing file: NamespaceManagementVirtualMachineClassesCreateSpec
DEBUG: Importing file: NamespaceManagementVirtualMachineClassesDynamicDirectPathIODevice
DEBUG: Importing file: NamespaceManagementVirtualMachineClassesInstanceStorage
DEBUG: Importing file: NamespaceManagementVirtualMachineClassesInstanceStorageVolume
DEBUG: Importing file: NamespaceManagementVirtualMachineClassesUpdateSpec
DEBUG: Importing file: NamespaceManagementVirtualMachineClassesVGPUDevice
DEBUG: Importing file: NamespaceManagementVirtualMachineClassesVirtualDevices
DEBUG: Importing file: AccessApi
DEBUG: Importing file: InstancesApi
DEBUG: Importing file: NamespaceSelfServiceApi
DEBUG: Importing file: NamespaceTemplatesApi
DEBUG: Importing file: NamespacesAccessCreateSpec
DEBUG: Importing file: NamespacesAccessSetSpec
DEBUG: Importing file: NamespacesInstancesAccess
DEBUG: Importing file: NamespacesInstancesCreateSpec
DEBUG: Importing file: NamespacesInstancesCreateSpecV2
DEBUG: Importing file: NamespacesInstancesIpv4Cidr
DEBUG: Importing file: NamespacesInstancesNetworkCreateSpec
DEBUG: Importing file: NamespacesInstancesNsxNetworkCreateSpec
DEBUG: Importing file: NamespacesInstancesPrincipal
DEBUG: Importing file: NamespacesInstancesSetSpec
DEBUG: Importing file: NamespacesInstancesStorageSpec
DEBUG: Importing file: NamespacesInstancesUpdateSpec
DEBUG: Importing file: NamespacesInstancesVMServiceSpec
DEBUG: Importing file: NamespacesNamespaceSelfServiceActivateTemplateSpec
DEBUG: Importing file: NamespacesNamespaceTemplatesCreateSpec
DEBUG: Importing file: NamespacesNamespaceTemplatesSubject
DEBUG: Importing file: NamespacesNamespaceTemplatesUpdateSpec
DEBUG: Importing file: ExportFlagApi
DEBUG: Importing file: ImportFlagApi
DEBUG: Importing file: LibraryItemApi
DEBUG: Importing file: OvfLibraryItemCreateRequestBody
DEBUG: Importing file: OvfLibraryItemCreateSpec
DEBUG: Importing file: OvfLibraryItemCreateTarget
DEBUG: Importing file: OvfLibraryItemDeployableIdentity
DEBUG: Importing file: OvfLibraryItemDeploymentTarget
DEBUG: Importing file: OvfLibraryItemDeployRequestBody
DEBUG: Importing file: OvfLibraryItemFilterRequestBody
DEBUG: Importing file: OvfLibraryItemResourcePoolDeploymentSpec
DEBUG: Importing file: OvfLibraryItemStorageGroupMapping
DEBUG: Importing file: ServiceApi
DEBUG: Importing file: ServicesServiceUpdateSpec
DEBUG: Importing file: ComplianceApi
DEBUG: Importing file: PoliciesApi
DEBUG: Importing file: VmApi
DEBUG: Importing file: StoragePoliciesCheckCompatibilityRequestBody
DEBUG: Importing file: DeploymentTypeApi
DEBUG: Importing file: PscRegistrationApi
DEBUG: Importing file: DeploymentRemotePscSpec
DEBUG: Importing file: SystemConfigDeploymentTypeReconfigureSpec
DEBUG: Importing file: AssociationsApi
DEBUG: Importing file: NodesApi
DEBUG: Importing file: ReplicationStatusApi
DEBUG: Importing file: AttestationApi
DEBUG: Importing file: BaseImagesApi
DEBUG: Importing file: CaCertificatesApi
DEBUG: Importing file: ClientCertificateApi
DEBUG: Importing file: ConsumerPrincipalsApi
DEBUG: Importing file: CredentialApi
DEBUG: Importing file: CsrApi
DEBUG: Importing file: CurrentPeerCertificatesApi
DEBUG: Importing file: EndorsementKeysApi
DEBUG: Importing file: EventLogApi
DEBUG: Importing file: KmsApi
DEBUG: Importing file: PrincipalApi
DEBUG: Importing file: ProvidersApi
DEBUG: Importing file: ServicesApi
DEBUG: Importing file: ServicesAppliedConfigApi
DEBUG: Importing file: ServiceStatusApi
DEBUG: Importing file: SettingsApi
DEBUG: Importing file: TpmApi
DEBUG: Importing file: TrustAuthorityClustersApi
DEBUG: Importing file: TrustedPeerCertificatesApi
DEBUG: Importing file: TrustedInfrastructureAttestationServicesCreateSpec
DEBUG: Importing file: TrustedInfrastructureAttestationServicesFilterSpec
DEBUG: Importing file: TrustedInfrastructureHostsHardwareTpmEndorsementKeysPolicyPcrSpec
DEBUG: Importing file: TrustedInfrastructureHostsHardwareTpmEndorsementKeysUnsealSpec
DEBUG: Importing file: TrustedInfrastructureKmsServicesCreateSpec
DEBUG: Importing file: TrustedInfrastructureKmsServicesFilterSpec
DEBUG: Importing file: TrustedInfrastructureNetworkAddress
DEBUG: Importing file: TrustedInfrastructureStsPrincipal
DEBUG: Importing file: TrustedInfrastructureStsPrincipalId
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersAttestationTpm2CaCertificatesCreateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersAttestationTpm2EndorsementKeysCreateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersAttestationTpm2SettingsUpdateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersConsumerPrincipalsCreateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersConsumerPrincipalsFilterSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersKmsProvidersClientCertificateUpdateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersKmsProvidersCreateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersKmsProvidersKeyServerCreateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersKmsProvidersKeyServerUpdateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersKmsProvidersKmipServerCreateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersKmsProvidersKmipServerUpdateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersKmsProvidersServer
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersKmsProvidersTrustedPeerCertificatesUpdateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersKmsProvidersUpdateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityClustersUpdateSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityHostsAttestationFilterSpec
DEBUG: Importing file: TrustedInfrastructureTrustAuthorityHostsKmsFilterSpec
DEBUG: Importing file: TrustedInfrastructureTrustedClustersAttestationServicesAppliedConfigFilterSpec
DEBUG: Importing file: TrustedInfrastructureTrustedClustersAttestationServicesCreateSpec
DEBUG: Importing file: TrustedInfrastructureTrustedClustersAttestationServicesFilterSpec
DEBUG: Importing file: TrustedInfrastructureTrustedClustersKmsServicesAppliedConfigFilterSpec
DEBUG: Importing file: TrustedInfrastructureTrustedClustersKmsServicesCreateSpec
DEBUG: Importing file: TrustedInfrastructureTrustedClustersKmsServicesFilterSpec
DEBUG: Importing file: TrustedInfrastructureX509CertChain
DEBUG: Importing file: ActiveApi
DEBUG: Importing file: ClusterApi
DEBUG: Importing file: DeploymentTypeApi
DEBUG: Importing file: ModeApi
DEBUG: Importing file: OperationsApi
DEBUG: Importing file: PassiveApi
DEBUG: Importing file: WitnessApi
DEBUG: Importing file: VchaClusterActiveGetRequestBody
DEBUG: Importing file: VchaClusterActiveSpec
DEBUG: Importing file: VchaClusterDeploySpec
DEBUG: Importing file: VchaClusterFailoverTaskRequestBody
DEBUG: Importing file: VchaClusterGetRequestBody
DEBUG: Importing file: VchaClusterModeSetTaskRequestBody
DEBUG: Importing file: VchaClusterNodeVmInfo
DEBUG: Importing file: VchaClusterPassiveCheckSpec
DEBUG: Importing file: VchaClusterPassiveRedeploySpec
DEBUG: Importing file: VchaClusterPassiveSpec
DEBUG: Importing file: VchaClusterUndeploySpec
DEBUG: Importing file: VchaClusterVmInfo
DEBUG: Importing file: VchaClusterWitnessCheckSpec
DEBUG: Importing file: VchaClusterWitnessRedeploySpec
DEBUG: Importing file: VchaClusterWitnessSpec
DEBUG: Importing file: VchaConnectionSpec
DEBUG: Importing file: VchaCredentialsSpec
DEBUG: Importing file: VchaDiskSpec
DEBUG: Importing file: VchaIpSpec
DEBUG: Importing file: VchaIpv4Spec
DEBUG: Importing file: VchaIpv6Spec
DEBUG: Importing file: VchaPlacementSpec
DEBUG: Importing file: BootApi
DEBUG: Importing file: CdromApi
DEBUG: Importing file: ComplianceApi
DEBUG: Importing file: CpuApi
DEBUG: Importing file: CustomizationApi
DEBUG: Importing file: DataSetsApi
DEBUG: Importing file: DeviceApi
DEBUG: Importing file: DirectoriesApi
DEBUG: Importing file: DiskApi
DEBUG: Importing file: EntriesApi
DEBUG: Importing file: EnvironmentApi
DEBUG: Importing file: EthernetApi
DEBUG: Importing file: FilesApi
DEBUG: Importing file: FloppyApi
DEBUG: Importing file: HardwareApi
DEBUG: Importing file: IdentityApi
DEBUG: Importing file: InstallerApi
DEBUG: Importing file: InterfacesApi
DEBUG: Importing file: LibraryItemApi
DEBUG: Importing file: LocalFilesystemApi
DEBUG: Importing file: MemoryApi
DEBUG: Importing file: NetworkingApi
DEBUG: Importing file: NvmeApi
DEBUG: Importing file: OperationsApi
DEBUG: Importing file: ParallelApi
DEBUG: Importing file: PoliciesApi
DEBUG: Importing file: PolicyApi
DEBUG: Importing file: PowerApi
DEBUG: Importing file: ProcessesApi
DEBUG: Importing file: RoutesApi
DEBUG: Importing file: SataApi
DEBUG: Importing file: ScsiApi
DEBUG: Importing file: SerialApi
DEBUG: Importing file: TicketsApi
DEBUG: Importing file: ToolsApi
DEBUG: Importing file: TransfersApi
DEBUG: Importing file: GuestAdapterMapping
DEBUG: Importing file: GuestCloudConfiguration
DEBUG: Importing file: GuestCloudinitConfiguration
DEBUG: Importing file: GuestConfigurationSpec
DEBUG: Importing file: GuestCustomizationSpec
DEBUG: Importing file: GuestDomain
DEBUG: Importing file: GuestGlobalDNSSettings
DEBUG: Importing file: GuestGuiUnattended
DEBUG: Importing file: GuestHostnameGenerator
DEBUG: Importing file: GuestIPSettings
DEBUG: Importing file: GuestIpv4
DEBUG: Importing file: GuestIpv6
DEBUG: Importing file: GuestIpv6Address
DEBUG: Importing file: GuestLinuxConfiguration
DEBUG: Importing file: GuestUserData
DEBUG: Importing file: GuestWindowsConfiguration
DEBUG: Importing file: GuestWindowsNetworkAdapterSettings
DEBUG: Importing file: GuestWindowsSysprep
DEBUG: Importing file: VmConsoleTicketsCreateSpec
DEBUG: Importing file: VmDataSetsCreateSpec
DEBUG: Importing file: VmDataSetsUpdateSpec
DEBUG: Importing file: VmGuestCredentials
DEBUG: Importing file: VmGuestCustomizationSetSpec
DEBUG: Importing file: VmGuestEnvironmentGetRequestBody
DEBUG: Importing file: VmGuestEnvironmentListRequestBody
DEBUG: Importing file: VmGuestFilesystemDirectoriesCreateRequestBody
DEBUG: Importing file: VmGuestFilesystemDirectoriesCreateTemporaryRequestBody
DEBUG: Importing file: VmGuestFilesystemDirectoriesDeleteRequestBody
DEBUG: Importing file: VmGuestFilesystemDirectoriesMoveRequestBody
DEBUG: Importing file: VmGuestFilesystemFilesCreateTemporaryRequestBody
DEBUG: Importing file: VmGuestFilesystemFilesDeleteRequestBody
DEBUG: Importing file: VmGuestFilesystemFilesFileAttributesUpdateSpec
DEBUG: Importing file: VmGuestFilesystemFilesFilterSpec
DEBUG: Importing file: VmGuestFilesystemFilesGetRequestBody
DEBUG: Importing file: VmGuestFilesystemFilesIterationSpec
DEBUG: Importing file: VmGuestFilesystemFilesListRequestBody
DEBUG: Importing file: VmGuestFilesystemFilesMoveRequestBody
DEBUG: Importing file: VmGuestFilesystemFilesPosixFileAttributesUpdateSpec
DEBUG: Importing file: VmGuestFilesystemFilesUpdateRequestBody
DEBUG: Importing file: VmGuestFilesystemFilesWindowsFileAttributesUpdateSpec
DEBUG: Importing file: VmGuestFilesystemTransfersCreateRequestBody
DEBUG: Importing file: VmGuestFilesystemTransfersCreateSpec
DEBUG: Importing file: VmGuestFilesystemTransfersFileCreationAttributes
DEBUG: Importing file: VmGuestFilesystemTransfersPosixFileAttributesCreateSpec
DEBUG: Importing file: VmGuestFilesystemTransfersWindowsFileAttributesCreateSpec
DEBUG: Importing file: VmGuestProcessesCreateRequestBody
DEBUG: Importing file: VmGuestProcessesCreateSpec
DEBUG: Importing file: VmGuestProcessesDeleteRequestBody
DEBUG: Importing file: VmGuestProcessesGetRequestBody
DEBUG: Importing file: VmGuestProcessesListRequestBody
DEBUG: Importing file: VmHardwareAdapterNvmeCreateSpec
DEBUG: Importing file: VmHardwareAdapterSataCreateSpec
DEBUG: Importing file: VmHardwareAdapterScsiCreateSpec
DEBUG: Importing file: VmHardwareAdapterScsiUpdateSpec
DEBUG: Importing file: VmHardwareBootDeviceEntry
DEBUG: Importing file: VmHardwareBootDeviceSetRequestBody
DEBUG: Importing file: VmHardwareBootUpdateSpec
DEBUG: Importing file: VmHardwareCdromBackingSpec
DEBUG: Importing file: VmHardwareCdromCreateSpec
DEBUG: Importing file: VmHardwareCdromUpdateSpec
DEBUG: Importing file: VmHardwareCpuUpdateSpec
DEBUG: Importing file: VmHardwareDiskBackingSpec
DEBUG: Importing file: VmHardwareDiskCreateSpec
DEBUG: Importing file: VmHardwareDiskStoragePolicySpec
DEBUG: Importing file: VmHardwareDiskUpdateSpec
DEBUG: Importing file: VmHardwareDiskVmdkCreateSpec
DEBUG: Importing file: VmHardwareEthernetBackingSpec
DEBUG: Importing file: VmHardwareEthernetCreateSpec
DEBUG: Importing file: VmHardwareEthernetUpdateSpec
DEBUG: Importing file: VmHardwareFloppyBackingSpec
DEBUG: Importing file: VmHardwareFloppyCreateSpec
DEBUG: Importing file: VmHardwareFloppyUpdateSpec
DEBUG: Importing file: VmHardwareIdeAddressSpec
DEBUG: Importing file: VmHardwareMemoryUpdateSpec
DEBUG: Importing file: VmHardwareNvmeAddressSpec
DEBUG: Importing file: VmHardwareParallelBackingSpec
DEBUG: Importing file: VmHardwareParallelCreateSpec
DEBUG: Importing file: VmHardwareParallelUpdateSpec
DEBUG: Importing file: VmHardwareSataAddressSpec
DEBUG: Importing file: VmHardwareScsiAddressSpec
DEBUG: Importing file: VmHardwareSerialBackingSpec
DEBUG: Importing file: VmHardwareSerialCreateSpec
DEBUG: Importing file: VmHardwareSerialUpdateSpec
DEBUG: Importing file: VmHardwareUpdateSpec
DEBUG: Importing file: VmHardwareUpgradeRequestBody
DEBUG: Importing file: VmStoragePolicyComplianceCheckSpec
DEBUG: Importing file: VmStoragePolicyDiskPolicySpec
DEBUG: Importing file: VmStoragePolicyUpdateSpec
DEBUG: Importing file: VmStoragePolicyVmHomePolicySpec
DEBUG: Importing file: VmToolsUpdateSpec
DEBUG: Importing file: VmToolsUpgradeRequestBody
DEBUG: Importing file: CheckOutsApi
DEBUG: Importing file: LibraryItemsApi
DEBUG: Importing file: VersionsApi
DEBUG: Importing file: VmTemplateLibraryItemsCheckOutsCheckInSpec
DEBUG: Importing file: VmTemplateLibraryItemsCheckOutsCheckOutSpec
DEBUG: Importing file: VmTemplateLibraryItemsCheckOutsPlacementSpec
DEBUG: Importing file: VmTemplateLibraryItemsCpuUpdateSpec
DEBUG: Importing file: VmTemplateLibraryItemsCreatePlacementSpec
DEBUG: Importing file: VmTemplateLibraryItemsCreateSpec
DEBUG: Importing file: VmTemplateLibraryItemsCreateSpecDiskStorage
DEBUG: Importing file: VmTemplateLibraryItemsCreateSpecDiskStoragePolicy
DEBUG: Importing file: VmTemplateLibraryItemsCreateSpecVmHomeStorage
DEBUG: Importing file: VmTemplateLibraryItemsCreateSpecVmHomeStoragePolicy
DEBUG: Importing file: VmTemplateLibraryItemsDeployPlacementSpec
DEBUG: Importing file: VmTemplateLibraryItemsDeploySpec
DEBUG: Importing file: VmTemplateLibraryItemsDeploySpecDiskStorage
DEBUG: Importing file: VmTemplateLibraryItemsDeploySpecDiskStoragePolicy
DEBUG: Importing file: VmTemplateLibraryItemsDeploySpecVmHomeStorage
DEBUG: Importing file: VmTemplateLibraryItemsDeploySpecVmHomeStoragePolicy
DEBUG: Importing file: VmTemplateLibraryItemsDiskUpdateSpec
DEBUG: Importing file: VmTemplateLibraryItemsEthernetUpdateSpec
DEBUG: Importing file: VmTemplateLibraryItemsGuestCustomizationSpec
DEBUG: Importing file: VmTemplateLibraryItemsHardwareCustomizationSpec
DEBUG: Importing file: VmTemplateLibraryItemsMemoryUpdateSpec
DEBUG: Importing file: VmTemplateLibraryItemsVersionsRollbackSpec
DEBUG: Importing file: AcqSpecsApi
DEBUG: Importing file: CounterMetadataApi
DEBUG: Importing file: CountersApi
DEBUG: Importing file: CounterSetsApi
DEBUG: Importing file: DataApi
DEBUG: Importing file: MetricsApi
DEBUG: Importing file: ProvidersApi
DEBUG: Importing file: ResourceAddressesApi
DEBUG: Importing file: ResourceAddressSchemasApi
DEBUG: Importing file: ResourceTypesApi
DEBUG: Importing file: AcqSpecsCounterSpec
DEBUG: Importing file: AcqSpecsCreateSpec
DEBUG: Importing file: AcqSpecsUpdateSpec
DEBUG: Importing file: CidMid
DEBUG: Importing file: RsrcId
VERBOSE: Populating RepositorySourceLocation property for module VMware.PowerCli.
VERBOSE: Loading module from path 'C:\Users\ZZZ\Documents\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCLI.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Users\ZZZ\Documents\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCLI.ps1'.
          Welcome to VMware PowerCLI!

Log in to a vCenter Server or ESX host:              Connect-VIServer
To find out what commands are available, type:       Get-VICommand
To show searchable help for all PowerCLI commands:   Get-PowerCLIHelp
Once you've connected, display all virtual machines: Get-VM
If you need more help, visit the PowerCLI community: Get-PowerCLICommunity

       Copyright (C) VMware, Inc. All rights reserved.


VERBOSE: Exporting variable 'productName'.
VERBOSE: Importing variable 'productName'.
PS C:\Users\ZZZ> Stop-Transcript
Stop-Transcript : An error occurred stopping transcription: The host is not currently transcribing.
At line:1 char:1
+ Stop-Transcript
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Stop-Transcript], PSInvalidOperationException
    + FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.StopTranscriptCommand

 

 

 

I'm not sure if this in anyway helps narrowing it down the issue. But since it is only reproducible with PowerCli, I'm guessing this isn't a Microsoft issue.

Who/How can we get VMware to take this issue serious and get it fixed?

[LucD]

Did you see the suggestion to try with PSv7 earlier in this thread?
Does that make a difference?

[MichaelRyom]

I did, the problem is PS7 is not feature compatible with PS5, so anything Windows specific, like encryption, does not work.

[MichaelRyom]

Just to add the output from console around the point where Start-Transcript seems to fail:

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

PS C:\Users\Administrator> $DebugPreference = "Continue"
PS C:\Users\Administrator> $VerbosePreference = "Continue"
PS C:\Users\Administrator> Start-Transcript
Transcript started, output file is C:\Users\Administrator\Documents\PowerShell_transcript.ARK.FGUYhsln.20230302123120.txt
PS C:\Users\Administrator> [Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.17763.0 Microsoft Windows NT 10.0.17763.0


PS C:\Users\Administrator> $PSVersiontable

Name                           Value
----                           -----
PSVersion                      5.1.17763.3770
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17763.3770
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


PS C:\Users\Administrator> Import-Module VMware.PowerCli -Verbose -Debug
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCli.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
WARNING: Please consider joining the VMware Customer Experience Improvement Program, so you can help us make PowerCLI a better product. You can join using the following command:

Set-PowerCLIConfiguration -Scope User -ParticipateInCEIP $true

VMware's Customer Experience Improvement Program ("CEIP") provides VMware with information that enables VMware to improve its products and services, to fix problems, and to advise you on how best to deploy and use our products.  As part of the CEIP, VMware collects
technical information about your organization’s use of VMware products and services on a regular basis in association with your organization’s VMware license key(s).  This information does not personally identify any individual.

For more details: type "help about_ceip" to see the related help article.

To disable this warning and set your preference use the following command and restart PowerShell:
Set-PowerCLIConfiguration -Scope User -ParticipateInCEIP $true or $false.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Exporting variable 'CustomInitScriptName'.
VERBOSE: Exporting variable 'currentDir'.
VERBOSE: Exporting variable 'CustomInitScript'.
VERBOSE: Exporting variable 'productShortName'.
VERBOSE: Exporting variable 'existsCustomInitScript'.
VERBOSE: Exporting variable 'message'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Importing variable 'currentDir'.
VERBOSE: Importing variable 'CustomInitScript'.
VERBOSE: Importing variable 'CustomInitScriptName'.
VERBOSE: Importing variable 'existsCustomInitScript'.
VERBOSE: Importing variable 'message'.
VERBOSE: Importing variable 'productShortName'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Common.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psm1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Common.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\ICSharpCode.SharpZipLib.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\ICSharpCode.SharpZipLib.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\Newtonsoft.Json.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\Newtonsoft.Json.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Ls2.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Ls2.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Sts.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Sts.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.WsTrust.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.WsTrust.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Util.Sspi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Util.Sspi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Http.Handlers.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Http.Handlers.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.SsoAuthentication.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.SsoAuthentication.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Commands.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Commands.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Util.OAuth2.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Util.OAuth2.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Wcf.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.Wcf.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\JsonSubTypes.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\JsonSubTypes.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.OpenApi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Binding.OpenApi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Sdk.OpenApi.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.Sdk.OpenApi.dll'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.Format.ps1xml'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.ps1'.
PS C:\Users\Administrator> Stop-Transcript^C
PS C:\Users\Administrator> ^C
PS C:\Users\Administrator> ^C
PS C:\Users\Administrator> Stop-Transcript
Stop-Transcript : An error occurred stopping transcription: The host is not currently transcribing.
At line:1 char:1
+ Stop-Transcript
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Stop-Transcript], PSInvalidOperationException
    + FullyQualifiedErrorId : InvalidOperation,Microsoft.PowerShell.Commands.StopTranscriptCommand

PS C:\Users\Administrator>

 

In the other transcripts "Importing function 'Get-Version'." Is the last output before transcripting fails - Running the commandlet Get-PSVersion does not seem to break anything, so whatever the next line means seems likely to be a clue.

VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Common.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psm1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Common.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\VMware.VimAutomation.Common.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Common\13.0.0.20797081\net472\VMware.VimAutomation.Common.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.

 

[LucD]

That same error message is also reported for other modules, like the Az(ure) and MicrosoftTeams module.
See for example #Issue12065

Can you check which .NET version you have installed?

[MichaelRyom]

.NET 528049 = 4.8 on server 3

.NET 461814 = 4.7.1 on server 1 and Server 2

 

I will have a look at the #Issue12065

[LucD]

The Compatibility Matrixes for VMware PowerCLI 13.0.0 specify 4.7.2 as a prereq.

[MichaelRyom]

I get that and I will upgrade Server1 as it is non production server. But Server3 is a higher version and still has this problem and the problem was also on older versions of PowerCli 12.6/12.7 as I recall from the original post.

[LucD]

The .NET 4.7.2 requirement has been there since PowerCLI 12.0

I'm not saying that the .NET version is the cause of the transcript issue you are seeing, but it apparently is not unique to PowerCLI.
I would at least make to meet all the requirements

[MichaelRyom]

Sorry for the confusion but according to this https://learn.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed

All server are on 4.7.2 and not 4.7 as previously stated

.NET Framework 4.7.2 	
On Windows 10 April 2018 Update and Windows Server, version 1803: 461808
On all Windows operating systems other than Windows 10 April 2018 Update and Windows Server, version 1803: 461814

 

[MichaelRyom]

I find it interesting that PowerCli seems to be loaded differently between PS5 and PS7

I have attached the PS7 transcript

Attachment(s)

Transcript.txt   667 KB 1 version

[LucD]

Besides using the correct directories (netcorexxx instead of netyyy) for PSv7, what differences do you see?

[MichaelRyom]

Just t first few lines differs nothing else

PS5:

VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCli.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psd1'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Sdk.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\VMware.VimAutomation.Sdk.psm1'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.psd1'.
VERBOSE: Cannot verify the Microsoft .NET Framework version 4.7.2 because it is not included in the list of permitted versions.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\log4net.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Ceip.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.Security.CredentialStore.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Impl.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Interop.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Types.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.ps1'.
WARNING: Please consider joining the VMware Customer Experience Improvement Program, so you can help us make PowerCLI a better product. You can join using the following command:

Set-PowerCLIConfiguration -Scope User -ParticipateInCEIP $true

VMware's Customer Experience Improvement Program ("CEIP") provides VMware with information that enables VMware to improve its products and services, to fix problems, and to advise you on how best to deploy and use our products.  As part of the CEIP, VMware collects
technical information about your organization’s use of VMware products and services on a regular basis in association with your organization’s VMware license key(s).  This information does not personally identify any individual.

For more details: type "help about_ceip" to see the related help article.

To disable this warning and set your preference use the following command and restart PowerShell:
Set-PowerCLIConfiguration -Scope User -ParticipateInCEIP $true or $false.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Sdk\13.0.0.20791442\net472\VMware.VimAutomation.Sdk.Util10Ps.dll'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Exporting variable 'CustomInitScriptName'.
VERBOSE: Exporting variable 'currentDir'.
VERBOSE: Exporting variable 'CustomInitScript'.
VERBOSE: Exporting variable 'productShortName'.
VERBOSE: Exporting variable 'existsCustomInitScript'.
VERBOSE: Exporting variable 'message'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Importing variable 'currentDir'.
VERBOSE: Importing variable 'CustomInitScript'.
VERBOSE: Importing variable 'CustomInitScriptName'.
VERBOSE: Importing variable 'existsCustomInitScript'.
VERBOSE: Importing variable 'message'.
VERBOSE: Importing variable 'productShortName'.
VERBOSE: Exporting function 'EnableParameterCompleters'.
VERBOSE: Exporting function 'Get-InstallPath'.
VERBOSE: Exporting function 'Get-PSVersion'.
VERBOSE: Exporting cmdlet 'Get-ErrorReport'.
VERBOSE: Importing cmdlet 'Get-ErrorReport'.
VERBOSE: Importing function 'EnableParameterCompleters'.
VERBOSE: Importing function 'Get-InstallPath'.
VERBOSE: Importing function 'Get-PSVersion'.
VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Common.

PS7:

VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.PowerCli\13.0.0.20829139\VMware.PowerCli.psd1'.

VERBOSE: Exporting function 'EnableParameterCompleters'.

VERBOSE: Exporting function 'Get-InstallPath'.

VERBOSE: Exporting function 'Get-PSVersion'.

VERBOSE: Exporting cmdlet 'Get-ErrorReport'.

VERBOSE: Importing cmdlet 'Get-ErrorReport'.

VERBOSE: Importing function 'EnableParameterCompleters'.

VERBOSE: Importing function 'Get-InstallPath'.

VERBOSE: Importing function 'Get-PSVersion'.

VERBOSE: Exporting cmdlet 'Get-PowerCLIContext'.

VERBOSE: Exporting cmdlet 'Get-Task'.

VERBOSE: Exporting cmdlet 'New-OAuthSecurityContext'.

VERBOSE: Exporting cmdlet 'Stop-Task'.

VERBOSE: Exporting cmdlet 'Use-PowerCLIContext'.

VERBOSE: Exporting cmdlet 'Wait-Task'.

VERBOSE: Importing cmdlet 'Get-PowerCLIContext'.

VERBOSE: Importing cmdlet 'Get-Task'.

VERBOSE: Importing cmdlet 'New-OAuthSecurityContext'.

VERBOSE: Importing cmdlet 'Stop-Task'.

VERBOSE: Importing cmdlet 'Use-PowerCLIContext'.

VERBOSE: Importing cmdlet 'Wait-Task'.

VERBOSE: Exporting cmdlet 'Connect-CisServer'.

VERBOSE: Exporting cmdlet 'Disconnect-CisServer'.

VERBOSE: Exporting cmdlet 'Get-CisService'.

VERBOSE: Importing cmdlet 'Connect-CisServer'.

VERBOSE: Importing cmdlet 'Disconnect-CisServer'.

VERBOSE: Importing cmdlet 'Get-CisService'.

VERBOSE: Populating RepositorySourceLocation property for module VMware.VimAutomation.Core.

VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\VMware.VimAutomation.Core.psm1'.

VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.Core.psd1'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.ViCore.Interop.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.ViCore.Cmdlets.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.ViCore.Impl.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.ViCore.Types.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.ViCore.Util10.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.ViCore.Util10Ps.dll'.

VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.Format.ps1xml'.

VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.Core.ps1'.

VERBOSE: Dot-sourcing the script file 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.Core.ps1'.

VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\VMware.VimAutomation.Core\13.0.0.20797821\netcoreapp2.0\VMware.VimAutomation.ViCore.Cmdlets.dll'

 

[Tocano]

Just wanted to clarify that we are able to avoid the premature Stop-Transcript behavior by only pre-importing:

> Import-Module VMware.VimAutomation.Common

Now, that doesn't mean that other packages don't have the same issue. However, we don't use a great many of the various packages. For example, we do not use anything in the Horizon, NSX, or Cloud packages.

Your mileage may vary, but you may be able to avoid the 4+ minute module loading by identifying the specific packages that you need and seeing if they need to be pre-loaded or not. 

Again, this is just a workaround, not a real solution which I think still needs investigated and identified.

[LucD]

I'm still convinced that doing these explicit Import-Module lines (be it for VMware.PowerCLI or VMware.VimAutomation.Core or any other module) is a bad coding practice.
Unless you want to load a specific version of a module of which you have multiple versions installed or for a module that is not located in a folder in $PSModulePath.

Module Auto-Loading, introduced in PSv3, loads the correct module at the time you use the 1st cmdlet from a module.
PS builds that module-cmdlet cache in any case, so why not use it?

[Tocano]

I completely agree. I would love to remove this from our profile.ps1 file. However, as the only workaround we've found to prevent premature transcript termination, it's the only way I've come up with to ensure that logs continue to populate properly until this issue is actually solved.

[LucD]

Something completely different, did you already try replacing the Write-Host in the original code with a Write-Output?

Start-Transcript -Path "C:\temp\test.log" -Append -Force
import-module VMware.PowerCli -force
Write-Output "Hallo World!"
Stop-Transcript

[MichaelRyom]

You script fails was well, but I don't write any output in the latest way I did it. Only to console and only before Import of module, given verbose/debug there is plenty of output to console for start-transcript to pick up on

$DebugPreference = "Continue"
$VerbosePreference = "Continue"
Start-Transcript
[Environment]::OSVersion
$PSVersiontable
Import-Module VMware.PowerCli -Verbose -Debug
Stop-Transcript

 

[Tocano]

While it doesn't fix the issue, we have found a workaround by adding the Import-Module VMware.PowerCLI line to the PS Profile.

This delays the kickoff of scripts a bit and takes more memory than auto-loading only the portions needed by the script, but it allows whatever the piece(s) that stop the transcript to load early, then when the script starts a transcript, the module is already loaded and so doesn't execute whatever it is that stops it.

Again, not ideal, but worked sufficiently for our case. However, I do still think this is a problem that needs to be investigated and resolved.

[MichaelRyom]

I like the idea. I will try to test it.

1. To see if it works with schedule tasks and service accounts

2. The 4 min+ load time of PowerCli, I don't care about here, but that's the main reason why I don't load at start up to begin with. It's a real productivity killer, debugging like that