Adding external email addresses to an exchange Distribution Group

You need to create the external email addresses as Contacts in Active Directory. To do this, you'll need to leave the SBS wizards and use Active Directory Users and Computers.

1.) Open ADUC from Administrative Tools
2.)  Navigate to MyBusiness, right click and choose New -> Organizational Unit to create a new OU, and call it Contacts
3.)  Right Click on the new OU and select New -> Contact
4.)  Fill in the details for the contact, selecting an SMTP address - the SMTP address will be their external email address.
5.)  Now, you can add them to your distribution group(s)

Note: when you're adding them to the Distribution Group, you will need to explicitly include contact objects in the AD dialog box in the field "Select this object type".

Vmware 4.1 on a HP ML110G6

Just a quick note on this as you need to tweek the standard install (The ML110 is not on the Vmware supported hardware list). Vmware won't install on the system using the onboard SATA DVD drive, you need to use an external drive to run setup successfuly.

The reason it doesn't install is due to the way HP have setup the SATA controller. Unfortunately there is no other way around this as far as i know!

Microsoft Hyper V

While Microsoft continue to play catch up to VMware in the virtualisation market they seem to be lagging behind quite significantly in terms of the quality of their product. Judging by various well respected forums and my own experience of installation & rollout into a production enviroment there are quite a few problems of which i'll list out the 4 prevalant ones :

1. Slow Network Response.

This seems to be the number one issue with Hyper V, it can be resolve 90% of the time by disabling the tcpv4 Large offload stack on the Host NIC and the Virtual Server NIC, There does seem to be hardware issues in the remaining 10% of cases which can be resolved generally by changing the Physical NIC to one confirmed as supported by Hyper V

2. Long installation time.

Apparantly when Microsoft changed/upgraded from Virtual Server to Hyper V there was some legacy issues brought accross without resolution one of these legacy issues was the slowness of emulation of drivers during install which can lead to a very laborious install.

3. Network redundancy.

You are unable to link more than one NIC to a virtual switch

4. The Host operating system is also windows.

This doesnt sound like too much of an issue but it does turn out to be, It means that every time i have to run windows updates on the host system i have to shut down the Virtual servers. If an update fails or corrupts the Host operating system then i lose the virtual servers and lastly the host is susceptible to Virus's and security loopholes.


Most of the problems with Hyper V Microsoft say they are working on fixes for them but for my money i'm sticking with VMware purely and simply because it makes my live easier...