Additional Macro Virus Protection Delivered Using ZENworks for Desktops 3.0
Novell Cool Solutions: Feature
By Martin Buckley
Digg This -
Posted: 12 Feb 2001
Versions: ZENworks for Desktops 2 and 3
This article describes how to use ZENworks for Desktops policies to deliver a lockdown which turns off the Windows Scripting Host -- a common exploit used by many new viruses.
Another day, another virus...it certainly seems that way. I've noticed that the majority of new virus alerts coming my way are warning me about VB Script viruses that lurk in e-mails as seemingly innocuous attachments.
Here's a great way to deliver an update to desktops using a ZENworks for Desktops policy. This method works for ZENworks for Desktops 3.0, and should also be good for those waiting to upgrade who are still using the previous version (ZENworks for Desktops 2).
Having this update as a policy has several advantages:
- It's just a policy, so it will be persistent even after the user logs off.
- It's delivered pretty easily -- you just need the Novell client and ZENworks for Desktops.
- If you are using ZENworks for Desktops 3.0 you can take advantage of the inherited policies. You can place this high in your Novell Directory Services tree and associate it with many different areas of your business.
- As a final extra Evil Scientist bonus -- the ADM will also work with those other, less cool solutions like Microsoft ZAK -- but you aren't using that anyway are you?
So what's needed?
- ZENworks for Desktops 3.0
- scripting.adm -- the Administrative control file to create the extensible policy.
Copy the scripting.adm file into the bin\zen\admfiles directory for every one of your management consoles. You may be calling ConsoleOne from your servers -- look in SYS:public\mgmt\consoleone\1.2\bin\zen\admfiles
Start ConsoleOne and create a Policy Package. You can deliver the update as a user policy or a workstation policy -- here I'll show creating a user policy that can be delivered to every user in your organization.
Add the ADM file to the list -- browse and select from the correct container.
You may want to set the policy schedule to run on User Login.
Finally associate the new policy with the users, groups and containers and you are done.
That's all for this update -- in the next installment I will probably have information on the ports used by ZENworks for Desktops 3.0.
For more information about how you can help manage this virus within GroupWise, see this article.
About the Author
By night Martin Buckley is the Evil ZENworks Scientist -- cooking up ZENworks solutions and hatching dastardly integrations. By day he is the ZENworks for Desktops Product Manager. Based in Provo, UT and Nottingham, England - he's always on the road. Be warned.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com