I originally installed Server 2003 a while back, when it was still in the 'beta' stages of development. It worked well, but I couldn't get everything functioning how I wanted. Older codecs weren't supported, even after extensive 'tuning' of the O/S. Games functioned (at a higher fps than XP or 2000 to be truthful!), but several with older codec intros (HL2 for example) weren't displaying fully. It didn't bother me too much, but knowing that the O/S would expire after 6 months wasn't great. So I reverted to XP Professional SP2.
Today, however, I have finally found a need to use it. Our fileserver at work is stupidly running on XP Professional SP2 (not my choice!). This leads to multiple problems when more than 10 users start accessing the fileserver at once. Since service pack 2, XP has been restricted to 10 simultaneous user connections, which Microsoft claims is beneficial to the end-user as it cuts down potential security threats. In reality, many believe they're just trying to force users to stump up the costs of a fully-fledged Server Operating System - I guess it makes sense.
So, after constant nagging from tutors at work, saying that their students cannot all access their files at once, I decided to look into switching to a Server O/S. Linux isn't a possibility, as I don't have much knowledge with it, definately not enough to setup a server!
Then I remembered Windows Server 2003 - perfect for the job, as it allows many simultaneous connections.
What does all this mean? I've spent the last couple of days heavily researching Microsoft's site, MSFN.org, and many forums around the 'net to get to grips with Server 2003 and what I can do with it in the long run. Afterall, I know how to use it (it's very similar to 2000) and get the most out of it (see link below), but simply formatting and installing a new O/S isn't so easy in an active business environment...
I've had to draw up an Action Plan (thanks to University and all them essays!), which details what I'm going to do, why I'm going to do it, and how I'm going to implement it. I've started informing the members of staff that the fileserver will be 'offline' for a day, which will cause problems. Now all that's left is to allocate the time for me to start.
The main difference between my usual formats and this one, is that this will affect many people, not just myself and my own rig. Everyone needs access to their files 24/7 (well 9-5/M-F), whereas I can live without mine for a day or so. Also, if it goes wrong, it's not just me who will suffer.
I am finally beginning to understand why my lecturers made us plan and document so much. I never once thought that I'd use it in day-to-day work. How wrong I was.
If you're thinking about Server 2003 as your O/S of choice, check out the .pdf here.