нашел там вот что
_________________________________________
Updating Client remotely on Win NT workstations
Question: Zsuzsanna S. wrote: I read about ACU, which solves the remote client update. That's OK. But what about Windows NT workstations, where you are unable to modify file system with non-administrator user ID? (If you are a non-administrator user at a Windows NT workstation, the ACU doesn't work.) What should I do in this case?
Answer: Two solutions:
Associate the NT/NDS user to a Dynamic Local User Policy in the NT User Package of ZEN. This will create a new ADMIN account on the NT workstation and configure the ACU to run in the context of the Interactive user. An unattend.txt file is strongly suggested with a DLU. Important Note: Be careful with this one. DON'T configure the DLU to "Manage Existing Accounts" and set it to be a volatile user. This will delete the existing NT Account. Just create a new account with ADMIN rights and set it to be volatile so that it deletes the new ADMIN account upon reboot after the client install is completed.
Add an ACU action item in the NT Workstation Package of ZEN to run as System Impersonation or Unsecure System.
Note: If you run the ACU as System Impersonation then an unattend.txt file MUST be used because there will be no UI present during the client install thus no way to answer the install questions. The unattend.txt will pre-answer all the install questions and can be created using \i386\admin\nciman.exe.
___________________________________
только вот не пойму
Add an ACU action item in the NT Workstation Package of ZEN to run as System Impersonation or Unsecure System.
что это значит ?
надо зен или нет ?