jhendricks123 Posted October 24, 2012 Posted October 24, 2012 I have written a command-line python script to login to our access control system and unlock doors, then added a scheduled task for each door on one of our servers where PC Monitor is installed. I've then selected each task in System > Scheduled Tasks in PC Monitor Manager 3.2. I can run the tasks by hand from Task Scheduler, but not from Mobile PC Monitor. I've tried from four different mobile devices (Nexus 7, Samsung Infuse, Droid Razr and Droid Bionic) and the command is sent, but the task is never triggered. Event Viewer shows the following: PC Monitor Warning Event ID 24002 A request was received from a non authorized device and it was denied: Request Run scheduled task '\*********' from device Id: '*********' The task name and device ID are removed on purpose, but they match the scheduled task and device ID. I've removed the device(s) from the Manage Devices dialog, and I've also tried blocking/unblocking devices in addition to visiting device access policy and revoking/granting full access. I've also verified that there are no group policies defined under Manage Computers > Manage Group Policies. I seem to have access to all information on this server and other servers from each mobile device, but I get this denial error whenever I try to manage a scheduled task.
jhendricks123 Posted October 24, 2012 Author Posted October 24, 2012 I should also add that all servers are running PC Monitor 3.2 and this server is 32bit. The client version on my mobile(s) is 3.2.1 (build 121015).
Marius Posted October 25, 2012 Posted October 25, 2012 Check the Devices tab in the PC Monitor Manager. The device you use to send the command is not in the list of authorized devices.
jhendricks123 Posted October 25, 2012 Author Posted October 25, 2012 Ah, I missed that tab. Thanks! It's a little confusing having device permissions in two different places
Marius Posted October 25, 2012 Posted October 25, 2012 Glad it worked. I agree, on the Devices tab we have added a note at the bottom recommending the use of device access policies instead of this.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now