Tell Kent I said, "hey" when you see him.
From: Anders Blomgren [mailto:[email protected]] Sent: Monday, September 24, 2012 12:40 PM To: NT System Admin Issues Subject: Re: System Center 2012 Endpoint Protection I don't have any problems per se with how they work, it's just that the workflow is much more open-ended than wsus is, which makes you plan a bit more how you want to handle them. Saw a recommendation from an MS blog but even that didn't give a straight answer. Also, I'm going to train with Kent Agerlund, a CM MVP next week, so I'm planning to get as many recommendations as I can during those 3 days. -Anders On Mon, Sep 24, 2012 at 5:15 PM, Heaton, Joseph@DFG <[email protected]> wrote: What difficulties are you running into with Software Updates? Joe Heaton ITB - Enterprise Server Support From: Anders Blomgren [mailto:[email protected]] Sent: Monday, September 24, 2012 7:57 AM To: Heaton, Joseph@DFG; NT System Admin Issues Subject: Re: System Center 2012 Endpoint Protection No, you cant push definition updates through another wsus than the one systems are using. You have to have the updates unmanaged (clients download best effort). The question I answered was about SQL and site systems coexisting - my Endpoint Protection installation is still at the testing stage. Until I get the SUP part done, I won't consider deploying Endpoint Protection. To be honest I find Software Updates the hardest part of implementing SCCM. Not having any experience with previous versions, other than "No way I'm doing that", was it always thus? -Anders On Mon, Sep 24, 2012 at 4:01 PM, Joseph L. Casale <[email protected]> wrote: > Same server. I have my other wsus install coexisting for now. SP1 will support bringing > in an existing wsus server. RTM requires that you use an unconfigured wsus installation. No problem, I actually want to punt the old one anyway. > For me, separate SQL means another VM which means another OS overhead. Yea, I thought about the license after and it seems setup wants it local anyway, funny in a single server deployment it omits to remove the port warning for sql. You mentioned your original wsus server is still up, so without any local wsus config for the sccm instance (as clients still point to their original wsus server) I suppose the policy source definition simply needs to be set to sccm server or url for example, then clients can happily use the existing wsus server for os updates etc? Thanks! jlc ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
