| |
Windows* 95/98 users and Windows NT* users require different management tasks. Managing users also includes upgrading their client software. See the following sections:
To modify the Windows 95/98 client configuration
In NetWare® Administrator, right-click a Win95-98 Workstation Package > click Details > 95 Novell Client Configuration > Details > Policy Schedule.
Change the policy schedule to not include the current time in the Start Time and End Time fields.
Wait 10 minutes to allow all the workstations to refresh their schedules.
Make the necessary changes to the Windows 95/98 client configuration policy.
Verify that the changes were saved correctly.
Reset the policy schedule to include the current time.
For Windows NT users, you can add them to groups or define them as Dynamic Local Users. See the following sections:
When Workstation Management creates the Windows NT workstation user, it can provide group membership to any NT user groups. The groups that the user is added to are listed in the Workstation Groups list. The default configuration is for the user to be added to the Users group. Other groups can be added.
In NetWare Administrator, click a WinNT User or WinNT Workstation Package > Details.
Click Workstation Import Policy > Details > Workstation Group.
Click Add to add a group to the Workstation Groups list.
In NetWare Administrator, right-click a WinNT User Package > click Details > Policies.
Click Dynamic Local User (make sure the box is checked) > Details.
Click Enable Dynamic Local User.
Select either Use NetWare Credentials or Manage Existing NT Account.
If you select Manage Existing NT Account, provide the NT Username, Full Name, and Description for the NT user account to be used.
If you select Use NetWare Credentials, the Volatile User option is automatically checked.
Add this user account to any groups where this user account is to be a member. (Existing groups are listed under Not Member Of.)
If necessary, create one or more custom groups by clicking the Custom button, clicking New, then providing the necessary information. The custom group is then added to the Not Member Of list, and you can add the NT user account you set up in the above steps to that group.
To dynamically create a user's account in the workstation's Security Access Manager (SAM) without any administrator intervention, you must enable the Dynamic Local User.
In NetWare Administrator, right-click a WinNT User Package > click Details > Policies.
Click Dynamic Local User (make sure the box is checked) > Details.
Click Enable Dynamic Local User.
If this box is not checked, a user is not created in the SAM. Instead, the NetWare Client attempts to find an existing Windows NT user in SAM, with the credentials indicated in the Windows NT tab of the login interface.
If this box is checked, the NetWare Client retrieves the user's login information (for example, user name) from the WinNT User Policy and queries the local SAM to see if the user already exists. If the user does exist, the NetWare Client authenticates the user to the NT workstation and access is granted. If the user does not exist in SAM, the NetWare Client creates the user in the local workstation SAM, authenticates to NT, and access is then granted.
Edit the fields.
See Dynamic Local User Dialog Box for more information.
The NDSTM name must be no longer than 48 characters in order to use Dynamic Local User.
Workstation Management requires that you specify whether a Dynamic Local User is to be created.
In NetWare Administrator, right-click a WinNT User Package > click Details.
Click Dynamic Local User > Details.
Click Enable Dynamic Local User, which creates the local user.
If Enable Dynamic Local User is enabled, then the NetWare Client gets the Windows NT user name from the WinNT User Policy and queries the local Security Access Manager (SAM) to see if the user name already exists. If it does exist, the NetWare Client authenticates the user to the NT workstation and access is granted. If the user name does not exist, the user account is created on the local workstation.
If the Enable Dynamic Local User box is not checked, a user account is not created in the local SAM. Instead, the NetWare Client attempts to find an existing NT user with the credentials indicated in the Windows NT tab of the login interface.
You can update or upgrade the Novell® ClientTM in one of the three following ways:
You can use ZENworksTM features to routinely update files you specify. You can create a policy package and then add an action to the policy package that updates a certain file each morning, for example. Then when you associate that policy package with a Workstation object, Workstation Group, or Container object where the Workstation object resides, the file will be updated each morning on that workstation.
You can distribute client updates to Workstations by using the Application Launcher.
The Novell Automatic Client Upgrade (ACU) provides a way to upgrade from earlier Novell Client software to the latest Novell Client software. On Windows NT* workstations, you can also upgrade the operating system. This upgrade happens when users log in.
The ACU process requires five tasks:
Extensive documentation about the ACU process is available in the Novell Client documentation for each platform, including specific requirements and examples to assist you. Read this documentation before establishing an ACU process for your network. The client documentation is available on the ZENworks CD. See the following documents:
You can also create a script that upgrades the clients on four different operating systems.
For Novell Clients only, see Example Login Script for Novell Clients for updating older Novell Clients to the latest Novell Clients on the Windows NT, Windows 95/98, and Windows 3.1x, and DOS platforms.
| |