Live Mesh reaches out to the Mac

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Graphic showing files moving between devicesOn the same day that I published my recent post about Windows Live FolderShare, I heard that the current Live Mesh beta is now available on a Mac.

Despite already being a Mesh user, I tried to add my Mac as a device but was disappointed to read that the Live Mesh Tech Preview was out of invitations so I tried again this evening and was pleased to find that it accepted me and let me install the software.

First impressions were good, with a really straightforward installation and good client support – working like a Mac application (not a Windows application running on OS X) and with support for both Safari and Firefox.

Then I realised that Mac-PC synchronisation in Mesh still needs to go via the Live Desktop (i.e. out to the ‘net and back), as evidenced when I tried to sync a folder that was not fully replicated:

The current version of Live Mesh cannot synchronize a folder with a Mac computer unless the folder is also synchronized with your Live Desktop.

This lack of LAN-based peer-to-peer support, combined with Mesh’s 5GB storage limit means that FolderShare is still the sync option for my work in progress (be prepared for a long wait if you’re syncing via the web and an ADSL connection – ADSL downloads are fine, but uploads are s…l…o…w…).

Predictably, some features are Windows-only too (like the remote desktop capability). There’s mobile device support too but it does depend on the phone – for example my Apple iPhone 3G was recognised as a Mac, after which Safari refused to install anything (I didn’t expect it to work but I just had to try!).

I don’t want to sound negative – Live Mesh is has so much potential and it is still a beta – over time new features will be added and it will be fantastic. Right now it’s still a little confusing – with the feature sets of Windows Live Skydrive, Mesh, FolderShare and Office Live Workspaces all overlapping slightly it’s sometimes difficult to fathom out the best tool to use – and those are just the Microsoft options! Hopefully this will all shake down over the coming months and the vision of my digital life being available wherever I am will become a reality.

More on the BT Home Hub

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Last year I blogged about the dangers of BT Home Hub users using WEP for “Wi-Fi Security”, pointing out that WEP is generally considered insecure and that WPA or WPA2 should be used instead. Then I set up my Dad’s Home Hub for him (just as an ADSL router/modem at this time… possibly with some of the other features later) and this is what I found:

  • The Home Hub is an elegant piece of hardware and BT have made cabling straightforward with colour-coded cables.
  • Following the instructions (which is what I did) involved installing a lot of software on the PC… just to connect to a router. I imagine that most of it can be disregarded (Customised browsers, BT Yahoo! sidebar etc.).
  • The setup failed to recognise that there was already an ADSL modem connection and that I was replacing that with a LAN-based connection (eventually I found a setting deep on the BT Broadband Help system to change that, after which uPnP jumped into life and the router was located).
  • The supplied password for BT Yahoo! Broadband didn’t work, resetting it required answering a security question that had never been set (chicken… egg…) and calling for support involved speaking to a well-intentioned but not very efficient call centre operative somewhere on the Indian subcontinent (who apologised for the quality of the phone line… ironic given that this service was on behalf of one of the World’s largest telecommunications providers)

Returning last week to finish the job, I found that BT have been updating the router firmware automatically for him and now he has options for WPA/WPA2 (which I duly configured). I also found a great link for information on the home hub (a rebadged Thomson device) – the The Frequencycast Home Hub FAQ – which told me useful things like to access the configuration via http://bthomehub.home/ and that the authentication prompt for administrator access does not requires the BT Broadband username and password but the username admin and password of admin (or the serial number of the device) until it is reset to something more memorable. If you need to know something about the BT Home Hub, the chances are it’s in this FAQ. Also worth a look (particularly if you have a Mac that’s not playing nicely with WPA-TKIP – although my OS X 10.5.5 MacBook seemed to be fine with Home Hub software 6.2.6.E) is the BT Home Hub page on hublog – and there is also a command line interface reference for the Home Hub.

Running VMware Server on top of Hyper-V… or not

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few days ago, I came across a couple of blog posts about how VMware Server won’t run on top of Hyper-V. Frankly, I’m amazed that any hosted virtualisation product (like VMware Server) will run on top of any hypervisor – I always understood that hosted virtualisation required so many hacks to work at all that if it saw something that wasn’t the real CPU (i.e. a hypervisor handling access to the processor’s hardware virtualisation support) then it might be expected to fall over in a heap – and it seems that VMware even coded VMware Server 2.0 to check for the existence of Hyper-V and fail gracefully. Quite what happens with VMware Server on top of ESX or XenServer, I don’t know – but I wouldn’t expect it to work any better.

