Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2437
  • Last Modified:

2012 STD - Add RDP Role, Failure

ON 2012 STD (not r2)  Server Trying to Add the RDP Role (Session Based) get the following error.  How do I Specifically make the change needed to get around this.  Thanks.


Event 7041

The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
 
Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
 
This service account does not have the required user right "Log on as a service."
 
User Action
 
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user right is assigned to the Cluster service account on all nodes in the cluster.
 
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated with this node might be removing the right.
0
howmad2
Asked:
howmad2
  • 6
  • 4
1 Solution
 
Cliff GaliherCommented:
That is one of the most descriptive error messages you can get. The "user action" section tells you what to do and even suggests what tool to use. If you launch the local security policy as it suggests, there is a list of various security privileges, and one of them will be "log on as a service." It is actually pretty tough to get more detailed than that error message already is.
0
 
howmad2Author Commented:
The 2012 Server is on a domain as a member server.  GPEdit from the local server has the Log on as a Service for editing grayed out.  

On the DC Group Policy Management and edited the default domain policy  / Security Settings / Local Policy / User Right Assignment / Log On as  a Service /  - was able to add the NetWork Service user and GPUpdate / Force.  

Adding Remote Desktop / Session Host fails the same way...
0
 
Cliff GaliherCommented:
If you look at the error, what needs the permissions is a SQL service account, not the network service. NT does not stand for network, it is the standard naming for all service accounts and the naming is a throwback to Windows NT some 20+ years ago.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
howmad2Author Commented:
Cliff.  I (really) appreciate you patience....in my case...looking at my original post....what is the name of the SQL Service account and where can I find it...
0
 
Cliff GaliherCommented:
account: NT SERVICE\MSSQL$MICROSOFT##WID
0
 
howmad2Author Commented:
where do I find NT SERVICE\MSSQL$MICROSOFT##WID and what permission do I add.  Thank You.
0
 
Cliff GaliherCommented:
You give it the logon as service right. It should be an account already present on the local server.
0
 
howmad2Author Commented:
if you mean on the 2012 server intended to be the RDP server......under Computer Management  / Users......  there is no user called  MSSQL$MICROSOFT##WID
0
 
howmad2Author Commented:
what was needed was go to the DC.  Under Group Policy Management, Group Policy Objects, Default Domain Policy, ..... Local Policy, User Right Assignment, Log On As a Service,  I Added "NT Service/All Services".  GPUpdate/force and DC and New RDP server and run wizard Again.  

Thanks for staying with me on this..
0
 
howmad2Author Commented:
Found Answer on my own.  Responses didn't solve issue but were appreciated.
0

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now