Some of the services' drivers do have altitude values that match Microsoft's values and I don't see that I could modify them. Only thing I can think of is the OS does not recognize the App Layer services as running. I've compared services with a working VM.
However, once the layer is on a vdisk and assigned to a 2016 server VM the SEP client will not run and throws the message that some of the Symantec services are not running. On building the App layer I can get SEP to update and go to green status by disabling the Intrusion Protection service then reactivating it prior to the finalization for shutdown. Then, restart the Packaging Machine as often as necessary until the post-installation restart request no longer appears in the App Layering management console. Each time you upgrade the application, Symantec adds another GUID.Ħ> Restart the Packaging Machine or the gold image. Go to [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\ccSettings_. Gathered it from several sources don't recall them.ĥ> Using regedit, change the Group and Tag values for each ccSettings GUID.Ī. 1101 from an app layer this is what I have for notes. not sure we had to but it was a concern that OS layer activity, virus def updates, can effect the layer being edited. We had to clean each layer of the older def folders to keep the images clean. folders in the C:\programdata\Symantec\Symantec Endpoint Protection path along with the 14.2. We noticed this when we upgraded our SEP from 12.X to 14.2 last month then ran an update to all our images and noticed all of our updated images still had 12.1. We have also noticed that putting the virus software on the OS layer can cause issues when the newer def files download while we are editing another layer.
Has anyone been able make this SEP version work on an app layer? I have seen other forums that mention the filter minidrivrs or the SEP version may play a part. We can't seem to get Symantec SEP version 14.2 RU1 MP1 (.1101) to update the def files, or recognize the SEP service is running from an app layer so we have it on the OS layer.now.
0 kommentar(er)
