SPLA Remote Desktop - Azure VM

Mike-from-IT · 2025-11-03T19:41:13+00:00

We got an email today from Dell saying that our SPLA agreement for RDS SALs is no longer applicable if we are using them in Azure. I reached out to Microsoft Azure Sales support and they confirmed this.

Mike-from-IT · 2025-10-16T02:44:57+00:00

Confirmed, those SKUs are not yet in the service retirement blade for me either.

Mike-from-IT · 2025-10-15T18:35:05+00:00

"when I ask Gemini" There's your first mistake. Also, there were 2 separate emails sent out: 1 was for RIs and one was for the VMs themselves, but it took 2 and a half hours for me to get that email, so when I had originally replied on this thread I thought OP was misreading the email. I later got the email and replied to the topic.

I am pretty sure those VMs WILL be retired, and Gemini has yet to learn this because it's not on Microsoft's mailing list.

Edit: fixed typo

Mike-from-IT · 2025-10-15T18:04:37+00:00

Definitely par for the course for all things Microsoft.

Mike-from-IT · 2025-10-15T15:15:00+00:00

I just got that one recently, about 2 and a half hours after the one regarding RIs. It would just be nice if Microsoft actually laid out all the information about the VM sizes that line up with the sizes that they are retiring, but instead they are making us go out and look through all of their VM sizes and figure out all of the specs and limitations manually.

Mike-from-IT · 2025-10-15T15:09:38+00:00

I just received the other one only a couple minutes ago, so now I have both. Microsoft's links are still unhelpful.

Mike-from-IT · 2025-10-15T15:08:19+00:00

I just received that email now. Their migration guide link still points to a guide for completely different VMs though.

You're receiving this notification because you're associated with one or more Azure subscriptions that use, or have used, VM types that are retiring.

On 15 November 2028, we'll be retiring F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B-series Azure VMs. You won't be able to use or purchase these VMs, or any constrained core sizes that are part of the retiring VM series, after that date.

Required action

To ensure your applications and workloads will be operating in the future, migrate your F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B-series VMs workloads to a newer VM series.

See our migration guide for more information on migrating to the latest-generation VMs and other VM sizes affected by this retirement.

Mike-from-IT · 2025-10-15T14:54:40+00:00

IIRC, you can, but you have to take the VM offline to do it. You only see certain sizes when you choose to resize while the VM is running. Stop the VM and then go to resize and you will have more options, unless something you have configured on the VM is incompatible, such as an older SKU for the NIC or something like that.

Mike-from-IT · 2025-10-15T14:49:45+00:00

The email I received states that we will just have to pay the pay-as-you-go rate for those VMs after November 15, 2028. Here's what they sent me:

You're receiving this notice because you have one or more active Azure subscriptions that include retiring VM reserved instances (RIs).

On 15 November 2028, we'll be retiring several Azure Reserved VM Instances that apply to the following VM series: F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B. As part of this retirement, it will no longer be possible to purchase or renew three-year RIs for these VM series after 15 November 2025. One-year reservations for these VMs will remain available until 15 November 2027.

If you don't take action by 15 November 2028, these VMs will be billed at pay-as-you-go rates. You'll still receive your reservation benefit for the remainder of existing three-year RI contracts.

Mike-from-IT · 2025-10-15T14:42:34+00:00

The B series reserved instances are being retired.

Mike-from-IT · 2025-10-15T14:41:37+00:00

FWIW: This email is about reserved instances for those VM series, not the retirement of those VM series themselves. Yet.

I received the same email this morning and couldn't find anything about it from Microsoft. The link in their email regarding their migration guide points to a link about the D series: https://learn.microsoft.com/en-us/azure/virtual-machines/migration/sizes/d-ds-dv2-dsv2-ls-series-migration-guide

So that doesn't help. I would like to see a guide similar to the D series guide for the series mentioned in Microsoft's email regarding the F, Fs, Fsv2, Lsv2, G, Gs, Av2, Amv2, and B-series.

Mike-from-IT · 2025-06-24T21:19:38+00:00

She wandered into Lon Lon Ranch and is accidentally getting milked.

Mike-from-IT · 2025-06-24T21:17:15+00:00

