locked
APP-V and User Profile Disks RRS feed

  • Question

  • Hi,
    We have been implementing RDS Collection using User Profile Disks but have been having some issues
    and that is every 4-6 log off the User Profile Disks are note getting detached that results in users getting a Temporary Profile when they log in to a new server in the Collection.
    First off we thought this has something to do with Microsoft Office in APP-V , scheduled tasks or something like that being executing.

    We have been narrowing to issue down and removed office and all packages related with to the user but that did not help.
    Then we uninstalled the APP-V client and after that disks get detached.
    Installed the APP-V Client and the same behavior occurred !

    I think the APP-V Client is accessing the C:\Users\%UserName% location and that is locking the disk.

    I have been doing some research on google but not hitting anything that might explain this or point to a solution.
    Can someone please point me in the right direction to solve this ?


    best regards, Valdi Hafdal

    Wednesday, February 3, 2016 8:11 PM

Answers

  • This may be similar to an issue we are currently working on related to the issue addressed for 5.0 Sp3 that is also affecting 5.1. The only way to confirm would be further diagnostics and debugging which often require an MS support case.

    Sometimes they do take time but that is usually how code changes and hotfixes come about for released products.


    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, February 15, 2016 3:42 PM

All replies

  • Which version of AppV5 are you using?
    Are there still processes running like AppVStreamingUX.exe?
    Hotfix2 for SP3 solves an issue where a handle was held to the users profile during logoff, so the profile could not be deleted.

    Wednesday, February 3, 2016 11:35 PM
  • Hi,
    we are currently running APP-V 5.1 but have not yet installed
    hotfix 1 : https://support.microsoft.com/en-us/kb/3115834

    but i assume that it will not help at least not with the issues that seem to be addressed in that Hot Fix, we intend to try that tomorrow just to rule it out.

    I will need to check if AppVStreamingUX is running, we just restarted all the servers in the farm so there are no locked disks at the moment for me to debug so I will have to wait a couple of hours to check.


    best regards, Valdi Hafdal

    Thursday, February 4, 2016 12:33 AM
  • Hi,
    I have looked over 5 users that now have a locked disk and there is no AppVStreamingUX.exe running under username where the issue is occurring !

    best regards, Valdi Hafdal

    Thursday, February 4, 2016 1:31 PM
  • I am currently working with the original poster on this problem. The "log" from our test you can see below. 

    -- App-V 5.1 Client with Microsoft Office 2013 package published globally. <- The original/current setup -- 

    About 4th or 5th logon results in locked disk. 
    -- Removed the package and all scheduel tasks related to Office -> rebooted -- 
    S
    ame problem. Around 4th or 5th logoff resulted in locked disk. 

    -- Published the Microsoft Office 2016 App-V Package Globally -> Reboot -- 
    Logon/logoff 3x = OK (Opened up Microsoft Outlook with a profile and then straight to logoff)
    Locked disk 
    Logon/Logoff 5x = OK (Outlook opened and logoff). 
    Locked Disk

    -- Office 2016 Scheduel Task -> Telemetry Data Disabled/Deleted. -> Reboot -- 
    Locked Disk. 
    Logon/Logoff 2x = OK (Outlook opened and logoff)
    Locked Disk.
    Logon/Logoff 1x = OK (Outlook opened and logoff)
    Locked Disk.
    Locked Disk.
    Logon/Logoff 3x = OK (Outlook opened and logoff)
    Locked Disk.

    -- Remove All APP-V Package from Server, Remove Test User from all APP-V Package Groups in Active Directory.  
    Logon/Logoff 3x. Nothing opened. 
    Locked Disk. 
    Logon/Logoff 6x. Nothing opened.  
    Locked Disk.
    Locked Disk.  

    -- Remove APP-V Client 5.1 software from Server. Reboot. 

    Logon/Logoff 15x. <- Nothing opened, no locked disk what so ever (probably more than 15 logon/logoff)

    -- APP-V Client installed again -> Reboot. Test user in no App-V Package Groups.
    Logon/Logoff 8x. Nothing opened. 
    Locked Disk.
    Logon/Logoff 5x. Nothing opened.  
    Locked Disk.

    APP-V Folder in AppData/Local Deleted. 
    Logon/Logoff 3x. Nothing opened.
    Locked Disk.

    As you can see above we did quite many changes and tests and it seems to come down to the APP-V Client Software it self being installed on the server. 

    Thursday, February 4, 2016 1:42 PM
  • Hi,
    Any ideas what can be causing this issue or how to bypass it ?
    or will I need to raise a support call MS that will take for ages and then need another age for a fix :(

    best regards, Valdi Hafdal


    Tuesday, February 9, 2016 11:54 AM
  • This may be similar to an issue we are currently working on related to the issue addressed for 5.0 Sp3 that is also affecting 5.1. The only way to confirm would be further diagnostics and debugging which often require an MS support case.

    Sometimes they do take time but that is usually how code changes and hotfixes come about for released products.


    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, February 15, 2016 3:42 PM
  • This may be similar to an issue we are currently working on related to the issue addressed for 5.0 Sp3 that is also affecting 5.1. The only way to confirm would be further diagnostics and debugging which often require an MS support case.

    Sometimes they do take time but that is usually how code changes and hotfixes come about for released products.


    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.”

    Since a case was raised with Microsoft last year without a clear fix (still ongoing withing Microsoft departments according to lates information) this is currently the best answer.  
    Friday, January 20, 2017 10:13 AM