Can't log in to Azure VM - azure

I have an Windows 8.1 VM on Azure that I've been successfully using for months. I login via the admin account that I originally set up.
Today my RDP sessions keep telling me that the password is incorrect.
So I used the Azure Portal to reset the password, but still can't get in. I've tried waiting for a while (in case updates were being installed) and I've restarted the machine.
I notice that the Portal UI says 'Provide a new user name for the built-in administrator account'. I've tried changing it with no luck.
Help?

Azure must have changed the username requirement.
It works if I login with host\username
Connect Azure RDP, "The logon attempt failed"

SOLUTION: instead of copy-paste, type the password
This solution comes from teh answer of another similar question Connect Azure RDP, “The logon attempt failed”. You can have a try.

Related

SQL Data Sync Agent 2.0 install error system services

I am trying to install SQL Data Sync Agent 2.0 but I got this install error
I am running virtual machines with Hyper-V.
I tried in a windows server 2016 and a windows 10. Up to date.
I added the account to log as a windows service.
What could be the issue?
Thanks
I have fixed this issue by adding Computer-name in front of the Username.
Make sure the following,
Username and password are correct.
Prefix the computer name along with the username (Eg: MYPC\user).
You can find the computer name on This PC's properties.
This error occurs in two situations:
User name and/or password are incorrect. Do not use the Windows Live login to install the agent use (create) a local Windows account to install the agent.
The specified user account does not have sufficient privileges to logon as a service, but you told us you did this already. Anyway please verify the following steps:
To Grant logon-as-a-service credentials to the user account please do the following steps:
Navigate to Start > Control Panel > Administrative Tools > Local Security Policy > Local Policy > User Rights Management.
Find and click the Logon as a service entry.
Add the user account in the Logon as a service Properties dialog.
Click Apply then OK.
Close the windows.
Some more suggestions:
Install the client agent using the least privilege account with network service access.
It is best if the client agent is installed on a computer separate from your on premises SQL Server computer.

I am not able to log into my azure VM

I am not able to login my Azure VM. I have reset the password through azure portal but it is still not logging in. Previously, it used to log in and now it is showing following error :
An authentication error has occurred.
The function requested is not supported"
I have other VM which are logging in fine as before. Please help.
Check out the following link.
This is due to a combination of three factors:
You activated NLA on your target computer
The target computer is not patched for CVE-2018-0886
You enforced the Force updated clients or Mitigated parameters on the source computer
https://itluke.online/2018/03/29/solved-authentication-error-function-not-supported/

Azure "Your credentials did not work"

Suddenly I'm encountering the dreaded "Your credentials did not work" error connecting to my VM. I've tried several different accounts, I've made sure of the password (I use a password management tool and the password used to work fine). I tried resetting it via the management console and I also tried resetting RDP via the console. Nothing.
The only thing that changed is that I rebooted the VM once.
Any other steps I can take to troubleshoot it? Is my only option to save the VHD and create a new VM?
you can reset you password using the steps given here https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-windows-reset-rdp/

Azure Remote Desktop - Access Denied

I'm currently facing an Access Denied error while connecting to an Azure VM. This VM is registered in an Active Directry. When I log with the AD credentials, I get an "Access Denied" error message with a "Ok" button without any other text on the screen. I never faced this issue before. The maching was working perfectly last week...
Do you have any idea about this issue ?
Thanks for your help
Access Denied Error Screenshot
Can you still access the VM and its using your Azure Portal login? If so, try adding the AD user via RDP.
Go to Computer Mgmt on the VM via Remote Desktop
Expand the list of Remote Desktop Users.
Select the user(s) to add.
See details in the MSDN thread:
https://social.msdn.microsoft.com/Forums/en-US/9ebce1bb-2aa0-4bb0-adc7-d1e229c5ee9e/add-user-to-remote-desktop-group-in-azure-vm?forum=WAVirtualMachinesforWindows
If you're having RDP issues with the primary user account, check the Settings blade of your VM in the Azure Portal, and look at the Users list under Resource Management.
Hope that helps!
I had the same issue, in my case it was related to Terminal Service Licensing.
First save a local copy of the RDP file from the portal and run this command at a PowerShell command prompt to connect. This will disable licensing for just that connection:
mstsc <File name>.RDP /admin
after you are able to connect then open the Event Viewer an look for an Event with ID 4105 in WIndows Logs > System. this event should appear every time a logging was attempted.
If that is the case, follow this steps to solve the issue
Event ID 4105 — Terminal Services Per User Client Access License Tracking and Reporting
Hope this helps.

Azure publish can't use saved RDP password?

Every time we publish our Azure project (all machines in our team/at home as well) it always asks us to re-enter our RDP password.
This is a bit annoying as it means the files check out and we have to keep entering the password.
The error message is "The existing Remote Desktop credentials could not be loaded in this environment. Re-enter the desired password".
Anyone got any idea what is up? Its a bit frustrating.
Answer was because we were publishing to different instances with the same configuration and not using a fixed RDP cert. It was re-generating the certificate each time.
If you have this problem upload the cert to each cloud service you are deploying to and use the one cert across all deployments.

Resources