Jump to content


anyweb

using vNext in a LAB - Part 9. Configuring SUP

Recommended Posts

In Part 1. of this series we Installed vNext.

In Part 2., we then Configured vNext to use the New AD Site as a boundary and Configured Discovery Methods in vNext.

In Part 3, we installed the Reporting Point Role along with some additional roles and configured them.

In Part 4 we configured the client Agents and deployed the vNext Client.

In Part 5 we deployed an Application to All Users.

In Part 6 we added Windows Deployment Services, added the PSP role, added the Windows 7 Enterprise image, and updated our boot image for Deploying Windows 7.

In Part 7 we created our Build and Capture Task Sequence, enabled the Network Access Account, Advertised (Deployed) the Task Sequence, and created a new hyper-v virtual machine for capturing the wim on.

In Part 8 we installed WSUS and then the SUP and SLP roles.

 

Now we will configure add some products to get sync info about, and target some updates to collections.

 

Step 1. Select some Products.

 

In the Wunderbar click on Administration. Select Site Operations, Sites and then Right click our Site Server and click Properties.

 

site properties.png

 

When the properties appear, select the Component Configuration Tab, Select Software Update Point and click on Edit.

 

software update point component.png

 

Click on the Products tab and scroll down, select the following products.

 


     
  • Windows 7
  • Windows Server 2008 R2
  • Windows Server 2008

 

Click Apply when done.

 

select products.png

 

Then click Ok and Ok again.

Share this post


Link to post
Share on other sites

Step 2. Run a Synchronisation

 

In the Wunderbar, click on Software Library, Select Software Updates, All Updates, note that 0 items appear, Click on Run Synchronization in the Tasks pane.

 

run sync.png

 

You will be prompted to review the sms_wsus_sync_manager log to get confirmation, answer Yes.

 

sms_wsus_sync_manager.png

 

In the Wunderbar, click on Monitoring, system Status, Component Status, Select our SMS_WSUS_SYNC_MANAGER component, right click and choose Show Messages, All. Click Ok to the 1 day prompt.

 

sync status.png

 

Look for the Message ID 6702 Sync Done message,press F5 to refresh while waiting...

 

wsus sync done.png

 

Once the Sync is done, and you've verified it in the logs, in the Wunderbar click on Software Library, Software Updates, All Updates. You should see hundreds of updates listed like so

 

483 items found.png

Share this post


Link to post
Share on other sites

Step 3. Create a new Search Folder

 

Right click on All Updates, choose Search Folder

 

search folder.png

 

click on New

 

new search folder.png

 

select the following options

 

Bulletin ID

Expired

Superseded

Product

 

click Add Selected when done

 

add selected.png

 

Click on Bulletin ID, when the window appears, type in the value MS and change Equals to Starts With

 

starts with.png

 

for Expired and Superseded, select No as the value, and for Product select Windows 7, give your search folder the name Windows 7 Security Updates

 

windows 7 security updates.png

 

click ok and ok again.

 

Notice the number of updates changes to much less than above, as we have filtered them to only show Windows 7 Security Updates that are not expired or superseded. Now we have 85 updates (Windows 7 security Updates)

 

all updates 85.png

Share this post


Link to post
Share on other sites

Step 4. Deploy our Windows 7 Updates

 

We want our Windows 7 computers that are being deployed to get these new updates. So let's target both the Unknown Computers collection and All Windows 7 computers collection with these updates.

 

Select the first update in the list, scroll down and select the last so that all are selected (you can press CTRL and A to select All). Notice that all items are now selected

 

85 items selected.png

 

right click and choose Deploy

 

deploy updates.png

 

on the General screen, select browse and browse to the All Unknown computers collection

 

general.png

 

set the Intent to Required (this makes the deployment mandatory)

 

required.jpg

 

set the Schedule, and make sure to choose Set A Deadline

 

set a deadline.jpg

 

set your User Experience options

 

user experience.png

 

set your Alert options, I entered 95%

 

95 percent.png

 

review your download settings (leave as default)

 

download settings.png

 

for Specify the Package to use, enter the following details (it's a new deployment package)

 

new deployment package.png

 

select our VNEXT dp by click on browse, Change to Distribution Points, vnext

 

vnextdp.png

 

select the download from internet option

 

download from internet.png

 

select English as the language, click next at the summary, and review the confirmation

 

done !

 

updates done.png

Share this post


Link to post
Share on other sites

Step 5. Create All Windows 7 collection

 

In the wunderbar click on Assets and compliance and select Device Collections, click on Create Collection in the Tasks Pane

 

create collection.png

 

give the collection a name, All Windows 7

 

all windows 7.png

 

fill in the query with this

 

select *  from  SMS_R_System where SMS_R_System.OperatingSystemNameandVersion like "%Workstation 6.1%"

 

query.png

 

success !

 

win7done.png

Share this post


Link to post
Share on other sites

Step 6. Deploy the Windows 7 updates to our new collection

 

repeat step 4 using the All Windows 7 collection we created above, except name the deployment Windows 7 2010 Baseline. Any Windows 7 client that you have running will now receive these new policies and the All Windows 7 targetted deployment will mean that these updates are deployed, you can review them being installed in the Installation Status tab of Software Center.

 

installation status.jpg

 

To Summarise, we created Two Software Update deployments, one to the All Unknown Computers (this targets Windows 7 updates to computers getting deployed via OSD) and the other to All Windows 7 Computers.

 

 

Step 7. Review our Deployment Settings.

 

You can review these two Deployments (advertisements or Deployment Management Tasks if you are thinking the same way as before with SCCM 2007) by Selecting Update Groups

 

update groups.jpg

 

if you select one Deployment (1.)and then click on the Deployment Tab (2.), Right click on Microsoft Updates below, and select Properties (3.).

 

123.jpg

 

now you can review/change settings of the original Deployment by selecting the various tabs.

 

various tabs.jpg

 

click Cancel to exit.

 

 

Step 8. Rename our Update Group

 

Right click on our original Update Group Deployment called Update Group.... Choose Properties

 

rename update group.jpg

 

when the properties appear, Mark the Name, right click, choose Cut,

 

cut.jpg

 

Paste the information that you Cut above into the Description Field (so that you know when the Deployment was made) and give it a new, meaningful name like All Windows 7 Updates for Unknown Computers, click apply then ok.

 

all windows 7 updates.jpg

 

Notice how our Software Updates Deployments look now...

 

update group renamed.jpg

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...