NSIS Error – Error writing temporary file

Solution – copy the installer file into the temp folder and install!

If you are using Windows 7, it’ll probably be this folder by default:
Just copy and paste it into Start – Run.

Took sometime (and dedication) to figure this out, but nothing else worked. Tried changing TEMP and TMP variables and checked permissions etc. Wasn’t about to reinstall Windows. Had plenty of installers using the NSIS (Nullsoft) system install, just this one was giving me grief (WinPcap_4_1_1.exe).

Happy installing!

Hyper-V WordPress Appliance

After my server crash, I moved from Vmware Server to Hyper-V. I wanted to go ESX, but I haven’t got hardware fully support by ESX. Nonetheless, using Hyper-V I’m extremely impressed by it’s speed and reliability.

The problem with Hyper-V is that there is not as many appliances readily available. And those that are available are generally a port of a VMware appliance and not really tested.

I had an issue looking for a WordPress appliance that would work on Hyper-V without too much mucking around as I’m not really a hardcore Linux person. I managed to find a VMware appliance that would port straigh over to Hyper-V with little fuss. It’s the TurnKey WordPress appliance available here: http://www.turnkeylinux.org/wordpress

Just use the StarWind Converter on it to port the vmdk files to a VHD file. Then chuck it into Hyper-V and start it up. Make sure you use the legacy Network Adapter. Everything works error free and without hassle! Great appliance that is ready to go!

Migrating WordPress Blog to new server using same domain name

The import/export feature of WordPress is excellent. The issue is when you choose to import the images/media files and it needs to download them from your old WordPress site. You won’t have an issue if your old and your new site use different domain names (ie. oldblog.fuelip.com and newblog.fuelip.com).

However, if you’re like me and you just want to move from blog.fuelip.com to another server whilst still maintaining blog.fuelip.com then it’s a little more work. You’ll probably find that images may not display properly because WordPress embeds the full path of the image when it’s being uploaded.

Please note that I am writing this blog which details a method I used to get my site across. There may be alternative ways/easier ways, but this worked for me and I thought I’d share it.

This is how I did it.


  • Windows PC
  • Ability to modify DNS records on the linux server or a DNS server

Setup your new blog and have your old blog up and running.

For arguements sake, let’s say:
blog.fuelip.com ->
new wordpress ->

Now use the export feature to export your current blog to an XML file. This does not export the images. Images are pulled from the old site automatically (it’s an option) when you use the Import Feature.

Here’s the tricky bit.
Edit the host file on your Windows PC so that blog.fuelip.com points to (which is the new site). This means that on your PC only, blog.fuelip.com will point to the new/empty blog site.

On the new WordPress server, the DNS should point to a DNS server you have access to. This should still be pointing to the OLD WordPress server ie. blog.fuelip.com still points to

So let’s recap, we have got a Windows PC that thinks blog.fuelip.com points to which is the NEW WordPress server. The actual server hosting the new WordPress application thinks blog.fuelip.com points to which is the OLD WordPress server.

Not on the Windows PC, lets use the Import feature and import the XML file we saved earlier. Make sure you choose to download images/media. Also make sure the users are setup the way you want. Then hit Import.

You should find that the whole site is imported perfectly.

Why does this work?

  • The references for the images are based on the URL that is shown whilst you’re browsing the site on the Windows PC (host file makes DNS point to the new site)
  • The downloading of the images from the old site is handled behind the scenes by the actual WordPress server which is looking at a different site due to the DNS change.

Hope this is not too confusing…

Comments welcome!

VMware to Hyper-V (STOP 0×0000007b)

Been migrating from Vmware to Hyper-V after my server crash. I was pretty damn impressed with Hyper-V. It’s extremely fast and easy to manage. It’s a great hypervisor, with the only draw back being the base OS taking just under 1GB of RAM. But that’s what you pay for to get a highly versatile virtualisation OS that will install onto any hardware.

Just a tip for those migrating from VMware to Hyper-V. It’s highly documented on the net that VMware uses SCSI hard drives to boot off (as this is what VMware suggests). Hyper-V only boots off IDE (even Hyper-V in 2008 R2).

