Creating an Internet Explorer Testing Environment on a Mac

Luke Perrie

I have been a Mac man for a long time. I know some people hate ’em for whatever reason, but I have always found them to be great machines for what I do. The only thing that makes it a little tough when it comes to working on the web though, is the fact that you can’t really test in IE, unless you install something like Parallels Desktops and Windows. That works somewhat, but a copy of Parallels Desktop will run you $79 and Windows can cost you $100 or more. In the end, it costs quite a bit and you can only run one version of IE. That doesn’t really make for a great testing environment, especially when there is a better option out there that is absolutely FREE. I had previously written about Installing Microsoft Explorer 6 on a Mac but recently I discovered a better way of setting up a testing environment for IE thanks to Andrew Odri and Jeff Couturier and their great articles. (All credit goes to them in steering me in the right direction on this one.) There were a few problems I encountered along the way so I thought it would be a good idea to let you know exactly how I got it to work. Here is what you need before we start:

VirtualBox 2.0.6 – Only version 2.0.6 will work for this tutorial.
Q – this make it possible to install 3 versions of IE
Zipeg – to convert the IE files to a format we can use
Internet Explorer – download these three files: IE6-XPSP3.exe, IE7-XPSP3.exe, IE8-XPSP3.EXE

Once you have downloaded everything, install VirtualBox, Q and Zipeg. I’ve broken it down into three sections. First, I’ll show you how to get everything ready. Next I’ll walk you through installing IE with VirtualBox. Then I’ll help make sure everything runs properly. For this tutorial, I’ll use IE6-XPSP3.exe as an example. Afterward, just repeat all the steps below to install IE 7 and IE 8.

1. Change the extensions on IE6-XPSP3.exe from .exe to .zip. 2. Create a sub-folder in your Applications directory called “IE”. 3. Launch Zipeg and drag the IE6-XPSP3.zip file into it for extraction. Extract the .vhd files into the IE sub-folder you created.

4. Open up your IE sub-folder and you will see a folder called “IE6-XPSP3”. Open that folder and you should have a file called “XP SP3 with IE6 2009-Apr.vhd. Rename that sucker something simple like ie6-xpsp3.vhd. 5. Now launch Terminal (Applications => Utilities => Terminal) and type:

/Applications/Q.app/Contents/MacOS/qemu-img convert -O raw -f vpc /Applications/IE/IE6-XPSP3/ie6-xpsp3.vhd /Applications/IE/IE6-XPSP3/ie6-xpsp3.raw

This will take about 5 minutes to process so just wait until your Terminal prompt returns. 6. Next, type:

VBoxManage convertdd /Applications/IE/IE6-XPSP3/ie6-xpsp3.raw /Applications/IE/IE6-XPSP3/ie6-xpsp3.vdi

This will also take a few minutes so just wait for that prompt to return.

Now we need to launch VirtualBox to get the show on the road. Once you have the software opened do the following.

1. Click the New button in the top left to enter the “Create New Virtual Machine” wizard. 2. Click “Next” and enter “IE 6” in the Name field and select “Windows XP” as the OS Type. 3. Click past the next screen until you reach the Virtual Hard Disk page. Click the Existing button and a new window will open. 4. Select “Add”. Browse through your folders to Applications => IE => IE6-XPSP3 and select the .vdi file that we created through our Terminal commands above. You will return to the Virtual Hard Disk page. Click next. 5. You should now be at the Summary screen. Click finish and you will see a selection for IE 6 in VirtualBox.

Now that everything is installed, let’s launch IE 6 and make sure it runs properly.

1. Select IE 6 in the VirtualBox window and click start in the tool bar at the top. Press F8 right away to load Windows into Safe Mode. If it doesn’t load in Safe Mode, just close the window and try again. It will automatically load in Safe Mode the second time around.

2. A bunch of hardware prompts will appear. Just cancel them all. Go to the Start menu and select Run. Type “cmd” to open the command line. 3. Type the following at the command prompt.

cd WINDOWSsystem32drivers
ren processr.sys processr.old
exit

4. Restart Windows. 5. When Windows loads up, close all those popups. Go to the top menu of Virtualbox VM (your Windows window) and select Devices=> Install Guest Additions. Click through the windows. If a warning comes up just click Continue Anyway and move on. When the process is complete, select Reboot Now and click Finish. 6. After Windows reboots, more popup windows will appear. Cancel them all and go to Start => My Computer, right-click and select Properties. The System Properties window will appear. Go to Hardware => Device Manager. 7. Now you will see a list with two items that are not recognized. First, select Batteries => Unknown device and right-click. Disable this because you will never use it. Next go to Ethernet Controller and right-click. Select Update Driver. 8. In the Hardware Update Wizard, select the middle option “Yes now and every time I connect the device” and click next. Click next again to install the driver automatically. Close all your windows. 9. Click on the desktop icon to open Internet Explorer 6.

