Go to Creating Pseudo-Drives
  Go to Adding or Replacing a Workstation

Defining User Logons

From the viewpoint of the Export-It application the requirements for a user logon under a terminal service, or other multiple logon scenario, must be the same as if the user were running on a separate machine.  In other words, the user logon must be viewed as defining a “virtualized PC” which will run the application just as would a physical computer.

The specific requirements for each user logon are as follows:

Every user must be a "local" administrator

Fundamentally, every user must have a "locale" in Australia, use Australian date format, have "Full" file access permissions to the application drives ("Database" and "Platform"), have "Full" Registry access privileges to the application keys in the HKEY_LOCAL_MACHINE hive of their Registry and have "Full" file access permissions to their "Windows" directory.  For more details refer to these topics:

See also:

Basic User Settings

File Access Permissions

User Security Privileges

User Registry Access

Custom Group for Users

 

Every user must "see" the same “Database "server" Drive”

The “Database "server" Drive” letter of every user must refer to the same physical location.  For a user that logs on to the machine where it is physically located this should not be a "network" drive [see prior topic for reasons], but for a user on a different machine it must be a "network" drive mapping.  Refer to the following topics for more details:

See also:

Database "server" Drive

Database "server" Folder

Creating Pseudo-Drives

 

Every user must "see" a “Platform "local" Drive”

Each user must have a “Platform "local" Drive” letter where the modules, libraries and resources needed to execute the application can be found.  This can be the same drive for most user logons (since the files it contains are the same for all non-SEDI users), but it must be a different location for the user logon that can act to provide Secure EDI [SEDI] communications (since that user has unique communications requirements not shared by other users).  The following topics provide additional details:

See also:

Platform "local" Drive

Platform "local" Folder

Creating Pseudo-Drives

 

Each user should have a unique “User "Windows" Folder”

The “User "Windows" Foldermust be a unique location for every user, but it need not be their "real" Windows® directory.  Syscob recommends that each user logon define a "user" (not "system") environment variable named “windir” whose value is the path to this private “User "Windows" Folder” location.  This will override the "real" Windows® directory (whose path is the "system" environment variable “windir” value) for that user.  This should be unique for each user because it contains files that hold user-specific settings and spooled printing.

 

There is no limit—excepting the performance of the computer— in respect to how many Export-It user logons may run on any single computer.  But each user logon should be setup as described above.

Notes