I’m getting a least a couple of emails every month asking about building custom Kaseya reports.

Kaseya reporting out of the box can be nasty and in my opinion K2 took a backward step on a handful of reporting features (a step forward in a lot of ways too!)

I’ve seen a bunch of different SQL Reporting Services custom jobs around Kaseya reports which can work well if you’ve got inhouse SQL Reporting skills.

If you don’t have the time or patience and want to invest your resources into something that actually makes money, checkout Brightgauge.com

www.brightguage.com or hit them up on twitter @brightgauage – twitter.com/brightgauge

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

For those that haven’t heard of Ninite before, its a tool that enables you to prepackage autoinstallers for common apps, quickly, easily and without digging around for a bunch of command line switches – well worth checking out at Ninite.com

Auto-update common apps

The guys at Ninite have released a new feature whereby Ninite can auto-update third party apps if they’re already installed. There’s also the ability to do some reporting on installed apps and whether or not they can be updated automatically.

Haven’t had a chance to play with the new feature as yet but more info on the update is available on their blog, go check it out! – blog.ninite.com

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

If you’ve read my “About” page on the site you’ll know in a former life I ran an online retail store. That business grew extremely rapidly through leveraging online marketing techniques, primarily SEO & old school social media. I now do ongoing consulting for a handful of online retail stores helping them with building their businesses online.

How-to Marketing stuff for MSPs

After reading Mike Cooch’s latest blog post he does paint a pretty clear picture of how badly MSPs market and sell themselves. While there’s plenty of technology to help MSPs do business better there’s only a handful of people that MSPs can turn to for marketing and sales advice. If you don’t know the big ones, I’ve listed them below (please add any I’ve missed to the comments and I’ll update this post):

Gary Pica

Robin Robins

Kutenda

Stuart Selbst

I figure that I might as well pitch in and share the love so over the next few months I’m going to rollout some posts around online marketing and see how they’re received – I think the guys above have the strategy stuff pretty well covered so I’m going to share some tactics, more “What To Do” and “How To Do it” around online marketing. Some of it is common-sense mainstream online marketing stuff, some of it you’ll only know about if you’re heavily in the online marketing space, either way, looking at some of the MSP websites in the MSPMentor top 100 list, most MSPs have implemented neither.

Brightgauge.com – an up & coming tool to keep an eye on

I tweeted this out the other day, if you missed it then this is one to keep an eye on, particularly for newer MSPs who are still feeling their way around Kaseya’s reporting engine.

Check out www.brightgauge.com which is scheduled to launch in Jan 2011

Basically, its a dashboard and reporting tool that sits over the top of Kaseya & Connectwise…like they say in their website copy, this could be an invaluable sales tool!

Kaseya2 upgrade – time to upgrade now

I’ve had a lot of emails come through this month about Kaseya 2, is it any good? should I upgrade? what should I watch out for? – I figure that everyone has been working through their todo lists in the leadup to Thanksgiving and looking to get some of the bigger action items ticked off the list.

The quick answer is upgrade now!

My experience now is that K2 is as stable as its ever going to be and the scheduling engine and some of the improvements now make this a really worthwhile upgrade. Kaseya has done a good job ironing out the bugs and apart from general support stuff, I haven’t really seen any major issues for a few months now.

The new 6.1 version of the VSA is also due out soon and the improvements scheduled for the new .1 upgrade will leave MSPs who’ve haven’t upgraded at a disadvantage. I’m sure 6.1 is going to have some bugs so if you haven’t bitten the bullet and moved to K2 I say do it now, iron out the bugs over the holiday period when things should be fairly quiet and then look at the 6.1 upgrade towards end of Q1 next year.

If you have an K2 upgrade feedback, please share in the comments!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Subscribe by emailing KaseyaScripts-subscribe AT yahoogroups.com

Here’s a great app/tool Yan from Jointtech posted about this week: Ninite.com for creating scripted autoinstallers….timely post for me as I need to create some Irfanview deployment scripts today.

Also loved this comment re the Video chat in K2: “P.S. I find my guys use video chat way more often with the younger hotter employees of my customers. Can’t really blame them either. Some of them are gorgeous. ”

Know any other tools the community could benefit from? Post a link in the comments

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

I’ve been on the road for a bit involved with various projects over the last couple of months and have been insanely busy so very few updates from me.

Thought I’d post a quick one anyway particularly for those who aren’t subscribed to the Yahoo user groups for Kaseya.

Couple of quick links to:

Kaseya 2008 Script pack for Kaseya 5 – several hundred scripts to do various things in Kaseya

K2 Script pack – handful of new scripts for K2

Enjoy!

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