And there you have it. Repeat the process to install IE 7 and IE 8 so you can round off your testing environment. TIP: If you don’t want to wait for Windows to load each time you open your VirtualBox VM, click the red x at the top on your window and select Save the machine state. Next time you access your IE 6 VM it will be exactly how you left it.

WordPress maintenance vs management is the single most expensive misunderstanding in the WordPress services market, and most agencies actively make it worse.
Quick answer: In the WordPress maintenance vs management comparison, maintenance is the technical upkeep that keeps a site running — updates, backups, security scanning, uptime monitoring. Management includes all of that and adds ownership of the site’s direction and performance. Maintenance keeps the site alive. Management is accountable for what it does.
Most providers reduce WordPress maintenance vs management to two tiers sitting side by side on a pricing page. Pick one.
That framing is wrong, and it is why so many businesses sign a contract expecting one thing and receive the other. Maintenance and management are not siblings. Management is the superset that contains maintenance. Every genuine management engagement includes the full maintenance task list. No maintenance plan includes management.
Get the WordPress maintenance vs management decision wrong and you end up with a site that is perfectly updated, perfectly backed up, perfectly secure — and going nowhere.
WordPress maintenance vs management at a glance
WordPress Maintenance WordPress Management
Core question Is the site working? Is the site working for the business?
Posture Reactive and scheduled Proactive and strategic
Who decides what changes You do. The provider executes. The provider recommends. You approve.
Scope Updates, backups, security scans, uptime monitoring Everything in maintenance, plus performance, content, SEO, conversion, roadmap
Monthly deliverable A completed-tasks report A performance report with recommendations
Measured by Uptime, patch currency, backup success Traffic, rankings, conversions, revenue
Accountable for outcomes No Yes
Typical US cost $50–$200/mo $250–$2,000+/mo
If you skip it The site breaks The site quietly stops competing
WordPress maintenance vs management: the 7 critical differences
Seven differences do the real work in WordPress maintenance vs management. Everything else is a variation on them.
1. Detection. Under maintenance, you notice problems first. Under management, your provider does.
2. Decision-making. Maintenance executes your instructions. Management forms its own recommendations.
3. Accountability. Maintenance is accountable for tasks completed. Management is accountable for business outcomes.
4. Scope boundaries. Maintenance has a fixed task list. Management has a roadmap that changes with your goals.
5. Reporting. Maintenance reports what was done. Management reports what happened and what to do next.
6. Judgement. Maintenance keeps your existing plugins updated. Management questions whether you should be running them at all.
7. Direction. Maintenance preserves the status quo. Management moves the site somewhere.
What WordPress maintenance actually covers
WordPress maintenance is the recurring technical work required to keep an installation secure, current and available. Whether you run the list in-house or buy WordPress maintenance services from an agency, that list barely changes month to month:
Core, plugin and theme updates, staged and tested before they touch production
Offsite backups with periodic restore tests — an untested backup is a guess
Security scanning and malware monitoring, plus firewall rules and login hardening
Uptime monitoring with alerting
Database optimisation — post revisions, expired transients, orphaned tables
Broken link and 404 monitoring
PHP compatibility checks ahead of host-forced version bumps
A monthly report confirming what was done
That is the whole category. It is genuinely valuable and genuinely finite.
The defining characteristic is that the provider is not deciding anything. If your plugin roster is wrong, maintenance keeps the wrong plugins updated. If your homepage does not convert, maintenance keeps a non-converting homepage online with excellent uptime.
What WordPress management adds on top
Management contains the full maintenance list, then adds responsibility for direction and performance. That is the line between buying a maintenance plan and buying website management services: one keeps the site current, the other is answerable for what it achieves.
You cannot manage a site you are not maintaining. You can absolutely maintain a site nobody is managing — and a great many businesses are doing exactly that.
Management adds performance ownership, content and publishing, SEO oversight, conversion work, roadmap planning, vendor coordination, and reporting that ties site metrics to business outcomes.
The one test that settles WordPress maintenance vs management
Ignore the feature list. Ask one question:
When something on your site should change, who notices first?
Under maintenance, you notice. You find the broken contact form when a customer complains, email your provider, and they fix it — billing you if it falls outside scope. Detection sits with you. That is not a failure; it is how maintenance is designed.
Under management, your provider notices, and comes to you with a diagnosis before you have seen the problem.
Detection order matters more than response time. If your provider’s first awareness of a problem is your email, a two-hour response SLA is irrelevant. The delay already happened, and it was measured in days.
Why “my host handles updates” is dangerously wrong
This is the costliest misunderstanding inside the WordPress maintenance vs management question, and the documentation is partly to blame.
Plugin and theme auto-updates are off by default in WordPress. The explicit statement lives on make.wordpress.org rather than user-facing docs. There is a setting called plugins_auto_update_enabled that defaults to true, which is easy to misread as auto-updates being on. It only controls whether the interface elements display.
More significantly: any plugin or theme not hosted in the WordPress.org directory receives no automatic updates at all. The update check is a single request matched by directory slug, so a commercial product produces no result. If you run a premium theme or paid plugins — and most business sites do — that entire portion of your attack surface is invisible to every automatic mechanism in the platform.
The scale is not small. Patchstack recorded 11,334 new WordPress vulnerabilities in 2025, a 42% year-on-year rise, with 91% in plugins. (Patchstack, State of WordPress Security in 2026)
Here is why that lands on the management side of the WordPress maintenance vs management line. Patching on schedule is a checklist task. Deciding which plugins are worth their attack surface, keeping a tracked manual process for every commercial product the auto-updater cannot see, and noticing when a vendor has abandoned a plugin — those are judgement calls. No checklist produces them.
One honest caveat. The widely repeated claim that plugin vulnerabilities cause most WordPress compromises is not currently sourced. The 91% figure describes the vulnerability catalogue, not breach causes. The most recent hacked-site telemetry, Sucuri’s 2023 report, found 13.97% of compromised sites had a vulnerable component present — presence, not cause. Meanwhile Wordfence blocked 55 billion password-hacking attempts against 48 billion vulnerability-targeting requests in 2024, and both vendors name stolen credentials as the rising intrusion source. (Wordfence, 2024 Annual WordPress Security Report)
Which is itself the argument. Maintenance patches. Management looks at where the evidence points and fixes your credential controls too.
WordPress maintenance vs management in five real scenarios
Scenario Maintenance only Full management
Critical plugin vulnerability disclosed Patched next scheduled cycle Identified, staged, tested, deployed — including commercial plugins no auto-updater reaches
Traffic spike overloads the server Site slows; you hear it from visitors Load monitored, resources scaled before users notice
Rankings decline over three months You find it in Analytics weeks later Flagged in the monthly report with a fix
Contact forms stop capturing leads You find out when prospects stop calling Conversion tracking catches it and escalates
Seasonal campaign needs a new feature You request a quote; billed separately Proposed proactively as part of the roadmap
That is WordPress maintenance vs management in practice: maintenance keeps the engine running, management drives the car somewhere.
Where hosting and support fit into WordPress maintenance vs management
Managed WordPress hosting covers the server: infrastructure uptime, server-side caching, platform security, sometimes automatic core updates. It does not cover anything inside your install. If a plugin update breaks your checkout, your host will tell you that is not their problem.
WordPress support services are reactive help on request. Something breaks, you open a ticket, someone fixes it. Support is measured in response time. Maintenance is measured in prevention.
The clean hierarchy:
Hosting — where the site runs
Maintenance — keeping what runs healthy
Support — fixing what breaks
Management — all of the above, plus deciding what should change and owning the result
WordPress maintenance vs management: which does your business need?
Your decision is not which to pick. It is how far up the hierarchy your site needs to go.
WordPress maintenance vs management: choose maintenance when…
The site is primarily informational, changing infrequently
It is not central to lead generation or revenue
Someone internal can handle edits and recognise breakage
You accept being first to notice problems, because the stakes are lower
Paying management rates here is a waste. Buy good maintenance and spend the difference elsewhere.
WordPress maintenance vs management: choose management when…
The site supports lead generation, ecommerce or donations
Downtime or slow performance has material financial impact
You cannot describe the site’s roadmap for the next year
Multiple integrations create dependencies nobody is watching
Nobody internally owns the site’s performance
This is the most expensive gap we see: a site receiving excellent maintenance, no downtime in two years, and not one ranking position gained. The provider did nothing wrong — nobody asked them to.
If you are losing leads because something broke and nobody noticed for days, you do not have a maintenance problem. You have a management gap.
Start with maintenance, upgrade later when…
You are early, budget is tight, and the site is not yet a primary channel. Set a trigger and revisit. The mistake is not starting with maintenance — it is staying there for four years while expecting management outcomes.
Five questions that settle WordPress maintenance vs management before you sign
Who decides what changes on my site? “You tell us” means maintenance.
How do you detect issues, and how fast? Management describes monitoring, alerting and SLAs.
Do you test updates in staging first? Lower tiers push straight to production.
What is in the monthly report? Completed tasks is maintenance. Metrics with recommendations is management.
What is out of scope, and what does it cost? A provider who cannot answer quickly has not thought about it.
Red flags
A plan marketed as management, priced at maintenance rates, with no strategic work
No proactive monitoring beyond a basic uptime check
No tracked process for commercial plugins and themes
The provider has never contacted you first. You always initiate.
Audit which side of WordPress maintenance vs management you are paying for
Review the last three issues. Did your provider flag them, or did you?
Check six months of reports. Tasks, or metrics with recommendations?
Count your commercial plugins and themes — those get nothing automatically.
Map the site’s business role. Revenue or leads means maintenance alone is insufficient.
Match spend to need. Do not overpay on a brochure site; do not underpay on a revenue site.

