Windows
Numerous articles for Microsoft Windows administrators.
Most of my Windows experience has been acquired from consulting in terminal services and hosting environments. I began acquiring my Windows server administration experience with a very thorough understanding of NT4 server (1998). This experience continued with Windows 2000 server and Windows 2003 server as they became available.
My first production design/implementation of Windows 2000 Terminal Server solution was in an environment with a dozen locations and hundreds of end users (2001). I have since implemented Windows 2000/2003 Terminal Server in dozens of environments, continuing to give careful attention to reliability and performance of the application servers as well as cleanliness and simplicity of the user environment.
My first production implementation of Windows 2000 IIS was in a hosting environment with hundreds of clients (2002). I have since implemented numerous Windows 2000 IIS servers in hosting environments, while continuing to give careful attention to the security and reliability of each web server.
Recent Articles
Windows: Using BackupPC with mobile Windows XP clients via OpenVPN and Cygwin Rsync Server
BackupPC assumes your mobile hosts will occassionally visit your network and allows backup of those hosts while they are on your local network. But what if you need to backup mobile Windows hosts that NEVER connect to your BackupPC LAN? We will use OpenVPN to build a VPN connection between the client and the BackupPC server. We will configure BackupPC server to backup via an Rsync Server on the BackupPC client. This solution is working well for several remote PCs (Windows XP) and Servers (Windows 2000).
Windows: Windows Terminal Server Printer Driver Compatibility
We are often asked to assist with printer configuration in Terminal Server environments. This article provides a brief list of the native printer drivers we have successfully used with numerous "unsupported" printers. This driver compatibility list is helpful since Microsoft and others recommend you avoid using third-party printer drivers on your Terminal Server. You should only use the native printer drivers provided by Microsoft to ensure system stability (ie: avoid blue screens and other unnecessary errors).
Windows: Mapping any RDP printer in Terminal Services w/ REDMON
I have always felt that RDP printer mapping within Windows Terminal Services has been more challenging than necessary. Especially since previous articles I have read from Microsoft and other sources do not recommend using ANY third party printer drivers on your terminal server. These articles claim that third party printer drivers are the #1 cause for blue screen situations on a terminal server. As a result, I would often try to find a "compatible" driver in the existing Windows printer list. Sometimes I simply could not get a printer to work within a terminal server session.
This article demonstrates how to map ANY working client printer within a terminal server session. Although I would still recommend settling on a compatible driver when possible, this allows black and white printing on any working client printer from within an RDP session.
Windows: Setup Solomon IV client in Terminal Server 2003
We are often hired to assist customers with application compatibility issues on Windows Terminal Server. We use a variety of methods to determine why an application is not working (properly) on a Terminal Server. Today, I was tasked with configuration of the Solomon IV client on Windows Terminal Server 2003. The application was returning numerous errors, mostly while trying to use Print or Print Preview functionality. The Solomon IV server had already been properly installed and configured and had already been used to successfully install the Solomon IV client on standard Windows workstations. This article assumes you are also to this point and only addresses installation of the Solomon IV client onto a Terminal Server.
Windows: Using Sprint PCS internet (PPP) via Samsung SPH-A680 w/ USB cable
If you use Sprint PCS and you have a Samsung SPH-A680 handset, you can likely use your phone to dialin to the Internet from anywhere you receive a reasonable (2-4 bars) Sprint PCS signal. Depending on your account, your usage may be unmetered (ie: vision plan) or may consume minutes as if the connection were any other phone call. I can receive SMS (text) messages while I am dialed into the Internet through my handset, but I cannot make calls or send SMS messages. You only need to install the necessary driver and dial into the Sprint PCS PPP phone number (see below).