Windows 2003 server install to existing domain.

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER

Thanks for the promtp reply dekkar. How do you think the exising domain would handle another DC not in the forest?

Lee W, MVP

It won't be a problem, BUT, you'll need to take special care of the clients. ONE Network will not be able to use DHCP and must be set to operate statically. This way, you configure the DNS on the clients to point to the new DC/domain and it should be fine.

Brian Pierce

With 30 users it sounds ideal for SBS server, which supports up to 75 users as a significant saving over Win2003 Standard server if you want other facilities such as Exchnage and SQL as well.

A domain is definately the way to go - the central admin and control alone will more than pay for the investment.

Lee W, MVP

I should have asked - is there any reason both companies need to work together? If so, then SBS would not be ideal - SBS cannot setup trusts.

ASKER

KCTS,
Thanks for the SBS suggestion, but after the contract job is finished this server will joining the home network and another DC will not be allowed. Also, no need for exchange.

yeh.... steer clear of sbs.... as sbs demands that it is the 'PDC' (it needs to be the FSMO role holder)..... which I can say will cause issues.... SBS will allow other DCs...... what it wont allow is another SBS server.... but if you have a domain setup already, SBS will casue u pain and suffering ;)

2003 server is designed to do what you are aiming to do.....

any reason you simply dont migrate the P2P into the existing domain...

there is no hassle with having two domains though, and the user training is nothing, do a profile copy for them and they wont even notice the difference

Brian Pierce

Sorry I missed the fact that there was an existing domain - which does rule out SBS. Jay_Jay70's idea though has a lot to offer and would be simpler and less costly than creating another seperate domain.

ASKER

Jay Jay70,
The existing domain is an enormous corporate entity. They are permitting the use of their server now for DHCP and DNS, but I don't think they will permit what you are suggesting. What are your thoughts of just putting in as a member server. The job will complete in about a year and the server wil be moved to another location.

Pressley

ASKER

Or if we were able to get permission, join it as a child-domain?

unfortunately child domains arent a possibility with SBS either :)

I would probably look at a single new domain environment in your situation...there isnt really a lot more that you can do with SBS and the limitations you are looking at

yeh... do as you planned originally.... it seperates u away, which helps you plan for when you move...... if you are only going to be connected to this 'parent' domain for 12 months, dont revolve you plans around it.....

Create a trust between then, so that when it dissappears, you dont have to rebuild the domain...

again, its SBS, there will be no trusts

Jay, he didnt plan on implementing SBS... someone just suggested it.....

ahh oops - caught up in it all - my apologies :)

ok, with that in mind and cleared up, i wouldnt go child at all, i do however like the trust scenario if needed

again, apologies

ASKER

Thanks all for suggestions. Just received server today so I'll be busy biulding it next day. I'm still not certain what path I will take. I'm leaning toward installation as a member server for he relatively short duration that it will be in production at this site. I will respond with the result of the deployment and how everything went.

ASKER

Thanks for the help dekkar. The server actually went in aa a workgroup member. The individuals responsible for the existing domain environment weren't keen on adding another server to their domain, even as a member.