RDS Remote Gateway Service not installing

Just for the record, the connection broker and the gateway are two different roles. Your subject says gateway, but the error is shows a failing connection broker install.

With that said, the error pictures is (as I'm sure you realized) not going to help you. It lets you know *that* the deployment failed, but not the why. For that, you should view the event logs on the server you attempted to deploy the RDCB role to. The failure should have logged more detailed events.

this is one of the error in the event logs
i have try all users i can imagin still not work

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.

By default, when you install the Windows Internal Database, the account is created and granted those rights. But if it was already installed, or if you have a group policy overriding the defaults, then the WID will fail to start. It doesn't matter what user you use to install the role. THAT isn't the problem. The problem is that the database itself runs with its own unique user, and that unique user doesn't have the necessary permissions.  You can uninstall and reinstall the WID role/feature. Or you can manually add that account to the necessary permissions in the local security policy. And you may need to adjust any high-security group policies that may be superseding the local policy to allow that account to run as a service.

hi,

interesting how can i do this

"Or you can manually add that account to the necessary permissions in the local security policy."

thanks,

cgaliher, would you recommend removing the WID, manually adding a new account with these permissions to the local security policy, or maybe just starting from scratch with a new OS installation?

if you could provide some guidance on the suggestion for "manually adding that account to the necessary permissions in the local security policy.", it would be great. thanks again

base on the recommendations i did this changes and got the installation done

http://www.smallbusinesstech.net/more-complicated-instructions/windows/fixing-windows-internal-database-installation-error-on-windows-server-2012

thanks,