I've begun to notice that several people are unaware of a very important feature of terminal services that can come in handy.  When a server is setup for remote administration mode Microsoft allows two remote administration sessions.  There are at least two issues with this  The first one is that there are only two, so if you have three different administrators trying to remotely log into the same server then the third administrator who tries is going to receive a message informing them that they cannot log in.  The other issue is that some applications output their messages to the console, so if you are logged in remotely you may not be able to view a critical message.
    So what's the solution to this?  Well what few people seem to be aware of is that you can remotely connect to the console session.  This allows you to view any error messages that may get outputted directly to ...

    Well, I recently passed the Microsoft 70-290 exam, Managing and Maintaining a Windows Server 2003 Environment and the primary book I used for studying was a book published by Que titled MCSA/MCSE Training Guide: Managing and Maintaining a Windows Server 2003 Environment.  The book was an easy read, but I don't feel it was enough alone to pass the test even though I did manage to do so on the first try.  I do consider the book a good introduction for someone who is not very familiar with Windows server environments.  It goes over all the basics of the features of 2003, but I don't feel the details were covered enough to allow someone to successfully pass the test.  My suggestion would be to go over plenty of practice tests and have hands on experience with Server 2003 ...

  Originally the mail server for cltralt313373.com was running on a FreeBSD box using the qmailrocks setup.  IMHO, this is the best mail setup you can have and it’s all free except for your hardware.  This setup has built in spam and virus filters, webmail access, web administration features, and an excellent mailing list setup.  So what's the only drawback to it?  Well you have to setup and administer it yourself.  Not a problem for day to day activities, but when it comes to upgrades and troubleshooting errors it can get a little hairy.  The support mailing list it full of very helpful people, but trying to get things fixed when you really need to get them fixed fast can be complicated unless you know all the in's and out's of the multiple software packages that are involved in the install.