Glad to here.  Those first syncs can take forever if you have a lot of
products selected.  When I have to sync a new one I usually plan to let it
run overnight

-----
Dwayne Allen
[email protected]
(479) 310-0027

On Wed, Oct 1, 2014 at 11:02 AM, Charles Hiland <[email protected]
> wrote:

> Updates are moving a long – I may be good from here, but will check back
> if I run into a wall.  Thanks, all!
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Charles Hiland
> *Sent:* Wednesday, October 01, 2014 11:54 AM
>
> *To:* [email protected]
> *Subject:* RE: [mssms] SCCM 2012 + SUP Help
>
>
>
> I’ve installed WSUS on my primary SCCM server and configured the WSUS
> update source to point to my current WSUS server.  I’m performing  a sync
> at the moment, but it’s taking its time… Still @ 0% and has been running
> for only a few minutes. I think I’m on the right track, no?
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Jason Wallace
> *Sent:* Wednesday, October 01, 2014 11:48 AM
> *To:* [email protected]
> *Subject:* RE: [mssms] SCCM 2012 + SUP Help
>
>
>
> This article discussed repurposing a WSUS server.  Charles is wanting to
> retain his existing WSUS server and to synch from it.
>
> From a CM site you will still need to install WSUS and set it up as a SUP,
> then you will configure synchs to come from an upstream WSUS server.
>
> ------------------------------
>
> From: [email protected]
> To: [email protected]
> Subject: RE: [mssms] SCCM 2012 + SUP Help
> Date: Wed, 1 Oct 2014 15:36:37 +0000
>
> Charles,
>
>
>
> You might want take a look this:
> http://social.technet.microsoft.com/Forums/en-US/1f6962ab-7f7a-4b1c-b950-1184b3babfaf/sccm-and-standalone-wsus-server-integration?forum=configmanagerdeployment
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Dwayne Allen
> *Sent:* Wednesday, October 01, 2014 8:31 AM
> *To:* [email protected]
> *Subject:* RE: [mssms] SCCM 2012 + SUP Help
>
>
>
> When you set up your SUP have it use the WSUS  server as an upstream
> source instead of Microsoft
>
> On Oct 1, 2014 10:24 AM, "Charles Hiland" <[email protected]>
> wrote:
>
> Jason, you are correct in saying that I want SCCM to synchronize updates
> from our existing WSUS machine.
>
>
>
> -Charles
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Jason Wallace
> *Sent:* Wednesday, October 01, 2014 11:03 AM
> *To:* [email protected]
> *Subject:* RE: [mssms] SCCM 2012 + SUP Help
>
>
>
> Hi Charles
>
> To summarise, are you saying that you want to use SCCM for management but
> you DO NOT want SCCM to deploy software updates to SCCM clients?  If this
> is the case then you simply do not enable the Software Updates policy in
> SCCM and clients will take WSUS settings from Group Policy or however else
> it is that you wish to deliver them.  In this case SCCM would not be used
> at all and no content would reside upon your DPs
>
> If what you want to achieve is to have your internal WSUS server act as
> the single point of updates and then have SCCM synchronise some or all
> updates from this machine then again this is possible.
> ------------------------------
>
> From: [email protected]
> To: [email protected]
> Date: Wed, 1 Oct 2014 10:42:45 -0400
> Subject: [mssms] SCCM 2012 + SUP Help
>
> I’m looking to set up SUP on our SCCM 2012 primary server (we also have 6
> DPs located in other offices).  We currently have a stand-alone WSUS server
> that handles Windows updates for servers and clients.  That being said, we
> don’t have the CALs to support servers via SCCM, so this setup would be
> strictly for workstation systems.  Does anyone have any steps for setting
> this up?  Google has plenty of results for if WSUS is going to run on the
> SCCM server, but what I’m trying to do is use the SCCM server to pull
> updates from our WSUS server.
>
>
>
> Any help is greatly appreciated.
>
>
>
> Thanks.
>
>
>
> ______________________________
> *Charles Hiland*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>



Reply via email to