natjohn
asked on
RDS Install fails due to Powershell remoting not available
Ultimate goal is to have RDS running on server 2016. Per Experts advice, I have now re-created new physical server as Server 2016 standard running the Hyper-V role; created 1st vm as serverA running Server 2016 with roles of ADDC, DNS, DHCP; 2nd vm as serverB with Server 2016 and attempting to add RDS role quickstart deployment. I see this server but it states that cannot deploy because "unable to connect to server by using Windows Powershell remoting". Both servers are in same domain, can see one another, have only 1 user, administrator, so far, firewalls on both are turned off, tried Powershell Enable-psremoting -force on both. I am new to virtualization and don't know if I have missed steps in the setup of these 2 servers that would cause this issue? Are there networking issues I am missing? Where do I go from here? Any help is appreciated.
ASKER
I am trying to run the quickstart deployment on serverB remotely. All I have done on that particular server is name it and join it to the domain. I don't know what you mean by 'force enable parenting'. The results of powershell was that it was enabled. I agree on the normal deployments -that the wizards work. But I've done nothing to these 2 virtual machines. The only thing I had to do was put in the ip of the 2nd server of the 1st server which is the dns, so it would find it to join the domain. I then set it back to auto dns setting. And I activated Server 2016. I will go onsite and try the install. Are there other steps I should have done, or should do?
Parenting was autocorrect at its finest. Was supposed to say "psremote"
You added the -force flag which... On ANY powershell... Is usually neither required nor recommended. Many commands include it for various reasons (automation scripts mostly where transient errors can hang a script) but the same things that allow a script to continue can hide legitimate errors when running interactively.
Remote powershell isn't necessary if you are running the wizard on serverB (on the console or via RDP) and all roles are also going on serverB (the default for that wizard.). That it is failing indicates either a bad install or some early configuration you did is clobbering the default behavior. 3rd party antivirus and remote management tools are often culprits.
VMs are cheap and easy. I'd just spin up a new clean VM and try again.
Remote powershell isn't necessary if you are running the wizard on serverB (on the console or via RDP) and all roles are also going on serverB (the default for that wizard.). That it is failing indicates either a bad install or some early configuration you did is clobbering the default behavior. 3rd party antivirus and remote management tools are often culprits.
VMs are cheap and easy. I'd just spin up a new clean VM and try again.
ASKER
I see about the 'force' command. I did that after it failed the first time. When I typed in the powershell command, it did its work and came back to the prompt. It did not say 'psremote'. I will do just that: eliminate this vm and try again. Thanks and will let you know if this works!
ASKER
Well, no luck. Removed and reinstalled server; only user is administrator; on dashboard enabled remote management, remote desktop, corrected time zone, joined domain, disabled firewall. Started quickstart deployment, session based, begins then quickly fails on install of connection broker saying "the server is not operational". I have done no other steps and will see what your reply is. I am installing updates now. I can see all other machines in the domain and can browse the internet. What other suggestions are there, or angles to change? Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I disabled the firewall in case it would be an issue. Can certainly re-enable. I created a gen 2Vm with 10240mb memory and 400GB of space. I am changing no settings other than the location of the files and I placed them on host server c drive in folder called \vms. I have done nothing with any group policies, just created users in AD and joined them to default group of remote users and print operators. I do have teamviewer installed on the host. I installed the OS from a usb that I created from the dvd that came with server using Imgburn.
Why did you create a USB? Why not just mount the DVD directly in the guest? As counterproductive as this seems, also try reducing the amount of RAM in the guest. Go with 4 gigs or so. Disable dynamic memory if you've enabled it. Then retry the wizard and tell me exactly where it fails.
ASKER
Ok. Deleted vm; recreated with 4 RAM and never have selected dynamic memory, 400GB space, installed server2016 from the DVD; set time zone; put in dns ip to join domain, restarted and into domain; removed dns ip; started RDS deployment. Did remote desktop install; quickstart deployment; session-based; at server pool screen it shows just this virtual server and so kept the default of it being highlighted; on next screen did check mark in box to Restart destination server; clicked deploy and in a fraction of a second it says RD connection broker install fails "The server is not operational". Attached is a picture of the screen.
It does only pertain to this serverB, correct? not the others? I honestly am not doing anything else that I can notice.
Capture.PNG
It does only pertain to this serverB, correct? not the others? I honestly am not doing anything else that I can notice.
Capture.PNG
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I didn't think it was the "right" thing to do. So put it in and YES it is starting to install the connection broker! The install of RDS completed successfully. Thank you!! I will leave in that ip address.
In your opinion, which is the best server to place the data, quickbooks used by inhouse and remote users, and a piece of software which requires SQL Express - also be used by inhouse and remote users; host server, serverA running ADDC, DNS and DHCP, or serverB running RDS?
Really appreciate your expertise!!
In your opinion, which is the best server to place the data, quickbooks used by inhouse and remote users, and a piece of software which requires SQL Express - also be used by inhouse and remote users; host server, serverA running ADDC, DNS and DHCP, or serverB running RDS?
Really appreciate your expertise!!
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just what I was thinking. Thanks again for your expertise!
In a normal deployment you don't have to do any extra stuff. Install the machine. Join the domain. Run the wizard. It "just works." When it doesn't, it is usually because extra stuff was already done causing problems. Group policy, etc.