To not get a STOP 0x0000007b BSOD error, you have to add a IDE hard drive into the virtual machine whilst it’s still running in VMware. Make sure you choose IDE Channel 1:0 or 1:1 as this installs the Primary IDE Channel. You probably already have a Secondary IDE Channel from the CDROM drive.

Last but not least, for me anyway I had to go to Computer Management and initialise the newly created IDE Hard Drive in VMware. I found that if I didn’t do this I’d end up with a BSOD in Hyper-V after the migration.

To summarise the steps in full (it’s been done a million times on the net already – but this is for those who want a one stop shop)

  1.  Uninstall VMware tools
  2. Shutdown virtual machine whilst it’s still in VMware
  3. Install an IDE hard drive on channel 1:0 or 1:1
  4. Startup the virtual machine
  5. Initialise the disk in Computer Management
  6. Shutdown virtual machine
  7. Convert from vmdk to vhd using the tool of your choice (I had most success with VDMKtoVHD from http://vmtoolkit.com/)
  8. Mount the image into Hyper-V
  9. Using the Legacy Network Card will allow the network to work without drivers but restricts you to 10/100.
  10. Otherwise, use the standard Network Card but make sure you install the Integration Services (requires SP2 or higher if you’re running Windows 2003 Server)
  11. You’ll probably get Service Failed to Start errors, so you’ll have to check in Event Viewer and teeth through those issues. Nothing is perfect right? Just keep in mind that it may be caused by some of the VMware Services still installed on the system (check in Service.msc). For some reason, the VMware Tools uninstall does not get rid of them all.

eTrust Threat Management Console (ITM) Password Reset

If anyone else is struggling to work out how to reset this password, hopefully this will help. It follows the local administrator password (NOT the domain administrator). So right-click on My Computer, choose Computer Management – Local Users and Groups. Reset the Administrator password there and you should be good to go.

For good measure, restart the following services:

  • eTrust ITM Server Service
  • eTrust ITM Web Access Service

Server Crash!

Just had a server crash. Think its faulty memory… caused a heap of corruption across all my virtual machines.

I’ll be updating this blog with the missing articles again!
Apologies about the downtime!

Update: Wasn’t memory in the end. Weirdest of problems… after replacing all the SATA cables in the server (RAID and CDROM drive), it all worked??? Craziest problem I think I’ve ever had! Was pulling my hair out trying to isolate the different combination of memory sticks and was about to scrap the server until the last ditch effort to try the SATA cables…

 FYI – the error that occured was that the Windows install kept on saying that the files were corrupt! I’d occasionally fluke an install, but when I blew everything away and tried to reinstall it again, I’d get the same error!

South Australia (Adelaide) Daylight Savings Patch 2009 – 2010 (09-10) – and 2010 – 2011

Pretty annoying how the government keeps changing the daylight savings schedule year to year.
Here is a working registry patch to correct the daylight savings issue for Adelaide.

This patch is good for Windows XP, and should work on Vista as well.
It corrects the daylight savings time to the current official schedule (first Sunday Oct to first Sun April):

2009-10 TAS, VIC, ACT, NSW, SA 4/10/2009 4/4/2010

Paste the following (between the lines) into a registry file and run it (ie. call it Adelaide2009DST.reg)
You may need to change your timezone to another one, and then pick Adelaide again for it to apply immediately.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionTime ZonesCen. Australia Standard Time]
“Display”=”(GMT+09:30) Adelaide”
“Dlt”=”Cen. Australia Daylight Time”
“Std”=”Cen. Australia Standard Time”


 If you want to know how to create a patch like the above for other cities, go here:


Updated – 22/10/10

If you create a registry file with the following timezone info ripped from a Windows 7 computer, it should for each year here on in. The above patch modified it only for one year.


Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionTime ZonesCen. Australia Standard Time]
“Display”=”(UTC+09:30) Adelaide”
“Dlt”=”Cen. Australia Daylight Time”
“Std”=”Cen. Australia Standard Time”

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionTime ZonesCen. Australia Standard TimeDynamic DST]


Windows 2003 SBS Transition Pack Upgrade

Man, where do I start with this…

