Jump to content


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Simple ask. I've had this with other PSA in the past. Despite coaxing, customers still email the techs for service. That aint going to change. So techs forward the customers email to the ticket parser. This isn't new information to anyone, we all probably do it several times a week if not day. When a tech, a named user of the PSA system, forwards an email to the ticket parser it opens a ticket in the techs name. Why, why? So much needless work. Use logic and match the sender as a tech and use the next address.
  2. Hi all, I'm looking for more information on how to setup this feature. "1-Click" button in the Remote Control client. I assume this pulls embedded passwords from itglue, however this isnt working for me. "Pulseway Remote Control, No credentials found."
  3. Hi all, My goal is to create a Win32 package to deploy using Microsoft Intune that auto registers the computer. I've done this successfully with agent version 8. However, today I cannot get it to work with agent version 9. Despite contradicting help information out there that directs you to use Orca, the .MSI file that is generated contains the appropriate information to auto-register the agent. In the past I've converted the .MSI to .INTUNE, created the app in Endpoint Manager and assigned it with success. I'm working on doing this process again with agent version 9. I can get it to deploy with Intune, however auto-registration fails. My process is the same as with agent version 8. I'm at a lost as to why the registration info is being manipulated somehow during the .MSI conversion to .INTUNE. I'd love to get my hands on a version 8 agent to test with. Any advice appreciated.
  4. Hi folks, Anyone have this issue and know a fix? Maybe I need to update or enable something on the agents, IDK. When using Private Remote Desktop Sessions (new feature); We are using Pulseway RMM On-premise Launch a new Pulseway RDP Session - I provide local computer credentials and get 'Value cannot be null. Parameter name: value' Launch a new Session using Microsoft RDP Client - 'An error occurred while trying to start the remote control session (131084)
  5. Hi folks, I am seeing this trigger, System Registered, in the Automation > Workflows area. I'm imagining this trigger combined with the organization condition value can easily automate a series of actions to perform onboarding computers automatically. In testing, this works fabulously. However, it seems Pulseway RMM only allows one active workflow to use the 'System Registered' trigger. Understandable. I suppose I could use a single Workflow that uses the 'System Registered' trigger that cascades through all my clients. i.e. Organization Condition=ABC Customer: true/false > a false answer cascades to a new Organization Condition=XYZ Customer: true/false, etc, etc until a true result is found that kicks off the actions. This would quickly become difficult to manage, though I am considering it as I dont have any other options at the moment. Looking for how you all have automated your on-boarding efforts? What are you doing that works for you?
  6. Figured out my answer. Trigger: Updated by: Employees Condition: Primary Assignee: Changed Notification: Assigned Resources
  7. I've discovered my answer. Apparently when you assign any Work Type to the ticket proper, it limits subsequent time entries to only that work type selected. When I leave the Work Type field blank on the ticket proper, it works as expected.
  8. I'm attempting to define a workflow that will send an email notification to the assignee when they are assigned a ticket. Seems straight forward, but I'm not sure how to set up the trigger. Anyone have this in production? How did you do it? Thanks for any help!
  9. Hi Gary, Not sure if you're still out there but I thought I'd ping you and see. I'm wrestling with how we want to use Roles and Work Types. My thought is to use them as you describe in this thread. "Work types we use for "Regular Hours, Non Billable and Overtime"." . However I see a hurdle with this method. From what I can tell, the Work Type must be selected with-in the ticket information. While adding time entries you can only select the work type that is added into the ticket info. So that doesnt work for multiple time entries on the ticket with different work types. I dont get how you can use it that way. I would love to set it up that way, if I could work around having to specify a work type on the ticket.
  • Create New...