zlorimer

Least rights possible

cmd > gpresult /V > C:\gpresult.txt Post the results

http://www.edugeek.net/forums/windows-7/65502-printing-oddities-specified-port-unknown.html#post830895 Check that out and see if it helps.

Well if anyone comes across the same problem that I did, I fixed it. I had to uninstall everything involving WSUS and reinstall everything. It wasn't bad, but it took some time.

I use WID as well for WSUS. I only use one server in WSUS, but I am getting ASP.NET 2.0.x.x errors in addition to the WID errors. But yeah, I'm basically dead in the water currently since I cannot do anything and no one in my network is receiving updates now. Thankfully, summer just started so I have some time to be patient.

It seems to be a common problem I will post up if I can find a fix, but just a forewarning to everyone, be careful. WSUS 3.0 SP2 will not run after installing update 2720211

Nah. We don't use proxies here. I cannot open the MMC using the Internal MS DB setup on WSUS3.0 SP2. I am thinking I am going to have to rebuild it because I cannot find any real answers or anything.

These updates broke my WSUS and I cannot get anything to work again. I guess I will be rebuilding the server...

What is the error that you are receiving in the event logs of the PCs? How do you have the printers set to map through GPP? It could be as simple as you only have 64bit drivers installed on the 2k8R2 server and not the 32bit drivers, or it could be a bit more complex and require a few more steps.

I was having these problems, but have since fixed them. I posted my information in the other thread, but just in case here is a link: http://www.edugeek.net/forums/windows-7/65502-printing-oddities-specified-port-unknown.html#post830895

There are a few tweaks to getting GPP to work perfectly. I have spent the past month making sure everything works great. 1) If you have any Dell or HP printers, I strongly recommend using their appropriate drivers. The Dell Open Print Driver or the HP Universal Print Driver work okay, but are not great for all of their respective branded printers. 2) I fully disabled UAC as it created problems with my Shoretel stuff, but it also makes installing the printer drivers much easier. 3) Make sure that your printers have both 64bit and 32bit drivers installed and enabled for each printer. 4) You need to disable the popups that people receive about drivers and non-signed stuff. To do this you enter the following items in a GPO: Computer Configuration > Policies > Administrative Templates > Printers > Point and Print Restrictions set to Enabled, Users can only... set to Disabled, Users can only point and... Disabled, and then set the two drop down boxes to "Do not show warning or elevation prompt." Computer Configuration > Policies > Administrative Templates > System > Driver Installation > Allow non-administrators to install drivers for these device setup classes set to Enabled. Then add {4D36E979-E325-11CE-BFC1-08002BE10318} as an allowed class. Computer Configuration > Policies > Administrative Templates > System > Group Policy > Printers preference extension policy processing set to Enabled. Then set Allow processing across a slow network connection to Disabled, Do not apply during periodic background processing to Enabled, Process even if the Group Policy objects have not changed to Disabled, and Background priority to Idle. Computer Configuration > Policies >Administrative Templates > System > Logon > Always wait for the network at computer startup and logon set to Enabled User Configuration > Policies > Administrative Templates > System > Driver Installation > Code signing for device drivers set to Enabled and set When Windows detects a driver file without a digital signature to Ignore. Your printers should work perfectly through GPP after setting those parts. I have been running for 3 weeks without problems now and I was having problems multiple times per day beforehand.

I disable the access to the Control Panel and it gives the students a popup stating they do not have access to the EoA stuff. However, one of the kids has figured out a method around this. I am further investigating the latter.

The only I problem I ran into was making sure users on a clean Windows 7 install had a registry key in place before installing the Smartboard Notebook 10.8 software. Other than that, everything I've run into has been a breeze with Win7x64.

I use 4 different WMI filters. They are as follows: Windows 2k/XP PCs, Windows Vista/7 PCs, Windows 7 x86, and Windows 7 x64. Win2k/XP PCs root\CIMv2 select * from Win32_OperatingSystem where (Version like "5.%") and ProductType = "1" Win7/Vista PCs root\CIMv2 select * from Win32_OperatingSystem where Version like "6.%" and ProductType = "1" Win7 x86 root\CIMv2 SELECT * FROM Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType = "1" AND NOT OSArchitecture = "64-bit" Win7 x64 root\CIMv2 SELECT * FROM Win32_OperatingSystem WHERE Version like "6.1%" AND ProductType = "1" AND OSArchitecture = "64-bit" As far as GPOs and such, I have various different ones that do a lot of different things and I don't mind posting them, but how strict or lenient of a policy do you want to see?