To enable SMBv2, all five protocol RPMs must be installed in a single command. Administrators who attempt to install the protocol files individually will experience installation errors due to rpm dependencies. Administrators must download and install these protocol files using the included instructions. To reduce the impact to users, administrators should consider scheduling a maintenance window to complete this procedure as services are restarted. Before you begin, download the following files: - PROTOCOL-SmbTailProtocol-.rpm - PROTOCOL-OracleDatabaseListener-.rpm - PROTOCOL-WindowsDHCPProtocol-.rpm - PROTOCOL-WindowsExchangeProtocol-.rpm - PROTOCOL-WindowsIISProtocol-.rpm WARNING: As a Deploy Full Configuration will temporarily interrupt event and flow collection while services are restarted on all hosts in the deployment. A web server restart will expire the session token, which will log off all users and interrupt reports in progress. Administrators can advise users to manually start reports that are interrupted by a web server restart. For 7.2.x Consoles: 1. Using SCP or WinSCP, copy the protocol rpm files to the Console. 2. Using SSH, log in to the Console as the root user. 3. To install the five protocol rpms, type: yum install -y PROTOCOL-SmbTailProtocol-7.2-20180123081341.noarch.rpm PROTOCOL-OracleDatabaseListener-7.2-20171212142247.noarch.rpm PROTOCOL-WindowsDHCPProtocol-7.2-20171212142247.noarch.rpm PROTOCOL-WindowsExchangeProtocol-7.2-20171212142247.noarch.rpm PROTOCOL-WindowsIISProtocol-7.2-20171212142247.noarch.rpm 4. From the Admin tab, select Advanced > Deploy Full Configuration. 5. From the Admin tab, select Advanced > Web Server Restart. For 7.3.x Consoles: 1. Using SCP or WinSCP, copy the protocol rpm files to the Console. 2. Using SSH, log in to the Console as the root user. 3. To install the five protocol rpms, type: yum install -y PROTOCOL-SmbTailProtocol-7.3-20171212193657.noarch.rpm PROTOCOL-OracleDatabaseListener-7.3-20171212192242.noarch.rpm PROTOCOL-WindowsDHCPProtocol-7.3-20171212192242.noarch.rpm PROTOCOL-WindowsExchangeProtocol-7.3-20171212192242.noarch.rpm PROTOCOL-WindowsIISProtocol-7.3-20171212192242.noarch.rpm 4. From the Admin tab, select Advanced > Deploy Full Configuration. 5. From the Admin tab, select Advanced > Web Server Restart.