Sysinternals Homepage
Forum Home Forum Home > Sysinternals Utilities > PsTools
  New Posts New Posts RSS Feed - >>> EULA prompt when running PSTools <<<
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Topic Closed>>> EULA prompt when running PSTools <<<

 Post Reply Post Reply Page  <1 45678 10>
Author
Message
Karlchen View Drop Down
Senior Member
Senior Member
Avatar

Joined: 18 June 2005
Location: Germany
Status: Offline
Points: 5131
Direct Link To This Post Posted: 10 April 2007 at 2:36pm
Good evening, Rodney.

The 2 programme authors, Mark and Bryce, do monitor this forum. So they read our thoughts about the EULA prompt and its negative impact on scripts, be assured.

So writing a petition will not be required in order to let them know.

I will refrain from speculating on both open questions:
+ why the EULA acceptance dialogue was added to the command line programmes
+ how good or bad chances are it will be removed again

Karl
Back to Top
brikface2 View Drop Down
Newbie
Newbie
Avatar

Joined: 04 May 2007
Status: Offline
Points: 1
Direct Link To This Post Posted: 14 May 2007 at 5:21pm
I just want to add another voice urging Microsoft to either drop the EULA for all Windows Sysinternals or to show EULA only once upon installation (or unzipping). I haven't posted to these forums or the old Sysinternals forums, but I have avidly lurked and am responsible for dozens of fellow System Administrators adopting the tools. A BIG factor in my recommending the tools to so many peers was their *pure* commandline nature. I, like many others, was sort of shocked but not shocked when Microsoft immediately violated that pure nature upon acquisition from Messrs. Russinovich and Solomon by adding a GUI dialogbox that, at one stroke, broke thousands of non-interactive scripts-- some of them essential to the basic operation of entire LANs and WANs... Let's please be consistent: either dispense with this EULA for the Sysinternals executables or pop up an EULA every time anyone opens a CMD window, and again when they type DIR and hit enter, and again when they type CD [path] and hit enter, etc,., ad nauseam. Dead.

Come on now, guys Wink.


.
Back to Top
fruiz View Drop Down
Newbie
Newbie
Avatar

Joined: 09 November 2006
Status: Offline
Points: 4
Direct Link To This Post Posted: 18 May 2007 at 11:28pm
I don't want to get off on a rant here, but how, oh how do you make Microsoft understand the magnitude of this blunder without resorting to a Lewis Black impersonation? Think of the most grievous blasphemy anyone can inflict on one's personal mythology, and then multiply that by a googol...
 
Mark, you are obviously extremely smart and astronomically intelligent... Why did you let this happen?
 
And Microsoft, shame on you. Shame, shame on you. To quote a great writer, you have forgotten the face of your fathers. You have displayed what can only be adequately explained by either dull malice or acute idiocy. Even deciding by flipping a coin, the statistics are not in your favor.
 
Of course, this is just my opinon. I could be wrong.
Back to Top
xiris View Drop Down
Newbie
Newbie


Joined: 20 June 2007
Status: Offline
Points: 2
Direct Link To This Post Posted: 20 June 2007 at 9:07am
The current 'listdlls' 2.25 still gives the EULA Window.
Will there be a cure for t this tool as well?

TIA,
   xiris
Back to Top
Hilitec View Drop Down
Newbie
Newbie
Avatar

Joined: 24 June 2007
Location: Switzerland
Status: Offline
Points: 5
Direct Link To This Post Posted: 24 June 2007 at 1:42pm
Hello,

Here is a trick for ListDlls:

Add this line in your script:

REG ADD HKCU\Software\Sysinternals\ListDlls /v EulaAccepted /t REG_DWORD /d 1 /f

It will add the correct Eula acceptation information in the registry.

REG.EXE is a native command in Windows XP. In Windows 2000, REG.EXE is available on the Windows installation CD-ROM, but has to be installed manually (on the CD-ROM run "\SUPPORT\TOOLS\SETUP.EXE"). For Microsoft Windows NT Server 4, the ressource kit also provides REG.EXE.

Hope it helps.

Best regards,

André

Technical blog (currently, only in french)



Edited by Hilitec - 24 June 2007 at 1:43pm
Back to Top
Hilitec View Drop Down
Newbie
Newbie
Avatar

