Windy08

SYNACK, I'm using vbs. The 7 machines are 32 bit. I got a call after I'd been tinkering with the 7 machines to say that nobody could print so I toddled off back to find that the print spooler service had stopped and the printers were no longer installed on the server. I got that back up and running by starting the service and reinstalling the printers, but when I tried to reinstall, it said the printer was already in use, so I created a new printer, and just as I'd finished installing it, the other 2 printers appeared in the printers folder as if by magic. Don't know what that was all about. Anyway, I dug deeper and found that staff (with roaming profiles) could also see the printers, but pupils (with mandatory profiles) couldn't, so it started to look like group policy issues when logging on as a user even though the printer script runs on an OU that contains computers and not users. I only work there for 2 hours twice a week so I will investigate more when I'm back in, but it seems to be heading towards a policy on the users OU that is stopping the script working. I will report back when I've found the culprit

I have a similar problem. We have got 30 Win7 netbooks on a Server 2003 domain. My VB printer script works fine on the XP machines. On the 7 machines, my printers are mapped when logged on as admin but not when I log on as a user. Gpresult says the policy with the script in it "is applied", but the printers aren't mapped. I have got RSAT installed on the 7 machines and done the point to print restriction policy as described by SYNACK. I can install the printers when logged on as a user in the normal way, so the drivers are there and there aren't any restrictions.

Have you tried going to the computer in question and running the setup from the shared INTERCHK folder? I've had to do that on a few machines for it to register in Enterprise Console.

When 7 connects to the network with a user who's My Documents are redirected (the XP way), 7 renames their folder "Documents". It does that for all users, so you end up with folder full of folders saying "Documents" instead of their names like it was when XP uses them. The ones that are still named the old way, are users that haven't logged onto a 7 machine yet. 7 knows which ones are which and XP picks up the right ones as well.

GPO->User Configuration->Administrative Templates->Windows Components->Windows Media Player->Networking->Streaming Media Protocols

ITalc is another easy one to set up. You get the option to lock them out with a massive padlock picture popping up on screen. You ort to see their faces when I first ran it!!!!

You have to set the loopback processing as well. Open the Group Policy Object editor (gpedit.msc) and go to the group policy you set for the script you are using. Expand the Computer Configuration node. Expand the Administrative Templates node. Expand the System node. Expand the Group Policy Locate the setting "User Group Policy loopback processing mode". Double click this setting. Set it to "Merge" Your Group Policy should now work If it still doesn't work, try putting your script in the "Logon" part of the OU instead of the "Startup"

You can set up a Group Policy on your Server to use an audit log which lets you audit account logon events. The Group Policy is in Computer Configuration->Windows Settings->Security Settings-Local Policies->Audit Policy Don't log everything cos they can take up a fair amount of space

If you've got a 2008 license, then you can use it on a win2k3. What are your current CALs issued for? Win2k or Win2008?

Wots your local LEA prices like? I found they were very competitive

Just had that today. I changed it with another keyboard and it was OK Don't ask me why, it worked so I wasn't bothered why