The additional two files will install automatically If you experience download interruptions, consider a download manager utility. W04 W05 W06 W07 W08 W09 W10 9. Save all of the files to your computer when prompted 3. Double-click the file ProUpdate. The additional nine files will install automatically. If you experience download interruptions, consider a download manager utility.
By joining Download. Free YouTube Downloader. IObit Uninstaller. Internet Download Manager. Advanced SystemCare Free. VLC Media Player. MacX YouTube Downloader. Microsoft Office YTD Video Downloader. Adobe Photoshop CC. VirtualDJ Avast Free Security. WhatsApp Messenger. Talking Tom Cat.
Install a supported version of WSUS on all site system servers that you configure for the software update point role. When you don't install the software update point on the site server, install the WSUS Administration Console on the site server.
This component allows the site server to communicate with WSUS that runs on the software update point. This component performs periodic health checks. Choose one of the following options to configure the required permission:.
Configure a minimum of the webService database role membership. When you install more than one software update point at a primary site, use the same WSUS database for each software update point in the same Active Directory forest.
Sharing the same database improves performance when clients switch to a new software update point. When you install WSUS, you'll need to provide a content directory path. Otherwise it shares the same website that's used by the other Configuration Manager site systems or applications. This configuration is especially necessary when you install the software update point role on the site server.
Specify these ports when you create the software update point at a site. When you add the software update point role on a primary site server, you can't use a WSUS server that's configured as a replica. The first software update point that you install at a primary site is the default software update point. Additional software update points at the site are configured as replicas of the default software update point.
Using the SSL protocol to help secure the software update point is highly recommended. If you still require a user proxy despite the security trade-offs, a new software updates client setting is available to allow these connections.
The software update point at a Configuration Manager central administration site communicates with WSUS on the software update point.
WSUS communicates with the synchronization source to synchronize software updates metadata. Software update points at a child site communicate with the software update point at the parent site. When there's more than one software update point at a primary site, the additional software update points communicate with the default software update point.
The default role is the first software update point that's installed at the site. When your security policy doesn't allow the connection, use the export and import synchronization method.
For more information, see the Synchronization source section in this article. If your organization restricts network communication with the internet using a firewall or proxy device, you need to allow the active software update point to access internet endpoints. For more information, see Internet access requirements.
Software updates synchronization in Configuration Manager downloads the software updates metadata based on criteria that you configure. The top-level site in your hierarchy synchronizes software updates from Microsoft Update. You have the option to configure the software update point on the top-level site to synchronize with an existing WSUS server, not in the Configuration Manager hierarchy. The child primary sites synchronize software updates metadata from the software update point on the central administration site.
Before you install and configure a software update point, use this section to plan for the synchronization settings. The synchronization source settings for the software update point specify the location for where the software update point retrieves software updates metadata.
It also specifies whether the synchronization process creates WSUS reporting events. Synchronization source : By default, the software update point at the top-level site configures the synchronization source for Microsoft Update. You have the option to synchronize the top-level site with an existing WSUS server.
The software update point on a child primary site configures the synchronization source as the software update point at the central administration site. The first software update point that you install at a primary site, which is the default software update point, synchronizes with the central administration site. Additional software update points at the primary site synchronize with the default software update point at the primary site.
When a software update point is disconnected from Microsoft Update or from the upstream update server, configure the synchronization source not to synchronize with a configured synchronization source. Instead configure it to use the export and import function of the WSUSUtil tool to synchronize software updates. For more information, see Synchronize software updates from a disconnected software update point. These events aren't used by Configuration Manager. When these events aren't created, the only time that the client should connect to the WSUS server is during software update evaluation and compliance scans.
If these events are needed for reporting outside of Configuration Manager, modify this setting to create WSUS reporting events. Configure the synchronization schedule only at the software update point on the top-level site in the Configuration Manager hierarchy. When you configure the synchronization schedule, the software update point synchronizes with the synchronization source at the date and time that you specified. The custom schedule allows you to synchronize software updates to optimize for your environment.
Consider the performance demands of the WSUS server, site server, and network. For example, AM once a week. Alternatively, manually start synchronization on the top-level site by using the Synchronization Software Updates action from the All Software Updates or Software Update Groups nodes in the Configuration Manager console. Schedule the software updates synchronization to run by using a time that's appropriate for your environment.
One common scenario is to set the synchronization schedule to run shortly after Microsoft's regular software update release on the second Tuesday of each month. This day is typically referred to as Patch Tuesday. If you use Configuration Manager to deliver Endpoint Protection and Windows Defender definition and engine updates, consider setting the synchronization schedule to run daily.
After the software update point successfully synchronizes, it sends a synchronization request to child sites. If you have additional software update points at a primary site, it sends a synchronization request to each software update point. This process is repeated on every site in the hierarchy. Every software update is defined with an update classification that helps to organize the different types of updates.
During the synchronization process, the site synchronizes the metadata for the specified classifications. Critical Updates : A broadly released update for a specific problem that addresses a critical, non-security-related bug. Feature Packs : New product features that are distributed outside of a product release and are typically included in the next full product release. Security Updates : A broadly released update for a product-specific, security-related issue. Service Packs : A cumulative set of hotfixes that is applied to an OS or application.
These hotfixes include security updates, critical updates, and software updates. Update Rollups : A cumulative set of hotfixes that is packaged together for easy deployment. An update rollup generally addresses a specific area, such as security or a product component.
Configure the update classification settings only on the top-level site. The update classification settings aren't configured on the software update point on child sites, because the software updates metadata is replicated from the top-level site. When you select the update classifications, be aware the more classifications that you select, the longer it takes to synchronize the software updates metadata. As a best practice, clear all classifications before you synchronize for the first time.
After the initial synchronization, select the desired classifications, and then rerun synchronization. The metadata for each software update defines one or more products for which the update is applicable. A product is a specific edition of an OS or application. An example of a product is Microsoft Windows A product family is the base OS or application from which the individual products are derived.
An example of a product family is Microsoft Windows, of which Windows 10 and Windows Server are members. Select a product family or individual products within a product family.
When software updates are applicable to multiple products, and at least one of the products is selected for synchronization, all of the products appear in the Configuration Manager console even if some products weren't selected. For example, you only select the Windows Server product.
If a software update applies to Windows Server and Windows Server Datacenter Edition, both products are in the site database. Configure the product settings only on the top-level site. The product settings aren't configured on the software update point for child sites because the software updates metadata is replicated from the top-level site. The more products that you select, the longer it takes to synchronize the software updates metadata. Configuration Manager stores a list of products and product families that you choose from when you first install the software update point.
Products and product families that are released after Configuration Manager is released might not be available to select until you complete synchronization. The synchronization process updates the list of available products and product families from which you can choose. Clear all products before you synchronize software updates for the first time.
After the initial synchronization, select the desired products, and then rerun synchronization. Typically, a software update that supersedes another software update does one or more of the following actions:. Enhances, improves, or updates the fix that was provided by one or more previously released updates.
Improves the efficiency of the superseded update file package, which is installed on clients if the update is approved for installation. For example, the superseded update might contain files that are no longer relevant to the fix or to the operating systems that are supported by the new update. Those files aren't included in the superseding file package of the update.
Updates newer versions of a product. In other words, it updates versions that are no longer applicable to older versions or configurations of a product. Updates can also supersede other updates if modifications were made to expand language support. For example, a later revision of a product update for Microsoft Apps might remove the support for an older OS, but it might add additional support for new languages in the initial update release.
In the properties for the software update point, specify that the superseded software updates are immediately expired. This setting prevents them from being included in new deployments. It also flags the existing deployments to indicate that they contain one or more expired software updates. Or specify a period of time before the superseded software updates are expired.
This action allows you to continue to deploy them. A superseding software update supports only newer versions of an OS. Some of your client computers run earlier versions of the OS. A superseding software update has more restricted applicability than the software update it supersedes.
0コメント