Martin_T

Hi Chris, We're happy with how to use it, my point is that it's not working correctly. Cheers, Martin

Hi Chris, We are using the recurring services contracts but they only appear to bill out on the 1st or last day of the year. Many thanks, Martin

Hi guys, Is there any way to allow user-submitted tickets via a web-form or something on our website that would automatically map the appropriate fields within the PSA & assign it to the correct customer? I'd like to allow the end-users of the various businesses we look after to be able to create their own tickets directly from our website. Cheers, Martin

I have to agree, this would be really helpful. Also if issues could 'stack' i.e. I'd rather not have 30 tickets for one client saying each individual machine has updates rather than one general one that encompasses an entire client base. Sure have the individual notifications on the RMM but each one having its own ticket is a drag.

If the timeout isn't being removed from the webapp, what's the point of this setting (attached) within the RMM? The PSA has an adjustable timeout which arguably will have more sensitive information regarding clients held within.

Hi guys, I think I may have mentioned this previously, but I see there is a new section here for the PSA. We're having troubles with the annual renewals on services. They will only show up as billable at the start/end of the year, not necessarily when the contact actually started. I.E. An annual contract starting on 01/08/15 will be billed on the last day of the year or the first day of the next year rather than every 1st of August. Many thanks, Martin

Hi everyone, I encountered an issue which some of you may have encountered and no-doubt some will encounter in the future whereby you will need to install Pulseway on multiple workstations, laptops etc. and multiple servers. You may also not necessarily want to have the same Pulseway Group Policy enabled for every single device on the network. So, how do we go about doing this? Essentially, it’s the same as the Pulseway Windows GPO installation but with some small changes. Prep the Shared Folder Firstly, we need to make a share that all users can access, and make sure you’ve put the Pulseway_XX.msi in this folder. Make the Config File(s) Next, load up Pulseway Manager and make any changes you want to the config, this will then need to be saved in the same folder as the .msi If you wish to make different config files for Servers, Workstations, Laptops, Tablets etc., please do so now and save them to the same folder. Create the Security Groups For each type of machine you wish to have managed/monitored by Pulseway please create a new Security Group within ADUC (Active Directory Users and Computers) and then add the devices you want to the appropriate group(s). Make the MST File(s) Thanks to forum user robbinschut for this snippet which I’ve modified for this purpose. Follow these steps to create a successful MST file: Open the Pulseway MSI file in Orca Click in the menu "Transform" -> "New transform" Go to the Property table In the right pane right click -> Add row Fill in the property names CONFIG (UNC Path to config file) and CONFIGPASSWORD and the value(s) NOTE: Fill in the property name in UPPER CASE! At this point you can make any other adjustments you would like to the msi on installation. After you added all the arguments you want, click in the menu "Transform" -> "Generate transform..." Save the MST file to the same folder with Pulseway_XX.msi If you have multiple config files for different machines, please create a new Transform for each config file, making sure to make the changes as needed. Set the GPOs You will need to create one of these for each type Transform File you have created. 1. Create a new Software Installation Package in User Configuration > Policies > Software Settings node of Group Policy Management Editor. 2. Select the Pulseway MSI file, and then click Advanced. 3. On ‘Deployment’ tab, Select “Assigned” Deployment type and make sure “Install this application at logon” is also selected and finally select Basic under “Installation User Interface Options”. 4. On the Modifications tab, click Add and select the MST file you created. (This is the ONLY opportunity you will have to apply a Transform to this Package.) 5. Click OK Update client machines Run Command Prompt as Admin and type: gpupdate /force /sync /boot The system will restart and when you next log in Pulseway will install with the correct Config File for your device! I hope this helps those in a bit of a bind when it comes to sending out the Pulseway software across networks without having to worry about setting up multiple groups for the same customer, manually setting up each instance of Pulseway or manually updating the config on each machine.

Would this be possible to run as a scheduled task using a Powershell Script?