IsolatedAL: A per user isolated application launcher


IsolatedAL

Version: 2.0.22.702

Description: An Isolated Application Launcher that runs on user login, (for all users and every session, or current user and selected session), and controls which applications should launch, when they should launch, and how many instances are allowed.

Example:
  • Want Dropbox to launch for all users who log in to a server and for multiple sessions for that user (setup app, users to launch app= all, type=all).
  • Want application to launch for all users who login, but only want it to launch for the first session that user logs in on (setup app, users= all, type=first).
  • Want app to launch only for username1 or domain\username1 or machinename\username1 on their first session (setup app, users= \username1, type=first).
  • Delay launch of applications from 0-60 seconds to allow fine-control of launch timing.


Features: 
  • Fine-grain control of application launch on login to machine.
  • One installation shared on machine (Program Files install, ProgramData settings).
  • Import AutoRuns from the current machine setup (create backups during import).
  • Backup/Restore settings.
Requirements: 
  • .NET 4.8

Screenshots:











Setup application settings

Application Name: Description
Target App: Path to application
Optional Arguments: Arguments to pass to application if desired
Start in directory: Path to use as start in for application launch (blank is the app dir)
User(s) to launch application: Username filter to use to determine if application should launch for the current user logging in. (all = everyone, domain\username = domain specific, machine\username = machine specific, \username = less restrictive)
Type: Launch type of first session for user or all sessions for user.
Delay: Delay application launch for 0-60 seconds.

Import AutoRuns

This allows a user to more easily import tasks from their StartMenu autorun (All Users and Current User), and from the Registry Startup keys (All Users HKLM and specific users HKU).

It will create a backup within the application that prompts to restore the import if the entry is deleted from the application. It also creates a secondary backup in the ProgramData that can be manually added back in via the script in the same folder.

Enjoy.

Comments

Popular posts from this blog

B4SDCT: B4 Systems Design Connectivity Toolkit v4.3

Convert2Utf8: Detect and convert file encodings in batch

cTail: Large File Tailer