It annoys me that AVG Corporate has such a bad name/reputation in the wild because of its association with AVG Free. As such, several MSPs I work with want to keep the AVG name away from users as much as possible. One of the options when rolling out KES is to setup a Windows Explorer shell extension – you know where you right click and choose “Scan with AVG”

There’s no way to undone this from the KES Management console once you roll out machines with it. So here’s the Kaseya script (v5.1) that does it – pretty simple, just delete the regkey and it disappears immediately. You should be able to straight copy and paste this into the script import window:

Script Name: AVG/KES/Managed AV - Disable Shell Context Menu
Script Description: This script disables the shell context menu that shows the "Scan with AVG" menu item when right clicking in Windows Explorer.
Script by Tullibo.com

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

So if you follow me on twitter you’ll have seen my rant I had a few days ago about AVG9 problems and server freezing & crashing along with some stuff directed to @kaseyacorp re actively notifying clients of known issues.

Starting at the beginning – I’ve been working with a client on a Netware & Groupwise to Windows & Exchange 2010 migration. It’s in the final steps and we’re in the process of unplugging the old Netware gear and cleaning up minor tasks left behind.

The solution is a combination of data centre hosted VMs and a physical box onsite. Its been a difficult migration but all has been working well for a couple of months until the Exchange box locked up about two weeks ago, *almost* unresponsive. The weird thing was, mouse movements worked on the console, the box was accepting OWA/webmail connections through a web browser but wouldn’t allow SMTP connections or allow any Outlook clients to connect.

Fair enough, we’d been playing with the VM snapshot backups and VSS and figured it had broken something, hard booted the box and it’s been running fine every since.

I hate weird server crashes

Then comes Monday, the physical box onsite locks up with the exact same problem. Hmmm…coincidence? I think not. What do they have in common? One box is physical, one is a VM, can’t be a VM or hardware issue. Hmmm, both Win2008 boxes, same patch level, could be an MS update problem or Win2008 issue. Both running Kaseya & KES. Well, plenty of other Win2008 + KES servers about but these are missing about 15 odd MS patches since put into production. Lets roll out those badboys and log a case with Microsoft.

Crashedy crash crash crash…

Tuesday rolls around – I get a call in the morning, one of the other boxes has locked up, same problem again. One of the data centre domain controller VMs…..well this is getting awkward, fortunately the client didn’t notice this lockup. Looks like client signoff on this project is going to be delayed until we can work these bugs out.

So MS were completely useless. I logged a case on Monday. They suggested running Windowsupdates and then trying to do a manual memory dump the next time the issue happened. Great! The box isn’t blue screening and is unresponsive when it crashes, how am I supposed to do a memory dump? So, I took matters into my own hands because clearly I’m not getting anywhere in a hurry with Microsoft.

Kaseya agent v5.1.0.10

The client is running Kaseya 5.1 and the agents are at 5.1.0.0 version. Turns out theres an agent version 5.1.0.10 – thanks for the headsup Kaseya! Netter upgrade that agent version.
What else do all three boxes have in common? Hmm…KES/AVG
2 minutes and some snappy Google-izing later, I uncover a well known issue with AVG9 freezing boxes in the exact same manner as the three crashes on these boxes. Check the Kaseya forums, oh yeah, there’s multiple threads about the problem, oh, and with a workaround! Great

I then proceed to apply the workaround and all has been running sweet since.

Communication is key

So here’s my problem. I know that software issues happen. Bugs happen. Shit happens, its IT after all, stuff breaks all the time, we wouldn’t have a job if it didn’t. What really bugs me is that this is a known issue. From what I can see in the Kaseya forums, it’s been a known issue since January! Why then do I:

1-have to wait until this problem happens to me/clients I’m involved with, causing completely unnecessary downtime, stress and client angst
2-have to actively search for the potential existance of this particular problem
3-have to rely on a Kaseya end user workaround to resolve the problem

Selective hearing talking?

One thing that Kaseya is really good at is interacting on twitter. What I don’t get is that they have Twitter, Facebook (i think?), Kaseya forums, a blog, an email list and a knowledgebase and they still can’t advise clients of known issues, problems and their fixes.
For a company who’s primary business is software, this is absolutely beyond belief. Granted I tweeted this out and @cozthegrov @replied me right back and advised that they’re working on this in the Kaseya portal but frankly, I don’t care. For the last 3-4 years Kaseya has happily send me marketing emails at regular intervals, why can’t they have a second email list that advises clients of known issues, workarounds and also things like what the Kserver updates they roll out actually do!

There’s a lot of Labtech ranting on twitter lately and a lot of Kaseya bashing re K2 support…I totally understand the frustration and at the same time think that it’s a lot of noise over nothing and disagree whole-heartedly about the K bashing and labtech ship jumping. On the flipside, I think its time Kaseya got their asses into gear and started acting like a real software company.

