Windows Home Server 2011 Launchpad Breaks New Mac OSX 10.7 Lion Launchpad

We’ve started receiving early bug reports from WGS readers who have attempted to update their Windows Home Server 2011-connected Apple Macs to OSX 10.7 Lion, and are now experiencing issues.

From what we can gather, the Windows Home Server 2011 Launchpad, when installed on the Mac before the Lion upgrade, suppresses the new Mac Launchpad application – most likely as they have the same name. End result, you will not be able to use (or even see) the Mac Launchpad – click the icon, and your Windows Home Server 2011 Launchpad will run instead.

The issue, as first reported by KHU on the WGS Forums, is as follows:

After an in-place upgrade of 10.6 to 10.7 the OSX Launchpad does not work and does not exist if the Microsoft Windows Home Server 2011 add-in for Mac was installed previously.

When starting Mac Launchpad from the apps folder or dock shortcut the Microsoft version of the Launchpad app is started instead. The Apple version of Launchpad is nowhere to be found.

Steps to Reproduce:

Install Microsoft Windows Home Server 2011 Connector for Mac in OSX 10.6. This installs an application called Launchpad from Microsoft. Now if 10.6 is updated to Lion the WHS 20111 Launchpad application is still present, instead of OSX 10.7 Launchpad. Evenif the MS Launchpad was removed from the dock previously, it is put back again and not replaced with the new OSX Launchpad.

Expected Results:

Either the Microsoft Launchpad should be replaced or (preferably) the Lion Launchpad should co-exist with Microsoft’sLaunchpad and be present instead or in addition in the OSX dock.

Actual Results:

Microsoft Launchpad is put (again) into the dock, OSX Launchpad is nowhere to be found. The dock and app icon look like the Microsoft version and if started it really is Microsoft’s Launchpad which was installed as part of the Windows Home Server Connector before the Lion 10.7 upgrade.

Thankfully, a quick workaround has been discovered by Peter ter Haar to replace the Windows Home Server 2011 Mac Launchpad with the OSX 10.7 Lion Launchpad (if you wish):

  • Remove the Microsoft Launchpad (with AppCleaner). Load the Lion disk (dmg file) and under Packages,  install the Essentials package. This will reload the Mac OSX Launchpad.

We’ll make sure that Microsoft are aware of this issue today and will let you know any plans to resolve.

Total
4
Shares

