Hello, I created an AD service in the cloud (in the management panel). I have a domain like "mycompany.onmicrosoft.com". Now, I'm trying to connect my existing Azure VM to this domain, but I can not, because my domain could not be found.

What should I do to connect my Azure VM to Azure AD?

Thank you!

I'm sure I've done something stupid, but I can't figure out what. Here's the situation.

I need to be able to create VMs from within a Virtual Network in order to have the ability to connect to these VMs as an Administrator. It's part of some automation that I want to do within Azure, PowerShell and SQL Server running on the VMs. Here's the basic setup:

I have a virtual network set up, per the Microsoft example that Scott Klein wrote. It seems to be working. I can add servers to it. I have to log in using my CORP account, etc. It has an Affinity Group, GFVMDojo and a name GFDojo. I have a storage account, newly created, gfbudemo. It’s location is GFVMDojo (East US), which means it’s part of the same location as the VM. I have a cloud service, gfvmbudemo (yes, I stopped trying to name stuff appropriately when I got frustrated. I’ll rebuild everything once I figure out what’s wrong). It’s location is also GFVmDojo (East US). I’m logged into a VM who’s location is GFVMDojo (East US), using the CORP login that is part of the virtual network. So, as near as I can tell, everything is stacked up appropriately.

Now, in PowerShell, I have the imported my certificate for my subscription. I’ve supplied

$subscriptionid
$subscriptionname
$thumbprint
$virtualnetworkid
$password

##All 100% correct. I then set variables:

$azureLocation = "East US";
$login = "Grant";
$vmImage = "fb83b3509582419d99629ce476bcb5c8__SQL-Server-2014CTP2-CU1-12.0.1736.0-Evaluation-ENU-WS2012R2-CY13SU12";
$vmName ="BackupTesting";
$certificate = get-item Cert:\CurrentUser\my\$thumbprint
$cloudService = "gfvmdemo";
$storageAccountName ="gfbudemo";
$domain ="CORP";
$FQDN ="corp.clouddojo.com";
$subnet ="Back";
$dnsSettings =New-AzureDns -Name"BackDNS" -IPAddress"10.10.2.0";
$medialocation ="http://gfbudemo.blob.core.windows.net/vmstorage";

And then these commands

Set-AzureSubscription -SubscriptionName
$subscriptionname -SubscriptionId
$subscriptionid -Certificate
$certificate -CurrentStorageAccountName
$storageAccountName;

##create a VM, wait until it's provisioned

New-AzureVMConfig -Name $vmName -InstanceSize ExtraSmall -ImageName $vmImage  -MediaLocation $medialocation `    | Add-AzureProvisioningConfig -WindowsDomain -Password $password -AdminUsername $login -Domain
$domain -JoinDomain $FQDN -DomainUserName $login -DomainPassword $password `    | Set-AzureSubnet -SubnetNames $subnet `    | Add-AzureEndpoint -Protocol tcp -Name MSSQL -PublicPort 1433 -localport 1433 `    | New-AzureVM -WaitForBoot -ServiceName $cloudService -VNetName "GFDojo" -DnsSettings $dnsSettings;

When I was just running this externally from my local machine, everything worked. But now, on the VM within the virtual network, I keep getting this error:

New-AzureVM : CurrentStorageAccountName is not accessible. Ensure the current storage account is accessible and in the same location or affinity group as your cloud service.

The locations are the same. And what's marked as the storage account, at least according to what I see from Get-AzureSubscription. The URL for the storage account is also right. I'm just not sure what I've done wrong here, and I know I've screwed something up. Any help on what to look for in terms of troubleshooting beyond this one error message?

Hi,

Im unable to ping to my azure vm created. When i try to ping with both the dns name or External ip address, i get no responses to my pings,

Kindly advice.

Alan.

UPDATE 01/31/14: Currently for most VMs, using the Shutdown option with Sysprep works as expected. However in limited cases, the VM is unexpectedly restarted. When this happens, you are unable to RDP to the VM because it is waiting for input at the first screen of Windows setup.

To avoid this issue, specify Quit instead of Shutdownwhen running sysprep, shut it down using the Shutdown option in the management portal, then useCapture to create an image.

We will update the thread when additional information is available.

