I am seeing different behaviour when running prunsrv either as an Administrator or not. I have seen this in the past and it has bothered me, but I thought it was about time to get to the bottom of it!
Starting from a clean install of Windows 2012 Server Base, if I login as my user account `aretter` which is a member-of the `Administrators` group... 1. Launch "Command Prompt" from the Windows Start Menu, then execute `prunsrv.exe //?`. I get a dialog asking if I want to allow the program to make changes to my computer, clicking "Yes" then briefly flashes a second black console screen before returning me to the original cmd.exe with absolutely no output, i.e. I see just this on the cmd.exe c:\tools\bin>prunsrv.exe //? c:\tools\bin> 2. Right-click on "Command Prompt" in the Windows Start Menu, and click "Run as adminstrator", accept the warning, then execute `prunsrv.exe //?`. I get no security dialog, and I get the expected help message printed on the console: C:\Program Files\FusionDB Server\bin>prunsrv.exe //? Usage: prunsrv command [ServiceName] [--options] Commands: help This page install [ServiceName] Install Service update [ServiceName] Update Service parameters delete [ServiceName] Delete Service start [ServiceName] Start Service stop [ServiceName] Stop Service run [ServiceName] Run Service as console application pause [Num Seconds] Sleep for n Seconds (defaults to 60) version Display version Options: ... So I am wondering what the difference is, and why I don't get anything in (1)? Do you have to run prunsrv as THE Administrator? Thanks Adam. -- Adam Retter skype: adam.retter tweet: adamretter http://www.adamretter.org.uk --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
