Paul

Hi there, Is that machine also a domain controller? You can only enable the Active Directory server module on Directory Controllers...

In that case go to advanced firewall rules and add a new outbound rule that allows only PCMonitorSrv.exe access to the internet. Then create another outbound rule that blocks everything else. When you are home you will need to disable those firewall rules (if possible without your son noticing). Or maybe create a batch file and save it into a directory that's included in your PATH variable so you can send commands to the terminal like: firewallon.bat or firewalloff.bat . Let me know if you need help with the commands.

I may misundertand you but you want to completely block all outbound traffic that's not using port 443 (HTTPS) only for two computers in the LAN? This is a bad idea since your system still needs to do DNS queries (to properly resolve PC Monitor's servers and to provide other services). Again, why do you want to block outbound traffic?

Why not do it from Windows Firewall? Create a rule that blocks all outgoing traffic that's not from port 443.

Why would you want to manage ALL services? You will have to scroll on the list to find the one you need. Same goes for counters, you really read all counter values?

I think you can only do this if you have an enterprise server and share your computers from one main account. When you share computers you get the option to select if you wish to get notifications.

Using a self signed certificate will require you to manually add the certificate signer to the trusted root certificates on all machines you wish to use PC Monitor agent, PC Monitor Dashboard, Windows Phone and Windows 8.1 App. Furthermore you will only be able to use the Android app if you manually inject the certificate signer to the device's certificate store (which requires root access). iOS app will never work since iOS system has a certificate store for each app installed. You can get free signed SSL certificates at www.startssl.com or you can buy one for 10$.

Hello spammy, You can setup a Device Access Policy for that using PC Monitor Manager. Go to Registered Devices -> Device Policies, select your device and chose the access you wish that device will have for the machines you wish to restrict. If you set readonly access that device will no longer be able to access the terminal or send system commands like (shutdown, restart). Also you can change the Default Device Policy to have readonly access to all monitored systems and manually set a policy for the devices you wish to have full control. Furthermore you can increase your account's security by enabling two factor authentication (from account details) which will ask for a OTP (one time password) whenever you try to change account's security and policies. Most of this information (if not all) is available in PC Monitor's User Manual available at: http://www.pulseway.com/manual. I personally like to keep my account locked out so that I have to manually approve each device that gets added before it gets access to my systems.

Try enabling diagnostic logging on PC Monitor (open PC Monitor Manager app -> Settings -> Diagnostics -> Enable Diagnostic Logging), suspend your computer, wait for a minute, wake your computer, wait for it to suspend again, wake the computer one more time and now copy and paste the contents of the trace.log file from PC Monitor's installation directory. Also try checking the Application and System event logs to see if there are any relevant log entries that may help understand what's causing the computer to enter a suspended state for the second time.

Hello Chris, At this moment there is no way to remotely input login details for monitored systems. But if you wish you can configure windows autologon feature (control userpasswords2). Why do you need to remotely logon? Services run regardless of user sessions.

Mobile PC Monitor's Roadmap (http://forum.pulseway.com/topic/15-roadmap/) announced updates for the Exchange server module so there is a possibility that you might be in luck and see your requests in a future version.

There is a difference between the locally attached harddisks and removable drives, that's why you are not seeing any sensor readings for the USB drive. Judging from the Roadmap they plan on adding support for more hardware sensors so you might be in luck .

This is odd. It seems like something is actually preventing the reboot process. If you run the 'reboot' command in the PC Monitor terminal does it perform the same behaviour?

As far as I know PC Monitor servers will never try to connect to your computers. I would recommend you to setup monitoring of your public services exposed from that machine via ping, websites, certificates, snmp or any other method you may think might work.

The problem is that iOS doesn't allow to execute for long once it's in background. If another app requests memory there is a high chance that the application will get stopped making it hard to monitor. Also having an agent in Android might consume a lot of battery which might not be a great idea too. The features you indicated could work on demand. For instance you start PC Monitor and press the request support. While the app is running other devices should be able to see and check screens and processes of the source device. This approach would be less invasive for the client in my opinion.

Invalid username and/or password (295). Check your account details, maybe you made a typo.

No, the notification system did not change. If you want, you can send an email at: support at mobilepcmonitor dot com, requesting this Auto Clearing Notification feature. More people ask for it, more importance this feature will receive.

Basically you are requesting an override setting to always send WoL packets on a hostname rather than the last known IP address. This could be a good idea since some people may have a server with multiple IP addresses where one IP address (which can happen to be the one he uses on outgoing requests) to be filtered in a firewall. +1 for this.

I believe you are referring to the message you get when you start the PC Monitor Manager app. Marius over here ask you to click the Validate Account button on the application and let him know what message you are getting.

Hello, You open the MIB file to know which variable names you want to monitor then using PC Monitor add/crawl the variables you are interested in monitoring. With a bit of common sense you'll be up in no-time. Paul

Have you copied the configuration sample to the real configuration file name? sudo cp /etc/pcmonitor/config.xml.sample /etc/pcmonitor/config.xml sudo /etc/init.d/pcmonitor restart This is standard procedure on most linux apps. Yes, I believe that the GUI app from the native linux agent is still in development but you can configure everything with a configuration file too. Paul

It might help if you could provide us with an installation log or an error screenshot or the event that got created in the windows event log.

You can do that by creating a performance counter monitor. Go to Notifications -> Counters -> Add -> Category: Process -> Instance: processname.exe -> % Processor Time. Paul

Are you getting any error messages in the Console?