Lync Server installation error: prerequisite installation failed encountered on Windows Server 2008 R2 SP1

March 15th, 2011 | Tags: ,

I have come across various posts within the TechNet forums for Lync Server 2010 installations that have failed where Windows Server 2008 R2 Service Pack 1 is applied. Whilst SP1 is supported the following error is experienced:

Executing external command: C:\Windows\system32\dism.exe /online /norestart /add-package
/packagepath:C:\Windows\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum /ignorecheck
MM/DD/YYYY HH:MM:SS AM
Installation result: -2146762496   MM/DD/YYYY HH:MM:SS AM
Error: Prerequisite installation failed: Wmf2008R2

Some have enabled “Desktop Experience” as a workaround, this is not recommended and the suggested workaround is to apply the Windows Media Format Runtime prior to running the Lync Server installer. This manual step can be achieved via the following command:

%systemroot%\system32\dism.exe /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum /ignorecheck

Please note:a reboot is required prior to re-commencing the Lync Server installation process.

Source: here

  1. soder
    March 15th, 2011 at 18:39
    Reply | Quote | #1

    Hi,

    do you have any sensible reason why the Desktop experience pack should not be installed on the Lync server. I am simply unable to remember that creepy Wmf installation commandline (I hardly believe any human can :), it is always easier to type: servermanagercmd -i desktop-experience, and voila!

  2. Adam [I’m a UC Blog]
    March 16th, 2011 at 11:12
    Reply | Quote | #2

    Hi Soder,

    But all you need in to remember my blog, right? 🙂 Seriously though point taken…

    “Desktop Experience” essentially enables the Windows client UI, which as you can imagine takes a performance hit on the server. Cut a long story short, you don’t want it – try to use the command line above and preferabley remove this from existing installations – not sure on the impact here?

    – Adam