In my last post I talked about moving infrastructure services to the cloud. With the launch of Windows Server 2012 cloud services are a big push for Microsoft and I firmly believe the market is now mature enough for businesses to seriously consider running services full time with a public cloud supplier. In this post I’m going to take you through building a virtual public cloud on Microsoft Windows Azure.
With Microsoft’s release of Windows Server 2012 and System Center 2012 it’s clear that Microsoft’s big push is towards the cloud. System Center has been rebranded as a private cloud management suite and Windows Server 2012 is designed to cloud-optimise your IT. This post is an introduction to running infrastructure services in the cloud, the first in a series of posts about Windows Server 2012.
Last week after about two years away I had to do some more work on Windows Deployment Services and found myself writing a guide on how to add Windows Updates to an offline WIM file in WDS. It’s really simple so thought I’d share it here.
So it’s been a while since I had to use Windows XP and for security I’ve made sure that all my servers (Windows 2008 and R2, naturally) are "more secure" by only allowing computers that support Network Level Authentication to connect. Unfortunately I recently had to use a machine that was locked to Windows XP, which kind of scuppered me when I needed to do some remote administration in a hurry. Luckily, I remembered that Windows XP does support NLA – you just need to know how to configure it.
For the last week or so I’ve been playing around with Microsoft’s Remote Desktop Virtualization component of Windows Server 2008 R2. For those of you that haven’t used or heard of RD-V, it’s Microsoft’s free VDI offering, utilising Remote Desktop to initiate a connection and spin up a dedicated Hyper-V Virtual Machine for the user. Anyway, one thing that really bugged me was that I couldn’t get Aero Glass to work, no matter what I did. Everything I read said it should work, but it didn’t. Why not? Well, the answer was both simple and irritating. Aero Glass remoting doesn’t work under anything other than Windows 7 Enterprise or Ultimate.
This annoyed me immensely – why not include it in Windows 7 Professional?
Yesterday I had an interesting problem I had to fix. As you may or may not know, using Hyper-V within Failover Clustering sometimes requires the use of volume GUIDs for storage if you have more LUNs than drive letters available (like we do). What you may not know is that these GUIDs can, under some circumstances, change – completely screwing up Failover Clustering’s ability to move virtual machines between nodes.
So, I use Sky Broadband at home and it’s always been truly excellent. Great speeds, stable connection, everything you could want from an ISP. Until today, that is, when my Sky provided router died due to ‘a failed firmware upgrade’. Now, I work from home and Sky have remotely bricked my router. Nice of them. Even better, calling them up, it’s against their Terms of Service to use a third party router on their network. The icing on the cake? It’ll take 7-10 days for my replacement to turn up. So, frankly, I said ‘nuts to that’ and managed to find this wonderful site. Now I’m using my own router – with 802.11n networking to boot – rather than Sky’s.