doomie

I have 30 machines or so to create local policy lockdowns on. I add in the Local Policy snap-in on the computer, create the .MSC file, configure all the settings, then that computer is done. But when I copy the .MSC file to the next computer via USB drive, all the settings become unconfigured. Is there a way to copy local policy settings manually to each computer or am I out of luck? I have to manually configure each MSC file on each individual machine and that takes quite awhile. Thanks! p.s. all the machines are exactly the same. I dont know why this wouldnt work especially if the Local Policy snapin is on all machines in the first place.

Well, I fixed the problem. I renamed the student profile to student1, and it worked. Had something to do with how the original student profile and printers were set up. So strange.

OK, I deleted the student account completely, deleted the profile, and created a new student account. This fresh new account is still not allowing me to print. Any account named student will not work, period. Is this to do with the SID number? The fact that an SID number is assigned to each user name, and stays, even if deleted? I can change another account name to student, and that accounts printing capabilities dissapear as well. I really am at a loss.

Yeah, its crap equipment, but it is functioning. I have ruled out the print server as the problem, and am now more focused on the workstation side. The print server chooses not to work only for 1 logon? The server is fairly transparent, any user logged in should be able to send jobs through it. argh!

No, no quota software. Still working on this - print jobs are piling up in the queue, the jobs are communicating, they just arent printing ........on the student account. All other accounts are working flawlessly. Student account in in the users group, full printing rights.

At my school, we have a library with 3 win2k pro sp4 computers. All are set up with mandatory profiles and local policy lockdowns. There is one printer in this room, attached to a trendnet TE100-P2U1P print server. The print share has been installed along with the drivers to a Windows 2000 server machine, SP4. My problem is this. I can install the printer from //print, and printing works great, under the administrator account. When I switch the the student account (mandatory profile), I can see the printer, and can send jobs to it. The print job goes through like it worked, but obviously nothing prints. I have created a test account, regular profile, no policy, and it prints. So, The Admin account will print, a test account will print, but the account with the mandatory profile will not, even if I give the student account admin rights. The installed printer shows up on all profiles. I am at my wits end, and seem to want to believe the mandatory profiles are part of my problem. One bit of info - the original printer for these machines was installed when the machines were imaged for installation. Since then we have changed printers. Is it possible the mandatory profile is holding onto old print drivers, etc, and not letting the jobs from the current printer go through? It would be awesome if I could get afew pointers. Thanks!