SCCM NetBackup Client Deployment User Guide
SCCM NetBackup Client Deployment User Guide
Third-party mass-deployment tools like System Center Configuration Manager (SCCM) and Chef are available for
mass deployment on different platforms. These tools help to configure systems, deploy software, and orchestrate
more advanced IT tasks such as continuous deployments and performing custom actions before and after the
deployment.
Customers can use these third-party mass-deployment tools for deploying NetBackup clients on platform such as
Linux, Solaris, AIX, HP-UX, and Windows. These clients support different methods for deployment.
Veritas has developed deployment templates for SCCM to deploy NetBackup clients. This document explains the
methods on how to use these SCCM templates.
Software requirements
Ensure that the SCCM client is installed on all the servers where NetBackup client is to be installed.
Ensure the version level for SCMM is Microsoft System Center Configuration Manager 2012 R2
All windows platforms are supported. See the NetBackup Software Compatibility list for specific versions that
NetBackup supports:
https://netbackup.com/compatibility
Note: The SCCM template name for the NetBackup client deployment is Deployclient.ps1
1. Create a directory named Data on the SCCM share. The following example uses a share named
Mastershare:
\\Shareserver\Mastershare\Data
2. Download the SCCMTemplate.zip file from the Veritas Services and Operations Readiness Tools (SORT)
site (https://sort.veritas.com/utility/netbackup/deployment).
Extract the files from the .zip file and copy the files to the Data directory.
3. Copy the NetBackup client installable files for Windows to the SCCM share, as follows:
\\FileShareServer\NetBackup_8.1_Win\PC_Clnt
4. In the SCCM Assets and compliance tab, ensure the collection includes all the servers on which NetBackup
clients need to be deployed.
2
NetBackup Deployment Template User Guide for SCCM
5. Edit the \Data\masterlistfile.csv to associate master server names and client names and the master
server fingerprint and security token details, as in the following example:
The master server names and client names in the file should be fully qualified domain names (FQDNs).
The fingerprint and token details are unique to the master server. They are generated when you install the
NetBackup master server. For more information, see the NetBackup 8.1 Installation Guide or the NetBackup
8.1 Upgrade Guide.
3. Provide a name and brief description for the package, then select This package contains source files and
specify the path of the SCCM share.
3
NetBackup Deployment Template User Guide for SCCM
4. On the Program Type page, select Do not create a program, then complete the wizard.
1. In SCCM, right-click the Netbackup Client Deployment package and select Create program.
4
NetBackup Deployment Template User Guide for SCCM
2. The Create Program Wizard launches. Select Standard program as the program type.
3. On the Standard Program screen, specify the name Deploy Client and click Browse. Navigate to the
\\Shareserver\Mastershare\Data directory. Select Deployclient.ps1 and specify that the program
can run whether a user is logged on, as follows:
5
NetBackup Deployment Template User Guide for SCCM
4. On the Requirements page, select This program can run on any platform, and complete the wizard.
1. Before starting the deployment, ensure that the following prerequisites are in place:
The Masterlistfile.csv file contains the master server(s), clients, fingerprints and tokens
The NetBackup client software installation package is present in the Data on the SCCM share, as in the
following example: \\Shareserver\Mastershare\Data
The collection containing the servers is present under the SCCM Assets and compliance tab
6
NetBackup Deployment Template User Guide for SCCM
2. In SCCM Application Management > Packages, right-click NetBackup Client Deployment and select
Update Distribution Points, as follows:
7
NetBackup Deployment Template User Guide for SCCM
4. In SCCM Application Management > Packages, right-click NetBackup Client Deployment and select
Deploy, as follows:
5. The Deploy Software wizard launches. On the General page, select Browse to specify the Deploy client
software to deploy. For Collection, select the collection of servers on which NetBackup clients will be installed.
8
NetBackup Deployment Template User Guide for SCCM
6. On the Content page, click Add and select the distribution point for your collection, as follows:
9
NetBackup Deployment Template User Guide for SCCM
8. On the Scheduling page, specify when you want the deploy to run and select Always re-run program.
10
NetBackup Deployment Template User Guide for SCCM
10. On the Distribution Points page, select Download content from distribution point and run locally and
complete the wizard.
11. Clients will deploy at the schedule time. You can check the execution logs generated at the following location:
C:\Windows\ccmcache\<latest directory>\Data\<clientname>.txt
Note: You can skip the procedure to download the files if you have completed it for installing NetBackup clients.
1. Create a directory named Data on the SCCM share. The following example uses a share named
Mastershare:
\\Shareserver\Mastershare\Data
2. Download the SCCMTemplate.zip file from the Veritas Services and Operations Readiness Tools (SORT)
site (https://sort.veritas.com/utility/netbackup/deployment).
Extract the files from the .zip file and copy the files to the Data directory.
3. Copy the NetBackup client installable files for Windows to the SCCM share, as follows:
\\FileShareServer\NetBackup_8.1_Win\PC_Clnt
4. In the SCCM Assets and compliance tab, ensure the collection includes all the servers on which NetBackup
client needs to be deployed.
11
NetBackup Deployment Template User Guide for SCCM
3. The Create Package and Program Wizard launches. On the Package page, provide a name and brief
description for the package, then select This package contains source files and specify the path of the
SCCM share.
4. On the Program Type page, select Do not create a program, then complete the wizard.
12
NetBackup Deployment Template User Guide for SCCM
1. In SCCM, right-click the Netbackup Client Uninstallation package and select Create program.
2. The Create Program Wizard launches. Select Standard program as the program type.
13
NetBackup Deployment Template User Guide for SCCM
3. On the Standard Program screen, specify the name Uninstall Client and click Browse. Navigate to the
\\Shareserver\Mastershare\Data\PC_Clnt\X64 directory. Select silentuninstall.cmd and
specify that the program can run whether a user is logged on, as follows:
4. On the Requirements page, select This program can run on any platform, and complete the wizard.
14
NetBackup Deployment Template User Guide for SCCM
1. Before starting the uninstall, ensure that the following prerequisites are in place:
The NetBackup client software installation package is present in the Data on the SCCM share, as in the
following example: \\Shareserver\Mastershare\Data
The collection containing the servers is present in SCCM under the Assets and compliance tab
2. In SCCM Application Management > Packages, right-click NetBackup Client Un-installation and select
Update Distribution Points, as follows:
15
NetBackup Deployment Template User Guide for SCCM
4. In SCCM Application Management > Packages, right-click NetBackup Client Un-Installation and select
Deploy, as follows
16
NetBackup Deployment Template User Guide for SCCM
5. The Deploy Software wizard launches. On the General page, select Browse to specify the Uninstall client
software to deploy. For Collection, select the collection of servers on which NetBackup client will be installed.
6. On the Content page, click Add and select the distribution point for your collection, as follows:
17
NetBackup Deployment Template User Guide for SCCM
8. On the Scheduling page, specify when you want uninstall to run and select Always re-run program.
18
NetBackup Deployment Template User Guide for SCCM
10. On the Distribution Points page, select Download content from distribution point and run locally and
complete the wizard. Clients will uninstall at the schedule time.
19