Novell Cool Solutions

Workaround if a Second Workstation Object is Created

coolguys

By:

November 14, 2006 12:00 am

Reads:4,935

Comments:0

Score:Unrated

Print/PDF

“Although this may work, remember that it’s not supported by Novell. You should not get a second workstation object in normal circumstances, unless you move workstation objects from the container where your import policy creates them.” — Shaun Pond

PROBLEM

If you reinstall a workstation, sometimes a second workstation object is created by policy in another container. This is a problem if you have associated several applications. The applications are not available after the reinstall, because the old object is not available.

SOLUTION

  1. Go to the old Workstation object in ConsoleOne.
  2. Go to the Other Tab and copy the zenwmid.
  3. Go the Workstations Registry HKLM\Software\novell\workstation manager\identification.
  4. Copy the old workstation ID into the Workstations registry.
  5. After Reboot, the workstation is remotable and all associated Applications are available.
  6. Eventually you must also change the NDS Path from the Workstation object in the registry, if there is another one.

If you have any questions you may contact Oliver at oliver.fischer@TAKETHISOUTopb.de

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Loading...Loading...

Categories: Uncategorized

0

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS