Hello Sijtze,

I have run into this problem once before, my script ran perfectly when I executed it manually but did not produce a result when executed through a GPO.

I would suggest you check the UAC settings on the system you are testing the policy. With UAC enabled any scripts that are run from a policy will execute, but under a different security context to the user. When UAC is enabled the logon/logoff scripts are executed by an Administrative user, the desktop then loads afterward as the user.

One suggestion to resolve the problem was to firstly apply this registry setting:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

EnableLinkedConnections =(dword)1

Google UAC and logon scripts and you will find further information and suggested workarounds.

I hope this helps

David

Hi David,

I figured it out. It was my own fault. I exported the keys to the roaming folder uf the users profile but guess what. The roaming folder wasn't included in te metaprofile. So I made other metaprofile entry with a new folder and exported the files to that folder. Now it works perfect. We finally can save our personal printer settings :-)

Thanks for your help. I appreciate it.

regards

Sijtze