# Set up PS remoting on home edition

**URL:** <https://forums.powershell.org/t/set-up-ps-remoting-on-home-edition/5544>\
**Category:** PowerShell Help\
**Created:** [January 15, 2016, 4:08am UTC](https://forums.powershell.org/t/set-up-ps-remoting-on-home-edition/5544 "2016-01-15T04:08:36Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![gerard-ashton](https://avatars.discourse-cdn.com/v4/letter/g/35a633/32.png) [@gerard-ashton](https://forums.powershell.org/u/gerard-ashton)\
**Post date:** [January 15, 2016, 4:08am UTC](https://forums.powershell.org/t/set-up-ps-remoting-on-home-edition/5544/1 "2016-01-15T04:08:36Z")

</div>

I’m just learning PowerShell and taking the Getting-Started-with-Powershel-3.0-Jump-Start from the Microsoft Virtual Academy. I have Windows 10 home edition on 2 machines. The command suggested to enable remoting, “enable-psremoting”, ran OK but remoting does not work. For example, “Enter-PSSession -computername anothercomputer” gives the error message

Enter-PSSession : Connecting to remote server anothercomputer failed with the following error message : The WinRM client cannot process the request. If the authentic  
scheme is different from Kerberos, or if the client computer is not joined to a domain, then HTTPS transport must be used or the destination machine must be  
the TrustedHosts configuration setting. Use winrm.cmd to configure TrustedHosts. Note that computers in the TrustedHosts list might not be authenticated. Yo  
more information about that by running the following command: winrm help config. For more information, see the about\_Remote\_Troubleshooting Help topic.  
At line:1 char:1

- Enter-PSSession -computername anothercomputer
- 

```auto
  + CategoryInfo : InvalidArgument: (anothercomputer:String) [Enter-PSSession], PSRemotingTransportException
  + FullyQualifiedErrorId : CreateRemoteRunspaceFailed

```

So what is the best way to set up remoting in this environment?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\
**Post date:** [January 15, 2016, 4:34am UTC](https://forums.powershell.org/t/set-up-ps-remoting-on-home-edition/5544/2 "2016-01-15T04:34:36Z")

</div>

Home editions cannot join Windows Active Directory domains, which means that Kerberos cannot be used as the authentication method. This means you’ll need to read up on TrustedHost, as the error message indicates. When this is complete, you may need to include the -Authentication parameter (when using Enter-PSSession) with a different value, as well. Read the full help on Enter-PSSession by entering _Get-Help -Name Enter-PSSession -ShowWindow_.

---

<div class="post-metadata">

**Author:** ![gerard-ashton](https://avatars.discourse-cdn.com/v4/letter/g/35a633/32.png) [@gerard-ashton](https://forums.powershell.org/u/gerard-ashton)\
**Post date:** [January 15, 2016, 4:38am UTC](https://forums.powershell.org/t/set-up-ps-remoting-on-home-edition/5544/3 "2016-01-15T04:38:55Z")

</div>

Thanks tommymaynard, I didn’t know whether it was better to learn about trusted hosts or https transport, which the error message hints is the other way to go. Thanks to your pointer, I’ll learn about trusted hosts.

---

<div class="post-metadata">

**Author:** ![matt-bloomfield](https://avatars.discourse-cdn.com/v4/letter/m/dec6dc/32.png) [@matt-bloomfield](https://forums.powershell.org/u/matt-bloomfield)\
**Post date:** [January 15, 2016, 4:42am UTC](https://forums.powershell.org/t/set-up-ps-remoting-on-home-edition/5544/4 "2016-01-15T04:42:10Z")

</div>

You’ll also find more information in the free [PowerShell.org](http://PowerShell.org) book [Secrets of PowerShell Remoting](https://www.penflip.com/powershellorg/secrets-of-powershell-remoting/blob/master/accessing-remote-computers.txt).

Something you may wish to consider doing is getting hold of a free hypervisor such as VirtualBox or VMware player and then downloading an evaluation version of Windows server. It doesn’t take an awful lot of resources to run a couple of virtual machines and you’ll be able to set up an Active Directory domain.

---

<div class="post-metadata">

**Author:** ![victor-vanegas](https://avatars.discourse-cdn.com/v4/letter/v/e68b1a/32.png) [@victor-vanegas](https://forums.powershell.org/u/victor-vanegas)\
**Post date:** [January 22, 2016, 7:37am UTC](https://forums.powershell.org/t/set-up-ps-remoting-on-home-edition/5544/5 "2016-01-22T07:37:31Z")

</div>

Hi  
You also need to make sure that your network location is set to anything but Private network. And set the default admin password.

---

<div class="post-metadata">

**Author:** ![dotnVo](https://avatars.discourse-cdn.com/v4/letter/d/4af34b/32.png) [@dotnVo](https://forums.powershell.org/u/dotnVo)\
**Post date:** [May 16, 2024, 8:43pm UTC](https://forums.powershell.org/t/set-up-ps-remoting-on-home-edition/5544/6 "2024-05-16T20:43:05Z")

</div>