Had to transition a client that had fully outgrown their SBS server. To cut a long story short, its not that they hit the 75 user limit. It’s because they wanted to introduce extra complexity that an SBS system couldn’t handle. Ie. Multiple secondary servers, file replication, etc.

Just to make other people’s lives easier, here’s the order  in which the transition needs to be performed:

Windows 2003 SBS Premium (non R2)
1. Upgrade to 2003 SBS Premium R2
2. Apply SBS 2003 Transition Pack
3. Test and Deploy server applications to other servers
4. Purchase kit

1. Upgrade to 2003 Premium R2

Before attempting the Upgrade to R2, make sure you only have SP1 installed on the SBS server. It’ll make you’re life a lot easier. If it’s been patched to SP2, remove it. Also, make sure that SP1 for SBS has been applied “properly”. If you’re picking up a site from an IT admin that has no idea, then double check. SBS SP1 contains 5 patches that need to be applied. Obtain from here:


If SBS SP1 has not been applied properly, then you’ll probably get all sorts of errors saying SBS is not the right SP level.

Once you’ve sorted this out, run the SBS R2 upgrade.

2. Apply SBS 2003 Transition Pack

Now, from the yellow slip in the box, it appears you can transition directly from R1 SBS (and you don’t need to transition from R2 SBS). But in my case, my licensing contact said I had to transition from R2 SBS so I followed his advice. In the end, the bulk of the cost is with the Transition pack anyway, the R2 upgrade is outweighed.

Installing the Transition pack involves inserting the CD and following the wizard. It does the rest. After a few reboots, everything should complete. I had an issue however with the second phase of the transition. I received the following message:

Report System CompatabilityThe following items are not compatible with windows.

The compatability issue with some of these items must be resolved before running setup again.

X Small Business Server 4.0

! Service packs and/or quicm fix (QFE) updates

! Port configuration for Routing ans RemoteAccess Service

! Windows 95 and Windows NT 4.0 interoperability issues (Read Details)

The upgrade then bombed out, restarted the server and said it was complete. Same error as here:

Nonetheless, everything looks ok. All the SBS branding has been converted to Standard. This last part that bombed out appears to only update the OS and it’s files. The SBS transition happens in the steps prior.

To prevent this from happening to you, and for a successful transition, I can only suggest you try this:

And finally, here we go to the GOTCHAS!This is truly what the post is aimed towards - this is what people call PSS for.

6-Before installing the transition pack make sure you Export and Remove the following

registry key:HKEY_LOCAL_MACHINESOFTWAREMicrosftSmall Business

Note: There will be a SMALLBUSINESSSERVER key and that is OK, we are only interested

in the “Small Business” key. Presence of this registry key when installing the

Transition pack may cause it to fail.

Hope this helps with anyone else attempting this transition.

3. Test and Deploy server applications to other servers

Test to make sure your SBS server is no longer SBS. You should see that the licensing logging service has now been disabled. Also, I performed an ADPREP and introduced a secondary domain controller. Seems to have worked well. This is something you would not be able to do if the SBS restrictions were still in place.

You can now install your applications on other servers. For me, the aim was to get SQL 2005 onto a seperate server. I can offer a tip here. Attempt to install SQL 2005 onto the SBS box first so you can obtain the serial number. The serial is autofilled, so you won’t find it written anywhere. With the serial, you can then install it onto a seperate server. Please keep in mind that if you have not transitioned SBS, you are not entitled to do this. Furthermore, when you transition SBS you need to buy seperate SQL CALs as the transition pack only covers Exchange!

4. Purchase Kit

This is what I purchase to complete my upgrade (this covers SBS R1 Premium to SBS R2 Premium, and covers the one install of Windows 2003, Exchange and SQL only):


Transition Pack -> MS WIN SBS PRM 03 R2 5 CLT TRANS


SQL Licences -> Microsoft SQL Workgroup CAL 2008 Sngl OPEN No Level User CAL

Last word

Not such a bad experience in the end considering the amount of time it could’ve taken without the transition pack. What I should also mention is that although I had SBS R2 to begin with, after the transition it’s just 2003 Standard R1. I looked this up online, and the consensus is that SBS R2 is not actually Windows Server 2003 R2.