Question Locked

Two domains at once? or domain and workgroup...

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have to make a decision that requires some non-standard working methods in a Windows environment.

First the environment info:
1. My organization has some Windows 2003 servers at a main site, including a Windows 2003/Exchange 2007 server and some citrix servers. We run active directory 2003.

2. We have another site that has a Novell 6.5 server that we are replacing with a windows 2003 server.
3. Users at this remote site get their email across the WAN from our exchange server. They are prompted for AD credentials when doing so. They are also prompted for AD credentials when logging into our Citrix servers. That's all fine.

The problem:
You would expect that I would add the server at the other location to the domain(and make it a DC), simplifying management and authentication. Unfortunately I am forbidden from doing so. The CIO of the organization has made it aggressively clear that he doesn't want the additional WAN traffic that might create, nor problems that may occur when the WAN is flakey. (Which is frequent.) This is not open for debate.

So my options are;
1. create a seperate forest/domain at this site, or
2. leave it as a workgroup server.

I like the idea of the centralized management that a domain server presents, but I worry that if users are logged and authenticated to that domain, they will have difficulty logging into and authenticating to the citrix server and exchange server of our forest/domain. Is that a legitimate concern?

What is my best option when I am not allowed to put the server in the same forest or domain as the main site? Do I have to just setup the remote site server with local users and groups? Or is it not a problem to have users login into one active directory and then authenticate to another for access to email and citrix?

17 replies

by wizard-09

don't no if this is within what your allowed to do but maybe setup a trust between the 2 domains?

by kenone

You can have two domains and, if you do it right the users in one domain can access all the allowed resources in the other. It's all in the "Trusts". However, I think that setup would generate as much, if not more, network traffic than a single domain.

by ugadata

Sites are a way to keep everything in a single domain and still seperate WAN traffic to within each site.

You would still have a domain controller at each site. Each site could have it's own DHCP, DNS, etc. And each site would have it's own subnet.

by kchandley

Yes but in doing so, both servers would be part of the same active directory/domain. If I violate my bosses orders I will certainly be terminated immediately.
I understand that I can designate the amount of site traffic using the sites and services console, but I am not the CIO of the organization, and after discussing it, he has made a final decision that is not open to debate should I wish to stay employed. I wouldn't be asking the question if I was going to do the MS standard deployment of making the server part of the domain/AD and managing the traffic and trusts using the sites and services console. That was my suggestion, it was firmly denied, and is not an option.

The remote server must not be part of the main sites domain/forest/AD should I wish to keep my job. If anyone can answer the above question within the parameters designated by my superior, I will appreciate your insight.

by tonythetiger

will be less reliable under flaky wan conditions and generate MORE traffic.

On the other hand, you might want to ask yourself why he hired you? If it's just to be a yes-man, suggest a trained monkey with an "OK, Boss" sign as your replacement.

by tonythetiger

Another option is to have NO server at the remote site and simply join the computers to the domain. Having 8 such sites, I can testify that it DOES work.... as long as the link is up. How fast is your WAN? We're running T-1s with 7-10 computers and the same number of IP phones at each location, and though we could use a little more speed with some things, it does fairly OK.

by kenone

A. It makes the remote site a standalone site if the WAN gets wonky
B. His boss wants a separate domain for that site.
C. It makes admin so much simpler with bigger groups.

by kchandley

In the geographic area we're in, phone lines, T1, and cable have less than 99.9 uptime and are flakey. We have frequent wan outages due to storm damage, car accidents, lightening strikes etc. We have two different circuits from different providers with a failover switch should one provider goes down, and we still have a few outages each year when both tier one providers go down.
The server is needed at the remote site to handle large file and application serving. There are too many users (more than 80) and it would be way too much traffic for a T1.

by wizard-09

You wouldn't tell him how to do his job he hired you for a reason because your the expert in the matter go set him straight lol

by kchandley

It has been made abundantly clear while I've worked here that the role of IT staff under him, is to follow orders first, and be an expert second. If I wanted to continue the debate with him, I could join the unemployment line with the last 8 people that held my job.

It's OK that he wants it done his way, I don't care about getting into a power struggle about it. I just want to know the best way to implement the solution within the parameters he has given. The only thing that matters is that he is happy. It does not matter if it is done within best practices and procedures.

by kchandley

That'd be OK as long as the "OK, Boss" sign was going to sign the paychecks over to me. Otherwise in the current economy, I'll do my job, which is not to be maverick expert, but to follow the orders I'm given. That's how corporate bureaucracy works. Where I work techs are a dime a dozen and I'm glad to have a steady job.

by wizard-09

It was a light hearted joke, I would be the same lol hope you find the answer :-p

by kchandley

Sorry if I misunderstood. I hope to find a good answer too. The parameters of the way that I must implement this solution create SOOOOOOOO much more work. But I get paid to work 9-5 either way so what difference does it make?

by ugadata

If this needs to be done yesterday, then you could set it as a workgroup for now.

In time as/if needs require then change the remote server to a DC within it's own Domain and create trust relationships between the Domains.

However, if you already know that you need the greater control over the remote network your choice of a 2nd Domain has been made for you.

by cg it

have the users at the other office remain remote users to the domain.

As long as they are not complaining about the network being slow or they get kicked off while working, your network is working.

As far as security, you already have that in place by requiring the users to log on using their domain accounts.

This discussion is closed to new replies.