Unable to Set-IntersightConfiguration in the same session with PowerCLI loaded

[wgjhstt247]

Describe the bug
When the latest version of Intersight.powershell is loaded in the same powershell session as PowerCLI modules, Set-IntersightConfiguration fails. Loading both modules in the same session is a requirement for our company. I don't have administrative rights to perform local powershell remoting.

To Reproduce
Run this (replacing <config_here> with the real configuration)

Import-Module VMware.Vim
Import-Module Intersight.Powershell
$config = @{ <config_here> }
Set-IntersightConfiguration @config

Version used
See description

Expected behavior
I expect Set-IntersightConfiguration to succeed.

[Ghufz]

The issue is caused by a DLL conflict because the PowerCLI and Intersight.PowerShell modules rely on the same dependent assembly but use different versions.

As workaround I would recommend to use the either Intersight.PowerShell cmdlet or PowerCLI cmdlets in different thread.

$script = { 
Import-Module Intersight.PowerShell

# Configure Intersight API signing
$ApiParams = @{                       
    BasePath          = "intersight.com"
    ApiKeyId          = "ABCDXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX"
    ApiKeyFilePath    =  "C:\Secrect.key"
    HttpSigningHeader = @("(request-target)", "Host", "Date", "Digest")
}
Set-IntersightConfiguration @ApiParams

 }

[wgjhstt247]

I want to load both modules in the session without threads. Can Cisco work with Broadcom to resolve this conflict? Can the code be updated to support this?

[tbrock47]

I'd love to see a fix or functional workaround for this as well as these are my two most used modules.