Adding Users in XPE Terminal

Adding Users in XPE Terminal


Summary

This Technote describes how to add local users in XPE. It also describes the concerns of keeping the local and domain users profile in the flash

Audience

1st Level Support, Systems Engineering Group

Affected Products

All XPE Terminals

Issues

There are two issues that need to be considered when adding local user to the XPE terminal namely Write Filter and NetxClean.

Effect of Write Filter on Local User
We need to either disable or flush write filter cache after the local user is created. Otherwise the user account will be gone on next reboot.

Effect of NetxClean on Local User
This utility cleans up and save the flash from being filled up with temp/junk files. It deletes all the user profiles except for Administrator and User at user logoff. It also deletes some unnecessary files in those two profiles and cleans up ramdrive. Hence if you want to keep the changes of the user settings for the new local users then you need to change the configuration file Netxclean.ini as described in procedure below. Otherwise every time you logoff all the changes in your profile will be wiped away.

If the terminal joins a Windows/Active Directory Domain then domain user’s profile will also be created in the flash. If write filter is enabled the profile will be created from scratch every time the user logs in. This increases the wear and tear of the flash memory but keeps the system clean. On the other hand NetxClean does not have any effect on the domain users’ profile. Hence you need to add few lines manually in the Netxclean.ini if you need to clean up user profiles with Write filter disabled.

Procedure/Solution

The Following steps should be followed for creating a local user in XPE Models.

  1. Login as Administrator.
  2. Run lusrmgr.msc from Start->Run Command.
  3. It will open the Local User/Group Console.
  4. Create new users here.
  5. Disable and then enable Write Filter again. This will make the changes permanent. In case of SP2 builds you can flush the write filter instead.

Now you need to decide whether to allow the changes in the profile of the local users or not. If you want to keep the changes then follow these additional steps:

  1. Login as Administrator.
  2. Make changes in C:\Windows\system32\Netxclean.ini and add the following line in Profiles section
    P3=user1
    P4=user2
    ..
    ..
  3. Disable and then enable Write Filter again. This will make the changes permanent. In case of SP2 builds you can flush the write filter instead.

In a domain scenario if you want to delete the user’s profile every time the user logs off then you need to make changes in C:\Windows\system32\Netxclean.ini and add one entry each for every profile in Directories section. Also add a section named for these entries to define the actual directory of the profile.


An example for an entry for domain user Julie is as follows
[Directories]
.
.
P9=Julie
.
.
[julie] Path=C:\Documents and Settings\julie\
Action=DIR_EMPTY
ActionTrigger=USER_LOGOFF | SVC_STARTUP

An example of Netxclean.ini with setting for keeping local user profile for user Anirban:
[Parameters]
;CleanProfiles accepts the following values
; 1 = True, clean the profiles except for those listed in the Profiles Section ; when the action trigger is reached
; 0 = False, do not clean any profiles whether listed below or not. CleanProfiles=1
;SaveDynamicProfiles refers to the number of dynamic profiles to save. The defaul ; number is 1.
SaveDynamicProfiles=1
;ActionTrigger
These are the events that cause the action to be triggered.
More than one of these can be used simultaneously, just put them
all on the same line, separated by a vertical bar "|".
For example: ActionTrigger=ON_POLLTIMER | USR_LOGOFF
SVC_STARTUP - when the service is started
USER_LOGOFF - when the user logs off the system; Actions with this trigger
; are also performed when the system is shutdown.
; ON_SHUTDOWN - when the shutdown procedure is called
;Actions
Only one of these can be used at a time
For files
FILE_DELETE – Delete the file(s) matching the filename. Wild-chars can be used
; in defining the filename.
; For directories
DIR_DELETE – Delete the directory and its contents.
DIR_EMPTY - Delete all of the files in the specified directory, but not the
; directory itself.
[Profiles]
;This is the list of profiles to not cleanup. There are also defaults defined by
Netier that the user cannot override.
NOTE: If the ActionTrigger can happen while a user is logged in,
that user©s profile is NOT skipped.
P1=Administrator
P2=User
P3=anirban
ActionTrigger=USER_LOGOFF | SVC_STARTUP | ON_SHUTDOWN
.
.
.
.
.
.
.
.
.


An example of Nextxclean.ini with settings for deleting the domain user Juli’s profile is as follows:
[Directories] ;This is the list of directories to cleanup. Further definition of the directory ; is done in the directory section
P1=TempDir
P2=AdminHist
P3=AdminDocuments
P4=UserHist
P5=UserDocuments
P6=Security
P7=DriverBackups
P8=RamDrive
P9=julie
[DontDeleteDirs]
;This is the list of directories to not cleanup, even if they are a child of a
directory listed to be emptied or removed. These directories and any children
are not touched.
D1=C:\Windows\security\Database
D2=C:\Windows\security\logs
[Files] ;This is the list of files to cleanup. Further definition of each file is done ; in the filename section.
F1=FileName1
;F2=FileName2
[Applications]
A1=Wfacss
A2=ArchiveInfo
[TempDir]
Path=C:\Windows\Temp Action=DIR_EMPTY
ActionTrigger=USER_LOGOFF | SVC_STARTUP
[AdminHist]
Path=C:\Documents and Settings\Administrator\Local Settings\History Action=DIR_EMPTY
ActionTrigger=USER_LOGOFF | SVC_STARTUP
[AdminDocuments]
Path=C:\Documents and Settings\Administrator\Recent Action=DIR_EMPTY
ActionTrigger=USER_LOGOFF | SVC_STARTUP
[UserHist]
Path=C:\Documents and Settings\User\Local Settings\History Action=DIR_EMPTY
ActionTrigger=USER_LOGOFF | SVC_STARTUP
[UserDocuments]
Path=C:\Documents and Settings\User\Recent Action=DIR_EMPTY ActionTrigger=USER_LOGOFF | SVC_STARTUP
[Security]
Path=C:\Windows\security Action=DIR_EMPTY
ActionTrigger=USER_LOGOFF | SVC_STARTUP
[DriverBackups]
Path=C:\Windows\system32\ReinstallBackups Action=DIR_EMPTY ActionTrigger=USER_LOGOFF | SVC_STARTUP
[RamDrive]
Path=Z:\ Action=DIR_EMPTY
ActionTrigger=USER_LOGOFF | SVC_STARTUP
[julie]
Path=C:\Documents and Settings\julie\ Action=DIR_EMPTY ActionTrigger=USER_LOGOFF | SVC_STARTUP .





Article ID: SLN293903

Last Date Modified: 06/08/2018 08:06 AM


Rate this article

Accurate
Useful
Easy to understand
Was this article helpful?
Yes No
Send us feedback
Comments cannot contain these special characters: <>()\
Sorry, our feedback system is currently down. Please try again later.

Thank you for your feedback.