Yeah, its super inconsistent though. It's very very odd. We do plan on having another package created (our vendor has to create this - ugh). But the goal is to make sure the new package has zero reboots, zero user interaction etc.
From: [email protected] [mailto:[email protected]] On Behalf Of Spengler, Jeff Sent: Wednesday, October 30, 2013 3:29 PM To: '[email protected]' Subject: [mssms] RE: Symantec Endpoint Protection and OSD Task Sequence (CM12 / MDT) Do you get the same results if you use the MSI version vs. wrapped setup.exe of SEP? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Dzikowski, Michael Sent: Wednesday, October 30, 2013 1:14 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] Symantec Endpoint Protection and OSD Task Sequence (CM12 / MDT) Anyone else running into issues deploying SEP during OSD? We're seeing SEP cause some issues during our TS. Basically SEP is super inconsistent in the way it behaves after it installs. Sometimes the machine will reboot, sometimes the TS will error out, etc. But the application is installing... We have a package created from SEP and we've configured our SCCM application with the following command line: setup.exe /s /v"/qn /l*v c:\support\MSILOGS\SEP_Inst.log RUNLIVEUPDATE=0 REBOOT=REALLYSUPPRESS" We've also tried just using setup.exe /s - no improvement I've googled, and got to the end of the Internet and it seems like this is common issue with SEP and OSD. *sigh* Anyone got this working? Michael Dzikowski Senior Systems Engineer | Ally Technical Infrastructure - Windows Hosting 200 Renaissance Center, Detroit MI M + 734 629 7797 | [email protected]<mailto:[email protected]> [cid:[email protected]] ________________________________ [Idaho Power Legal Disclaimer] This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ________________________________
<<inline: image001.png>>
