Invalid login credentials

%3CLINGO-SUB%20id%3D%22lingo-sub-79877%22%20slang%3D%22en-US%22%3EInvalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-79877%22%20slang%3D%22en-US%22%3E%3CP%3EAzure%20Host%20server%20setup%20and%20ready%20for%20use%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20remote%20desktop%20get%20to%20final%20screen%20of%20negotiating%20credentials%26nbsp%3B%3C%2FP%3E%3CP%3Eand%26nbsp%3BInvalid%20login%20credentials%20please%20re-enter%20username%20and%20password%20is%20the%20message%20I%20keep%20getting%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-79877%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-171543%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-171543%22%20slang%3D%22en-US%22%3EI%20had%20this%20issue%20the%20second%20time%20I%20tried%20to%20access%20my%20(shut%20down%20and%20restarted)%20VM%20-%20but%20it%20was%20because%20I%20was%20using%20an%20RDP%20file%20from%20before%20and%20I%20hadn't%20realised%20that%20the%20DNS%20gets%20reallocated%20(of%20course%20it%20does!).%20Solution%20was%20to%20set%20up%20a%20'DNS%20name%20label'%20and%20you%20then%20endup%20with%20e.g.%20myvm.uksouth.cloudapp.azure.com%20which%20auto%20routes%20each%20time.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80963%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80963%22%20slang%3D%22en-US%22%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80962%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80962%22%20slang%3D%22en-US%22%3E%3CP%3EI%20did%20the%20installation%20over%20and%20got%20in%20without%20an%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80917%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80917%22%20slang%3D%22en-US%22%3EAnytime%2C%20did%20you%20access%20the%20current%20installation%20or%20did%20you%20start%20over%20%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80907%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80907%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20all%20your%20help%20I%20was%20able%20to%20log%20in.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80571%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80571%22%20slang%3D%22en-US%22%3E%3CP%3EOk%2C%20remeber%20that%20the%20deployment%20you%20are%20using%20gives%20you%20a%20local%20login.%3C%2FP%3E%3CP%3EBut%20the%20machine%20is%20also%20a%20domain%20controller%2C%20so%20you%20have%20to%20specificy%20a%20domain%20user%20for%20login%20or%20try%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CCOMPUTERNAME%3E%5C%3CUSERNAME%3E%3C%2FUSERNAME%3E%3C%2FCOMPUTERNAME%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80552%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80552%22%20slang%3D%22en-US%22%3E%3CP%3EI%20believe%20this%20is%20the%20orgin%20of%20my%20problem.%3C%2FP%3E%3CP%3EDuring%20the%20installation%20process%20I%20was%20unable%20to%20get%20the%20serve%20to%20accept%20my%20password%20I%20choose.%3C%2FP%3E%3CP%3EMy%20Apple%20OS%20suggested%20one%20for%20me%20and%20I%20accepted%20it%20without%20recording%20and%20the%20server%20accepted%20it%20also.%3C%2FP%3E%3CP%3ELater%20I%20earned%20more%20understanding%20of%20what%20was%20needed%20to%20create%20a%20password%20that%20I%20would%20remember.%3C%2FP%3E%3CP%3ESince%20losing%20orginal%20password%2C%20resetting%20password%20does%20not%20fix%20my%20login%20issue.%3C%2FP%3E%3CP%3EMy%20next%20course%20of%20action%20that%20I%20am%20going%20to%20try%20is%20to%20delete%20my%20Laas%20infastructure%20and%20build%20a%20new%20one%20using%20the%20understanding%20that%20I%20have%20earned%20recentlt%20and%20this%20link%20you%20sent%20me%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fremote%2Fremote-desktop-services%2Frds-in-azure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fremote%2Fremote-desktop-services%2Frds-in-azure%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80547%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80547%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20this%20confirms%20that%20you%20are%20indeed%20running%20an%20IaaS%20infrastructure.%3C%2FP%3E%3CP%3EThe%20pictures%20you%20sent%20me%20is%20of%20a%20Single%20VM%20in%20azure.%20try%20mstsc.exe%20%2Fconsole%2C%20connect%20to%20the%20ip%20of%20the%20VM%20and%20use%20the%20username%20and%20password%20you%20specified%20during%20the%20installation%20process%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80545%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80545%22%20slang%3D%22en-US%22%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80544%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80544%22%20slang%3D%22en-US%22%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80543%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80543%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20will%20take%20me%20like%205%20hours%20to%20confirm%20if%20your%20last%20reply%20worked%20for%20me%20or%20not.%3C%2FP%3E%3CP%3EBut%20in%20effort%20to%20help%20you%20help%20me%20better%20here%20is%20the%20screen%20shot%20you%20requested%20plus%20more.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80533%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80533%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20unaware%20of%20a%20product%20called%26nbsp%3B%3CSPAN%3EAzure%20VDI%20Cloud%20for%20Desktop%20Virtualization.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20link%20you%20provided%20just%20refers%20to%20running%20a%20VDI%20infrastrcture%20on%202016%20servers.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHow%20did%20you%20deploy%20the%20VDI%20infrastrcture%3F%20right%20now%20im%20guessing%20its%20just%20IaaS%20machines.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EThere%20is%20a%20deployment%20package%20defined%20in%20the%20market%20place%20that%20uses%20ARM%20templates%20to%20help%20you%20deploy%20the%20infrastructure.%20this%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows-server%2Fremote%2Fremote-desktop-services%2Frds-in-azure%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Elink%3C%2FA%3E%20would%20describe%20that%20process%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ethe%20market%20place%20would%20have%20asked%20you%20the%20following%3A%3C%2FSPAN%3E%3C%2FP%3E%3CUL%3E%3CLI%3EAdministrator%20user%20name%20and%20password.%20This%20is%20a%20new%20user%20that%20will%20manage%20the%20deployment.%3C%2FLI%3E%3CLI%3EDNS%20name%20and%20AD%20domain%20name.%20These%20are%20NEW%20resources%20that%20are%20created.%20Make%20sure%20the%20names%20are%20meaningful.%3C%2FLI%3E%3CLI%3EVM%20size.%20You%20get%20to%20choose%20the%20size%20of%20VMs%20to%20use%20for%20the%20RDSH%20endpoints.%20You%20can%20also%20manually%20change%20the%20sizes%20after%20the%20initial%20deployment%20to%20help%20you%20optimize%20the%20VMs%20for%20your%20workloads%20and%20for%20cost.%3C%2FLI%3E%3C%2FUL%3E%3CP%3EBut%20this%20would%20not%20intergrate%20with%20you%20current%20directory%2C%20also%20as%20an%20administrator%20you%20may%20need%20to%20connect%20using%20%2Fconsole%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eif%20i%20misunderstood%2C%20perhaps%20you%20could%20provide%20screen%20shot%20of%20the%20deployed%20resources%20in%20azure%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80525%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80525%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F43428%22%20target%3D%22_blank%22%3EKent%20Gaardmand%3C%2FA%3E%3A%3C%2FP%3E%3CP%3EI%20tried%20that%20also%20several%20times%20before%20posting%20and%20it%20did%20not%20work.%3C%2FP%3E%3CP%3EI%20hope%20below%20give%20you%20the%20clarity%20you%20where%20looking%20for%20so%20that%20you%20can%20help%20further%20if%20you%20can.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20specs%20are%3A%3C%2FP%3E%3CP%3EMac%20Book%20Pro%20with%20Apple%20OS%3C%2FP%3E%3CP%3E(MRD)%20Microsoft%20Remote%20Desktop%20App%20from%20App%20Store%3C%2FP%3E%3CP%3EAzure%20VDI%20Cloud%20for%20Desktop%20Virtualization%26nbsp%3B%3C%2FP%3E%3CP%3E*Those%20specs%20should%20work%20seamlessly%20like%20they%20advertised%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fcloud-platform%2Fdesktop-virtualization%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fcloud-platform%2Fdesktop-virtualization%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-80410%22%20slang%3D%22en-US%22%3ERe%3A%20Invalid%20login%20credentials%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-80410%22%20slang%3D%22en-US%22%3E%3CP%3ETo%20clarify.%3C%2FP%3E%3CUL%3E%3CLI%3Eyou%20have%20a%20Windows%20based%20VM%20in%20Azure%3C%2FLI%3E%3CLI%3EWhen%20you%20try%20to%20RDP%20to%20the%20VM%2C%20you%20are%20told%20the%20password%20is%20incorrect.%3C%2FLI%3E%3C%2FUL%3E%3CP%3Eyou%20have%20an%20option%20via%20the%20portal%20to%20reset%20the%20password%2C%20this%20requires%20the%20VM%20agent%20to%20be%20installed.%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20211px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F16166i156622269CDAC344%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Untitled.png%22%20title%3D%22Untitled.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Azure Host server setup and ready for use 

