Disable-PSRemoting is not recognized as a cmdlet

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 4 years and 5 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
clum09
Posts: 150
Last visit: Sun Jan 21, 2024 5:07 pm

Disable-PSRemoting is not recognized as a cmdlet

Post by clum09 »

Product, version and build: 7.5.132
32 or 64 bit version of product: 64 Bit
Operating system: Windows 10
32 or 64 bit OS: 64 Bit

PrimalScript does not recognize "Disable-PSRemoting" as a cmdlet - the color code appears to show this cmdlet as a function instead. See the attached picture.

Disable-PSRemoting.jpg
Disable-PSRemoting.jpg (32.82 KiB) Viewed 2882 times
Please add "Disable-PSRemoting" as a cmdlet with proper color code.

Thanks.
User avatar
Alexander Riedel
Posts: 8478
Last visit: Tue Mar 26, 2024 8:52 am
Answers: 19
Been upvoted: 37 times

Re: Disable-PSRemoting is not recognized as a cmdlet

Post by Alexander Riedel »

It was, for some reason, added to the pre-defined function list in PowerShell. I am assuming a late night copy-paste gone wrong. It will be removed.
Alexander Riedel
SAPIEN Technologies, Inc.
This topic is 4 years and 5 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.