Hi,
I encounter a problem with the new Standards Load Balancer.
With 2 VM behind a Standard Load Balancer and without public IP Address affected on VM NIC, I can't access to Internet.
I've verified DNS configuration, I use Azure DNS.
Is anyone encounter the same problem ?
Best Regards,
MsAzureAlex
Aditya Mediratta
Hi Team,
I am trying to patch an Azure gallery Linux RHEL vm using update management but finding hard to achieve this.
Just Giving more information on it.
VM is machine
Can run update assessment from Azure portal and could see status as Non-Compliant
OMS agent is running fine (Green)
Can check perf logs in OMS
However when I am creating an update deployment no Linux VM all 265 updates are either failed or not attempted.
Please feel free to suggest and do let me know if you need any further information from side.
Cheers, Gourav Please remember to mark the replies as answers if it helped.
Hello,
Quick question: How likely is it to get the HB60rs as a low priority instance in South Central US? I'm trying to get one for a better week now and the batch pool resize always times out. Is it even possible? The price/perfomance is amazing on it, so it bums me out I can't get it at all after all these days.
Regards.
Hi,
I have setup a Windows Server 2016 Datacentre VM in Azure and configured Hyper-v so I can run nested VMs.
I'm assuming that I can run unlimited Windows Server 2016 VMs as I'm running datacentre. How do I license these and what media should I use when adding an image to install Windows.
Many Thanks
Hi Team,
I am trying to install OMS extension on Linux VM using cli but getting below error. however I can run command on few other servers.
Can anyone help me to fix this road block.
Deployment failed. Correlation ID: 293f8984-0c47-4040-98a9-d4db3ca8fb17. Handler 'Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux' has reported failure for VM Extension 'OmsAgentForLinux' with terminal error code '1007' and error message: '[ExtensionError] Non-zero exit code: 22, omsagent.py -install'
-------------------EDIT-----------------------
Script using by me : -
az vm extension set \Hi,
I have been researching Turbo boost issue for over a year now. Seem that it is not possible at all - because Microsoft turn off of bios.
As i understand it is "good" reason for this - turbo boost can be turned on only on whole server - 22 cores and if you use only 1 or 2 server just will consume too much energy.
As i understand the only way to turn it on - get full server - all 22 cores - than call microsoft and ask them to turn it on and in some cases they will do it.
I am not sure if this true or not and maybe somebody can comment on this.
We using 30+ cores over multiple D servers. Who should we call? I called everybody i could in microsoft and nobody seems to have answer.
As of now it seems that "and with Intel Turbo Boost Technology 2.0 can go to 3.2 GHz. Dv2-Series and D-Series are ideal for applications that demand faster CPUs" can be misleading advertisement. I think microsoft should clarify right there- how it can be turned on.
Hi, I am running a standard Windows 2016 VM on Azure. It is a standard implementation with RDS and Active directory installed and running.
The network rules have been modified to ensure that only Https (443) traffic is allowed to the server, and this is done using RDP clients that run on clients that have a certificate generated on the server in question installed on the local. Access is gained via the configured RDS gateway.
I have created a automated account which runs a schedule in which the server is automatically shutdown and started each working day. The automation works extremely well.
On a few occasions, I would say about 5 times in 3 months, once the server was successfully restarted (according to the Azure VM portal), users were unable to connect to the server using their RDS clients (Remote Desktop Connection). On these limited occasions, even opening up the RDP port did not allow anyone to initiate an RDP connection. A restart was required on each occasion in order to establish normal access.
I have looked at the event log and can see no direct reason for the inability to connect. There are a number of 7023 errors (apparently resolved with KB4467684 which has been installed on the server), 46 (crash dump failed) , 5774 NETLOGON and 36874 (TLS1.2 multi certificate selection) errors. I do not believe that any of these errors should result in the inability to logon to the server.
We are now simply running the server full time - which works without any problems.
When we experienced the problem, users had attempted to logon about 30 minutes after the server had restarted.
Is there any issue with regard to running a server in this manner and if so had could the operation be altered to ensure that this periodic inability to connect after a scheduled startup is resolved.
This is my Terminal log
https://gist.github.com/donhuvy/7b2bf3683978f4da5c726650d2bf1662
<style type="text/css">p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 15.0px Menlo; color: #000000} p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 15.0px Menlo; color: #000000; min-height: 18.0px} p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font: 15.0px Menlo; color: #2fb41d} span.s1 {font-variant-ligatures: no-common-ligatures; color: #2fb41d} span.s2 {font-variant-ligatures: no-common-ligatures} span.s3 {font-variant-ligatures: no-common-ligatures; color: #400bd9} span.s4 {font-variant-ligatures: no-common-ligatures; color: #000000} </style>donhuvy@vy2:~$ sudo apt-get install dotnet-sdk-2.2
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
dotnet-sdk-2.2 : Depends: aspnetcore-runtime-2.2 (>= 2.2.0) but it is not going to be installed
Depends: dotnet-runtime-2.2 (>= 2.2.0) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
donhuvy@vy2:~$
Hi All,
I need to set up a two node Failover Cluster running 4 instances SQL Server. Each instances requires a 1TB disk, so 4x 1TB disk. From what I've researched, it looks like these disks cannot be connect to both machines similar to an ISCSI disk in a data center,
but that they need to be configured with Storage Spaces Direct.
I'm confused as to how this works as it seems to gather the disks from each machine and create a pool (similar to a SAN); then from this pool you create your drives. However, if one of these disks is attached to VM1, and that VM goes down, how does it fail over to VM2 if it's attached only to VM1?
Do I need to duplicate the disks (meaning 4x 1TB disks per VM) so that it can replicate the data? Or am I completely missing something?
Cheers,
Ollie
Hi all,
One of our customers complains about RDP issue to his VMs in Azure which is Remote Desktop disconnects frequently in Azure VM, we followed this procedure to troubleshoot the issue: https://docs.microsoft.com/en-us/azure/virtual-machines/troubleshooting/troubleshoot-rdp-intermittent-connectivity but still the issue persists, every 2-3 minutes or so, the RDP session is lost, even we make continuous ping during the lost RDP session to check network connectivity and the ping is working ... please advice what to troubleshoot?
i have a virtual machine with static IP 10.0.0.20
it has an assigned Public IP to it
i need to be able to ping and not psping my virtual machine.
my application is a windows form application developed under c# and it needs to ping the server and check that it has access to it before performing some tasks on it.
i cannot use psping from my c# application.
please advise
Nassim
Would anyone be able to confirm that it is indeed possible to stream data from Azure Diagnostics running on a VM to EventHubs. From my reading of the docs it would appear to be possible, but I'd like to be certain as a number of issues with configuring sinks and event hubs seem to contradict this.
The overall goal is to be able to feed the data to our own monitoring applications so that we can track disk space usage and some other metrics that aren't provided through portal alerts for VMs.
Hello,
While I'm trying to deploy a Windows 10 image in Azure I get an error and can not continue the deployment.
Inside this commandline I create credentials
Set-AzureRmVMOperatingSystem -Windows -ComputerName $name -Credential $cred | `
Next when trying to deploy with
New-AzureRmVM -ResourceGroupName $rg -Location $location -VM $vmConfig
I get below error
New-AzureRmVM : Changing property 'adminUsername' is not allowed. ErrorCode: PropertyChangeNotAllowed ErrorMessage: Changing property 'adminUsername' is not allowed. ErrorTarget: adminUsername StatusCode: 409 ReasonPhrase: Conflict
Hello,
We are planning to migrate VM's (SAP ERP) from SAP HEC to Azure, and this would require a live data replication from source to target. I would need your help on below items.
1. What would be the best tool to migrate from SAP HEC to Azure?
2. If I migrate the VM's on my own using the freeware migration tool - AZ site recovery (by Azure) tool, What type of support I would get from Azure? Would Azure provide me support if I am struck in the middle of migration activity while using AZ site recovery tool?
3. If I don't want to migrate on my own, Would Azure team do that service for me? (i.e migrating VM's from SAP HEC to Azure).
4. What would be the migration procedure? I would like to have any similar test cases/ success stories with similar approach.
5. What is the downtime period and data transfer rate for this migration?
Thanks,
Navakanth,
Hi,
I've been trying to delete a VMSS for over 20 minutes and the instance is stuck in the Deleting state. From the looks of it, it is still provisioning. It is a Linux instance with custom cloud-init, which seems to have no exited properly. Is there any way to force the instance to die?
Thanks.