Note: I'm not really writing all of this information myself, a good portion of it came from http://www.visualwin.com/, my intent is to take the basics listed there and apply it to the limited scope of this howto. This document also assumes that you already have your box configured for the most part.
IMPORTANT UPDATE: While as near as I can tell, all of the instructions in this post are correct, I cannot guarantee it will work as advertised... matter of fact, I managed to run into a problem myself. See Here for details. I'm still not entirely sure which part caused the problem... it was either using my hostname for the original cert, creating the cert about 5 times using different parameters, or perhaps using the main hosting IP as the SSL domain. Any way you look at it, I suggest being careful and backing up your Helm Database BEFORE you proceed. You can get a backup tool at: http://www.webhostautomation.com/helm/downloads.asp. However, once I went back and fixed the problems, it's now working like a charm. (/end update)
Step 1: Log into your server using remote desktop connection or something similar.
Update: Before going any further, I suggest you do the following: Log into your EV1/RackShack account, request an additional IP address and add it to your server. Once you've done this, on your remote desktop, open up Helm Configuration Tool and then select the tab 'Control Panel Website' You should see the new IP address listed in the pull down list... select it... if the Apply button doesn't highlight, put a letter in the 'Host Header Name' box and then erase it... hit apply. Now is not a bad time to head over to the 'System Database' tab and test the connection. Once you've done all of this... then feel free to move on. (/update)
Steps 2 though 5 can be safely ignored if you've already got a sub-domain you'd like to dedicate to the control panel.
--------------------------
Step 2: Go to the 'DNS' link under Administrative tools
Step 3: In the left pane under 'Forward Lookup Zones' find the Domain name you intend to use to access your Panel and left click on it.
Step 4: Now, in the right side pane, you should see all of the zone records for that domain. RIGHT click on the right pane and select 'New Host (A)...' from the menu that pops up. In this new window, type your new chosen name into the name area... for instance... 'helm' DO NOT type out the full host name (ie: helm.yourdomain.com) just the helm part. In the lower portion, put your IP address in (Use the one I had you get earlier). Click the 'Add Host Button' and then hit 'Close' once you're all done.
Step 5: Just to make sure it all took, back in the left hand pane, right click on your domain name, and choose 'Update Server Data File'. Now you can close the DNS window.
--------------------------
Step 6: Open up Internet Exporer or your browser of choice on the server. Go to the following Address: http://www.microsoft.com/downloads/details...&displaylang=en
and download the resource kit for IIS6. Install it, what options you choose while doing so are up to you, just make sure that 'SelfSSL' remains checked.
Step 7: Now you'll need to open up the IIS 6 Manager, this can be found under 'Administrative Tools'. In the left pane, expand the window until you can see 'Websites'... highlight it by left clicking on it. Now in the right hand pane, you will need to locate the site named 'Helm Control Panel' . Take note of the number next to it in the 'Identifier' column.
Step 8: Go to your start menu, under All Programs you should find 'IIS Resources'. Expand that menu and then expand the menu labled 'SelfSSL' and finally, open up SelfSSL.
Step 9: In the resulting shell window, you will need to type in something similar to the following:
SelfSSL.exe /N:sub.domain.com /V:365 /S:2 /P:8087
Now behind the /N: you will need to fill in whatever sub domain you created in DNS earlier.
/V:365 specifies that the certificate is valid for the next year... choose whatever you'd like
/S:2 is the Identifier Number you obtained in Step 7... change it as needed.
/P: Specifies the port number... Set this to whatever you'd like, just make sure it's different from your nonSSL port (usually 8086)
Step 10: once you've filled in those values, hit enter, it may ask you if you want to overwrite the SSL settings, accept the changes.
Step 11: Open up your browser window and type in https://sub.domain.com, where sub.domain.com is the subdomain you just spent the rest of the howto working with. It should now pop up a warning about semi-vaild SSL cert... just accept it and it'll go away for now. Then... it should load up helm over SSL.
Finally, you are almost done... just reboot your server, if it comes up and Helm still works, you're in business.
Good Luck and I hope this helps you out
