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

Splunk that!

Saw this advert on Slashdot and went on to look for it and found the tour pretty neat to look at. Check out the demo too! So why would I need it? WHY NOT? I'd say. As an organization grows , new services, new data comes by, new logs start accumulating on the servers and it becomes increasingly difficult to look at all those logs, leave alone that you'd have time to read them and who cares about analysis as the time to look for those log files already makes your day, isn't it? Well a solution like this is a cool option to have your sysadmins/operators look at ONE PLACE and thus you don't have your administrators lurking around in your physical servers and *accidentally* messing up things there. Go ahead and give it a shot by downloading it and testing it. I'll give it a shot myself! Ok so I went ahead and installed it. Do this... [root@tarrydev Software]# ./splunk-Server-1.0.1-linux-installer.bin to install and this (if you screw up) [root@tarrydev Software]# /op