Hi All,
just to close this one out, Issue over view: USMT task sequence to capture profiles was failing with an error 0x00000046 (the remote server has been paused or is in the process of being started) at the use toolkit package step of the task sequence. This task sequence would work correctly when tested on new computers where the McAfee Policy hadn’t applied, but would fail on computers where the Policy had applied. On review of the SMSTS log files it pointed to ZTISCCM: permission denied (70) and the McAfee log was not logging anything. Resolution: We have discovered that the pre-canned “Prevent Execution of scripts from the temp folder” rule was turned on without the report feature (which explains no logging), and this rule was preventing cscript from calling the scripts from MDT package inside the Task Sequence. To remediate this issue the nice McAfee agent recommended to exclude the cscript.exe Process from this rule, so the rule will look something like this: hope this helps out others Cheers Steve From: steven hosking Sent: Wednesday, 16 July 2014 6:21 AM To: [email protected] Hi Trevor, I completely agree with your statement to avoid rushing in to blame the a/v, but we have very much validated that we have issues with the McAfee VSE 8.8 with our SCCM2012 implementation, it has been quite frustrating, as we solo McAfee to auto deploy its agent, so when we did testing of software install and USMT on brand new built OSes it has worked, and then we hand it over to our desktop team and it doesn't work, with errors pointing SCCM distribution issues and hash error’s and no mention of McAfee stopping the processes. We will be spending more time investigating the issue as we were doing an office 2010 version change over last night and McAfee was killing the processes and alike, very frustrating, Cheers Steve From: Trevor Sullivan Sent: Wednesday, 16 July 2014 1:17 AM To: [email protected] While I wouldn’t discount the importance of discussing A/V exclusions, I would also not be too hasty to blame it on McAfee, unless there is specific evidence supporting it. · Does the same deployment exhibit the same symptoms on a system without the McAfee client installed? · What is the exact error? · Do all systems exhibit the same behavior, or a specific subset of them? · What attributes about the failing systems are common to each other? o Same Manufacturer? o Same OS? o Same geographic location? o etc. Cheers, Trevor Sullivan Microsoft PowerShell MVP From: [email protected] [mailto:[email protected]] On Behalf Of steven hosking Sent: Tuesday, July 15, 2014 1:45 AM To: [email protected] Subject: Re: [mssms] AV Exclusions for SCCM 2012 R2 Thanks David, Exactly what I was looking for. 😊 From: David O'Brien Sent: Tuesday, 15 July 2014 4:07 PM To: [email protected] Hi Steve, Have a look here: http://blogs.technet.com/b/systemcenterpfe/archive/2013/01/11/updated-system-center-2012-configuration-manager-antivirus-exclusions-with-more-details.aspx and http://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012/ Cheers David From: [email protected] [mailto:[email protected]] On Behalf Of steven hosking Sent: Tuesday, July 15, 2014 4:00 PM To: [email protected] Subject: [mssms] AV Exclusions for SCCM 2012 R2 Hi Guys, We are running McAfee VSE 8.8 and getting some wacky results with application deployments and Task Sequences, just wondering if anybody has a list of AV Exclusions, or can point me in the direction for the 2012 list of exclusions then I can pass on to our McAfee Admins? Cheers Steve
