While you’re there, you should also have out David Walsh’s ebook, Source Control. As David says, “if you’re not outsourcing, you’re either about to get crushed by someone who is, or wasting time on worthless tasks.”

Nowhere in my mind is this more true than in the MSP market where we’re now at MSP 2.0. Everybody is using the same tools and price is now becoming a differentiator – ultimately, cost pressures are going to go up and outsourcing the routine, mundane, boring and specialized tasks is a smart way to cut costs. Outsourcing is hard, but David’s book really helps simplify the process.

No related posts.

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

I’ve seen MSPs burn hours applying customized monsets to monitor server disk drive space for different drive letters. Here’s how I do it, simple and effective:

1. I use the in-built disk space alert and set this to alert at 3% free

I find 3% gives me the right balance to capture low disk alerts for both big and small disks.

Unfortunately, this alert only works after a latest audit is done on a server. I like to schedule my server latest audits nightly, but still, a nightly check of disk space is hardly realtime monitoring.

My main motivation behind using the inbuilt monitoring for disk space is to capture instances where no monset has been applied for disk space monitoring or the monset has stopped capturing data for whatever reason.

2. I use a single disk space monset that monitors free disk space on all drives.

I have a single monset that monitors all disk drive instances for both % free and GB free.

Again here, I trigger an alert at 3% disk space free or less and also at 2.5GB free or less. Once more, using a combination of % free and GB free gives me a good balance for coverage of a variety of disk drive sizes.

Not that here I use the *ALL instance which allows the set to monitor for all disk drive instances. Once the set is applied to servers Kaseya seems to do weird things and modify the monset itself and add drive letters to the monset. This will cause the monset to attempt to capture data for drives that do not exist but I figure no harm done, I rather that than not monitoring drives at all because a tech missed a monset.

What’s your feedback? Any other ways you’re monitoring disk space?

Related posts:

1. A smarter way to handle Kaseya Low Disk Space Alerts for PCs It still amazes me the volume and number of...
2. Editing Kaseya “INDividualized” & Standard Monitoring sets made by another admin Ever had to edit another admin’s IND monsets on...

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

I’m really excited about the new iPad revealed last week. In fact, I’m really excited about Apple in general at the moment. A month ago I made the switch to a Macbook Pro fulltime because I’ve simply had enough of Windows. Win7 is simply too little too late. The elegancy and performance of Mac OS wins hands down every time. I love my new MBP…its just ridiculously fast compared to my old Windows notebook.

A growing trend towards Apple hardware in the SMB/SME space…

Talking with a few different clients over the past fews months, I’ve noticed a new trend occurring. CEO & Exec level staff at companies they support are heavily leaning towards iPhone and ditching their old Blackberry handsets. A lot of these guys have also ditched their Windows notebooks in favour of a Macbook (granted a lot are still running Windows on top of Parallels or VMware). Staff working for these MSPs seem to be moving towards Apple too opting to use their own personal MBPs at work too.

So here’s the thing, 2-3 years ago, many MSPs wouldn’t have even thought of supporting Apple machines or equipment. 18 months ago – many were forced into a position where they had to. Sure, the majority of machines on networks they managed were Windows boxes with a couple of Macs so not a big deal. Today, if the CEO of a SME business you support is ditching his beloved Blackberry and Windows notebook for an iPhone and Macbook Pro, you can be certain than 18 months down the track, he’ll be much more inclined to look at rolling out more Apple machines in that business.

MSPMentor could only find 1 Mac MSP firm?

So here’s the opportunity that I don’t think anyone in the MSP sector is really leveraging except maybe for these guys: MSPMentor.net found an Apple friendly MSP firm
Build some internal capability to support Mac machines and start promoting yourself as a capable Apple & Mac support provider.

At a time when the MSP market is becoming heavily commoditized, you need something to help you stand out from the rest and here is something that’s really simple. A lot of MSPs shun Macs because they don’t need much (any?) maintenance, rarely need patches and simply just work. The reality is, users need support regardless of what machine they’re running. The fact that Macs need significantly less maintenance than a Windows box is even more reason why you should be pushing into this vertical market.

Would love to hear your take on supporting Macs….post in the comments.

Related posts:

1. Social Media:Are you missing a massive opportunity? Social media is a massive opportunity for any business –...
2. New site theme & mobile support I finally got around to implementing a mobile version of...
3. Couple of great MSP resources I’ve been hearing quite a lot about Gary Pica and...

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

