I think I may have screwed up but I need advice from those more knowledgeable than myself.
I do IT consulting work and one of my customers is a small manufacturing company, we will call CompanyA. This company has 3 servers, 2 of which are Domain Controllers and the other is a file server. There are a number of workstations, all of which are part
of the domain and all the users are domain users and access is controlled through Group Policy.
This company has acquired a smaller company, we will call CompanyB. CompanyB has one server and 3 workstations. The server acts as a file server and the user accounts are replicated on all computers to enable file sharing.
CompanyA wishes to do the production for CompanyB which means they need an efficient way to transfer design drawings from one company to another.
I installed a VPN capable router at each site and initiated a VPN connection between the two locations. This means adjusting the network address used by CompanyB.
To avoid the duplication of user accounts, etc, I decided to integrate CompanyB into the AD of CompanyA. I considered creating a sub-domain as one alternative or keeping a single domain and creating 2 sites. After studying the issue, I concluded, possibly
incorrectly, that a single domain with 2 sites was the way to go.
According I joined the server at CompanyB to the CompanyA domain, created user accounts for the people at CompanyB in the domain and promoted the server at CompanyB to be a Domain Controller so that should the VPN fail, everyone could still logon.
All worked well and I was very pleased with myself.
This morning the boss at CompanyB called wanting access to his server in order to do an update for their accounting software that is resident on the server. So now, I have this dilemma. Since only Domain Admins have administrative rights on the DC, I had
to give him access. Now, these are small companies with trusted employees so I am not terrified of this security breach, but it is not the right way to go.
I know having Domain Controllers host software is essentially not a good idea, but in an outfit this small it is a necessity since there is only one server. But I don't like the idea of having anyone at CompanyB having control over the CompanyA domain.
I was looking for an option to create an account that would be an administrator on CompanyB's server but not a Domain Administrator, but I can't find anyway to do that.
As I see it, I have 3 options, one of which is probably a non starter and I seek guidance as to the best way forward.
- Demote the CompanyB server from being a DC and have no Domain Controller at CompanyB. The boss could then become an administrator on the member server and do software updates.
- Roll back everything and instead create a different domain in the Forest and then set appropriate trusts to allow cross domain access where needed. This would work but as the two companies achieve closer integration might prove cumbersome in sharing data.
- Install another server to act solely as a Domain Controller. I am pretty sure this would be resisted on cost grounds. I could run a virtual server under the current server and make it a Domain Controller, but the CompanyB server only has 4 GB RAM and isn't
really up to this.
I am open to suggestions as to which path I should follow. If you have ideas that are superior to any of the 3 I outline above, I'd like to hear them as well.
Even though these are small companies, I like to set them up using the same tools as though they were larger companies as I believe that doing things the right way, even if a little more trouble, always pays off in the end.
Thanks in advance for any help.
Martin Horton