moving wingate to a new pc

[jdc]

We're moving servers and I have to move wingate aswell.
First off I'll say the old server ran Windows XP Pro and it seems wingate 6.1.2, whilst the new server runs Vista Ultimate and 6.2.2.

I exported my settings using the Save Registry Options button on the old machine, copied the file to the new machine, and ran it. But it seems to have made no change whatsoever to the new wingate. Please advise.

[labull]

I don't think Version 6.X is Vista compatible. The next version will be.

[sccs]

WinGate 6.2.2 (Build 1137) works fine under vista. cant help with the settings migration tho

[logan]

The proxies seem to work OK under Vista. It's just the ENS driver and any features associated with it that do not work because there isn't a Vista compatible version of the ENS driver for WinGate 6.x. However, WinGate 6.x has not been written for or tested on Windows Vista. WinGate 2008 on the other hand has been written with Windows Vista and 2008 in mind, so will fully support the OS. In your case, if you only require the WinGate proxies, you could probably get away with this setup even though we do not officially support it.


Did you follow the proper procedure for importing a backed up registry file?
- Stop the WinGate engine.
- Open regedit
- Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Qbik Software
- Delete or rename the WinGate registry key
- Run the backed up registry file to reimport it
- Start the WinGate engine


I will try and get my hands on a vista machine some time this week to have a look at importing/exporting registry files with it for you.

[logan]

Just in addition to my last post. The move to virtualised registry settings in Vista may have something to do with this problem. The registry settings may be getting imported to a location that WinGate is not checking.


See the following msdn article for more info on registry virtualisation
http://msdn.microsoft.com/en-us/library/aa965884(VS.85).aspx

[alyork]

We have to migrate one of our servers from Windows 2000 Server to Windows Server 2003. If I read the above posts correctly, is it safe to assume that Wingate does NOT have a configuaration file in the Wingate progam folder and that we have to muck around with registry stuff to transfer our settings?

- Al

[logan]

It would be safe to assume that, yes.

[alyork]

Non-dependence on the Windows registry would have been better. OK I managed to find the "Save Registry Options" button under Options / Advanced in Gatekeeper. Hopefully it works. :)

- Al

[adrien]

there's also regedit.

We normally just recommend

exporting:
1. open Regedit.exe
2. Export the key HKEY_LOCAL_MACHINE\Software\Qbik Software to a file.

importing:
1. Install WinGate on the target machine, incl reboot.
2. Stop WinGate engine
3. open Regedit.exe
4. Delete the key HKEY_LOCAL_MACHINE\Software\Qbik Software.
5. double click on the reg file from the export process above to enter the exported data into the registry.
6. Start WinGate

the reason you need step 4 in importing is because importing data from a reg file just adds those values/keys to the registry. It doesn't replace the keys, so if there are other settings etc you can end up with a mixture.

Adrien

[olaf.krause]

I did this registry export import - but all services where still running with wong parameters - eg. WWW at port 80 but I configured 8080 (and also the registry stated 8080!!??? - bit strange). I was trying to relocate a wingate 6.2 (windows 2003 32bit) to 6.4 on another machine (win 2008 R2 64bit).

Since this was not working I now first upgrade the 6.2 to 6.4. The only issue I found yet was that the NT userdb settings were lost and I had to reapply the sync with NT domain controller.

Could my issue be related to the fact that I also changed the wingate version? I exactly followed

exporting:
1. open Regedit.exe
2. Export the key HKEY_LOCAL_MACHINE\Software\Qbik Software to a file.

importing:
1. Install WinGate on the target machine, incl reboot.
2. Stop WinGate engine
3. open Regedit.exe
4. Delete the key HKEY_LOCAL_MACHINE\Software\Qbik Software.
5. double click on the reg file from the export process above to enter the exported data into the registry.
6. Start WinGate

[logan]

Hi Olaf,

In 32bit windows, WinGate's registry settings are located in HKLM/Software/Qbik Software.

In 64bit winodws, WinGate's registry is located in HKLM/Software/Wow6432node/Qbik Software.

To import a 32bit config into a 64bit machine, you will need to open the reg file in a text editor and do a find and replace to add Wow6432node to all the paths.
e.g. find 'Software/Qbik' and replace with 'Software/Wow6432node/Qbik Software'.

And vice versa, when going from 64bit to 32bit, Wow6432node must be removed from the path.

[olaf.krause]

Hi logan,

thx of course - a bit stupid from my side - I expected something like that. Anyway I did it manually and it seems to work.

@QBIK: please update you KB accordingly - this might avoid that the next user falls into this trap...

thx

Olaf

[logan]

Just wanted to let everyone know that I have written a KB article for this 32bit <-> 64bit migration issue.

http://support.qbik.com/index.php?_m=kn ... 92&nav=0,2

[olaf.krause]

thx