MSP Helpdesk Options
-
@CCWTech said in MSP Helpdesk Options:
@scottalanmiller said in MSP Helpdesk Options:
@CCWTech what it doesn't tell you is if the 12th user will cost zero, $200, $2000... no idea.
Some good news. I just had a user on the RepairShopr FB page tell me he has 16 users and it's actually $20.00 per user per month not $200.00.
I can't be the only person who has noticed this. Very odd for them to have a typo like this.
Maybe they try to get away with it? I mean it's an absurd typo IMO
-
From RepairShopr:
"Thank you for using RepairShopr.
The correct amount is $110/year per additional user.
I have documented the issue and forwarded it to the development team to look further into why the Add a Paid User page is showing $220/month.
The Buy Credits / Add Ons "Additional Users" page does show the correct $110/month pricing for your account. You can go to that page and purchase the additional users and then add their details via the Users page."
-
@CCWTech said in MSP Helpdesk Options:
From RepairShopr:
"Thank you for using RepairShopr.
The correct amount is $110/year per additional user.
I have documented the issue and forwarded it to the development team to look further into why the Add a Paid User page is showing $220/month.
The Buy Credits / Add Ons "Additional Users" page does show the correct $110/month pricing for your account. You can go to that page and purchase the additional users and then add their details via the Users page."
That's a pretty big typo, lol.
-
@notverypunny said in MSP Helpdesk Options:
@vhinzsanchez said in MSP Helpdesk Options:
Had deployed SW on-premise in my previous employment, I do not know how it will fare out after reading the news earlier. It has been rock solid even when others had an issue logging in when a problem struck...it seemed that my installation was not affected then.
I've tried and really liked osTicket but I am now testing GLPI. I was looking into a ticketing system with inventory and the features which tied the ticket to a person and/or hardware and keep its history (like SW). GLPI with FusionInventory seemed to be just that.
Let me know if you need any help, I've been dealing with the inventory side of that combo for going on 3 years now. Going to be getting more into the data-center / server room management side of it with the management and financials stuff next week.
Yup, the network scanning inventory (fusion inventory) is where I stopped at. I have installed agent on 2 computers successfully but as it seems, it was not updating. It was not due to how it was programmed, rather, it is due to my limited understanding on how to configure it.
Another wall I hit is that all emails (new tickets and responses) have different time-stamp (15 hours late).
-
@vhinzsanchez said in MSP Helpdesk Options:
@notverypunny said in MSP Helpdesk Options:
@vhinzsanchez said in MSP Helpdesk Options:
Had deployed SW on-premise in my previous employment, I do not know how it will fare out after reading the news earlier. It has been rock solid even when others had an issue logging in when a problem struck...it seemed that my installation was not affected then.
I've tried and really liked osTicket but I am now testing GLPI. I was looking into a ticketing system with inventory and the features which tied the ticket to a person and/or hardware and keep its history (like SW). GLPI with FusionInventory seemed to be just that.
Let me know if you need any help, I've been dealing with the inventory side of that combo for going on 3 years now. Going to be getting more into the data-center / server room management side of it with the management and financials stuff next week.
Yup, the network scanning inventory (fusion inventory) is where I stopped at. I have installed agent on 2 computers successfully but as it seems, it was not updating. It was not due to how it was programmed, rather, it is due to my limited understanding on how to configure it.
This should be set and forget so long as you're installing as a service (or daemon if *nix) and your configuration file / registry entries are good.
Another wall I hit is that all emails (new tickets and responses) have different time-stamp (15 hours late).
Sounds like a possible issue with the php timezone config on your server
-
@notverypunny
For the love of me, yes, it did update. Never expected that. When I was testing previously, it seemed it did not. Checked the latest software I installed and it did get it.
Perhaps it just took time like the other workstation which was inventoried yesterday but not today.
Also have difficulty in setting up network scan and SNMP. No previous experience here.
Adding task, job configuration, targets, actors, etc, all foreign to me. -
There are a few touchpoints for SNMP scanning and inventory.
- setup and associate your ip ranges and snmp credentials in the plugin's network tab
- configure a task / job and associate it with one of your deployed nodes (typically the server)
- if things don't work, debug in command line from the server, hope you're using linux as it's much simpler to use for this. There might be additional perl dependencies if you're trying to use snmpv3. You might need to use an snmp testing tool from your workstation to validate that the devices are replying to the snmp values that you're using.
-
@kamidon said in MSP Helpdesk Options:
I've used Spiceworks and then Zendesk.
I LOVE Zendesk.
It's simple, well priced, and very fast!
Survey system, reporting, customization available, etc etcThese guys just spammed me through LinkedIn paying to send me a spam conversation. So they are out of the question now. That's totally not okay behaviour, that's what those Indian offshore "hire an app developer" businesses do.
-
@scottalanmiller please post screenshots
-
@VoIP_n00b said in MSP Helpdesk Options:
@scottalanmiller please post screenshots
Oh sorry, I reported them as spam and it auto-deletes to hide LinkedIn's shame.
-
Oh, found it in spam...
-
@scottalanmiller This was reoccurring or happened once?
-
He's not in my contacts. But paid to get the message to me which is crazy annoying.
-
@DustinB3403 said in MSP Helpdesk Options:
@scottalanmiller This was reoccurring or happened once?
once, but he isn't a contact or asking for a contact. Just blind spam.
-
@scottalanmiller said in MSP Helpdesk Options:
once, but he isn't a contact or asking for a contact. Just blind spam.
I didn't think random people could just message you, outside of the "<so and so> wants to connect" messages.
-
@DustinB3403 said in MSP Helpdesk Options:
@scottalanmiller said in MSP Helpdesk Options:
once, but he isn't a contact or asking for a contact. Just blind spam.
I didn't think random people could just message you, outside of the "<so and so> wants to connect" messages.
Yeah, they can. They literally get to pay LinkedIn to bypass the spam blockers. LinkedIn does tell you that they've done it, so you know that it's spam, but it still goes to your inbox and is spam. That you can pay to guarantee spam delivery is just pure evil. No good company would ever do this.
-
@DustinB3403 said in MSP Helpdesk Options:
@scottalanmiller said in MSP Helpdesk Options:
once, but he isn't a contact or asking for a contact. Just blind spam.
I didn't think random people could just message you, outside of the "<so and so> wants to connect" messages.
@DustinB3403 said in MSP Helpdesk Options:
@scottalanmiller said in MSP Helpdesk Options:
once, but he isn't a contact or asking for a contact. Just blind spam.
I didn't think random people could just message you, outside of the "<so and so> wants to connect" messages.
Yeah it is pretty bad.
-
@scottalanmiller said in MSP Helpdesk Options:
They literally get to pay LinkedIn to
bypass the spam blockersmessage people who aren't connected to. -
@scottalanmiller said in MSP Helpdesk Options:
That you can pay to guarantee spam delivery is just pure evil. No good company would ever do this.
Microsoft is super shady
-
@VoIP_n00b said in MSP Helpdesk Options:
@scottalanmiller said in MSP Helpdesk Options:
That you can pay to guarantee spam delivery is just pure evil. No good company would ever do this.
Microsoft is super shady
Especially in their LI division.