Microsoft remote desktop get to final screen of negotiating credentials 

and Invalid login credentials please re-enter username and password is the message I keep getting 

14 Replies
Highlighted

To clarify.

  • you have a Windows based VM in Azure
  • When you try to RDP to the VM, you are told the password is incorrect.

you have an option via the portal to reset the password, this requires the VM agent to be installed.

Untitled.png

Highlighted

Kent Gaardmand:

I tried that also several times before posting and it did not work.

I hope below give you the clarity you where looking for so that you can help further if you can.

 

My specs are:

Mac Book Pro with Apple OS

(MRD) Microsoft Remote Desktop App from App Store

Azure VDI Cloud for Desktop Virtualization 

*Those specs should work seamlessly like they advertised: https://www.microsoft.com/en-us/cloud-platform/desktop-virtualization

Highlighted

I am unaware of a product called Azure VDI Cloud for Desktop Virtualization.

The link you provided just refers to running a VDI infrastrcture on 2016 servers.

 

How did you deploy the VDI infrastrcture? right now im guessing its just IaaS machines.

There is a deployment package defined in the market place that uses ARM templates to help you deploy the infrastructure. this link would describe that process

 

the market place would have asked you the following:

  • Administrator user name and password. This is a new user that will manage the deployment.
  • DNS name and AD domain name. These are NEW resources that are created. Make sure the names are meaningful.
  • VM size. You get to choose the size of VMs to use for the RDSH endpoints. You can also manually change the sizes after the initial deployment to help you optimize the VMs for your workloads and for cost.

