Jump to content


  • Posts

  • Joined

  • Last visited

Everything posted by WYE

  1. Hi @Jamie Taylor Can you or a member of the team update the roadmap then please? It hasn't been updated since Jan, and as I mentioned over here at https://forum.pulseway.com/topic/4294-clarification-around-upcoming-2fa-changes/?do=findComment&comment=15143, Some items have been developed and released 6months after planned, but it has not been updated to reflect that. It really is worth ensuring that the public roadmap is updated regularly, especially when some of the most required features (as voted for by Pulseway Customers) are not even on there! Thanks in advance,
  2. Thanks @Robert Stan. I did notice it in the roadmap link, however it doesn't look like its been updated since Jan 2021, and it also states that "Remote Control from macOS systems (est. Q1 2021) - in development" - however that was released just recently. Therefore, would it be fair to say, the roadmap is running 6 months behind? Perhaps this post get updated based on the feature voting that all your customers have been doing please? I'm sure other customers would also appreciate it. For example - really keen to know when offline information for systems is to be delivered. Its a very highly voted feature. Thanks!
  3. Yes. If you send your clients the MSI from within Onboarding > Downloads, its an unconfigured agent that you and\or your clients will need to configure (although I suspect it will have the Server\Instance name preconfigured based on @Paul's comment?) If you create agent groups and send the clients the MSI from that group, then as Paul mentioned - it will be preconfigured with your Agent Group and Server name. Once you have an agent installed, then you can start applying policies to the agent group, so that all your clients will have same configuration (such as - alert if offline for x mins) Suggest testing out with a test client on your network, and reporting back any issues. Also, check the help guides over at Pulseway Help Center (intercom.help). They are generally helpful enough to get started.
  4. Create Agent Groups accordingly within Server Admin > Configuration. Then select "Downloads" for the relevant group, and download the Windows Agent. that MSI will be preconfigured for the Agent Group. Once you have the MSI, you can apply arguments to it outlining your dedicated server. Then install via this in a batch \ powershell script including the server instance so you don't need to provide any details to your clients. msiexec /i pulsewayagent.msi /qn /norestart Then you can create a scope that points specifically at that Agent Group. Group Management in Pulseway Pulseway Deployment Methods
  5. Regarding the following in the recent security response statement: At what point with 2FA be required when adding or modifying scripts? We will be prompted when saving a script, or will the upcoming change jus check that MFA is enabled on the account that is updating the script? In relation to this, are there any plans to integrate Azure AD SSO into Pulseway? (appreciate it has pro's and con's in regards to security)
  6. @Curtsen, What do you want to monitor in VMWare? What version of VMWare are you using? What is the actual problem - is it you don't know how to configure Pulseway to monitor VMWare... you don't know what the OID's map to... something else. Let me know, and I'll see if I can help!
  7. WYE


    I suspect this is to do with Pulseway Agent running as "SYSTEM" \ Session 0. You will either need to do Powershell Impersonation within the agent, or use PSEXEC. This posts may help you: launch EXE files with pulseway - Requests - Pulseway
  8. @Jamie Taylor - I've mentioned this before to our account manager and in general feedback, but is it possible that customers could get a list of defects resolved per release? Its frustrating to not know what has or hasn't been fixed. All we see in the release notes is the new features, not development that has improved existing functionality. FYI - This should not be a feature request, this is something nearly all SaaS companies do in one way or another. Please don't direct me to the feature request upvoting site!
  9. I cannot replicate the issue: I have just run your script, only modifying the password, the URI, and I removed the IF statement so it returned all hosts. It worked first time. I suggest you raise this with Support, as it is most likely to be something with your tenancy - and hopefully they can see why? Would appreciate you posting the solution if you get it! I'm going to embark on API integration soon, so I may come across similar issues! Thanks,
  10. Hi, I have a script that runs on new PC being discovered (via the Workflows) Remove-Item 'C:\Users\*\Desktop\Pulseway Manager.lnk' Remove-Item 'C:\Users\*\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Pulseway Manager.lnk' Everything in the Pulseway Manager Agent, can be configured remotely in Server Admin > Policies, and applied accordingly.
  11. From what I believe it only monitors Azure Classic - not Resource Management. Hopefully someone from Pulseway can confirm and\or provide further detail to this.
  12. Are the machines that are failing to restart, failing because they have some processes open that they cannot close (or are awaiting user input)? You could always append "-force" to your restart-computer cmdlet to force it.
  13. What do you expect to see from the application when it is run? E.g. has it got a GUI interface? is it expecting input? It's hard to troubleshoot without the detail. Perhaps replace the script with something that just writes a text file to temp to check the process actually works set-content -Path "$ENV:Temp\TestFile.txt" -Value "test data" if it does - you know the issue does not lie with Pulseway Agent.
  14. Hi, Pulseway Agent runs as "SYSTEM", therefore by default it probably doesn't have access to UNC shares. Have a look here - similar issue, and outlines how to run the Agent as a domain user via group Policy (or if a single system, you can do this via Policies or in the agent itself) Executing MSI installer from Network Location - PowerShell - Pulseway
  15. Kyle, It's not Pulseway, but have a look at LAPS from Microsoft. If you have an AD Environment, it works a treat, and meets the requirement of recording password "relatively" securely, and allows for password rotation.
  16. Is it down to your PowerShell Inheritance config within Pulseway agent? Remember, by default Pulseway agent runs as "SYSTEM" - you may need to enable impersonation so it runs as a domain user or a whatever. Not sure, but that would be my first suspicion.
  17. Is it that the policy is not applying, or that you cannot confirm if it has applied? The Agent GUI (annoyingly) doesn't update according to the policy set - see here: How To Configure Group Policies (pulseway.com) "
  18. That list is maintained by Pulseway - we cannot modify it. Although- Is it Office 2016 (e.g. non subscription) or is it Office 365? (which is also version 2016). You can patch Office365 using the 3rd Party Software Rules, failing that - I guess you'd have to use GPO's to update Office 2016 accordingly. Hope this helps?
  19. Not fully sure on your question, so do correct me if i'm wrong - but do you want every notification to be sent via email? If so, this is configured in the account settings (Account > Notifications). You can enable alerts for email and push, and then configured for which sites\agents groups you want alerts for.
  20. Hi, There isn't a report as such to list the certificates in a store. You could write a script to gather this using PowerShell, however its the storing of the data that would be difficult. It's possible to put data into a Custom Field, and then run a report on that Custom Field - however depends on what you want to see from your certificate store. If you just want to know just about one certificate for example, then you could run your PowerShell and drop the answer into a single custom field. If however you want to know about multiple, the custom field i don't think would work very well here - it's better for storing a single item of data. Custom Fields Help Doc - Introduction to Custom Fields | Pulseway Help Center (intercom.help Hope this helps
  21. For completeness - this has been solved. Details: When using the REST API, you use your username and password, NOT the API Key. API key-based authorization is not supported on Pulseway. The API key is only used for this API called the "Cloud API" and it is not used for RESTful API's. As for the authentication on Postman, Authorization Type as "Basic Auth" and enter your Pulseway User Name and Password in Plain Text. The base64 encoding will be done automatically by the System.
  22. HI, I'm really struggling to authenticate to API - we have a dedicated hosted solution - therefore our web app base URL is https://[thename].pulseway.com. So, following the API documentation - am i correct in therefore assuming that the API base URL is https://[thename].pulseway.com/api/v2/ ? Every time i login, i get: "invalid username and\or password (199)" I've search forums, and tuned my code accordingly - some things i have tried: Using an account with or without MFA. Using Postman, with API Key as Authorisation - using Username (in plain text) as key, and API Key as Value Using Postman with Basic Auth as Authorisation - using Username (in plain text) as Username, and API Key as Password Using Postman with Basic Auth as Authorisation - using Username and Password both as Base64 encoded (as per api documentation) Using Curl (to simplify even more) with a non-MFA account, using username:api-key. Please can someone assist and ideally post some PowerShell or Curl example code for a hosted dedicated instance? It's driving me mad! TIA
  23. For forum topic completeness (and apologies for delay) Response from Pulseway Support:
  24. Currently, the notification and optional completion email states that it failed on X systems. It should state "The task XYZ has failed on X out of Y systems" so we have an idea of the task ahead.
  • Create New...