fancyabrew

cooorrrrrrrrr our users will be pleased I've been waiting for a fix for this issue for ages! I'll download it and give it a whirl. Thanks for the heads up!

This is a know issue (although MS doesn't seem interested in a fix) you will see the problem if you use Offline files on a folder that you also redirect. We had a number of users with the issue as we redirect My Documents and user were making this offline as its their main user home folder. There is no fix, the only workaround is not make a redirected folder avaliable off line (

You're a star it was indeed the computer GPO setting

Right I'm deploying around 40 Win7 boxes and I've come across an issue with point and print (don't get the issue with Vista) Basically if a non admin user tries to install a network printer they get prompted for admin rights to do the install. Which is all well and good EXCEPT I have point and print restrictions turned off so there shouldn't be ANY restrictions on non-admins installing the printers. grrrrrrrrrrrrr Vista boxes are configured the same and DON'T have an issue, which is most annoying. Even if I turn on point and print restrictions but set it to NOT give users elevated privileges warnings they still get them, double grrrrrrrrrrrrrrr

try to edit the gpo via a w2k3 box or a vista one. I've not had any problems doing the edits from those OS's only with w2k8

also works fine from a vista SP2 box. So from a w2k8 box you get the error and the software won't deploy from vista and w2k3 things work fine

hmmm ok if I make the GPO changes from w2k3 boxes everything works fine, w2k8 and you get the error

ok its now doing it on a fresh GPO

ok logout and back in to the DC and the error returns

hmmmm werid I've just restored a GPO and now the problem seems to have gone on all GPO's tre'werid!

funny enough I've just started to get this error on w2k8 DC's if I use a w2k3 DC I don't get the error. Now I have'n done enough playing to see whether I still have a problem on w2k3 DC and just don't get the error message or whether its a w2k8 issue. as the article says the error message goes away if I create a fresh GPO, BUT this would be a BIG headache if I had to do this