Here’s my immediate right now Kaseya wishlist – to me, this doesn’t need to wait for the new Kaseya portal, it needs to happen right now, as in this week:

1-an email list I can subscribe to where I can get notified of known issues & notification of Kserver updates PRIOR to them being auto rolled out
2-ability to subscribe to knowledgebase updates so I get notified when new articles are published
3-a unified front across all Kaseya social media, I current need to watch Twitter, Kaseya Forums and the blog just to stay on top of things, why can’t important updates be published across all mediums?
4-an update on how Kaseya 2 deployments are going and regular updates on bug fixes/issues. With all the noise going on, I’m hesitant to get involved with K2

What are your thoughts?  A lot of noise on the net about K2 support & Labtech at the moment…how’s your Kaseya experience been lately?

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

The Problem…

If you’re familiar with Kaseya BUDR, you’ll be aware that by default, Kaseya password protects the each image file it creates. This works great when you’re backing up data for a client, the image is protected by a password and encryption. The potential for disaster is when you’re using password protection in conjunction with the images of your Kaseya server and SQL backend box.

In the event of a disaster you’re going to need to rebuild one of those boxes or both from a BUDR Acronis image. If you’re protecting that image file with a password and your Kaseya system is down, where are you going to get the password from? You’re stuck, the password is stored in the SQL db somewhere and you have no quick and easy access to it

A simple solution…

So a simple solution to the problem is to either:

• stick the image password for your Kaseya and SQL servers in your doco somewhere; or the second choice (which is probably better for ease of restore during a crisis)
• disable password protection totally for your Kaseya and SQL server images, which you can do from the passwords section on the backup tab. Note that if you reset the password, the next image backup will be a full image backup

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

I actually submitted a feature request to Kaseya ~6 months ago asking them to build a spam blacklist checking feature into Kaseya monitoring – it’s actually a really simple concept and only requires a bunch of DNS MX record lookups and a check through of the results. I was trolling through the forums one day and someone had cooked up a basic spam blacklist script checker. The script was OK but only checked a few blacklists and was a bit buggy so I used the basics of the script and built my own.

Anyway, here it is. It utilises the codebase from the original script I stole plus a couple of scripts available in the Kaseya 2008 script pack. The scripts is actually four scripts, Script 1 does most of the heavy lifting, Script 2 checks the login and scripts 3 and 4 write events to the Windows event log with the appropriate output. I’ve left out scripts 3 and 4 but you can grab these from the Kaseya 2008 script pack.

Not sure how well copying and pasting from the blog post will work – the code is embedded in code tags, if you have any problems, post in the comments and if necessary I’ll dump a couple of .txt files somewhere to download. I haven’t played with this script in detail in ~4-6 months so there’s a chance an RBL or other blacklist used in the script is no longer utilised – the script has been running flawlessly for me and regularly picks up spam problems but please, if you have any feedback, stick it in the comments.

Have fun!

EDIT: Oh, forgot to mention that this script automatically grabs the server gateway IP address from the Kaseya database and uses that for the lookup. In some weird network configurations or where private networks are in place, this may not be appropriate for what the script needs to do as the connection gateway may be a private network address.

Script 1

Script Name: SPAM Blacklist Pt1
Script Description: Script Description: This scripts checks to see if a public IP returns a value that contains 127.0.* from various RBLs and other spam blacklists
RBL DNSBL and other BList sourced from: http://checker.msrbl.com/
Original script taken from pjones on forums.kaseya.com
Mods made to this script by Tullibo.com
http://forum.kaseya.com/showthread.php?t=7954

