M
Maurizio
Is it recommended to install PS 2007 in a Virtual Server?
Thanks,
Thanks,
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
B
Ben Howard
It's not a supported configuration from Microsoft, but then neither is VMWARE
and plenty of people use that. Would I recommend it? not for production, but
I would for development and test. I would recommend VMWARE though for
production.
As usual, way up your business requirements deploy as necessary.
HTH,
and plenty of people use that. Would I recommend it? not for production, but
I would for development and test. I would recommend VMWARE though for
production.
As usual, way up your business requirements deploy as necessary.
HTH,
M
Maurizio
Ben,
Thanks a bunch! This was very helpful!
Thanks a bunch! This was very helpful!
B
Ben Howard
You're welcome.
B
Bill Busby
I do not recommend using a virtual server in prod.
We have a pretty large virtualization push going on in my company (possibly
because we have about 900 Windows servers?) so we decided to play nice and
install Project Server 2007 on a virtual server. In our VMWare guest we were
allocated 1 GB RAM and a single CPU. VMWare took a good chunk of the RAM so
we were closer to the MS recommended minimum of 512K and the single CPU
causes our multithreaded queue to run serially. Testing went fairly well but
as soon as we opened the door to 15 project managers to publish new plans (no
resources were allowed in yet... thank <your choice of deity>). The server
nearly immediately began swapping the page file to disk at nearly 100%. We
resolved that by giving the guest another Gig of RAM and our newly empowered
box then began to peg the CPU at an average of approx 70% utilization with
frequent stretches at 100%. The app was sluggish and we frequently had 30 to
50 jobs pending in the queue. Our users were not impressed. We conferred with
our server team (one of the most professional and skill groups I've ever had
the good fortune to work with) and they recommended we pull out of the
virtual environment. The moved us to a physical blade with 2GB RAM and dual
core CPU. The server is hosting 40 project managers, 27 resource managers and
350 resources without breaking a sweat. Response time is great and the queue
processes fast enough that we rarely have more than four jobs pending when
activity is high.
We have a pretty large virtualization push going on in my company (possibly
because we have about 900 Windows servers?) so we decided to play nice and
install Project Server 2007 on a virtual server. In our VMWare guest we were
allocated 1 GB RAM and a single CPU. VMWare took a good chunk of the RAM so
we were closer to the MS recommended minimum of 512K and the single CPU
causes our multithreaded queue to run serially. Testing went fairly well but
as soon as we opened the door to 15 project managers to publish new plans (no
resources were allowed in yet... thank <your choice of deity>). The server
nearly immediately began swapping the page file to disk at nearly 100%. We
resolved that by giving the guest another Gig of RAM and our newly empowered
box then began to peg the CPU at an average of approx 70% utilization with
frequent stretches at 100%. The app was sluggish and we frequently had 30 to
50 jobs pending in the queue. Our users were not impressed. We conferred with
our server team (one of the most professional and skill groups I've ever had
the good fortune to work with) and they recommended we pull out of the
virtual environment. The moved us to a physical blade with 2GB RAM and dual
core CPU. The server is hosting 40 project managers, 27 resource managers and
350 resources without breaking a sweat. Response time is great and the queue
processes fast enough that we rarely have more than four jobs pending when
activity is high.