At the site
www.warmetal.nl there's a new article about the ZENworks Dynamic Local User policy:
If you log into a windows workstation using the Novell client you are only logged into eDirectory. Not into the workstation itself, which has it's own user database, called the Security Access Manager (SAM) Database. That's why you get a second login window, to login into windows. To prevent that from happening (the second login, that is) you could enable the Dynamic Local User policy. A Dynamic Local User (DLU) is a user object that is temporarily or permanently created in the workstation’s SAM database. The DLU is aZENworks feature and is covered in this article.
The DLU policy is used in case multiple users share a single workstation, with a terminal server or when the sysadmin is just lazy. For me, the most important feature is that after imaging a workstation, the workstation can be automatically imported into the tree, and with that done, when you log in it just works. So even when users have their own workstation there is no good reason to not have dynamic local user enabled. There is however a situation in which you don't want a DLU policy. That is the case you have an Active Directory domain and the workstations are joined into that domain. In this setup the domain takes care of the local account. You don't want to use the domain setup and the DLU policy at the same time. In my experience the DLU policy does not use the local domain account which means users get a different account than before. The configuration is rather straight forward and flexible enough to adjust to your own needs.
Read the complete article at
http://www.warmetal.nl/DynamicLocalUser