Bizarrely, Virtual PC and Virtual Server will run on Hyper-V (I have even installed Hyper-V on top of Hyper-V whilst recording the installation process for a Microsoft TechNet video!) and, for the record, ESX will run in VMware Workstation too (i.e. hypervisor on top of hosted virtualisation). As for Hyper-V in VMware Workstation VM – I’ve not got around to trying it yet but Microsoft’s Matt McSpirit is not hopeful.

Regardless of the above, Steve Graegart did come up with a neat solution for those instances when you really must run a hosted virtualisation solution and Hyper-V on the same box. It involves dual-booting, which is a pain in the proverbial but, according to Steve, it works:

  1. Open a command prompt and create a new [boot loader] entry by copying the default one bcdedit /copy {default} /d "Boot without Hypervisor"
  2. After successful execution copy the GUID (ID of the new boot loader entry) including the curly braces to the clipboard.
  3. Set the HyperVisorLaunchType property to off bcdedit /set {guid} hypervisorlaunchtype off [using] the GUID you’ve previously copied to the clipboard.

After this, you should now have a boot time selection of whether or not to start Hyper-V (and hence whether or not an alternative virtualisation solution will run as expected).

Ready for an Xtremely Technical seminar on Windows Server 2008?

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I’ve always been impressed with John Craddock and Sally Storey’s presentations on Active Directory and related topics so, a couple of weeks back, I was pleased to catch up with them as they presented at the inaugural meeting of the Active Directory User Group.

In that session, John and Sally gave a quick overview of the new features in Windows Server 2008 Active Directory as well as the new read only domain controller (RODC) functionality and, if that whet your appetite (or if you missed it and think you’d like to know more), it may be of interest to know that John and Sally are running one of their XTSeminars later this month, looking at Windows Server 2008 infrastructure design, configuration and deployment. Topics include:

  • Building virtual environments with Hyper-V.
  • Creating high-availability with application and virtual machine clustering.
  • Windows imaging and the Windows Deployment Services (WDS).
  • What’s new in the Active Directory.
  • The benefits and caveats of Read Only Domain Controllers (RODC).
  • Windows networking with IPv6 and Network Access Protection (NAP).
  • Managing Server Core.

This is a chargeable event but I’ve never been disappointed by one John and Sally’s presentations, which are dedicated to delivering good technical content in a highly consumable format. For more information, and to book a place, visit the XTSeminars website.

(For a limited time only, using the code CC349, you can attend this two day event for just £349 For other seminars, try TN1384 for a 35% discount.)

Windows Live FolderShare – an example of Microsoft’s cloud computing platform that’s here to use today

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

I started off writing this post on the train, as the stacation (taking a break from work but staying at home) part of last week became the vacation part (a few days by the seaside with my wife and sons – the fact that I woke up to snow in Buckinghamshire didn’t seem to put the boys off wanting to build sandcastles in Dorset… even with their winter coats on).

The point of this is that I wanted to use the time on the train to good effect – and that meant catching up on my writing. Despite having spent a few days decommissioning my old file server in favour of a new NAS box, I still have a certain amount of local data that I need to access – spread across multiple Windows and Macintosh PCs. This is where Microsoft’s web services platform comes in. I’ve been using the Live Mesh CTP for a while now, but the current version of Mesh is just a starting point and there is another Live service in beta that I’m using here – Windows Live FolderShare.

FolderShare is a web service for distributed folders across multiple devices – either personal or shared folders. If you’ve used Windows Live SkyDrive as file storage in the cloud, then imagine if that data was hosted on your PCs (phones, and other devices) rather than in cyberspace – and replicated automatically.

Over time, I expect to see FolderShare move into Live Mesh and, in my coverage of the recent PDC keynote, I wrote about how:

Live Mesh bridges [islands of information] with a core synchronisation concept but Mesh is just the tip of the iceberg and is now a key component of Live Services to allow apps and websites to connect users, devices, applications and to provide data synchronisation.

My personal file data may not be the scale of enterprise service Microsoft plans for Windows Azure but Windows Live FolderShare does nicely demonstrate the concept in a way that most of us can appreciate. Here I am, creating content on the train using my Macintosh PC and I know that, when I hook up to a network, FolderShare will sync this (via Windows Live Services) to people/devices that I want to share the data with – for example my Windows PC in the home office. Then, whichever device I’m using, I can continue my work without worrying about where the master copy is. Add a phone into the mix and one would expect me to be able to access that data wherever I am as well as creating additional content – for example photos, or location specific data.

