PowerShell Scripts, Tips, Expert Advices, Forums, and Resources

image rotation

Welcome to PowerShell.com, the educational and community site for Windows PowerShell People. Get a quick overview.

Latest Scripts

10-19-2014 - Get-RawPEHeader
10-16-2014 - Get-CPUInfo
10-16-2014 - Get-MemoryStatus

Latest Announcements/Events

10-15-2014 - Class Dismissed
10-12-2014 - The Case for PowerShell
09-26-2014 - PowerShell Magazine completes 3 years!

As a Powershell.com member you will have access to:

  • Daily PowerShell tips written by Microsoft MVPs and other leading Windows PowerShell experts
  • Free Windows PowerShell advice and training provided by Microsoft MVPs and other leading Windows PowerShell experts
  • Access to leading Windows PowerShell blogs
  • A free ebook, Mastering PowerShell, written by Microsoft MVP Dr. Tobias Weltner
PowerTip of the Day

Using PowerShell Remoting without Domain

PowerShell 3 and later

By default, when you enable PowerShell remoting via Enable-PSRemoting, then only Kerberos authentication is enabled. This requires both computers to be in the same domain (or trusted domains), and it only works when you specify computer names (possibly including domain suffixes). It will not work across domains, outside domains, or with IP addresses.

To make this work, you need to make one change on the computer that initiates the remoting. In a PowerShell console with Administrator privileges, enter this:

 
PS> Set-Item WSMan:\localhost\Client\TrustedHosts -Value * -Force 
    

If that path is not available, you may have to first (temporarily) enable PowerShell remoting on that machine (using Enable-PSRemoting –SkipNetworkProfileCheck –Force).

Once you made the change, you now can authenticate using NTLM, too. Just remember that now, with domain-joined computers, you need to always submit the –Credential parameter and specify a username and enter a password.

Twitter This Tip! ReTweet this Tip!

Copyright 2012 PowerShell.com. All rights reserved.