Users unable to login to terminal server with Webroot installed.
We are deploying Webroot to our clients and have been running into an issue with users unable to login at a certain point. After testing we found it has to do with Webroot being installed on there but we cant figure out what is causing the issue and we've had to remove Webroot. This seems to only be affecting Server 2008 R2 environments.
Already have an account? Login
Login to the community
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Just because you have version 18.104.22.168 installed does not mean that the issue for you is different. A part of the resolution process was to ensure that Webroot was completely removed before applying the update.
Before installing the latest agent build please ensure that you have removed the agent currently installed and ensure that C:Program DataWRData has been removed (if not please delete this folder) Please ensure that you reboot the server after applying the latest update.
To bring back activity to the server, the TermService service can be restarted to allow connections again.
Please reach out to our Support Team so they can run through the necessary checks and escalate your case if necessary.
Support Number: 1-866-612-4227 M-F 7am?6pm MT
Send us a Support Ticket
I was wondering if you have looked through my previous posts on this topic? I too am an MSP and experienced this exact same issue. My resolution to the problem has been detailed several times in this post. If you cannot find it then let me know and I will post it again.
Next step - replace Webroot with another solution.
However if this is your first post on this, can you please advise if you have tried the fixes that have posted all through this thread? It would be helpful to know what you have attempted to do to resolve this so as we, the community, can be of more help to you.
At one of my customersites RDP-server are Server 2012 and NOT Server 2012 R2.
The 4 advised patches are for Windows 8.1 and Server 2012 R2 only. Installing them on my customers Server 2012 servers is not supported.
Does this mean that Webroot on Server 2012 (not R2) does not have 4005 errors or RDS connection Issues. Their present AV-software is at his end and i would like to rollout Webroot.
Hope you can conform that installing webroot without issues is possible.
Please contact them at your convenience for further assistance.
Merry Christmas! ?
No, as soon as you start to describe the issue you're experiencing they'll know what you're talking about. Thanks!
I understand from your previous posts that the process should not be explained externally so I appoligize if this seems vague.
Yes, it should be stable so long as the steps are followed correctly. If you do somehow experience issues, please let the Support Team know in your ticket.
Even great support is a pain - we're frequently busy with other things when support gets back to you. Sometimes in the car, other times busy with another crisis...
If they'd publish updates in the Knowledge Base, we'd at least have something to work with.
I am frankly appalled that a major security softwareprovider could let this issue go on for years without a reliable fix.
So, I have started a support case and will wait until it's convenient for them to get back to me. WR's response time has been good, no complaints there. However, this issue is dragging on and it's inexcusable. Shouldn't have to deal with this...
Thanks for your feedback. We are working on being more transparent and sharing more information, and we actually have just launched a knowledge base area for known issues here. Here is the KB on for the 4005 issue. Please take a look when you have a chance!
I have confirmed that my RDS-Server policy contained these settings (listed in the KB article), and that it was applied to the server in question.
I used this poilicy previously on another RDS server (same OS) and it successfully resolved the issue. On this server, however, the problem still occurs, about once a week or so...
Support has requested some diagnostic information, and I guess I need to gather that for them.
Is there a KB article that will help with issues on these servers?
The solution shown there worked for me on one 2008r2 server, but not on a second one.