Best practices Design Active directory

Hello gents

i have a question I want to redesign an Active directory ? but there is something that I'm not certain of : Actually I have 2 networks : 192.168 . 6. X where there is One domain Controller and A second Network of 192.168.7.X where there is a Second Domain controller  (Domain is the same). I have Servers that are seating in the two domains.

I want to create a domain for the servers only . Is it a recommended practice?  I want to create a VLAN dedicated to servers .  any Impact on Active directory ?

Rgds
gazambeyIT CONSULTANTAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Wilder_AdminCommented:
You are mixing topics. First to make all clear. AD is more or less for authenticating users and computers so easily to say a trustcenter then you have the topic of network. You have to network as a subnetting setup for locations maybe. And you have VLAN is a accessingcontrol for networks.

All are depending on each other but here does it not make sense to create a new domain.

What you can do instead ist to bring the servers in a own subnet / Vlan and clients etc in a different one. This is depending if you have two locations (cities?) and how they are connected. For VLAN you need special hardware and a way to manage them. Its one to setup and one to manage them. I hope i made it more clear???

At the end you need a concept what you want and how you achieve. In both i can help if you need.
0
David Johnson, CD, MVPOwnerCommented:
With a VLAN separating clients and servers brings another question .. how does a client access a server?
0
gazambeyIT CONSULTANTAuthor Commented:
Hello People

I appreciate your comments. first of all I'm not mixing Subjects . I know that AD is for Authentication . My question is is it a good practice to have a VLAN for Servers and another One for Computers?

And sorry I don't want to create a new domain . I wanted to say a new network.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Andy MInternal Systems ManagerCommented:
If you have a separate network for the domain controllers the computers would still need access to that network to authenticate/access files/etc.

I think the first question is what are the reasons for separating out the server/computers - unless there's a specific reason to do so I don't see any reason to separate the servers to another network.
0
Wilder_AdminCommented:
You are not seperating Servers from clients with vlan the best practise if you can is to group clients with servers. For example your accounting has a own Terminalserver where alle financial Software is installed on. So it would make sense to seperate them from the rest of the network except of the dc.

Thats the way for vlans. What you can do is the subnetting topic to collect all clients in one and the servers in the other. Thats only cosmetic. It can make sense for example when your dhcp scope is getting to small then it would be a good idea to seperate the clients.

Even think about of ipv6 in your internal network? I know its the future and no need yet but if you want to be the first then its time to do.
0
Pramod UbheCommented:
recommended practice is that you should have separate vlans for desktops and servers but those should communicate with each other. In AD you can create separate sites based on your subnets/location or map both the subnets to be authenticated within single site.
I think in your current setup you have separate domains which can easily be  done with sites and services or subnets in AD
0
Seth SimmonsSr. Systems AdministratorCommented:
i can see separating the networks through vlans like that in a large environment but if it isn't too large i would keep it simple and use one network; perhaps using 192.168.6.0/16 which will give you 512 addresses and will still allow you to separate into the .6 and .7 for servers and clients.  unless they are in different physical locations, i would keep both subnets in the same AD site
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.