IF True
THEN
Write Script Log Entry
Parameter 1 : Spam blacklist check started
OS Type : 0
Execute Shell Command
Parameter 1 : ipconfig /flushdns
Parameter 2 : 0
OS Type : 0
Get Variable
Parameter 1 : 10
Parameter 2 :
Parameter 3 : temp
OS Type : 0
Execute Shell Command
Parameter 1 : echo SERVERNAME: #vMachine.machName# - MSP results of Spam List Tests >>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : echo TIME STARTED: %time% >>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : echo DATE RAN: %date% >>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : echo Testing gateway IP address is #vMachine.ConnectionGatewayIp# >>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : echo. >>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.abuse.net >>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.zen.spamhaus.org >>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.list.dsbl.org >>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.nospam.ant.pl>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.bl.spamcop.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dnsbl.burnt-tech.com>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.cbl.abuseat.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dnsbl.njabl.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dnsbl-3.uceprotect.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dnsbl-2.uceprotect.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dnsbl-1.uceprotect.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.cbl.abuseat.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dul.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.zombie.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dnsbl.ahbl.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.bl.technovision.dk>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.bl.csma.biz>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.bl.deadbeef.com>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.list.dsbl.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.multihop.dsbl.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.unconfirmed.dsbl.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dul.ru>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.rbl.efnet.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.korea.services.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.combined.rbl.msrbl.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.phishing.rbl.msrbl.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.virus.rbl.msrbl.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.images.rbl.msrbl.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.spam.rbl.msrbl.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.web.rbl.msrbl.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.no-more-funn.moensted.dk>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.okrelays.nthelp.com>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.relays.nthelp.com>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.psbl.surriel.com>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.rbl.schulte.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.bl.spamcop.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.sbl-xbl.spamhaus.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.xbl.spamhaus.org>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.http.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.socks.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.misc.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.smtp.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.web.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.new.spam.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.recent.spam.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.old.spam.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.spam.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.escalations.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.block.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.zombie.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Execute Shell Command
Parameter 1 : for /f "tokens=1,2,3,4 delims=." %a in ("#vMachine.ConnectionGatewayIp#") do nslookup %d.%c.%b.%a.dul.dnsbl.sorbs.net>>>>#temp#\spam-results.txt
Parameter 2 : 0
OS Type : 0
Get Variable
Parameter 1 : 1
Parameter 2 : #temp#\spam-results.txt
Parameter 3 : spamresults
OS Type : 0
Get File
Parameter 1 : #temp#\spam-results.txt
Parameter 2 : spam-results.txt
Parameter 3 : 1
OS Type : 0
Execute Script
Parameter 1 : SPAM Blacklist Pt2 (NOTE: Script reference is NOT imported. Correct manually in script editor.
Parameter 2 :
Parameter 3 : 0
OS Type : 0
ELSE


Script 2 checks the output and takes appropriate action

Script Name: SPAM Blacklist Pt2
Script Description: Part two of the Spam Blacklist checker.
Don't run this script directly, run SPAM Blacklist Pt1 instead!

IF Check Variable
Parameter 1 : #spamresults#
Contains :127.0
THEN
Get Variable
Parameter 1 : 2
Parameter 2 : SPAM BLACKLIST CHECK RESULT ERROR - GATEWAY LISTED ON BLACKLIST - Gateway IP is #vMachine.ConnectionGatewayIp#
Parameter 3 : error_description
OS Type : 0
Write Script Log Entry
Parameter 1 : SPAM BLACKLIST CHECK RESULT ERROR - GATEWAY LISTED ON BLACKLIST - Gateway IP is #vMachine.ConnectionGatewayIp#
OS Type : 0
Get File
Parameter 1 : #temp#\spam-results.txt
Parameter 2 : spam-result-last-blacklisted.txt
Parameter 3 : 1
OS Type : 0
Execute Script
Parameter 1 : Create Kaseya ERROR Event Log Entry (NOTE: Script reference is NOT imported. Correct manually in script editor.
Parameter 2 :
Parameter 3 : 0
OS Type : 0
ELSE
Get Variable
Parameter 1 : 2
Parameter 2 : SPAM BLACKLIST CHECK RESULTS - ALL OK, not listed
Parameter 3 : error_description
OS Type : 0
Write Script Log Entry
Parameter 1 : SPAM BLACKLIST CHECK RESULTS - ALL OK, not listed
OS Type : 0
Execute Script
Parameter 1 : Create Kaseya INFO Event Log Entry (NOTE: Script reference is NOT imported. Correct manually in script editor.
Parameter 2 :
Parameter 3 : 0
OS Type : 0


No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

Ever had to edit another admin’s IND monsets on your Kaseya server and found you couldn’t?

Here’s the fix…

Quite often, a standard monitoring set needs to be tweaked to accommodate a particular quirk with a server or client site. To me, it’s actually a really great feature to be able to tweak monitor sets as required without having to create a complete monset from scratch.

A problem arises though, if another admin has created a monset that is no longer appropriate or working properly and it needs to be tweaked.

By default, you cannot modify their monset and you can’t delete it either!

Another problem is that an admin will create and apply a monitoring set but not share it so other admins can’t apply/delete/modify that monitoring sets.

I logged a ticket with Kaseya support about this and they came back with a copy of handy SQL commands that will sort these two problems out…..be careful before you unleash this as it will add all the INDividualized monsets to the drop down box in the assign monitoring section (as per the picture above!)

Note that this is only a problem in Kaseya 5, in Kaseya 6, all master admins can see all monitoring sets on the Kserver

Share all IND monitoring sets:

********SQL code starts here************

update monitorset
set shareall = 1
where name like ‘(IND)%’

**************************************

Share ALL monitoring sets:

********SQL code starts here************

update monitorset
set shareall = 1
where shareall != 1′

**************************************

Share ALL SNMP sets:

********SQL code starts here************

update monitorsnmpset
set shareall = 1
where shareall != 1

**************************************

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.