Our windows 2003 server was set up as a peer to peer network server. i want to make use of the active directory. is this a complicated process since we have the users and permissions already set up?

Yes it is complicated. You will in effect create a new network. What is it you want to do and why do you think AD is the answer? Give a person a fish, they eat for a day. Suggest they internet search and they learn a skill for a lifetime.

y would u set up 2003 server as a P2P?? (im assuming u mean a workgroup?) the whole idea of 2003 server is for a domain and normally as a domain controller depending on your requirements.assuming u have permissions locally they will all be scrapped if u decide to use AD DNS and group policy which are all fundamental features of 2003 and any domain infact.As domain wide policys ALWAYS override local policies.a domain is effective only when there is a central resource.

Honestly, I don't think it's very complicated at all. Ljlocke could easily google 20 pages of step by step, screen shots included, walk throughs on how to complete this task. He already has the server, he could even buy 2-3 hours from an outside contract company and spend 200 bucks and have it done for him if he doesn't fill comfortable doing it himself. Scurlaruntings, you're aware that this user probably has no idea what you're talking about, right? Policys and DNS havn't even arised in discussion yet, he is simply asking if a domain environment would be useful for him. I think it's safe to say that this user has a resource being shared within his office, thus him having a server and a workgroup environment in the first place. "A domain is effective only when there is a central resource" Huh? An active directory environment is only good for sharing resources? How about the security? Managed administration? How about ease of use for end users? How about the features such as roaming profiles and home folders? Sure, these are 'resources' but they are ones obtained from a domain environment. Even if I was working at an office that didn't have any file shares, didn't have any shared applications, etc etc I would still impliment a domain environment if, like this user, they office had a server laying around. At this point, it wont cost the user anymore money other than his time. Holy Wow.

... and maybe a bad headache. :) Holy Wow.

im fully aware of that jesbible.my reply to him was short and conciswe.DNS and AD go hand in hand.

Jestible hit the nail on the head. we have one server and 8 workstations in a small office. we previously used windows nt (since 1998), upgraded to windows 2003 in jan. 2004. i basically set up the new server based on the previous set up (which i did not install). having just been to a windows 2003 seminar, i wanted to make use of the ad because of everything he said. (security, management, roaming profiles etc.) i have never had any problem with the network that i could not figure out. if i started using the ad, wouldn't it be just like setting it up initially. i know i would loose my user permissions, etc. but at the same time i would be adding them through ad. we have dell computers and server and use windows xp professional.