Jasdev Dhaliwal has an interesting article about Microsoft’s cloud computing announcements over at the Web Pitch. Jas’ post includes: Microsoft’s “Overnight Success” video which talks about the greater sum of software plus services “moving beyond devices and across borders to capture the imagination of the world… a world where the richness of software and the ubiquity of services are rapidly converging”; a BBC interview with Ray Ozzie where he talks about how it has become burdensome to manage the computer we’ve got at work, the computer we have in the den, childrens’ PCs, a cellphone with contacts, photos and information, cable boxes with recorded movies and how “Windows in the sky” can bring all of those devices together and make it easier to manage – more than just applications in the cloud but a total computing infrastructure; another BBC film where Rory Cellan-Jones visits one of Microsoft’s vast datacentres; and finally Microsoft’s “Synchronizing Life” video where a Mum takes a picture of a child at play using her mobile phone and that picture appears on a display many miles away in Dad’s office, on his PC, on his Mac, and how the Live Mesh extends to his media player, phone, into the car and to the childrens’ games console.

I started this post on the train, using a Mac. Now I’m ending it in the office, on a Windows PC – and I haven’t had to think about which copy of the data is current – it just works. That’s what connected synchronicity is about – it’s not about uploading everything I do to some website but about a mesh of devices working together to make my local data available globally… synchronising my life.

Coalface Tech: a podcast produced by IT pros for IT pros

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

Coalface Tech podcast graphicWay back in June, I wrote that James Bannan and I were thinking of launching a podcast – the theory being that we are both full-time IT guys who write about IT in our spare time, rather than professional journalists who write about IT but don’t need to worry about keeping the lights on.

Well, last month, we finally recorded the pilot episode for what has become known as “Coalface Tech”, and APC Mag has kindly given us a home on the web (multimedia downloads would blow my bandwidth allowance for this site very quickly!) – please do check it out and let us know what you think.

Please bear in mind that this is a pilot and we still have some work to do on the audio production (next time I will use a headset!) and the RSS feeds (for MP3 and AAC versions of the podcast) are not live yet so you can’t subscribe via iTunes (we’re working on it!). James and I are looking to schedule another recording soon but, in the meantime, check out the pilot episode – and please do leave a comment if you have any constructive feedback about podcast length, frequency, potential topics or anything else that seems relevant!

Issues experienced when uninstalling Virtual Server virtual machine additions after importing to Hyper-V

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few days ago, I was migrating a couple of legacy virtual machines from Virtual Server to Hyper-V. I used Matthijs ten Seldam’s VMC to Hyper-V Import Tool to save some time on the import process, although it is an import tool (not a migration tool), so I did need to move the .VHDs manually.

I realised that I’d forgotten to remove the Virtual Machine Additions before I shut the machines down in Virtual Server but I figured I would be able to do that in Hyper-V, before installing the Hyper-V integration components. Unfortunately, that didn’t work for me and attempting to uninstall the Virtual Machine Additions from the Control Panel Add or Remove Programs applet resulted in the following error message:

Virtual Machine Additions

{\Tahoma8}You can install Virtual Machine Additions only on a virtual machine that is running a supported guest operating system.

followed by:

Add or Remove Programs

Fatal error during installation.

A little bit of googling turned up a TechNet Social thread, where Tim Cerling explained that:

“You can only install the Virtual Machine additions from within Hyper-V if the virtual machine is running Windows XP SP3, Windows Vista SP1, Windows Server 2003 SP2 or Windows Server 2008 and the additions are version 13.803, 13.813, or 13.820. If the operating system is different or the additions are different, they can only be removed from Virtual Server or Virtual PC.”

Clicking on the support information in Control Panel’s Add or Remove Programs applet told me that my Virtual Machine Additions were still at 13.552.0.0, so I had to load the VHD under Virtual Server to remove them, before copying the .VHDs back to Hyper-V (I could use the same virtual machine configuration that I had created earlier but had to remove the disks and add them again in order to assign the appropriate permissions).

After starting the VMs, I cancelled the Found New Hardware Wizard and installed the Hyper-V integration services (including an automatic HAL update and a couple of reboots). Because I’d used legacy (emulated) network adapters and allocated static MAC addressing (carrying forward the MAC addresses from Virtual Server), the guest operating systems didn’t notice that the underlying NIC had changed and so it wasn’t necessary to reconfigure TCP/IP settings.