22 comments

  1. OK, this explains the opposite side of the error that I've been experiencing over the last couple of weeks trying to install MS Launchpad on a clean install of Lion (the developer preview and now the release version). I always got the error message that it was already installed, and I guess this is why!

    So has anyone come up with a workaround to install MS Launchpad on Lion?

    1. I'm experiencing the same problem as above, previosly had MS Launchpad for Home Server installed and now Apple Lion Launchpad not appearing although it put MS Home Server Launchpad in the Dock during the Lion install.

    1. You'll read about where to find the Lion dmg file in http://osxdaily.com/2011/06/08/create-burn-bootab
      I understand the package is removed from disk after installation of the OS, so you'll have to re-download from the AppStore. Before the OS installer is started, follow the steps in the link above.
      I had access to the gold master dmg to solve my problem.

  2. OSX launchpad icon is missing on my Lion machine but I can trigger it using the swipe actions on trackpad and then it works fine. The MS launchpad still seems to function (was installed prior to upgrade).

    So they can both co-exist.

  3. Rather than have to chose between one or the other I just left the windows Server launchpad where it was and set the apple launchpad to be invoked from a hot corner in OSX.

    When you configure the hot corner the Launchpad that appears as a choice in the drop down is the apple one.

  4. The problem I've got is when you do a clean install of Lion – Mac Launchpad is there; it's an intrinsic part of the OS so it can't be moved, renamed or deleted, and therefore MS Launchpad won't install.

    This seems like one of those problems where's there's a really simple but ingenious solution, but right now I've not got a clue what it is!

    1. Solved it myself in the end (posted the how-to in the original thread). Though I have to say I'm not really sure what advantage having the WHS Launchpad connector actually brings to the Mac – it just seems to be an unnecessary extra click for things you can click-to directly.

      1. No one has mentioned Dashboard name clash? Can't Microsoft and Apple talk? I would simply like to have a name change, such as WHS_LaunchPad and WHS_DashBoard for Mac connector.

        On my new Mac, I can't install connector software, it says I already have it.

        I see that the WHS 2011 price has fallen significantly at the online stores since I purchased it from Amazon less than a month ago for $115. I wonder?

        1. Well, this problem on July 21st mysteriously went away on July 22nd??? On a brand new MacBook Pro with Lion purchased on July 22nd, I started it up, did the setups, then I did all of the Lion updates for the day on July 22nd. After this I did the hpHomeServer/connect. It installed Launchpad perfectly and as an option, it even starts up automatically when I start up the laptop.

  5. After I went through the steps above to restore the Lion Launchpad, I re-named it to Mac LaunchPad.app then reinstalled the Windows Launchpad all seems fine.

  6. Alternatively do what I did. WIth the WHS launchpad already installed, the Lion launchpad can't be installed because of the name clash, so as I happen to have another hard drive attached to my Mac, I ran the Essentials.pkg as mentioned in the article but changed the destination to my other drive. The installer created a few folders on it including an Applications folder containing the Lion launchpad. I renamed this to OSX Launchpad, copied it to my main Applications folder on my OS drive and all worked fine. Just needed to cleanup the unwanted folders on my second drive. No need to mess around uninstalling the WHS launchpad first and this would probably even work if you had a 4 Gbyte USB stick to use as a temporary second Mac volume.

  7. ohh nice – but one problem – if LION still runs you can´t download lion again from appstore :-/ or i don´t find it.

    maybe someone can upload the LaunchPad.app (as archive) or the essentials.pkg?
    Would be very nice 🙂

  8. Yes you can re-download LION if you are running it, like;
    Launch the App Store
    While holding down the OPTION key, click on the “Purchases” section
    You should see “OS X Lion” and “Install” should now be gray and you can click that to re-download Lion (you may have to re-authenticate within the App Store with your Apple ID).

  9. How do you rename LaunchPad.app to Mac LaunchPad.app? When we use Get Info, the area to rename it is grayed out!

    1. Guys,

      Just fixed the problem of installing the mac connector. Use the steps below and the connector will install without problems (All steps are performed within OSX LION);

      – open the [applications] folder in [Finder];

      – right click [Launchpad] and select [Get Info];

      – open [Sharing & Permissions] and set the permission for [Everyone] to [Read & Write];

      – open [Terminal] and goto the [Applications] folder;

      cd /Applications

      then make a rename using th mv command;

      mv Launchpad.app "MacLaunchpad.app"
      – now it's ok to set back the permissions to the default;

      – Launch the MacConnector.dmg again and the WHS Launchpad will install.

      Regards,

      Pedro de Goeij

    2. Guys,

      Just fixed the problem of installing the mac connector. Use the steps below and the connector will install without problems (All steps are performed within OSX LION);

      – open the [applications] folder in [Finder];

      – right click [Launchpad] and select [Get Info];

      – open [Sharing & Permissions] and set the permission for [Everyone] to [Read & Write];

      – open [Terminal] and goto the [Applications] folder;

      cd /Applications
      then make a rename using th mv command;

      mv Launchpad.app "MacLaunchpad.app"
      – now it's ok to set back the permissions to the default;

      – Launch the MacConnector.dmg again and the WHS Launchpad will install.

      Regards,

      Pedro de Goeij

      1. I know this is old…but I was calling MS things they haven’t been called since ME…and I never thought of this possibility. I only installed WHS yesterday 12/23/2011 and have been trying to get the Mac Launchpad since then. Thank-you and Merry Christmas!

  10. it does not work for me. If I change the name of the Launchpad app, the Launchpad for WHS 2011will not install. The installation process quits without any failure message…

  11. It sucks that we can't use Time Machine backups yet. Check out the new Orbital Add-in that is supposed to allow Time Machine backups on WHS. As of now it only works with Snow Leopard, since Lion has the Launchpad nameclash.
    http://forum.wegotserved.com/index.php/topic/1909

    I renamed the Apple "Launchpad" to "Mac Launchpad" and let the Microsoft Launchpad install normally then as suggested. For some reason things are still funky though if you see the screen shots and problems people are having in the link I posted above.

    I hope a fix from Microsoft comes out in the near future. (frustrating)

Leave a Reply