Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >

KB-6432: Does cloud connector work when C drive is full?

Centrify Identity Service, App Edition ,  

29 June,16 at 01:08 AM

Applies to: All versions of Centrify IdentityService


By default the AD cached data is stored under 
C:\Users\<user>\AppData\Roaming\​, <user> is the service account running the Cloud Connector on the local host. 
If the service account is the local system itself, then cached data will be stored under C:\Windows\System32\config\systemprofile\AppData\Roaming\.
The location of storing AD cached data can not be changed. Then does Cloud Connector work when C drive is full? 


Basically if C drive is full then Cloud Connector logging will not work, so running a Cloud Connector without available disk space is never recommended.

When C drive is full, Cloud Connector no longer writes information to log file. While Windows will free up a few MB after the disc is full then Cloud Connector starts logging again, once the space is filled again AD users would not be able to login and Cloud Connector will show as "Cloud connector is unavailable", then "Creating communication channel for cloud...", then it shows Successful apparently after some disc space is freed again by Windows or the Cloud Connector itself.

In conclusion once C drive is full, cloud connector can no longer function consistently.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.