IMG Home PageIMG ProductsProduct DownloadsOrdering InformationTechnical Support and Frequently Asked QuestionsDeveloper's Corner and UtilitiesAbout IMG
CustomersIMG ResellersMedia InformationIMG Events / Trade ShowsUseful LinksIMG Contact InformationIMG Information / Policies
Translate

Advanced Notes for Logon Utilities (Large Keyboard Dialog - Windows 2000/XP)

The My-T-Pen Logon Utilities provide the basic functionality of the standard Windows 2000 / XP logon. Because its underlying design is different, the following section outlines exactly how the implementation was designed, providing advanced users and system administrators information that may allow a different approach or setup to resolve any incompatibilities.

User Shell Activation

This is the most critical aspect of the My-T-Pen Logon Utility, and extreme care and detailed testing steps were taken to ensure compatibility with existing systems. There are 6 main areas that the Logon Utility addresses, with notes & details listed.

  1. Logon User

  2. Environment

  3. Activate User Profile

  4. USERINIT

  5. Logon Scripts

  6. Network Logon

Logon User

The Windows API LogonUser is used to establish a valid user under the Domain, Name & Password. If successful, the returned user security token is used to create the User's Shell.

Environment

To emulate the standard Windows logon, 3 Environment variables are added:

HOMEDRIVE

HOMEPATH

LOGONSERVER

The HOMEDRIVE entry is established as the 2 character drive returned from the GetSystemDirectory - Note: a system directory as the root may cause this entry to be invalid.

The HOMEPATH is attempted as \USERS\DEFAULT, then \USERS, then \ (root) as per specification.

The LOGONSERVER is obtained from the LookupAccountName Windows API.

Activate User Profile

The User Profile is loaded via Windows API calls.

USERINIT

The USERINIT entries are established via the CreateProcessAsUser Windows API call with the established Environment. The entry is tokenized via delimiters, and each entry is processed.

Logon Script processing

The script entry is obtained via the Windows API, and is processed as tokens with CreateProcessAsUser. The GetSystemDirectory is appended with *\REPL\IMPORT\SCRIPTS\" to find the script. If the script entry contains a '.' character, then it is processed directly. Otherwise, a FindFirstFile is used with a *.*" to identify a file name to process.

Network Logon

The logon script provided via MprLogonScript supported by WinLogon is processed via tokens using the CreateProcessAsUser API.


IMG Home PageIMG ProductsProduct DownloadsOrdering InformationTechnical Support and Frequently Asked QuestionsDeveloper's Corner and UtilitiesAbout IMG
CustomersIMG ResellersMedia InformationIMG Events / Trade ShowsUseful LinksIMG Contact InformationIMG Information / Policies