Just looking to confirm my understanding of the situation and how
ZENworks/Windows behaves...

Two DLU policies are in effect. Each policy is assigned to a specific
container holding user objects. Both policies are configured to "manage
existing user accounts", "use edir credentials" and "volatile" - the
only difference is that one policy creates local Windows profiles as
"Users" while the other creates "Administrators".

On the workstation side, public workstations are configured with
volatile user caching *disabled* to prevent retention of profiles and
associated data. All other workstations are configured with caching
*enabled* and with a time period of 366 days. This is done via Windows
registry, not the agent policy in the workstation package.

The issue of volatility is under review for the admin users so i'm
looking into the feasibility of reconfiguring the DLU policy for these
users from volatile to non-volatile. I understand that in earlier
versions of ZENworks this could not be done in a direct fashion but had
been addressed in later versions of the Novell Client (ZENworks 3) and
ZENworks Agent (ZENworks 4) (TID 10088027).

So, provided admin users are authenticating to eDir, if the DLU policy
is reconfigured from "volatile" to "non-volatile" any newly created
Windows profiles should essentially be permanent. The workstation config
(re: 366 day time period) should not apply to these "non-volatile"
profiles, meaning they should *not* expire/be purged after 366 days
(from the agent config, the wording implies that caching apply
explicitly to *volatile* users...).

Question: After the DLU policy is reconfigured, will existing/cached
Windows profiles initially created as volatile by DLU be updated to
non-volatile? Will there be any risk to existing/cached profiles
resulting from the change in volatility?

I will of course run through this in my test environment...