Dameware !!LINK!!
George Bignell
Than it sounds like the traffic that is involved with the authentication process is being blocked. I'm not sure of your setup but typically the pc will try to authenticate to the local DC and if it can't contact it will try to look for the secondary DC and so on down the line. It sounds like the DC traffic is being blocked and eventually dameware allows the connection, perhaps using something like cached credentials.
I can use dameware NT utilities to access all the tools for the respective computer but a soon as I try to use MiniRemote and try to login I get the error. I can use other remote desktop apps and windows RDP w/ smart card authentication w/o errors.
Sometime when connecting to high resolution clients, my dameware mrc does not let me move the window on my screen. I am connected to two clients right now for example. One is at 1024x768. The dameware "window" has a menu bar (File, Send, Monitor...) and buttons, and the display of this remote machine is integrated within this window. I can minimize, maximize, close or drag this window around no problem.
The other machine I am connected to is 1920x1080. The view of this remote machine is separated from the dameware toolbar in the top middle of my screen. The window border around the view of the remote machine is so thin that there is nothing to grab ahold of to move this window around my screens. I can only really awkwardly resize it to move it to another monitor or another place on my screen. How could I get the view of this remote machine attached with the menu bar and tool bar, like the other machine? There's no way to disconnect either. Well one would have to close it from the taskbar. If you click the little X in the top anchored, centered toolbar that is detached from the remote PC view, that toolbar goes away permanently . unless you close dameware and reopen it.
For instance we would like to be able to call '\\server\dameware.exe' (server of course has a valid installed dameware license) from any of our 23 school sites for when we can't be in two places at once. Currently when we try this we get a 'license expired' message.
We are having this exact same issue as well. All the exclusions are added above as you have in your setup, but sporadically we are still seeing dameware files removed from endpoints. We had a ticket opened and closed but I think its about time to open one up again.
So, when we were seeing the issue of dameware being removed we had whitelisted all of the above folders and .exe that you all have gone over above. I thought it was possible that it was removing the dameware product before it was gathering the policy, like on a new install of checkpoint client on an endpoint. Meaning it would scan and remove before gathering our default policy. Checkpoint said it was how the product behaved where it would take up to five minutes to gather policy so we closed the ticket. However now we are seeing like 5 or 6 computers a day where dameware is still getting removed, yet their policies should be current. Not really sure where to go from here. Another ticket I suppose
Currently I have gone back over and made the changes recommended from sk131312 exactly, and removed any other additions we had added for dameware. Going to watch for updates and probably open another ticket.
f5d0e4f075