Page 1 of 1

Service Name

Posted: Thu Jul 11, 2013 12:38 pm
by jhicks
I know you don't want feature requests but I'm going to make sort of one anyway. When admins work with services from the command line, we're use to short names with no spaces like lanmanserver, bits and alerter. Having a space in the name is a a little awkward. Displayname is just fine.

It might also be handy to have a service control option in the GUI to start, stop or restart the service.

Re: Service Name

Posted: Thu Jul 11, 2013 2:19 pm
by Alexander Riedel
I don't mind feature requests. Just as long as you don't mind if I ignore them :-)

No seriously, go ahead. Let us know what you want to see.

Re: Service Name

Posted: Mon Jul 15, 2013 2:18 pm
by jasonh@interfacett.com
jhicks wrote:I know you don't want feature requests but I'm going to make sort of one anyway. When admins work with services from the command line, we're use to short names with no spaces like lanmanserver, bits and alerter. Having a space in the name is a a little awkward. Displayname is just fine.

It might also be handy to have a service control option in the GUI to start, stop or restart the service.
He JEff, I didn;t understand the "spaces" thing -- can you give me an example.

Re: Service Name

Posted: Tue Jul 16, 2013 4:31 am
by jhicks
Jason, most service names since the days of NT are things like bits, lanmanserver or lanmanworkstation. Run Get-Service and you'll see the service names I'm talking about. In most admin situations it is this name which we use to control the service from the command line. However, some vendors have started introducing long service names that are essentially the same as their display name. Those become more awkward to work with.

Personally, I would prefer a service name like vrsvc or even versionrecall instead of the current "VersionRecall Service"