Joined: 24 June 2007
Location: Switzerland
Status: Offline
Points: 5
Direct Link To This Post Posted: 24 June 2007 at 1:47pm
And it is the same for the other utilities Wink:

VolumeID
REG ADD HKCU\Software\Sysinternals\VolumeID /v EulaAccepted /t REG_DWORD /d 1 /f

RegMon
REG ADD HKCU\Software\Sysinternals\Regmon /v EulaAccepted /t REG_DWORD /d 1 /f

And so on...

Regards,

André

Back to Top
Santana View Drop Down
Newbie
Newbie
Avatar

Joined: 11 April 2007
Location: Germany
Status: Offline
Points: 21
Direct Link To This Post Posted: 24 June 2007 at 1:58pm
Hm, I think I remember having read something to this effect before.

Thank you for being prepared to share helpful ideas with us nonetheless, of course.

Santana

Back to Top
depriest View Drop Down
Newbie
Newbie
Avatar

Joined: 27 June 2007
Location: United States
Status: Offline
Points: 17
Direct Link To This Post Posted: 06 July 2007 at 1:21pm
Why can't the EULA message be something that is displayed on the command-line?

I have old MS-DOS programs that had no problem with that.

The little box, instead of popping up, was right there in the command.com window.

I'd get a [y] or [n] to whether or not I agreed and on it would go without pulling me from my command prompt.

I'm sure this can be done for these apps, too.

The end-user experience would look something like this:
Quote Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>psexec \\server ipconfig.exe
|=============================================================================|
|=| PsExec License Agreement                                                |=|
|=| You can also use the /accepteula command-line switch to accept the EULA.|=|
|=============================================================================|
|=| SYSINTERNALS SOFTWARE LICENSE TERMS                                     |=|
-- blah blah legal blah blah --
|=============================================================================|
|=| I accept the terms of this end-user license agreement: [Y]es or [N]o    |=|
|=============================================================================|
Y
PsExec v1.83 - Execute processes remotely
Copyright (C) 2001-2007 Mark Russinovich
Sysinternals - www.sysinternals.com



Windows 2000 IP Configuration

Ethernet adapter Local Area Connection:

        Connection-specific DNS Suffix  . : domain.com
        IP Address. . . . . . . . . . . . : 10.10.10.10
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 10.10.10.1
ipconfig.exe exited on ESECSRVB with error code 0.

C:\>


-Jason
Back to Top
molotov View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 October 2006
Status: Offline
Points: 17516
Direct Link To This Post Posted: 06 July 2007 at 1:36pm
Hi, Jason.
 
Quote Why can't the EULA message be something that is displayed on the command-line?
If I had to guess, I would say that things are they way they are because the GUI EULA code had to be written for the GUI tools, and it was quicker to make the command-line tools work with the already-written GUI EULA dialog than it would have been to write something specifically for the command-line tools.  But that is just what I said it was - my guess.  Embarrassed
Daily affirmation:
net helpmsg 4006
Back to Top
dcohn View Drop Down
Newbie
Newbie


Joined: 26 October 2006
Status: Offline
Points: 9
Direct Link To This Post Posted: 08 July 2007 at 2:11pm
I actually changed to beyondexec every time I have an issue now and I am still having issues crop up.  BeyondExec is better code anyway.

http://beyondlogic.org/consulting/remoteprocess/BeyondExec.htm



OK Now I am confused. why couldn't you change the script (yes a royal PIA to update all our scripts  I am using older versions of the code that did not need the eula)

psexec \\server ipconfig.exe
/accepteula

Please explain what someone will not write a single batch, or better yet a compiled EXE that contains all the eulas for every friggin Systinternals script now and forever.  Let us accept it once and then apply it tpo as many servers as we need to.

The Eula is done and legal.

Why are they  being so darn ridic about this.

I will bet my bottom dollar that if Gates himself knew that he had code out there that was causing this much havoc he would flip.

I am still finding scripts breaking today.  Stupid moron some of my people are they updated the damn utilities.  Not everyone is perfectly organized about everything.  That said it is the reason this has created such havoc for me. 

But I would never have changed had the original code not been screwed with as it was.  And intentionally screwed with.
Back to Top
 Post Reply Post Reply Page  <1 45678 10>
  Share Topic   

Forum Jump Forum Permissions View Drop Down