New Apple keyboard

Earlier today, I dropped into the Apple Store in Solihull to pick up a case to protect my iPhone and, as is so often the case with me and computer hardware, I ended up buying something else. Not the 17″ MacBook Pro that I’m still seriously tempted by but the new Apple chiclet keyboard.

Apple Keyboard (top view)It’s very “Logan’s Run” (well, 1970s Sci-Fi anyway) but also incredibly comfortable to use, with none of the “stickiness” of the keys on my previous Apple keyboard. If I had one criticism, it would be that the return key on the UK keyboard is a little skinny (the graphic here shows the US version) but nevertheless this was definitely a worthwhile upgrade. Now it only they’d do something about that damned “mighty” mouse

Say hello to iPhone

Apple iPhone (UK model)So I did it, I bought an iPhone – two in fact: one whilst I was in the States earlier this week, which I then returned because once the sales tax was added it was nearly as expensive as buying one in the UK and the risk of having a brick on my hands was too great if the AT&T unlock went wrong; the second a few minutes ago from an O2 store close to where I live.

As for all the people who queued up to get one – why? I just waited until the kids were in bed, drove into town and strolled in to the store with no queues whatsoever. One question I do have though… if, as reported, this handset is not subsidised, then why did O2 advise me to buy additional insurance because a replacement unit if this gets lost, stolen or damaged (outside the warranty conditions) will be £600 rather than £269?

Windows Server 2008 Worldwide Technical Workshop

There haven’t been many blog posts on the site this week but it’s been a full-on week in Redmond at at the Windows Server 2008 Worldwide Technical Workshop.

Not many people will write about their experience of attending a conference for the IT industry press (I’m not a journalist – just a blogger) but it’s been great to be labelled as a member of the “worldwide press” (I kid you not) for a few days and I wanted to write something about the experience.

Sign for Building 33It was a long trip out here and I was pretty tired but also very exited about the event – my first visit to the Microsoft Campus. As I waited for the coach that took us from the hotel to the Microsoft Conference Center, I got chatting to Paul Hearns, the editor at ComputerScope (of one of Ireland’s leading IT trade publications) and realised that I was probably one of only a small number of bloggers at the event – with the distinction being that journalists write objective opinion pieces (at least, that’s the idea – PR is a strong influencing factor) and that IT bloggers are often enthusiastic techies, with less focus (but an increasingly wide audience).

The calibre of the other attendees was soon apparent as, the first person I saw after registration was Paul Thurrott (best known for his SuperSite for Windows, WinInfo Updates and the Windows Weekly podcast). Mark Wilson and Paul Thurrott in 2007I hold Paul’s work in high regard as he is one of the few tech writers that I know of who manages to write objectively about both Windows and Macintosh topics (provoking criticism from both sides – often unfounded). I introduced myself (not expecting Paul to know my work, even though we have exchanged e-mails on occasion) but I’m afraid it’s difficult not to appear a little geeky when you ask someone if they would mind posing for a photo with you.

As the day moved on, I met journalists whose work I was familiar with but whom I only knew from their bios – people like Karen Forster and David Chernicoff – and later I introduced myself to Steven Bink, who constantly amazes me for being able to pump out so many Microsoft news stories from his site.

I also met John Savill, who I always thought was a) American and b) a professional technical writer – it turns out that he’s actually English and, just like me, he has a day job working for a large IT company and writes in his spare time. Also, just like this blog, John’s Windows FAQs started out as being for his own benefit and has become a useful resource for other people. And it turns out that John and I are not alone in this world of part-time IT writers as I hooked up with James Bannan (best known for his work at APC Mag) and Andrew “Dugie” Dugdell.

One thing I was totally unprepared for was the size of the Microsoft Campus. I don’t know the exact size but it must cover at least a square mile, on both sides of I-520. I’m not sure how this compares to the GooglePlex or Apple’s base in Cupertino but certainly puts 5 buildings in Thames Valley Park into context.

Another thing that I found interesting is that there is no building 7… and being sent to a meeting in building 7 is a common prank to play on new employees (thanks to John Howard for providing that little piece of trivia – Scott Guthrie has more trivia about the various buildings on the Microsoft campus).