But this would not intergrate with you current directory, also as an administrator you may need to connect using /console

 

 

if i misunderstood, perhaps you could provide screen shot of the deployed resources in azure ?

Highlighted

It will take me like 5 hours to confirm if your last reply worked for me or not.

But in effort to help you help me better here is the screen shot you requested plus more.

Highlighted
 
Highlighted
 
Highlighted

Thanks this confirms that you are indeed running an IaaS infrastructure.

The pictures you sent me is of a Single VM in azure. try mstsc.exe /console, connect to the ip of the VM and use the username and password you specified during the installation process 

Highlighted

I believe this is the orgin of my problem.

During the installation process I was unable to get the serve to accept my password I choose.

My Apple OS suggested one for me and I accepted it without recording and the server accepted it also.

Later I earned more understanding of what was needed to create a password that I would remember.

Since losing orginal password, resetting password does not fix my login issue.

My next course of action that I am going to try is to delete my Laas infastructure and build a new one using the understanding that I have earned recentlt and this link you sent me https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/rds-in-azure

 

 

 

 

Highlighted

Ok, remeber that the deployment you are using gives you a local login.

But the machine is also a domain controller, so you have to specificy a domain user for login or try:

 

<computername>\<username>

Highlighted

Thanks for all your help I was able to log in.

Highlighted
Anytime, did you access the current installation or did you start over ?
Highlighted

I did the installation over and got in without an issue.

 

Highlighted
 
Highlighted
I had this issue the second time I tried to access my (shut down and restarted) VM - but it was because I was using an RDP file from before and I hadn't realised that the DNS gets reallocated (of course it does!). Solution was to set up a 'DNS name label' and you then endup with e.g. myvm.uksouth.cloudapp.azure.com which auto routes each time.