Bluetooth communications between Apple iPhone 3G and an Audi mobile telephone preparation system

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A few weeks back I had the use of a 2008 Ford Mondeo for a week and I wrote about my experiences of pairing my Apple iPhone 3G with the Ford Audio system. This morning, I got to play with a new Audi A4 Avant (2.0 TDI 170PS) for a few hours (it was fun – I will be ordering one soon) and I repeated the experiment with the iPhone 3G.

I didn’t have time to collect screenshots/photos but this is a quick summary of what I was told by the dealer/verified to be true (this car was an S line model and was fitted with the Audi Mobile Telephone Preparation Low and Audi Music Interface options):

  • The iPhone 3G will happily pair with the Audi’s audio system via the Mobile Telephone Preparation Low option but it is useful to know that: the pairing needs to occur within 30 seconds of opening the car and inserting the key (i.e. activating the car’s systems); the car identifies itself with a device name of handsfree; and the PIN for pairing is 1234.
  • Once paired, calls will ring the iPhone and the car simultaneously. The Bluetooth logo and signal strength are displayed on the Audi Multi Media Interface (MMI) display.
  • The car can access the iPhone 3G’s list for recently dialled numbers, missed calls, etc. but full directory integration does not appear to be available. Numbers can be dialled from the car’s systems (and the call placed on the iPhone). I did not have access to a vehicle with voice control system so this was not tested.
  • To use the iPhone as an iPod with the Audi Music Interface (AMI), a special cable is required (which I did not have access to).

Remote Desktop Services – more than just a terminal

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

In last week’s post looking some of the new features to expect in Windows Server 2008 R2 I didn’t mention terminal services at all. There’s a reason for that – Terminal Services is being replaced by what Microsoft is calling Remote Desktop Services (RDS) and all the Terminal Services applications will change names accordingly.

Why the change of name? Well, RDS is no longer limited to presentation virtualisation as it includes a new session broker capability to extend its role to support a virtual desktop infrastructure – further strengthening the ties between Microsoft’s virtualisation platform and the Windows Server operating system. By combining RDS with Windows Server 2008 Hyper-V or Microsoft Hyper-V Server, System Center Virtual Machine Manager, App-V within MDOP, and VECD licensing, Microsoft now provides an end-to-end VDI solution.

With Remote Desktop Services, centralised desktop environments can be created and managed, allowing remote connections from managed and unmanaged clients whilst keeping critical intellectual property secure and to radically simplifying regulatory compliance by removing applications and data from the desktop. Furthermore, unlike existing presentation virtualisation methods, RDS includes multiple application delivery methods.

Windows Server 2008 R2 provides the platform – with RemoteApp, Remote Desktop Web Access, Remote Desktop Gateway and the new Remote Desktop Connection Broker, which extends the session broker capabilities in Windows Server 2008 to create a unified administrative experience for session-based remote desktops and for virtual machine-based desktops, supporting bother persistent (permanent) and pooled virtual machines. As with VMware’s VDI offering, persistent VMs have a 1:1 mapping between users and the VM with any changes preserved, whereas the pooled VMs use a single, replicated, image with user state stores via profiles and folder redirection rather than in the VM. In either case, the images are stored on a Hyper-V host.

Meanwhile, the Remote Desktop Protocol (RDP) is also enhanced to offer more of the functionality that is typically associated with a local desktop, including: multimedia redirection; multiple monitor support; audio input and recording; Aero glass support; DirectX redirection; improved audio/video synchronisation; and language redirection.

RDS also includes improved application publishing and streaming through a Remote Desktop and Application feed with full Windows 7 support whereby RemoteApp programs and desktops appear on the Start Menu with a system tray icon indicating connectivity status, but also with connectivity options for Windows XP and Vista.

There are also improvements around management, with a new Windows PowerShell provider for RDS, as well as features to: help improve application compatibility (MSI compatibility); profile improvements; group policy caching; IP address virtualisation; and to ensure system stability by protecting against runaway applications (kernel scheduling).

As has always been the case with Terminal Services, Windows Server’s Remote Desktop Services capability is targeted at low-complexity deployments and as a platform for partner solutions, which can extend scalability and manageability to address the needs of more demanding enterprise deployments, for example with policy, load-balancing, orchestration and placement extensions for the connection broker. Regardless of this, RDS represents a signifcant step forward – and the inclusion of a connection broker for virtual desktops is a long overdue addition to Microsoft’s virtualisation portfolio.

Useful Links: October 2008

This content is 17 years old. I don't routinely update old blog posts as they are only intended to represent a view at a particular point in time. Please be warned that the information here may be out of date.

A list of items I’ve come across recently that I found potentially useful, interesting, or just plain funny: