My observations are the following on Server 2012. When you install the feature you actually only install the files and bits needed for WSUS but nothing is actually done in the system beside that. When you run the "post install task" the database and the file system is created and set up. So in Windows Server 2012 those two steps together is equal to the setup for WSUS 3.x and earlier. After the post install is complete you should not do any further configuring on the wsus server but let SCCM do its magic as usual.
Regards Mattias Benninge On Tue, Jun 4, 2013 at 11:51 PM, Trond Karstensen <[email protected] > wrote: > I have installed wsus/sup on several WinSrv 2012 - SCCM 2012 systems and > have had to run the “wsus post install task” on all.**** > > It did not work at all if I did not do the wsus post install task.**** > > ** ** > > Not had any issues with any of them so far.**** > > **** > > Trond**** > > ** ** > > *From*: Brian McDonald > [mailto:[email protected]<[email protected]>] > > *Sent*: Tuesday, June 04, 2013 05:05 PM > *To*: [email protected] <[email protected]> > *Subject*: [mssms] SCCM 2012, WSUS on Windows Server 2012 > **** > > I have installed WSUS on Windows Server 2012 for SCCM 2012 SP1. When I > enabled the role, server manager wants me to configure the server. I was > under the impressions that we did not want to configure WSUS when used with > SCCM. I clicked on configure as I had no other choice to cancel out like we > could back with Windows Server 2008R2. Will this screw anything up when I > go to configure my site server (SUP)? > > Thanks, > > Brian**** > > ** ** > >
