January UpSlide SCCM DEPLOYMENT. Step by step guide

Transcription

1 January 2017 UpSlide SCCM DEPLOYMENT Step by step guide

2 Table of contents 1 Introduction Prerequisites Packaging NET Framework Packaging Visual Studio Tools for Office Runtime (VSTO) UpSlide Packaging

3 1 Introduction UpSlide is fully compatible with SCCM Deployment. The following pages describe, in details, how UpSlide should be deployed via SCCM. 2 Prerequisites Packaging UpSlide will only function if these two Prerequisites are found on the machine:.net Framework 4.5.2: Visual Studio Tools for Office Runtime 2010: NET Framework Packaging For UpSlide to function,.net Framework needs to be installed. This section describes How to create the package on System Center Configuration Manager. The first step is to download the offline package of.net Framework from this link: Once downloaded, open the Configuration Manager Console: Fig. 1: Configuration Manager Console 3 23

4 Next, go to Applications and select Create Application. Fig. 2: Create a New Application On the General page of the Create Application Wizard, select Manually specify the application information, then click on Next. Fig. 3: General Page Specify general information about the Application such as Name, and Version. Fig. 4: General Information On the Application Catalog page, enter Application details such as name and language and click on Next: 4 23

5 Fig. 5: Application Catalog On the Deployment Types page of the Create Application Wizard, click on Add to create a new deployment type. The Create Deployment Type Wizard will open. Fig. 6: Add a new Deployment Type 5 23

6 On the General page of the Create Deployment Type Wizard, select Manually configure the deployment type information. Fig. 7: Create Deployment Type Wizard On the General Information page, enter deployment details such as the Name and comments, and click on Next. Fig. 8: General Information 6 23

7 On the Content Page, fill these two fields: Content Location: Path to.net Framework Install File (1) Installation Program: {.NET Install Filename}.exe /q /norestart (2) Fig. 9: Content Page Next, configure the detection methods to indicate the presence of the application with these settings: Setting type: Registry, Hive: HKEY_LOCAL_MACHINE, Key: SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full, Value: Release, Data Type: Integer, Select This Registry Settings Must Exist on the Target System to indicate presence of this Application. 7 23

8 Fig. 10: Detection Methods Parameters Validate the Detection Rule, on the User Experience screen specify these settings: Installation Behavior: Install for System, Logon Requirement: Only when a user is logged on, Installation program visibility: Normal. Fig. 11: User Experience Click on Next and leave Requirements and Dependencies pages with default settings. Close the Deployment Type Creation wizard. 8 23

9 Fig. 12: Deployment Type Successfully Created On Application Creation Wizard under Deployment Types page select the newly created deployment type and click on Next. Fig. 13: Deployment Types Close the Application Creation Wizard. You can now push your Application to the Distribution Point. 2.2 Visual Studio Tools for Office Runtime (VSTO) For UpSlide to function, Visual Studio Tools for Office Runtime needs to be installed. Please follow these steps to create the package on System Center Configuration Manager. The first step is to download the offline package of VSTO from this link: Once downloaded, open the Configuration Manager Console: Fig. 14: Configuration Manager 9 23

10 Next, go to Applications and select Create Application. Fig. 15: Create Application On the General page of the Create Application Wizard, select Manually specify the application information, and click on Next. Fig. 16: General Page 10 23

11 Specify general information about the Application such as Name, and Version and click on Next. Fig. 17: Application Information On the Application Catalog page, enter applications details such as name and language and click on Next. Fig. 18: Application Catalog 11 23

12 On the Deployment Types page of the Create Application Wizard, click Add to create a new deployment type: Fig. 19: Add a New Deployment Type The Create Deployment Type Wizard will open, on the General page of the Create Deployment Type Wizard, select Manually configure the deployment type information: Fig. 20: Create Deployment Type Wizard 12 23

13 On the General Information page, enter Deployment details such as the Name and comments, and click on Next: Fig. 21 General Information On the Content Page, fill these two fields: Content Location: Path to VSTO Install File (1), Installation Program: {VSTO Install Filename}.exe /q /norestart (2). Fig. 22: Content Page 13 23

