Based on the variability of the state of the machine before it gets to SEP, we had to add a reboot right before that install step to get things to behave consistently. (There are some hardware-based application install steps before SEP, which is what created that variability based on the model.)
From: [email protected] [mailto:[email protected]] On Behalf Of Dzikowski, Michael Sent: Wednesday, October 30, 2013 3:58 PM To: [email protected] Subject: [mssms] RE: Symantec Endpoint Protection and OSD Task Sequence (CM12 / MDT) That's what I've done in the past. I'm 99% sure it's the package the "vendor" gave us and now I'm chasing ghost. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of [email protected]<mailto:[email protected]> Sent: Wednesday, October 30, 2013 4:47 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Symantec Endpoint Protection and OSD Task Sequence (CM12 / MDT) I created a silent package, that suppresses the reboot from my SEPM server (12.1 latest rev.) and am just running "setup.exe" :) Christopher Catlett Consultant | Detroit [MCTS_2013_small] Sogeti USA Office 248-876-9738 |Fax 877.406.9647 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456 www.us.sogeti.com<http://www.us.sogeti.com/> From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sander Groen Sent: Wednesday, October 30, 2013 4:05 PM To: [email protected]<mailto:[email protected]> Subject: [mssms] RE: Symantec Endpoint Protection and OSD Task Sequence (CM12 / MDT) Hi, We deploy version 12.1.3001.165 of SEP and I use the following command line: "setup.exe" /s /v"/qn REBOOT=REALLYSUPPRESS" I have not seen reboots during OSD or after a normal software deployment. Met vriendelijke groet, Brink Groep Sander Groen Van: [email protected]<mailto:[email protected]> [mailto:[email protected]] Namens Dzikowski, Michael Verzonden: woensdag 30 oktober 2013 20:14 Aan: [email protected]<mailto:[email protected]> Onderwerp: [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]] [CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records. To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com
<<inline: image001.jpg>>
<<inline: image002.png>>
