Follow

Existing User Profiles Are Being Automatically Deleted

Product: ProfileUnity-FlexApp

Product Version: 6.5.10

Expires on: 365 days from publish date

Updated: May 15, 2017

 

Problem: 

Existing User Profiles Are Being Automatically Deleted on Persistent systems

 

Effect

Windows 7, 10, 2016

 

Description

User Profiles are being deleted or removed from machines, despite having no ProfileUnity configuration deployed or Profile Cleanup is not engaged.

 

Resolution

This is a known issue and currently affects Windows 7, 10, 2016 Desktops (RDSH) on reboot even when profile cleanup is not engaged.  Desktops that refresh at logoff are not affected.

 To resolve, you must do one of the following options:

 

  1. Uninstall and reinstall the client with the Profile Cleanup service set to not deploy. To do this uninstall the client and edit the file called LwL.ProfileUnity.Client.Startup.exe.config.  Change

     <setting name="InstallProfileCleanupService" serializeAs="String">

   <value>Start</value>

 

to

 

      <setting name="InstallProfileCleanupService" serializeAs="String">

         <value>DontDeploy</value>

OR

 On non-persistent

  1. Uninstall and reinstall with the new (attached) ProfileService.exe 
  2. Log into parent image
  3. From a administrator command prompt, run the following command or edit the GPO and replace computer startup script with this line:

    \\server\netlogon\profileunity\LwL.ProfileUnity.Client.Startup.exe /uninstall 

To address this please refer to the attached file  profsvc.renameme

 

  1. Download  the file profsvc.renameme locally
  2. Rename the file to profsvc.zip
  3. Copy this .zip to Netlogon or share where client tools reside and overwrite existing profsvc.zip
  4. Re-Run LwL.ProfileUnity.Client.Startup.exe on the parent image and or recompose the pool to verify new files make it down to the desktop.

See https://liquidwarelabs.zendesk.com/hc/en-us/articles/210630623-Installation-of-ProfileUnity-onto-a-Base-Image-gold-image- 

On Persistent or Physical

To address this please refer to the attached file  profsvc.renameme

 

  1. Download  the file profsvc.renameme locally
  2. Rename the file to profsvc.zip
  3. Copy this .zip to Netlogon or share where client tools reside and overwrite existing profsvc.zip
  4. Edit the LwL.ProfileUnity.Client.Startup.exe.config
  5. change the version to force a new client tools install
  6. <setting name="ClientVersion" serializeAs="String">
    <value>6.5.6292-4cb7c3e</value>
  7. to...
  8. <setting name="ClientVersion" serializeAs="String">
    <value>6.6.6292-4cb7c3e</value>
  9.  AND
  10. <setting name="ClientDotNetVersion" serializeAs="String">
            <value>6.5.6292-4cb7c3e</value>
  11. to...
  12. <setting name="ClientDotNetVersion" serializeAs="String">
            <value>6.6.6292-4cb7c3e</value>
  13. Re-Run LwL.ProfileUnity.Client.Startup.exe manually (see step 10)  or reboot so LwL.ProfileUnity.Client.Startup.exe runs
  14. See https://liquidwarelabs.zendesk.com/hc/en-us/articles/210630623-Installation-of-ProfileUnity-onto-a-Base-Image-gold-image- 

OR

 

  1. In session, Stop the profile clean up service and replace ProfileService.exe with the attached version.

 

OR

 

  1. Remove the Profile Clean up service from within ProU
    1. App launch rule
      1. Net stop “Liquidware Labs Profile Service”
      2. sc delete “Liquidware Labs Profile Service”
    2. Or import attached json which includes associate app launcher rules

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.