I'm fed up with how things are going right now with our network. Computers are slow, manageability is like hell, user accounts are "customized" because of permissions issues with many Gov't required programs (SSS, BIR, Payroll, etc). I'm just about to throw away all the policies and just use our Win2k3 server as an authentication server, print server, file server, dns, dhcp, and web server.
No more GPO, no more Forefront client security (w/ WSUS and all that resource hogging applications it needs). Sticking to MS Security Essentials, local windows updates, and just pure log-in/out.
I know I'm doing something wrong. But I can't for the life of me figure out what it is. I've been researching round the clock for months now on how best to handle a domain. I've finished the CBT nuggets MCSE (2k3) pack. Still have no idea how to best handle a domain w/ 30 users.
Oh and on top of that...Roaming profiles!!!!! things are so slow. they're great for when one of the computers hard drive blows up, just log back in, wait a while and then everything's there. But man is it slow and takes up a lot of storage!
I don't know if I'm ranting or looking for suggestions or what. Please mods, delete this if you deem it not fit for serverfault. But if you have suggestions to fix my domain, I'd appreciate it.
EDIT: I'm trying to solve primarily slow log-in/out, having to log users out to install software (that they need) and then log back in (again slow). Roaming profiles takes the cake as the 1st one to go. But without roaming profiles, how best should I be "preempting" a disk failure? I really love how roaming profiles gets users back up and running in half the time it takes to do a restore...
But of course, the issue here is big user profiles (every shit they download gets copied to the server).
and yes, there's only 1 server handling everything. dual-core with 8GB of RAM 160GB RAID1, and a 500GB backup drive (ntbackup scheduled).