FSLogix Apps 1.3 Now Available!

Posted by Randy Cook on Apr 7, 2014 8:46:00 PM

Thanks to a rigorous beta and a lot of customer feedback, the FSLogix team is pleased to announce the availability of FSLogix Apps 1.3, our third release since we came out of stealth last year at BriForum.

CLICK HERE FOR TRIALWARE 

If you're new to FSLogix, here is a list of our most implemented use cases.

  • Easily manage per-user application extensions like Office add-ins and browser plugins
  • Massively reduce the number of Windows gold images in your environment
  • Eliminate silos in your Citrix and RDS infrastructure
  • Achieve 100% success with app virtualization projects
  • Implement VDI and DaaS without legacy management overhead
  • Ensure license compliance for all users and all apps on all Windows infrastructure
  • Simplified version control and rollback on application updates
Our solution requires no repackaging or sequencing, and can also work to supplement your existing app-virt and streaming solutions from any vendor.
With the 1.3 release, we've added:
  • Per process visibility
  • Specify registry value data
  • Per user printer visibility
  • Assignment file template
  • And lot of minor enhancements to our top use cases

Before I go into detail on the new features I really want to again thank our beta participants.  We're passionate about developing solutions that work outside our lab, in your mission critical enterprise environments.  We thank you for your time, your feedback and insight, and your help to bring our concepts into highly scalable enterprise solutions.  From the entire team, Thank you.

To request an evaluation copy of 1.3 please click here.  To get news on FSLogix, including news on our next beta, please click here.

Thank you,

Randy Cook
CTO, FSLogix

 

FSLogix Apps 1.3:  New Features

Per Process Visibility

Visibility of files and registry settings can now be controlled at the application level.  Additionally, the admin can select whether or not the visibility settings also apply to child processes. 

Scenarios where this is useful include:

-        The admin wants to make access to particular data or configuration information only available through a particular application.

-        The admin wants to specify a version of a runtime that should be visible to, and therefore used by, an application.

-        Limit visibility of certain applications to particular shells, for example PowerShell.  The converse is also possible, the admin can remove visibility of certain applications from particular shells.

Specify Value Data

The admin now has the ability to specify the data that should be returned when a particular registry value is queried. This is particularly useful when the admin wishes to change a File Type Association when a particular application is hidden.  For example, when a user doesn’t see the Chrome browser, make the IE browser the default handler for .htm and .html files.

Per User Printer Visibility

The admin can now add a Rule that controls the visibility of printer objects.  The main use case for this is when a particular application installs a printer driver (e.g. Adobe) and the admin only wants users who have access to the application to be able to access the printer.

Assignment File Template

The admin can now specify the set of Rule Assignments that should be present by default when a new Assignment File is created.

Per Process Visibility

To specify the visibility of a Rule Set for a process (application), a new “Process” assignment needs to be created. From the Assignments dialog, click on “Add” and select the “Process” option.

 

Process

Enter the path to the executable and select whether or not this should apply to child processes as well.  Note that a full path is required.

Specify Value Data

To specify the data to be returned when a specific value is read, add a new Rule and select “Specify Value Rule” from the dropdown menu:

SpecifyValueData

Enter the name of the Value in the “Registry Value Name” field.  Enter the data to be returned in the Data field.  Click “OK”.

Per User Printer Visibility

To control the visibility of a printer object, a new Hiding Rule must be created.  Add a new Rule and select “Hiding Rule” from the dropdown menu:

PerUserPrinterVisibility

Type in the name of the printer, or select “Printer” from the browse menu.  Ensure that “Printer” is selected for the Object Type.

Assignment File Template

If an Assignment File Template has been created, its contents will be copied to any new Assignment files that are created. A new Assignment File Template can be created, or the existing one overwritten, by selecting the “Set As Template” button in the Assignments dialog.

AssignmentFileTemplate

Topics: VDI, DaaS, Citrix, RDS

Subscribe to Email Updates

Recent Posts

Posts by Topic

see all

Follow Me