If you use Google Analytics on your website (and you should be), you’ll notice that one of your highest ranked search terms is likely to be your business name. People are just too lazy to type your full web address so will rely on search to find it. Guess what, this is the same for almost all other bricks and mortar businesses on the web.

So what’s the sneaky trick? Well simple, add your competitor company names and domain names into your list of keywords. Then when their clients or more importantly, potential clients search for their company name, up comes your company at the top of the search results right next to theirs.

Related posts:

1. How to improve the effectiveness of your Google Adwords Campaigns I LOVE GOOGLE ADWORDS! I think adwords is fantastic....

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

**the link needs to be for something tech or MSP related….no link spam merchants!

No related posts.

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

I’m keen to hear about Dean Wilson’s experience and have signed up.

Check it out here – drop me a line on Twitter if you’re going and say g’day when you’re there.

No related posts.

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

If you’re looking to improve your marketing and sales efforts you should check them both out at the links below or in the Kaseya Resources section in the sidebar.

From Gary’s site:
FormulaWon gives you the tools you need to take your business to the next level. It covers leadership; packaging, pricing and delivery; sales; and performance tracking because those are the 4 key factors that make the difference between the MSPs that make it and those that don’t.
Gary Pica – TruMethods.com

From Robin Robins site:
“My Technology Marketing Toolkit Takes the Mystery and Hard Work Out of Marketing Your Business, Attracting New Clients, and Selling Profitable Managed Services Contracts”
Robin Robins – TechnologyMarketingToolkit.com

Any other good MSP business or marketing resources out there? Drop me a line in the comments and let me know!

EDIT: as commented by Brendan Cosgrove, Stuart Selbst also does some great work coaching MSPs towards profitability and success!

http://www.stuartselbst.com/

Excerpt from his site:

Stuart now owns Stuart Selbst Consulting, a consulting firm which offers an executive coaching along with other business development programs that align sales and marketing together with business processes along with the practice of goal setting to achieve individual and team success.

No related posts.

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

I’ve been using the Application Blocker feature of Kaseya for quite some time to block Peer-2-Peer apps from running on end user machines. I can’t take credit for this idea as the idea was thrown about on the Kaseya forums about 18 months ago and seems to have recently resurfaced.

Peer-2-Peer apps can be a nightmare in a multi-branch environment where Terminal Services and Citrix are in use when they hammer all available bandwidth. Yes it’s possible to block installation of these apps by restricting user rights on desktops. Often, in many environments this is not possible or realistic because proprietary apps may need full admin rights, or the staff roam overseas regularly and need full access to the machine or staff own the machines and you have limited scope for locking them down. Those vague helpdesk calls about “the entire branch running slowly” can simply be a nightmare to diagnose at times and worse, burn through consulting resources. The Network Statistics report can often help pin down the problem but this isn’t always the case.

So anyway, if you didn’t know already. Kaseya has an Application Blocking feature that I use to block P2P apps from running which completely removes any problems generated by them. Here’s how I configure my Peer-2-Peer application blocking in Kaseya. This method also allows you to generate reports of what machine the apps were blocked on so you can go back to the client and demonstrate more value and identify problem users if necessary. Setting up this process will take you around 10 minutes or so depending on how familiar you are with the system.

Part A – setting up the blocking

1. Create an Offline Agent

(I use an Offline Agent to apply the settings as its much easier than typing in 20 odd applications by hand, use an Offline Agent template and you’ll only have to type in the list once)

• Goto the Agent Tab->Create
• Create an offline agent in your _templates group. Call this something meaningful like P2P-blocking-template or similar.

2. Load up the Peer 2 Peer apps you want to block in the application blocker section.

My list below hasn’t been updated in a while but works for me, it also includes a few spyware apps that have caused me headaches in the past.

• Go to the Audit Tab->Application Blocker in bottom left hand corner
• Enter the list below one by one and apply to your new template (apologies about the inability to cut and paste, trying to keep this short!)

braviax.exe   bitlord.exe   g3torrent.exe   klrun.exe   peravir.exe   btdownloadgui.exe   btmaketorrentgui.exe   azureus.exe   emule.exe   pctstray.exe   buritos.exe   av2009.exe   napster.exe   edonkey2000.exe   morpheus.exe   shareaza.exe   limewire.exe   bearshare.exe   kceasy.exe   gnucleus.exe   kazaa.exe   ares.exe   utorrent.exe   warez.exe   khancer.exe   bitcomet.exe

