Microsoft Windows NT 4.0 Guide Instrukcja Użytkownika Pobierz pdf (Strona 14)

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

Microsoft Windows applications can create objects (such as Events, Devices,

Semaphores, and Sections) which are used to communicate with other applications.

Each object has a name which is globally visible on the system. This can create a

problem similar to shared files. That is, two instances of an application might both

reference the same object name. They want separate objects but instead end up

sharing a single object. This can cause erratic or incorrect behavior.

To solve this problem, Terminal Server appends a colon and the logon ID to each

object that gets created. Thus, if an application runs under logon ID 4, it creates

object foo as “foo:4”. Under logon ID 7, the same application would create “foo:7”.

This prevents object collision between several running copies of an application.

Objects that are renamed are known as user global objects.

The console is treated differently. If an application that is running on the console

creates an object, nothing gets appended to the name. Using the above example,

object foo would actually be named “foo”. Objects that do not get renamed are

known as system global objects. In addition to programs explicitly run on the

console, service programs also run in the context of the console logon.

Maintaining the name of the System Global objects:

Certain classes of applications require the system global objects. For example,

Enterprise backup and defragmentation utilities often run a service on each system

in the network. An administration program can then be run on one machine in the

network. The administration program communicates with the service running on

each machine.

The service will create system global objects. The administrator program, on the

other hand, most likely runs on a client instead of the console. When it creates an

object with the same name, the object gets renamed. As a result, the service and

the administrator program actually use different objects, even though they intended

to share a single object.

If an application works correctly when run from the console and it fails when run

from a client logon, this problem may be present.

Resolution:

Keep the administrator program’s objects from being renamed. By default, all

objects are user global. There are several methods of telling Terminal Server that

an object should be system global.

The easiest method involves registering the DLL or executable that creates the

object. By default, every object created by a DLL or EXE is user global. That

default can be changed with the command “register filename /system” which marks

the file as one which creates system global objects. After this change, any object

created by this DLL/EXE will not be renamed.

OBJECTS

1 2 ... 9 10 11 12 13 14 15 16 17 18 19 ... 34 35

Brak uwag

Microsoft Windows NT 4.0 Guide Instrukcja Użytkownika Strona 14