For whatever reason, Microsoft has decided that driver signing is now REQUIRED in Windows Vista x64 (and I hear this also applied to Windows 2008). There used to be a couple of different ways you could disable this requirement, but as of Vista SP1 neither of these methods work anymore. There are also individual pre-SP1 hotfixes that “fix” Windows so you can’t disable the driver signing requirement. This is a big issue for anyone who wants to use tweaked video drivers, or for anyone who wants to use VMWare Server. Read on for the solution.

Getting Syspro e.net Business Objects to work remotely from a non-Administrator account can be tricky if you’re not familiar with DCOM. Syspro has some general instructions in their Support Zone, but they are missing a couple of steps for Windows Server 2003. Below are the steps I used to configure DCOM for Syspro e.net Business Objects in Windows Server 2003.

In this post I will explain how to ensure your WHM/CPanel installation is access securely using SSL. WHM and CPanel support SSL out of the box, as long as you connect to the right port. However, the words whm, cpanel, and webmail are a lot easier to remember than port numbers like 2087, 2083, or 2096. So, I prefer to log in by putting them at the end of the URL. Unfortunately by default these URLs point to the insecure ports, and not the SSL ones. Sure, you can you use “/securewhm” instead of “/whm” or “/securecpanel” instead of “/cpanel”, but that’s more typing, and there is no “/securewebmail” alias by default. Besides, why would you ever want to log into these services without SSL? Fortunately, you can change this behavior and have all of these URLs point to the SSL ports.