Review the Installation Considerations› ›Review the Installation ConsiderationsReview the following installation considerations before installing Arcserve UDP Agent (Windows):. The Arcserve UDP Agent (Windows) installation package is available through a web download and from the product installation CD.Note: You can use Arcserve UDP for a trial period. At the end of the trial period, if you have not obtained a license, Arcserve UDP will automatically revert to a with limited capabilities. Verify that you have administrator privileges or the proper permissions to install software on the servers where you are installing Arcserve UDP Agent (Windows). If you uninstall and install a new Arcserve UDP Agent (Windows) build and specify the same backup destination as the previous build, the first backup after the installation runs as a Verify backup.Note: After deploying the agent, you do not need to reboot to start backup. For details, refer to.
![](/uploads/1/2/6/8/126859104/926956748.jpg)
After installation, you can configure your antivirus software to exclude specific processes, folders, and files so that the antivirus software does not interfere with the proper operation of Arcserve UDP Agent (Windows). For a complete list of processes, folders, and files that should be excluded, see. If Arcserve UDP Agent (Windows) is being installed on a x64 Windows Core Operating System, you should also install Windows-on-Windows 64-bit (WOW64) on the Server Core for the Arcserve UDP Agent (Windows) setup to work. For a list of the possible error codes that the Arcserve UDP Agent (Windows) installer could return, see. Review the which provides the supported operating systems, databases, and browsers.Copyright © 2016.All rights reserved.
Use the Hotfix Installer to install updates for Configuration Manager. 15 minutes to read.In this articleApplies to: Configuration Manager (current branch)Some updates for Configuration Manager are not available from the Microsoft cloud service and are only obtained out-of-band. An example is a limited release hotfix to address a specific issue.When you must install an update (or hotfix) that you receive from Microsoft, and that update has a file name that ends with the extension.exe (not update.exe), you use the hotfix installer that is included with that hotfix download to install the update directly to the Configuration Manager site server.If the hotfix file has the.update.exe file extension, see. NoteThis topic provides general guidance about how to install hotfixes that update Configuration Manager. For details about a specific update, refer to its corresponding Knowledge Base (KB) article at Microsoft Support. NoteUpdates for site system roles (including updates for the site database and cloud-based distribution points) are installed as part of the update for site servers and services by the site component manager.However, updates pull-distribution points are serviced by distribution manager instead of the site component manager.Each update bundle for Configuration Manager is a self-extractable.exe file (SFX) that contains the files that are necessary to install the update on the applicable components of Configuration Manager.
Typically, the SFX file can contain the following files: FileDetails-QFE-KB-.exeThis is the update file. The command line for this file is managed by Updatesetup.exe.For example:CM1511RTM-QFE-KB123456-X64-ENU.exeUpdatesetup.exeThis.msi wrapper manages the installation of the update bundle.When you run the update, Updatesetup.exe detects the display language of the computer where it runs.
Expand How to Install Arcserve Backup Using Unicenter Software Delivery. Agent Deployment is a wizard-like application that lets you install or upgrade Arcserve. Do not install the Arcserve Backup Client Agent for Windows into the same. SQL Server 2008 Express Edition) complete the required fields on this dialog. I) Ca ARCServe may not be able to communicate properly with tape devices if another vendor's backup application is installed, even if the services for that application are disabled. Do not install tape diagnostic tools when CA ARCserve Services are running. Remove the tape diagnostic tools after the diagnostic tests are complete.
By default, the user interface for the update is in English. NoteYou can deploy updates only to computers that run the Configuration Manager client.If you reinstall a client, Configuration Manager console, or SMS Provider, you must also reinstall the updates for these components.Use the information in the following sections to install updates on the each of the components for Configuration Manager. Update serversUpdates for servers can include updates for sites, the site database, and computers that run an instance of the SMS Provider: Update a siteTo update a Configuration Manager site, you can install the update bundle directly on the site server, or you can deploy the updates to a site server after you install the update bundle on a different site.When you install an update on a site server, the update installation process manages additional actions that are required to apply the update, such as updating site system roles. The exception to this is the site database. The following section contains information about how to update the site database. Update a site databaseTo update the site database, the installation process runs a file named update.sql on the site database.
You can configure the update process to automatically update the site database, or you can manually update the site database later.Automatic Update of the Site DatabaseWhen you install the update bundle on a site server, you can choose to automatically update the site database when the server update is installed. This decision applies only to the site server where you install the update bundle and does not apply to deployments that are created to install the updates on remote site servers. ImportantBefore you update the site database, create a backup of the site database. You cannot uninstall an update to the site database. For information about how to create a backup for Configuration Manager, see.Manual Update of the Site DatabaseIf you choose not to automatically update the site database when you install the update bundle on the site server, the server update does not modify the database on the site server where the update bundle runs. However, deployments that use the package that is created for software deployment or that installs always update the site database. WarningWhen the update includes updates to both the site server and the site database, the update is not functional until the update is completed for both the site server and site database.
Until the update is applied to the site database, the site is in an unsupported state.To manually update a site database:.On the site server stop the SMSSITECOMPONENTMANAGER service, and then stop the SMSEXECUTIVE service.Close the Configuration Manager console.Run the update script named update.sql on that site's database. For information about how to run a script to update a SQL Server database, see the documentation for the version of SQL Server that you use for your site database server.Restart services that were stopped in previous steps.When the update bundle installs, it extracts update.sql to the following location on the site server: SMSHotfixupdate.sqlUpdate a computer that runs the SMS ProviderAfter you install an update bundle that includes updates for the SMS Provider, you must deploy the update to each computer that runs the SMS Provider.
The only exception to this is the instance of the SMS Provider that was previously installed on the site server where you install the update bundle. The local instance of the SMS Provider on the site server is updated when you install the update bundle.If you remove and then reinstall the SMS Provider on a computer, you must then reinstall the update for the SMS Provider on that computer. Update clientsWhen you install an update that includes updates for the Configuration Manager client, you are presented with the option to automatically upgrade clients with the update installation, or manually upgrade clients at a later time.
![Installing Installing](/uploads/1/2/6/8/126859104/411871019.jpg)
For more information about automatic client upgrade, see.You can deploy updates with Updates Publisher or a software deployment package, or you can choose to manually install the update on each client. For more information about how to use deployments to install updates, see the section in this topic. ImportantWhen you install updates for clients and the update bundle includes updates for servers, be sure to also install the server updates on the primary site to which the clients are assigned.To manually install the client update, on each Configuration Manager client, you must run Msiexec.exe and reference the platform-specific client update.msp file.For example, you can use the following command line for a client update.
This command line runs MSIEXEC on the client computer and references the.msp file that the update bundle extracted on the site server: msiexec.exe /p SMSHotfixClient /L.v REINSTALLMODE=mous REINSTALL=ALL Update Configuration Manager consolesTo update a Configuration Manager console, you must install the update on the computer that runs the console after the console installation is finished. ImportantWhen you install updates for the Configuration Manager console, and the update bundle includes updates for servers, be sure to also install the server updates on the site that you use with the Configuration Manager console.If the computer that you update runs the Configuration Manager client:.You can use a deployment to install the update. For more information about how to use deployments to install updates, see the section in this topic.If you are logged directly on to the client computer, you can run the installation interactively.You can manually install the update on each computer. To manually install the Configuration Manager console update, on each computer that runs the Configuration Manager console, you can run Msiexec.exe and reference the Configuration Manager console update.msp file.For example, you can use the following command line to update a Configuration Manager console. This command line runs MSIEXEC on the computer and references the.msp file that the update bundle extracted on the site server: msiexec.exe /p SMSHotfixAdminConsole /L.v REINSTALLMODE=mous REINSTALL=ALL Deploy updates for Configuration ManagerAfter you install the update bundle on a site server, you can use one of the following three methods to deploy updates to additional computers. Use Updates Publisher 2011 to install updatesWhen you install the update bundle on a site server, the installation Wizard creates a catalog file for Updates Publisher that you can use to deploy the updates to applicable computers.
![Download Download](/uploads/1/2/6/8/126859104/160715992.png)
The wizard always creates this catalog, even when you select the option Use package and program to deploy this update.The catalog for Updates Publisher is named SCUPCatalog.cab and can be found in the following location on the computer where the update bundle runs: SMSHotfixSCUPSCUPCatalog.cab. ImportantBecause the SCUPCatalog.cab file is created by using paths that are specific to the site server where the update bundle is installed, it cannot be used on other site servers.After the wizard is finished, you can import the catalog to Updates Publisher, and then use Configuration Manager software updates to deploy the updates. For information about Updates Publisher, see in the TechNet library for System Center 2012.Use the following procedure to import the SCUPCatalog.cab file to Updates Publisher and publish the updates. To import the updates to Updates Publisher 2011.Start the Updates Publisher console and click Import.On the Import Type page of the Import Software Updates Catalog Wizard, select Specify the path to the catalog to import, and then specify the SCUPCatalog.cab file.Click Next, and then click Next again.In the Security Warning - Catalog Validation dialog box, click Accept. Close the wizard after it is finished.In the Updates Publisher console, select the update that you want to deploy, and then click Publish.On the Publish Options page of the Publish Software Updates Wizard, select Full Content, and then click Next.Complete the wizard to publish the updates.Use software deployment to install updatesWhen you install the update bundle on the site server of a primary site or central administration site, you can configure the installation Wizard to create update packages for software deployment. You can then deploy each package to a collection of computers that you want to update.To create a software deployment package, on the Configure Software Update Deployment page of the wizard, select the check box for each update package type that you want to update. The available types can include servers, Configuration Manager consoles, and clients.
A separate package is created for each type of update that you select. NoteThe package for servers contains updates for the following components:. Site server. SMS Provider. Site databaseNext, on the Configure Software Update Deployment Method page of the wizard, select the option I will use software distribution. This selection directs the wizard to create the software deployment packages.After the wizard is finished, you can view the packages that it creates in the Configuration Manager console in the Packages node in the Software Library workspace. You can then use your standard process to deploy software packages to Configuration Manager clients.
When a package runs on a client, it installs the updates to the applicable components of Configuration Manager on the client computer.For information about how to deploy packages to Configuration Manager clients, see. Create collections for deploying updates to Configuration ManagerYou can deploy specific updates to applicable clients. The following information can help you to create device collections for the different components for Configuration Manager.
![](/uploads/1/2/6/8/126859104/926956748.jpg)