Re: Windows 2008 TS Memory
- From: "Schmeg" <sschmeg@xxxxxxxxx>
- Date: Mon, 14 Jul 2008 10:19:53 -0500
Thanks for the feedback.
My original plan was to use Hyper-V from the Windows 2008 32-bit standard
host as I wasn't aware Hyper-V was only supported on 64-bit. Knowing that, I
would likely pursue the VMWare product.
What do you consider as "very few users on the system before it is a
performance issue" and what would make it the performance hog - the
virtualization or other reasons?
Thanks
"Jeff Pitsch" <jeff@xxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OdAk4Wb5IHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
What are you using for virtualization? Keep in mind that Virtual Server
will give you lousy performance and Hyper-v is only supported on 64-bit.
Of course this will all depend on how many users you are planningo n the
server but in your configuration, yes it will work with PAE switch on the
host OS, you will get very few users on the system before it performance
is an issue.
Jeff Pitsch
Microsoft MVP - Terminal Services
"Schmeg" <sschmeg@xxxxxxxxx> wrote in message
news:%23MrEpMb5IHA.2064@xxxxxxxxxxxxxxxxxxxxxxx
I have a Windows 2008 Stanard 32-bit terminal server.
I need to run a Windows 2003 Standard 32-bit terminal server on it as a
virtual machine.
Our applications are not 64-bit compatible and do not have near term
plans to support it.
I know Windows 2008 Standard has a memory limit of 4G.
With the virtual machine scenario, I am limited to splitting the 4G or
could I physically put 8G in the box and split 4G for the host OS and 4g
for the guest OS ?
.
- Follow-Ups:
- Re: Windows 2008 TS Memory
- From: Jeff Pitsch
- Re: Windows 2008 TS Memory
- References:
- Windows 2008 TS Memory
- From: Schmeg
- Re: Windows 2008 TS Memory
- From: Jeff Pitsch
- Windows 2008 TS Memory
- Prev by Date: profile issues
- Next by Date: Re: Terminating a license on a thin client
- Previous by thread: Re: Windows 2008 TS Memory
- Next by thread: Re: Windows 2008 TS Memory
- Index(es):
Relevant Pages
|