Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 4 replies
  • Subscribers 1 subscriber
  • Views 4740 views
  • Users 0 members are here
Options
Suggested
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

Group Policy deployment

pc

I'm looking to deploy ESDP via group policy. I read the article at http://www.sophos.com/support/knowledgebase/article/13090.html

It looks like that is an old article for an old version because the shares it has is the batch script don't exist in the current version. The share is has is \\<SERVER>\InterChk\ESXP\Setup.exe

I'm assuming the share should be something like:

\\<SERVER>\SophosUpdate\CIDs\S000\SAVCFXP\Setup.exe

Is this correct?

Is the method described in that article still the best practice for deploying with GP (besides a different share)?

Usually it is prefered to use a .msi for managed software deployment. What are the alternatives with using the .msi files?

If there is an article about GP deployment for the current version please post the link.

Thanks,

Patrick

:69


This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    just a quick remark :smileyhappy:...

    With Sophos Anti-Virus 9 /Enterise Console 4 you are also able to use the -G parameter when using setup.exe. This enables you to put the client into a Console group during the first rollout (if you really decide to use a script bases rollout mechanism).

    Usage of the -G parameter:

    setup.exe -G \Servername\Groupname

    Important is the \ in the begining as well as the servername. Another thing is that everything is cases sensetive - so if you want to put you client into a group "Internal" and you're using "-G \Servername\internal" it probably won't work.

    :84
Reply
  • 0

    Hi,

    just a quick remark :smileyhappy:...

    With Sophos Anti-Virus 9 /Enterise Console 4 you are also able to use the -G parameter when using setup.exe. This enables you to put the client into a Console group during the first rollout (if you really decide to use a script bases rollout mechanism).

    Usage of the -G parameter:

    setup.exe -G \Servername\Groupname

    Important is the \ in the begining as well as the servername. Another thing is that everything is cases sensetive - so if you want to put you client into a group "Internal" and you're using "-G \Servername\internal" it probably won't work.

    :84
Children
No Data
Unfiltered HTML