I actually just rolled out the agent to all of our coputers Monday morning. While I didn't do any checking on the OS (I'm loading on all Windows OSes), I've added a statement to my code to check for 95/98/2000Pro. This should do the trick:

code:
--------------------------------------------------------------------------------

If @ProductType="Windows 95" or @ProductType="Windows 98" or @ProductType="Windows 2000 Professional"
$=ReadValue("HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent", "Installed Path")
If ReadValue("HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent", "Installed Path")="" or @error<>0
SHELL "C:\Lscript\Poaginst.exe /s C:\EPOagent"
EndIf
Endif

--------------------------------------------------------------------------------

I prefer to look at the registry to ensure that the program is properly installed and not have to be concerned with what folder it is installed in. This script checks to see if you're using one of the OSes that you want to check for. It then checks the registry to see if the agent is already installed. If not, it installs it from a library called C:\LSCRIPT to a library called C:\EPOAgent.

There is no reason to create a log file, since this information can all be accessed through the ePolicy Orchestrator console.

I've been using ePolicy Orchestrator on our servers for about 3 months. I would never go back to using scripts to update them. Now that I'm using it for desktops as well, I'll never go back to using scripts to roll out updates and upgrades. This program is so powerful I can't believe that everyone isn't using it.

[ 20 March 2002, 11:13: Message edited by: mmantei ]
_________________________
Mike