Fixed bugs, new options for cooks

This commit is contained in:
2019-09-05 08:38:06 +02:00
parent ada3b9a6d2
commit 90683c44b0
7 changed files with 89 additions and 55 deletions

View File

@@ -16,7 +16,7 @@ It's not error proof, then, I don't have any responsability if something crashes
- Complete translation English and Spanish
- Somewhat more security in API 1
- Stabilize all
- I created a simple GUI in EasyGUI to be easy used, but maybe I will transition to a web GUI more dynamic and visually better
- I created a simple GUI in EasyGUI to be easy used, but if I have time, maybe will do a webUI more dynamic and visually better (Without needing to install php/apache/nginx, using python)
# Requirements
@@ -55,4 +55,7 @@ For server you can use Linux or Windows, and in theory any environment that can
Note: client.ps1 has to have controlpcm.ini file with it
- If you don't have Active Directory, you can do the Task Scheduled task in every computer without problems, and using another Shared folder, it will work
- Start api.py using .bat o .sh file. You can do in systemd way, or a cron, or in a terminal of windows server,...
- Start control.pyw to setup password and start adding computers, groups and cooks
- 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
- Start control.pyw to setup password and start adding computers, groups and cooks. You can use doc/example_cooks for examples. If anyone wants, I will setup a git repo for cooks.