Techkiwi's Blog

The adventures of a technical kiwi


August 2013

Google Apps Sync – Migrate .PST

A common question I always had with our Google Apps users was, can you shift the .pst storing file from one machine to another say if they got a new machine?

After doing some research I found one person who had tried it so I thought I would give it a go and here are the results and what you need to do to migrate.

On the original machine locate the Google Apps Sync folder and files. C:\Users\%username%\AppData\Local\Google\Google Apps Sync

Here you should see multiple files, you just need to copy the .pst file.

On the new machine, download and setup google apps sync, configure the user and profile and open Outlook.

Once an email arrives shut down Outlook (Don’t leave it syncing!).

Go to: C:\Users\%username%\AppData\Local\Google\Google Apps Sync

It should look something like this (I have made blanks for the users email and username).


Copy the name of the current .pst file in this location and rename the current .pst in this location by adding .old to the end.

Copy over the old .pst file from the old machine and rename it to the name you copied above (effectively replacing it).

This should trick google apps sync into thinking it is the same file.

Now you just need to remove ALL the other files in this location, (not the tracing folder though). There should now be the tracing folder and the renamed .pst file here.

Reopen Outlook, it will rebuild the files you deleted and should then realize the file exists and just make increment changes rather than downloading the entire email file again.

There are a few reasons why you might need to do this, Saving Outlook only data like flags and categories, or purely because the .pst file is very large (In this case I wanted both the file was 18GB!)


Paypal PHP IPN – Action Required before October 7, 2013 Email

Paypal recently sent out an email subject: Action Required before October 7, 2013

This was to instruct all current sellers using their PHP IPN for automatically completing payments that would you need to make changes as they are changing over to HTTP1.1 from HTTP1.0


The PHP code they emailed:

// post back to PayPal system to validate
$header=”POST /cgi-bin/webscr HTTP/1.1\r\n”;
$header .=”Content-Type: application/x-www-form-urlencoded\r\n”;
$header .=”Host:\r\n”;
$header .=”Connection: close\r\n\r\n”;
This is missing Content-Length which is required for HTTP1.1
Here is a modified version of the code which I have tested and does work:
// post back to PayPal system to validate
$header = “POST /cgi-bin/webscr HTTP/1.1\r\n”;
$header .= “Content-Type: application/x-www-form-urlencoded\r\n”;
$header .= “Content-Length: ” . strlen($req) . “\r\n”;
$header .= “Host:\r\n”;
$header .= “Connection: close\r\n\r\n”;


I guess not even one of the web giants double checks all code sent out to millions of customers before clicking send!

Office 365 Unlicensed Product Error

This has been an on going issue for most people using Office 365 licensed Office products since the beginning.

After a period of time (Sometimes a password change sets it off) Your user might get the error (Unlicensed Product) in the banner when opening an Office product like Word or Outlook.

There are two different fixes, one for Office 2010 & another for Office 2013.

You need to open a command prompt (I would elevate) and run the following.

Office 2010

32bit: C:\Program Files\Common Files\Microsoft Shared\OFFICE14\OSAUI.exe /F

64bit: C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE14\OSAUI.exe /F”

Office 2013:

You need to go to one of these locations first and then run the script below

32bit: C:\Program Files\Microsoft Office\Office 15\

64bit: C:\Program Files (x86)\Microsoft Office\Office15\

Now run: cscript OSPP.vbs /act

This should bring up am activation window which should show “Successful” after completing.

Hopefully this will help you solve your Office 365 Office Licensing issue.

Update 14/07/2015

I have since had issues where the above does not resolve the issue for Microsoft Office 2013. Where this occurred I have done the following which seems to work ok.

run: cscript OSPP.vbs /dstatus

This will show you the status and last 5 digits of each license key. Now locate the installation that won’t install properly.

Now run: cscript OSPP.vbs /unpkey:Last 5 Digits Of key

(Example: cscript OSPP.vbs /unpkey:4B44N3)

*Note: You can just run this for each of the installations, but be aware you will need the license keys or accounts to reactivate*

Once you have run those commands I recommend rebooting the machine and then right clicking on Word and selecting “Run as administrator”. This should hopefully re-prompt the Office activation window an you can sign into Office 365

Windows 8 SSTP VPN Error 0x800704D4

I received the error 0x800704D4 today when trying to help a client with their SSTP VPN issues.

While there are many causes for this error to occur this was not one of the issues I found listed so I thought I would share it as an option.

This was caused because there were not enough SSTP VPN ports free in routing and remote access.


To Resolve:

On the server (in this case SBS 2008)

Start – > Administration Tools -> Routing and remote access.

Click the + to open the site -> Right click on Ports and select properties

Highlight the Wan Miniport (SSTP) option and click Configure at the bottom -> Add the number of ports you require and click Ok.


Now try connecting the SSTP VPN connection again remotely and hopefully your issue will be resolved.




Windows 8 computer fails to remote desktop using RWW

I had a really interesting error when using Remote Web Workplace (RWW) from a Windows 8 machine back to a SBS2008 server this morning which caused me a few problems.

The error was:

The wizard cannot configure remote desktop connection settings, make sure that the client version of remote desktop protocol (RDP) 6.0 or later is installed on this computer.

The wizard cannot configure remote desktop connection settings, make sure that the client version of remote desktop protocol (RDP) 6.01 or later is installed on this computer.



This is not an error I have seen before, usually RWW is a very stable way for clients to get basic Remote Desktop (RDP) back to their work machines, This issue appears to only be related to Windows 8/IE10.

Here is the work around which has been trialled on multiple machines and works correctly.


Fix Option #1:

Click the compatibility icon and try logging in again



Fix Option #2:

Click on Tools (If tools isn’t appearing, right click on the top banner and select “menu) -> Compatibility View Settings




All the sites name in and click Add



Try logging out of RWW and logging back in, now you should be able to connect to RWW computers correctly from a Windows 8 machine.


Hopefully this will help you solve any issues you encounter using RWW from a 2008/2011 server with Windows 8.


(Screen Shots were taken from MS Technet, all rights reserved)

Windows 7 – User profile service failed the logon.

Now if you work in IT you would have seen this error a thousand times, today I want to touch on an instance of it I have not seen before.

When having profile login issues usually the first things to try are:

1. Remove old profile folder, Can you login now?

2. Check registry, has the profile now been named with .bak?


However today I had an issue with a Windows 7 laptop creating a new profile from scratch.

There was NO user profile folder, nothing in the registry, yet still you get the User profile logon issue. I had taken the machine off and on the domain, could login with our account but not any new users.

The problem was eventually solved with the fix below!


Go to another Windows 7 machine (32 or 64 it doesn’t matter)

Go to Windows Explorer and Unhide hidden folders so you can see them.

Locate the default user profile. C:\Users\Default and copy this entire folder.


Login to the broken machine, unhide the hidden folders and go to C:\Users\ Rename the old Default folder to Default.old

Copy the folder from the other machine over, go to File -> Properties -> Security and check Everyone has read access.


Restart the machine and now try logging into the new user again, with any luck this will solve your issue!


Create a free website or blog at

Up ↑