In order to move MDaemon to a new machine you should first remove the MDaemon service.  To remove MDaemon as a service
Go to Setup
Click on System Service Settings
Click on Remove Service
Open Windows Explorer and navigate to your MDaemon directory.  Make a backup of the entire directory. Make a note of the directory where you currently have MDaemon installed
Copy the entire MDaemon directory from the old machine to the new machine
Download and install the correct version of MDaemon into the same directory that it was installed in on the old machine
NOTE: You must install into the same directory.  If you install MDaemon into a different directory it will result in a new installation and it will not retain all of your settings.
At the end of the installation you will be prompted to run Advanced Installation.  Select ‘no’ here.
Start MDaemon by going to
Start
Programs
MDaemon
Start MDaemon.
From the MDaemon menu bar select
Setup
System Service Settings
Install Service.

Many a time I cursed and vailed because VMware had let me down. Here is a “quick” and dirty way to access your corrupted VMware server/workstation .vmdk files.

Here is how I managed to recover Zimbra mail servers “mail folders” (Ubuntu6/ext3) from corrupted VMware server image using WindowsXP, VMware Server, Ken Kato’s “Virtual Disk Driver for Windows NT platform” & Diskinternals Linux reader.

1) Copy corrupted .vmdk file to your WindowsXP workstations c:\temp folder. My filename was Opt.vmdk – I had to use WinSCP without any compression on the Linux side to copy it to Windows.

2) Download Ken’s “Virtual Disk Driver” (VDK) and extract it to c:\temp folder. (Freeware) – http://communities.vmware.com/community/developer/forums/vddk

3) Type

CMD

in the “Run” on Windows to start the “Command Prompt”.

4) Change to the folder where vdk.exe is located using

cd c:\temp

command.

5) Type

vdk start

6) Type

vdk open 0 <diskfile> /L:R:

-My command was

vdk open 0 Opt.vmdk /L:R:

<diskfile> has to be substituted by the vmdk file. In my case it was the opt.vmdk file which then was mounted. /L:R: = Mount it as drive R:.

7) Now you probably have the disk mounted on your Windows PC. Problem is that your Windows does not understand Linux formated drives yet.

Download and install “Disk Internals Linux Reader.” (Demoversion.) – http://www.diskinternals.com/download.shtml#cd

9) When I started the Linux Reader it crashed, but I just ignored that and continued. It was still able to find my mounted Linux drive. After scanning the drive in vain I cancelled all the scans and just proceeded to restore the folders it found to the Windows local hard drive.

Hope this helps. VMware Server’s own recovery/mount tools did not work out well for me.

OpenVPN is a full-featured SSL VPN solution which can accomodate a wide range of configurations, including remote access, site-to-site VPNs, WiFi security, and enterprise-scale remote access solutions with load balancing, failover, and fine-grained access-controls.

Although originally developed for Linux, OpenVPN is now widely used for providing VPN services for Windows clients. This document describes how we install and configure OpenVPN to work in a Microsoft Windows only environment.

Prerequisites

This how to assumes that you have various things already set up:

OpenVPN Server

You need a Windows system to act as the OpenVPN server. This can be a Windows 2000/2003 Server or 2000/XP Professional system.

OpenVPN Clients

One or more OpenVPN client systems. These should be Windows 2000/XP Professional, although 2000/2003 server should work equally well.

Networking

The OpenVPN server system needs to be publically reachable on UDP port 1194 (you can use another port if required but this is the standard port for OpenVPN). If the server is behind a NAT router then this will require address/port forwarding.

It’s preferable for the server IP address to be static as this makes things more stable. If your server has a dynamic IP address then you will need to use a dynamic DNS service to provide a fixed hostname.

All systems should have an unfiltered Internet connection, or at least one that allows communication on UDP port 1194. It is possible to run OpenVPN through through more restrictive connections (e.g. a proxy server), but this is outside the scope of this article.

Names and addresses

The names and addresses used in this how to are examples only and should be changed to suit your environment.

• Company Name: Acme Corp.
• Public Domain Name: acme.com
• Private (Windows) Domain Name: acme.com.local
• Server Hostname: widget
• LAN address: 192.168.0.0/24
• Server public address: 1.2.3.4
• Server private address: 192.168.0.1
• VPN address: 10.8.0.0/24

Software

OpenVPN

We generally use the OpenVPN GUI package on Windows systems rather than the stock package, as this provides a system tray icon for controlling the application:

http://openvpn.se/download.html

Server Configuration

Install OpenVPN

OpenVPN GUI can be installed with default options (certificate wizard is not needed). Near the end of the install it will add a TAP-Win32 virtual adapter that is not signed, you need to tell Windows to install this as requested.

