psexec
psExec e PsTools Suite
roberto bianchi su uic h.e.


www.sysinternals.com/Utilities/PsExec.html
psExec e PsTools Suite
WindowsNT-2000
WindowsXp     Lingua:
Non in italiano
Prezzo: gratuito
Dimensione: 56 KB
17/01/06 - PsExec permette di eseguire comandi su macchine
remote in ambiente Windows
(NT/2000/XP/2003) da linea di comando all'interno di una
lan. Questa pratica interessa
chiunque abbia una lan, sia sotto
dominio
che
peer to peer,
domestica o aziendale. A parte usi poco puliti di un comando
simile, un'applicazione
pratica è quella dell'esecuzione da un server centrale del
già recensito
RootKit Revealer
su tutte le macchine di un dominio.

Naturalmente, oltre al perverso piacere dei feticisti della
digitazione, un comando
simile si adatta perfettamente all'automazione. È infatti
possibilissimo effettuare
un gran numero di operazioni remote usando Desktop Remoto
oppure
UltraVNC
ed affini... ma quando non è necessaria l'interattività o
una interfaccia grafica
oppure serve davvero solo automatizzare batch/script che
vadano da un pc ad un altro,
con PsExec è suffciente dire "esegui questo comando in
quella macchina". Se il comando
è presente, ed è nel cosiddetto "path", allora viene
eseguito e restituirà un eventuale
codice di errore o di riuscita (zero). Se non è presente se
ne viene informati e
si può comunque decidere di inviare il comando per
l'esecuzione remota direttamente
dalla macchina che ordina questa operazione.
Un comando molto potente, dunque, che tutto sommato
sostituisce una operazione di
apertura del servizio telnet sulla macchina remota, la
chiamata dal telnet client,
l'esecuzione e la necessità di richiudere il tutto, senza
contare che è possibile
inviare il comando (eventualmente mancante sulla macchina
remota) che serve eseguire.
Non è superfluo ricordare che la potenza di questo comando
può generare danni se
usato in modo poco accorto e che è possibile utilizzarlo
solo se si conoscono utenti
e password delle macchine remote e/o si dispone di diritti
amministrativi molto elevati
nell'eventuale dominio.

Oltre all'uso da una sola macchina ad un'altra è possibile
indicare anche una lista
di pc sui quali agire, ed è anche possibile semplicemente
utilizzarlo per lavorare
da
linea di comando
come se ci si trovasse sull'altro pc.

Introduction

Utilities like Telnet and remote control programs like
Symantec's PC Anywhere let
you execute programs on remote systems, but they can be a
pain to set up and require
that you install client software on the remote systems that
you wish to access. PsExec
is a light-weight telnet-replacement that lets you execute
processes on other systems,
complete with full interactivity for console applications,
without having to manually
install client software. PsExec's most powerful uses include
launching interactive
command-prompts on remote systems and remote-enabling tools
like IpConfig that otherwise
do not have the ability to show information about remote
systems.

Note: some anti-virus scanners report that one or more of
the tools are infected with
a "remote admin" virus. None of the PsTools contain viruses,
but they have been used
by viruses, which is why they trigger virus notifications.

Installation

Just copy PsExec onto your executable path. Typing "psexec"
displays its usage syntax.

PsExec works on NT 4.0, Win2K, Windows XP and Server 2003.

Usage

See the July 2004 issue of Windows IT Pro Magazine for
Mark's article
that covers advanced usage of PsExec.

