1 reply to this topic

[anyweb]

In Part 1. of this series we Installed vNext, in Part 2 we started to configure it. In Part 3, we configed Beta 2 some more by enabling Active Directory discovery methods, adding some site system roles, configuring the computer client agent and client push settings and finally doing a manual client installation to verify it all worked, in Part 4 we looked at installing an application using Application Management and the Software Catalog and Software Center features of SCCM 2012. Our next task is to add WSUS and then add some additional roles which we'll use later on in this series (Windows Updates and Data Migration in OSD).


Perform the following on the vNext server as SMSadmin

Step 1. Add the WSUS role
We'll need the WSUS role installed as part of the Software Update Point role installation in the next step, so start Server Manager and click on Roles, Add Roles. Select Windows Server Update Services and a window will pop up asking to add role services required for Windows Server Update Services (IIS Dynamic Content compression), click Add Required Role Services



click next through the wizard, you'll see the Select Role Services window appear, click next again



at the confirmation click Install, the WSUS role will be downloaded and if you are on 3G like me that'll take a bit of time, so take a break and have a cup of coffee

after a while you'll see the Welcome to Windows Server Update Services 3.0 SP2 setup wizard appear click next



To install WSUS SP2 you must accept the terms of the EULA, which are probably hidden behind the active windows, so in your system tray find it and click on it to show the EULA otherwise you'll be twiddling your thumbs for a long time wondering whats going on...



click accept and then choose where to store the updates locally, I selected D:\sources\WSUS



for database options choose Use an existing database server on this computer, click next



it will connect to your VNEXT sql server instance, click next



accept the Use an existing Default website



at the ready to install WSUS, click next



click Finish when done.



and close the Roles Wizard



followed by Cancel you must cancel the Windows Server Update Services Configuration Wizard

[anyweb]

Step 2. Add the SLP, SMP, SUP and FSP roles

We will be doing some DATA migration later and hope to install Windows Updates too, so as part of that let's add the following roles, Server Locator Point (SLP - to find the Site server when not joined to AD, eg: workgroup joined as in Build and Capture), State Migration Point (SMP, for storing our saved user data) and Software Update Point (SUP, software updates), Fallback status point (FSP).

In Configmgr's console, click on Administration, Site Operations, Servers and Site System roles, in the Ribbon, click on Add Site System Role



Click next on the Create Roles Wizard page



select the 4 roles and click next



and accept the settings for SLP



for SMP, click on the yellow starburst and point the Storage folder to d:\sources\usmtstore, click ok and next when done



our previously defined Boundary Group (P01 Clients) is listed, click next to continue, it's needed for the SMP



click next at the specify software update point settings (we have no proxy)



select this server as the active software update point and configure WSUS to listen on default website (ports 80 and 443)



Synchronize from Microsoft Update



enable Sync on a Schedule



set it to Immediately Expire superseded updates



leave classifications as it is, we'll come back to this later



leave Products as it is, we'll come back to this later (after a sync...)



and leave only English selected in Languages



now that the SUP role questions are out of the way, for the FSP leave it as it is



click next, next and review the successful completion



That's it !