AD or no AD 6

[iolair]

I'm sure this has been asked before, so please don't flame me. I've looked at Microsoft's website, and have searched the FAQ's and Forum questions on this forum and the W2K forum. I haven't found a satisfactory answer.

I have a small LAN (50 users, 10 printers). We have been told by upper management to convert to an all-Windows network. We currently use file services, print services, backup services, anti-virus services, and use a login script to map users' drives.

We have studied our situation and think we can get by with three servers, so that one server will be file, print, and backup. One server will be anti-virus and network monitoring, and one server will be for internal webservices.
Our email is hosted by someone else.

My question is this: with such few servers and users, would we be better off NOT using AD, since we would only have to enter a user's account on three servers? How much of an impact on server performance does AD have? Is it a memory hog? Disk hog? Would there be any benefit to using AD on such a small LAN?

Thanks

Iolair MacWalter
Director of IT

 

[terry712]

look at the vbs forum faq's

markdmac faq covers it well
not as good as you are used too

if you have zen then the gpo's are the same
well the policy is - the way it handles isnt

the policy modelling gives a good info

with the size etc and no wans etc - it easy enough

dont mod the defaults though - create new one
mark's book is a good start and the forums are ok as well
willem will keep u right

 

[technome]

Probably way more control than I need"
More control then I ever need. Obviously you will moan when there is something not in the GPO. Initially there is little you need to change in the GPO to get get AD going, no rush to be an expert at the start.

Events relating to computer functions are helpful, though finding the cause of errors can be tedious, Internet searches give best results. Auditing users/files can be a pain, unless you can dump and filter into a report.

Login script to map drives.. Mark Minasi, goes over that, easy.

Multiple NICs, pay attention to Mark's reference to Multihoming, not good unless done properly.

As to file security, use groups extensively. Takes some time to get used to, definitely not Novell quality, but you already have a good security background.

Very important, once you get a live production AD system going, attach the Windows system to the Novell. Run both at the same time, and gradually make the transition, otherwise it is very stressful on both you and the users. If it takes you a few of months, your better off, you will make less mistakes. If you killed off the Novell over night, you would need body armor to stop the spears from the users.



........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[iolair]

No, haven't killed off the Novell yet. Will probably run them side by side. I do have an old copy of W2K that has something called "Gateway for Netware." Would that be helpful?

Iolair MacWalter
Director of IT

 

[technome]

Have not had to deal with Novell along side Windows in 3 years, from memory that is old.
Your best off getting an Eval of Win 2003 server (6 months free, downloadable full version) for your lab. Plan on getting Win 2008 server out soon ( release date Feb 27), 2003 is better much better than 2000, 2008 should be really mature, and has some really great "toys" to play with. If you can wait, get a 2008 eval.. you could get a beta at this time but I have not succeeded in getting it going on a Dell 2900III as of yet (likely due to the raid driver).
The installation of Windows server is relatively simple, small mistakes can slow you down, like in DNS. Lastly, do not even consider installing IIs on a AD FSMO, even on a lab machine, it is an unrefined memory pig.


........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[acl03]

In my experience, running netware and windows (that is, accessing netware shares and windows shares) at the same time leads to VERY slow performance from either one or the other. I'd just pick one and go with it.

Also, look at Shadow Copies on your windows server as a replacement for Netware's Salvage utility.



Thanks,
Andrew

 

[GrimR]

cajuntank, You did say compare apples with apples.

You forgot to add Exchange 2003 + 50 CALS

http://www.microsoft.com/windowsserver2003/sbs/evaluation/features/default.mspx