Technical data
JSC 36381 MARCH 30, 2000
Baseline
4-9
or bat) may be uplinked and placed in the File Server Stage Folder (C:\Stage). The
UnpackNT application will then automatically run the uplinked files.
4.12 Virus Scanning
SSC provides Norton AntiVirus scanning software to accomplish virus scanning on
client and server systems. The program will be loaded upon start-up and will run
continuously in the background. The program will be set to examine all disk drives
continuously also. Periodic updates to the virus signature file will be performed by
ground controllers.
4.13 User Profiles and System Policies
A user profile consists of user-specific information contained in the file USER.DAT,
which is one of the two files in the Windows 95 Registry. Optionally, a user profile can
also contain special Windows 95 directories. The benefits of using user profiles are
summarized in this section.
“Roaming” users can log on to the network from any workstation and work with the
same desktop settings as long as the computer is running a Windows 95 32-bit,
protected-mode network client. Roving profiles will be used for crewmembers. The
profile will be maintained on the server in the crewmembers home directory and will
allow crewmembers to roam to any SSC Client, excluding the ECS/OCA workstation,
the MEC, or any other non-SSC client.
Whether profiles are stored locally or on the network, user profiles should be enabled
only for the computers where they will be used. Either system policies or mandatory
user profiles can be used to enforce user settings, but not both. The two methods differ
in the following ways:
• System policies let you mandate user-specific and computer-specific settings.
Mandatory user profiles let you mandate only user-specific settings.
• System policies let you selectively determine a subset of user settings to control,
and each user controls the remaining settings. Mandatory user profiles always
control every user-specific setting.
4.14 Trust Relationships
A trust relationship allows users that are authenticated in another NT domain to access
the OPS LAN NT domain. Likewise, a trust relationship might be established to permit
OPS LAN users to access other onboard NT domains. Currently, it is not possible to
establish trust relationships between the SSC domain (“opslan”) and the MCC, as a true
network connection does not exist. When OCA Router arrives onboard, a peer-to-peer
network communication will exist between the MCC and the OPS LAN. This
relationship reduces network protocol overhead caused by trust security, which often
prevents application communication across the TDRS link delay,