Windows Administrative Tools PDF
Windows Administrative Tools PDF
Release 7.1
Copyright 2005 -2012 EMC Corporation. All rights reserved. Published July 2012 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. For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. Corporate Headquarters: Hopkinton, MA 01748-9103
Contents
Chapter 2: Concepts...............................................................................9
Local groups...........................................................................................................10 User rights..............................................................................................................10 Auditing..................................................................................................................11
Contents
Chapter 4: Troubleshooting..................................................................41
EMC E-Lab Interoperability Navigator..............................................................42 VNX user customized documentation...............................................................42 EMC Training and Professional Services...........................................................42
Glossary..................................................................................................43 Index.......................................................................................................45
Preface
As part of an effort to improve and enhance the performance and capabilities of its product lines, EMC periodically releases revisions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC representative.
Preface
Special notice conventions EMC uses the following conventions for special notices:
Note: Emphasizes content that is of exceptional importance or interest but does not relate to personal injury or business/data loss.
Identifies content that warns of potential business or data loss. Indicates a hazardous situation which, if not avoided, could result in minor or moderate injury. Indicates a hazardous situation which, if not avoided, could result in death or serious injury. Indicates a hazardous situation which, if not avoided, will result in death or serious injury.
Where to get help EMC support, product, and licensing information can be obtained as follows: Product information For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Online Support website (registration required) at http://Support.EMC.com. Troubleshooting Go to the EMC Online Support website. After logging in, locate the applicable Support by Product page. Technical support For technical support and service requests, go to EMC Customer Service on the EMC Online Support website. After logging in, locate the applicable Support by Product page, and choose either Live Chat or Create a service request. To open a service request through EMC Online Support, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.
Note: Do not request a specific support representative unless one has already been assigned to your particular system problem.
Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send your opinion of this document to:
[email protected]
1 Introduction
The EMC VNX supports the Common Internet File System (CIFS) protocol that allows Windows clients to access files stored on the VNX. After you configure the VNX to support Windows clients on the network, use Windows tools to perform a variety of administrative tasks on the Data Mover. The Configuring and Managing CIFS on VNX provides more information about how to configure the VNX for CIFS support. This document is part of the VNX documentation set and is intended for system administrators responsible for implementing the VNX in their Windows network or for adding Windows clients to their existing UNIX network. Topics included are:
Introduction
System requirements
Table 1 on page 8 describes the EMC VNX software, hardware, network, and storage configurations.
Table 1. System requirements Software Hardware Network Storage VNX version 7.0. No specific hardware requirements. No specific network requirements. No specific storage requirements.
Related information
Specific information related to the features and functionality described in this document are included in:
Configuring and Managing CIFS on VNX EMC VNX Command Line Interface Reference for File Managing a Multiprotocol Environment on VNX Using International Character Sets on VNX for File Using Wizards to Configure VNX for File Configuring VNX User Mapping Using NTMigrate with VNX VNX for File man pages
EMC VNX documentation on the EMC Online Support website The complete set of EMC VNX series customer publications is available on the EMC Online Support website. To search for technical documentation, go to http://Support.EMC.com. After logging in to the website, click the VNX Support by Product page to locate information for the specific feature required.
VNX wizards Unisphere software provides wizards for performing setup and configuration tasks. The Unisphere online help provides more details on the wizards.
2 Concepts
Concepts
Local groups
When a new CIFS service is created on a Data Mover and it becomes a domain member, there are no local groups resident on the Data Mover. After you create a CIFS service on a Data Mover and add the CIFS server to the domain, use Windows Computer Management MMC to create and manage local groups on the CIFS server. A local group is granted permissions and rights from its own computer to only those resources on its own computer on which the group resides. In the Windows Server native domain, local groups can contain user accounts, global groups, and domain local groups, but not other local groups. VNX supports all types of Microsoft Windows Server user groups and nested groups. VNX also supports local user accounts if they are set up. Configuring and Managing CIFS on VNX provides more information about local groups. In a Windows domain, local groups can contain user accounts and global groups, but not other local groups. VNX supports all types of Windows users groups. Windows online help provides more information on creating and managing local groups.
User rights
You can use user rights assignments to manage which users and groups can log in to or execute tasks on a Data Mover. User rights assignments are local policies that apply only to the selected Data Mover. Local groups, individual users, and global groups can be assigned privileges to:
Access this computer from the network Back up files and directories Bypass traverse checking (improves performance) Perform EMC Virus Checking Generate security audits Increase quotas Log in as a batch job Log in as a service Log in locally Manage auditing and security log Restore files and directories Set security audit (users with this privilege can manage audits on the server) Take ownership of files or object (all administrators have this capability)
10
Concepts
Note: This capability is not supported for Data Movers in the current release.
To set user rights for individual users and global groups on a Data Mover, use the VNX Data Mover Security Management Console, which is an MMC snap-in to the Unisphere. Installing Management Applications on VNX for File provides information about installing the Unisphere. The VNX Data Mover Security Management snap-in online help provides information about setting user rights.
Note: You cannot use Microsoft Windows Local Policy Setting tools to manage user rights assignments on a Data Mover because in Windows Servers, these tools do not support managing user rights on a remote computer.
Auditing
To audit CIFS servers on a Data Mover, use the VNX Data Mover Security Management Console, which is a MMC snap-in to the Unisphere. By default, auditing is disabled for all Windows object classes. To enable auditing, you must explicitly turn it on for specific events on specific Data Movers. After it is enabled, auditing is initiated whenever the CIFS service on the relevant Data Mover is started, and terminated whenever the CIFS service is stopped. Installing Management Applications on VNX for File contains information about installing the Unisphere. The VNX Data Mover Security Management snap-in online help provides information on setting audit policies. If the Group Policy Object (GPO) is configured and enabled on the Data Mover, then the GPO configuration of the audit settings is used. Configuring and Managing CIFS on VNX provides more information about configuring audit settings. The log files (security.evt, application.evt, and system.evt) are typically stored in the root file system, which has a maximum capacity of 128 MB. If you expect to retain large Event Viewer logs, you should select a different directory for storing these log files. To do so, edit the Registry residing on the Data Mover.
If you do not have experience editing the Registry, seek assistance.
You can use the Windows Event Viewer to audit Data Movers for certain events and activities. Many of the event types available for monitoring and auditing on a Windows Server can be audited on a Data Mover. Auditing is available on the object classes and events listed in Table 2 on page 12. Only members of the Administrators local group can set auditing on a server.
Auditing
11
Concepts
Windows/UNIX mapping (user/domain combina- Failure tion not found) Password authentication error returned by domain controller (DC) DC returned a nonprocessed error code No reply from DC (insufficient resources or bad protocol) Success and Failure
Object Open:
File and directory access, if system access control list (SACL) is set, for read, write, delete, execute, set permissions, and take ownership Security Access Manager (SAM) local group modification
Close Handle:
File and directory access (if SACL set) for read, write, delete, execute, set permissions, and take ownership
Object Open for Delete: File and directory access (if SACL set) Delete Object: File and directory access (if SACL set) Process tracking System restart/shutdown Not supported Restart:
N/A Success
CIFS service startup (includes DART release number) CIFS service shutdown Audit log cleared
12
Concepts
Table 2. Auditing object classes (continued) Object class Security policies Event Session Privileges:
Policy Change: List policy categories and associated audit state Use of user rights User and group management Not supported
N/A Success
Create local group Delete local group Add member to local group Remove member from local group
When auditing is enabled, the Event Viewer creates a Security log with the default settings shown in Table 3 on page 13.
Table 3. Default log settings Log type Security Windows filename C:\security.evt Maximum file size 512 KB Retention 10 days
Note: Before you can modify these values, you must complete the procedure in Change log file size on page 33.
All Windows network users can establish auditing on directories or files they own, or to which they have read, write, and execute rights. The VNX supports auditing on individual folders and files.
Auditing
13
Concepts
14
Open Computer Management MMC on page 16 Create local groups on a CIFS server using MMC on page 17 Assign user rights using Unisphere on page 21 Create shares and set ACLs using MMC on page 24 Monitor Data Mover connections and resource usage using MMC on page 25 Audit CIFS users and objects using Unisphere on page 29 Disable auditing on page 37 Connect the MMC to a CIFS server on page 38
15
4. In the Computer panel, right-click the Data Mover to manage, and then select Manage from the shortcut menu.
As an alternative: Click Start, and then select Programs Administrative Tools Computer Management. The Computer Management window opens. To connect to a Data Mover, click Computer Management (local), and then select Connect to another computer. Type the name of the Data Mover, and then click OK.
16
1. Open the Computer Management MMC for the Data Mover on which you want to create a local group. Open Computer Management MMC on page 16 provides instructions. 2. Under System Tools, double-click Local Users and Groups.
3. Right-click Groups, then select New Group from the shortcut menu.
17
4. In the New Group dialog box, click Add. 5. The Select Users, Computers, or Groups dialog box appears. Click Advanced.
6. A new screen with a Common Queries tab opens. Click Find Now to search for users or groups. Names appear in the Search results window.
18
7. Select the users or groups. Click OK to add users or groups to the new group.
8. The Select Users, Computers, or Groups dialog box appears with the object names displayed.
19
9. Click OK. 10. The New Group dialog box opens and your selection appears in the Members window. Type a group name and description in the fields provided. Click Create and Close. The new group is created.
20
3. If a Data Mover name appears after Data Mover Management, go to step 4. Otherwise: a. Right-click Data Mover Management, and then select Connect to Data Mover from the shortcut menu. b. In the Select Data Mover dialog box, select a Data Mover by using one of the following methods:
In the Look in list, select the domain in which the Data Mover that you want to manage is located, and then select the Data Mover from the list. In the Name field, type the computer name, IP address, or the NetBIOS name of the Data Mover.
4. Double-click Data Mover Management, and then double-click Data Mover Security Settings. 5. Select User Rights Assignment. The assignable rights appear in the right panel.
21
6. Double-click a user right to assign it to a particular group or user. 7. To add a group to a User Rights assignment, right-click User Rights Policy from the list in the right panel. Click Security. From the Security Policy Setting window, click Add.
22
8. Select users or groups from the window. Click Add and then click OK.
9. The users appear in the Security Policy Setting window. Click OK. The Current setting of the Celerra Management window displays the group added.
The Data Mover Security Management snap-in online help provides more information on setting rights.
23
Have assigned UNIX UIDs and GIDs to CIFS users. Configuring and Managing CIFS on VNX and Configuring VNX User Mapping provide instructions for assigning UIDs. Have mounted the file system and created directories that you want to share. Be a member of the local Administrators group on a Data Mover.
Procedure Use the MMC to create shares and set ACLs on shares after you create a CIFS server on a Data Mover, join it to the domain, and start the CIFS service.
Note: Shares created through Windows administrative tools are accessible only 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 VNX server_export command and omit the option netbios=<netbiosName>.
This procedure creates a share on a Data Mover for Windows Server: 1. Open the Computer Management MMC for the Data Mover. Open Computer Management MMC on page 16 provides instructions. 2. In the console tree, click Shared Folders Shares.
The current shares in use appear on the right. 3. Right-click Shares, and then select New File Share from the shortcut menu. The Create Shared Folder dialog box appears. 4. Provide:
24
The name of the folder to share. Type 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. The VNX supports only ASCII share names. Share name length is limited to 12 ASCII characters unless Unicode support is enabled, in which case the limit is 80 multibyte characters. Share names cannot include the following characters: /, \, %, ", NUL (Null character), STX (start of header), SOT (start of text), and LF (line feed). Share names can contain spaces and other nonalphanumeric characters, but must be enclosed by quotes if spaces are used. Share names cannot begin with a - (hyphen). Share names are case-sentitive. A share description.
5. Click Next. You are prompted for share permissions. 6. For Windows Server, set permissions by selecting one of the options. With the Customize Share and Folder Permissions option, you can assign permissions to individual groups and users. 7. Click Finish.
Monitor users on the Data Mover on page 26 Monitor access to shares on the Data Mover on page 27 Monitor use of files on the Data Mover on page 28
25
3. Optionally:
To force disconnections from the CIFS server, right-click the username, and then select Close Session from the shortcut menu. To force all users to disconnect, right-click Sessions, and then select Disconnect All Sessions from the shortcut menu.
26
1. Open the Computer Management MMC for the Data Mover. Open Computer Management MMC on page 16 provides instructions. 2. In the console tree, click Shared Folders Shares. The current shares in use appear on the right.
3. Optionally, to force disconnections from a share, right-click the share name, and then select Stop Sharing from the shortcut menu.
27
3. Optionally, to close an open file, right-click the file, and then select Close Open File from the shortcut menu. To close all open files, right-click the Open Files folder, and then select Disconnect All Open Files from the shortcut menu.
28
Specify the audit policy on page 30 Set the audit log parameters on page 32 Change log file size on page 33 View the audit events on page 35
Note: Ensure that the CIFS service is running on the Data Mover.
29
If a CIFS server is selected (name appears after Data Mover Management), go to step 4. If a Data Mover is not selected: a. Right-click Data Mover Management, and then select Connect to Data Mover from the shortcut menu. b. In the Select Data Mover box, to select a Data Mover:
In the Look in list, select the domain in which the Data Mover you want to manage is located, and then select the Data Mover from the list. In the Name field, type the computer name, IP address, or the NetBIOS name of the Data Mover.
4. Double-click Data Mover Management and double-click Data Mover Security Settings. 5. Select Audit Policy. The audit policies appear in the right panel.
30
6. Right-click Audit Policy, and then select Enable Auditing from the shortcut menu. 7. Double-click an audit object in the right panel to define the audit policy for that object. The Data Mover Security Management snap-in online help provides more information on audit policy.
31
4. Normally, the Maximum log size field is locked. You cannot modify the log file size unless you complete the procedure described in Change log file size on page 33. After 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:
32
Overwrite events as needed: Specifies whether all new events are written to the log, even if the log is full. When the log is full, each new event replaces the oldest event. Overwrite events older than ( <n> ) days: Overwrites events older than the number of days specified. Use the arrows to specify the limit, or click the field to type a value. The file size specified in step 4 is not exceeded. New events will not be added if the maximum log size is reached and there are no events older than this period. Do not overwrite events: Fills the log up to the limit specified in step 4. When the log is full, no new events are written to it until you clear the log.
1. On the Windows Server system used to manage the Data Movers, start the Registry Editor as follows: a. Select Start Run. b. Type regedit.exe in the Open field. c. Click OK. The Registry Editor opens. 2. From the Registry menu, select Connect Network Registry. The Connect Network Registry dialog box appears.
Note: Depending on how the CIFS account is set up, you might receive an error message stating, "Unable to connect to all roots in the computers registry." Click OK to continue.
3. In the Computer name field, type the name of the CIFS server and click OK. The Registry Editor is updated to display the Registry information for the CIFS server.
33
4. Navigate to the following Registry key on the CIFS server: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Eventlog\ Security The settings for the Registry key appear in the right panel. 5. Right-click the File icon in the right panel, and then select Modify. The Edit String dialog box appears.
6. In the Value data field, edit the path for the log file. For example: C:\<mtpnt>\<directory_name>\security.evt where:
<mntpt>=
mount point of the file system (not the root file system) = name of the directory that contains the log file
<directory_name>
Example: C:\CIFS_FS_1\Win2KLog\security.evt
Do not change the name of the log file.
7. Click OK. 8. Close the Registry Editor. The changes take effect immediately.
34
2. Right-click the Event Viewer icon in the right panel, and then select Connect to Another Computer from the shortcut menu. The Select Computer dialog box appears.
3. Click Browse, select the name of the Data Mover to which you want to connect, and then click OK. Click OK again to close the Select Computer dialog box. 4. Click the log. The log entries appear in the right panel. 5. Double-click the log entry to view the event detail. The Sucess Audit Properties window opens.
35
36
Disable auditing
1. Log in to a Windows domain controller by 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.
If a Data Mover is already selected (name appears after Data Mover Management), go to step 4. If a Data Mover is not selected: a. Right-click Data Mover Management, and then select Connect to Data Mover from the shortcut menu. b. In the Select Data Mover dialog box, select a Data Mover by using one of the following methods:
In the Look in list, select the Domain in which the Data Mover you want to manage is located, and then select the Data Mover from the list. In the Name field, type the computer name, IP address, or the NetBIOS name of the Data Mover.
4. Double-click Data Mover Management, and then double-click Data Mover Security Settings. 5. Right-click Audit Policy, and then select Disable Auditing from the shortcut menu.
Disable auditing
37
38
2. In the MMC, right-click Computer Management (Local) and select Connect to another computer. The Select Computer dialog box appears.
3. In the Select Computer screen, select Another computer. Type the VNX CIFS server hostname in the Another Computer field and click OK.
4. Once connected, click Classic Event Viewer Global Logs to manage the CIFS server.
39
40
4 Troubleshooting
As part of an effort to continuously improve and enhance the performance and capabilities of its product lines, EMC periodically releases new versions of its hardware and software. Therefore, some functions described in this document may not be supported by all versions of the software or hardware currently in use. For the most up-to-date information on product features, refer to your product release notes. If a product does not function properly or does not function as described in this document, please contact your EMC Customer Support Representative. Topics included are:
EMC E-Lab Interoperability Navigator on page 42 VNX user customized documentation on page 42 EMC Training and Professional Services on page 42
41
Troubleshooting
42
Glossary
C CIFS server Logical 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 CIFS server process that is running on the Data Mover and presents shares on a network as well as on Microsoft Windows-based computers. Common Internet File System (CIFS) File-sharing protocol based on the Microsoft Server Message Block (SMB). It allows users to share file systems over the Internet and intranets. D Data Mover In VNX for file, a cabinet component that is running its own operating system that retrieves data from a storage device and makes it available to a network client. This is also referred to as a blade. F file system Method of cataloging and managing the files and directories on a system. N network file system (NFS) Network file system (NFS) is a network file system protocol that allows a user on a client computer to access files over a network as easily as if the network devices were attached to its local disks.
43
Glossary
Network Information Service (NIS) Distributed data lookup service that shares user and system information across a network, including usernames, passwords, home directories, groups, hostnames, IP addresses, and netgroup definitions.
44
Index
A
access rights Windows Server 21 ACLs setting for Windows Server 2003 groups 24 auditing changing log file size 33 setting log parameters 32 Windows Server specifying policy 30 Windows Server 2003 auditing 29 CIFS users on Data Mover 35 viewing audit events 35
F
files, monitoring on Data Mover for Windows Server 25
L
Windows Server setting user rights 17, 21 log file, changing sizefor Windows Server 33
M C
creating shares 24 MMC, opening 16 monitoring files on Data Mover 28 shares on Data Mover 27 shares on the Data Mover 27 Windows 2003 users on Data Mover 26 Windows Server files on Data Mover 28
D
editing Registry for Windows Server 2003 33 Windows 2003 monitoring user 26 Windows Server 2003 monitoring shares 27 disabling user auditing for Windows Server 2003 37
R
Registry, editing Windows Server 33
E
EMC E-Lab Navigator 42 Event Viewer
S
security log file, changing size for Windows Server 33 setting ACLs on shares 24
45
Index
shares (continued) Windows Server 2003 setting ACLs 24 specifying audit policy 30
T
tools Event Viewer Windows Server 2003 35 MMC 11
W
setting log parameters 32 monitoring users on the Data Mover 26 Windows Server changing log file size 33 setting user rights 21 Windows Server 2000 MMC 16 Windows Server 2003 creating 24 disabling user auditing 37 monitoring on Data Mover 27
U
Windows Server 2003 disabling 37 viewing events 35 auditing
46