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 deploy - computer startup script failing

I'm having problems getting the computer based startup script working in our environment.

I've followed the guide at https://www.sophos.com/en-us/support/knowledgebase/120611.aspx#AD

If i run the script manually (as an admin)  on a client PC, the black window appears and Cloud installs successfully. If I change the GPO to a user based "login script", the script runs successfully and Cloud installs. However this requires an admin to login for the script to run successfully.

So from what I can gather the script, share to the software and permissions seem to be setup correctly. Just the computer based startup script doesn't seem to be kicking into gear. I can't see any clues in event viewer either.

Has anyone succcessfully deployed Sophos Cloud using computer based startup scripts and have some pointers?

Admittedly I've never deployed software this way, usually its pushing out the MSI directly which unfortunately isn't an option with Cloud.

Appreciate your input.

:58226


This thread was automatically locked due to age.
Parents
  • Issue resolved.

    I added a simple echo line at the start of the script to output to a text file on the C drive. Following a gpupdate and restart the fact that the text file was generated on the PC confirmed that the policy was being applied, but the rest of the script was failing. This indicated that it was indeed a permissions problem.

    To get install working i tweaked the NTFS permissions on the installation directory to include the "everyone" group to have read/execute permissions.

    :58227
Reply
  • Issue resolved.

    I added a simple echo line at the start of the script to output to a text file on the C drive. Following a gpupdate and restart the fact that the text file was generated on the PC confirmed that the policy was being applied, but the rest of the script was failing. This indicated that it was indeed a permissions problem.

    To get install working i tweaked the NTFS permissions on the installation directory to include the "everyone" group to have read/execute permissions.

    :58227
Children
No Data