Install MSMQ via a Group Policy

Has Message Queuing been installed on the machine?

Server Manager | Features | Add Features

Having JUST left an academic environment where we were ghosting 1200+ workstations each quarter and needed to keep University students from hacking them to smithereens, I feel your pain. As it happens I spent September through January hacking on that exact problem. I did not find a complete answer, but I did find out some things that helped:

• Nearly all problems are a result of setting up the default user profile for use by students.
• Machines that are properly sysprepped experience this problem a lot less often than profile-copy methods.
• When it happens, sometimes the access to the print server is actually the ghost-user or the profile-copy user, or some other cached credential on the image rather than the logged in user.
  • Jason Berg's delay method will make this work if this is what's nailing you. By the time the GPO fires, profile setup is completed and these cached-user accesses won't happen.
• Sometimes, going into the Options on the Preference and hard specifying "Run with user's permissions" make it work more often.
• This seems to rarely happen when the profile exists on the machine, such as happens when troubleshooting the problem :P. I haven't used Deep Freeze, so don't know if it leaves profiles behind after a login.
• Sometimes Deploying the printer to the user and also setting a GPO Preference to set the default printer works more reliably than Deploying to the computer. You're using loopback processing anyway, may as well just put everything in the User GPO that you can.

And I still didn't get it completely knocked down. It's a tough problem.