# Powershell - No Remoting

**URL:** <https://forums.powershell.org/t/powershell-no-remoting/8833>\
**Category:** PowerShell Help\
**Created:** [June 15, 2017, 12:07am UTC](https://forums.powershell.org/t/powershell-no-remoting/8833 "2017-06-15T00:07:32Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![andrew-rasdell](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@andrew-rasdell](https://forums.powershell.org/u/andrew-rasdell)\
**Post date:** [June 15, 2017, 12:07am UTC](https://forums.powershell.org/t/powershell-no-remoting/8833/1 "2017-06-15T00:07:32Z")

</div>

Dear Community,

Corporate Domain Environment, Windows 7 Enterprise, Powershell V5, Remoting not enabled across the desktop fleet

What would be the best way to remotely enable PS-Remoting, then later Disable PS-Remoting (One or two machines). I am toying with the idea of using PSExec to launch a batchfile which then launches powershell on the remote machine to do the enable / disable remoting piece

Does this sound OK - Open to better suggestions

Thanks

---

<div class="post-metadata">

**Author:** ![vmotion1984](https://avatars.discourse-cdn.com/v4/letter/v/7feea3/32.png) [@vmotion1984](https://forums.powershell.org/u/vmotion1984)\
**Post date:** [June 15, 2017, 12:55am UTC](https://forums.powershell.org/t/powershell-no-remoting/8833/2 "2017-06-15T00:55:50Z")

</div>

I think if it are just 2 machines just enable it by hand or let some helpdesk dude walk by the machine. if you want to do it voor your whole fleet i suggest you should use a GPO.

---

<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:38pm UTC](https://forums.powershell.org/t/powershell-no-remoting/8833/3 "2024-05-16T20:38:35Z")

</div>

Closed on May 16, 2024, 8:38pm UTC


