I had a user who was reporting all sorts of weird issues: could not see the network, could not browse folders, etc. Several reboots later, issues remained. On a subsequent reboot, no user could login to EE. Out comes SafeTech and I perform an emergency boot. Miraculous things happen: All Windows-side weirdness goes away and of course user can log back into to EE. The world is a happy place.
The question is why? I am assuming the EE client was hobbled in some way and that was causing network communication issues, cleared up by the emergency boot. But my explaination to the higher-ups is expected to be much more technical than that. Having already sat on the phone waiting 10 minutes for a McAfee tech to answer, I decided to try my luck here.
Any insight is appreciated.
I am happy to provide the log, but I don't need troubleshooting at this point (and the user is currently offline). I am just hoping to better understand the relationship between EE and Windows. Does it hook the network stack? All of the user's issues could be attributed to lack of network connectivity.
It does not replace anything in Windows network environment. It is just an application, that tends to communicate over the network. It puts very light and sporadic load also. I doubt to see any correlation there. More likely it was Windows reboot or some other timing.
"I had a user reporting..." is the first thing to investigate unless you experienced the problem yourself. Our users report all kinds of stuff that should not be happening and we can't re-create when we get our hands on their machine. If the EE client was somehow degraded, I'm not sure you would be able to login at all, and since it's a PBA, it should not ever affect any O/S network settings or functionality.
We use WinTech and it has only ever solved EEPC issues and allowed access to the O/S if we needed to replace corrupt Windows boot file or something. SafeTech has a different function and I'm not familiar with it.
Too bad there is no flag or process within Emergency Boot to force a reboot, run again, bypass pba, and perform the SBFS rebuild.