LFNAlias Version 1.0

User Guide
Installing LFNAlias Version 1.0
Installing LFNAlias Version 1.0 is just as easy as installing any other software. But, because more than just one setup package may be made available for LFNAlias, the process may appear more complicated than it actually is. This page will help to clarify potentially confusing terms and issues.

Installation Types
All LFNAlias setup packages permit three types of installation. These three installation types being:
1.  Per user installations
2.  Per machine installations
3.  Administrative installations

Per User Installations
A per user installation is the default installation type of all LFNAlias Version 1.0 setup Packages. It installs, patches or update software on per user account basis. That is, on a NT-based (e.g. Windows 2000, XP, Vista, Windows 7, or later) system with the user accounts Jane and John, if the software is installed under Jane's user account, the software will be installed for exclusive use by Jane, and John will not be able to use the software unless he also installs the software under his user account.
In contrast to per machine installations, per user installations can be performed under any user account with adequate privileges to install (and uninstall) software. Although this is applies to the default user privileges of most NT-based operating systems, recent and current versions of Windows with User Account Control (UAC) (i.e. Windows Vista, Windows 7, Windows 10, and later) may require elevated privileges to install LFNAlias. Nonetheless, a per user installation is recommended for most users.
Because per user installations are the default installation type, they do not need to be explicitly selected or specified on the command line, even when performed under an account with administrator privileges.
 
Per Machine Installations
Unlike per user installations, a per machine installation (automatically) makes the (installed) software available under all user accounts on a particular computer, including local user accounts that are created after the software has been installed. Unfortunately, the downside of a per machine installation is that it has to be performed under an administrator account. In other words: Elevating the privileges to administrator, either prior to installation or on-demand, under a guest, user, power user, etc. account, does not suffice to perform a per machine instalation. Under newer Windows versions, particularly those with User Account Control (UAC), this may involve creating and/or modifying user accounts.
Furthermore, for technical reasons, a per machine installation may also require removing remnants of the (installed) software manually, both from the file system and/or the registry, when the software is uninstalled.
A per machine installation can be selected in the repsective dialog of the executable component, named the SST Setup Launcher (which click here to see) of the LFNAlias Version 1.0 web, disk, and self-extracting packages. If a dialog of this nature is not displayed, your system and/or the account under which the installaiton is being performed, does not fulfill the criteria for a per machine installation and a per machine installation should not to be attempted.
 
Administrative Installations
Administrative installations are essentially only a form of pseudo-installation, in that they do not install the software for direct use by individual users under their own user account(s). Instead, they provide a single installation source for numerous users, commonly, but not necessarily, located on a network server. Users with access to this local or network location can then install the software on their own computers from the source created by the administrative installation.
Because the target folder of the administrative installation is comparatively easy to administer and this installation type permits an end-user installation of the software in which most of the software's files can remain in the central installation repository ("run from source"), this type of installation is recommended primarily for medium to large LANs or WANs. As it requires experience in managing access rights and user accounts, it is less suited for smaller networks without a permanently accessible server and stand-alone computers.
Administrative installations are invoked by specifying "-a" or "/a" (without the quotation marks) on the command line.
 
Mixing Different Installation Types
While it is perfectly OK to mix a per machine or a per user installation with an administrative installation, it is not recommended to mix per user with per machine installations, as this may lead to unpredictable results when the software is uninstalled.

Click to expand or collapse Installing LFNAlias Version 1.0 by Means of the Microsoft Installer Package

Click to expand or collapse Installation by Means of the LFNAlias Version 1.0 Web Setup Package

Click to expand or collapse Installation by Means of the Self-Extracting LFNAlias Setup Package

Click to expand or collapse Installation by Means of the LFNAlias Version 1.0 Disk Setup Package


Topic Hierarchy: LFNAlias  •  Support  •  User Guide  •  Table of Contents  •  Installation  •  Installing LFNAlias Version 1.0
 
See Also: Installation, Installation Types, The SST Setup Launcher, System Prerequisites, Folders and Files Created During Installation, Links Created During Installation, File Extension Associations, Registry Entries.  


Document/Contents version 1.00
Page/URI last updated on 05.01.2024
 
Copyright © Stoelzel Software Technologie (SST) 2019 - 2024
Suggestions and comments mail to:
webmaster@stoelzelsoftwaretech.com