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

running tasks (ie VBScript) prior to 'Protect Computers' rollout

Hiya,

I've tried to search the board for this, but not found anything.

Is there a way to run tasks before having the Sophos installed? For instance, I need to disable Simple File Sharing on machines before roll out, and since the site is remote (400 miles away) i can't run past every client.

I have a VBS that would do this for me, but I am not sure where this is to be configured.

If it is just a matter of prepping the environment even before kicking off Protect Computers, that'b be fine too, but I like to bundle tasks and automate as much as i can (also for new PC's that come on board)

Thanks!

:32119


This thread was automatically locked due to age.
  • Hello IK,

    maybe this recent post by Jak gives you some ideas. Beware though, such tinkering is unsupported!

    Christian

    :32137
  • thanks for the update QC .. such a shame that Sophos doesn't even have a section to support the Admin on this..

    ah well .. i'll keep looking, as i am not keen to replace any original files, nor undertake actions that aren't supported ...

    :32155
  • What is you did the installation via the script as well?

    Then you can do all your prerequisites followed by the installation.

    The only thing is that you would need an alternative method to deploy it.

    PSEXEC could work, or I also like an application called Remote Installer by a company called Compulsion Software

    Not sure what kind of access you have at your remote site though.

    :32163
  • Hello IK,

    some things are not easy in Windows. File and Printer sharing is an adapter specific setting - there's no simple way to change this after install time - didn't read your first post carefully enough, should have mentioned it.

    Christian

    :32169
  • Wow you can't toggle File and Printer sharing from a script?

    That is a bit of a pain.

    I have never tried so I didn't know that. Devastating.

    :32173
  • Hi QC, your first post hit the nail on the head, unfortunately i will not go that route .. I guess it comes down to manual prep prior to roll out Sophos .. but i am sure the developers would be able to add an extra tab for Protect Computers to allow us Admins to include scripts for pre- and post- rollout  :robotwink:

    TODDH : Thanks for the suggestion, and yes, i could all script it, but i would like to keep it to the console, that would make mine and my successor's work easier (think support guides etc) .. for whoever will need to support this in the future. Currently we have full access to support the site, but who knows in a few years the support model will change.

    PS. the Simple File Sharing can be scripted via VBScript .. 

    :32249
  • Hello IK,

    could you post an example how it can be done? Might help others.

    Christian

    :32529
  • Hi Christian,


    Assuming you're talking about scripting the disable of SFS:

    strComputer = "."
    
    Set StdOut = WScript.StdOut
    Set oReg = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\default:StdRegProv")
    
    strKeyPath = "SYSTEM\CurrentControlSet\control\lsa"
    
    strValueName = "forceguest"
    
    dwValue = 0
    
    oReg.SetDWORDValue HKEY_LOCAL_MACHINE,strKeyPath,strValueName,dwValue
    
    MsgBox "SFS Turned off"
    
    Set StdOut = Nothing
    Set oReg = Nothing
    :32551
  • Hello IK,

    right you are. The weekend helped me to read things right (and not to get carried away by my imagination). Of course dealing with Simple Filesharing should be rather easy. Past experience made me mix this up with a related problematic setting viz (Enable) File and Printer sharing. Let's say I've seen install where is was installed but not enabled. Sorry for not reading your post correctly twice. Ugh - don't want to find out what else I've messed up last week ... :smileyvery-happy:

    Christian

    :32659
  • Does this relate to clients no longer being able to print to network printers? eventho they're allowed in the FW?

    :32733