This isn't a Setupbuilder problem per se, but I'm hoping someone here
might have some advice for me.

We have a service deployed that has been running under the Local
System account since the beginning (years and years). It was always
okay because everything that it did was local to the server. Now we
need to be able to access network paths via UNC paths that don't
support a NULL session. So we need to use a different account than
Local System.

My problem is that we need to provide the username/password for the
service in order to install it under another account. I would rather
avoid having to ask to become a middleman app (unless your app is a
girl) for a user's Windows credentials, as we're on some pretty secure
sites.

I'm thinking of leaving my SB Service Installation as a SYSTEM, and
then letting the system admin change the service's user/pass via the
system's services UI.

I guess another option could be to add another user on the fly just
for this service, but that seems even less polite than asking for a
user's login credentials.

What do other folks do?

Is there a way to call up the service properties window directly?
e.g., the update windows from the the services.msc. If I could do that
from my SB project, that would be cool.

Thanks.

Jeff Slarve
www.jssoftware.com
Twitter free since Jan 11, 2016
I'll search help files & Google for you.

Grammar troll's, are the worse.