| Subject: | Safe way to deploy test Win2003 server on prod network so it can accessed from s |
| Posted by: | lchiu7 (lchi…@gmail.com) |
| Date: | 27 Feb 2007 |
We have a small network with 60 users. Windows 2003 server, Exchange,
DHCP, domain controller and AD (a number of different servers). Basic
services are file and print.
I am keen to put a test server on the network that I can install
Win2003, SharePoint (to test out document management), SQL Server 2003
and possibly Microsoft CRM etc. The tech guys said while they could
setup a server for me, they would not allow it to be connected to the
main network since it could impact production. Reasons included,
accidentally providing another DHCP server, possible problems with
users getting confused with what server to use, etc. I would have to
access it directly in the server room (not very practicable) or via a
separate physical cable!
This seems strange to me. If I disable DHCP on the test server,
provide no file and print services (don't really need them for
SharePoint I think), don't worry about connecting to AD and don't put
the server name in the local DNS so users would have to know the IP
address, what impact could that have on production?
Any gotcha's would be greatly appreciated.
Thanks
Larry