From af1abf51f6652f4867963e249e5d57daef4e8ee4 Mon Sep 17 00:00:00 2001 From: Kevin Puertas Ruiz Date: Thu, 5 Sep 2019 09:15:17 +0200 Subject: [PATCH] README.md --- README.MD | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/README.MD b/README.MD index 276fca3..dcd24ea 100644 --- a/README.MD +++ b/README.MD @@ -46,16 +46,19 @@ For server you can use Linux or Windows, and in theory any environment that can - Copy this folder to a folder in your server - Install dependencies - Open sysopt.py file and change values if needed -- Use bat file if you are in Windows to run the python server, or sh file if you are in Linux environment -- Go to Client folder and copy "configpcm_example.ini" to "configpcm.ini" and change their values to yours. Change lang value for having client gui translated to your lang +- Start the server: Start api.py using loadserver.bat (Windows) o loadserver.sh (Linux) file. You can do in systemd way, or a cron, or in a terminal of windows server,... +- Go to "client" folder and copy "configpcm_example.ini" to "configpcm.ini" and change their values to yours. Change lang value for having client gui translated to your lang. Here you will see: + - server=X -> Its where server app is running and port by default is :3333. You can change in loadserver file. You can use an IP like 192.168.1.200:3333. + - resources=\\XX -> UNC/Path where software are. When you write cooks, you will do come "REPOTOLOCAL|somefile.msi", well, this folder is where it will copy files. It has be readable by clients. - For clients to work, they have to run "client\client.ps1" every 30 mins/1 hour or so, I did using Active Directory and a Task Scheduled GPO (Copying client.ps1 and configpcm.ini files from Client to SysVol\DomainName\Scripts\) - User: SYSTEM (Or NT\SYSTEM) - Command: powershell.exe - Args: -executionpolicy bypass -windowstyle hidden -noninteractive -nologo -file "\\SERVER\SysVol\DOMAINNAME\scripts\client.ps1" - 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,... + + Note: client.ps1 has to have controlpcm.ini file with it and has to be readable and executable by clients +- 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 right. + - 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 + - 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. \ No newline at end of file