Paul

Hello, While you wait for an official answer you can use something like this: http://rammichael.com/a-command-line-screenshot-maker . You put the exe in system32 or windows or any other folder in the PATH variable with a nice short name and you call the application from terminal using it's parameters. Good Luck, Paul Note: I don't vouch for the functionality or safety of the mentioned product. I just took the first command line screenshot utility I found on google, use it at your own risk.

Hello, To make your service startup automatically (As Marius already said, it's automatically set to startup by itself right after it's installed, but if it doesn't) go to start menu, click run and type: In the right hand side of the window you will see a list of services. Double click the PC Monitor item. Right bellow the executable path there is a setting called Startup Type. Choose Automatic and then press apply. The scheduled task you did has no use for this kind of problem. Paul.

Hello Jeff, I've been using PCMonitor on two of my servers for three months now and it never used up more than 3,5 percent of my cpu. My server machines are old, xeon 3ghz and windows server 2003 but I never experienced high or medium cpu usage from PCMonitor not even on my personal desktop. Are you sure that this is not isolated on that box? The svchost high cpu usages should increase the cpu usage of pcm but why it's eating away your cpu I don't know. If you uninstall pcm svchost processes have low cpu usages? Paul

Hello, You can create a GPO that will force the PCMonitor service to pass to Automatic startup and to run a configuration script that restores settings from a reg file that's located into a network path trough a gpo. For creating a GPO please follow this link: http://technet.microsoft.com/en-us/library/cc776678%28WS.10%29.aspx . For assigning a gpo to some computers use this link: http://www.ucertify.com/article/how-to-link-a-gpo-to-an-ou.html . The GPO Setting path is: Computer Configuration--Policies--Windows Settings--System Services (Please note that in order to see PC Monitor service in this list you MUST have PC Monitor installed in the AD Controller). For instructions on how to distribute the registry changes look here: http://technet.microsoft.com/en-us/library/bb727154.aspx . This could do the job until the unattended install will be completed. This is how I would approach this problem, if you find any better solution please post it here, you might help me too . Paul.

Hello, I can only see this possible to be done by public api calls to the pc monitor application (which is not available yet) with user created plugins, because every application can have it's own way of formatting the log file. It would require a specific Parser for each particular log format. It's a great idea but for now you can set your application to only log alerts / errors the you enable the file preview feature and you can see the log file from the device. Eventually it will be easier once pc monitor file atribute monitoring feature will be released. This will send you a notification if the file gets modified so you would know when to look for updates using the file browser. Paul

I am sure that the development team will take in consideration all possible ways to achieve RDP support, however no release date has been announced for this feature. You can see the current progress on developing new features by reading the pinned Roadmap topic.

Hello, I think that the best way to perform this changes at a faster rate using the avaiable features is the Dashboard application. You can export the settings of each computer in a file then using a text editor you can modify entire setting blocks like email configurations. You can use the NotepadPlusPlus, a freeware text editor, to quickly replace text in multiple files at once. Ofcouse you will need to restore the configuration from the changed files on each computer but it's a better way to do it rather than manually changing on each computer. Paul

Hello, I don't think this is possible because as far as I know a domain controller doesn't know if the user is actually logged into a domain computer or not. (For a good example, take a computer that's currently part of a domain, remove it's lan cable, restart, try to login with the same username and password you have for the domain and it will log you in).