usage: psexec [\\computer[,computer[,..] | @file ][-u user
[-p psswd]][-n s][-l][-s|-e][-i][-c
[-f|-v]][-d][-w directory][-][-a n,n,...] cmd
[arguments]
Elenco definizioni di 18 elementi
computer = Direct PsExec to run the application on the
computer or computers specified.
If you omit the computer name PsExec runs the application on
the local system and
if you enter a computer name of "\\*" PsExec runs the
applications on all computers
in the current domain.
@file = Directs PsExec to run the command on each computer
listed in the text file
specified.
-a = Separate processors on which the application can run
with commas where 1 is the
lowest numbered CPU. For example, to run the application on
CPU 2 and CPU 4, enter:
"-a 2,4"
-c = Copy the specified program to the remote system for
execution. If you omit this
option then the application must be in the system's path on
the remote system.
-d = Don't wait for application to terminate. Only use this
option for non-interactive
applications.
-e = Loads the specified account's profile.
-f = Copy the specified program to the remote system even if
the file already exists
on the remote system.
-i = Run the program so that it interacts with the desktop
on the remote system.
-l = Run process as limited user (strips the Administrators
group and allows only
priviliges assigned to the Users group).
-n = Specifies timeout in seconds connecting to remote
computers.
-p = Specifies optional password for user name. If you omit
this you will be prompted
to enter a hidden password.
-s = Run remote process in the System account .
-u = Specifies optional user name for login to remote
computer.
-v = Copy the specified file only if it has a higher version
number or is newer on
than the one on the remote system.
-w = Set the working directory of the process (relative to
the remote computer).
-priority =
Specifies -low, -belownormal, -abovenormal, -high
or -realtime to run
the process at a different priority.
program = Name of the program to execute.
arguments = Arguments to pass (note that file paths must be
absolute paths on the
target system)
fine elenco

You can enclose applications that have spaces in their name
with quotation marks e.g.
"psexec \\marklap "c:\long name\app.exe". Input is only
passed to the remote system
when you press the enter key, and typing Ctrl-C terminates
the remote process.

If you omit a username the remote process runs in the same
account from which you
execute PsExec, but because the remote process is
impersonating it will not have
access to network resources on the remote system. When you
specify a username the
remote process executes in the account specified, and will
have access to any network
resources the account has access to. Note that the password
is transmitted in clear
text to the remote system.

You can use the current version of PsExec as a Runas
replacement when you target the
local system because PsExec does not require you to be an
administrator.

Examples

This article I wrote describes how PsExec works and gives
tips on how to use it:

www.winnetmag.com/Windows/Issues/IssueID/714/Index.html

The following command launches an interactive command prompt
on \\marklap:

psexec \\marklap cmd

This command executes IpConfig on the remote system with the
/all switch, and displays
the resulting output locally:

psexec \\marklap ipconfig /all

This command copies the program test.exe to the remote
system and executes it interactively:

psexec \\marklap -c test.exe

Specify the full path to a program that is already installed
on a remote system if
its not on the system's path:

psexec \\marklap c:\bin\test.exe

Run Regedit interactively in the System account to view the
contents of the SAM and
SECURITY keys::

psexec -i -d -s c:\windows\regedit.exe

To run Internet Explorer as with limited-user privileges use
this command:

psexec -l -d c:\program files\internet
explorer\iexplorer.exe

PsTools

PsExec is part of a growing kit of Sysinternals command-line
tools that aid in the
adminstration of local and remote Windows NT/2K systems
named
PsTools.
Download PsExec (50 KB)
Download PsTools

The Windows NT and Windows 2000 Resource Kits come with a
number of command line tools
that help you administer your Windows NT/2K systems. Over
time, I've grown a collection
of similar tools, including some not included in the
Resource Kits. What sets these
tools apart is that they all allow you to manage remote
systems as well as the local
one. The first tool in the suite was PsList, a tool that
lets you view detailed information
about processes, and the suite is continually growing. The
"Ps" prefix in PsList
relates to the fact that the standard UNIX process listing
command-line tool is named
"ps", so I've adopted this prefix for all the tools in order
to tie them together
into a suite of tools named PsTools.

Note: some anti-virus scanners report that one or more of
the tools are infected with
a "remote admin" virus. None of the PsTools contain viruses,
but they have been used
by viruses, which is why they trigger virus notifications.

The tools included in the PsTools suite, which are
downloadable individually or as
a package, are:
Elenco di 13 elementi
. PsExec -
execute processes remotely
. PsFile -
shows files opened remotely
. PsGetSid -
display the SID of a computer or a user
. PsKill -
kill processes by name or process ID
. PsInfo -
list information about a system
. PsList -
list detailed information about processes
. PsLoggedOn -
see who's logged on locally and via resource sharing (full
source is included)
. PsLogList -
dump event log records
. PsPasswd -
changes account passwords
. PsService -
view and control services
. PsShutdown -
shuts down and optionally reboots a computer
. PsSuspend -
suspends processes
. PsUptime - shows you how long a system has been running
since its last reboot (PsUptime's
functionality has been incorporated into
PsInfo)
fine elenco

All of the utilities in the PsTools suite work on Windows
NT, Windows 2000, Windows
XP and Windows Server 2003. The PsTools download package
includes an HTML help file
with complete usage information for all the tools.

Installation

None of the tools requires any special installation. You
don't even need to install
any client software on the remote computers at which you
target them. Run them by
typing their name and any command-line options you want. To
show complete usage information,
specify the "-?" command-line option.

PsTools Forum

If you have questions or problems please visit the
Sysinternals PsTools Forum.
Download PsTools Suite (550 KB)
*trucchetto

Puo' essere utilizzato sulla macchina locale per avviare
applicazioni con autorita'
System anziche' administrator,
ad esempio avviare con psexec -i -d -s il programma
prescelto parte sulla macchina
locale ma con dei permessi piu' ampii quali la possibilita'
di accedere o modificare
files di sistema normalmente inacessibili o di modificare
zone del registro protette
(nonche' di accedere a rootkits che si installano come
drivers o ai monitor degli
antivirus).
indubbiamente e' un mezzo eccezzionale per fare anche danni
al sistema.
risposta: ciò non toglie che devi avere la password di
administrator locale



-----Messaggio Originale----- 
Da: "Giuseppe Fornaro" 
A: 
Data invio: martedì 17 gennaio 2006 10.10
Oggetto: [uic-helpexpress] Backup Dizionario Word


Backup Dizionario Word

Gli utenti del  Microsoft Word, possono effettuare un backup
del dizionario
personalizzato, quello che contiene
le parole aggiunte dall'utente. Normalmente scegliendo
"AGGIUNGI" dal menu
contestuale delle parole, queste vengono inserite nel
dizionario che fa
riferimento
al file:

C:\Documents and Settings\[NOME UTENTE]\Dati
applicazioni\Microsoft\Strumenti di correzione\CUSTOM.DIC

Tuttavia la directory potrebbe essere diversa o potreste
aver creato altri
dizionari. Per vedere la directory corretta controllate da
Word stesso in

STRUMENTI - OPZIONI - ORTOGRAFIA E GRAMMATICA
DIZIONARI PERSONALIZZATI - NUOVO

Basterà effettuare quindi una copia dei file .DIC .