This does not impact portal-initiated shutdown (clicking Shutdown in the Windows Azure management portal), only guest-initiated shutdowns.

A guest-initiated shutdown is any process that triggers a shutdown from within the guest OS, which could be sysprep /shutdown, or manually shutting down the VM from within an RDP session.

When capturing an image, the guest needs to remain shutdown for it to be captured in the correct state. If you capture a VM that has been started after sysprep has been run, the guest OS is not in the correct state. The capture operation will succeed, but VMs created from the image will fail to provision successfully, and will ultimately show statusProvisioning timed out. This is because the VM was captured when the setup state was IMAGE_STATE _UNDEPLOYABLE instead of the desired IMAGE_STATE_GENERALIZE_RESEAL_TO_OOBE (see alsohttp://technet.microsoft.com/en-us/library/cc721913(v=ws.10).aspx for description of those values).

To workaround this issue, specify Quit instead of Shutdown when running sysprep, and once sysprep completes, shutdown the VM from the Shutdown option in the Windows Azure management portal instead of from within the RDP session.

1. Create a second user account that you add to the local Administrators group to use for troubleshooting if needed.
    
2. Run Sysprep, selecting Enter System Out-of-Box Experience (OOBE) andGeneralize checked but select Quit instead of Shutdown.
    
   
    
   Or from a command-line:
    
   c:\windows\system32\sysprep\sysprep.exe /generalize /oobe /quit
    
3. Wait for the C:\Windows\System32\sysprep\Sysprep_succeeded.tag file to be created before doing anything else, as that indicates sysprep completed.
    
   
    
4. Log off from the VM, leaving it running. Do not shut it down from within the RDP session.
    
5. Click Shutdown for the VM in the Windows Azure management portal.
    
6. When the Status under Quick Glance on the Dashboard of the VM in the portal shows Stopped (Deallocated), then you can clickCapture at the bottom to create the image.

I followed the instructions on creating an image as on help, but now the remote desktop or the VM doesn't work.

I followed the instructions to the point, and clicked "generalized". Please help on how to connect back to the VM, it has a lot of vital files.

Found this issue being reported with a lot of users.

The help section in the portal directs the steps in this article: http://www.windowsazure.com/en-us/documentation/articles/virtual-machines-capture-image-windows-server/

I used "Shutdown" for sysprep, but apparently it's incorrect, and leads to a bug that doesn't let users connect with VM either with RDP or any other means.

Read posts, and comments - all with link to this article for NEXT time you do a sysrep. http://social.msdn.microsoft.com/Forums/windowsazure/en-US/fafb9ee6-1e57-46ba-8440-27467ad986cf/image-capture-issue-vm-unexpectedly-started-after-guestinitiated-shutdown

How can the last VM be made accessible again? I have a lot of important data on it.

I have a Windows 2012 Server running in Azure. After I patched my server the "Windows Azure Guest Agent" service has started to crash because of a .NET Runtime error (see below). In order to fix this the service tries to restart itself, this happens each second, which causes a 100% CPU usage. This made me disable the service. Has anyone experience something similar and solved it?

Application: WindowsAzureGuestAgent.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
Stack:
   at Microsoft.WindowsAzure.GuestAgent.ContainerStateMachine.AgentConfigurationSection.get_Current()
   at Microsoft.WindowsAzure.GuestAgent.AgentCore.AgentCore.Start()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()

And here is the Application error

Faulting application name: WindowsAzureGuestAgent.exe, version: 2.3.1198.653, time stamp: 0x52a77387
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988aa6
Exception code: 0xe0434352
Fault offset: 0x000000000003811c
Faulting process id: 0xf18
Faulting application start time: 0x01cf3de01b80da00
Faulting application path: C:\WindowsAzure\GuestAgent_2.3.1198.653\GuestAgent\WindowsAzureGuestAgent.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 594a022f-a9d3-11e3-93f8-00155d6218e9
Faulting package full name: 
Faulting package-relative application ID: 

Morten

Other than using the web based dashboard is there a way to remotely start up my VM instance?

I am trying azure out as a backup service for my websites and I don't need it running all day. I just need to be able to write a script that runs on Linux servers to do the following.

The workflow of the script is:

1. start up VM instance
2. FTP in
3. Retrieve the file with checksums of tar.gz file
   
4. If different, upload the new compressed file
5. Upload the checksum file
6. Shut down instance

2-6 is trivial but is 1 possible?

Or is there a different Azure service I could use from Linux based servers?

My Silverlight app uses EF and has this connection string:

<add name="[AppNameDBConn]"
    connectionString="metadata=res://*/DAL.[AppName].csdl|res://*/DAL.[AppName].ssdl|res://*/DAL.[AppName].msl;
    provider=System.Data.SqlClient;
    provider connection string=&quot;
    data source=[ServerName]\[InstanceName];
    initial catalog=[NA];
    integrated security=True;
    multipleactiveresultsets=True;
    application name=EntityFramework&quot;"
    providerName="System.Data.EntityClient" />

Note that the data source includes the server and instance names. It works fine in Dev. However, it does not work in an Azure VM hosting SQL Server. I must remove the instance name from the data source leaving only the server name. Doesn't make sense, but it works.

Now the problem is I recently installed a new database instance in Azure and can't connect to it. I assume it's some kind of configuration issue since I now have two instances. Did some research, but haven't found a solution yet.

In my Azure VM I'm getting lots of these errors in the System event log:

The IO operation at logical block address xxxxxxx for Disk x was retired.

These errors are causing my VM to preform very slowly and lock up such that I can't access it via RDP or access the web site it is hosting. Rebooting seems to help, but the problem continues to come back. What can be done to fix this?

Hi, 

I have a disk with my files, nopCommerce files in this case.

How do i attach this disk to a Vm, so that i can reach and edit the files from the RDP/MTSC?

disk info: 

portalvhdsty13h9c4s0w6d

Storage Account

Online

Hbxnc-sql

North Europe

according to this tutorial, there should be a "attach disc" and a "attach empty disc". i only have "attach empty disc available".

Thanx/Hobbe

Hello, I have a VHD file but I cannot delete it.

It is not attached on existing VM or cloud services.

Here are some results from Windows Azure PowerShell:

PS C:\> Get-AzureDisk
詳細資訊: 上午 12:10:36 - Begin Operation: Get-AzureDisk
詳細資訊: 上午 12:10:40 - Completed Operation: Get-AzureDisk


AffinityGroup        :
AttachedTo           : RoleName: ly2314gallery
                       DeploymentName: ly2314gallery
                       HostedServiceName: ly2314gallery
IsCorrupted          : False
Label                :
Location             : East Asia
DiskSizeInGB         : 30
MediaLink            : http://***.blob.core.windows.net/vhds/ly2314gallery-ly2314gallery-2012-11-15
                       .vhd
DiskName             : ly2314gallery-ly2314gallery-0-20121115032603
SourceImageName      : OpenLogic__OpenLogic-CentOS-62-20120531-en-us-30GB.vhd
OS                   : Linux
OperationDescription : Get-AzureDisk
OperationId          : 2eabb95b-9faa-7cad-aa98-e7773285c4ac
OperationStatus      : Succeeded

AffinityGroup        :
AttachedTo           : RoleName: ly2314vpn
                       DeploymentName: ly2314vpn
                       HostedServiceName: ly2314vpn
IsCorrupted          : False
Label                :
Location             : Japan West
DiskSizeInGB         : 30
MediaLink            : http://***.blob.core.windows.net/vhds/ly2314vpn-ly2314vpn-2014-03-07.vhd
DiskName             : ly2314vpn-ly2314vpn-0-201403070238320991
SourceImageName      : b39f27a8b8c64d52b05eac6a62ebad85__Ubuntu-12_04_3-LTS-amd64-server-20140130-en-us-30GB
OS                   : Linux
OperationDescription : Get-AzureDisk
OperationId          : 2eabb95b-9faa-7cad-aa98-e7773285c4ac
OperationStatus      : Succeeded



PS C:\> Remove-AzureDisk

Cmdlet Remove-AzureDisk 在命令管線位置 1
請提供下列參數的值:
(輸入 !? 可取得說明。)
DiskName: ly2314vpn-ly2314vpn-0-201403070238320991
詳細資訊: 上午 12:10:56 - Begin Operation: Remove-AzureDisk
Remove-AzureDisk : BadRequest: A disk with name ly2314vpn-ly2314vpn-0-201403070238320991 is currently in use by virtual
 machine ly2314vpn running within hosted service ly2314vpn, deployment ly2314vpn.
位於 線路:1 字元:1
+ Remove-AzureDisk+ ~~~~~~~~~~~~~~~~+ CategoryInfo          : CloseError: (:) [Remove-AzureDisk]，CloudException
    + FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.RemoveAzureDiskCommand

詳細資訊: 上午 12:10:59 - Completed Operation: Remove-AzureDisk
PS C:\> Get-AzureVM

ServiceName                             Name                                    Status
-----------                             ----                                    ------
ly2314gallery                           ly2314gallery                           ReadyRole


PS C:\>

Hi,

We are currently evaluating Amazon Workspaces and I was wondering if Microsoft is planning a similar DaaS offering anytime soon?

We're a small company therefore we love the idea of simplicity as well as ease/speed of deployment of Amazon Workspaces. No need to configure servers and invest in layers and layers of technology -- as in the case with VMWare. We don't want to be in the business of managing servers/desktops, we just want to use them.

I'm aware of some articles that cover how to set up terminal services on virtual machines on Azure. That would take us back to managing servers. We love the fact that in Workspaces, we can just go to the portal and provision a new desktop. However, that's the extent of what we love about Workspaces. We've found lots of limitations about Workspaces e.g. no AD integration yet so no single sign-on, no group policies so if we create a new Workspace, we'd have to install all the apps manually,  and the list goes on.

Would love to see an Azure based solution where we could just log into the portal and select an image from the catalog just the way we do with servers and within minutes provision desktops -- preferrably both Windows 7 and Windows 8 -- that we can join to our domain/AD.

Is this something we can expect from Microsoft or should we keep praying that Amazon comes through?

Thanks, Sam

RDP failed. Show the next message

• The port it´s configured, but not responding telnet or ping. 
• The VM is ON

Help me please

Update 3/17 - for a VM to have encountered this issue, among other factors, it would have had to have been created sometime between 2/27 and 3/9. As of 3/10, newly created VMs could've no longer seen this issue since an updated VM agent was being deployed during provisioning after that date.

If you encountered the issue on a VM and disabled the RdAgent service as a workaround, you should leave RdAgent disabled until the Windows Installer package (.MSI) is released and you can manually install the agent MSI package to resolve the issue overall for that VM.

-----------------

We are currently investigating an issue where the WaAppAgent.exe process spikes at 100% CPU. WaAppAgent.exe is the process for theRdAgent service, which is part of the VM Agent for Windows Azure Virtual Machines.

If you encounter this issue, you can change the Startup type for the RdAgent service to Disabled, clickApply, then click Stop to stop the service.

If the WaAppAgent.exe process is still running, right-click it inTask Manager and select End Process.

We are continuing to investigate the issue and will provide more information as it becomes available.

Thanks,

Craig

Hello All,

Checking if Powershell would be the best way to automate the transferring of files to an Azure VHD drive versus using RDP.

Thanks for any suggestions,

Bob

BobH

we can see that the servers were instructed to restart via a windows process 'Event ID 1074 , the process 'c:\windows\system32\vmicsvc.exe has initated a shutdown of computer'

I have found other Azure subscribers having the same issue

'social.msdn.microsoft.com/Forums/en-US/40ce155c-2188-4a59-9507-85bb06d6e0e2/unexplained-shutdown-of-three-vms-last-night'

Is this still an issue as the last posts I have read are nearly a year ago, this is also unacceptable for our client who have production systems running via Azure.

We resized the servers about 3 months ago, so do we have to re-size again?? or is there a permanent fix?

Kind Regards 

Hello all,

Is there any easy way to identify disks (vhd) names in windows azure?
I have
1 - OS image (sysprep)
1 - Virtual Machine (used already prepared OS disk)
1 - Data disk (attached to Virtual machine)

Under Azure Portal -> Virtual Machines -> Disks, how can i know which one is my prepared image, which one is my running VM and which one is my attached disks? I created few virtual machines and images before so there are more disks than I should have. Now I am not sure which one is to be deleted.

And another thing about disk space license: do I still charged if I keep those disks inside my storage account without using?

Thanks in advanced,

Lin