UpSlide is fully compatible with SCCM Deployment. The following pages describe, in detail, how UpSlide should be deployed via SCCM.
UpSlide will only function if these two Prerequisites are found on the machine:
- .NET Framework 4.5.2 and above: https://www.microsoft.com/en-us/download/details.aspx?id=42642
- Please note that .NET Framework is now integrated into Windows 10, you may not need to deploy it.
- Visual Studio Tools for Office Runtime 2010: https://www.microsoft.com/en-us/download/details.aspx?id=48217
If you already have deployed those prerequisites previously, you can go ahead and start UpSlide Packaging.
Please click on the links below to display the procedure
1- .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 : https://www.microsoft.com/en-us/download/details.aspx?id=42642
Once downloaded, open the Configuration Manager Console:
Next, go to Applications and select Create Application.
On the General page of the Create Application Wizard, select Manually specify the application information, then click Next.
Specify general information about the Application such as name and version.
On the Application Catalog page, enter Application details such as name and language and click Next:
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.
On the General page of the Create Deployment Type Wizard, select Manually configure the deployment type information.
On the General Information page, enter deployment details such as the name and comments, and click Next.
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)
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”.
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
Click Next and leave Requirements and Dependencies pages with default settings. Close the Deployment Type Creation wizard.
On Application Creation Wizard under Deployment Types page select the newly created deployment type and click Next.
Close the Application Creation Wizard. You can now push your Application to the Distribution Point.
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: https://www.microsoft.com/en-us/download/details.aspx?id=48217
Once downloaded, open the Configuration Manager Console and create a new Application.
On the General page of the Create Application Wizard, select Manually specify the application information, and click Next.
Specify general information about the Application such as name and version and click Next.
On the Application Catalog page, enter applications details such as name and language and click Next.
On the Deployment Types page of the Create Application Wizard, click Add to create a new deployment type, the Create Deployment Type Wizard will open and on the General page of the Create Deployment Type Wizard please select Manually configure the deployment type information:
On the General Information page, enter Deployment details such as the name and comments, and click Next:
On the Content Page, fill in these two fields:
- Content Location: Path to VSTO Install File (1),
- Installation Program: {VSTO Install Filename}.exe /q /norestart (2).
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 10.0.60301)
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 10.0.60301)
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.
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.
Finish the Deployment Type Wizard, on Application Creation Wizard under Deployment Types page select the newly created deployment type and click on Next then finish the wizard. You can now push your Application to the Distribution Point.
3- UpSlide Packaging
This part consists of creating an UpSlide Application in SCCM and making the Prerequisites install with UpSlide if they are not detected on the computer.
Open the Configuration Manager Console.
Next, go to Applications and select Create Application.
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.
Click on Next, default parameters should be loaded automatically.
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. As of May 2014, support languages are: en-US, fr-FR.
- /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.
- "CheckProcesses=0" to allow UpSlide to install while Office processes are running (Excel, PowerPoint or Word).
- "PathToConfigFolder=CustomPath" to have UpSlide look for the customization in a custom folder. For example, put the content of the Config folder (found in UpSlide installation folder by default) in I:\UpSlide\Config and add "PathToConfigFolder=I:\UpSlide" to the installation command. Note that the installer will not automatically populate the selected config folder; this must be done manually.
- "AllUserInstallFolder=CustomPath" to specify a custom location for installation.
Example for Silent Install and Reactivation Service:
- msiexec /i "UpSlide.msi" /q EXEOPTIONS ="-q2 ""DeployReactivationService=1""".
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.
Edit the properties of the Deployment type associated with UpSlide Application.
- Right Click on Deployment Type -> Properties -> Detection Methods.
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\UpSlide\Binaries,
- File name: Finance3point1.UpSlide.Engine.dll,
- Select This file setting must exist on the target system to indicate presence of this application
The 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.
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.
Click on OK. The UpSlide package is now successfully configured and ready to be pushed to users.