Short Track Racer
Join Date: Jul 2006
Location: Honolulu, Hawaii
Re: Test environment - at work
[quote author=murph182 link=topic=91395.msg1773419#msg1773419 date=1192115300]
1) if you have a domain controller that is not a member of the same domain as everything else at work, then the test computers shouldn't be part of a workgroup at all, but members of the test domain. And if you don't need them to join a domain, then you shouldn't be using a DC anyway.
2) a simple workstation utilizing the production network won't have any impact on that network (except in terms of whatever bandwidth it is using) unless the application you are testing requires AD, DNS, etc. And even then it won't actually do anything unless the app makes changes to AD/DNS (a bad thing that shouldn't happen anyway) or needs you to make changes to those services in order to function. And if that's the case, then see #1 above because the computer you are testing it on shouldn't be a member of a workgroup as you have it configured but a member of the test domain that you have created on your test domain controller.
3) you can use the production gateway and DHCP without a problem. You should probably add a new scope to the DHCP server for the test environment, and specify the test DC for DNS. The DC should obviously have a static IP on that subnet. Or you can set up DHCP in your test environment and block DHCP with an ACL on the router that separates your test and production environments. If these options are not possible, then you still shouldn't have any problems just using the production DHCP server, just remember to give your test domain DC a static IP.. You need to remember that domain controllers only service members of their respective domains. So as long as your test machines are members of the test domain, you won't have any issues with the production domain. The routers in your network will handle TCP/IP just the same, regardless of which domain it is from. The routers can't see such things, so it doesn't matter.
Can you be more specific about the app you are testing, and the network infrastructure of your environment? Is it a fairly simple so/ho type network with a single router? Or are you using enterprise class routing and switching gear, with multiple networks, etc.
Thanks so much for your time!
the software Im testing is System Center Essentials 2007
it requires a DNS and AD so that's why I have that setup
3 computers all plugged into a netgear 4-port firewall that plugs into our work connection
the only reason why Im hesistating is because I had it on the work domain while testing and it created some objects in the Group Policy on the DC and threw all the computers on the network off (firewall settings)
I'm pretty sure your answer will provide me with the help I need
once again, thanks so much, I just needed to hear someone else confirm