Version 5.2
February 2004
Contents
Overview of Windows Administrative Tools . . . . . . . . . . . . . . . . . . . . . . . .2
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
EMC NAS Interoperability Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Windows Administration Tools Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . .5
Using Windows 2000 and Windows Server 2003 Administrative Tools . .6
Opening the Computer Management MMC . . . . . . . . . . . . . . . . . . . . .6
Creating Local Groups on a Data Mover . . . . . . . . . . . . . . . . . . . . . . .8
Assigning User Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Creating Shares and Setting ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Monitoring Data Mover Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . .15
Auditing CIFS Users and Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Using Windows NT Administrative Tools . . . . . . . . . . . . . . . . . . . . . . . . .27
Accessing Windows NT Management Interfaces for a CIFS Server 27
Creating Local Groups on a Data Mover . . . . . . . . . . . . . . . . . . . . . .31
Assigning User Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Creating Shares and Setting ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Monitoring Data Mover Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . .36
Auditing CIFS Users and Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Want to Know More? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
1 of 56
Overview of Windows Administrative Tools
The Celerra® Network Server supports the CIFS protocol that allows Microsoft
Windows clients to access files stored on the Celerra Network Server. After you
have configured the Celerra Network Server to support Windows clients on the
network, you can use Windows tools to perform a variety of administrative tasks on
the Data Mover.
Note: For information on configuring Celerra for CIFS support, refer to the Configuring
Celerra for the Windows Environment technical module.
This document is part of the Celerra Network Server documentation set and is
intended for system administrators responsible for implementing the Celerra
Network Server in their Windows network or for adding Windows clients to their
existing UNIX network.
Terminology
This section defines terms that are important to understanding the Celerra Network
Server in the Windows environment. Refer to the Celerra Network Server User
Information Glossary for a complete list of Celerra terminology.
CIFS (Common Internet File Service): A file-sharing protocol based on the
Microsoft Server Message Block (SMB). It allows users to share file systems over
the Internet and intranets. The CIFS protocol is primarily used for file sharing by
Windows platforms.
CIFS Server: A server that uses the CIFS protocol to transfer files. A Data Mover
can host many instances of a CIFS server. Each instance is referred to as a CIFS
server.
CIFS Service: A CIFS server process that runs on the Data Mover and presents
shares on a network, as well as on Windows-based computers.
Data Mover: Celerra Network Server cabinet component running its own operating
system that retrieves files from storage devices and makes the files available to a
network client.
File system: A method of cataloging and managing the files and directories on a
storage system.
NFS (Network File System): A distributed file system that provides transparent
access to remote storage system. NFS allows all systems on the network to share a
single copy of a directory.
NIS (Network Information Service): A network naming and administration system
for smaller networks. NIS lets a user with a single user identification and password
to gain access to files or applications on any host in the network. NIS is similar to
the DNS in that it converts host names to IP addresses or IP addresses to host
names but somewhat simpler and designed for a smaller network.
Task Procedure
Performing Windows 2000 and Windows Server Using Windows 2000 and Windows Server
2003 administrative tasks a CIFS server. 2003 Administrative Tools on page 6
Note: For these tasks, Windows 2000 and Windows Server 2003 are virtually identical.
Differences between the two are noted within the procedures themselves. The screens that
are documented are Windows 2000 unless otherwise noted.
Step Action
1. Log on to the Windows 2000 or Windows Server 2003 domain controller with
administrator privileges for the Data Mover.
Note: This is the default location. This may have changed when the CIFS
server was joined to the domain.
4. In the Computer panel, right-click the Data Mover you want to manage and select
Manage from the shortcut menu. The Computer Management window opens.
Note: Celerra Network Server supports all types of Windows 2000 or Windows Server 2003
user groups, as well as nested groups. However, Celerra Network Server does not support
local user accounts.
For more information about creating and managing local groups, refer to the
Windows 2000 or Windows Server 2003 online help.
To Create a Local Group
For Windows 2000 or Windows Server 2003, use this procedure to create a local
group on a Data Mover.
Step Action
1. Open the Computer Management MMC for the Data Mover on which you want to create
a local group. Refer to Opening the Computer Management MMC on page 6 for
instructions.
3. Right-click Groups and select New Group from the shortcut menu. The New Group
dialog box appears.
6. • For Windows 2000, add users or groups to the new group by selecting user or group
names and clicking Add.
• For Windows Server 2003, add users or groups to the new group by typing the name of
the user or group and clicking Add. You can also search for users or groups by clicking
Advanced and using the search fields.
7. When you are done adding group members, click OK. You return to the New Group dialog
box.
8. Click Create. The group is created and added to the Groups list.
Note: You cannot use Microsoft’s Windows Local Policy Setting tools to manage user rights
assignments on a Data Mover because in Windows 2000 and Windows Server 2003, the
Windows Local Policy Setting tools do not allow you to manage user rights on remote
computers.
Step Action
1. Log in to a Windows 2000 or Windows Server 2003 server with administrator privileges
for the Data Mover.
2. Click Start and select Programs, Administrative Tools, Celerra Management. The
Celerra Management window appears.
4. Double-click Data Mover Management, and then double-click Data Mover Security
Settings.
5. Click User Rights Assignment. The assignable rights appear in the right panel.
6. Double-click a user right to assign it to a particular group or user. Refer to the Celerra
Data Mover Security Management snap-in online help for more information on setting
rights.
Note: Shares created through Windows administrative tools are only accessible from the
NetBIOS name used by the Windows client. If you want the share to be globally accessible
by all NetBIOS names, create a share with the Celerra server_export command and
do not specify the netbios=<netbiosName> option.
Prerequisites
To create a share with MMC, you must:
◆ Have assigned UNIX UIDs and GIDs to CIFS users. Refer to Configuring CIFS
User Authentication in the Configuring Celerra for the Windows Environment
technical module.
◆ Have mounted the file system and created directories you want to share.
◆ Be a member of the local Administrators group on a Data Mover.
Step Action
1. Open the Computer Management MMC for the Data Mover on which you want to
create the share. Refer to Opening the Computer Management MMC on page 6 for
instructions.
3. Right-click Shares and select New File Share from the shortcut menu.
• For Windows 2000, the Create Shared Folder dialog box appears.
• For Windows Server 2003, the Share a Folder Wizard appears.
4. In the Create Shared Folder dialog box or Share a Folder Wizard, provide the
following information:
• The name of the folder to share. Enter the path of the folder or click Browse and
locate the folder.
• The share name for the folder. You cannot create a NetBIOS share name with the
same name as a global share.
Note: The Celerra Network Server only supports ASCII share names.
Share name length is limited to 12 bytes, unless Unicode is enabled, in
which case the limit is 255 bytes.
• A share description.
5. Click Next. The Create Shared Folder dialog box or the Share a Folder Wizard
prompts you for share permissions.
6. For both Windows 2000 and Windows Server 2003, set permissions by selecting one
of the options. The Customize Share and Folder Permissions option lets you assign
permissions to individual groups and users.
7. Click Finish.
Result: The share is created on the Data Mover.
Step Action
1. Open the Computer Management MMC for the Data Mover that you want to monitor.
Refer to Opening the Computer Management MMC on page 6 for instructions.
2. Under Shared Folders, click Sessions. The current users connected to the CIFS
Server appear on the right.
3. Optional action:
• To force disconnections from the CIFS server, right-click the username and select
Close Session from the shortcut menu.
• To force all users to disconnect, right-click Sessions and select Disconnect All
Sessions from the shortcut menu.
Step Action
1. Open the Computer Management MMC for the Data Mover that you want to monitor.
Refer to Opening the Computer Management MMC on page 6 for instructions.
2. Under Shared Folders, click Shares. The current shares in use appear on the right.
3. Optional action:
To force disconnections from a share, right-click the share name and select Stop
Sharing from the shortcut menu.
Step Action
1. Open the Computer Management MMC for the Data Mover that you want to monitor.
Refer to Opening the Computer Management MMC on page 6 for instructions.
2. Under Shared Folders, click Open Files. The current files that are in use appear on
the right.
3. Optional action:
• To close an open file, right-click the file and select Close Open File from the
shortcut menu.
• To close all open files, right-click the Open Files folder and select Disconnect All
Open Files from the shortcut menu.
Note: Check that the CIFS service is running on the Data Mover.
Note: If the group policy object (GPO) is configured and enabled on the Data Mover, then
the GPO configuration of the audit settings will be used. Refer to Managing Celerra for the
Windows Environment for more information.
Step Action
Setting the Audit
Log Parameters 1. Log in to a Windows 2000 or Windows Server 2003 server using an account that is a
member of the local Administrators group on the Data Mover.
4. Double-click Data Mover Management, and then double-click Data Mover Security
Settings.
5. Click Audit Policy. The audit policies appear in the right panel.
6. Right-click Audit Policy and select Enable Auditing from the shortcut menu.
7. Double-click an audit object in the right panel to define the audit policy for that audit
object. Refer to the Celerra Data Mover Security Management snap-in online help for
more information on setting rights.
1. Open the Computer Management MMC for the Data Mover you want to audit. Refer to
Setting the Opening the Computer Management MMC on page 6 for instructions.
Audit Log
Parameters
2. Double-click Event Viewer. The specific log files are displayed.
3. Right-click a log file and select Properties from the shortcut menu. The property sheet
for the log appears.
4. Normally, the Maximum log size field is locked. You cannot modify the log file size
unless you complete the procedure described next in Changing Log File Size on page
22.
Once you have completed the procedure, return to the Application Properties dialog
box for the log and click the arrows to increase or decrease the size of the logs.
5. In the Log size area of the dialog box, specify what happens when the maximum log
size is reached:
• Overwrite events as needed: Overwrites the earliest events in the event log once
the file size specified in Step 4 is reached.
• Overwrite events older than (<n>) days: Overwrites events older than the number
of days specified. You can use the arrows to specify the limit, or click the field to
enter a value.
The file size specified in step 4 is not exceeded. If the number of events generated
fills the file before the time limit you specify, the earliest events will be overwritten
even if they are not older than the limit.
• Do not overwrite events: Fills the log up to the limit specified in step 4. Once the
log is full, no new events are written to it until you clear the log.
Note: You must have auditing enabled on the Data Mover for these changes to take effect.
! !
CAUTION
If you do not have experience editing the Registry, seek the assistance of someone
who does before beginning this procedure.
Step Action
1. On the Windows 2000 or Windows Server 2003 system used to manage the Data
Movers, start the Registry Editor as follows:
a. Select Start, Run.
b. Enter regedit.exe in the Open field.
c. Click OK.
The Registry Editor opens.
2. • For Windows 2000, from the Registry menu, select Connect Network Registry. The
Connect Network Registry dialog box appears.
Note: Depending on how your CIFS account is setup, you might receive an error
message stating, “Unable to connect to all roots in the computer’s registry.” Click OK to
continue with the next step.
• For Windows Server 2003, from the File menu, select Connect Network Registry.
The Select Computer dialog box appears.
3. • For Windows 2000, in the Computer name field, enter the name of the CIFS server
and click OK.
• For Windows Server 2003, in the Enter the object name to select field, enter the
name of the CIFS server or click Advanced to search by name. Click OK on the
Select Computer dialog box.
The Registry Editor is updated to display the Registry information for the CIFS server.
5. Right-click the File icon in the right panel and select Modify. The Edit String dialog
box appears.
6. In the Value data field, edit the path where you want to store the log file. For example,
C:\<mtpnt>\<directory_name>\security.evt
Where:
<mntpt> = mount point of the file system (must not be the root file system).
Example: CIFS_FS_1
<directory_name> = name of the directory.
Example: Win2KLog
! !
CAUTION
Do not change the name of the log file.
7. Click OK.
8. Close the Registry Editor. The changes you have made take effect immediately.
1. Click Start and select Programs, Administrative Tools, Event Viewer. The Event
Setting the Audit Viewer opens.
Log Parameters
Viewing the
Audit Events
2. Right-click the Event Viewer icon in the right panel and select Connect to Another
Computer from the shortcut menu. The Select Computer dialog box appears.
3. • For Windows 2000, click Browse, and select the name of the Data Mover to which
you want to connect, and click OK.
• For Windows Server 2003, enter the name in the Enter the object name to select
field or click Advanced to search for a computer.
Click OK again to close the Select Computer dialog box.
4. Click the log you want to view. The log entries appear in the right panel.
5. Double-click the log entry to view the event detail. The Event Properties window
opens.
Disabling Auditing
For Windows 2000 or Windows Server 2003, use this procedure to disable auditing.
Note: If the group policy object (GPO) is configured and enabled on the Data Mover, then
the GPO configuration of the audit settings will be used. Refer to Managing Celerra for the
Windows Environment for more information.
Step Action
1. Log in to a Windows 2000 or Windows Server 2003 domain controller using an account
that is a member of the local Administrators group on the Data Mover.
2. Click Start and select Programs, Administrative Tools, Celerra Management. The
Celerra Management window appears.
4. Double-click Data Mover Management, and then double-click Data Mover Security
Settings.
5. Right-click Audit Policy and select Disable Auditing from the shortcut menu.
Step Action
2. Click Start and select Programs, Administrative Tools, User Manager for Domains.
The User Manager window appears.
3. On the User menu, select Select Domain. The Select Domain window appears.
4. In the Domain field, enter the UNC name of the Data Mover’s CIFS server (for
example, \\DM101) or the CIFS server’s IP address, and then click OK. The User
Manager windows displays the default groups for the CIFS server.
Step Action
2. Click Start and select Programs, Administrative Tools, Server Manager. The Server
Manager window appears, displaying a list of servers in the domain.
Note: If you want to access the server manager as someone else or from another
domain, the username or group should be added to that Data Mover’s Administrator’s
local group using User Manager for domains.
Step Action
1. Click Start and select Programs, Administrative Tools, Event Viewer. The Event
Viewer window for the server you are using appears.
2. Select the Select Computer option from the Log menu. The Select Computer window
appears.
3. In the Computer field, enter the UNC name of the Data Mover’s CIFS server (for
example, \\DM101) or the CIFS server’s IP address, and then click OK. The User
Manager windows displays the default groups for this Data Mover.
Note: You cannot use User Manager to create local users on the Celerra Network Server.
Note: Celerra Network Server supports all types of Windows NT users and groups.
For more information about creating and managing local groups, refer to the
Windows NT online help.
To Create a Local Group
For Windows NT, use the following procedure to add a local group to a Data Mover.
Step Action
1. Open User Manager for the CIFS server you want to manage. Refer to Accessing User
Manager for Domains on page 27 for instructions on opening User Manager.
2. From the User menu, select New Local Group.... The New Local Group window
appears.
3. Enter the name of the local group in the Name field. Optionally, enter a description in the
Description field.
4. Click Add... to add the users to the local group. The Add Users and Groups window
appears.
5. Click the down arrow in the List Names From field to display the list of domains.
6. Select a domain. The Names field displays the list of users and global groups in this
domain.
7. Select the users or global groups you want to add to the local group and click Add. As
you add names, they are displayed in the Add Names field.
If you want to add only certain individuals from a global group do the following:
a. Select the global group.
b. Click Members. The Global Group Membership window that lists all members of
this group appears.
c. Select the users you want to add to the local group, and click Add. The users are
added to the local group, and their names are displayed in the Add Names field in
the Add Users and Groups window.
8. When you have finished adding users and global groups to the local groups, click OK.
The users and groups you have added appear in the Members field of the New Local
Group window.
Note: This capability is not supported for Data Movers in the current release
Step Action
1. Open User Manager for the CIFS server you want to manage. Refer to Accessing User
Manager for Domains on page 27 for instructions on opening User Manager.
2. From the Policies menu, select User Rights. The User Rights Policy window
appears.
3. Select the access right you want to assign to the local group by clicking the down arrow
in the Right: field. For example, to assign the right to take ownership of files to the local
group, click the down arrow to select Take ownership of files or other objects.
Note: Click Show Advanced User Rights to display all possible user rights.
5. Click the down arrow in the List Names From: field and select the UNC name of the
Data Mover’s CIFS service (for example, \\DM101). The list of groups with accounts
on the Data Mover are displayed in the Names: field.
6. Select the local group name and click Add. The local group you selected appears in
the Add Names field.
7. Click OK. The local group appears in the Grant To: field of the User Rights Policy
window.
8. Repeat steps 3 through 7 for each access right you want to grant to the local group.
9. When you have assigned all desired rights to the local group, click OK in the User
Rights Policy window.
Note: Shares created through Windows administrative tools are only accessible from the
NetBIOS name used by the Windows client. If you want the share to be globally accessible
by all NetBIOS names, create a share with the Celerra server_export command and
do not specify the netbios=<netbiosName> option.
Prerequisites
To create shares with Server Manager, you must:
◆ Have assigned UNIX UIDs and GIDs to CIFS users and groups. Refer to
Configuring CIFS User Authentication in the Configuring Celerra for a Windows
Environment technical module.
◆ Have mounted the file system and created directories you want to share.
◆ Be the Administrator—or another user that is a member of the Administrators
local group on a Data Mover—for the domain to which the Data Mover belongs.
If you want to use the NT Server Manager as someone else or from another
domain, the username or group should be added to that Data Mover’s
Administrator’s local group using User Manager for Domains.
Step Action
1. Open Server Manager for the CIFS server you want to manage. Refer to Accessing
Server Manager for Domains on page 28 for instructions on opening Server Manager.
2. Select a CIFS server and then select Shared Directories from the Computer menu.
The Shared Directories window appears, displaying a list of shares on the Data
Mover.
Note: The Celerra Network Server only supports ASCII share names.
Share name length is limited to 12 bytes, unless Unicode is enabled, in
which case the limit is 255 bytes.
5. Enter the local pathname of the share in the Path: field. The local pathname is the path
on the local machine. For example, to create the share \News under the \Events
directory on the C: drive, enter C:\Events\News.
Note: You must create and mount the \Events\News directory on the Data Mover
prior to executing this step.
7. To set ACLs on the share, click Permissions. The Access Through Share
Permissions window appears, displaying the default permissions for this share.
9. When you have completed the assignment of ACLs, click OK to return to the New
Share window.
Note: For CIFS users, the ACLs you create override the base ACLs that may exist on
the file system.
Step Action
1. Open Server Manager for the CIFS server you want to monitor. Refer to Accessing
Server Manager for Domains on page 28 for instructions on opening Server Manager.
2. From the Computer menu, select Properties. The Properties for ... window appears,
where the system name appears in the dialog box name.
3. Click Users. The Users Session on ... window appears, displaying the users with
sessions on the Data Mover and the network resources (such as shares) that are
available.
4. To force disconnections from the Data Mover, select the username and click
Disconnect or Disconnect All.
Step Action
1. Open Server Manager for the CIFS server you want to monitor. Refer to Accessing
Server Manager for Domains on page 28 for instructions on opening Server Manager.
2. From the Computer menu, select Properties. The Properties for ... window appears,
where the system name appears in the dialog box name.
3. Click Shares. The Shared Resources on ... window appears, displaying all active
network resources (such as shares) available on the Data Mover, the number of users
of the resource, and the path to the resource.
5. To force disconnections from the resource, select the username and click Disconnect
or Disconnect All.
Step Action
1. Open Server Manager for the CIFS server you want to monitor. Refer to Accessing
Server Manager for Domains on page 28 for instructions on opening Server Manager.
2. From the Computer menu, select Properties.... The Properties for ... window
appears, where the system name appears in the dialog box name.
3. Click In Use. The Open Resources on ... window appears, listing users who are
accessing resources (such as shares) on the Data Mover.
4. To force disconnections from the resource, select the username and click Close
Resource or Close All Resources.
Note: Only members of the Administrators local group can set auditing on a server.
1. You must complete the procedure in Changing Log File Size on page 44 before you can modify
this value.
Note: Check that the CIFS service is running on the Data Mover.
Note: To enable auditing on the Celerra Network Server, you must be an Administrator or a
Specifying the
Auditing Policy member of the Administrator local group on the Data Mover.
3. By default, the Do Not Audit option is selected. To enable auditing, select Audit These
Events. When you do so, the list of audited events becomes active.
4. For each supported object class that you want to audit, select Success or Failure.
Refer to Table 3 on page 41 for a list of supported object classes.
5. Click OK.
6. Repeat steps 1 through 5 for each CIFS server that you want to audit.
3. In the Change Settings for field, click the down arrow to select the log you want to
modify.
4. Normally, the Maximum Log Size field is locked. You cannot modify the log file size
unless you complete the procedure described in Changing Log File Size, which follows.
Once you have completed the procedure, return to the Event Log Settings dialog box
and click the arrows to increase or decrease the size of the log.
5. In the Event Log Wrapping area of the dialog box, specify the log wrapping setting:
• Overwrite Events as Needed: Overwrites the earliest events in the event log once
the file size specified in Step 4 is reached.
• Overwrite Events Older than (<n>) Days: Overwrites events older than the
number of days specified. You can use the arrows to specify the limit, or click the
field to enter a value.
The file size specified in Step 4 is not exceeded. If the number of events generated
fills the file before the time limit you specify, the earliest events will be overwritten
even if they are not older than the limit.
• Do Not Overwrite Events: Fills the log up to the limit specified in step 4. Once the
log is full, no new events are written to it until you clear the log.
7. Repeat steps 2 through 6 for each log file you want to modify.
Note: If you receive an autorefresh warning message when updating the registry, click OK
to continue.
! !
CAUTION
If you do not have experience editing the Windows NT Registry, seek the assistance
of someone who does before beginning this procedure.
Step Action
1. On the Windows NT system used to manage the Data Movers, select Run from the
Start menu.
3. From the Registry menu, select the Select Computer option. The Select Computer
dialog box appears.
4. In the Computer Name field, enter the NetBIOS name of the Data Mover and click OK.
The Registry Editor is updated to display the Registry information for the Data Mover.
6. Right-click the File icon. The Edit File Value window displays the absolute path for the
security log file (C:\security.evt by default) in the File field.
7. In the File field, edit the path where you want to store the log file. For example,
C:\<mntpt>\<directory_name>\security.evt,
Where:
<mntpt> = mount point of the file system (must not be the root file system).
Example: CIFS_FS_1
<directory_name> = name of the directory.
Example: WinNTlogs
! !
CAUTION
Do not change the name of the log file.
8. Click OK.
9. Select Exit from the Registry menu to exit the editor. The changes you have made
take effect immediately.
Viewing the
Audit Events
Step Action
1. Open User Manager for the CIFS server you want to manage. Refer to Accessing User
Manager for Domains on page 27 for instructions on opening User Manager.
2. In the User Manager for Domains window, select Audit from the Policies menu. The
Audit Policy window appears.
4. Repeat steps 1 through 3 for each CIFS server that you want to audit.
Step Action
1. Ensure that auditing has been enabled on the share in which the file or folder you want
to audit resides. Refer to Enabling User Auditing on page 42 for details on how to
enable auditing on a Celerra-resident share.
2. Click Start and select Programs, Windows NT Explorer. The Windows NT Exploring
window appears.
3. In the All Folders panel, navigate to the folder or file you want to audit.
4. Right-click the folder or file you want to audit and select Properties from the shortcut
menu. The Properties window for this folder or file appears.
8. You can audit activity on this directory or file by local group or by individual user, as
follows:
To audit activity by local group:
1. Select the local group you want to audit.
2. Click Add. The local group is added to the Add Names: box.
3. Repeat steps 1 and 2 for each local group you want to audit.
4. When you have added all local groups you want to audit, click OK to return to the
Directory Auditing window.
9. Once you have added the local groups and users you want to audit, you must select
the events to audit.
To select events to audit:
1. Select the events for the folder or file that you want to audit in the File Auditing
window. You can select Read, Write, Execute, Delete, Change Permissions, or
Take Ownership, and you can choose to audit Success or Failure for each.
2. Click OK. The File Auditing window closes.
3. Click OK in the Properties window to apply the changes and close the window.
A L
access rights limitations, Windows NT administrative tools 31
Windows 2000 10 local groups
Windows NT 33 Windows 2000
ACLs setting creating on Data Mover 8
for Windows 2000 groups 12 setting user rights 10
for Windows NT groups 34 Windows NT
auditing creating on Data Mover 31
Windows 2000 setting user rights 33
auditing 25 log file, changing size
changing log file size 22 for Windows 2000 22
CIFS users on Data Mover 18–25 for Windows NT 44
enabling 18
setting log parameters 20 M
specifying policy 19 MMC, opening 6
viewing audit events 24 monitoring
Windows NT Windows 2000
CIFS users on Data Mover 39–46 files on Data Mover 16
disabling 47 shares on Data Mover 16
enabling 42 users on Data Mover 15
enabling for folder or file 48 Windows NT
setting log parameters 43 shares on Data Mover 38
specifying policy 42 users on Data Mover 37
viewing events 46
R
D Registry, editing
Data Mover Windows 2000 22
creating local groups Windows NT 44
for Windows 2000 8
for Windows NT 31
editing Registry S
for Windows 2000 22 security log file,changing size
editing registry for Windows 2000 22
for Windows NT 44 for Windows NT 44
Windows 2000 Server Manager for Domains 28
monitoring files 16 shares
monitoring shares 16 Windows 2000
monitoring users 15 creating 12
Windows NT monitoring on Data Mover 16
monitoring shares 38 setting ACLs 12
monitoring users 37 Windows NT
disabling creating 34
user auditing for Windows 2000 25 monitoring on Data Mover 38
user auditing for Windows NT 47 setting ACLs 34
E T
enabling tools
auditing for folder or file for Windows NT 48 Event Viewer
user auditing Windows 2000 24
for Windows 2000 18 Windows NT 29
for Windows NT 42 MMC 6
Event Viewer Server Manager for Domains 28
Windows 2000 24 User Manager for Domains 27
Windows NT 29
W
Windows 2000
changing log file size 22
creating
local groups on the Data Mover 8
shares 12
disabling user auditing 25
enabling user auditing 18
MMC 6
monitoring
files on the Data Mover 16
shares on the Data Mover 16
users on the Data Mover 15
setting
ACLs on shares 12
log parameters 20
user rights 10
specifying audit policy 19
Windows 2003 3, 6
Windows NT
administrative tools, limitations 31
auditing a file or folder 48
changing log file size 44
creating
local groups on the Data Mover 31
shares 34
disabling user auditing 47
enabling user auditing 42
Event Viewer 29, 39
monitoring
shares on the Data Mover 38
users on the Data Mover 37
Server Manager for Domains 28
setting
ACLs 34
audit log parameters 43
user rights 33
specifying audit policy 42
User Manager for Domains 27
viewing audit events 46
Windows XP 3
EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR
WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.