Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Workstation Manager

Status
Not open for further replies.

bwarner

Technical User
Feb 27, 2002
143
We need to upgrade the client on all our 300 NT 4.0 workstations, which currently have version 4.11a installed. We would like to install version 4.71 or higher. Currently Workstation Manager is installed on the client which allows the users to bypass local NT login. But, in order to get the new client to work, I am having to remove the existing client first (apparently client 4.11a is so old we can’t go directly to 4.71). After the old client has been removed and the PC has been rebooted, I run custom setup on the new client and click to install Workstation Manager. The problem is that Workstation Manager does not work. After the workstation is rebooted and I try to login with the new client, I am prompted for a local NT password. Obviously, this 2nd login box will be something our users are not used to and we need to find a way around it. Any suggestions would be appreciated.
 
Have you definately got a ZENworks policy configured for Dynamic Local User to create the local account?

Also ensure that the tree name is configured in the Workstation Manager properties -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
I do have a Zenworks Policy enabled with Dynamic Local User. But, does the workstation have to be registered and/or imported before the policy takes affect? If so, how can you register a workstation when the client hasn't even been installed yet? That seem to be the problem.
 
I do have a Zenworks Policy enabled with Dynamic Local User. But, does the workstation have to be registered and/or imported before the policy takes affect? If so, how can you register a workstation when the client hasn't even been installed yet? That seems to be the problem.
 
You DO NOT need to import the workstation into the NDS for policies to work.

You also need to ensure that your container package has a search policy configured so that the policies can be found. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
I think I understand it now and it seems to be working. Thanks for the help.
 
Good, glad it's working. Any other queries, let us know. -----------------------------------------------------
"It's true, its damn true!"
-----------------------------------------------------
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top