Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 3182 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

Protect Computer Wizard (Push) to WinXP from Sophos SEC console does not work!

GCCCDEDU_Admin

I have read a number of Sophos support articles and I am stumped.  I am attempting to use the "Protect computers wizard" to protect some Windows XP clients, but it does not work. 

The unmanged comptuers show in the console, the wizard runs, valid administrator credentials are supplied but absolutly nothing happens.

As best I can tell from the client side the following services must be running:

  1. Task Scheduler
  2. Remote Registry Service

Everything looks good from the client side, but it's as if the server never even tries to connect.  The clients remain grayed out (unmanged in the console)

How I debug what is wrong?

:14297


This thread was automatically locked due to age.
  • 0

    HI,

    I'll assume you are in a domain.  The test I would do is as follows:

    1. Log onto to the SEC server as the same account you are entering in the protect wizard.  E.g. Domain\Administrator.

    Maybe ensure that from the client, if you look in the local Administrators group on the client, the client can resolve the Domain administrators group just to ensure that the account has administrative rights over the client.

    A quick test from the SEC machine:

    \\<XPmachine>\C$

    does this work?

    2. Taking the computer name as is appears in SEC.  From the SEC server type:
    \\<XPmachine>\
    You should see the scheduled tasks "folder".  If you go into that, can you manaually create a task on the XP machine as SEC essentially creates a scheduled task to run the setup.exe from the central installation directory.

    Regards,

    Jak

     

    :14305
  • 0

    jak,

    Thanks.  Yes the credentials are not an issue.  On the client computer, the "Domain Users" group is a member of the local adminstrators group, therefore virutally any domain account has the authority to perform the push.  However, to be clear we are using a domain admin account to do the push.  We have tried numerous accounts, all result in a failure with no feedback to determine what the cause is.  I poked around in some Sophos logs, but it is unknown to me which the correct log file to examine is for the client push.

    The default volume shares are healthy on the clients.

    :14309
  • 0

    Did creating a test schedule task work?

    If so, then monitor the scheduled tasks directory does one get created by the management service on the XP machine? 

    Jak

    :14319
  • 0

    Jak,

    The server never connects.  We're auditing the Windows security event log to watch for new logons.  This is not happening.  The server is not connecting for some reason.

    I'm on the phone with tech support tring to work out whats wrong. 

    I did obtain a list of services that must be running on the client side:

    • Computer Browser
    • Remote Registry
    • Server
    • Task Scheduelr
    • WorkStation
    • Windows Installer
    • c$ must be available
    :14323
  • 0

    Could the Windows XP firewall be blocking file and printer sharing?

    When you say the server is not connecting, is that when performing the test from the server of:

    \\<XPClient>\
    Does this show anything?

    Can you open up regedit on the server and connect to the remote client's registry?

    Jak 

    :14325