I’m on my way home now, worn out after 24 sessions in 3 days and yes, I drank the Kool-aid (actually it was Mountain Dew…), picking up a stack of information about Windows Server 2008, as well as meeting some great people. Expect to see plenty of Windows Server 2008 information posted here over the coming weeks.

Off to Redmond

In a few hours time, I’ll be catching a flight to Seattle and then spending the next three days as a guest of Microsoft at the Windows Server 2008 Worldwide Technical Workshop in Redmond. Without wanting to sound like a fanboy (I believe that one of the reasons I was invited is that, in spite of generally being an advocate of Microsoft technologies I’m also critical when they get something wrong – I’d like to hope that the same goes for Apple and the various Linux vendors too), I’m really excited. Not because a suburb of Seattle is top of my list of places to visit (it isn’t) but because I have built my career on implementing Microsoft products and technologies and, even though I work in the Microsoft Practice at a leading IT services company, this invitation has come about in recognition of the work that I put into this blog and am truly honoured to have been invited.

I haven’t dared mention this trip to anyone other than family, close friends and colleagues (just in case something happened that meant I couldn’t go) but I do know that there are several readers of this blog at Microsoft (both in “corp” and in the UK subsidiary) and I’d like to say a big “thank you” to whoever put my name forward.

Creating and managing a virtual environment on the Microsoft platform

Several months back, I blogged about a Microsoft event with a difference – one which, by and large, dropped the PowerPoint deck and scripted demos in favour of a more hands-on approach. That was the Windows Vista after hours event (which I know has been popular and re-run several times) but then, a couple of weeks back, I attended another one at Microsoft’s new offices in London, this time about creating and managing a virtual environment on the Microsoft platform.

Now, before I go any further I should point out that, as I write this in late 2007, I would not normally recommend Microsoft Virtual Server for an enterprise virtualisation deployment and tend to favour VMware Virtual Infrastructure (although the XenSource products are starting to look good too). My reasons for this are all about scalability – Virtual Server is limited in a number of ways, most notably that it doesn’t support multiple-processor virtual machines – it is perfectly suitable for a workgroup/departmental deployment though. Having said that, things are changing – next year we will see Windows Server Virtualisation, the management situation is improving with System Center Virtual Machine Manager (VMM).

…expect Microsoft to make a serious dent in VMware’s x86 virtualisation market dominance over the next couple of years

Throughout the day, Microsoft UK’s James O’Neill and Steve Lamb demonstrated a number of technologies for virtualisation on a Microsoft platform and the first scenario involved setting up a Virtual Server cluster, building the second node from a Windows Deployment Services (WDS) image (more on WDS later…) and using the Microsoft iSCSI target for shared storage (currently only available as part of Windows Storage Server although there is a free alternative called Nimbus MySAN iSCSI Server) together with the Microsoft iSCSI initiator – included within Windows Vista and Server 2008 (and available for download on Windows 2000/XP/Server 2003).

When clustering Virtual Server, it’s important to understand that Microsoft’s step by step guide for Virtual Server 2005 R2 host clustering includes an appendix containing a script (havm.vbs) to add as a cluster resource in order to allow servers to behave well in a virtual cluster. Taking the script offline effectively saves the virtual machine (VM), allowing the cluster group to be moved to a new node and then bringing the script back online will restore the state of the VM.

After demonstrating building Windows Server 2008 Server Core (using WDS) and full Windows Server 2008 (from an .ISO image), James and Steve demonstrated VMM, the System Center component for server consolidation through virtual migration and virtual machine provisioning and configuration. Whilst the current version of VMM only supports Virtual Server 2005 and Windows Server Virtualisation, a future version will also support the management of XenSource and VMware virtual machines, providing a single point of management for all virtual machines, regardless of the platform.

At this point, it’s probably worth looking at the components of a VMM enterprise deployment:

  • The VMM engine server is typically deployed on a dedicated server, and managed from the VMM system console.
  • Each virtual server host has a VMM agent installed for communication with the VMM engine.
  • Library servers can be used to store templates, .ISO images, etc. for building the virtual infarstructure, with optional content replication using distributed file system replication (DFS-R).
  • SQL Server is used for storage of configuration and discover information.
  • VMM uses a job metaphor for management, supporting administration from graphical (administration), web (delegated provisioning), or command line interfaces (the command line interface is through the use of VMM extensions for Windows PowerShell, for which a cmdlet reference is available for download and the GUI interface allows identification of the equivalent PowerShell command).

