Posts made by zizka

@theopenem_admin Hello, it seems that this does not work - the "All modules list" is empty...

@theopenem_admin Thanks, I will try that.

@theopenem_admin Hello, thanks. So just to be clear - I should add that domain account to a local Backup operators group on each computer?

It would be very useful to know what error occured. Something more detailed than just "ERROR [4] PolicyExecutor - An Error Occurred In Module Install Ev"

@theopenem_admin Yes, it is. I've tried to re-enter it again to prevent a typo error, but the result is the same. The account is correct, working, enabled, I can log in with these credentials without any problems. Even from the target computer.

@theopenem_admin Yes, I did. There was a different error in the log before I did that. Unfortunately it did not help.

I would need some sort of overview of the status of all policies. Currently it is only possible to pin each individual policy to the Dashboard, but it would be very useful to see somewhere an overview of all policies and their status in a table.

I would be very useful to have a list of all modules independent on their type.

Hello, I have problem running a (powershell) script module under a different than "Default" user. The user is from a domain, the password is set correctly, however when I run a script module with this user, it does not work. When I just change the user to "Default", it works without any issue. There is no information why the execution failed, is there any option to turn on any more detailed log information?

INFO [4] PolicyExecutor - Executing Policy 518cd8fb-5df4-447f-9d63-3fdbb6387c2a (Install Ev)
DEBUG [4] PolicyExecutor - Evaluating Conditions For Install Ev
DEBUG [4] PolicyExecutor - No Conditions Found For Module
DEBUG [4] PolicyExecutor - Evaluating Conditions For Install Ev
DEBUG [4] PolicyExecutor - No Conditions Found For Module
INFO [4] ModuleScriptManager - Running Script Module: Install Ev
DEBUG [4] ServiceImpersonationTask - Starting Impersonation Task
DEBUG [4] ApiRequest - ProvisionedComm/Policy/GetImpersonationAccount/
INFO [4] ModuleScriptManager - 267011
INFO [4] ModuleScriptManager - Script Module: Install Ev Finished
ERROR [4] PolicyExecutor - An Error Occurred In Module Install Ev
ERROR [4] PolicyRunner - Aborting Current Policy

Ok, I will do that. However can it be implemented in some future version? It would be quite useful to have an option to "not overwrite existing target" there.

Hello, is there any option to tell the File copy module not to overwrite the target file if it is already present on the computer?