Return
-
Title
CCU is configured and deployed correctly, but won't start on time -
Description
CCU was configured and deployed correctly. Not prompting for credentials when time comes. User is in vmover.ini and can access CCU share without any issues.
Additionally, there's no cachecredsvc.log file in c:\programdata\Quest Software\CacheCred. Even Quest Software folder doesn't exist under the C:\ProgramData
-
Cause
Issue is caused by incorrect JUNCTION pointer of Application Data under the c:\ProgramData folder. Sometimes after deployment from the golden image, junction points are leading to non-existing drive like D or E. -
Resolution
There are several workaround for this issue:
1. Simple method
Rename c:\ProgramData\Application Data shortcut to anything else and restart the CacheCredSvc service2. More complicated
- Deploy CCU to the test machine
- Go to c:\Program Files (x86)\Quest Software\CacheCred folder
- Open cachecred.ini file and replace all paths with %ALLUSERSPROFILE%\Application Data\Quest Software\... to %ALLUSERSPROFILE%\Quest Software\... Basically, remove "Application Data" from all paths in the file
- Copy cachecred.ini to some share
Now, when CCU setup.msi need to be deployed:
- deploy setup.msi to the machine
- stop CacheCredSvs service
- copy good cachedred.ini file from the share to machine's c:\Program Files (x86)\Quest Software\CacheCred
- start CacheCredSvs service back
-
Additional Information
Issue is environmental https://social.technet.microsoft.com/Forums/en-US/0145ab0d-8f4b-4460-ba40-97d46f3f81d9/why-do-all-junction-points-point-to-dltsomepathgt-and-not-cltsomepathgt-after