If you do supernetting then you should manually specify the SCCM site and you'll be fine. You can do that when you deploy the agent, either automatically or manually. (And it can be done with a registry key change and service restart on the client afterwards) (Specifying the site may be even a capability of the client utility. I can't remember off the top of my head, but it probably is.).
But no, it isn't officially supported. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Free, Bob [mailto:[email protected]] Sent: Friday, February 04, 2011 4:50 PM To: NT System Admin Issues Subject: RE: RE: Patch management, revisited Do you ever run into any problems with SCCM clients where folks have done supernetting of AD Sites? Our SSCM guys are scared of it because they were told it could be problematic but we're tired of all the netlogon events we get on the DCs. We did an ADRAP and got dinged on it again this week and it came up again, the PFE said he didn't think it was a problem but could find articles in the internal KB/DLs where the SCCM team said worst case, it wasn't a supported configuration. I looked today and see the SCCM documentation team has even blogged about it. From: Michael B. Smith [mailto:[email protected]] Sent: Friday, February 04, 2011 11:46 AM To: NT System Admin Issues Subject: RE: RE: Patch management, revisited So, I wouldn't do anything without a few hours of discovery. But if you are just going to use it for patch management, say three days (worst case) to set it up and train someone how to deal with patches. Ongoing support is really no different than WSUS from my perspective. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com From: Jonathan [mailto:[email protected]] Sent: Friday, February 04, 2011 2:36 PM To: NT System Admin Issues Subject: Re: RE: Patch management, revisited "SCCM works very well if you have the time and staff to dedicate to it. I have about 1,000 PCs/ laptops here and tried SCCM, but never had the time to dedicate to it. And it was a real a pain to manage when you have limited time. But, it can be a great product and has flexibility. I wasn't willing to hire a staff member just for SCCM." This is one of the things that concerns me....administrative overhead is not a luxury we've got. MBS says it "just runs" once it is setup.... So, what's it really take to get it running and keep it that way? Also, I now know that we're initially focusing on strictly MS updates. Once MS patches are under reasonable control, we may look at 3rd party apps. Jonathan - Thumb typed from my HTC Droid Incredible (and yes, it really is) on the Verizon network. On Feb 4, 2011 2:24 PM, "Rod Trent" <[email protected]<mailto:[email protected]>> wrote: ~ 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]<mailto:[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]<mailto:[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]<mailto:[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
