V6 Client Deployment Preparation Check List

Transcription

1 V6 Client Deployment Preparation Check List Please ensure you read through the following install guide sections before deploying the Policy Central V6 Client; Policy Central Client Machine Folder Permissions Anti-Virus Software Exclusion Settings WAN Security (Proxy/Firewall) Policy Central Client MSi Installation Files Third Party Software Installation Pre-Requisites Policy Central Client Machine Folder Permissions When the Policy Central client is installed the following folder must have and retain Everyone (Read, Write, Edit) permissions for any login; C:\tmp Anti-Virus Software Exclusion Settings The following folders must be added to your Anti-Virus Software exclusion list; C:\Program Files\Future Digital C:\tmp C:\programdata\Future Digital NOTE : The above folder may be hidden. The following processes should also be added to your Anti-Virus Software exclusion list; C:\Program Files\Future Digital\PCEClient.exe C:\Program Files\Future Digital\PCEClient32.exe C:\Program Files\Future Digital\StartupService.exe C:\Program Files\Future Digital\PCEKey.exe C:\Program Files\Future Digital\PCEUpdater.exe C:\Program Files\Future Digital\Updater.exe

2 WAN Security (Proxy/Firewall) Confirm that the correct ports and protocols are available for the Policy Central Client & Policy Central Client Update Service. Ensure that the Proxy allows the specified executables and Java (JRE) to connect to the Internet through the correct ports and that the proxy allows connections to the correct IP/domains. Read your Proxy's documentation or contact the manufacturer to find out how to confirm these settings. Make sure that the perimeter firewall has exceptions for the Policy Central Server (if external) and any specified IP Address/Domain Name values below; PCEClient.exe and PCEClient32.exe using JAVA connect over TCP ports 80 (HTTP) and 443 (HTTPS) The default folder for these files is C:\Program Files\Future Digital PCEClient.exe and PCEClient32.exe using JAVA connect via HTTP and HTTPS to your designated Policy Central Server IP address and Domain Name PCEUpdater.exe and Updater.exe using JAVA connect over TCP ports 80 (HTTP) and 443 (HTTPS) The default folder for these files is C:\Program Files\Future Digital PCEUpdater.exe and Updater.exe using JAVA connect via HTTP to and via HTTPS to s3-eu-west-1.amazonaws.com/fsl.pceclient.package.bucket NOTE : The specified download source location URL should only need to be added if your security is currently preventing the download of any files via PORT 443 Ports and Protocols to be allowed in the proxy rules: Function Location Protocol Port General Client Communication Between clients and the Policy Central Server (IIS, SQL) & Policy Central Server Administration Console HTTP (TCP) 80 Secure General Client Communication (optional) Between clients and the Policy Central Server (IIS, SQL) & Policy Central Server Administration Console HTTPS (TCP) 443 Client Auto Update Communication Between clients and the Policy Central Auto Update Administration Service HTTP (TCP) 80 Client Auto Update Download Communication Between clients and the Policy Central Auto Update Download Service HTTPS (TCP) 443

3 Policy Central Client MSi Installation Files Combo MSi Installer For Group Policy PCEgpo62315x32.pceservername#clientid.msi PCEgpo62315x64.pceservername#clientid.msi Designed to be deployed to a computer via Group Policy with the MSi assigned as a package via the Group Policy Management Editor (Computer Configuration/Policies/Software Settings/Software Installation). Once successfully assigned via Group Policy the machine will require a restart before the V6 Client actually initiates. This installer contains the V5 Client Force Removal ol, Microsoft C redistributables (x86, x64) and latest V6 Client installer. Only the Java Version 7 Update 67 (build 1.7) minimum and Microsoft.NET Framework (or later) pre-requisites must be in place before deployment. Re-Naming The Combo MSi Installer For Group Policy Before deploying the Policy Central Client MSi installer you must first rename it correctly. The first 3 characters in the MSi name must be PCE in uppercase. After the first period (.) in the MSi name, you must specify the Policy Central Server and if applicable after a hash (#) your assigned Client ID. NOTE : All downloaded MSi files will have the correct prefix (only the version numbers will differ) so there is no requirement to change them. Central (shared/hosted) PCE Server Installations For this example the Policy Central Server URL is myschool.fslhost.org The install location (school/academy/college etc.) is Grange Hill and this site s unique Client ID is grangehill. Therefore the Combo MSi Installer For Group Policy needs renaming as follows; PCEgpo62315x32.pceservername#clientid.msi PCEgpo62315x64. pceservername#clientid.msi PCEgpo62315x32.myschool.fslhost.org#grangehill.msi PCEgpo62315x64.myschool.fslhost.org#grangehill.msi Local PCE Server Installations (No Client ID required) For this example the Policy Central Server computer name is FutureDigital Therefore the Combo MSi Installer For Group Policy needs renaming as follows; PCEgpo62315x32.pceservername#clientid.msi PCEgpo62315x64. pceservername#clientid.msi PCEgpo62315x32.FutureDigital.msi PCEgpo62315x64.FutureDigital.msi

