-
Notifications
You must be signed in to change notification settings - Fork 36
Open
Description
Hello,
i use following script:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
$clientId="<clientid>"
$clientSecret="<clientsecret>"
$tenantId="<tenant>"
Import-Module StoreBroker
Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope Process
$css = ConvertTo-SecureString -String $ClientSecret -AsPlainText -force -Debug
$cred = New-Object System.Management.Automation.PSCredential $ClientId, $css
Set-StoreBrokerAuthentication -TenantId $TenantId -Credential $cred -Debug
Get-Applications -GetAll | Format-Applications -Verbose
- When using this Script on Windows 11 client machine, everything works fine.
- When using this Script on Windows Server 2016, i get the following message:
Be sure to check that your client id/secret are valid.
The underlying connection was closed: An unexpected error occurred on a send.
At C:\Program Files\WindowsPowerShell\Modules\StoreBroker\1.21.2\StoreBroker\StoreIngestionApi.psm1:556 char:9
+ Write-Log -Message $newLineOutput -Level Error
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
+ FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Write-Log
Be sure to check that your client id/secret are valid.
The underlying connection was closed: An unexpected error occurred on a send.
At C:\Program Files\WindowsPowerShell\Modules\StoreBroker\1.21.2\StoreBroker\StoreIngestionApi.psm1:557 char:9
+ throw $newLineOutput
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : OperationStopped: (Be sure to chec...rred on a send.:String) [], RuntimeException
+ FullyQualifiedErrorId : Be sure to check that your client id/secret are valid.
The underlying connection was closed: An unexpected error occurred on a send.
Do you have an idea?
best regards
Volkhard
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels