dhallam

We are also having the same issues with only a few Updates this month, and we also have Sophos. But the above fix in Sophos is not working for us and even with those disabled for an entire room for testing its still getting the error. Strangely if i log onto the computers as the SCCM_Push account and Roll the update in Software Centre i get the error, but if i login as a domain admin and manually run the update in Software Centre it downloads and installs fine. Im going to do some more testing Today and see if i can narrow it down. But for us the office updates are working fine 😖

We have just had the same reports from our New Mac Studio M1 Rooms. They have only just reported it but been happing for months supposedly. Have reached out to XtremeMac to see what can be done as we don't have the funds to replace all 40 keyboards and mice. Will see what they come back with. ours are the same model as above Keyboards are XWH-WIK-83-UK Mice are XWH-WM0-83 We only went with this brand as it was the one recommended by our 2 of our suppliers. Typical

We have been trying to resolved this all week, and you fix works spot on. Thanks so much we were starting to give up all hope. You never know microsoft might actuall put this fix into GPO polices :-)

We only had that issue for the admin users because the group that we were in had Disable Workstation ticked in the group settings which had not been working but now is as it disabled us access.

Currentaly running 5.3.25 and all working fine apart from the computer power off policy seems to not to be working now. Its not turning computers off after 15 mins, but if you edit the policy and change somthing within the power off policy the room then powers off we are trying to test at the mo.

Yes the remote login of a classroom is still working. We never had any issues with that feature. cheers

Hi again we have resolved our unable to connect issue as after further investigation once the new client had been installed (5.3.25) staff accountswere working fine and had no connection issues, it was just our admins that could not connect. I then created a staff account to an admin so I could get access to the groups to check and noticed that our Domain Admins group had the disable workstation ticked (which has always been ticked but was probably not working) This has now been unticked and is now working again for admins and staff connecting. Shame the error didnt say you are not allowed to connect as the client is disabled message :-) 5.3.25 is looking good WOL working again and the AD connect is working again.

We now have version 5.3.25 and cannot get even the admins to connect now. The server is running 2012r2 so does not have that update, but we do have some updates from the 14th so im uninstalling one at a time to see if this sorts the connection issue. We have noticed DLL errors within the logs and the error below all the time: CCSS4: ImperoClientSVC53252016-05-25 16:20:17System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.20.20.74:30016 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at ImperoClientSVC.clsTCPServerClient.Connect(String pIPorName, Int32 pPort) CCSS4: ImperoClientSVC53252016-05-25 16:20:21System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.20.20.74:30016 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at ImperoClientSVC.clsTCPServerClient.Connect(String pIPorName, Int32 pPort)

We have managed to get hold of support and hopefuly a download link to the fix is comming?? Hopefuly we are getting all the the above issues (cannot connect to server, and AD groups not working, and WOL only working 30%)

Also we have noticed a few other issues in testing today: 1 User Groups not taking effect with the GET_AD_GROUPS_FAILED error 2 Wake on lan only waking 50% of computers and was working fine before the update. 3 Impero Server is unreachable on most computers?? some work some don't.. all direct to server IP with serverIP.txt (admins fine) All after upgrade to 5.3.21

I also have an issue with Version 5.3.21 We have an issue with out user groups within the new version 5.3.21. We have a All Staff and All Students user groups but this seems only to be working for some users. I have noticed that the users that it is working for if you check their properties the active directory groups show a correct list and contains the result GET_AD_GROUPS_OK but the users that are not showing within the user group it just shows GET_AD_GROUPS_FAILED within the properties. I have restarted workstations and server and still have the same issues, have logged a support case just thought i would see if anyone else having this issue. Cheers David Hallam