WordPress maintenance vs management FAQ

What is the difference between WordPress maintenance vs management?

Maintenance is scheduled technical upkeep — updates, backups, security scanning, uptime monitoring. Management includes every maintenance task and adds ownership of performance, content, SEO and business outcomes. Maintenance sits inside management rather than beside it, which is why every management plan includes maintenance but no maintenance plan includes management.

Is WordPress management the same as managed WordPress hosting?

No. Managed hosting is a server product covering infrastructure, caching and platform security. Management is a service relationship covering everything inside your site, including strategy. You can have both, and most active business sites should.

How do I know which one I am currently buying?

Over the past six months, has your provider contacted you about a performance decline or a ranking drop before you noticed? Do reports contain recommendations, or only completed tasks? If the answer to both is no, you are receiving maintenance regardless of what the invoice says.

Can I start with maintenance and upgrade to management later?

Yes, and many businesses should. As traffic and revenue dependence grow, the cost of nobody noticing problems first grows with them. Most providers offer stackable tiers that make the transition straightforward.

How much does WordPress maintenance cost compared to management?

In the US market, WordPress maintenance plans typically run $50–$200 per month. Management generally starts around $250 and rises with scope, commonly reaching $1,000–$2,000 where the provider owns SEO, content and conversion work.

Why is maintenance important if my host already does updates?

