Please be aware that the instructions differ significantly between AeroFS versions, due to AeroFS changing under the hood. Please be very careful that you check which version you are working with before following any instructions. AeroFS 1.0.0-1.0.1 This was tested under AeroFS 1.0.1 and 1.0.0 and Hyper-V 2012 R2. It may not work for your environment. This is not a supported configuration. You're on your own. Sign up for the private cloud edition, and download the OVA file from the AeroFS if you don't already have it.

This post is largely for future me. I'm fed up with (re)writing/(re)discovering some of these queries. However, I also hope it can help other people. This post was written specifically whilst I was finishing up with an Exchange 2010 installation. However, should work verbatim with 2007 and some of the queries may require a little alteration for 2013. If you're still on 2003. I'm sorry. So your Exchange server has a w3wp instance with high memory and cpu.

The important thing to remember is that in Exchange 2013 Public Folders don't really exist like they used to. They're basically mailboxes. In this particular scenario Public Folders were accessible internally, but not via Outlook Anywhere (or Outlook RPC over HTTPS if you're old). This problem can manifests where the email address policy that applies to the Public Folder mailbox does not assign an email address that can be configured by autodiscover.

In the run up to Windows 2012 R2 I've not been paying as close attention as I would normally, meaning that I seem to have missed out on an interesting new feature in powershell 4 called Desired State Configuration (or DSC).

Example configuration to ensure that Hyper-V feature is installed on hv01-hv03 # Basically a block that can be used to generate a file Configuration HyperVNodeCfg { Node ("hv01", "hv02", "hv03") { WindowsFeature HyperVFeature { Ensure = "Present" Name = "Hyper-V" } } } # Compile to MOF HyperVNodeCfg -OutputPath HyperVNodeCfg # Apply the MOF Start-DscConfiguration -Path HyperVNodeCfg -Wait -Verbose It ships with Windows 8.

One of the most heralded features in Windows Server 2012 (previously known as Windows Server 8) is support in Hyper-V for virtual machine replicas. If you're familiar with VMWare it's similar to Site Recovery Manager, for Xen you're probably looking at Remus, and Kemari for KVM (bear in mind that none of these products are necessarily exactly the same, but close enough). Virtual Machine replication across sites is very attractive. You get a lot of flexibility with minimal effort.

Despite being a topic that I've discussed extensively at work, over the last 12 months I've made no less than 4 attempts at organising my thoughts coherently into a blog entry. I hope that I've finally got it. In my mind System Administration falls under 2 general families; Enterprise and Jack of All Trades. To me enterprise administrators manage large systems, and are generally focused on their specific trade - be it systems or network.

I'm openly paranoid about many things. Probably a secondary reason I'm basically bald at 25. The future of my profession is one I'm very paranoid about. It's one I love, despite all my moanings, and as the world starts it's seemingly inexorable move back to the mainframe^Wcloud, I fear that as time progresses we'll be in a world where there are few of us outside of large cloud companies. How much longer is on-premises server hardware still required?

I know that the content of this entry is common knowledge among certain circles, especially after an email to van Hauser of The Hackers Choice(THC), and some time spent this afternoon checking out a few mailing lists. However this is not who I'm aiming this post at. Or that's what I'm telling myself so that I don't feel like I've wasted a few hours of my life over the course of 2 days.