McAfee MANAGEMENT EDITION 2.5, Руководство администратора

Страница: 234 / 338

Using Mirror and Linked Repositories
234 Management Edition
You can find a copy of this file (MEUPRQ32.EXE) in a subdirectory called
MEUPREQ\32 in the installation directory for the Management Console.
This file is only about 80k in size.
Doing this will cause the Management Agent on the workstation to
request an update from the server when the users logs on.
Be aware that MEUPRQ32.EXE is a 32-bit Windows application and thus
will not run in a non-Win32 environment (i.e., 16-bit Windows). A 16-bit
Update Requester (MEUPRQ16.EXE) is located in the directory
MEUPREQ\16. If you do have the same users logging on to the same
Windows NT domain on different platforms, you should detect the
platform in your login script and launch the appropriate executable.
5. You can set a number of options with the batch update method,
including the ability to let users postpone updates a specified number of
times, and the ability to specify a time before which the update should
not run.
Configuring access to NetWare mirrors
Configuring access to repositories
Certain types of NetWare user IDs must be created on the server hosting a
repository, as shown in the following table:
1. NetWare servers are only able to update from a Windows NT-based
repository via Push On installation via the Management Console.
2. A bindery context must be enabled on the server, and the specified user ID
must be within the first bindery-context container.
3. A fully qualified name must be entered, in the format
Name.Container.Organization .
Clients using the
repository
Repository locations:
NT Workstation
or Server
NetWare 3
.x
Server
NetWare 4
.x
Server
Windows only None Bindery ID Bindery ID
2
Windows,
NetWare 3
.x and/or
4 .x
None
1
Bindery ID Bindery ID
2
NetWare 3 .x only None
1
Bindery ID Bindery ID
2
NetWare 4
.x only
None
1
Bindery ID NDS ID
3