Jump to content

Paul

Administrators
  • Posts

    1740
  • Joined

  • Last visited

Everything posted by Paul

  1. No, sorry I keep pushing forward on my schedule. I will try doing it during the weekend.
  2. Does this work if there is no user logged in?
  3. Do you see the correct version in "Programs and Features" (appwiz.cpl)?
  4. Looks cool, thank you. Does it force a shutdown or restart or it will issue a plain shutdown command?
  5. I am guessing that your NAT is not supporting loopbacks and that's why you can't connect to your server using the hostname. If you have a DNS server inside your local network add a new primary zone for your domain and copy all your current DNS records except pcmonitor. For pcmonitor create an A type record that points to your server's local IP address. Don't forget to setup DNS forward servers and change your primary DNS entry on all local machines to your local DNS server. This workaround will avoid the NAT loopback problem. If you are using Active Directory then you are in luck because you already have a local DNS server and all your clients use it as a primary DNS server, you just need to configure the new zone.
  6. 5 ms is pretty bad I might say. On a loaded network 5 ms can happen whenever there is a considerable amount of traffic in that moment. For instance you might have a really nice 10/100/1000 network over there, all patched up fancy but spikes can occur due to switches and other transport issues. 5 ms is very sensitive... From my research I found out that there already exists a Ping class inside .NET which offers the same functionality of the win32 ping application. Further more I dug up that the .NET ping class uses an unmanaged method IcmpSendEcho2 from the iphlpapi.dll which is the exact same method used by the native ping application judging from unmanaged method imports from a debugger's point of view. So it's fair to say that PC Monitor does that exact same thing as you would do when you test out your network connectivity so we can exclude the first and second possibilities you pointed out. For the third way there is no way of knowing unless someone from PC Monitor will say how their ping logic works.
  7. Right so you pretty much have two solutions over here: Reduce the time to kill amount to something acceptable (20 seconds maybe?). This value controls the amount of milliseconds it allows a service to shutdown before the system will actually kill it in order to proceed with shutdown. You will find that value here: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout Manually stop Exchange services before shutting down the machine. Create a batch script called shutdown_properly.bat and put it into a directory that's inside your PATH variable. In that batch script put something like this: @echo off echo 'Stopping Microsoft Exchange Services' net stop MSExchangeAB net stop MSExchangeADTopology net stop MSExchangeAntispamUpdate net stop MSExchangeEdgeSync net stop MSExchangeFBA net stop MSExchangeFDS net stop MSExchangeIS net stop MSExchangeMailboxAssistants net stop MSExchangeMailboxReplication net stop MSExchangeMailSubmission net stop MSExchangeProtectedServiceHost net stop MSExchangeRepl net stop MSExchangeRPC net stop MSExchangeSA net stop MSExchangeSearch net stop MSExchangeServiceHost net stop MSExchangeThrottling net stop MSExchangeTransport net stop MSExchangeTransportLogSearch shutdown -s -t 00 The last line on the batch script will call the system shutdown without forcing applications to close. In other words it will be a nice and clean shutdown just the way your server likes it. If you would like a reboot instead you can modify the last line to something like this: shutdown -r -t 00 Please note that the batch script will differ from Microsoft Exchange Server versions. The one I wrote to you works only with Microsoft Exchange Server 2010. If you are using a different version I recommend you to add the correct exchange services and remove the ones that are not installed on your system. Then if you would like to shutdown or restart you machine from your PC Monitor client open up terminal and write the batch file's name (Now you see why I made you place it into a directory inside the PATH variable, otherwise you would have to write the full path to the file too).
  8. Plugins are extensions to the agent you install on your systems. All my plugins are windows based but some can be easily adapted to work on linux too. You can consult the user manual or cheat by reading below. To install a plugin: Open up PC Monitor Manager on a monitored system Go to the Plugins tab Click Add Browse to the location of a downloaded plugin (Note: all Windows based PC Monitor plugins have an extension of .dll and it it's filename is not PCMonitorClient.dll as that is a dependency) On the following screen where you have to select which class you would like to activate make sure that everything is selected (usually there is only one entry) and then click on OK Optionally if the plugin requires additional configuration you can click on the plugin entry in PC Monitor and click on the Configure button on the right side of the application Click Apply or Ok button on PC Monitor Manager to save your settings Once the plugin is installed you are good to go, just use your mobile device / web app / windows 8 app to browse to your monitored system and beneath the system commands you will see plugin controls. Also it's worth adding that most of the plugins (well at least my plugins) are opensource and without any licenses which means you can freely get their source code and modify them then release them as your own. Good luck, Paul.
  9. Yes, You can manage multiple hypervisors by using: Multiple PC Monitor Agents For VMware vSphere you can install vCenter and have PC Monitor manage it For Citrix Xen you can add multiple hosts to the pool
  10. What is the ping threshold you configured in PCM Manager?
  11. Usually Exchange servers shutdown like that because they are installed on the same machine with the Active Directory Controller. The symptom is that the ADDS services shutdown before exchange does and Exchange waits for a reply from a query he makes to AD. As far as I know the timeout is set to five minutes. I've reduced that timeout on my exchange server to 30 seconds and the machine shutsdown faster now.
  12. Paul

    Dashboard

    It could work as long as you only see detailed information for one system at a time (just like the mobile clients do).
  13. Any shortcuts to the system / module would do great as everyone seems to be doing the same thing when they read the notifications: Read message, Investigate current status and Apply fix. I particularly like this idea. +1
  14. Hi, So you're asking that instead of a new notification that the ping endpoint can be reached again you would like that the agent would modify the previously sent ping failure notification to change it's priority and content. I like the idea but I don't see a practical use of it. When I receive a notification that some device cannot be reached I would like to know why that happened and queue an investigation of the network to evaluate potential downtimes and future risks. At the moment notifications can be ordered by date so I can quickly identify when something happened and when it got fixed (if applicable). However this doesn't mean that the notification cannot change a notification if the problem got fixed as long as the two notifications get merged nicely (Fix date to be properly appended to the original message and notification priority to be dropped to low or normal).
  15. Paul

    Upgrading

    As far as I know you can purchase a subscription for any number of systems where the minimum subscription is the amount of systems that are currently registered on your account. On the purchase subscription wizard on the website you can move slider that controls the amount of systems you wish to buy back and forward.
  16. Ups, I totally forgot about this. I will create the plugin and post it here today or tomorrow. Thanks for the heads-up.
  17. Paul

    Dashboard

    Well that would mean that if you have 100 monitored computers you would have 100 computers constantly sending a lot of data. I like to use dashboard to see the overall status of the monitored systems, when there is something bad happening a notification will fireup on the dashboard and I can quickly identify the system and it's severity. It would be an overkill to add all that information for all computers, imagine the traffic you would generate...
  18. Can you wake up your computer with another application that supports WoL? Have you enabled WoL in your BIOS settings? Are you connected to internet via an ethernet connection (wired, not wireless)?
  19. You can also delete a service using the sc command: sc delete "PC Monitor" Good Luck, Paul.
  20. Why not use a scheduled task to do it?
  21. Sure, whitelist: Note: List may not be acurate so test it and see if it works.
  22. Any event logs, diagnostic outputs, operating system details, anything at all other than "it doesn't start after windows update restart"? I can't reproduce this on my servers: 2003 R2. Standard and 2008 R2 Standard. All update, restart and PC Monitor starts up as expected.
  23. Download the msi file again then execute msiexec /x msifile or msiexec /uninstall msifile .
  24. Hello, This is normal behaviour when the configuration has been protected with a password. On the lower left side of the application you have a padlock that should say: "Click here to unlock the configuration" or something similar. You will be prompted to input a passcode. Good luck.
×
×
  • Create New...