General discussion

Locked

Same Domain?

By shaundyc ·
I have a situation right now were some of my existing workstations(WS) (15 to be exact) that are a present member of my existing domain needs to relocate to a different location.

I am making another server for this situation, my question is;

1. Should I make this server an additional server on my domain and have this host those 15 WS?

2. And if I make this new server an additional server what configuration needs to be done between my Old server and New server?

3. Or should i make this new server a different domain?

Any suggestions will be very much appreciated.

Hope to hear from each of you guys the soonest.

Lots of Thanks

This conversation is currently closed to new comments.

20 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by sgt_shultz In reply to Same Domain?

check this out:
Branch Offices
A Focus on Server Infrastructure
http://www.microsoft.com/windowsserversystem/solutions/branch/default.mspx

Collapse -

by sgt_shultz In reply to

my idea is: call microsoft and ask them how much to help you design this.

Collapse -

by shaundyc In reply to

Thank you guys for your advice.

one thing though, what is more easier and faster thing to do as my time is running out here. I already have a machine in me as my server but have not configure it either way as to additional or new domain?

yes my users on the new location needs some shared resources access here on our existing site, but its only bits and pieces of files like excel or word or cad drawings. I can copy their files and transfer it to the new machine if i decide to have it make a new domain.

the new site also will be having their own internet as by next year new employees will be hire.

Collapse -

by adembo In reply to Same Domain?

A domain, be definition, is a logical security boundary. You would create a new domain if you wanted security between them. Do you not want shared resources? You could obviously create trusts between the domain, but users would still have to authenticate unless the other domain was granted permission.

Keeping them in a child domain, or the same domain, would make sense if shared resources are needed.

Collapse -

by adembo In reply to

Also, if you keep the same domain, (assuming you have the sites linked) then you will have replication occur. DNS records, user accounts, and the like will be replicated to your new server. If you create a new domain, then that wont occur.

Collapse -

by adembo In reply to

Also, if you keep the same domain, (assuming you have the sites linked) then you will have replication occur. DNS records, user accounts, and the like will be replicated to your new server. If you create a new domain, then that wont occur.

Collapse -

by shaundyc In reply to

Thank you guys for your advice.

one thing though, what is more easier and faster thing to do as my time is running out here. I already have a machine in me as my server but have not configure it either way as to additional or new domain?

yes my users on the new location needs some shared resources access here on our existing site, but its only bits and pieces of files like excel or word or cad drawings. I can copy their files and transfer it to the new machine if i decide to have it make a new domain.

the new site also will be having their own internet as by next year new employees will be hire.

Collapse -

by CG IT In reply to Same Domain?

well a general rule of thumb for sites is: if there is a reliable, fast, under-utilized link; small # of users and no servers, you don't need a DC there.

a general rule of thumb for domains is: keep it simple, keep it flexible, try not to go more than 3 layers deep.

If your bent on having a server at the site, make the server a DC with the global catalog role. That way users authenticate locally instead of over the WAN link. setup the site in AD Sites and Services.

Collapse -

by shaundyc In reply to

Thank you guys for your advice.

one thing though, what is more easier and faster thing to do as my time is running out here. I already have a machine in me as my server but have not configure it either way as to additional or new domain?

yes my users on the new location needs some shared resources access here on our existing site, but its only bits and pieces of files like excel or word or cad drawings. I can copy their files and transfer it to the new machine if i decide to have it make a new domain.

the new site also will be having their own internet as by next year new employees will be hire.

Collapse -

by hozcanhan In reply to Same Domain?

shaun , what is your server ? Anyway 2 possible easy methods.
1. Serial connection : Modem to modem direct dial-up connection . You load RAS on your Microsoft Server and SLIP on your XP "moving" member .
2. Apply to an ISP and get two VPN routers . Again load RAS on your server and VPN client on the moving member .
In both cases you don't need a new server and you don't need a new domain . The above is general info for detailed info check out and read all related Q&A answers under this topic . Good Luck

Back to Networks Forum
20 total posts (Page 1 of 2)   01 | 02   Next

Related Discussions

Related Forums