Difference between revisions of "AD User Control using Powershell Docker on Linux"
Jump to navigation
Jump to search
Michael.mast (talk | contribs) |
Michael.mast (talk | contribs) (→Server) |
||
| Line 5: | Line 5: | ||
==Server== | ==Server== | ||
This is run on the Windows server. | This is run on the Windows server. | ||
| + | Open powershell as admin | ||
| + | <pre> | ||
| + | enable-psremoting -force | ||
| + | set-item wsman:\localhost\client\trustedhosts <ip or name to be trusted> -force | ||
| + | |||
| + | </pre> | ||
==Client== | ==Client== | ||
This is on the Linux client that sends the commands to the server. | This is on the Linux client that sends the commands to the server. | ||
Latest revision as of 10:27, 15 May 2017
Server
This is run on the Windows server. Open powershell as admin
enable-psremoting -force set-item wsman:\localhost\client\trustedhosts <ip or name to be trusted> -force
Client
This is on the Linux client that sends the commands to the server.
- ↑ https://www.howtogeek.com/117192/how-to-run-powershell-commands-on-remote-computers/
- ↑ http://techgenix.com/creating-active-directory-accounts-using-powershell/
- ↑ https://superuser.com/questions/1156138/allow-powershell-remoting-only-from-one-address
- ↑ https://msdn.microsoft.com/en-us/powershell/reference/5.1/microsoft.powershell.core/enable-psremoting
