Indeed - FEP, not SCEP! Doh
> On 5 Mar 2014, at 22:15, "Todd Condit" <[email protected]> wrote: > > %allusersprofile%\Microsoft\Microsoft Security Client > > > Todd Condit > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Joshua Searles > Sent: Wednesday, March 05, 2014 2:04 PM > To: [email protected] > Subject: RE: [mssms] FEP Updates without WSUS > > No such log file exists on any of my FEP clients that I’ve looked at. > > From: [email protected] [mailto:[email protected]] > On Behalf Of Jason Wallace > Sent: Wednesday, March 05, 2014 1:56 PM > To: [email protected] > Subject: Re: [mssms] FEP Updates without WSUS > > %windir%\ccm\logs on the client > > On 5 Mar 2014, at 21:54, "Joshua Searles" <[email protected]> wrote: > > Hmm where would that log file be located? I don’t see it on the log file > list. http://technet.microsoft.com/en-us/library/gg477022.aspx > > > From: [email protected] [mailto:[email protected]] > On Behalf Of Jason Wallace > Sent: Wednesday, March 05, 2014 1:36 PM > To: [email protected] > Subject: Re: [mssms] FEP Updates without WSUS > > Does endpointprotection.log give you any clues? > > On 5 Mar 2014, at 21:34, "Joshua Searles" <[email protected]> wrote: > > It appears according to policy configurations that I can setup FEP clients to > get their updates from a UNC share, and take WSUS completely out of the > equation(It’s complicated, please don’t ask.) Has anyone on the list here > successfully configured FEP policy for their clients to get their definition > updates from a UNC path? I’ve configured the default policy to get updates > from a UNC Path. I’ve configured the UNC path share for read only (both > users and computer accounts). The x86, and x64 architecture folders are in > place. The updates are in the folders, yet clients will not install the > updates from the UNC path. What am I missing? > > Confidentiality Notice: This e-mail message, including any attachments, is > for the sole use of the intended recipient(s) and may contain confidential > and privileged information. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, please > contact the sender by reply e-mail and destroy all copies of the original > message. > > > > > >