3. Apply the blocking to the agents you want it active on.

• Goto the Agent Tab->Copy Settings
• Make sure you change your Machine Group and View to show the machines you want to apply the blocking on.
• Select your source template to copy the settings from – IMPORTANT here to only copy the Protection Settings, choose to either Add or Replace settings. Use Add if you already use protection settings
• Apply the settings and copy, this should only take a moment to apply

Once step 3 is complete, Application Blocking is now in place and Kaseya will block P2P executables from starting – this is great, but to demonstrate real value, we need to create end user reports which we’ll do in Part B

Part B – setting up reporting

1. Create a script to write to the Kaseya Script log

To create end user reports, we trigger a Script to run every time a P2P app is block. The script writes to the Kaseya script log which we can then create a custom report to determine which machines a trigger the Peer 2 Peer blocker. That make sense?

• So, create a new script, call it “P2P App Block Log Script” or something that makes sense to you.
• Then add a single line with action Write Script Log Entry the write Illegal P2P Application Blocked Application: #pv# to the log.
  The #pv# writes the executable name of the app blocked. If you want to get fancy, you could modify this script to also write the username of the user at the time of the blocking to the log also – for simplicity sake, we’ll leave it as is for now.

2. Configure Protection Violation Alerting

We perform this step so that Kaseya auto triggers our new script whenever it blocks a P2P app.

• Again here, change the Machine Group and View to show the machines you want to setup reporting on and goto the Monitor Tab>Alerts
• From the dropdown, select Protection Violation.
• From the three checkboxes, we only need to select “File Access Violation Detected”  and you want to select the action to Run Script when triggered. Select your newly created P2P App Block Log Script and then apply the settings to the machines.

3. Configure a Custom Report

• Head to the Reports Tab>Logs
• Here you want to create a new Script Log report, click the checkbox to Ignore Machine without data
• In the “Show entries matching….” dialog box, enter this string and make sure you keep the asterisks: *Illegal P2P Application Blocked*
• Once done, give the report a meaningful name, share it if you want to and click save and you’re done.

If you run the report straight away, you’re probably not going to get any data show up but leave the monitoring for a day or day and come back and run the report. You’ll be surprised at how many machines trigger the blocking.

So give it a try, see how you go – if you get stuck or need help, feel free to post in the comments and I’ll reply as best as possible. Have fun!

Related posts:

1. Custom View to show only Domain Controllers in Kaseya On the Yahoo Kaseya groups last week somebody posted...

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

One of my clients attempted to resolve this problem and in their NOC/helpdesk they run a custom built dashboard solely dedicated to server offline alarms, but they found a couple of major problems with this:

1. Consultants are busy and it may be 10+ minutes before they glance up at the dashboard and pickup on server down alerts – generally the client has called in before that anyway
2. Consultants are based in multiple states and whilst not located at the NOC, many of these consultants may be assigned to helpdesk and NOC duties – without direct access to this dashboard, remote consultants found it difficult to track server offline alerts.

A Desktop Alert tool for Kaseya?

This clearly wasn’t good enough with over 400 servers under monitoring. So, in conjunction with this client, we developed a desktop application to alert their consultants in realtime when a server goes offline – the consultants are alerted via a popup and audible alarm. The solution has been working well for the past few months with a few refinements and iterations to the tool. (Sorry, no screenshots available as contains the client’s branding which they do not want made public)

They’re now at the stage where they want to expand the capability and flexibility of the tool. They’ve plonked down some cash to get the tool built and figure that the tool has worked well for them so surely there’s other MSPs who could benefit. So right now, they’re looking to offset the cost of software development by commercializing the tool and sharing with the community – that’s where you come in!

Register your EOI in the comments section…

Before creating a formal EOI for the tool and investing a heap of time into the project, we want to know whether you as an MSP would be interested in such a tool and if so, please post in the comments. If we get enough traction in the comments section over the next 30 days we’ll open up a formal EOI and get started on the project. We’ll be looking to a freemium model for the tool, with the free version limited in some way, most likely ad driven and the pro/premium version and pay per license monthly subscription model (no more than a couple of bucks per month per user).

So, what do you think? Could this be useful in your MSP business?

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.