Furthermore, Windows Remote Management (WinRM/WS-Management) can be used to tunnel virtual machine management through HTTPS, allowing a virtual host to be remotely added to VMM.

VMM is currently available as part of an enterprise server management license; however it will soon be available in workstation edition, priced per physical machine.

The next scenario was based around workload management, migrating virtual machines between hosts (in a controlled manner). One thing that VMM cannot do is dynamically redistribute the workload between virtual server hosts – in fact Microsoft were keen to point out that they do not consider virtualisation technology to be mature enough to make the necessary technical decisions for automatic resource allocation. This is one area where my opinion differs – the Microsoft technology may not yet be mature enough (and many organisations’ IT operations processes may not be mature enough) but ruling out dynamic workload management altogether runs against the idea of creating a dynamic data centre.

It’s worth noting that there are two main methodologies for virtual machine migration:

  1. Quick migration requires shared storage (e.g. in a cluster scenario) with the saving of the VM state, transfer of control to another cluster node, and restoration of the VM on the new node. This necessarily involves some downtime but is fault tolerant with the main considerations being the amount of RAM in the VM and the speed at which this can be written to or read from the disk.
  2. Live migration is more complex (and will not be implemented in the forthcoming release of Windows Server Virtualization), involving copying the contents of the virtual machine’s RAM between two hosts whilst it is running. Downtime should be sub-second; however there is a requirement to schedule such a migration and it does involve copying the contents of the virtual machine’s memory across the network.

