サポートと今すぐチャット
サポートとのチャット

NetVault Plug-in for Microsoft 365 13.2 - User Guide

Installing or upgrading the plug-in

The following topic describes the process for installing the plug-in on a single client or upgrading an existing one. If you have multiple clients of the same type, you can use the NetVault Configuration Wizard to install the plug-in on multiple clients at the same time. For more information on using push installation to update multiple clients at the same time, see the Quest NetVault Administrator’s Guide.

To install or upgrade the plug-in
1
In the Navigation pane, click Manage Clients.
2
On the Manage Clients page, select the applicable client in the table, and click Manage.
3
On the View Client page, click .
4
Navigate to the location of the “.npk” installation file for the plug-in, for example, on the installation CD or the directory to which the file was downloaded from the website.
Based on the OS in use, the path for this software may vary on the installation CD.
5
Select the file entitled “not-x-x-x-x-x.npk,” where xxxxx represents the version number and platform, and click Open.
After the plug-in is successfully installed, a message is displayed.

Removing the plug-in

To remove the plug-in
1
In the Navigation pane, click Manage Clients.
2
On the Manage Clients page, select the applicable client, and click Manage.
3
In the Installed Software table on the View Client page, select the applicable plug-in, and click .
4
In the Confirm dialog box, click Remove.

Configuring the plug-in

•
Adding a certificate for configuration
•
Using the Microsoft 365 admin portal to obtain configuration details
•
Preparing SharePoint Online for backup and restore
•
Entering the configuration details in the plug-in
•
Multi-tenant support
•
Improving backup and restore performance by modifying parameters in the configuration file

Adding a certificate for configuration

Plug‑in for Microsoft 365 supports certificate-based authentication. NetVault uses certificate thumbprint to fetch the private key from the Windows Certificate Manager.

Microsoft recommends certificate-based authentication over the domain, key, and access key method. Reasons for using a certificate to authenticate include:

•
Credential rotation is prone to human error.
•
Certificates last longer than credentials (mostly more than one year).
•
Using a certificate shares responsibility with Microsoft Credential Manager (Windows OS), Certificate Authority, and Azure AD.
•
It is the highest level of security for Microsoft Graph Client.
•
It has reliable credential encryption for compliance.

Before you add the certificate to your configuration as a means for authenticating, complete the following processes.

To add a certificate for configuration
1
Creating a self-signed certificate using PowerShell
2
Adding a certificate in the Azure AD admin portal
3
Importing a self-signed certificate to the local machine certificate store
Creating a self-signed certificate using PowerShell
To create a self-signed certificate using PowerShell
1
Run the following script as an administrator:
# --- config start
$dnsName = "mytenant.sharepoint.com" # Your DNS name
$password = "Come up with something secure!" # Certificate password
$folderPath = "C:\temp" # Where do you want the files to get saved to? The folder needs to exist.
$fileName = "mycert" # What do you want to call the cert files? without the file extension
$yearsValid = 10 # Number of years until you need to renew the certificate
# --- config end
 
$certStoreLocation = "cert:\LocalMachine\My"
$expirationDate = (Get-Date).AddYears($yearsValid)
 
$certificate = New-SelfSignedCertificate -DnsName $dnsName -CertStoreLocation $certStoreLocation -NotAfter $expirationDate -KeyExportPolicy Exportable -KeySpec Signature
 
$certificatePath = $certStoreLocation + '\' + $certificate.Thumbprint
$filePath = $folderPath + '\' + $fileName
$securePassword = ConvertTo-SecureString -String $password -Force -AsPlainText
 
Export-Certificate -Cert $certificatePath -FilePath ($filePath + '.cer')
Export-PfxCertificate -Cert $certificatePath -FilePath ($filePath + '.pfx') -Password $securePassword
Adding a certificate in the Azure AD admin portal
To add a certificate in the Azure AD admin portal
1
Login to the Azure AD admin portal.
2
Go to Certificates & secrets.
3
Click Upload certificate.
4
Select the .cer file you generated with the PowerShell script, and click Add.
5
Note the thumbprint that appears. You will need it for Entering the configuration details in the plug-in.
Importing a self-signed certificate to the local machine certificate store
To import a self-signed certificate to the local machine certificate store
1
In Windows, run MMC.
2
Click File,
3
Click Add/Remove Snap-in.
4
In the Add or Remove Snap-ins window, select Certificates and then click Add.
5
When prompted, select the computer account and then click Next.
6
Select Local computer (selected by default) and then click Finish.
7
In the Add or Remove Snap-ins window, click OK.
8
In the MMC main console, expand the certificate snap-in by clicking the plus (+) symbol.
9
Navigate to the Personal | Certificates pane.
10
Open the Certificate Import Wizard by right-clicking within the Certificates panel and clicking All Tasks | Import.
11
To import the private key alone with a password, follow the Certificate Import Wizard.
 
* 
NOTE: For SharePoint Online backup and restore, the private key should reside in the Personal folder with certificates managed on the local computer.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択