mirror of
https://gitlab.com/JKANetwork/powerfulcomputermanager.git
synced 2026-03-03 09:06:46 +01:00
Changes for fixing bugs in code
This commit is contained in:
@@ -1,5 +1,9 @@
|
||||
# Changelog
|
||||
|
||||
## 2021/12/15
|
||||
- Some fixes in code
|
||||
- NuGet try to avoid stuck on a question
|
||||
|
||||
## 2020/09/11
|
||||
- Fixes in webui in some options
|
||||
- Fix IF64BIT/IF32BIT, was not working
|
||||
|
||||
@@ -68,6 +68,13 @@ For server you can use Linux, Mac or Windows, and in theory any environment that
|
||||
- For use of param "-startup 1" for cooks that has to be run without users, you will have to create a Task Scheduled GPO when workstation startsup/powers off with param -startup 1, like:
|
||||
- Args: -executionpolicy bypass -windowstyle hidden -noninteractive -nologo -file "\\SERVER\SysVol\DOMAINNAME\scripts\client.ps1" -startup 1
|
||||
|
||||
- Note: You can add Windows GPO to show the poweron/poweroff/logon/logoff scripts, I think can be great (Mostly if command stucks):
|
||||
- https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.Scripts::Run_Startup_Script_Visible
|
||||
- https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.Scripts::Run_Shutdown_Script_Visible
|
||||
- https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.Scripts::Run_Logoff_Script_Visible
|
||||
- https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.Scripts::Run_Logon_Script_Visible
|
||||
- (This in some enterprises is useful) https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.WindowsLogon::VerboseStatus
|
||||
|
||||
## Control app
|
||||
- Start control.pyw to setup password
|
||||
- Go to a browser and load https://SERVER_IP:3434/ , login and manage all. control.pyw is the old way, it has to work, but its deprecated
|
||||
|
||||
Reference in New Issue
Block a user