All points well taken... It really depends on your network and your level of control and admin workload vs laziness (Cheap & Dirty). On my LAN, I control what account is used for non-owned PCs so easier to add to grp NO_NAV. That one line is not the end-all. There are other checks as well. But then, we are creeping off topic.If you have a standardized WKS naming convention, a spin on Jeroen's concept could work with less effort. Instead of managing a computer list manually, just search for a common substring within the WKS name.
If you want to do an elegant quasi-SMS software deployment instead of C&D, you could setup an INI file to hold all WKS related config and manipulate that INI file. Sealeopard has an excellent example of that in his post:
HOW-TO: Running scripts with ADMIN powers
Amantica,
I sense you're still at the baby-steps phase of deployment. It may be time well spent to study Sealeopard's implementation for consideration in your setting before building a legacy of haphazard scripts as I have.