Some time ago, I wrote about using the Virtual Server Migration Toolkit (VSMT) to perform a physical to virtual (P2V) conversion. At that time, the deployment technology in use was Automated Deployment Services (ADS) but ADS has now been replaced with Windows Deployment Services (WDS), part of the Windows Automated Installation Kit (AIK). WDS supports imaged deployment using Windows imaging format (.WIM) files for installation and boot images or legacy images (not really images at all, but RIS-style file shares including support for pending devices (prestaged computer accounts based on the machine’s GUID). P2V capabilities are now included within VMM, with a wizard for gathering information about the physical host server, then converting it to a virtual format, including analysis of the most suitable host using a star system for host ratings based on CPU, memory, disk and network availability. At the time of writing, VMM supports a P2V conversion as well as virtual to virtual (V2V) conversion from a running VM (strangely, Microsoft still refer to this as P2V) and V2V file format conversion and optimisation (from competing virtualisation products) but not virtual to physical (V2P) conversion (this may be possible using a Windows Vista System Restore but there would be issues around hardware detection – success is more likely by capturing a virtual machine image in WDS and then deploying that to physical hardware). In addition, VMM supports creating template VMs by cloning a VM that is not currently running and it was also highlighted that removing a VM from VMM will actually delete the virtual machine files – not simply removing them from the VMM console.

The other components in the virtual machine management puzzle are System Center Operations Manager (a management pack is available for server health monitoring and management, performance reporting and analysis, including this ability to monitor both the host server workload and the VMs running on the server), System Center Configuration Manager (for patch management and software upgrades) and System Centre Data Protection Manager (DPM), which allows for virtual machine backup and restoration as well as disaster recovery. DPM builds on Windows’ Volume Shadow Copy (VSS) technology to take snapshots of running applications, with agents available for Exchange Server, SharePoint, SQL Server and Virtual Server. Just like traditional backup agents, the DPM agents can be used within the VMs for granular backups, or each VM can be treated as a “black box”, by running just the Virtual Server agent on the hosts and backing up entire VMs.

The final scenarios were all based around Windows Server Virtualization, including running Virtual Server VMs in a WSV environment. WSV is an extensive topic with a completely new architecture and I’ve wanted to write about it for a while but was prevented from doing so by an NDA. Now that James has taken the wraps off much of what I was keeping quiet about, I’ve written a separate post about WSV.

Finally, a couple of points worth noting:

  • When using WDS to capture an image for deployment to a VM, it’s still necessary to sysprep that machine.
  • Virtualisation is not a “silver bullet” – even though Windows Server Virtualisation on hardware that provides virtualisation assistance will run at near native speeds, Virtual Server 2005 is limited by factors of CPU speed, network and disk access and available memory that can compromise performance. In general, if a server is regularly running at ~60-75% CPU utilisation then it’s probably not a good virtualisation candidate but many servers are running at less than 15% of their potential capacity.

Microsoft’s virtualisation technology has come a long way and I expect Microsoft to make a serious dent in VMware’s x86 virtualisation market dominance over the next couple of years. Watch this space!

A light-hearted look at infrastructure optimisation

I’ve written before about Microsoft infrastructure optimisation (IO), including a link to the online self-assessment tool but I had to laugh when I saw James O’Neill’s post on the subject. I’m sure that James won’t mind me repeating his IO quiz here – basically the more answers from the right side of the table, the more basic the IT operations are and the more from the left side, the more dynamic they are. Not very scientific (far less so than the real analysis tools) and aimed at a lower level than a real IO study but amusing anyway:

The rest of my company… …involves the IT department in their projects. …accepts IT guys have a job to do. …tries to avoid anyone from IT.
My team… …all hold some kind of product certification. …read books on the subject. …struggle to stay informed.
What worries me most in the job is… …fire, flood or other natural disaster. …what an audit might uncover. …being found out.
My department reminds me of… …’Q branch’ from a James Bond movie. …Dilbert’s office. …trench warfare.
Frequent tasks here rely on… …automated processes. …a checklist. …Me.
What I like about this job is… …delivering the on the promise of technology. …it’s indoors and the hours are OK. …I can retire in 30 years.
If asked about Windows Vista I… …can give a run down of how its features would play here. …repeat what the guy in PC World told me. …change the subject.
New software generally is… …an opportunity. …a challenge. …something we ban.
My organization sees “software as a service” as a way to… …do more things. …do the same things, more cheaply. …do the same things without me.
Next year this job will be… …different. …the same. …outsourced.

Google Maps gets better and better

I used to use the AA and RAC websites to plan routes but these days Google Maps is faster and easier. And I just noticed that the Google Maps service has been improved with the ability to drag and drop the route line to customise the route.

Another feature (which may have been around for a while – it only seems to be available for US directions at the moment and I generally need to look at UK routes), is the ability to get directions using public transit. I’m planning my trip to the States next week (more on that in a couple of days) and it’s really useful.

iPhone: should I? shouldn’t I?

My mobile handset used to be just what I needed. It’s a phone, with a WAP browser. Basically, it works for making calls and reading my e-mail via OMA – and it fits the full handsfree kit in my car that my work phone uses (yes, I have two phones… one so I can be contacted by friends and family whenever I want and the other so that work colleagues can only call me when I’m working).

But I have been tempted. I’m a geek, and geeks feed on gadgets. And whilst common sense tells me that a Windows Mobile phone would best match my needs, I am seriously tempted by the Apple iPhone, which goes on sale in the UK next week. The trouble is that even hardened Apple fanboys on some of the podcasts that I listen to admit that this is just a first generation device – an iPhone beta if you like – and at £269 (on an 18-month contract at between £35 and £55 a month), it’s expensive – especially without the 3G and GPS that other handsets offer.

I did look at the Nokia N95 but Apple’s decision not to allow their phone to be subsidised by the networks means that other smartphone vendors are pushing up their prices too (thanks for nothing Apple) and Vodafone
wanted over £300 on an 18 month contract, plus an extra £7.50/month for 120MB of data.

My existing Vodafone contract is up in a few days time, so I called them and asked for my PAC code so that, if I do buy an iPhone next week, I can transfer my number to O2. Not surprisingly, Vodafone’s customer retention department wanted me to stick with them (that’s their job). After I rejected their revised offer (“ah, the £300 was retail, but we’re able to make you a better offer”) of an N95 for £170 (still £120 more than it would have cost me a few months ago…), they suggested that if I could source an iPhone from somewhere outside the UK it would work with any UK network (UK models will be locked to O2), and they could offer me another 12 month contract, with lower charges. That sounds good, but it’s a bit underhand of them to offer that solution as I don’t think it will work – this is why:

  • Even though I’m planning to be in the US next week (so picking up US iPhone would be reasonably easy) an unactivated iPhone can’t even perform non-phone related tasks like playing music and videos and activation would require a contract on a network in the country from which it is sourced (i.e. AT&T for a US-sourced phone).
  • Whilst I’m sure that hackers will find a way to unlock the iPhone (again), Apple is playing cat and mouse with them, so the next software upgrade (which I could ignore) would prevent me from using my Vodafone SIM in it (and possibly “brick” the device).
  • In any case, even if I never used the phone with the AT&T SIM once it was activated, I’d have problems opening an account without a US address and I’d be legally bound to a contract.

So, here’s the choice as I see it:

  1. Wait until next Friday and buy an iPhone on O2 with an 18 month contract: Cost £269 + (18 x £35) = £899 (with 200 minutes/200 texts/unlimited data each month).
  2. Buy an iPhone from an Apple store in the United States and use it over here (if it works): Cost £191.66 (at today’s exchange rate) + ((9 x £10) + (3 x £16) + (12 x £7.50)) = £419.66 with 75 minutes/stop the clock/120MB data each month.
  3. (Wait for the next iPhone model/buy something else/do nothing).

So option 2 looks best on paper, but what if it doesn’t work? Does anyone know if I’m right about options for using an unactivated iPhone in the UK?

Connecting to a Linux server using VNC

Many of my computers are not in my office/den but are providing server functions for which the need to access them directly is rare. When I do need access to the Windows machines, I can connect to them using a variety of RDP clients; for my Red Hat Enterprise Linux (RHEL) 5 box it’s a similar situation but this time using SSH (for command line access) or VNC (for a GUI).

Although RHEL includes a VNC server and I’d opened up TCP port 5900 in the firewall configuration (using system-config-securitylevel), for some reason I was still having problems creating a VNC connection and it turns out that there were two main reasons for this.

  1. Each VNC display will use a new port number, so display 0 is on 5900, display 1 on 5901, etc. I was trying to connect on port 5900 but it’s not as simple as opening the port – I needed to start a session with vncserver (supplying a password if required – the vncpasswd command can also be used for this), then note the port number (open the appropriate firewall ports) and connect from my chosen VNC client.
  2. For connection to an existing logged on console session on the server running a graphical environment (display 0), it’s necessary to enable this in the Remote Desktop preferences:

Remote Desktop PreferencesOnce I’d got around this, it was fairly straightforward to connect to display 1 on port 5901 but the default display was using the rather dated Tab Window Manager(TWM) GUI (although starting GNOME applications like gedit applied the GNOME look and feel to that application’s window. By editing the /root/.vnc/xstartup file I could comment out the twm & line and replace it with startx &; however, because there was already an instance of X running on the server (for display 0), I found that the startx & command failed and I needed to use gnome-session & in its place. I also commented out the line starting with xterm and included gnome-terminal & at the end of the script so my xstartup file now reads:

#!/bin/sh

# Uncomment the following two lines for normal desktop:
# unset SESSION_MANAGER
# exec /etc/X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
# xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
# twm &
gnome-session &
gnome-terminal &

Just for completeness, here are a few more notes that might be useful:

  • Use chkconfig --list to check whether the VNC server service is started by default (if necessary, use chkconfig --levels 5 vncserver to make it start in run level 5 in future).
  • If not already running, then start the service with service vncserver start.
  • Kill VNC desktops with vncserver -kill :displaynumber.
  • VNC sessions may be tunnelled through SSH for a secure connection.

Problems connecting to a Windows Server cluster

A few weeks back, I was at a Microsoft event where the presenter was struggling to connect to a Windows Server cluster using the Cluster Administrator tool. It turned out that the problem was down to having started devices in the wrong order (it should be storage, then network, then cluster nodes) but when one member of the audience suggested entering . as the cluster name in the Cluster Administrator dropdown he was able to connect to the cluster (with much relief!)… may be worth remembering for the future.