During login with Client for Open Enterprise Server 2 SP4 (IR12) on Windows 10 64bit (1703-1809) sometimes it cannot find the Tree or Server. Especially if you are quick to login, like as soon as you possible can during a startup. And sometimes if you do the really fast login, no network drives are mapped. But, if you wait a min or so, windows gets things started and it works.
Is there a way to stall the login until Windows is more ready?
We have the Local GPO set to wait for all networks services before attempting logon enabled.
We are also getting some startups without the OES client, even though it is installed, and then a restart is needed to solve that. Mostly, it's a very strange behaviour.
Anyone else seen this or have any good tips for help?
Nykvarn Municipal, Sweden