The Scense Application Object.
The Application object holds the information used within Scense related to the installation and functioning of applications within the Scense environment. The enhanced presentation mode provides a user-friendly interface with all functionality needed to managed applications and their user-environment.
After selecting an application object, the application view is shown with information related to the application object. Two hyperlinks are available to the user to be able to edit the application properties and configuration settings related to the application object.
The information shown depends on the type of application (Scense supports Windows Installer, Generic applications, Virtual Layers and App-V):
- General information related to the application object:Runtime Status (is the application available for deployment, blocked or disabled), Is the application visible in the Scense-client and which settings relate to the application object.
- Information about the installer type like the location of the package.
- Deployment: Which users will be able to use the application.
- Information about the shortcuts used.
- Information about the File Type Associations
- Information about the steps needed to install the application.
Creating a new application object
New applications are created through the context menu (in the application-node), with File, New, Application or using the Taskpad (Create a new application). After selecting the application type (Generic, Windows Installer, Virtual Layer or App-V) a new entry in the application object list is created. By double clicking or selecting properties, the user will be able to edit the application-object.
The name of the application object. This name will be shown within Scense explorer.
The Application Link is the link between the application and everything that has to do with it and therefore has to be unique.The Application Link is used for communication with the registry, the repository and the ‘installers’.
Domain / Group
Users within this scope, will be able to access the application.
The version used for an application does not necessarily have to be the actual version of the application. The version number is used within Scense to indicate the version of the application deployment.As an administrator it is possible to use this version number to make sure an application is refreshed ‘globally’.At the moment the administrator increases the version number, the application will no longer be considered ‘installed’, for all users. Consequently, the application will have to be installed again on every workstation, when the user intends to start the application.
The user is able to link configuration settings
If the Taskset of an application generates shortcuts during the execution of the logon script, the application will be added to the application list within Scense Client.
However this only happens if you have indicated in the Application object that the application must be visible in this application list.
The administrator can specify architecture for the application. This will allow applications to be used in mixed environments of both 32-bit and 64-bit systems.
A 64-bit application can only run on a 64-bit operating system.
But a 32-bit application can run on both 64-bit and 32-bit systems.
Another type of application that potentially can run on both 64-bit and 32-bit is the .NET application. A .NET application will be compiled “just-in-time” (JIT) for the processor architecture on which it is run. So it will be a 32-bit application on a 32-bit system and a 64-bit application on a 64-bit system.
Scense allows these applications to be created once and run on both platforms.
The table below shows how to set the Architecture for different Application Types in such a way that they work on different platforms.
As pure 64-bit applications will not run on 32-bit systems, the best way of avoiding errors is to set conditions on the applications shortcuts evaluating the %OSArchitecture% variable.