Witchcraft

I've recently gotten my hands on a new PC that has the Intel-VT instruction set enabled.

What's the first thing I do? 

Install OS X Lion. On VMWare ESXi.

Time will tell how it behaves as it's going to replace my current mixed (and not very nice( environment (Windows Server 2K8 running iTunes serving to an apple TV and Debian (a broken Squeeze install) running Twonky serving to my PS3. Now theres going to be one machine doing it all.

Epic.

802.1q VLAN Tagging/VTP with Windows Hyper-V R2

I came across this potentially useful piece of information whilst trying to get a new guest VM to speak to it's default gateway. 

It was set to use a VLAN on a shared interface on the firewall (VLAN 1,2&3), this was a new VLAN and was configured in the same manner as the other two functioning VLANs. The whole way through both switches (allowing VLAN trunking, configuring the allowed VLANs on the switch ports affected etc.) but it was not working, it couldn't ping it's gateway, nor could the gateway ping it.

The problem was that the Hyper-V Host was not  trunking all VLANs, only specified ones. I don't know if this is an out of the box setting, but I don't recall changing it, or adding the other VLANs to it. 

To rectify this, open up the Host properties in SCVMM or in Hyper-V Manager, then  navigate to the Network tab.

Click on the affected connection (LAN1 in this case) then select Edit.(You should see that the VLAN is set to Trunk already) If this isn't the case, you may need to allow trunking on the next screen as well.

Now you can either add the VLAN manually, or select the Trunk All VLAN ids. This will then populate the list below with all VLANs 1-4095. The checkbox will disappear the next time you open this but the list remains populated.

If you are managing a lot of VLANs (100's) or if you're only in charge of the Virtualisation technology, I might suggest allowing all, if you have a close coupling with the network team (or you *are* the network team) then allowing only specified VLANs may be a better, safer solution.

Exchange 2010 and iPhone with ActiveSync

You need to make sure that the following is set up when attempting to use an iPhone with iOS > 4 with Exchange > 2010 SP1.

1. In the Hub Transport section under Organization Configuration, ensure that both the "Name" and "Accepted Domain" do not contain any spaces. I recommend using the accepted domain as the name.  This does not matter if it is an Authoritative, Internal or External Relay. You can use the GUI to do this, i.e. right click on the domain with spaces and select properties. Or use the Exchange cmdlet

Set-AcceptedDomain –Identity <value> -Name “ValidSMTPDomainName” 

2. You need to reenable inheritance of permissions from parent if you are adding privileged accounts, i.e. member of Domain Admins. 

To do this, open up Active Directory Users and Computers, then click on View, and then click on Advanced Features. 

Right click on the affected user, then select "Properties". Go to the "Security" tab and click "Advanced". Then enable "Include inheritable permissions from this object's parent" Click Apply and OK.