This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

rolling out the client via Zenworks

So we're trying to roll out the client software to our windows workstations from the workstation's Novell Server's setup.exe.  I have written a .bat file (and a .cmd file) but Zenworks doesn't seem to push the application as expected (the .bat file works if run manually.)  Anyone else have experience with rolling the client out via Zenworks?

:3133


This thread was automatically locked due to age.
Parents
  • Hi Karl,

    we had to use a forced run .EXE directly from the CID since Sophos doesn't provide/support the MSI installation method. The school CIDs were created with the following rights: SophosUpdateMgr (R;W;FileScan) and Public also has access.

    In our case the install commandline looks like this:

    \\ZENWSIMPORT\VOL1\Distribute\Antivirus\CIDs\S000\SAVSCFXP\setup.exe -ni -s

    By _not_ setting the 'Update path' in th command line it will fall back to the default which is the installtion source folder (useful!). More info for commandline: http://www.sophos.com/support/knowledgebase/article/12570.html

    We also had to implement a version number check (if existant Sophos isntall is less than 9.5.x then run the installer else don't do anything which prevents that this installer will run all the time).

    In our tests we had trouble to consistenly install the new Sophos since it will try to uninstall the old version first. This was due to sometimes the ALUpdate.exe (Sophos Autupdater) will run and both installers will clash eventually aborting/preventing Sophos to properly update. We tried to kill all services and terminate all sophos realted processes until eventually we found the official way to do it ( described here: http://www.sophos.com/support/knowledgebase/article/27646.html )

    Hope that helped a bit to get a kickstarted.

    :10989
Reply
  • Hi Karl,

    we had to use a forced run .EXE directly from the CID since Sophos doesn't provide/support the MSI installation method. The school CIDs were created with the following rights: SophosUpdateMgr (R;W;FileScan) and Public also has access.

    In our case the install commandline looks like this:

    \\ZENWSIMPORT\VOL1\Distribute\Antivirus\CIDs\S000\SAVSCFXP\setup.exe -ni -s

    By _not_ setting the 'Update path' in th command line it will fall back to the default which is the installtion source folder (useful!). More info for commandline: http://www.sophos.com/support/knowledgebase/article/12570.html

    We also had to implement a version number check (if existant Sophos isntall is less than 9.5.x then run the installer else don't do anything which prevents that this installer will run all the time).

    In our tests we had trouble to consistenly install the new Sophos since it will try to uninstall the old version first. This was due to sometimes the ALUpdate.exe (Sophos Autupdater) will run and both installers will clash eventually aborting/preventing Sophos to properly update. We tried to kill all services and terminate all sophos realted processes until eventually we found the official way to do it ( described here: http://www.sophos.com/support/knowledgebase/article/27646.html )

    Hope that helped a bit to get a kickstarted.

    :10989
Children
No Data