Re: Virtual SBS2003 R2 Test Machine Hosted by WXP X64 SP2

Yeppers! That's the ONLY reason I'm trialing it as a VM Host.

Thanks Charlie...


"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:u6PhyJBIHHA.816@xxxxxxxxxxxxxxxxxxxxxxx
Server 2k3 EE is not particularly more or less efficient. BUT, it has an
interesting VM licensing difference, which I'm sure you're aware of.

--
Charlie.
http://msmvps.com/xperts64


"Gary J. Dikkema" <gary_d-no-spam-@xxxxxxx> wrote in message
news:e9jBe2vHHHA.3872@xxxxxxxxxxxxxxxxxxxxxxx
Interesting Charlie!

Is one more efficient than the other at this hosting task?

I chose the EE Trial thinking I might want to try running multiple
versions of VS Server running and hosting.

Thanks!


"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5D4B132E-CF02-433F-8B9E-26887BBE1B37@xxxxxxxxxxxxxxxx
Not my experience at all. I have x64 EE as my hosting environment as
well on one box. Other is still running XP x64 because it needs a legacy
app that is ported to XP x64, but not to Vista x64 or LH Server.

--
Charlie.
http://msmvps.com/xperts64


"Gary J. Dikkema" <gary_d-no-spam-@xxxxxxx> wrote in message
news:%23%23X8PHtHHHA.4056@xxxxxxxxxxxxxxxxxxxxxxx
Not sure.

In my case that Server 2K3 was Enterprise Edition (EE) X64... tried
promoting it to a DC and it failed... perhaps it was a wait on the VS
R2 - which hadn't been auto started - that might have been it. <VBG>
however, I've encountered things working differently on EE X64 boxes so
attributed it to that... seems 'things' work better if the EE box
isn't the host... at least that is my finding/opinion.

Using local account on the host means that it won't Auto Update thru
WSUS - at least that was my finding with the set up that I have.... and
to me that is not ideal as a lot of things that rely on being part of
the domain won't work either...

Just to clarify, I do have a WXP SP2 X64 hosting my R2, a WS2k3 SE T/S
box as well as a WXP SP2 X86 box. The host is a member on the R2 domain
which means Auto Update et al works. If I wait on the R2 virtual
machine to start up before doing anything that needs domain resources
it all seems to work. This trial setup is a 2 Gig AM2 X2 mobo which
means it will perform better on my AMD64 4 gig box.

Thanks for your help Charlie...



"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:A737BB5A-992B-4BDF-B082-A6BCE1D1AE01@xxxxxxxxxxxxxxxx
What is the problem? I've got a Server 2k3 box sitting next to me. It
is a member server of the domain I'm logging in to, for which the DC
is one of its virtual machines. Not ideal, but if I'm patient and wait
for the VMs to all get started, it works.

There are three ways to do this:
1.) make the host a secondary DC in the domain
2.) use _local_ accounts on the host
3.) be patient until your DC's get started before logging in. (You
would, obviously, need to set your guest(s) to autostart.)

--
Charlie.
http://msmvps.com/xperts64


"Gary J. Dikkema" <gary_d-no-spam-@xxxxxxx> wrote in message
news:u20ADUsHHHA.3780@xxxxxxxxxxxxxxxxxxxxxxx
So... that begs the question of what is so special about WS2003 EE R2
X64?

Tried to use it as the host in place of WXP X64 and had no joy...
seems the security on EE is a little more stringent than WXP X64, or
so I thought.

Comments?

TIA.


"Charlie Russel - MVP" <charlie@xxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:C5D88479-D13A-46AB-AD4D-0C0652F6AD3B@xxxxxxxxxxxxxxxx
Yes, I use Virtual Server for this exact scenario on XP x64. For a
test environment, it's fine.

--
Charlie.
http://msmvps.com/xperts64


"SuperGumby [SBS MVP]" <not@xxxxxxxxxxx> wrote in message
news:%23IOlVEXHHHA.4636@xxxxxxxxxxxxxxxxxxxxxxx
it should eventually but you might try going to Microsoft Update
just get to the point where you scan for updates, but I'm not sure
what will happen with the beta.

re making the server available before logon, you would need to use
Virtual Server which can be told to run a vm at startup. VS is not
supported for production use under XP but it does work quite well.

"Gary J. Dikkema" <gary_d-no-spam-@xxxxxxx> wrote in message
news:e3Kub0WHHHA.4636@xxxxxxxxxxxxxxxxxxxxxxx
And... the WXP X64 host doesn't get registered with WSUS...

Darn!

"Gary J. Dikkema" <gary_d-no-spam-@xxxxxxx> wrote in message
news:eArrEZWHHHA.3292@xxxxxxxxxxxxxxxxxxxxxxx
Finally...

I have the following virtual guest machines running... WXP X86,
WS2k3 T/S and my SBS2003 R2 PE box.

Everything runs well... so today I decided to add the host WXP
X64 SP2 (Beta) to the R2 domain.

After doing that and rebooting when I try and log into the domain
it says the domain is not available. Which sort of makes sense as
the R2 box being a virtual machine won't come alive until after
the Host is running and starts it.

Just wondering if there's a way around this...perhaps auto
starting R2 so that it's running when I log into the Host? Is
such a thing possible? For now I log in the WXP X64 SP2 local
machine and everything runs as before... and the X64 box is a
member machine on the domain.

Thanks in advance...

Oh...

FYI, connecting to the domain using RWW and the T/S box is
quick.... considering all this is happening within a 2 GB memory
environment. Please keep in mind this is a Test box for proof of
principle. If I can sort out the remaining quirks I have a prod
X64 box with 4 Gigs of ram to drop all this onto... personally, I
think this is a good DRP method... images are supposedly
transportable across hosts... supposedly! <VBG>


















.