RE: [ActiveDir] OT: Virtual Server 2005

2004-12-08 Thread Noah Eiger
Title: RE: [ActiveDir] OT: Virtual Server 2005 Hi Glenn: I have been building a configuration similar to what you recommend, but using RRAS (I don't own ISA). I have RRAS running on the physical host. This has two physical NICs (ipconfig at the end of this post): ProductionLAN and TestLAN

RE: [ActiveDir] OT: Virtual Server 2005 NEVER MIND

2004-12-08 Thread Noah Eiger
Title: RE: [ActiveDir] OT: Virtual Server 2005 The answer is that you should have nothing entered in the default gateway field for the internal (TestLAN) interface. Traffic is flowing now. Sorry to waste the bandwidth. -- nme From: Noah Eiger [mailto:[EMAIL PROTECTED

RE: [ActiveDir] OT: Virtual Server 2005

2004-12-01 Thread Glenn Corbett
PROTECTED] Subject: RE: [ActiveDir] OT: Virtual Server 2005 Thanks. From your descriptions, I think I would want to use NAT only on the NIC connected to the production network. That is, have all of the traffic from the virtual network appearing as a single address on the production network. Since

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-29 Thread Bernard, Aric
configuration should not negatively impact anything HTH Aric Bernard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger Sent: Sunday, November 28, 2004 9:50 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Virtual Server 2005 Thanks, Glenn

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-29 Thread Your Name
Thanks. From your descriptions, I think I would want to use NAT only on the NIC connected to the production network. That is, have all of the traffic from the virtual network appearing as a single address on the production network. Since I want everything on the test network (virtual and

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-29 Thread Bernard, Aric
:[EMAIL PROTECTED] On Behalf Of Your Name Sent: Monday, November 29, 2004 11:15 AM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] OT: Virtual Server 2005 Thanks. From your descriptions, I think I would want to use NAT only on the NIC connected to the production network. That is, have all

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-24 Thread Glenn Corbett
ry to each VS to speed up performance, but hey, money can fix that *grin*. Glenn From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah EigerSent: Saturday, 20 November 2004 5:27 PMTo: [EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual Server 2005 Ok. Lets just say that

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-21 Thread Robert Bobel
Hi Noah, I prefer the sysprep/copy method; although using the differencing disks option is attractive. The oringinal system I'm going to SYSPREP is always mutli-homed. The first NIC I put into Host Only mode so it talk to other Hosts on my system. The second NIC I NAT/Bridge to the external

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-20 Thread Ulf B. Simon-Weidner
Desmond[EMAIL PROTECTED]Payton on the web! www.wpcp.orgv - 773.534.0034 x135f - 773.534.8101 From: [EMAIL PROTECTED]Sent: Fri 11/19/2004 3:16 PMTo: [EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual Server 2005 I don't use sysprep. I just use newsid from sysinternals. T

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-20 Thread Grillenmeier, Guido
PMTo: [EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual Server 2005 Thanks all. I will play around with the various methods of duplicating servers (Al, I assume by PXE you mean in combination with RIS? Do you use a virtual RIS server?) As for the networking portion, I find that when I add

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-19 Thread Bernard, Aric
An internal virtual network can be configured to allow all Virtual hosts to communicate together without interacting with other physical hosts on the VS2005 servers real network. VMs can be connected to the real network of the VS2005 server allowing them to interact with all hosts on the

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-19 Thread Mulnick, Al
Networking outside the box is usually done by adding the virtual host to the phys host network card. The phys NIC acts as a router in this case and everything is NAT'd off to the external network. That's the same for letting the hosted OS access anything off the host server whether internet

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-19 Thread Mulnick, Al
RIS is just one way of doing it. Any PXE system could be used I would imagine ;) From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah EigerSent: Friday, November 19, 2004 4:21 PMTo: [EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual Server 2005 Thanks all. I will play

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-19 Thread Bernard, Aric
] Subject: RE: [ActiveDir] OT: Virtual Server 2005 Thanks all. I will play around with the various methods of duplicating servers (Al, I assume by PXE you mean in combination with RIS? Do you use a virtual RIS server?) As for the networking portion, I find that when I add a virtual host

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-19 Thread Brian Desmond
! www.wpcp.orgv - 773.534.0034 x135f - 773.534.8101 From: [EMAIL PROTECTED]Sent: Fri 11/19/2004 3:16 PMTo: [EMAIL PROTECTED]Subject: RE: [ActiveDir] OT: Virtual Server 2005 I don't use sysprep. I just use newsid from sysinternals. Then I edit the .vmc to reflect the new VS name/location. I'm that lazy

RE: [ActiveDir] OT: Virtual Server 2005

2004-11-19 Thread Noah Eiger
Ok. Lets just say that was scary-easy (i.e., deploying new machines). Thanks! Wow, if only real life could run in RAM. Someone asked me to describe generally what I was looking to do. I want to setup a test environment that contains: 2 DCs 1 Exchange box 1 database server 1+ XP Pro