1. Home
  2. Forums
  3. Variable Star Observing
  4. AAVSOnet

Need IT help (remote shutdown of Win7 computer)

KTC
Affiliation
American Association of Variable Star Observers (AAVSO)
Mon, 09/17/2012 - 17:55

I need some IT help at Astrokolkhoz.

The local network of observatory computers can be shut down with a single BAT file...using the   shutdown    command....

...except for one stubborn computer.  (Win 7 Home Premium 32-bit)  It gives the not-very-informative error message:  Access denied (5).

I've got plenty of XP machines, and one or two Win 7 64 bit Home Premium machines that respond properly to a remote shutdown command.

Why does this one computer refuse to work?  (I'm the administrator and sole operator of all of them...set them up all the same way, etc.)

If you have any ideas on how I can troubleshoot and fix this issue, please tell me how I can peer inside this black box that only says  "Access denied (5)."  (If I knew it was a registry entry...I'd change it in a heartbeat...but I'm fumbling in the dark on this issue.)

Thanks in advance.

clz
Affiliation
American Association of Variable Star Observers (AAVSO)
Mon, 09/17/2012 - 21:32
Have you the Full control on

Have you the Full control on the Folder ?

Laurent

KTC
Affiliation
American Association of Variable Star Observers (AAVSO)
Mon, 09/17/2012 - 22:59
All computers geeting time sych from Internet time software

All computers geeting time sych from Internet time software, and I verify it during test runs.

On another forum this issue was mentioned:

http://experts.windows.com/frms/windows_entertainment_and_connected_hom…

Might this be the cause of the problems?  (Do I really need the remote desktop capability to allow the shutdown command to be recognized.)

petike1
Affiliation
American Association of Variable Star Observers (AAVSO)
Mon, 09/17/2012 - 23:18
I don't think the concurrent

I don't think the concurrent remote desktop patch would help.

You can try to disable the UAC remote restrictions ("This mechanism also helps prevent local malicious software from running remotely with administrative rights."):

 

  1. Locate and then click the following registry subkey:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  2. If the LocalAccountTokenFilterPolicy registry entry does not exist, follow these steps:
    1. On the Edit menu, point to New, and then click DWORD Value.
    2. Type LocalAccountTokenFilterPolicy, and then press ENTER.
  3. Right-click LocalAccountTokenFilterPolicy, and then click Modify.
  4. In the Value data box, type 1, and then click OK.

(From this page: http://support.microsoft.com/kb/951016)