Microsoft has decided to disable the SMB1 protocol in Windows Server 2019 by default to force the use of newer SMB versions. However, Windows XP does not support these new versions, and only works with SMB1. This makes communication between these two operating systems impossible via File and Printer Sharing, which is a UserLock prerequisite for communication between service and agents.
Therefore, if UserLock is installed on Windows Server 2019 and Desktop UserLock agents are installed on Windows XP workstations, UserLock will not be able to protect these workstations.
For UserLock to work correctly in this scenario, you can enable the SMB1 protocol on Windows Server 2019 as follows:
- Open Server Manager
- Manage -> Add Roles and Features
- Advance to the "Features" section
- Check “SMB 1.0/CIFS File Sharing Support”:
- Continue until "Install" can be selected, then click on it
- Restart the server
Other related questions
- What Operating Systems are supported by UserLock
- What is the hardware requirement?
- What is the disk space consumed by the UserLock database?
- What is the bandwidth consumed by UserLock?
- Do I need to install UserLock on a Domain Controller?
- Do I need to install UserLock on a dedicated server?
- Can I install the UserLock console on another machine than the server?
- What are the protocols used for UserLock server/agent communication?
- What results (credentials, files, folders, registry...) from the installation of UserLock and its agents on a domain?
- What are the requirements for the UserLock Backup server?
- Configure client requirements through group policies
- How do I install UserLock across multiple sites?
- How to run a UserLock server installed on Windows Server 2019 with Desktop UserLock agents installed on Windows XP workstations
- Can the UserLock SSO feature be installed as a separate service?
- Is Userlock affected by the CVE-2021-44228 CVE-2022-22963 CVE-2022-22965 Log4Shell Vulnerability?
- Why do I have to upgrade a beta version?
Can't find your response?
If you are not able to solve your problem despite the information available here, then do not hesitate to open a ticket with our technical support department.
