I have spun up a Windows VM compute engine to host a software application(exe) from a 3rd party vendor.
Multiple users (>15) will need to use this application simultaneously so they will need to RDS into the VM through their user accounts.
We have set up Cloud IAP. Currently 2 users can access the VM simulatenously as is expected because the VM provides 2 RDS licenses.
We are trying to get more licenses but apparently an Azure AD is required for those licenses to work. Is there away to have more licenses without the Azure AD or without hosting a new AD on google?
I just want to be able to have >15 people simultaneously accessing the application on the server.
It is possible to configure Windows RDS without a domain, keep in mind that you need to purchase Device CAL's - User CALs can only be used in an AD environment; and you are limiting your options for high availability.Check the following links for guidance:
Deploying a RDSH Server in a Workgroup – RDS 2012 R2
Windows Server 2019 Remote Desktop Services without Domain
RDS Without Domain
I have a instance with Windows Server 2012 R2 Standard in AWS. the instances is a m4.large and run a application for locations users.
The instances is in on-demand model.
i know that AWS gives me the license, but when i access the instances, i see a message requesting a license.
enter image description here
In the instance I have applications but I don't want to relaunch instances.
Anyone know the solution?
The situation is:
- There is an EC2 instance with Windows Server 2012 R2, and the Administrator's password is lost.
- There is no other user accessible either.
- It is not an imported ovf instance, so there is no way to export it (or is there?).
- There is no EC2 Agent installed on the instance.
- I thought about using Offline NT Password & Registry Editor, but I don't know how to boot into it from an EC2 Instance.
What can I do to restore the password?
AWS has documented the process, but there are certain requirements:
http://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/ResettingAdminPassword_EC2Config.html
If you created the instance from an imported image, or don't have EC2Config running, you may be out of luck.
You can still detach the volume from the instance, associate it with another instance, mount it, and from there extract any data you may need.
My Azure marketplace VM image was removed suddenly by Microsoft due to WannaCry vulnerability.
I'm trying to run Certification Test Tool 1.2 for Azure Certified on a new VM created from the new patched image.
I am logged in as a local administrator and running the tool on the VM as per the documentation: "The certification tool runs on a running VM, provisioned from your user VM image, to ensure that the VM image is compatible with Microsoft Azure."
I've tried running the tool on default Classic (not Azure Resource Manager) Windows Server 2012 R2 Datacenter and Windows Server 2016 Datacenter VMs.
I've tried turning the Windows firewall and UAC off.
I have not tried changing the firewall rules on Azure for the VM because: "When you create a Windows virtual machine in the Azure classic portal, common endpoints like those for Remote Desktop and Windows PowerShell Remoting are typically created for you automatically."
Here is the log created from running the tool on a brand new Azure Classic VM (with WannaCry patches applied):
5/18/2017 6:23:22 AM
Log generated by Certification Test Tool for Azure Certified
Test name: ****** Test Date :5/18/2017 6:23:22 AM Tested on: ******.cloudapp.net Test for: Microsoft Azure Test in: Windows Server
5/18/2017 6:23:24 AM
Test case/Verification: TestConnection
Description: Instantiates connection to the specified VM.
Connection Attempt: 1 Connecting to the Azure VM.... ******.cloudapp.net Error in connecting to the VM. Reason for not connecting to the VM : System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server ******.cloudapp.net failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic. at System.Management.Automation.Runspaces.AsyncResult.EndInvoke() at System.Management.Automation.Runspaces.Internal.RunspacePoolInternal.EndOpen(IAsyncResult asyncResult) at System.Management.Automation.Runspaces.Internal.RemoteRunspacePoolInternal.Open() at System.Management.Automation.RemoteRunspace.Open() at WindowsAddin.PSConnection.OpenSession() ----------------------------------------------------------------->
EDIT: Add a couple links.
I did manage to connect and run the tool, the trick was not to run it on the machine. You must run it from a remote machine. The tool denies access to itself.
I am trying to Remote Desktop onto an Azure instance from Mac OS X, but can't find a tool that allows me to do it. Address and username is fine, but none of the clients seem to have the capabilities to include the instance information.
I have so far tried the Miscrosoft RDC and CoRD but to no avail.
Has anyone succeeded in using RDP to an Azure instance on a Mac?
By default, you can't connect to an Azure Windows server except through the Windows Remote Desktop client.
To connect from OS X, whether through CoRD or the Microsoft Remote Desktop client for Mac, you need to turn off network level authentication:
Connect to the Azure server using the Remote Desktop client on a Windows machine
Under Control Panel, go to System, then open 'Advanced system settings'
On the Remote tab, uncheck "Allow connections only from computers running Remote Desktop with Network Level Authentication (recommended)"
Re-connect from OS X
you need to create connect from microsoft remote desktop on mac
add ip, user, password
and you can connect now
if you still can't connect , check your azure endpoint setting
set the port that your firewall can pass
I have the same problem with you, and I think there is nothing to do with the network level authentication. The main reason is the default remote desktop app will connecting through port 3389, but your VM's default endpoint set another public port, here is what i do to solve it:
Download the latest version of Microsoft Remote Desktop app at Mac app store.
Add the port after your connection's DOMAIN/IP like yourvmdomain.com:yourpublicport. You will find the public port on endpoint setting tab. To me, the public port of Remote Desktop is 58494, so the connection will be xx.xx.xx.xx:58494.
This works for me.
Download the new Microsoft remote desktop client, which will allow you to connect to Azure instances without changing the configuration.
(As suggested in the comment from Kim Burgess)
It's tricky to connect to an Azure Cloud Service (aka Web or Worker Role) from a Mac, since PaaS instances sit behind a load balancer. You therefore need to specify which instance to connect to via cookies.
Royal TS supports cookies, so I got this working:
Install Royal TS free version (http://www.royalapplications.com/ts/osx/features)
Add the Remote Desktop plugin
Create new connection
Enter usual details (server/username/password)
Advanced > Connection > Load Balance Info > Cookie: mstshash=Your.Server#Your.Server_IN_0
This cookie info is available in the RDP file you can download for your instance from the Azure management portal (just open it in a text editor).
I use the Microsoft Remote Desktop application on OSX to connect to an Azure VM.
Recently I set up a VM from a Windows machine and was able to connect successfully using the admin username and password, but found that I had to reset the admin password to connect from OSX.
You can easily reset the password from the Azure portal for the VM. Go to "Support + troubleshooting/Reset Password".
I often have to enter the user name in the form:
PC name: xxx.xxx.xxx.xxx:yyyyy
Gateway: No gateway configured
User name: localhost\user.name
Hope that helps someone.
To access Azure instances from a MAC download Microsoft Remote Desktop client in Appstore. The default RDP client Azure provides doesnt work on a MAC. Worked for me
Check that your Networking Inbound Port rules (typically port 3389, but will change behind a load balancer) for the Azure VM allow you in.