Unix and Windows operating systems have different and incompatible methods of specifying pathnames. EnlightenDSM supports only Unix pathnames. You can specify Windows pathnames in a Unix style by typing two forward slashes (//) before the drive designations and typing forward slashes throughout the rest of the pathname instead of back slashes. For example,

Use this Unix-compatible pathname anywhere in the GUI that requires a pathname. The pathname is automatically converted as needed by Windows agents. Pathnames from agents (for example, in disk snapshots) are displayed in Unix format.

The only exception to entering Unix-compatible pathnames occurs on Windows NT in the user administration Home Directory text field. In this field, enter a Unix directory and a Windows NT directory name, separated by a vertical bar ( | ). You can enter Unix or Windows pathnames. The target machine will use the directory filename formatted in the same style as its operating system.

Windows filenames, user names, and group names may contain spaces; however, you have to add double quotes around the name (for example, “//c/my files”). The program will automatically display filenames, user names, or group names that contain spaces with double quotation marks.

Windows pathnames are case-insensitive, which can lead to unexpected results in some operations, like compare disk snapshots.

Unix and Windows NT operating systems use different and incompatible means of managing file ownership. NT systems uses Access Control Lists (ACL) that determine what an individual user can do with particular files. Two users with complete ACL privileges for a particular file each “own” the file, since there is no information attached to the file giving one individual ultimate ownership. Unix systems mandate that every file has a single owner, though others may have access privileges.

Some of the file scanning operations, like Snapshot, work differently on NT systems. Since there is no single owner, each file will appear to be owned by User 0 and Group 0.

Also, you cannot determine if an Windows file has been renamed because they do not have inode numbers which provide information about the file (except the name) and “handles” to the Unix filesystem that disk snapshots store and use.

Directory access times are not available in Windows disk snapshots because directory access times are updated when a snapshot is traversed on Windows. Disk snapshots on Windows were changed to store the last modification time instead of the last access time, which means that you cannot determine if a disk has been scanned, but just modified since the last snapshot. The last access times of Windows files work the same as Unix files, as long as you are using NTFS partition. The FAT file system does not track access times, but only modification times for both files and directories.

Unix files have three levels of permissions that can be set independently: read, write, and execute. As mentioned previously in the section, “File Ownership,” Windows uses the ACL method and does not modify the ACL. On Windows, EnlightenDSM will only modify the owner write permission, and not change the execute or read setting

Windows supports several filesystem types, including NTFS which was developed specifically for the NT operating system.

Most Microsoft filesystems that run on Windows are case-insensitive. See the beginning of this appendix for information about how to convert Windows filenames to Unix file names.

NT does not use numeric IDs to uniquely identify users and groups. This may cause unexpected results for some operations because EnlightenDSM maps between names and numbers internally. To alleviate this problem, the program stores the provided UID number along with other information when creating an NT account. The “fake” ID is reported when the account is queried. For NT accounts not created with EnlightenDSM, a UID is created on the fly, creating a large number. This number serves as a place holder for missing information.

A similar process is used for Group ID's, but these GID numbers are not usually visible.

Login Status is not supported

The Activity Monitor activates the following:

EnlightenDSM does not recognize domains on Windows. Windows domains are not the same as Domain Name Service (DMS) domains. All user account administration by EnlightenDSM is performed on local accounts. To make changes to Windows domain accounts, you have to change the account domain controller. The account list of a Windows domain is the account list of the domain controller. Because the program does not recognize Windows domains, it is not possible to query a host to determine if it is a domain controller, or to find out the controller of a given Windows machine.

The Domain Name Servers (DNS) configuration screen provides a default pathname of /etc/named as a location for DNS files. This is correct for Unix machines, but when you configure an Windows NT machine as a DNS server, the correct path is //c/winnt/system32/dns. Because the EnlightenDSM GUI is unaware of the type of remote machine it will be talking to, it cannot provide a different default path for Windows NT targets.

Windows 95/98 machines cannot be configured as DNS servers.

Host Entries is fully supported only for DNS.

None of the Naming Services Overrides options are supported.

NIS and NIS+ is not a concept supported by Windows.

The NFS command features are not supported. NFS is not provided for Windows by Microsoft, so there is no standardized interface for administering it. Mounting and Exporting directories is not supported.

This feature is not supported.

The tape operation of retention and erase are not supported.

Raw device should be set to //a/filename when configuring a floppy device for backup.

None of the TTY Configuration options are supported, as Windows does not support controlling TTY's. All Windows processes will report the TTY as N/A. Also note that TTY Configure is only available on the host running the GUI.

Banner mode, Reconfigure, and Single-user mode shutdown options are not supported on Windows. Countdown is not supported on Windows NT.

Crontab management is not supported. NT provides a less sophisticated scheduled execution facility that is compatible with the EnlightenDSM interface. Future releases may provide an NT version of cron.

Mail aliases features are not supported. Windows does not use the Internet/sendmail model of e-mail distribution, rather it uses the Mail Application Programming Interface (MAPI) which uses the Address Books model.

Remote File Distribution status logs may be incomplete for failed jobs.

The use of pre and post install scripts on Windows is not supported.

Allowing and disallowing logins is not supported on Windows.

Events requires that the Microsoft SNMP package (included as a standard part of the Windows Workstation and Server distribution) to be installed. If this package is not loaded, all network related events will report as zero. The SNMP service daemon which is provided in the Microsoft SNMP package should not be enabled. EnlightenDSM provides its own SNMP agents, AgentENL and Agent Mon, which provide the actual SNMP service. Since the EnlightenDSM and Microsoft SNMP agents use the same SNMP network port, only one can run at a time. EnlightenDSM provides the same basic SNMP functionality as the Microsoft service, as well as enhanced DSM SNMP services.

The list of built-in events is quite different for Windows and Unix. A subset of the very large performance statistics on the Windows has been selected. The majority of these events are TCP/IP related; the other are mostly CPU and memory related. The cpu_busy event approximately corresponds to the cpu_load event on Unix, but is reported as a percentage of non-idle time rather than the an average process run queue length, as on Unix.

There are also events for the user, system and interrupt time, reported as percentages. Note that these CPU values are samples, not slow moving averages. They tend to fluctuate more quickly than the Unix load average.

On UNIX, process test names may contain arguments to check for similar processes that are started with different arguments. This information is not available on Windows, so this type of test is not supported.

Process test filenames are case-insensitive on Windows.

Although the program does not support MAPI, Events provides a limited mailer that can send e-mail from an Windows machine to Internet addresses (e.g., user @host). This utility is called smtpmail and is called by AgentMon. It only supports internet style addresses, and cannot send to other types of addresses. This mailer does not queue and so if the target host is unreachable or not listening for mail, the message is lost.

These tests are not supported.

The Host Overview Telnet feature is not supported on Windows.