MCP 4.1.0 client - major issue with RDP

[jround]

We deployed MCP 4.1.0 this morning and since deployment RDP does not work any more (you can RDP, enter credentials but then the RDP session immediately closes)

Rolling back to MCP 4.0.0 resolves the issue

[THoffard]

Hey jround!  What did you do to rollback?  I only have the option of the new 4.1 product?

Thanks!

[jround]

We just checked in the MCP 4.0.0 package back in to a different branch (available under Software Manager somewhere) then created a new client task to uninstall MCP 4.1.0 and a client task assignment with Immediate schedule set up to target any machines with a temporary MCP410uninstall tag (I literally just created that tag and manually applied it to all machines that reported a MCP 4.1.0 install)

Then another client task / client task assignment with install MCP 4.0.0 defined at the root of our structure (not Immediate) excluded from applying machines with the MCP410uninstall tag, once I noticed machines no longer showing a MCP 4.1.0 install I just manually removed that MCP410uninstall tag from then and they eventually picked up the MCP 4.0.0 task assignment and reinstalled that

Probably much more elegant solutions to achieve all that but it worked for us and no issues reported with RDP at all since the rollback so definetely related to 4.1.0, after spending the day thinking a Windows Update had caused the issues with it having been Patch Tuesday this week too!

[THoffard]

Thanks jround!  You must have on-prem, we have MVISION ePO and the option to client task 4.0 back is not there.  Very manual per machine, so lots of fun on a Friday!  Take care.

[Jucken]

Same Problem here. 
Winlogon.exe Fails with error 4005

Additional if you try to logoff on an local machine, winlogon.exe crashes with the same error and you can only resolve it with hard reset the system.

We need a fix here, or the possibility to rollback from MVISION ePO.

[jround]

We also had 'interactive sign in process initialisation has failed’ errors for some users until they performed a hard restart (we would have been in real trouble had that restart *not* resolved that for our work from home laptop users as they wouldn't then be able to login and connect to our VPN for the uninstall task to be sent to their device!), so interesting to know that seems to have been related to MCP 4.1.0 too

[Jucken]

I got a workaround from McAfee support until the hotfix is released.

Disable the access protection in the MCP Client Configuration policy.
Works like a charm, winlogon.exe doesn't crash anymore.

[jround]

Thanks, looks like they've released a hotfix release now too (4.1.1) so I'll give that a try on a few machines

[THoffard]

Let me know jround!  I have not heard or seen anything for MVISION yet, but curious on how that reacts once installed.  Good Luck!

[THoffard]

Thanks Jucken!  We actually did some testing with McAfee on this actual "fix" short term while a long term hot fix is still being developed for MVISION ePO.  We had to uninstall ePO, then manually install 4.0 and ensure the setting was unchecked for access protection. Good Luck!