GPO Dissabled HP ScanJet

  • Thread starter Thread starter carsonbrad
  • Start date Start date
C

carsonbrad

One of the admins where I work was creating a policy and accidentally
applied it to the entire domain and not the test OU.

We have corrected most of the incorrect GPO settings. One outstanding
issue is, after the policy was enabled, the PCs that have a USB HP
Scanjet w/ ADF connected can now longer see the ScanJet. The PCs are
able to see USB memory keys.
Is there anything I should look at.

Thank you

Brad Carson
 
I can't thing of anything off the top of my head but if you still have the
GPO that caused the problems and you have an XP Pro computer in the domain,
I would install Group Policy Management Console on the XP computer, enable
the GPO on a test OU, and use GPMC to view all the settings in the GPO and
print them out so that you can try and track down the setting causing the
problem. My guess is that it might be a security option that would show in
Local Security Policy [secpol.msc] security settings/local policies/security
options. For Windows 2000 computers the effective settings are the ones of
interest. You might want to compare to another computer that did not have
this policy applied to it or use the mmc snapin for Administrative Templates
and compare to the security options in the setup security.inf template. ---
Steve

http://www.microsoft.com/windowsserver2003/gpmc/default.mspx --- GPMC
 
Hi,
One of the admins where I work was creating a policy and accidentally
applied it to the entire domain and not the test OU. We have corrected
most of the incorrect GPO settings. One outstanding issue is, after
the policy was enabled, the PCs that have a USB HP Scanjet w/ ADF
connected can now longer see the ScanJet.
Click to expand...

I am assuming he has no idea what policies he set? Doesn’t sound too
much on the bright side if he confused a Domain GP for one he created
himself? I am curious if he wrote a custom .adm to modify the
registry. I am not familiar with a Policy to disable a USB scanner and
unless it is a new Policy, I am pretty familiar with them all.

If he wrote a Custom ADM, then it may be a registry hack. Custom ADM’s
often affect the registry of the user, unlike Group Policy ADM’s that
affect only the Policy Section. Therefore if he hacked the registry
you will have to know the exact ’hack’ so you can undo it. NT 4
Policies hacked the registry and so when you removed them the registry
was still "hacked".

I would need more info on the exact settings he made in order to help
you reverse them. The other option would be to reinstall the Scanjets
on the client computers.

Cheers,

Lara
 
Back
Top