1. To initiate the Updates Publisher Setup, run Setup.exe from the installation source folder.

2. On the Welcome page of the System Center Updates Publisher Setup Wizard, click Next.

3. Click I accept the license agreement and then click Next.

   Note
   You must accept the license terms and conditions to continue. Click Print license agreement to print a copy of the license terms.

4. Specify whether to use a local or remote database for Updates Publisher.

   Local Database: Specify Local Database if the Updates Publisher database will reside on the local computer.

   • If SQL Server 2005 or SQL Express 2005 is installed on the local computer, the Select SQL instance name page displays. Select the instance of SQL Server from the list, and then click Next.
     
     
   • If SQL Server 2005 or SQL Express 2005 is not installed on the local computer, the Detect and Install Required Components page displays. SQL Server 2005 Express Edition will be installed on the local computer using the default SQL instance. Continue to step 5.
     
     

   Important
   To create the Updates Publisher database, the user installing the publishing tool must be a local administrator with the proper permissions to create the local database.

   Note

   Because of a known issue, when using a local database with SQL Server 2005 64-bit, you must select Remote Database even though the database server is local. The local 64-bit database must be created prior to installing the Updates Publisher by using a script located on the installation CD. For more information about using a script to create the database, see How to Create the Updates Publisher Database.

   Remote Database: Specify Remote Database if the Updates Publisher database will reside on a remote computer. Enter the name of the computer running SQL Server and the name of the instance of SQL Server for the remote database, and then click Next. When the SQL Instance value is not specified, the default instance of SQL Server is used. Setup validates the connection to the server and instance of SQL Server. If the connection fails, an error message displays and Setup returns to the Select Database Server and Instance Name page for a valid entry.

   Important
   The remote database must be created prior to installing the Updates Publisher by using a script located on the installation CD. For more information about using a script to create the database on a remote computer, see How to Create the Updates Publisher Database.

5. Setup verifies that Windows Installer 3.1, .NET Framework 2.0, SQL Server 2005 or SQL Server Express 2005, and Windows Server Update Services (WSUS) 3.0 Administrator Console are all installed on the computer, and if not, the Detect and Install Required Components page displays and lists the missing components. Click Install to install the components on the local computer. Click Next. If Setup fails to install any of these components, it displays a message with the associated installation error. For more information, see Requirements for Updates Publisher.

6. Provide the path to an NTFS, non encrypted, local folder that will be used as the destination folder and package source folder location for Updates Publisher. The default folder path is %programfiles%\System Center Updates Publisher. Click Browse to select a different folder location, and then click Next.

7. Click Next to initiate the Updates Publisher installation.

   Note
   If an error occurs during the installation, an error message displays. Review %Temp%\PublishingToolsetup.log for error messages that might indicate the root cause for the issue.

8. On the Setup Complete page, click Finish.

1. To initiate the Updates Publisher Setup silently in unattended mode, run Setup.exe from the installation source folder using the following command-line switch:

   Setup.exe -qn

   Updates Publisher is installed silently using the default instance of SQL Server for a database on the local computer. To install Updates Publisher using a remote SQL database or a different instance of SQL Server, the following additional command-line switches are available:

   -DBLocationType type, where type is either Local or Remote. If this switch is not used in the command-line, Setup assumes that a local database is used.

   -SQLInstance instancename, where instancename is the name of the instance of SQL Server. If this switch is not used, Setup assumes that the default instance of SQL Server is used.

   -SQLMachineName computername, where computername is the name of the computer that hosts the SQL Server database. If this switch is not specified in the command-line, Setup assumes that the local computer is used to host the SQL Server database.

   The following two examples demonstrate the use of the command-line switches:

   • The following command-line specifies that the Updates Publisher database is on the local computer and that the SCUP instance of SQL Server should be used:
     
     Setup.exe -qn -SQLInstance SCUP
     
     
   • The following command-line specifies that the database is on the remote computer Server1 and that the default instance of SQL Server should be used:
     
     Setup.exe -qn -DBLocationType Remote -SQLMachineName Server1
     
     

2. The Updates Publisher installation completes silently for successful and failed installations. Review %Temp%\PublishingToolsetup.log for error messages that might indicate the root cause for the issue.

   Note

   The name of the computer running SQL Server and the name of the instance of SQL Server are not validated during a silent installation. The Updates Publisher installation will complete and an error dialog box will occur when the Updates Publisher console is opened. For more information about changing the computer running SQL Server or the instance of SQL Server, see How to Configure the Data Source for Updates Publisher.

Tasks

Concepts

Other Resources