Symptoms

In some scenarios it may be necessary to enable OOF in K2 for a user which has been disabled in AD DS and K2. For example if your process linked to some position/title in AD and you not going to change this routing matrix even when employee leaves a company. In such scenario you may want to do temporary redirect of missing user tasks via K2 OOF until new employee will be hired/appointed to have the same position reflected in AD DS.
 

Diagnoses

In case user has been disabled in AD and K2 there is no way to enable his OOF via K2 GUI (note that if OOF was enabled before user was disabled than you can manage disabled user OOF settings in K2 Workspace). As a workaround you can try to enable OOF for disabled user by making direct edits in K2 DB (by adding entries into oServer].]Actioner] and dServer].]ActionerShare] tables) - but you have to take K2 database backup and fully understand that this is not supported scenario.
Other option will be temporarily enable user in AD DS, then enable his K2 OOF and disable this user again. This will allow you to change user's OOF settings despite the fact that this user is disabled.

There is an existing feature request to add an ability to manage OOF (Out of Office) for users disabled in AD, with no ETA for implementation at this point.
 

Resolution

Currently the only fully supported way of doing that is to temporarily enable user in AD DS, and then enable his K2 OOF and disable this user again. This will allow you to change user's OOF settings despite the fact that this user is disabled. For alternatives/workaround see Diagnosis section above.