Hi, I know, if you change number of instances manually in Azure Cloud Services, the roles will restart.
With autoscale, if you have 1 instance, and tell it to increase by 1 as needed based off the number of messages in the queue, can you confirm that the existing instance will not be restarted while the others spin up?
We noticed that when we recently scaled from 1 to 2 instances manually, the 1st instance restarted.
I registered a complain in HP customer care on 8th jan 2013 reg the my thin client discreption below:-
Product description: MS6000/Q9500/500hq/6W/8k ALLProduct number: BM461AWSerial number: XXXXXXXXXX(for your security, I have removed the serial number from your post above - that's information you probably don't want to make publicly available.)
I am currently running windows 8.1 and had successfully installed VMware View agent 5.2.0-987719 x64. I was able to see my computer under the VMware Horizon View Administrator, and successfully remoted to my PC. However, upon taking my computer off the domain, and rejoining it, the connection broke. I removed the PC from the View Administrator. Upon reinstalling the agent, I get the following “This agent is already registered at xxxxxxx. Do you want to continue this installation and update registration information?
Tried rebooting. The problem is the bond creation never finishes. I can manually add the necessary entries and it works fine. After this, I can remove the bond partner via VM Manager and it will remove the entries, but the manager will never properly...
My cloud service is running on an Extra Small instance... and it has 98% CPU usage for the last hour... And it's taking 5 to 10+ seconds for simple API calls to return...
How can I tell what's causing the slowdown? Can I see what processes are running on the instance or something? I'm new to Azure and don't know much about this :/
I only have 400 people who could even be querying the cloud service API... And I doubt it's getting more than 3 simultaneous requests every minute! I would think an Extra Small instance would have no problem with that...
Hi, running in to a weird problem with a new vCD (latest) install. When trying to add the first vCenter and vSM to the vCD instance, the vCenter will add correctly, but the vSM fails with the error "vShield Manager is not registered with the VC x.x.x.x", where x.x.x.x is the IP of the vCenter.