Welcome, Guest
You have to register before you can post on our site.



Search Forums

(Advanced Search)

Forum Statistics
» Members: 101
» Latest member: Cutterdnf
» Forum threads: 79
» Forum posts: 138

Full Statistics

Online Users
There are currently 35 online users.
» 0 Member(s) | 35 Guest(s)

Latest Threads
VD image: pre-install app...
Forum: Help & Troubleshooting
Last Post: Paul Kieboom
11-10-2021, 04:41 PM
» Replies: 5
» Views: 17.517
Groups from all applicati...
Forum: Help & Troubleshooting
Last Post: Dennis
10-28-2020, 04:41 PM
» Replies: 1
» Views: 4.955
Can you convert active di...
Forum: Help & Troubleshooting
Last Post: ScenseGuru
09-27-2020, 05:34 PM
» Replies: 1
» Views: 5.436
Howto create a Language (...
Forum: Applications & Tools
Last Post: Richard
09-25-2020, 01:48 PM
» Replies: 1
» Views: 6.116
Forum: Applications & Tools
Last Post: ScenseGuru
09-10-2020, 04:34 PM
» Replies: 0
» Views: 2.893
Action: Import Registry C...
Forum: Runtime Extensions
Last Post: JVD
09-01-2020, 07:52 AM
» Replies: 2
» Views: 15.332
Does the MSI import also ...
Forum: General Discussion
Last Post: JVD
09-01-2020, 07:51 AM
» Replies: 5
» Views: 25.604
Mount VHD (with fallback)
Forum: Runtime Extensions
Last Post: ScenseGuru
11-16-2018, 02:38 AM
» Replies: 0
» Views: 6.087
Log bitlocker status
Forum: Runtime Extensions
Last Post: Michael Baars
10-07-2018, 06:23 PM
» Replies: 0
» Views: 5.111
Scense Service Point inst...
Forum: Help & Troubleshooting
Last Post: kpinsel
09-27-2018, 03:07 PM
» Replies: 2
» Views: 11.792

  Does the MSI import also get de *.msp files of that MSI?
Posted by: JVD - 08-26-2020, 04:28 PM - Forum: General Discussion - Replies (5)

On the following page:

I have read this about Adobe reader DC installers:

You might be tempted to do the extraction with 7zip, but you shouldn't. 7zip cannot see the included MSP-files, so you'll end up in most cases with an outdated MSI-file, and the MSP-file(s) required to do the update is/are missing.

The extraction must be done with a command like
AdbeRdr11002_en_US.exe -nos_oC:\AdobeFiles -nos_ne
If you do not like typing complicated commands, you can instead copy the installer.exe to an empty directory, dowload my script AcroRdr-Extract.cmd and copy it into the same directory, then double-click the script. It will detect the filename of the installer.exe in the same directory, and then issue the above command with the correct filename.

The extracted files will be saved in the newly created directory C:\AdobeFiles. It will contain one MSI-file, one file named data1.cab, plus in most cases one or more MSP-files, plus some other files like setup.exe that are not needed for deployment with GPO.

If there are MSP-files, then the included MSI-file and data1.cab are outdated, and you must apply the patches from the MSP-files to get the latest version. If you want to deploy using GPO, you must slipstream them, see below. In the example from above (version 11.0.2) you get two MSP-files: AdbeRdrUpd11001.msp and AdbeRdrSecUpd11002.msp. They must be applied one after the other, in the correct order, according to the version numbers in the filenames.

When i drag the MSI to the Scense explorer and i see all the processing, i wonder if the *.msp files are also taken in account for installation?

Print this item

Brick Software Metering report - unique users per application
Posted by: Richard - 11-04-2015, 05:14 PM - Forum: General Discussion - No Replies

Here's a new report file you might like to add to your Scense Report Viewer.
It shows the application users grouped per application, so you will know which unique users are using a specific application.

By default, the functionality for adding and removing reports to and from the database is disabled to protect the reports in the database.
This functionality can be switched on by adding a value in the registry.

You can install the report by following these steps:

  1. Create this registry key: HKEY_CURRENT_USER\Software\Scense\ReportViewer
  2. Create a new REG_DWORD in the above key: ‘AllowAddRemoveReports’ with a value of 1
  3. Open the Scense Report Viewer
  4. In the ‘File’ menu the ‘Add Report’ command has become available, click it
  5. Select the report that you have downloaded from this post and click OK
  6. Remove the registry value you just created (or set it to 0), just to make sure you're unable to unintentionally remove any reports
The procedure above has imported the report into the Scense database so it will be available for everyone using the Scense Report Viewer.
The new report can be found in the Scense Report Viewers tree-view and is named: “Application Users (unique, grouped)”.

You won't need the downloaded rpt-file any longer after you've imported it...


Attached Files
.rpt   ApplicationUsersGrouped.rpt (Size: 96 KB / Downloads: 5)
Print this item

  Post-install configuration
Posted by: Michael Baars - 09-03-2015, 09:48 AM - Forum: General Discussion - No Replies

During the install of Scense quite some settings are generated, like new accounts and data shares.

As some of these setting ensure a trouble-free usage and simple deployment, these settings might not always fit the company security best practice. Some quite simple changes in the configuration can solve this.

As it is in best interest for all to have stable installations, that are also secure I have decided to share the guideline with the community. You will find these as an PDF attachment on this post.

Feel free to give feedback! I will try to update the document in that case...

Attached Files
.pdf   Scense post install configuration v10r7.pdf (Size: 342,05 KB / Downloads: 55)
Print this item

Information How to get usage data on any application
Posted by: ScenseGuru - 07-07-2015, 12:57 PM - Forum: General Discussion - No Replies

Scense 10 lets you monitor the usage of applications. But what if you want to monitor applications that are not delivered by Scense?

By simply checking the box that says 'Enable metering for this Application' you can tell the Scense application monitor service to start monitoring the usage of the application.
This works for all applications you are delivering with Scense, but it also works for applications you're not delivering with Scense.
In this fictional scenario we would like to monitor the usage of the Windows Registry Editor (regedit.exe).
Regedit is not delivered by Scense as it is part of the operating system.

In Scense there's no application object for Regedit, so we can't enable software metering for it.
This is very easily solved by simply adding a new Generic Application Object for Regedit.
After creating the generic application we should remove the embedded Taskset because we don't want any runtime activity for this application object.
This leaves us with an empty Application shell that we can use to enable software metering.

It's probably a good idea to move this application object to a dedicated folder for application objects that are created with the sole purpose of enabling software metering (applications not delivered by Scense).

[Image: 070715_0940_howtogetusa2.png]

Now that we have the application object for Regedit we can start configuring it.
We should ignore all other pages and only configure the Metering page.

[Image: 070715_0940_howtogetusa3.png]

First we need to enable metering and specify some details about the usage context of the application.
Next, we tell software metering what program it should monitor.
We do this by clicking the 'Edit Programs' button, click Add, browse to the regedit.exe program and select it.

[Image: 070715_0940_howtogetusa4.png]

After clicking OK several times, the Scense software metering system will pick up on this new application and start monitoring it.
This can take up to 30 minutes by default. If you want to speed up things you can restart the Scense Application Metering Service.
Each usage of regedit.exe will be stored and prepared for reporting and after a while you will see the registry editor appear in your report viewer.

[Image: 070715_0940_howtogetusa5.png]

This post originally appeared on the ScenseGuru blog.

Print this item

Information Scense Client- and Update Service installers support SVCSTART property
Posted by: Richard - 06-03-2015, 09:19 AM - Forum: General Discussion - No Replies

As of Scense 10 the installers (msi) for the Scense Client and the Scense Update Service support a new public property called 'SVCSTART'.
This property controls the automatic starting of the installed services.
Using this property has some advantages:

  • Sometimes during a Scense Client upgrade the Scense Update Manager would indicate that the new Scense Client was successfully installed on a workstation where in reality it was not. This behavior was typically caused by the inability to start the Scense OnDemand service because of a logon failure, where after the installation was rolled back. With Scense 10, and thanks to the new SVCSTART property, the starting of the Scense OnDemand service is now separated from the actual installation making it much easier to troubleshoot, because the Scense Client software remains installed.
  • In unattended workstation scenarios it can be undesired that the Scense Update Service or the Scense OnDemand Service is started after it is being installed, because these installations are part of a larger unattended installation procedure which should not be disturbed by any actions the Scense services would invoke.
The services are still configured to start at computer startup, so there's no necessity for additional configuration. Everything will be as expected after a reboot.

SVCSTART=0 will leave the installed service in the stopped state.
SVCSTART=1 will start the service as part of the installation (Default).

Here's an example of how the SVCSTART property is used:
:Install Scense Client
start /B /HIGH /WAIT %windir%\system32\msiexec.exe /i "Scense Client.msi" ODSUSER="SCENSE\Scense_ODS" ODSPASS="password" SCENSESERVER="SERVER" ALLUSERS=1 REBOOT="ReallySuppress" SVCSTART=0 /q
net start Scense_ODS

Print this item

Exclamation Special notice for Live Profiles when upgrading to Scense 10
Posted by: Richard - 06-01-2015, 02:18 PM - Forum: General Discussion - No Replies

When you are about to upgrade to Scense 10 and you are already using Scense Live Profiles for roaming application settings, then please read the following carefully.
Scense 10 has a modernized 'process-to-application-mapping' (or PAM) that is shared between Live Profiles and the Software Metering subsystem.
Any existing mappings in the 'old' filter sets should be upgraded to the new PAM before the Scense Live Profiles Client is upgraded on the workstations and before any changes to Live Profiles settings are made with Scense Explorer.

The upgrade can be done with the attached tool.

The upgrade tool will first check if there are already new PAM records in the database.
If so the tool will assume that the upgrade has already taken place.
If not, the tool will enable the 'upgrade' button which will, after being clicked, convert the existing mappings to the new PAM.

The tool (Scense_SLP10.exe) must be run on a computer where Scense Explorer 10 is installed.

Attached Files
.zip   Scense_SLP10.zip (Size: 10,39 KB / Downloads: 5)
Print this item