search

aws-quickstart / quickstart-microsoft-rdgateway

AWS Quick Start Team
Apache License 2.0
48 stars 87 forks source link

rdgw-domain.template error with certs #33

Open jamnds opened 3 years ago

jamnds commented 3 years ago

When using the rdgw-domain.template (alone or with an other quickstart) it gets to the point its creating instances to add to the autoscale group but never adds them to the autoscale group. The instance spins up and looks healthy then it terminates.

The only errors I see in the cloudwatch log group for the setupconfiguration in the stdout log it says "Failed to Initialize RDGW with Certs Access to the object at RDS:\GatewayServer\CAP\Default-CAP is denied for the cmdlet New-Item.The supplied value is not valid, or you do not have sufficient permissions." log location = 9d276536-b525-4171-9c0f-76a1722151da/i-005d83973982626ac/runPowerShellScript/stdout

The stderr says "failed to run commands: exit status 255"

I've been trying to work through the error but haven't been having any success. Note that this seems to have started sometime in the last 2 weeks-ish, in late october it was working fine. The 29th I think was the last time I ran it successfully.

jamnds commented 3 years ago

Deleted. Was incorrect. next post has better info.

jamnds commented 3 years ago

So it appears that the RDS:\GatewayServer\CAP (and RAP) paths dont seem to have anything in them.

I'm not sure what is supposed to be there but will see if I can figure it out.

mazayan commented 3 years ago

@jamnds did you ever resolve this issue? I am running into the same thing

jamnds commented 3 years ago

No i didnt, sorry. :(

herigb commented 3 years ago

I have experienced the same error and I have fix it adding the dhcp configuration with the domain and the ips of the de Active directory. not sure if also this solution can work for you.

https://docs.aws.amazon.com/directoryservice/latest/admin-guide/dhcp_options_set.html

aledindinelli commented 1 year ago

Same, I've encountered the same error and was able to resolve it by adding the DHCP configuration at the VPC level using the AD ips.