Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by ComputerConsulting

  1. 3 minutes ago, Paul said:

    If you configure two tasks then it will work. The registry change is detected within 15 seconds.



    Excellent.  That was the answer I was looking for, and can't wait to try it.

    Now for the icing on the cake:


    How do I make a script pause for 15 seconds?

  2. 22 minutes ago, Paul said:

    I doubt that script 3 will execute. We don't continue a task execution after a reboot. If you need to schedule a reboot for your systems I recommend you to configure the Maintenance Schedule on your machines (can also be done via a Pulseway Group Policy).

    Powershell to control the maintenance mode:

    Set-ItemProperty -Path "HKLM:\Software\MMSOFT Design\PC Monitor" -Name "MaintenanceMode" -Value "1"



    Why wouldn't script 3 work?  The value would = 0 instead of 1 to turn it off again.  I'll have to test it, but wouldn't issuing a registry entry via the powershell overwrite the previous entry with value = 1 with the value = 0?

    I could set a powershell script to execute for all my nodes at a certain time each morning to make sure all nodes are NOT in maintenance mode.

    Wouldn't it also work, if I split it into two tasks instead of one?  The first task would set maintenance mode on do what it needs to do, and then reboot.

    The second task timed to run 30 minutes later would then take the computer or computers out of maintenance mode.

    One more question about my post above:

    After changing the registry entry, would that require a reboot or will the Pulseway Agent see that the registry has been changed, and act accordingly?

  3. It would be helpful to be able to enable maintenance mode in a script and disable it in another script.  

    See if this makes sense.


    Script 1 = turns on maintenance mode

    Script 2 = reboots computer

    Script 3 = turns off maintenance mode


    Would this work, and how would one do this?  This would be a lot simpler than setting a time for maintenance mode in the agent and be more useful since maintenance mode wouldn't depend on a time, but on a script no matter when it runs.

  4. 5 hours ago, Paul said:

    Hi there,

    The maintenance schedule will always use local time on each machine. If you remotely edit the configuration of a system and update the maintenance schedule you're editing the schedule in the timezone of the remote machine.

    Does this make sense?



    Sure it makes sense, but that isn't what I want.

    If I have Client A in Philadephia (EST) 

    Client B in Pomono CA (PST)

    And set a script to run at 5:00AM, it is going to run at 5:00AM my time, right?

    There is no way for Pulseway to know where a customer is located.



    And now that I've looked at the settings on your website, it only asks me which country I am in.  So If I set a script to run at 5:00AM, which 5:00AM is it going to run?  I just went to schedule a script and it gave me my time here in Bangkok.  I DO NOT want scripts to run at my time, but rather their time.  

    It's not clear to me when they run.  That's dangerous.

  5. On 1/16/2017 at 2:44 PM, Paul said:

    Hi there,

    Oh noes :(. You're right, we definitely need a "peek script" function from the task list to avoid further confusions. As for the script color, this would be awesome to have. I am a big fan of color coding things.



    As it stands now, I preface scripts with "Set C Drive Dirty and reboot" so at least I know it's got some power to cause annoyance if not executed at night. The (in brackets) for me indicates SHUTDOWN.

  6. I looked at another MST product last week that had the option to set up the time zone when setting up a client.

    I live in Thailand but my clients are mostly in the US.  I'm getting notifications with my time zone, but not theirs.  I need a way for the system to differentiate the times of various clients.

    In the agent, I can set the time or times that I want the computers to be in maintenance mode.  But when the time zone changes, there is no modify it according to the time zone itself.


  7. I rebooted EVERYONE in my dashboard yesterday to the great surprise of everyone in my dashboard who was not at lunch.  I created some scripts which I though did not contain a shutdown command but there was one in one of the scripts.  When creating a task, I can add a script, but I cannot see what is in the script without backing out and editing the script again.

    I can think of two things: 

    1.  I would like to be able to peek inside a script before adding it to a task.

    2.  I would like to color code scripts.  If I choose red for scripts with a shutdown command, then I can easily see danger including said script.

  8. The two-factor authentication as it stands now, is woefully incomplete.

    Until such time that the timeout for my browser login can be lengthened, I cannot use two-factor ID whether it is a OTP or a Google Authenticator number.

    As in most two-factor implementations, I should be able to whitelist my current browser for at least 30 days and not be asked for it again.

    The purpose of two-factor authentication is to keep the bad guys from logging in ONE TIME and all times, not to continually inconvenience me each and every time my browser decides to terminate the session for inactivity!


    Harumph, Harumph ... wait a second, I didn't hear a Harumph out of that guy .....

  9. 20 minutes ago, Paul said:

    Hi there,

    A couple of weeks ago we've released the 4.9.6 agent update which speeds up the service startup which should've resolved the issues to the service startup issues. I've sent you an email on the address on your profile as we'd like to further investigate why the service isn't startup up in your case.



    I've experienced this on different machines, and not just for Pulseway but for ScreenConnect as well.


  10. I had a conversation yesterday with Vick at Pulseway and discussed my solution to the problem of the Pulseway service not starting reliably 100 percent of the time.  I always set the service to run delayed in Windows. 

    I have had to do this with ScreenConnect as well.  If I do not, every once in a while, on reboot, I will find the service not running.  This is a real problem if I only had the remote built into Pulseway as my remote control, but I run ScreenConnect.  What I find, is that Pulseway may not be working but ScreenConnect is running, or it works the other way.  

    I would like to see an option on install of the agent, in the form of a radio button that I can check, to have the service installed and run delayed as opposed to a normal service start.

  11. On 1/28/2014 at 9:44 PM, Marius said:



    Thank you, we will email you / post a banner.


    As for the features, the list is here: http://www.pulseway.com/pricing - press the "view more features" option.


    Perhaps Pulseway should look into some form of affiliate marketing.  I love the product, and I've also looked at many others, but I pay for your product and if I'm going to promote it, I want a share of the profits.  

    I've got my own business to market.  

  12. On 6/11/2013 at 5:37 PM, Marius said:

    We will consider this. 

    BTW, we do support two-step authentication for accessing account settings, the web app and some other settings. Check the Account Details section in PC Monitor Manager.


    I used your two-factor authentication.  The timeout on it was so short as to be annoying.  I stopped using it.  

  • Create New...