powershell-remoting

I'm trying to execute a powershell script located at a remote machine using the below command and it works great invoke-command (powershell c:\install\install.ps1) -computername box1 -credential (get-credential) The above script in-turn copies files from a network share (using robocopy) - It fails complaining the location doesn't exist. Found out it was due to permission issue. It works when I explicitly mentioned in the script to use the following credentials for the share net use \share1\files password /user:username Is there a way to pass in the same credentials used to run the script to be

I'm using command1.ps1 script to install Azure Custom Script Extension on the target VM and execute command2.ps1. command2.ps1 is supposed to run a script (that is inside ScriptBlock) as domain administrator (hence -Credential $Credentials ). When I run command2.ps1 manually and input $domainAdminName and $domainAdminPassword it works, but when running it through command1.ps1 it doesn't work. Maybe the problem is cause by Azure Custom Script Extension running command2.ps1 as System account? Please, help me make the script work. command1.ps1: param ( [Parameter(Mandatory)] [String]

I'm trying to add multiple csv-imported lists to a remote executed PS script. It works fine when I pass only one list using the following command: Invoke-Command -filepath $createSAPSPath -ConnectionUri $uri -Credential $credential -ArgumentList (,$accountsList) What would be the correct syntax for multiple list objects? I've tried: Invoke-Command -filepath $createSAPSPath -ConnectionUri $uri -Credential $credential -ArgumentList (,$accountsList),(,$groupsList) But it doesn't seem to work... Thanks, Glenn You have to realize why you need unary comma in the first situation, to understand why

For a legacy application, I need to create a registry key with a name in the format c:/foo/bar/baz . (Note: forward slashes, not backslashes.) To be clear: that is a single key's name, with forward slashes, that otherwise looks like a Windows path. Because I need to script this against lots of servers, PowerShell seems like a great option. The problem is that I cannot figure out how to create a key in that format via PowerShell. New-Item -Path HKLM:\SOFTWARE\Some\Key -Name 'c:/foo/bar/baz' errors out with PowerShell thinking I'm using / as a path separator and failing to find the path HKLM:

This self-answered question, which focuses on Windows [1] , addresses the following aspects: Now that there are two PowerShell editions - the legacy, Windows-only Windows PowerShell and the cross-platform PowerShell Core , both may be installed on a given Windows machine: How can I tell which PowerShell edition will execute remote commands , such as via Invoke-Command -ComputerName ? How can I target a specific edition , both ad hoc and persistently , through configuration? Note: For an edition to be targetable via remoting on a given machine, it must be set up for remoting : Only Windows

I have this code in which I load a snapin (from MS Dynamics NAV in this case): using (Runspace runspace = RunspaceFactory.CreateRunspace()) { runspace.Open(); using (var ps = PowerShell.Create()) { ps.Runspace = runspace; ps.AddScript("Add-PSSnapin Microsoft.Dynamics.Nav.Management") .AddScript("Get-NAVServerInstance"); //This does not work. Says unknown cmdlet Get-NAVServerInstance //ps.AddCommand("Add-PSSnapin").AddArgument("Microsoft.Dynamics.Nav.Management") // .AddCommand("Get-NAVServerInstance"); var output = ps.Invoke(); } } This code works when I use the AddScript method as shown in