Zenworks / Grouppolicy / WUS

[Pevo58]

Hello,

We are using the ZW workstation policy for configuring our workstations. I put the neccesary lines into the workstationpolicy to configure the connection and our WUS server. After reboot the station has to signup to the WUS server but that is not the case. I checked with gpedit.msc if the wus-lines are present in the workstation policy and that was ok. For testing I imaged a new workstation and disabled the ZW workstation association with our policy. After startup I put the same wus lines into the policy with gpedit.msc (manual) and within a few seconds that workstation was visible withing our WUS server.
Am I missing something within the conf. of our ZW workstation policy ?? For your convenience, there are no typing errors made.

Peter.

 

[Provogeek]

Are you directly editing your group policy with gpedit.ms or are you going through ConsoleOne to make the desired edits?

Do other settings in your group policy come down?

Enabled debuging and post the results of *GrpPol files

http://www.novell.com/support/searc...iceId=&dialogID=12546726&stateId=0 0 12554739

Please be sure to trim it down to just a single boot, better to just set the log files to replace on each reboot.

=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
Brent Schmidt Certified nut case
Senior Network Engineer
Keep IT Simple

http://www.kiscc.com

 

[Pevo58]

The XP workstations are in one container. In that container is also the workstation policy that is associated to that container. In that policy I only have one adm active and that is wuau.adm. The policy is only ment for the workstation, not for the user or security. The policy is created with ConsoleOne. The workstation is auto-imported in the container and it's registered itself every boot, so that's ok. When the workstation has passed the policy I use gpedit.msc to check if the wus configuration is made. For my own purpose I configured a workstation with gpedit.msc for WUS that had not passed the ZW policy. With gpedit.msc and regedit I noticed the changes that were made by the system. I checked the WUS server and the station was registered. I noticed a difference in both the good and the bad situation. In the good situation there are two lines that point to the Intranet WUS server and STAT server. Those two lines are present within the registry and gpedit. In the bad situation those two lines are only visible with gpedit. In the registry the key with those two lines is not present. So I think that can be the problem. Tomorrow I will check your suggestion with the debug.

Peter van Opbergen
Manager/Network & Systems Engineer.