I work with kids in a computer lab, however, I wanted to know if there is a way(quick way), to disable the net connection (using the desktop I work on) from all computers(except the one use) to prevent them from accessing the web and then enable the net connection when I give them permission to use the web.
Solution
In agreement with kanewolf.
However, you most likely can give Powershell a try on your own.
For example the Stop-Computer cmdlet:
Here:
https://blogs.technet.microsoft.com/heyscriptingguy/2012/12/24/powertip-use-powershell-to-shut-down-a-remote-computer/
However, a full shutdown and restart is not probably viable when the results include a bunch of idle kids.....
However stopping and start a process remotely could work - examples:
http://rakhesh.com/powershell/killing-a-process-on-a-remote-computer-using-powershell/
and
http://www.vexasoft.com/pages/stop-remoteprocess
https://www.devopsonwindows.com/7-ways-to-manage-windows-processes-remotely/...
However, you most likely can give Powershell a try on your own.
For example the Stop-Computer cmdlet:
Here:
https://blogs.technet.microsoft.com/heyscriptingguy/2012/12/24/powertip-use-powershell-to-shut-down-a-remote-computer/
However, a full shutdown and restart is not probably viable when the results include a bunch of idle kids.....
However stopping and start a process remotely could work - examples:
http://rakhesh.com/powershell/killing-a-process-on-a-remote-computer-using-powershell/
and
http://www.vexasoft.com/pages/stop-remoteprocess
https://www.devopsonwindows.com/7-ways-to-manage-windows-processes-remotely/...
- Oct 11, 2014
- 34,813
- 3,307
- 146,290
In agreement with kanewolf.
However, you most likely can give Powershell a try on your own.
For example the Stop-Computer cmdlet:
Here:
https://blogs.technet.microsoft.com/heyscriptingguy/2012/12/24/powertip-use-powershell-to-shut-down-a-remote-computer/
However, a full shutdown and restart is not probably viable when the results include a bunch of idle kids.....
However stopping and start a process remotely could work - examples:
http://rakhesh.com/powershell/killing-a-process-on-a-remote-computer-using-powershell/
and
http://www.vexasoft.com/pages/stop-remoteprocess
https://www.devopsonwindows.com/7-ways-to-manage-windows-processes-remotely/
https://4sysops.com/archives/query-and-kill-a-process-on-a-remote-computer-using-powershell-and-wmi/
Depending on the circumstances and your time you can clone from examples in the above links. And there are other such links available.
Then you should be able to test against just one or two lab computers without too much difficulty. Just use the cmdlet formats shown and substitute in the names of your lab computers.... Credentials may be a bit more difficult but once you have a working script(s) in place then you just cut and paste for each system. And change the name.
And you can google specific Powershell commands for additional explanation, insight, and examples.
Give it a try if you are so willing. Make it work on your local computer first. Then go to a remote implementation.
Post your scripts and the problem(s) you encounter.
However, you most likely can give Powershell a try on your own.
For example the Stop-Computer cmdlet:
Here:
https://blogs.technet.microsoft.com/heyscriptingguy/2012/12/24/powertip-use-powershell-to-shut-down-a-remote-computer/
However, a full shutdown and restart is not probably viable when the results include a bunch of idle kids.....
However stopping and start a process remotely could work - examples:
http://rakhesh.com/powershell/killing-a-process-on-a-remote-computer-using-powershell/
and
http://www.vexasoft.com/pages/stop-remoteprocess
https://www.devopsonwindows.com/7-ways-to-manage-windows-processes-remotely/
https://4sysops.com/archives/query-and-kill-a-process-on-a-remote-computer-using-powershell-and-wmi/
Depending on the circumstances and your time you can clone from examples in the above links. And there are other such links available.
Then you should be able to test against just one or two lab computers without too much difficulty. Just use the cmdlet formats shown and substitute in the names of your lab computers.... Credentials may be a bit more difficult but once you have a working script(s) in place then you just cut and paste for each system. And change the name.
And you can google specific Powershell commands for additional explanation, insight, and examples.
Give it a try if you are so willing. Make it work on your local computer first. Then go to a remote implementation.
Post your scripts and the problem(s) you encounter.
TRENDING THREADS
-
-
Question Can´t open BIOS because no keyboard input is received.
- Started by Blatscher
- Replies: 11
-
-
-
News US sanctions transform China into legacy chip production juggernaut — production jumped 40% in Q1 2024- Started by Admin
- Replies: 35
-
-
Question New pc build r9 7900x3d rtx 4080 super no post only ram rgb turns on- Started by Harvey Durward
- Replies: 4
Latest posts
-
-
-
Question RTX 2060 Zotac stops giving display output when pushed hard- Latest: Moru Zerinho6
-
-
-
Facebook
Twitter
Instagram