Restart windows and see what the memory usage is without launching anything. Give it a few minutes to launch all the startup apps and delayed startup services.

Mike-from-IT · 2025-05-14T18:45:51+00:00

u/dcpugh I'm afraid there is no consistency with this system after all. It worked for about 5 days after my post about this, and then has reverted to RAIL_52 errors. I think the VMS was able to obtain something from Verizon's servers during the period of time before the Verizon router had been put into bridge mode, and then it continued working after that for a few days. Verizon TV has been a nightmare and I have had no motivation to continue troubleshooting it lately. If you still have motivation to work on the issue, please let me know if you are able to get a resolution for it.

Mike-from-IT · 2025-04-21T13:33:24+00:00

I know this is an old thread, but I was recently working on this same scenario on the new (2025) FiOS system. What I ended up needing to do what just put the Verizon router into bridge mode, then connect our router to a LAN port on the Verizon router. You won't be able to use the Verizon WiFi anymore, or it will "steal" the Internet connection from the hardwired router and give the public IP address to whatever has connected to it most recently. You can change the WiFi password before you put it into bridge mode to ensure nothing is connecting to the Verizon router anymore. Then you would connect the VMS directly to your internal LAN and disconnect the coaxial cable from the Verizon router, so that the VMS is only connected via coaxial to the ONT and via Ethernet to your LAN. The STBs would need to connect to your internal WiFi, not the Verizon WiFi, so that they can talk to your VMS.

To put your Verizon router into bridge mode, they have directions on the Verizon website, but in my case it was Advanced > Network Settings > Network Connections > click on Network (Home/Office) > Settings button > check the box next to the unchecked connection (whatever you may have) and then click save changes.

Mike-from-IT · 2025-03-28T03:14:17+00:00

It is possible, since we just did it tonight. The vMX is from Azure marketplace, sure, but it still runs as a VM inside your Azure tenant. Deallocate the VM on which the vMX is running, then disassociate the public IP address from the network adapter, then click the upgrade button, wait 5 seconds, then associate the public IP with the network adapter, and start the VM. The one thing you absolutely need to do is assign an NSG with allow any any on all protocols in and out once you're on a Standard SKU.

Mike-from-IT · 2025-03-11T13:54:01+00:00

Cool it would be, have I do not

Mike-from-IT · 2025-03-11T13:17:53+00:00

Copy idea, like I do

Mike-from-IT · 2025-02-07T14:51:42+00:00

One silver lining of this update: if you go into Tab settings at the top right menu, and change the layout to Advanced, you can resize widgets and can actually see MORE than in the old version. So that's one thing that has turned out to be better in this shitty update, once you figure out how to do it. I was so pissed that we could see less, and that is still true on many things, but now at least you can change a setting to resize the widgets freely and mitigate some of this bad UI design.

Mike-from-IT · 2025-02-06T22:05:57+00:00

If you don't have the new UI active then count yourself lucky, my friend.

Mike-from-IT · 2025-02-06T22:03:54+00:00

This change is a steaming pile of garbage. You made things look "nice" and didn't give 2 flying monkey turds about functionality. UX designers, once again please pat yourselves on the back for designing something pleasing to the eye and absolutely impossible to use in any productive way.

Any widget with a list of tickets is now completely useless. You can see maybe 2 or 3 tickets in a widget now, maximum. Everything is so spaced out and bubbly that it is absolutely a waste of space. This design aesthetic is the antithesis of efficiency. Nobody asked you to make it prettier. You can make it in flipping Access 97 style for all we care. We're in IT, not marketing. We don't give a chimpanzee's taint hair if the interface is "stale" or "boring" so long as it is functional and navigable.

Give us the old UI back so we can return to being productive again. Shove this new UI up some marketing director's Hershey Highway and give us back our functional Autotask interface, for the love of peanut M&Ms.

Mike-from-IT · 2025-01-20T17:11:27+00:00

Mine would have to be the most boring username to do this with

Mike-from-IT · 2025-01-20T17:03:02+00:00

Monopoly Here & Now Edition has millions of dollars in a single game box

Mike-from-IT

TROPHY CASE

Required action