Personal Edition Documentation

Personal Edition documentation

How to use SetUserFTA

SetUserFTA allows you to configure file type and protocol associations for the current Windows user.

Edition: Personal Edition 1.8.3 Context: Current user Platform: Windows Licensed Edition 2.x documentation →

Basic usage

Set a file type association

The basic syntax is:

SetUserFTA.exe <extension> <ProgID>

For example, to associate PDF files with Adobe Acrobat Reader:

SetUserFTA.exe .pdf AcroExch.Document.DC
Current user only

The association is applied only to the user running SetUserFTA.

Optional targeting

Set an association for members of a group

You can optionally specify an Active Directory group:

SetUserFTA.exe .pdf AcroExch.Document.DC "Adobe Acrobat Users"

The association is only applied if the current user is a member of the specified group.

Multiple associations

Configure multiple associations

For multiple file types and protocols, use a configuration file:

SetUserFTA.exe SetUserFTAconfig.txt

Example SetUserFTAconfig.txt

.pdf, AcroExch.Document.DC
.txt, Applications\notepad++.exe
mailto, Outlook.URL.mailto.15

A group can optionally be added as the third value:

.pdf, AcroExch.Document.DC, GRP_Adobe_Reader

Each association must be placed on a separate line, and values are separated by commas.

Discover associations

Find the correct ProgID

The easiest way is to configure the desired default application manually in Windows and then run:

SetUserFTA.exe get

This displays the current user’s protected file type and protocol associations and their ProgIDs.

You can also create a configuration file directly:

SetUserFTA.exe get > SetUserFTAconfig.txt

Reset

Delete an association

To remove a user-specific association:

SetUserFTA.exe del .pdf

Administration

Deployment

SetUserFTA can be deployed using a user logon script, Group Policy, scheduled task, software deployment solution, Citrix WEM, or a similar user-environment management solution.

Run in the user’s context

SetUserFTA must run in the user’s context, not as SYSTEM or Administrator, and should run after the user’s profile has been loaded.