Service(Process)Installer should support virtual and managed service accounts - by J Stangroome

Status : 

  Deferred<br /><br />
		The product team has reviewed this issue and has deferred it for consideration at a later time.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


4
0
Sign in
to vote
ID 795196 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 7/28/2013 12:15:01 AM
Access Restriction Public

Description

The System.ServiceProcess.ServiceProcessInstaller and ServiceInstaller classes do not support virtual accounts (eg NT SERVICE\servicename) or Managed Service Accounts (Group or Standalone).

ServiceInstaller.Install calls the CreateService win32 API which requires that the Password parameter be passed as NULL for virtual or managed accounts. Unfortunately there is no valid code path which allows the Password to be NULL while specifying a Username for a virtual or managed account.
Sign in to post a comment.
Posted by Adam Joseph Stone on 1/2/2015 at 7:37 AM
I second this. Managed service accounts and group managed service accounts have a lot of potential to be useful, but failure to support them via System.ServiceProcess.ServiceProcessInstaller represents a pretty fundamental roadblock.
Posted by Microsoft on 8/5/2013 at 4:29 PM
Hi J Stangroome

Thank you for your feedback.

We are not going to be able to address this issue in our next release due to other priorities, however we have logged it and we will continue thinking about addressing it in a future release.

Regards,
Alex Ghiondea
.NET Framework team
Posted by Microsoft on 7/29/2013 at 11:59 PM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by J Stangroome on 7/29/2013 at 9:31 PM
Demo project attached.
Posted by Microsoft on 7/29/2013 at 7:28 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by MS-Moderator07 on 7/28/2013 at 9:04 PM
Thank you for your feedback, We are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly (http://support.microsoft.com/)