Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by TorW

  1. On 2/17/2023 at 9:46 PM, dnelson said:

    I would suggest modifying HKLM\Software\MMSOFT Design\PC Monitor\ComputerName before/after installation to allow you to distinguish them. Besides that in Account > Manage Systems you should be able to tell them apart by the time they were last online.


    Depending on the logistics of your installation, you may be able to store the original ClientIdentifier in a temporary registry key. This would allow you to reinstall, and then replace the new Identifier with the original one. If you can keep the device from checking in before the key is replaced you may be able to save yourself the hassle of manually removing duplicate systems.

    Thanks for your answer!

    This is a pretty convoluted solution that doesn't lend itself to automation very well. We have over 1000 clients to manage and I'm not a fan of manual Rube Goldberg machines in ops, but some useful techniques in your answer anyway :)

    It would be even more useful if uninstalling a PW client with the MSI (what Intune does) also removed it from the web app, because as far as I know only the other way around works now. I.e. when you remove a client from the web app while it's online, the client will uninstall itself. Correct me if I'm wrong ... !

  2. Hi all. We are deploying the preconfigured Pulseway v9.x agent with Intune (MSI file), and that works well.

    However, whenever we do an Intune "Fresh start" on a client that has the Pulseway agent installed and working, we get a duplicate entry for the client in the web app. I assume it's because technically the agent gets reinstalled by Intune and in the process gets a new value in HKLM\Software\MMSOFT Design\PC Monitor\ClientIdentifier.

    Now, because the new and the old install is indistinguishable from each other in the web app, it's almost impossible to know what entry should be removed and what entry should stay.

    Is there a way to identify these obsolete entries in the web app, or maybe look up the client identifier value somewhere? Or maybe some other method we can use to clean up duplicated hosts that will never, ever come back online?

  3. For those who end up in this thread looking for automated configuraton of deployed macOS agents:

    According to Pulseway support it's simply not possible, and there are no config files or terminal commands to tinker with either. Manual agent configuration is the only way. At least that's the case right now. If you come here from the future, please feel free to update this thread with new information.

  4. I am also interested in automatic configuration of the macOS agent after installing it. The manual config is pretty cumbersome in large Mac shops. Are there e.g. any of the Pulseway or PulsewayAgent executables that take command line arguments, or is everything done in the GUI?

    If they don't take cmdline arguments, where is the actual configuration with authentication user, custom server, organization, site and device group stored in the macOS file system? 

  5. Hi all. A colleague of mine have created a patch management policy and assigned it to several groups of computers. This works as indented and have made everyone happy ;) However, if I create a new patch management policy it's impossible for me to go to Patch management -> Agents status, search for a group and change the patch policy. When I hover on the "Change Policy" or "Remove Policy" buttons, the mouse pointer transforms into a "forbidden" sign and the tooltip says "Disabled by policy".

    What policy is that, and how can I assign a new patch management policy to a group?

    I have the admin role in the Pulsway portal, and I'm able to edit patch policies.

  6. Regarding the storage of MSI files for 3rd pary installs/updates; can we store the MSI on a non public web server on the local network, or does it have to be publically available on the internet?

  • Create New...