Microsoft Windows NT 4.0 Guide Manual de usuario descargar pdf (Pagina 10)

Application Compatibility Scripts for Windows NT Server, Terminal Server Edition 6

The files and directories an application uses can also cause problems. Primarily,

the issue is with applications that use public locations for per-user files. Here are

the issues:

Incorrect Pathname for per-user data:

An application may use the same pathname for a file that contains per-user data. In

the best case, if one user updates this file, it affects all other users. More severe

problems include preventing multiple users from running the application

simultaneously and corruption of the file, which could cause the application to fail for

all users.

It’s important to note that most files don’t contain per-user data and are safe to

share. Some files could be classified either way, depending on the system

administrator’s preference. For instance, document template files could be made

read-only and safely shared. Or, users could have their own set of template files

that they can update as desired.

Resolution:

This is perhaps the most difficult configuration issue to resolve. The solution is to

update the pathnames of per-user files so these files reside in each user’s home

directory. There are three issues. First, you may not immediately know there is a

problem. Second, it is difficult to detect which files need to be made per-user.

Third, it isn’t always obvious where to change the pathname.

When you find that a problem exists, you often become aware of the conflicting file

too. If you have difficulty finding the shared file, you can turn file auditing on. It is

most helpful to audit successful writes to files.

♦ After finding the name of the offending file, you must determine where that path

is stored. . Applications can store the pathname of per-user files in a

configuration file or it can be hard coded within the application. The pathname

can also be stored in HKEY_LOCAL_MACHINE and

HKEY_CURRENT_USERS.

The first step is to use regedt32 to search HKEY_LOCAL_MACHINE and

HKEY_CURRENT_USERS for the file in question. Typically, applications store

their values in the “Software” sub-tree. If you don’t find anything, you might also

want to check the product documentation. Sometimes the default path is hard-

coded in the program, but registry settings can be added to override the default.

The second step is to check the Options or Preferences dialog in the application. It

may provide a way for you to change the path. If so, you should then determine if

the settings are stored in a configuration file. File auditing can tell you if any files

get updated after you make the change in the program. The idea is to determine

the configuration file so it can be propagated to other users. The technique for this

can vary since the configuration file may contain other information that is specific to

each user.

FILES

1 2 ... 5 6 7 8 9 10 11 12 13 14 15 ... 34 35

Sin comentarios

Microsoft Windows NT 4.0 Guide Manual de usuario Pagina 10