Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 10 subscribers
  • Views 2147 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

Failed to install sld: general error.

Rodjene Constantino

We have encounter this error repeatedly to our events log in central, can anyone know what must be done here?



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

    If SLD is failing to install, is there an install log under \windows\temp\ for it?

  • 0 in reply to Sophos User930

    Hi ,

    Yes you can see an install logs on the said path. if it's now showing there you can check on appdata by typing on run %temp%.

    In addition to this, Below is the known issue for SLD.

    • Lockdown was not tested for Terminal Servers. For further information on support for Remote Desktop (Terminal) Services see, Sophos Central Windows Server Protection – Remote Desktop (Terminal) Services.
    • Lockdown is not supported on gold images. Each image would need to be locked following deployment. For further information on using gold images see, Sophos Central Endpoint: How to install on a gold image to avoid duplicate identities.
    • Lockdown fails to install on a server with SAP Business One installed. SAP Business One and Sophos Server Lockdown both use the same registry key for Services:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SLD

      Attempts to install Server Lockdown will fail and Sophos Central will report a permanent 'Installing software' status. Server Lockdown is not supported on servers running SAP Business One.

    • When locking down a server, the state of the server includes the Volume Name assigned to the Hard Disks. Any change to the Volume Name will result in the blocking of applications on the Volume as the state of the server now differs to when it was locked. In such instances, the server must be unlocked and then locked to update the Volume Name change.
    Glenn ArchieSeñas (GlennSen)
    Global Community Support Engineer | Global Community and Digital Customer Support
    Connect, Engage, Earn Rewards - Join the Sophos Community
Reply
  • 0 in reply to Sophos User930

    Hi ,

    Yes you can see an install logs on the said path. if it's now showing there you can check on appdata by typing on run %temp%.

    In addition to this, Below is the known issue for SLD.

    • Lockdown was not tested for Terminal Servers. For further information on support for Remote Desktop (Terminal) Services see, Sophos Central Windows Server Protection – Remote Desktop (Terminal) Services.
    • Lockdown is not supported on gold images. Each image would need to be locked following deployment. For further information on using gold images see, Sophos Central Endpoint: How to install on a gold image to avoid duplicate identities.
    • Lockdown fails to install on a server with SAP Business One installed. SAP Business One and Sophos Server Lockdown both use the same registry key for Services:

      HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SLD

      Attempts to install Server Lockdown will fail and Sophos Central will report a permanent 'Installing software' status. Server Lockdown is not supported on servers running SAP Business One.

    • When locking down a server, the state of the server includes the Volume Name assigned to the Hard Disks. Any change to the Volume Name will result in the blocking of applications on the Volume as the state of the server now differs to when it was locked. In such instances, the server must be unlocked and then locked to update the Volume Name change.
    Glenn ArchieSeñas (GlennSen)
    Global Community Support Engineer | Global Community and Digital Customer Support
    Connect, Engage, Earn Rewards - Join the Sophos Community
Children
No Data
Unfiltered HTML