How many of you run Active Directory at home (As apposed to P2P)

zen62619 said:
I run server 2003 R2 licenced from my company with dns/ad/dhcp in vmware for test purpouses only. It is not overkill. It's called learning....

Especially if you work in a company who use it and you need to test somthing out in your own time.

Yes exactly. I've got 2 DCs plus a load of VMs (exchange cluster, a couple of ISA servers, Root CA, etc) which i power up when i need to test anything out.
 
ghgh said:
lol

its meant to only work on systems with more than 8 processors? apparently but it seems to run just fine on my duallie...might be overkill but it seems to function well.


And I thought I was going over the top running 2003 Enterprise on an old athlon :cool:
 
I run a 2000 AD server on a Dual Ppro 200Mhz with 196MB Ram at home.

Its the DC, DHCP, DNS & IIS server for my network :D Also runs a Postoffice Mail server. Uptime is about 9 months (since I rebuilt the SCSI drive)
 
Same here, Running SBS 2003 at home, for 1 PC, and three laptops over a wireless link.

And all legal too, I get my home mails whilst im here at work. and can RD to home, to fix any issue that the kids or the misses muck up.

And i can use ny home link for any big downloads i need, and them burn them to DVD for her to post out. Great
 
ruffneck said:
except technet copies are 180 day trials and MSDN copies arn't

Dunno about that. We have a Technet Plus subscription and we get full copies with full product keys. The only restriction is that they cannot be used in a production environment. Only for testing. Products that dont need activation under VL are required under TechNet. You are also limited to about 10 activations on most products. More info here:

http://technet.microsoft.com/en-us/subscriptions/ms772427.aspx

Otherwise why pay £1,000 per year for technet plus when you can download most products as an eval from microsofts site??!!
 
I recently moved to a domain at home just cause its easier to share shares/printers and email accounts and not having to setup local accounts on every computer.
 
FGZ said:
I recently moved to a domain at home just cause its easier to share shares/printers and email accounts and not having to setup local accounts on every computer.

Thats a good reason plus with the ease of setting up AD in 2003 it is worth doing.
 
with companies now gettin bigger and better it is needed to keep up the knowledge in IT. The easiest way to do it is to do it on a test network before it is implimented on a real network.

This iliminates errors in the real world resulting to happy customers.
 
I'm running SBS 2003 at home, but need to get a cluster set-up for exchange 2007. Again for learning purposes.

Was going to use virtual server for the clustering rather than VMWare

I need to get some more kit, but it's the electricity bill I need to watch. hoping to get a DL380 G2 soon :) I need HP proliant skills too.... (although they don't know I'm already HP APS certified)
 
tonyyeb said:
The only REAL issue i see is the cost difference ;):

It supports 32 CPU's. Somehow MS think they can charge more for that, as if its technically far more complex. I like the Linux way of editing the CONFIG_NR_CPUS in your kernel config file to whatever you want :p
 
A lot of people are talking about the cost of running 2003 server. Did you know that you can set up SAMBA on linux to act as a domain controller? It's not as fully featured, but you can do quite a lot with it, roaming profiles and LDAP for instance. I prefer it because it's easier to setup a streamlined setup without all the bloat that Windows has.
 
DeeJay-Mo said:
A lot of people are talking about the cost of running 2003 server. Did you know that you can set up SAMBA on linux to act as a domain controller? It's not as fully featured, but you can do quite a lot with it, roaming profiles and LDAP for instance. I prefer it because it's easier to setup a streamlined setup without all the bloat that Windows has.


I wouldnt say it was easier to set-up...If you dont have much experience with Linux based OS (Like me :) ) then its hard to get your head around it all.

Plus the reason i would prefer using a Windows based Server OS over Linux is that it doing it to learn as we use Windows Based servers in our office.
 
What I mean is it is possible to start off with a fairly lightweight distro, such as slax, and then only add the packages you need resulting in a relatively bloat-free environment. With Windows a lot of extra unnecesarry crap is installed which is quite tricky to get rid of. It is possible, but there is a high possibility of breaking the operating system. I'm not saying that Linux is easy to set up, but if you're prepared to spend the time tweaking and hacking it, then it is possible to set up an environment which is powerful but not resource hungry.
 
Back
Top Bottom