Remote Session

3 Topics

Troubleshooting UPN Authentication Issues in Remote Server Gateway
Hello everyone, I'm a system administrator currently facing an issue with UPN authentication on our Remote Server Gateway. I'm seeking advice or suggestions to resolve this problem. Here's a brief overview of the situation: Internally (at work), authentication using sAMAccountName and Kerberos works with no issues. However, with our Remote Server Gateway, UPN authentication consistently fails, while sAMAccountName works. Steps Taken: Adjusted user accounts, including adding them to global and forest admin groups. Checked DNS configurations, which seem to be correct. Reviewed group policies and found no restrictive settings affecting UPN authentication. Encountered some general event errors related to the failed connections, but they don't provide usable information. My concern is to understand how it could work. Is it possible that Kerberos or NTLM configurations are affecting UPN authentication on the Remote Server Gateway? If so, how can these settings be diagnosed and adjusted? Has anyone faced similar UPN authentication issues with Remote Server Gateways, but working with sAMAccount? Any solutions or advice would be valuable
FelData
Feb 07, 2024 Place Windows Server for IT Pro
1.4KViews
0likes
0Comments
Running an exe install remotely
I want to have a script run through an OU and install an exe on each server but I'm having difficulty putting everything together. What am I doing wrong? Is there a better way to script this? This is what I currently have. $cmd = '\\server\share\install.exe' $parm1 = '/S /Token=' $parm2 = 'Test$' foreach($server in Get-ADComputer -Filter * -SearchBase "OU=Servers,DC=Domain,DC=Local") { Invoke-Command -ComputerName $server $cmd $parm1"'"$parm2"'" } This is the error I'm currently getting. Invoke-Command : A positional parameter cannot be found that accepts argument '/S /TOKEN='Test$''. At C:\Scripts\Nagios-Push.ps1:7 char:9 + Invoke-Command -ComputerName $server $cmd $parm1"'"$parm2"'" + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Invoke-Command], ParameterBindingException + FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.InvokeCommandCommand
Baron164
Aug 09, 2022 Place Windows PowerShell
10KViews
0likes
1Comment
Azure Automation: issues connecting to security and compliance center in remote session
I'm at a loss here. I'm trying to use a Azure Automation PowerShell runbook to connect to the Security and Compliance Center. Specifically I am looking to use the https://docs.microsoft.com/en-us/powershell/module/exchange/policy-and-compliance-retention/get-retentioncompliancepolicy?view=exchange-ps and https://docs.microsoft.com/en-us/powershell/module/exchange/policy-and-compliance-retention/set-retentioncompliancepolicy?view=exchange-ps commands. I've tried a number of different modules to attempt to connect but none seem to work. I have code that works locally, but when put into a runbook and load the same module there, it won't connect properly. Instead it redirects and seems to loop on the connect and import step. When I finally got it to appear to connect and import once (not loop), it does not recognize the Get-RetentionCompliancePolicy command and I can't find it in a Get-Commands call. Any tips on how to get this to work? below is the code I'm using to connect and import. $cred = Get-AutomationPSCredential -Name "Admin" $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://ps.compliance.protection.outlook.com/powershell-liveid/ -Credential $cred -Authentication Basic -AllowRedirection Import-PSSession $Session -DisableNameChecking -AllowClobber | Out-Null Get-RetentionCompliancePolicy Get-PSSession | Remove-PSSession
Solved
thinkhaven
Apr 01, 2020 Place Azure
2.6KViews
0likes
1Comment