[AccessD] Setting up a Domain.

I wouldn't reuse a vmc file, instead, just setup a new virtual machine and just use the .vhd.  The virtual machine will 'boot' that virtual hard drive just fine.  I've never had a problem booting a virtual machine from a .vhd from Virtual PC in Virtual Server (or vice versa).

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Erbach
Sent: Wednesday, June 03, 2009 6:36 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Setting up a Domain.

Drew,

>> When you setup a domain, you need your domain controller to be on
whenever the network is in use, otherwise authentication fails, and
things will go bonkers! ;) <<

That makes perfect sense.  I had been trying Virtual Server 2005 for a
short time only because that was the only (free) way that I could try
out Windows Vista...but I uninstalled it because I couldn't seem to
get VS to recognize that I, indeed, did have a VMC/VHD set up already.
 I think I'll give it another shot for trying out this domain thing.

Since I already have Windows Server 2003 set up as a virtual PC, what
do I need to go through to "convert" it to run under Virtual Server
2005?

Steve Erbach

On Wed, Jun 3, 2009 at 4:22 PM, Drew Wutka <DWUTKA at marlow.com> wrote:
> Absolutely.... In fact, the demo I am putting together here is running
> in Virtual PC.  I've set the network connection to be 'local' only, so
> it's just like have a server on a brand new 'blank' network.
>
> Now, to setup a primary DC using Virtual PC, I would really recommend
> using Virtual Server, not Virtual PC, because Virtual server will allow
> you to have your virtual machines to startup with the host computer.
> When you setup a domain, you need your domain controller to be on
> whenever the network is in use, otherwise authentication fails, and
> things will go bonkers! ;)
>
> Drew
The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.