When you have a Configuration Manager hierarchy, install and configure the software update point at the central administration site first, and then install and configure the software update points on other sites. Some settings are only available when you configure the software update point on a central administration site, or stand-alone primary site, and there are different options that you must consider depending on where the software update point is installed. Use the steps in the following table to install and configure the software update point, synchronize software updates, and configure the settings associated with software updates.
I am running with CAS ,Primary and Secondary site. If you have only one primary site which is stand alone,perform the steps on primary site.
some information from TechNet:
Central administration site :
When you have a Configuration Manager hierarchy, install and configure the software update point on the central administration site before you install it on child primary sites and secondary sites. To enable software update in the hierarchy, you must have an active software update point on the central administration site.
Stand-alone primary site :
When you have a stand-alone primary site, a primary site that is not connected to a central administration site, install and configure the software update point to enable software update deployment at the site. When you have a secondary site connected to the stand-alone primary site, you must install the software update point on the primary site first.
Child primary site :
After you install a software update point on the central administration site, install and configure the software update point on child primary sites to enable software update deployment at the site. When you have a secondary site connected to the primary site, you must install the software update point on the primary site first.
Secondary site :
After you install the software update point on a primary site, you can optionally install and configure the software update point on a connected secondary site. When you do not have a software update point installed at the secondary site, clients assigned to the secondary site will use the software update point at the parent primary site. When there is limited network bandwidth to the software update point at the parent primary site or when Windows Server Update Services (WSUS) is approaching the maximum number of client computers at the primary site, consider installing a software update point at the secondary site.
Log into Central Administration site (CAS) and go to administration node.
Move onto site configuration—> Servers and Site System Roles
Right click on CAS site and select add site system Roles
Go with default settings
Select Software update Point Role
Specify proxy server name if you do not have internet on CAS site to get the updates into Database.
By default, the Local System account for the server on which an automatic deployment rule was created is used to connect to the Internet and download software updates when the automatic deployment rules run. When this account does not have access to the Internet, software updates fail to download and the following entry is logged to ruleengine.log: Failed to download the update from internet. Error = 12007. Configure credentials to connect to the proxy server when the Local System account does not have Internet access.
Select Use this server as Active Software update Point
select Synchronize from Microsoft Update to synchronize software updates from Microsoft Update. The central administration site must have Internet access or synchronization will fail. This setting is available only when configuring the software update point on the central administration site or stand-alone primary site.
When the software update point on the central administration site is disconnected from the Internet, you must select Do not synchronize from Microsoft Update and manually synchronize software updates
specify whether to synchronize software updates on a schedule.
Schedule software updates synchronization to run using a timeframe appropriate for your environment. One typical scenario is to set the software updates synchronization schedule to run shortly after Microsoft’s regular security update release on the second Tuesday of each month, typically referred to as Patch Tuesday. Another typical scenario is to set the software updates synchronization schedule to run daily when you use software updates to deliver Endpoint Protection definition and engine updates.
Specify how soon to expire the superseded updates.
This setting is configured only on the software update point for the central administration site.
Select the classification what is needed
Select the products to whom the patch needed
specify the languages for which you want to synchronize software update files and summary details. I go with English
Click Next summary Page
Monitor the SUPSetup.LOG file for software update point role installation is correctly done or not.