Sign in
 
HomeLibraryLearnDownloadsSupportCommunityForums
Application Virtualization >
> 
> 
AppV 4.6: Windows Live Essentials breaks App-V Clients

Answered AppV 4.6: Windows Live Essentials breaks App-V Clients

  • Wednesday, January 26, 2011 8:46 PM
     
     
    Sign In to Vote
    0

    Here's what I did:

    • Fresh install of Windows 7 (tried both Home Pro and Enterprise, and both 32- and 64-bit with the same results), not joined to a domain
    • Add user credentails to Credential Manager
    • Install and set up App-V Client
    • Refresh server, bring down apps, run apps just fine.  All is good.
    • Install Windows Live Essentials 2011
    • Attempting to run an App-V application prompts endlessly for username and password.  Canceling returns error code 4604EE8-1C504B01-0003100E
    • Attempting to refresh the server results in error code 4604EE8-1690900A-00002002

    Any ideas?


     

All Replies

  • Wednesday, January 26, 2011 10:50 PM
    Moderator
     
     
    Sign In to Vote
    0

    I have WLE installed along side the App-V client without issues, but I'm not using Credential Manager for authn. This article indicates that Windows Live Mesh might cause authentication issues: https://connect.microsoft.com/onecare/feedback/details/610295/app-v-and-windows-live-mesh-are-not-compatible

    Also see this blog post: http://blogs.technet.com/b/appv/archive/2010/03/24/network-devices-that-use-rtsp-inspection-may-cause-problems-in-specific-app-v-scenarios.aspx

     

    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
     
  • Wednesday, January 26, 2011 10:59 PM
     
     
    Sign In to Vote
    0

    I have WLE installed along side the App-V client without issues, but I'm not using Credential Manager for authn. This article indicates that Windows Live Mesh might cause authentication issues: https://connect.microsoft.com/onecare/feedback/details/610295/app-v-and-windows-live-mesh-are-not-compatible

    Also see this blog post: http://blogs.technet.com/b/appv/archive/2010/03/24/network-devices-that-use-rtsp-inspection-may-cause-problems-in-specific-app-v-scenarios.aspx

     

    This forum post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.


    I tried just installing Messenger through the Windows Live install, and it does the same thing as the first link describes.  I have a suspicion that the Sign-in Assistant is the actual culprit, since that appears to be what's common between all of the options.

    The second link I've seen, but it doesn't appear relevant as it only happens when Windows Live is installed.

     
  • Thursday, January 27, 2011 3:53 PM
     
     
    Sign In to Vote
    0
    After playing around a bit, I've discovered that "domain\user" works, but "user@domain" doesn't.  I'd really like to get UPN login working again.
     
  • Thursday, January 27, 2011 6:28 PM
     
     Answered
    Sign In to Vote
    1

    For anybody else who finds this -- I've discovered a workaround.  I don't, however, know what effect this would have on the Live tools (but everything seems to be working).

    • Open up Regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    • Remove "livessp" (leave the others) from "Security Packages"
    • Reboot

    It's a bit silly we have to do this.  And I'm guessing it will have to be done every time there's an update to the Sign-in Assistant.

     
  • Friday, January 28, 2011 3:22 PM
     
     
    Sign In to Vote
    0

    Would it be possible just to add the application to the exclusion list of the anti-virus if it is that which is causing the issue?

     

    I've had a similar issue with others app but not with APP-V Client to be honest. APP-V Sequencer has conflicted with other services for me in the past which was a bit of a pain.

     
  • Monday, January 30, 2012 8:52 AM
     
     
    Sign In to Vote
    0
    @ PatrickWSteele, how do I remove the "livessp" using GPO? I've tried to export the reg and use it with bat file via GPO but didn't get it going. Any hints please?

    thanks
     
  • Friday, July 20, 2012 10:36 AM
     
     
    Sign In to Vote
    0

    Hi

    As you say this is a bug and has been confirmed, and there maybe a fix out for it App-V client 4.6 SP2, as per link:

    http://techtonis.wordpress.com/2012/07/20/app-v-client-authentication-problem-when-you-install-live-essentials-or-office-365-client-components-on-the-same-windows-client/

    Thanks.

     
  • Wednesday, February 27, 2013 10:16 AM
     
     
    Sign In to Vote
    0
    Hi, Have just started a trial of Lync and have problem described above whereby AppV applications prompt for credentials after Live Sign On Assistant is installed.  Tested again after install of AppV 4.6 SP2 Client, problem not resolved.  Has anyone found a solution?
     
  • Wednesday, February 27, 2013 10:19 AM
     
     
    Sign In to Vote
    0

    Hello,

    Have you tested the above suggestions? (such as posted by albm23 and PatrickWSteele)

    Nicke Källén | The Knack| Twitter: @Znackattack

     
  • Wednesday, February 27, 2013 10:36 AM
     
     
    Sign In to Vote
    0

    Hi, As above AppV Client 4.6 SP2 does'nt resolve, virtual apps open but only after entering domain user name and password.  Checked the registry keys under HKLM\System\CurrentControlSet\Lsa\Security Packages, livessp isn't listed, options are kerberos, msv1_0, schannel,wdigest, tspkg, pkuu2u, msoidssp.  Lync 2010 seems to add msoidssp to the list, deleting this key and rebooting resolves but am assuming that this is only temporary as above as a software update will amend the key.  Denise

     
  • Wednesday, February 27, 2013 12:33 PM
     
     
    Sign In to Vote
    0

    Hello,

    Try to remove the part that you suspect breaks it and verify that it truely is it. Also verify if there is any other functionality breaking, if removing that key.

    Nicke Källén | The Knack| Twitter: @Znackattack

     
  • Wednesday, February 27, 2013 3:45 PM
     
     
    Sign In to Vote
    0

    As of now, the removal of the Live SSP package remains the workaround and this will probably stand. Also note, doing that removal via autoruns is another safe option.

    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

     
  • Monday, March 25, 2013 4:13 PM
     
     
    Sign In to Vote
    0
    I am having this same issue after rolling out the Microsoft Online Sign-in Assistant.  The only workaround I have been able to find is to remove the msoidssp entry from HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa - "Security Packages".  I am hesitant to use this solution as I'm afraid it will cause issues with MSO SIA down the road.  Has anyone been able to resolve this another way?
    • Edited by CJ78 Monday, March 25, 2013 7:06 PM
    •