Skip to main content

Exchange 2007 Testbed with VMware Server

This is an interesting multi-part series of setting up exchange on VMware.

If you have read my previous article [here] about some of the initial thoughts that I have had about the migration, you will have seen that I plan to use a method called “Bunny Hopping” – essentially as I have financial constraints on this migration (e.g I have to use my existing hardware) I have purchased a server which I intend to add into my Exchange organization and then move the mailboxes from one cluster onto it – then re blow the old clusters with Windows 2003 x64 and Exchange 2007 then move the mailboxes back – then repeat the process for the other clusters (long winded I know but the Organisation is not prepared to replace what was £70,000 of new hardware 24 months ago and I can kind of see the reasoning).


Excellent multi-part series! Why I like it?
  • Its detailed
  • It has tips and advices
  • It has print screens here and there
Strongly advised to check this out. Part 1 and Part2.

Comments

Popular posts from this blog

Security: VMware Workstation 6 vulnerability

vulnerable software: VMware Workstation 6.0 for Windows, possible some other VMware products as well type of vulnerability: DoS, potential privilege escalation I found a vulnerability in VMware Workstation 6.0 which allows an unprivileged user in the host OS to crash the system and potentially run arbitrary code with kernel privileges. The issue is in the vmstor-60 driver, which is supposed to mount VMware images within the host OS. When sending the IOCTL code FsSetVoleInformation with subcode FsSetFileInformation with a large buffer and underreporting its size to at max 1024 bytes, it will underrun and potentially execute arbitrary code. Security focus

OS Virtualization comparison: Parallels' Virtuozzo vs the rest

Virtuozzo's main differentiators versus hypervisors center on overhead, virtualization flexibility, administration and cost. Virtuozzo requires significantly less overhead than hypervisor solutions, generally in the range of 1% to 5% compared with 7% to 25% for most hypervisors, leaving more of the system available to run user workloads. Customers can also virtualize a wider range of applications using Virtuozzo, including transactional databases, which often suffer from performance problems when used with hypervisors. On the administration side, customers need to manage, maintain and secure just a single OS instance, while the hypervisor model requires customers to manage many OS instances. Of course, the hypervisor vendors have worked hard to automate much of this process, but it still requires more effort to manage and maintain multiple operating systems than a single instance. Finally, OS virtualization with Virtuozzo has a lower list price than the leading hypervisor for comme...