WSUS for SCCM SUP install on Win2008 R2 fails with "The update could not be found. There may be a network connection issue".

When trying to install WSUS on Windows Server 2008 R2 Standard the following error is thrown "The update could not be found. There may be a network connection issue". This is when trying to install WSUS from the Server Manager console.

The problem here was that this server was configured with a Local Policy to use another WSUS server as it's source for Windows Updates. I have no idea why it was configured as a Local Policy and not as a Group Policy. However, to resolve the problem, simply open the Local Policy editor, and browse to Computer Configuration/Administrative Templates/Windows Components/Windows Update.

Double click the Specify Intranet Microsoft update service location in my environment, this was enabled, with a legacy WSUS server populated in the intranet update fields. I changed this to Not Configure.

To double check the Local Policy has removed the problematic setting open the Registry, browse to Local Machine\Software\Policies\Microsoft\WindowsUpdate the intranet service points should not be present in this list of settings.

SCCM 2012 R2 error generated as Client Push tries to install SCCM Client onto a Hyper-V Cluster Object

SCCM 2012 R2 error "Client Configuration Manager failed to complete the ConfigMgr installation on client "HVCLUST01". In the past 168 hours, CCM has made 175 unsuccessful attempts. The operating system reported error 53: The network path was not found. This was failing because SCCM was trying to push the client to a Failover Cluster object for a Hyper-V Cluster. This is just a computer account that represents the logical cluster in Active Directory. However it was being discovered as a new computer during an SCCM discovery. 

The error was not causing any negative problems it was just causing red flags to be logged, which nobody likes.

The fix was to put the Hyper-V Cluster objects host name into the excludes servers list in the Registry of the SCCM server for that particular site. Browse to Local Machine\Software\Microsoft\SMS\Components\SMS_Discovery_Data_Manager and open the Registry key "ExcludeServers"

Installing and Configuring the Reporting Services (SRS) Point for ConfigMgr 2012 R2 (SCCM)

You should begin with installing the Reporting Services - Native instance feature from the SQL 2012 media.

 

You will be prompted to name the SQL Instance I named mine SRS. Click Next.

 

When Reporting Services installs successfully, click Close.

 

You must now configure Reporting Services before it is integrated with SCCM 2012 R2. Click the Reporting Services Configuration Manager icon from Start.

 

Click on the Service Account tab, and select Use another account: and input an Administrative domain account, and click Apply.

 

Skip over Web Services URL for now, and click Database.  Click on the Change Database button.

 

You will then follow through the wizard to provision a new database instance.

 

Also click Change Credentials from the Database tab, and ensure it is using an Administrative domain account. Click Apply. Now go back to the Web Service URL, you do not have to change any configurations here you must simply click Apply and this will push the wizard to provision and configure the IIS virtual directories to support the Reporting Server.

 

Now launch the ConfigMgr console and click Adminstration, expand Site and then Server and Site System Roles. Right click on your Primary Site Server and select Add Site System Roles.

 

Tick Reporting Services Point and click Next to continue.

 

Review the configurations and set the Reporting Services Username to an Administrative domain account. Click Next.

 

Reporting Services is now installed and configured.

 

Integrating ConfigMgr 2012 R2 and the Microsoft Deployment Toolkit (MDT)

On your Configuration Manager 2012 R2 server install the Microsoft Deployment Toolkit (MDT) 2013. Once MDT installed you will notice a new icon Configure ConfigMgr Integration.

 

Ensure Install MDT extensions for Configuration Manager is selected. Click Next.

Click Finish.

 

Now if you return to ConfigMgr and browse to Software Library expand Operating Systems and right click on Task Sequences the option to click Create MDT Task Sequence will now have appeared.

 

If you have been looking for a tutorial on how to integrate these products your requirements probably could benefit from the added OSD capabilities.