14 On the next Screen the Detection method needs to be defined, select Add a Clause and fill with these settings: For x64 Systems: Settings Type: Registry, Hive: HKEY_LOCAL_MACHINE, Key: SOFTWARE\WOW6432Node\Microsoft\VSTO Runtime Setup\v4 Value: Version, Data Type: String, Select This Registry Settings Must Satisfy the following rule to indicate the presence of the application. Operator: Equals Value: Version of VSTO downloaded (on our case ) For x86 Systems: Settings Type: Registry, Hive: HKEY_LOCAL_MACHINE, Key: SOFTWARE\Microsoft\VSTO Runtime Setup\v4, Value: Version, Data Type: String, Select This Registry Settings Must Satisfy the following rule to indicate the presence of the application. Operator: Equals Value: Version of VSTO downloaded (on our case ) Fig. 23 VSTO Detection Clauses 14 23

15 You can keep the two clauses to ensure compatibility with x64 and x86 Clients, the condition between the two clauses needs to be changed first from AND to OR. Fig. 24: Detection Clauses Conditions Validate the Detection Rule, on the User Experience screen specify these settings: Installation Behavior: Install for System, Logon Requirement: Only when a user is logged on, Installation program visibility: Normal. Fig. 25: User Experience 15 23

16 Click on Next and close the Deployment Type Creation Wizard. Fig. 26: Deployment Type successfully created On Application Creation Wizard under Deployment Types page select the newly created deployment type and click on Next. Fig. 27: Select Deployment Type Close the Application Creation Wizard. You can now push your Application to the Distribution Point

17 3 UpSlide Packaging The last part consists in creating UpSlide Application in SCCM and make Prerequisites install with UpSlide if they are not detected on the computer. Open the Configuration Manager Console. Fig. 28: Configuration Manager Console Next, go to Applications and select Create Application. Fig. 29: Create Application 17 23

18 On the General page of the Create Application Wizard, select Automatically detect information about this application from installation files: Type: Windows Installer (*.msi file), Location: Path to UpSlide MSI Installer. Fig. 30: Create Application Wizard Click on Next, default parameters should be loaded automatically. Fig. 31: Automatic Detection from MSI File 18 23

19 On the General Information page, the next step consists in configuring UpSlide installer to run silently. Fill the Setup Software field, by default fill with: msiexec /i "UpSlide.msi" /q EXEOPTIONS="-q2". You can adjust with the UpSlide Installer Switches: -q2 to force install to be silent. "LANG=en-US" to force the UpSlide User Interface to be in English. You can of course change the UI language and replace en-us by any supported language UID. o Supported languages are: en-us, fr-fr. TsuRunMode=2 to force uninstall. /a1 to force single user install. /a4 to force all user install (setup will request an administrator password to proceed if current user does not have sufficient permissions). "KeepExistingConfig=1" to force UpSlide to install on top of any existing version. In that case, the configuration folder is not modified by a new installation. Useful when the customization should not be impacted by deployment. "DeployReactivationService=1" to deploy the reactivation service. Example for Silent Install and Reactivation Service: msiexec /i "UpSlide.msi" /q EXEOPTIONS = -q2 DeployReactivationService=1. Fig. 32: Installer Switches 19 23

20 To have the Application marked as Successfully installed by SCCM, the detection method needs to be changed first. Go back to Configuration Manager Console -> Applications -> UpSlide and go to Deployment Types. Fig. 33: Deployment Types Edit the properties of the Deployment type associated with UpSlide Application. Right Click on Deployment Type -> Properties -> Detection Methods. Fig. 34: Change Detection Method Remove the Default Detection Method which is based on the MSI Product code. And Add a new clause: Setting Type: File System, Type: File, Path: C:\ProgramData\UpSlideBinaries, File name: Finance3point1.UpSlide.Engine.dll, Select This file setting must exist on the target system to indicate presence of this application 20 23

21 Fig. 35: New Detection Method Settings Next step is to tell SCCM to install UpSlide for All Users on the computer. Go to User Experience, and on Installation Behavior select Install for System. Fig. 36: User Experience Settings 21 23

22 The last step of this guide is to add the dependencies to VSTO and.net Runtime packages configured earlier in this guide. On Dependencies Tab Add two dependencies to.net Runtime Applications and VSTO Application. Fig. 37: Dependencies Configuration Click on OK. The UpSlide package is now successfully configured and ready to be pushed to users

23 PARIS 20, Avenue de l Opéra, Paris LONDON Level 39, One Canada Square, Canary Wharf, London, E14 5AB NEW YORK 1460 Broadway, New York, NY 10036