Once the installation is complete, you will need to create additional TAP-Win32 virtual adapters using the shortcut in the OpenVPN program group. One adapter is needed for each concurrent VPN user. Rename these adapters to “OpenVPN #n” where n is the adapter number. This is cosmetic only but helps identification.

Configure OpenVPN

Create the server configuration file in the OpenVPN config folder (c:\program files\openvpn\config\)

## server.ovpn ##
port 1194
proto udp
dev tun
ca ca.crt
cert widget.crt
key widget.key
dh dh1024.pem
server 10.8.0.0 255.255.255.0
ifconfig-pool-persist ipp.txt
push "route 192.168.0.0 255.255.255.0"
push "dhcp-option WINS 192.168.0.1"
push "dhcp-option DNS 192.168.0.1"
push "dhcp-option DOMAIN acme.com.local"
keepalive 10 120
comp-lzo
max-clients 4
persist-key
persist-tun
status openvpn-status.log
verb 3

Values in italics should be changed to suit your environment.

In this example the max-clients has been set to 4, which would require 3 additional TAP-Win32 virtual adapters to be created.

Set up a Certificate Authority (CA)

You need a Certificate Authority (CA) to sign your client and server certificates. The easy-rsa scripts make this pretty straightforward.

First we need to initialise easy-rsa. You should only do this once as it will wipe out any existing certificates, keys and settings.

C:\Program Files\OpenVPN\easy-rsa> init-config

Next edit vars.bat and change the “KEY_” settings at the bottom of the file.

set KEY_COUNTRY=GB
set KEY_PROVINCE=London
set KEY_CITY=London
set KEY_ORG=Acme
set KEY_EMAIL=hostmaster@acme.com

Finally create the keys folder and the root certificate itself.

C:\Program Files\OpenVPN\easy-rsa> vars
C:\Program Files\OpenVPN\easy-rsa> clean-all
C:\Program Files\OpenVPN\easy-rsa> build-ca

You will be asked to enter some details for the root certificate. Most of these will default to the values that you entered into vars.bat, but you will need to choose a “Common Name” for the certificate.

