> First off I must say I am a developer and not a network technician so my
> networking knowledge is limited.
>
>
> I have convinced my organization to let me set up my own test development
> domain with Active Directory. Our Development staff consists of 3
> developers, each with one physical computer, plus we have 4 physical
> computers - one running virtual server split into 3 seperate servers.
> Our goal is to isolate ourselves from the rest of the organization for
> testing and development. Also this would allow us to create users at
> will and change settings without affecting the main organization and take
> some of the pressure off network guys when we need changes to test.
>
> Each developer plan to load several different VPC's on their computer,
> each with a different test environment or development environment. Rarely
> will more than one VPC instance be running on a computer at a time.
>
>
> Our network is set up to use static IP's. No chance of changing this due
> to some legacy applications that prevent using DHCP.
>
> Our network guys suggested that we leave our host computer connnected to
> the main domain so we can still access production servers etc, and then
> set up each VPC to connect to our development domain. I am hoping to
> isolate our development vpc to the development domain to help ensure we
> don't actually publish or connect to a production environment or a end
> user connect to a development server. I am still in my planning stage
> for this, hopefully this is possible.
>
>
> My problem comes in how to set up each of the VPC's. I would hate to
> have to assign each a static IP address, this would not help reduce the
> work load on the network guys.
>
> Does anyone have any suggestions on what would be the best way to set up
> our environment?
>
> Thank you,
> Mike
>
>
>

> First off I must say I am a developer and not a network technician so my
> networking knowledge is limited.
>
>
> I have convinced my organization to let me set up my own test development
> domain with Active Directory. Our Development staff consists of 3
> developers, each with one physical computer, plus we have 4 physical
> computers - one running virtual server split into 3 seperate servers. Our
> goal is to isolate ourselves from the rest of the organization for testing
> and development. Also this would allow us to create users at will and
> change settings without affecting the main organization and take some of the
> pressure off network guys when we need changes to test.
>
> Each developer plan to load several different VPC's on their computer, each
> with a different test environment or development environment. Rarely will
> more than one VPC instance be running on a computer at a time.
>
>
> Our network is set up to use static IP's. No chance of changing this due to
> some legacy applications that prevent using DHCP.
>
> Our network guys suggested that we leave our host computer connnected to the
> main domain so we can still access production servers etc, and then set up
> each VPC to connect to our development domain. I am hoping to isolate
> our development vpc to the development domain to help ensure we don't
> actually publish or connect to a production environment or a end user
> connect to a development server. I am still in my planning stage for
> this, hopefully this is possible.
>
>
> My problem comes in how to set up each of the VPC's. I would hate to have
> to assign each a static IP address, this would not help reduce the work load
> on the network guys.
>
> Does anyone have any suggestions on what would be the best way to set up our
> environment?
>
> Thank you,
> Mike
>
>
>
>

>Consiering Virtual PC 2007 uses NAT for each VM, then if the LAN is using NAT
>there could be several layers to contend with in a given topology. You
>servers may be bound to to a hard coded IP or adapter so they mey be
>provisioned differently.
>
>"Mike Read" wrote:
>
>> First off I must say I am a developer and not a network technician so my
>> networking knowledge is limited.
>>
>>
>> I have convinced my organization to let me set up my own test development
>> domain with Active Directory. Our Development staff consists of 3
>> developers, each with one physical computer, plus we have 4 physical
>> computers - one running virtual server split into 3 seperate servers. Our
>> goal is to isolate ourselves from the rest of the organization for testing
>> and development. Also this would allow us to create users at will and
>> change settings without affecting the main organization and take some of the
>> pressure off network guys when we need changes to test.
>>
>> Each developer plan to load several different VPC's on their computer, each
>> with a different test environment or development environment. Rarely will
>> more than one VPC instance be running on a computer at a time.
>>
>>
>> Our network is set up to use static IP's. No chance of changing this due to
>> some legacy applications that prevent using DHCP.
>>
>> Our network guys suggested that we leave our host computer connnected to the
>> main domain so we can still access production servers etc, and then set up
>> each VPC to connect to our development domain. I am hoping to isolate
>> our development vpc to the development domain to help ensure we don't
>> actually publish or connect to a production environment or a end user
>> connect to a development server. I am still in my planning stage for
>> this, hopefully this is possible.
>>
>>
>> My problem comes in how to set up each of the VPC's. I would hate to have
>> to assign each a static IP address, this would not help reduce the work load
>> on the network guys.
>>
>> Does anyone have any suggestions on what would be the best way to set up our
>> environment?
>>
>> Thank you,
>> Mike
>>
>>
>>
>>