Remote shutdown windows masine?

[milanbb]

Da li je neko radio ovako nesto?

Pokusavam da napravim skript koji bi gasio racunare po firmi u slucaju kraja sveta. Prateci klasicna windows uputstva gde je sve opisano u par jednostavnih koraka, sve podesim kako pise i naravno ne radi 🙁

Dakle:

1. Pokrenuti Remote Registry service na udaljenoj masini.
2. Napraviti na udaljenoj masini istog korisnika i staviti ga u administrator grupu (ili grupu koja moze da ugasi comp).

http://technet.microsoft.com/en-us/library/cc770416.aspx
http://technet.microsoft.com/en-us/library/cc754820.aspx

Ideje? :|

 

[Pera]

Kada napraviš korisnika na udaljenoj mašini, obavezno čekiraj polje "Password Never Expires" u Properties-u od tog korisnika (prvo pokreni lusrmgr.msc, pa Users i desni klik na korisnika) - da ne bi imao problema kasnije.

Što se samog remote shutdown-a tiče, ja sam to rešio programom PsShutDown (http://technet.microsoft.com/en-us/sysinternals/bb897541.aspx), konkretna komanda je "psshutdown.exe \\remote_computer -u username -p password -f -k -t 00" i napravio sam .bat fajl gde je u svakom redu naveden kompjuter koji želim da ugasim daljinski.

 

[Dzoni_m]

Piiiiih ne mogu da nadjem sada, pisao sam skriptu za to. Jednostavno uzmi psshutdown.exe, kao sto ti je Pera vec napisao. Pogledaj malo help i bice ti jasno. Ja sam napravio tako sto sam imao poseban txt sa imenima masina koje restartujem. Pozovem skript koja iscita txt i restartuje ih. Razlog za posebnim txt je da ne kliknes slucajno na bat dvoklikom 🙂 Par puta sam tako restartovao sve zivo u prozivodnji jer sam hteo da dodam novi PC na listu. E zato napravi poseban TXT sa imenama masina koji cita glavna skripta. Tako da nema sta da trazis oko glavne skripte da je ne bi slucajno aktivirao, vec sve izmene koje masine gasis uradis u tom TXT fajlu.....ako nadjem tu moju pisaniju okacicu......

edit: e da meni su sve masine bile u domenu tako da nisam morao da pravim poseban user acc.

 

[milanbb]

Hvala za PSshutdown, video sam ga, ali je problem izgleda na drugom mestu.

.33 - nema ukljucen RemoteRegistry i rade svi moguci nacini za gasenje nebitno da li je ukljucen ili iskljucen FW :| (W7)
.181 - ima sve zivo ukljuceno i nece ni da bekne, stalno access denied (W7)
.180 - nema nista ukljuceno i nece 🙂
.4 - W2003 ubio sam ga ko zeca, nista nije ni pitao samo se ugasio

lutrija kanda 🙂

PsShutdown v2.52 - Shutdown, logoff and power manage local and remote systems
Copyright (C) 1999-2006 Mark Russinovich
Sysinternals - www.sysinternals.com

Couldn't access 172.27.27.181:
Access is denied.

If 172.27.27.181 is already performing a shutdown operation you must
abort it before issuing a different command.

Ovo je greska iako je u/p tacan.

 

[Ji 4Tze]

Meni radi prostim shutdown /i u promptu, samo ukucam ime mašine. Ne ako je XP na kompu koji gasim

 

[Pera]

Hvala za PSshutdown, video sam ga, ali je problem izgleda na drugom mestu.

.33 - nema ukljucen RemoteRegistry i rade svi moguci nacini za gasenje nebitno da li je ukljucen ili iskljucen FW :| (W7)
.181 - ima sve zivo ukljuceno i nece ni da bekne, stalno access denied (W7)
.180 - nema nista ukljuceno i nece 🙂
.4 - W2003 ubio sam ga ko zeca, nista nije ni pitao samo se ugasio

lutrija kanda 🙂

PsShutdown v2.52 - Shutdown, logoff and power manage local and remote systems
Copyright (C) 1999-2006 Mark Russinovich
Sysinternals - www.sysinternals.com

Couldn't access 172.27.27.181:
Access is denied.

If 172.27.27.181 is already performing a shutdown operation you must
abort it before issuing a different command.

Ovo je greska iako je u/p tacan.

Da li možeš da mapiraš admin share-ove sa tih računara na računar sa kojeg puštaš PsShutdown? Naravno, koristeći taj username/password koji si kreirao. Proveri i da li je isključen UAC na tim računarima na kojima imaš problema.

I ja sam koristio PsShutdown u domenu (sa DC-a 🙂 ), tako da nisam imao problem da pristupim svim računarima...

 

[milanbb]

Da, to sam sada probavao - ne mogu da mapiram admin share 🙁

 

[Pera]

Da li uopšte postoje Admin share-ovi? Da bi ovo sve radilo, mora da bude minimum W7 Professional (Home verzije ne podržavaju admin share-ove, koliko ja znam).

 

[milanbb]

Da, svi su W7 pro... pokoji 2003 i 2008 R2 ima i tri XP-a, ali ti mogu i da popadaju. 🙂

Na .33 W7 iskljucen UAC

Na .241 W2008 ukljucen UAC, ali rade Admin shares, PSShutdown radi, ostaje da proverim i shutdown.

 

[milanbb]

Posle ukljucivanja admin shares radi, radi i sa linuxa gasenje :|

http://forum.sysinternals.com/psshutdown-issue_topic3308.html

http://blog.hansmelis.be/2009/09/06/administrative-shares-in-windows-7/

Spojler

Those who have experience with NT-based operating systems on a network will certainly be familiar with the concept of administrative shares. If that doesn’t ring a bell, you access them like \\computername\c$. With this intro and the title of this post, you might be alarmed or enter panick mode fearing they might be gone in Microsoft’s latest OS iteration. Well don’t go into cardiac arrest because they are still there… but of course not without the odd problem.

Windows 7 still creates the administrative shares on install, but you can’t use them out of the box. First of all, you need to have File and Printer Sharing enabled. And the way to do that has once again been changed:

Open the control panel.
Go to Network and Internet.
Go to Network and Sharing Center.
In the left column, click on Change advanced sharing settings.
There are two profiles. You probably don’t want this on when you’re on a public network so open Home or Work.
Under the header File and Printer sharing, select the Turn on… option.

And now your administrative shares still don’t work 😛 You’ve just completed step 1 which implies there’s at least a step 2 and here it is: you also need to change the registry.

Click on the orb (= the round button with the Windows logo in the taskbar) and type regedit in the search box.
Open the registry editor.
Navigate all the way to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
Right-click in the pane on the right side and add a new DWORD (32-bit).
Give the new setting the name LocalAccountTokenFilterPolicy.
Double click on that setting and give it a value of 1.

It’s probably wise to reboot after doing this, although it might not be needed. I’m not sure if it works straight away because I rebooted without trying.

Anyways, if you’re lucky you will be able to access administrative shares after performing these steps. If you’re unlucky, like me, doing all these things appears to have zero effect at all. Once again don’t panick, because there’s another hint/tip/solution coming your way.

Somewhere at some point during the installation or configuration of Windows 7, you will be asked to do something with a thing called Homegroup. It’s some weird new sharing tool that looks OK but isn’t quite what you’re used to. Once you have enabled that feature, you won’t be able to use the administrative shares. So the tip is: disable the homegroup feature.

Open the control panel.
Go to Network and Internet.
Go to HomeGroup.
Click on the blue link Leave the homegroup.

The popup dialog should point out itself, but I believe I picked to first option. Once I had left the homegroup, the administrative shares started working again.

I hope this post can help anyone who experiences the same problem.

Eto,.... mislio sam da je bas neki velik problem 😀

Hvala svima na pomoci.