Realpoet02
asked on
Windows 7 x64 and SNMP
We install the SNMP feature on a windows 7 x64 workstation either by running the ocsetup.exe SNMP command remotely via psexec.exe or manually installing it. Once installed, we then configure the service remotely using the services.msc from another computer.
The issue is that when we remotly (via services.msc) click on the service name then click on the agent tab, traps tab, or security tab we receive an error “failed to read a registry key. This may be due to lack of resources. Try closing other windows applications to fix the problem.” This is being done as a Domain Admin
When we open services.msc on the local computer, and click on the trap tab...it appears normal and we can configure and save the changes. This works great, but I'd like to configure it remotley
This doesn’t seem to be related to open programs as it’s affecting multiple x64 computers; it works great on 32 bit.
Just to rule it out, I’ve disabled the local firewall and virus scanner to no avail. There also doesn’t seem to be a GPO settings affecting these computers that would modify SNMP in any way.
The issue is that when we remotly (via services.msc) click on the service name then click on the agent tab, traps tab, or security tab we receive an error “failed to read a registry key. This may be due to lack of resources. Try closing other windows applications to fix the problem.” This is being done as a Domain Admin
When we open services.msc on the local computer, and click on the trap tab...it appears normal and we can configure and save the changes. This works great, but I'd like to configure it remotley
This doesn’t seem to be related to open programs as it’s affecting multiple x64 computers; it works great on 32 bit.
Just to rule it out, I’ve disabled the local firewall and virus scanner to no avail. There also doesn’t seem to be a GPO settings affecting these computers that would modify SNMP in any way.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
arnold
The above is a windows 2008 reference, remove policies for windows 2003.
ASKER
Looks like the remote registry service was disabled by default on these systems.
The 32bit systems have this system on via GPO as they where in a different container.
Thanks for the sugjestions though.
The 32bit systems have this system on via GPO as they where in a different container.
Thanks for the sugjestions though.