Re: Copy users and groups to test DC?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks to you and all the rest. I've got a lot to think about... Much
appreciated...

--
Regards,
Hank Arnold

"Oli Restorick [MVP]" <oli@xxxxxxxx> wrote in message
news:e3KUorTZFHA.3984@xxxxxxxxxxxxxxxxxxxxxxx
> This won't work, and won't be reliable. The necessary DNS information
> about the test domain will not be available to clients querying the
> production domain, and you said in your original post that you wanted
> users to be able to log in to the test or production domains. Presumably,
> you want them to be able to do so from the machines they normally log in
> to.
>
> For this to happen, you need your test domain to trust the production
> domain (test trusts the users of the production domain to use its
> resources). You will also need the machines in the production domain to
> be able to resolve DNS queries about the test domain. In your situation,
> I think you should be looking at keeping DNS for test on the test DC
> itself. You can then use either secondaries or conditional forwarding on
> the DNS servers in the production domain. This will allow clients of the
> production domain to be able to log in and use resources of the test
> domain without you having DNS records from the test domain sitting on your
> production DNS servers.
>
> Hope this helps and makes sense.
>
> Regards
>
> Oli
>
>
> "Hank Arnold" <rasilon@xxxxxxx> wrote in message
> news:eVlFssPZFHA.1512@xxxxxxxxxxxxxxxxxxxxxxx
>> Both domains are in the same subnet. The test server is the DC for the
>> test domain. It is also the primary DNS for the test domain.
>>
>> I currently have it pointing to the production DNS server as the
>> secondary DNS. Is this a problem? Also, if I do use this tool, I want it
>> to be a one time/one direction thing. I can't allow anything happening in
>> the test domain to be reflected in the production domain...
>>
>> --
>> Regards,
>> Hank Arnold
>>
>> "Ulf B. Simon-Weidner [MVP]" <nospam2-ulf@xxxxxxxxxxxxxxxxxx> wrote in
>> message news:%23LVCKOFZFHA.2768@xxxxxxxxxxxxxxxxxxxxxxx
>>>
>>> Hi Oli,
>>>
>>> Thanks for pointing that possibility out - I was completely into the
>>> "not-connected testdomain with same name scenario".
>>>
>>> Also we need to mention here that the testdomain and the production need
>>> to have different DNS and NetBios names, and password export needs to be
>>> enabled if necessary.
>>
>>
>
>


.

Relevant Pages