I have created an Azure VM for the purpose of testing a new installation process for my software. The VM is using Windows 10 Preview.
Yesterday I uploaded an ISO file which contained our software plus installers for SQL Server Express (various editions). (About 1.8 gb)
I ran our custom setup program which installs SQL express, restores a new user database, adds firewall exceptions etc. etc.
This morning I cannot RDP into that VM. The connection is made, but when I attempt to login, I am simply returned to the Windows Security Dialog, with the message "Your credentials did not work..."
I know I am typing the password correctly, I have double checked things like typos in the user name and password, Caps Lock is not on ;-) and so on.
This happened to a VM I had set up last week too, after a similar test and after attempting various options including resetting credentials using Powershell (found here) I accepted that I must have forgotten the password or done something wrong, so I started again.
Now the same things has happened I am wondering if that level of activity (uploading 1.8gb then running a setup which retrieved and installed .Net runtime 3.5) on an Azure VM that runs under an MSDN Premium subscription Azure account, caused the user account to be locked out for a period of time - have I hit some limit of uploads to that machine or activity or some other limit I'm not aware of?
Related
my organizations runs some applications that requires a 32 bit O.S.
We created a VM with Microsoft HyperV console managment that runs a Windows 10 32 bit O.S.
The problem we are facing is that we are able to log in with a Domain\Administrator account when setting up a new machine but when we try non admin accounts (which we have something like 100+ for our staff - which they are already using every day to log into their machines currently in used ) we get this error "The User Profile Service service failed the sign-in. User profile cannot be loaded". When looking at the user registry we see only 4 files and not 10+ as seen in some internet guide. In some cases we have multiple forlders pointing to the same account and in each of them we have a ProfileImagePath that goes: Domain"user".001 and .002 ecc. ecc. ecc.
I'm having trouble when creating a VM in Microsoft Azure using a custom windows image.
Issue
When connecting to the newly spawned VM using the credentials entered in Azure Portal, I get the following message :
The user account is currently disabled and cannot be used.
Running a Get-LocalAccount script using the "Run Command" menu of the Azure Portal I get the following output:
Name Enabled Description
---- ------- -----------
DefaultAccount False A user account managed by the system.
Guest False Built-in account for guest access to the computer/domain
myusername False Built-in account for administering the computer/domain
WDAGUtilityAccount False A user account managed and used by the system for Windows Defender Application
Workaround
If I use procedure from Azure VM connection error - The user account is currently disabled and cannot be used, I'm able to unlock the user and connect to the VM via RDP.
I also try creating a new user prior to sysprepping the VM so the local admin account is renamed and disable by Azure during VM creation but the user account created remain enabled.
Image Info
OS: Windows 10 LTSC 2019
Source: Custom deployed image used by my company. It was installed with an ISO on local HyperV machine, uploaded to Azure and SysPrep from a managed disk.
WindowsAzureVmAgent version 2.7.41491.949_191001-1418 installed on the VM prior to running sysprep.
Step Taken
Re-enabling the account and running Sysprep again to create a new snapshot does not fix the issue
Renaming the local administrator account prior to Sysprep the device does not have any effect.
Checked the local policies and nothing look unusual.
Found the solution with the help of Microsoft Azure support engineer. For a VM uploaded from on premise source, you would need to add a SetupComplete2.cmd and EnableLocalAdminAccount.ps1 in C:/Windows/OEM to unlock the user account automatically upon VM creation. Strangely enough this does not appear on anywhere on Microsoft's guideline on how to migrate a on-prem VM to Azure, but the official windows image from the Marketplace do have those 2 files that are run after Sysprep.
This blog article was also very useful and points towards the creation of a SetupComplete2.cmd https://matt.kotsenas.com/posts/azure-setupcomplete2
This is probably a basic question but all I am looking for in Azure is the ability to back up files on my Windows Server at a scheduled time. MS SQL, MySQL and Web Site Files.
I have created a Trial account and a Storage plan but need a pointer to which section of the Dashboard I should be visiting - it isn't immediately apparent!
I assume you are asking about backing up your Windows server running as a VM instance on Azure.
Below is the latest Azure VM backup guide from Microsoft.
Hope it helps!
Azure virtual machine back up
I'm having a pretty strange issue with Azure tools for VS 2013 (version 2.6). Whenever I try to sign in to my Azure subscription (e.g. from Server explorer or creating a new web role project) I get the following error:
Server Explorer
An error occurred during the sign in process: User 'foo#gmail.com' returned by service does not match user 'bar#outlook.com' in the request
OK
My subscription owned by 'bar#outlook.com' and I can perfectly fine sign in either to management portal in a browser (IE, Spartan and Chrome) - as well as in the Power Shell. Tried everything - cleaning up browser caches/cookies, resetting IE settings, playing with different IE security settings - nothign works.
Any help is appreciated - this issue drives me crazy.
P.S. I'm on Windows 10...
I had the same problem. Imported the certificate manually and everything worked ok: https://social.technet.microsoft.com/Forums/en-US/9cdafeb4-f459-436d-b2b8-9bc5c01f0df1/azure-tools-for-vs-cant-sign-in-to-subscription?forum=windowsazuredevelopment
I had this issue, to resolve it I:
Added 'foo#gmail.com' as an alias in my 'bar#outlook.com' Microsoft account, via account.live.com
Made the 'foo#gmail.com' email address the primary alias for my Microsoft account
I could then log in successfully in to Azure by pressing the Connect to Microsoft Azure button in the toolbar of the Server Explorer in Visual Studio 2013 and see all of my websites under the App Service node.
(When I'd used the certificate method described in the other post and Microsoft documentation I'd been able to see all my sql databases etc. but not the websites.)
Once I'd done all that I then switched my primary alias back to 'bar#outlook.com' and server explorer carried on working.
NB: If you're experimenting with this beware that there is a limit on how many times you can switch your primary.. as I have just discovered.. and now my primary is stuck on the wrong email address for a week.
NB2: If your connecting in order to be able to remote debug the website, then this can still be done by going to Visual Studio>Main Menu>Debug>Attach To Process, and then enter the URL of the site (without the http bit, e.g. mysite.azurewebsites.net) as the Qualifier and then attach to the w3wp.exe process.
I am having the exact same issue. It seems that the Azure sign-in in Visual Studio is redirecting to our organizational Single Sign-On instead of the Microsoft one. I have managed to work around this problem by using a Microsoft account that is not tied to my organization:
Create new Microsoft account or use an existing account not associated with your organization
In https://manage.windowsazure.com select Subscriptions/Manage Administrators
Choose Add+ and add the new Microsoft account as administrator to your subscription
Log on to Azure using the new account from Visual Studio
/Morten
I changed my Microsoft account's email address and had this problem. Adding an alias did not help.
The problem is to do with the Azure Active Directory Library for DotNet. For whatever dumb reason, they throw an exception when Azure returns an ID different than the one requested (if the server isn't crying about it, why make up an error and make the client deal with it?).
Since Azures's support was no help, I had to build a custom copy of the ADAL with that moronic exception removed and an assembly version matching the one used in VS2013 (2.11). Also importantly, disable strong name verification for the custom assembly.
As you can tell from the title, I set up a virtual machine on Azure and installed a website and database that my company is hosting for a client. The spending limit was not lifted, and after it was reached my VM was deleted.
Since that time I have lifted the spending limit, but I have no idea how to get the VM back, or if that is possible at all. What are the steps I need to take in order to get back to where it was? Is the database that was on this server gone for good? I spent hours getting this server up to date with updates and Web Platform Installer software. This would be rather cruel if everything is now lost.
Are you sure the VM was actually deleted, or was the deployment deleted? Check in the portal under the Virtual Machines tab. Look under the Disks section and see if you have a disk there that represents the server that was running.
If so, you should be able to create a new Virtual Machine instance by using the New button at the bottom of the portal. Click on the New button and select Compute > Virtual Machine > From Gallery. Then click on the My Disks under the popup screen. This will let you select the disk that represents the OS disk from your server.
You may also want to check to see if the Cloud Service container that was running the server was also deleted. When you create a Virtual Machine a Cloud service is created to act like a container for that machine instance. You can also add additional machines to that same container. Take a look under Cloud Services in the portal and see if one is there named like what you had setup for the virtual machine. If so, then you'll either have to delete this one so you can reuse the name, or you can user the PowerShell cmdlets to start the virtual machine and put it into the already existing cloud services container.
I had the same experience. Our Azure Virtual machine was gone, and I got really scared when it was also missing from the management portal. I solved it like this.
Remove the spending limit on the credit card from the Azure account portal.
Delete the cloudservice that had the same name as the VM. The cloud service was only an empty container now that the VM was gone.
It is easy to restore the missing VM by creating a new Virtual Machine. Choose to create a new VM from Gallery, and under the Gallery you can find your missing machines harddisk under "My disks".
Wait while the machine is restored, and then start it.
Now you have to manually recreate all network endpoints. That was a pain as I had quite a few different streaming servers installed.
I wish that Azure only stopped an virtual machine instead of silently removing it when the customer fails to pay. Especially because it is quite hard to understand which services are free, which services are free trials and which services that you must pay for.