Introduction to Advanced Server for UNIX Compatibility
Product Manual U7613-J-Z815-6-76
© Siemens Nixdorf Informationssysteme AG 1995 Pfad: D:\O7613e6\u7613e.k02
2.7.6 LAN Manager/X V2.2
Advanced Server for UNIX since V3.5 is compatible with LAN Manager/X V2.2 as regards
the following:
●Advanced Server for UNIX supports the full functionality of LAN Manager/X V2.2.
●Interoperability is possible both with LAN Manager V2.x systems and with LAN
Manager V2.0 and V2.2 clients under MS-DOS, OS/2, Windows 3.1, and Windows 3.11
(Windows for Workgroups).
●The environment variable $xLMX and the lmx command are still available.
Important changes to Version 2.2
Advanced Server for UNIX has the following new or modified features and functions :
New and modified commands or procedures are explained in compar ative tables
with comments in Appendix A of the manual “Concepts and Planning”. Please refer
to the tables for these descriptions.
●Like a Windows NT server, Advanced Server for UNIX can take on the server role of
primary domain controller in a domain.
●The server roles of “member server” and “standalone server” have been omitted. In an
upgrade, the member server is given the role of “backup domain controller ” and the
standalone server is given the role of “primary domain controll er”.
●The share level security concept is no longer supported. In the upgrade installation, the
server is given the server role of primary domain controller with the user level security
concept.
●Modified processing and defaults for ac cess permissions
●The environment variable $xASX exists in parallel to the environment variable $x LMX.
The new command asx (e.g. asx start) corresponds to the lmx command, which can still
be used.
●The Replicator service is no longer started automatically.
●Trust relationships can be set up between domains. These facilitate the use of
resources in other domains.
●Global and local groups as well as global and local user accounts are supported.
●Customizable user environments: A specific user environment is recorded by means
of defining a user profile or by allocating a logon script regardless of whi ch client the
user logs on from.
i