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/
Related
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.
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/
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.
When I login to "Windows Azure Management Portal" I get the following warning in the notification tray:
Autoscale could not be enabled for [cloudserivce]"
When I click I'm redirected to the Scale tab for the specified cloud service, with no more info.
The cloud service is configured to autoscale based on CPU (60-80 target) and between 2-10 instances.
Everything looks OK to me, so why do I get this warning, and what does it mean?
It's likely you've exceeded the quota for roles with autoscale enabled. If you share your subscription and deployment IDs with me (tabrezm[at]microsoft[dot]com), we can take a look. We're working on making the error messages exposed in the portal better for this.
After talking to Ilya and Tabrez we found the problem.
It turned out that the error message was misleading, and that it actually meant "auto-scale job failed to perform scale action". According to Ilya this is fixed (but not deployed)
I've tried to scale manually and got the following error:
The certificate with thumbprint XXXXXXXXXXXXX was not found.
A few days ago I've changed the SSL certificate thumbprint directly on the configuration tab of the Cloud Service, and then deleted the old certificate. This was reflected correct on our website. But we was also using this certificate for Remote Desktop. The running instances already had the old certificate installed, but Auto Scale was not able to install this certificate on new instances.
Thanks to Ilya and Tabrez for helping... great support.
I am getting the error as below in my Azure Virtual Machine when I save my vhd:-
Failed to capture image vmvhdtrialacc of virtual machine vmvhdalpha
Endpoint Not found: There was no endpoint listening at https://management.core.windows.net:8443/*GUID*/services/hostedservices/vmvhdalpha/deployments/vmvhdalpha/roleInstances/vmvhdalpha/Operations that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.
Any idea what could be wrong here?
Unfortunately your problem is a recently known issue with Windows Azure Virtual Machines, described as "still investigating status", in the following Windows Azure Virtual Machine Forums:
http://social.msdn.microsoft.com/Forums/en-US/WAVirtualMachinesforWindows/thread/29fc7e72-6c95-4704-bf79-b9aba562c6ad
My suggestion will be to submit your issues in the same forum and track the status of your problem in the above link.
Strangely enough I had a running VM, then added an SSL cert to a separate Cloud Service via the portal, and that seemed to doom my VM. It went into a stopped state, and when trying to start it received the error above. Only solution as mentioned in prior post's links, delete the VM (or delete the VM and clone new one from VHD).