Because plugin and theme auto-updates are off by default in WordPress, and anything outside the WordPress.org directory receives no automatic updates at all. Most business sites run at least one commercial theme or paid plugin, so the platform’s automatic machinery cannot reach a meaningful part of the attack surface.

Can I maintain my WordPress site myself?

Yes, and for a simple site it is reasonable. Budget two to four hours a month. The failure mode is not incompetence — it is the third consecutive month where something more urgent came up.

How quickly should a provider notice and respond?

With proper monitoring, critical issues should be detected within minutes and a six-business-hour response is a reasonable benchmark. But detection matters more than response. If your provider’s first awareness comes from your email, the delay already happened.

In WordPress maintenance vs management, what happens if I only pay for maintenance?

The site stays secure, current and online. It will not improve. Over two or three years, competitors actively managing their sites will out-rank and out-convert you, and your maintenance reports will show green the entire time.

WordPress maintenance vs management: the short version

The WordPress maintenance vs management question comes down to this: maintenance answers “is the site working?” Management answers “is the site working for the business?” One is contained inside the other, and confusing them is the most common reason businesses feel let down by a provider who is technically delivering exactly what was purchased.

Work out which question you need answered, then buy accordingly.

Luke Perrie

Small Biz Website Tips Newsletter

Stay up to date with the latest marketing, sales, and service tips and news.

Small Biz Website Tips Newsletter

Stay up to date with the latest marketing, sales, and service tips and news.

	WordPress Maintenance	WordPress Management
Core question	Is the site working?	Is the site working for the business?
Posture	Reactive and scheduled	Proactive and strategic
Who decides what changes	You do. The provider executes.	The provider recommends. You approve.
Scope	Updates, backups, security scans, uptime monitoring	Everything in maintenance, plus performance, content, SEO, conversion, roadmap
Monthly deliverable	A completed-tasks report	A performance report with recommendations
Measured by	Uptime, patch currency, backup success	Traffic, rankings, conversions, revenue
Accountable for outcomes	No	Yes
Typical US cost	$50–$200/mo	$250–$2,000+/mo
If you skip it	The site breaks	The site quietly stops competing

Scenario	Maintenance only	Full management
Critical plugin vulnerability disclosed	Patched next scheduled cycle	Identified, staged, tested, deployed — including commercial plugins no auto-updater reaches
Traffic spike overloads the server	Site slows; you hear it from visitors	Load monitored, resources scaled before users notice
Rankings decline over three months	You find it in Analytics weeks later	Flagged in the monthly report with a fix
Contact forms stop capturing leads	You find out when prospects stop calling	Conversion tracking catches it and escalates
Seasonal campaign needs a new feature	You request a quote; billed separately	Proposed proactively as part of the roadmap