![]() Customers support was prompt and professional, and even after I fled the IT profession to preserve my sanity I kept SEP running on my own home computers. At the time, I found it to offer the best balance of effectiveness and efficiency. Something that needs to be updated continually like AV software is not a good candidate for inclusion in a sysprep image.Īnyway if I get any information on what's causing this problem I'll update people here.For quite a few years I had Symantec Endpoint Protection (SEP) deployed across servers and workstations in multiple offices. ![]() could I suggest that you don't install the SAV client on your image, but instead include it as part of the installation process to manually install from the SAV server? If you want to automate that you could do it with AD Group Policy, or something like LanDesk. In my case it's just a minor niggle (everything else works fine), but if you're creating a sysprep image then it's a show-stopper really. perhaps a faster PC shuts down quicker as well, and something in SAV doesn't like that? I recently upgraded to a savagely fast quad-core PC. I've never seen this particular problem before, even though I've been using SAV for almost 10 years. I'm now on on XP, mine is Corporate Edition on my home PC because I VPN into work. I've also gone back to recent previous editions (10.0.1, ) with the same effect. ![]() remove, reboot, reinstall, several times, all to no avail. so either there are only two of us, or else it doesn't bother other people. I found this forum via Google and yours was the one single hit.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |