Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn more about our patch management solution.

 

Home > Success Center > DameWare Remote Support & Mini Remote Control > DameWare Remote Support User Guide > Remote system tasks and views > Users view

Users view

Created by Anthony.Rinaldi, last modified by Anthony.Rinaldi on Jul 12, 2016

Views: 9 Votes: 0 Revisions: 2

The DameWare Remote Support Users view allows administrators to create and manage users on remote systems, along with multi-select copy, delete, and rename functions. The following sections describe related groups of user functions in this view.

View and Organize Users

Use the Users view to view and organize users, including:

  • View Microsoft Exchange and Windows Terminal Server User properties.

  • Copy users to remote systems and domains.

  • Drag and drop users to add to or removing from groups.

When you use the Copy User option, you may select to set the password to the same as the UserID, leave the password blank, or specify a new password.

Create and Edit Users

Use the Users view to create or edit users on remote systems. If you choose to create multiple users at the same time, the User Properties window provides the following configurable options:

  • Name and password schema(s)

  • Group membership

  • User profile information including logon script names and home directory options

  • Hours during the day that the user(s) is/are allowed logon access

  • Remote Access Administration options including call back and dial in permissions

  • Account expiration and account type

  • Workstation log in privileges

The User Properties Window

The User Properties window consists of the following tabbed dialogs.

  • User: Manage user property information like name, comments and password here. This is also where password expiration and account-disabled properties can be set. The password Age and password Last Changed date are displayed in the lower right hand portion of this dialog.

  • Group: User group membership and primary group properties can be set.

  • Profile*: User profile paths, login script and home directory properties can be set in this option. Terminal Server Home Directory properties can also be set here.

  • Configuration*: User options for Windows Terminal Server

  • Dialin: User dial in privileges are set in this option as well as call back options.

*Only available server(s) running Windows Terminal Server.

Supported macros

  • %USERNAME%

  • %USERFULLNAME%

When adding multiple new users you can specify ANSI or UNIX sprintf functions for format specifications. For example, change TestUser%d to TestUser%03d to create user accounts such as TestUser001, TestUser002, and so on.

Creating users' home directories

The following examples illustrate how to create users' home directories using macros. Drive E: serves as the hypothetical destination for the home directory on the user's system.

  • Map E: to \\server\users\%USERNAME% if the folder 'r;users' already exists on the server and is shared.

  • Map E: to \\server\c$\%USERNAME% to create the folder to the c:\root drive on the server, such as c:\jdoe.

  • Map E: to \\server\c$\users\%USERNAME% to create the folder on the server's c: drive, as in c:\users\jdoe. This also assumes the folder 'r;users' already exists.

Manage User Policies

Use the Users view to manage user account security settings, such as Account Policy, User Rights, and Audit Policy. To modify these settings, select a user from the Users list, and then click the corresponding button on the Users view mini toolbar.

Additional Information

The following is a brief summary of the Windows Vista/2008/Windows7 Security policies.

Account Policy

The Account Policy controls how passwords must be used by all user accounts. It defines things such as the maximum password age, minimum password age, minimum password length, whether a password history is maintained and whether users must log on before changing their passwords. It also determines lockouts. If locking out is enabled, then a user account cannot log on after a number of failed attempts to log on to that account within a specified time limit between failed attempts. Lockout can also occur from attempting to change the password using an incorrect password for the old password. A locked account remains locked until an administrator unlocks it or a specified amount of time passes. The Account Policy also determines whether or not a remote user is forcibly disconnected from a domain when that user's logon hours expire.

Failed password attempts against workstations or member servers that have been locked using Ctrl+Alt+Delete or password protected screen savers, do not count against account lockout settings entered in User Manager for Domains.

User Rights Policy

The User Rights Policy manages the rights granted to groups and user accounts. A right authorizes a user to perform certain actions on the system. A user who logs on to an account to which the appropriate right have been granted can carry out the corresponding actions. When a user does not have appropriate rights, attempts to carry out those actions are blocked by the system. User rights apply to the system as a whole and are different from permissions, which apply to specific objects. The rights granted to a group are provided to the members of that group. In most situations, the easiest way to provide rights to a user is to add that user's account to one of the built-in groups that already possesses the needed rights rather than by administering the User Rights Policy. The DameWare Remote Support User Rights window view will allow selection to show the Standard User Rights, Advanced User Rights or All User Rights. Once selected, the value will be saved when the User Rights window view is entered again.

Audit Policy

You can track selected user activities by auditing security events and storing the data in a security log. Your Audit Policy specifies the types of security events to be logged. These types can range from system-wide events (such as a user logging on) to specific events (such as a user attempting to read a particular file). They can include successful events, unsuccessful events or both. When you administer domains, the Audit Policy affects the security logs of all domain controllers. When you administer a computer that is not a domain controller, the Audit Policy affects the security log of only that computer. Use Event Viewer to review events in the security log on the local system.

Last modified
15:08, 12 Jul 2016

Tags

Classifications

Public