HELP - Successfully runs the Enable SSO PowerShell script via Pulseway RMM, but does not execute on the endpoint

[Jitesh Modashia]

HI All,

I am trying to enable SSO on my endpoint running Windows 10 x64 by running the below PowerShell Script through Pulseway RMM, however the Task runs successfully, but does not execute on the computer and doesn't give me any errors. I have however ran the script on Windows PowerShell ISE locally on the computer and it executes without any problems. Please can someone help me understand why this script will not execute on the endpoint via Pulseway RMM. i have however ran other scripts on my test machine and they work, but for some reason this one doesn't seem to want to execute.

PowerShell Script:

# Set variables to indicate value and key to set
$RegistryPath = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains\microsoftazuread-sso.com\autologon'
$Name         = 'https'
$Value        = '1'
$Path         = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZoneMap\Domains\microsoftazuread-sso.com\autologon'

# Create the keys if it does not exist
If (-NOT (Test-Path $RegistryPath)) {
  New-Item -Path "$Path" -Force | Out-Null
}
# Now set the value
New-ItemProperty -Path $RegistryPath -Name $Name -Value $Value -PropertyType DWORD -Force

 

 

[Tim]

Hi Jitesh,

Your script is writing to "Current Users" but the Pulseway agent runs as a local system account. When you test via Powershell ISE, you're running it under a specific user account. When executing via Pulseway, the agent is executing it (as Local System, not a user account), which means, if the script runs successfully, you'll likely see your keys put into the physical registry location for Current Users, which is in "Computer\HKEY_USERS\.DEFAULT\..."

[Peyton Young]

On 8/15/2022 at 10:11 AM, Tim said:

Hi Jitesh,

Your script is writing to "Current Users" but the Pulseway agent runs as a local system account. When you test via Powershell ISE, you're running it under a specific user account. When executing via Pulseway, the agent is executing it (as Local System, not a user account), which means, if the script runs successfully, you'll likely see your keys put into the physical registry location for Current Users, which is in "Computer\HKEY_USERS\.DEFAULT\..."

Tim,

 

You are absolutely correct. If I wanted to deploy a similar PowerShell script as a different user (rather than the Local system), is that possible? Or is the only option to manually remote into each desktop and use PowerShell ISE?

[Sanjeev]

On 8/15/2022 at 7:41 PM, Tim said:

Hi Jitesh,

Your script is writing to "Current Users" but the Pulseway agent runs as a local system account. When you test via Powershell ISE, you're running it under a specific user account. When executing via Pulseway, the agent is executing it (as Local System, not a user account), which means, if the script runs successfully, you'll likely see your keys put into the physical registry location for Current Users, which is in "Computer\HKEY_USERS\.DEFAULT\..."

It is vital to comprehend the difference in execution context between testing in Powershell ISE and using the Pulseway agent. While testing with Powershell ISE is done under a specific user account, Pulseway runs scripts as Local System. This variation may cause keys to be written to the physical registry location for Current Users after successful execution.sso login

[ssoidloginportalrajasthan]

Your script writes to "Current Users," but the Pulseway agent runs as a local system account, not a specific user. When testing in PowerShell ISE, it's run under a user account, which is why the script works differently when executed via Pulseway. If the script runs successfully through Pulseway, the registry keys will be placed in the "Computer\HKEY_USERS\.DEFAULT\..." location instead of the intended user-specific location. For more https://ssoidloginportal.in/

Edited July 25 by ssoidloginportalrajasthan
spelling mistake