Note Starting with Windows 8 and Windows Server 2012, the Plug-and-Play Manager no longer creates device representations for non-PnP (legacy) devices. So we'll need to find an alternate way to change those settings. Thanks for the insight, unfortunately after Windows 8, MS removed the "Non Plug and Play Drivers" from device manager. So I don't know the equivalent service names for 14.0.
Unfortunately, we only have this documented for 12.1.6. We don't really know what's going on, but when we've seen this before, we have (with Symantec's blessing) told people to set the service types from 0 (System) to 1 (Automatic), and it starts OK. In App and Platform layers, our filter is running and handling changes. You're just editing the base disk itself. The difference is that, in an OS layer, we don't run our filter drivers at all. There is simply something different about the App layer from an OS layer the SEP client doesn't like but I can't figure it out. What is different about a new/clean App Layer/Platform layer vs a new OS layer version that would prevent Symantec services from running properly? I have been fighting this problem for many days now and there are no helpful logs or events.
Using a new version of my platform layer or a brand new platform layer w/ no other changes yields the same results as above.
If I install the client in a new version of my OS layer, it works properly as expected even after a reboot.
Before the reboot, the Symantec Client works properly as expected, but after the reboot services fail to start and I can't find any indication as to why. If I install the SEP client in an App layer or a Platform layer, the Symantec services fail to start properly after the first reboot of the packaging vm. Hello, I'm attempting to get Symantec Endpoint Protection Client 14.0.1 installed as an App Layer (on Windows 10) and am running in to some difficulty.
0 kommentar(er)
