global install of OpenDNS Updater

Not planned

Follow

gordon451

July 14, 2013 13:38

Just joined the crowd, then downloaded Updater and installed it.

 

I have W7HP64, and run 4 accounts, Admin (where I install all software) and 3 user accounts.  All network activity runs thru a DrayTek 2710Vn router.

 

So when I switched to my personal user account, Updater wasn't there!  Looking in SysInternals AutoRuns showed me that Updater is started from HKCU\Software\Microsoft\Windows\CurrentVersion\Run, proxied from HKEY_USERS\S-1-5-...-1000\.  When I forced Updater from the Run box, it tried to re-enroll me in OpenDNS because it couldn't see the Admin registry entry

 

My idea is to change the startup to HKLM\Software\Microsoft\Windows\CurrentVersion\Run, and the main registry entry from HKCU\Software\ to HKLM\Software, so people with my setup can share OpenDNS with the entire family.

 

Gordon.

0

• 

  rotblitz July 14, 2013 16:40

  The OpenDNS Updater is not foreseen to run user independent and is easily be handled only via an admin account..

  If you want a quick solution, use Marc's Updater instead: http://updater.marc-hoersken.de/

  0

  Comment actions Permalink
• 

  gordon451 July 15, 2013 08:30

  Thanks rotblitz, you have helped my understanding of the service.
  
  As I do not have any internet presence (website, etc) I'll uninstall it, as it seems I actually don't need it.
  
  Gordon.

  0

  Comment actions Permalink
• 

  Brian Hartvigsen September 23, 2013 20:26

  As noted by rotblitz, the updater is designed for standard home use where it's unlikely there are multiple user accounts.  As such the updater runs in user space, not as a system service.  Marc's Updater or any number of other updaters that support the DynDNS Dynamic DNS Update Protocol will work to update OpenDNS.

  0

  Comment actions Permalink

Post is closed for comments.