Aws Domain Controller
Hi Guys,
we have started to check PDQ deploy software to do deploys at the moment i am checking the trial enterprise but for I am not able to deploy anything...
Our Domain controller is a windows server 2012 R2 in AWS, i dont know why i cannot do the deploy to my test laptop which is domain joined ...i always get the following error
The network path was not found
Share: \\laptop.doman\ADMIN$
Thanks
-
Shan,
Did you install PDQ on your domain controller? I will say that is not exactly best practice but it might be ok for your environment if it's just a quick test.
Does your AWS domain controller have a public IP address or do you reach it via NAT or a reverse proxy or something like that?
-
shan khan were you successful in getting this working? We're in the middle of setting up AWS Managed AD and I was hoping to get licenses for PDQ Deploy and Inventory as I used them at my previous job and loved the software for automation.
Please let me know as we don't have any on prem Active Directory at all.
Shane Brigg Angus Lex Hansen @... - any input from you would be most welcome :-)
-
If you are working through public IPs, are you opening the proper ports in AWS to get to your server? How about on your site's firewall? That is unless it is a site-site vpn between AWS and your office
Look here for port info for PDQ: https://help.pdq.com/hc/en-us/articles/220533627-Windows-Firewall-Ports-and-Exceptions
-
I've never used AWS AD, but I suspect you might be running into the same issue as Azure AD. Credentials need to be able to run as a service for our applications to work, including the Deploy/Scan user. As far as I am aware, it is not currently possible to run services with Azure AD accounts. This is a Windows limitation, not a Deploy/Inventory one.
Please sign in to leave a comment.
Comments
7 comments