Common Name (eg, your name or your server's hostname) []:Administrator

Keys and certificates are created in the keys subfolder. The ca.crt file (root certificate) should be copied to the OpenVPN config folder.

C:\Program Files\OpenVPN\easy-rsa> copy keys\ca.crt ..\config\

Important: Key files (.key) are very sensitive and should be kept safe and never sent over insecure (unencrypted) channels. The Certificate Authority key (ca.key) is particularly important – if it is lost or comprimised then you will have to replace all your keys and certificates.

Set up server key and certificate

Once the CA has been set up, we can generate a key and certificate for the server.

C:\Program Files\OpenVPN\easy-rsa> vars
C:\Program Files\OpenVPN\easy-rsa> build-key-server widget

Executing the vars.bat is not necessary if you do this straight after creating the CA because the environment will still be set (but it doesn’t hurt).

As with generating the root certificate, most of the details will default to the correct values but you will need to enter a “Common Name”. This is best set to the hostname of the server.

Common Name (eg, your name or your server's hostname) []:widget.acme.com.local

You can leave the challange password and optional company name blank.

The server also needs Diffie Hellman parameters.

C:\Program Files\OpenVPN\easy-rsa> build-dh

This may take a while…

Finally copy the key, certificate and DH file to the OpenVPN config folder.

C:\Program Files\OpenVPN\easy-rsa> copy keys\widget.crt ..\config\
C:\Program Files\OpenVPN\easy-rsa> copy keys\widget.key ..\config\
C:\Program Files\OpenVPN\easy-rsa> copy keys\dh1024.pem ..\config\

Setup VPN routing

Routing on the server should be enabled by enabling LAN routing in the Routing and Remote Access service, however we’ve found that this causes problems with the OpenVPN service so I would not recommend it. Instead use regedit to set the IPEnableRouter registry key to 1.

Key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Value: IPEnableRouter
Type: REG_DWORD
Data: 0x00000001 (1)

To allow VPN clients to communicate with systems on the LAN (other than the VPN server), you need to add the VPN network to your router(s) configuration. For a simple stub network you would do this by adding a static route to the default gateway to direct traffic for 10.8.0.0/24 to the server.

Network: 10.8.0.0
Subnet Mask: 255.255.255.0
Next Hop Address: 192.168.0.1

To do this with on an IPCop firewall, add a line to the /etc/rc.d/rc.local file.

 #!/bin/sh
 /sbin/route add -net 10.8.0.0/24 gw 192.168.0.1

You can also add this route at the command line to avoid rebooting the router.

root@ipcop:~ # route add -net 10.8.0.0/24 gw 192.168.0.1

Finishing touches

We like to create a batch file called restartvpn.cmd in the OpenVPN config folder (and desktop shortcut) to restart the OpenVPN service in case it gets stuck.

net stop openvpnservice
net start openvpnservice

Configure the OpenVPN service to start automatically on boot using the services applet, and then start the service.

Client Configuration

Install OpenVPN

Again the OpenVPN GUI can be installed with default options.

I like to rename the TAP-Win32 (in Network connections) adapter to “OpenVPN”. This is cosmetic only but helps identification.

Configure OpenVPN

Create the client configuration file in the OpenVPN config folder (c:\program files\openvpn\config\).

## acme.ovpn ##
client
proto udp
dev tun
remote 1.2.3.4 1194
resolv-retry infinite
nobind
persist-key
persist-tun
ca ca.crt
cert fred.crt
key fred.key
comp-lzo
verb 3

Values in italics should be changed to suit your environment.

In this example we assume that the name of the client is “Fred“.

Set up client key and certificate

We will generate client keys and certificates on the server, which means you have to be careful to securely transport the client key to the client machine. To avoid this you could generate the key on the client along with a Certificate Signing Request (CSR) which can then be transported to the server where it is signed to create the certificate, however this is beyond the scope of this document.

Generate the client key and certificate on the OpenVPN server machine.

C:\Program Files\OpenVPN\easy-rsa> vars
C:\Program Files\OpenVPN\easy-rsa> build-key fred

Then copy the client key and certificate along with the root certificate securely to the config folder on the client machine. The simplest way of doing this is to just put the files on a USB key (or floppy disk).

C:\Program Files\OpenVPN\easy-rsa> copy keys\fred.crt a:\
C:\Program Files\OpenVPN\easy-rsa> copy keys\fred.key a:\
C:\Program Files\OpenVPN\easy-rsa> copy keys\ca.crt a:\

Then on the client machine

C:\Program Files\OpenVPN\easy-rsa> copy a:\fred.crt ..\config\
C:\Program Files\OpenVPN\easy-rsa> copy a:\fred.key ..\config\
C:\Program Files\OpenVPN\easy-rsa> copy a:\ca.crt ..\config\

Test

Right click the OpenVPN tray icon and select “Connect”. It will open a status window showing the connection progress, and if everything is working ok then the status window should close and the icon should turn green.

To test the connection, try pinging 10.8.0.1 (the server VPN IP address), 192.168.0.1 (the server LAN IP address), the address of a PC on the remote LAN (e.g. 192.168.0.123), and then try pinging devices by name.

c:\> ping 10.8.0.1

c:\> ping 192.168.0.1

c:\> ping 192.168.0.123

c:\> ping widget

The option to format internal and external hard drives to the FAT 32 filesystem is not available to you from within the Graphical User Interface in Windows Vista/Windows 7 64 Bit Editions. If you wish to make data available to operating systems or applications that cannot properly read or write to NTFS partitions, this can pose something of a problem for you. Thankfully there is a relatively easy command prompt solution you can use to solve this little problem.

To perform this format successfully, you need to launch Command Prompt with Administrator permissions before executing the command.

Here are the steps to follow:

1. First, find the drive letter of the HDD you wish to format from My Computer. Check, double check, and triple check you have the right letter before executing any format commands on your drive.

2. Navigate to the Command Prompt program: Start Menu > Accessories

3. Right click the Command Prompt entry in Accessories and choose to “Run as Administrator”.

4. You should be prompted by User Account Control “Do you want to allow the following program to make changes to this computer?” Answer yes. If you have disabled UAC, you will not see this message.

5. With the command prompt now showing, enter the following command:

format XYZ: /FS:FAT32

Replace XYZ with the letter of the drive you wish to format.

You can also perform a quick format on any drive without bad sectors:

format XYZ: /FS:FAT32 /q

Again, replace XYZ with the letter of the drive you want to format.

Depending on the size and the method you choose to use to format your drive, it can take anywhere between one minute and several hours for the format to finish. But once complete, you will have your drive properly formatted to the FAT32 filesystem.

The Windows NT/2000 Resource Kit provides two utilities that allow you to create a Windows user-defined service for Windows applications and some 16-bit applications (but not for batch files).

Whats needed for Windows NT/2000:
Instrsrv.exe installs and removes system services from Windows NT/2000
Srvany.exe allows any Windows application to run as a service.
You can download both files here srvany.zip

This zip includes three files. The two you need srvany.exe and instsrv.exe to install the services and also srvany.wri which documents everything you can do with the program.
Note: Make sure the Services Manager is closed while running the DOS commands.