4 Non-Silent Combo MSi For Manual Installs PCEman62315x32.pceservername#clientid.msi PCEman62315x64.pceservername#clientid.msi Designed to be deployed manually on a computer, all information regarding the installation tasks, progress, failures and restart are displayed where applicable. This combo installer contains the V5 Client Force Removal ol, Microsoft C redistributables (x86, x64) and the latest V6 Client installer. Once the V6 Client has successfully installed the machine will require a restart before the V6 Client actually initiates. Re-Naming The Non-Silent Combo MSi For Manual Installs Before deploying the Non-Silent Combo MSi installer you must first rename it correctly. The first 3 characters in the MSi name must be PCE in uppercase. After the first period (.) in the MSi name, you must specify the Policy Central Server and if applicable after a hash (#) your assigned Client ID. NOTE : All downloaded MSi files will have the correct prefix (only the version numbers will differ) so there is no requirement to change them. Central (shared/hosted) PCE Server Installations For this example the Policy Central Server URL is myschool.fslhost.org The install location (school/academy/college etc.) is Grange Hill and this site s unique Client ID is grangehill. Therefore the Non-Silent Combo MSi For Manual Installs needs renaming as follows; PCEman62315x32.pceservername#clientid.msi PCEman62315x64. pceservername#clientid.msi PCEman62315x32.myschool.fslhost.org#grangehill.msi PCEman62315x64.myschool.fslhost.org#grangehill.msi Local PCE Server Installations (No Client ID required) For this example the Policy Central Server computer name is FutureDigital Therefore the Non-Silent Combo MSi For Manual Installs needs renaming as follows; PCEman62315x32.pceservername#clientid.msi PCEman62315x64. pceservername#clientid.msi PCEman62315x32.FutureDigital.msi PCEman62315x64.FutureDigital.msi

5 V6 Client Installer MSi PCE62315x32.pceservername#clientid.msi PCE62315x64.pceservername#clientid.msi Designed to be deployed to a computer via Group Policy, with the MSi assigned as a package via the Group Policy Management Editor (Computer Configuration/Policies/Software Settings/Software Installation). Once successfully assigned via Group Policy the machine will require a restart before the V6 Client actually initiates. This installer contains the latest V6 Client only. ALL pre-requisites must be installed and PCE V5 (or older) must be removed before deployment. Re-Naming The V6 Client Installer MSi Before deploying the V6 Client Installer MSi you must first rename it correctly. The first 3 characters in the MSi name must be PCE in uppercase. After the first period (.) in the MSi name, you must specify the Policy Central Server and if applicable after a hash (#) your assigned Client ID. NOTE : All downloaded MSi files will have the correct prefix (only the version numbers will differ) so there is no requirement to change them. Central (shared/hosted) PCE Server Installations For this example the Policy Central Server URL is myschool.fslhost.org The install location (school/academy/college etc.) is Grange Hill and this site s unique Client ID is grangehill. Therefore the V6 Client Installer MSi needs renaming as follows; PCE62315x32.pceservername#clientid.msi PCE62315x64. pceservername#clientid.msi PCE62315x32.myschool.fslhost.org#grangehill.msi PCE62315x64.myschool.fslhost.org#grangehill.msi Local PCE Server Installations (No Client ID required) For this example the Policy Central Server computer name is FutureDigital Therefore the V6 Client Installer MSi needs renaming as follows; PCE62315x32.pceservername#clientid.msi PCE62315x64. pceservername#clientid.msi PCE62315x32.FutureDigital.msi PCE62315x64.FutureDigital.msi

6 Third Party Software Installation Pre-Requisites JAVA (For All V6 Client Deployments) Java Version 7 Update 67 (build 1.7) minimum must be installed on all target machines. The latest Java downloads can be found here; Microsoft's.NET Framework (For All V6 Client Deployments) Microsoft.NET Framework (or later) must be installed on all target machines. Microsoft's Visual C++ Redistributable for Visual Studio 2013 Update (For V6 Client Installer MSi Deployments ONLY. Not required if using any of the Combo installer MSi files) The Microsoft C redistributable must be installed on all target machines. NOTE : For 64bit Windows OS machines, both the x64 and x86 Visual C++ redistributables require installing.

7 Troubleshooting Section Pre-Installation 1. verify that Java is installed correctly, you can check that the following registry entry and key value exists on the target machine; HKLM\SOFTWARE\JavaSoft\Java Runtime Environment\ The value for CurrentVersion should be at least 1.7 If the client installation advise that the Java version is too old or cannot be found then please go to the following web page and re-apply the applicable Java x32 and/or Java x64 installation; If you are still receiving a message during the client installation advising that the java version is out of date (old), then it may be due to login permissions. verify this, please carry out the following; Go to start and type in cmd Right click on cmd.exe and select Run As Administrator In the command prompt window go the directory (folder) that contains the client MSi Now type in (or copy/paste) the full name of the installer MSi, then press Return. The client should install without issue. If not please contact Future Digital Support (support@futuredigital. ).

8 Post-Installation 1. Following the successful installation of the Policy Central client you discover the machine is not showing in the Policy Central Server Console. There may be server URL connection errors listed within c:\tmp\monitor.log Please carry out the following checks; A) Check that your Policy Central server is running Version If it is then continue to check B If not then please contact us (support@futuredigital. ) to arrange a Policy Central server update. B) Please download: On a machine which has the V6 client installed and is not registering on the server; Create a folder name c:\java test then place the extracted file PCEPing.class into it. Open the cmd window (start, run, cmd), then type c:\java test Please refer to your V6 Client Install MSi name and use your designated Policy Central Server name/url. For example: PCE62314x32.myschool.fslhost.org#grangehill.msi You type in java PCEPing then press <<return>> You should get back Response Code: ***, PASS (*** represents 3 digits) If the ping test fails, please contact your Network Team to ensure that JAVA initiated network connections are allowed and that your site has full unrestricted http/https access via JAVA to the Policy Central Server IP address. If you are using one of our centrally hosted PCE Servers, you or your Network Team can confirm your designated Policy Central Server IP address by contacting us at support@futuredigital. 2. If you have successfully run the Java ping test, but the client still does not appear to work please contact us at support@futuredigital. advising us of; Operating System (For example: Windows bit) Policy Central Client install MSi name in full that you used Brief details of the issue Please also ensure you zip and attach the following Policy Central client log folders; C:\tmp C:\programdata\Future Digital (This folder may be hidden so please use folder view options to acquire)