Zen works / User profiles

[Sharpedge]

We use NT with Novell Clients, on our new ws (2000) when users login no matter what type of profile (NT) they've got it automatically goes to roaming profile for Novell.

I am the administrator on the NT box have no writes on the Novell side, can I fix this problem??

Can I bypass or force Novell to use NT profiles?

We use Zenworks and I believe that this problem is related to Zenworks.

Please help!%-(

Thanks

 

[Sirn30]

The Following is done using Netware Administrator and u need administrator rights!

1. Yes the problem is Zenworks however you can stop the roaming profile in Zenworks. Go to the container were the user that you are having this policy problem and check the WinNT/Win200 user policy the the user is using. Now go to the desktop preferences in the policy and click on details, next click on the roaming profile tab and disable it by unchecking the roaming profile box.


2. Also take a look at the dynamic local user in the same policy to make sure the you have that it configure correct. The Dynamic User page lets you configure users created on Windows NT** workstations after they have successfully authenticated to NDS*. Once a user has been associated with an NT Configuration object, NetWare* Graphical Identification and Authentication (NWGINA) can retrieve information from the NT Configuration object to create an NT user account on the workstation and put the user in a local group on the workstation.

3. Enable Dynamic Local User

Enables creation of a User object that resides either temporarily or permanently in the workstation's Security Access Manager (SAM) database. NWGINA requires that you specify whether a local user is to be created.

If this box is not checked, NWGINA does not create a user in the local SAM. Instead, NWGINA attempts to find an existing NT user with the credentials indicated in the Windows NT tab of the NWGINA login interface.
If Enable Dynamic Local User is enabled, then NWGINA gets the NT Username from the NT Configuration object and queries the local SAM to see if the Username already exists. If it does exist, NWGINA authenticates the user to the NT workstation and access is granted. If the Username does not exist, NWGINA creates the user in the local workstation SAM.

If Windows NT password restriction policies are set on the local workstation, Dynamic Local User will not be used.

Manage Existing NT Account (if any)

Allows management through the existing NT account. Click if the User object you want to manage already exists. Workstation group assignments specified by Workstation Management will be implemented, including changing the account from nonvolatile to volatile when the user logs in to the account. The account will also be removed from the workstation after the user logs out.

 

[Questy]

What version Zenworks? What version NW Client? There are a lot of new features, and issues, with Zen 3, which on W2k requires NW Client 4.8