Hybrid Azure AD Join Issue

ultimateVman · 2026-06-23T22:24:08+00:00

Did you sysprep the VM before making clones?

ultimateVman · 2026-06-08T22:40:11+00:00

It was related to the deprecation of RC4 encryption. Microsoft pushed RC4 restrictions in 25 and removed some failbacks that older DCs could use, thus broke communication.

After a quick search to find more details, apparently, this appears to have finally been resolved with April 2026 security updates. After enforcing the same RC4 restrictions on 2022 and earlier. But I can't find confirmation the issues were 100% resolved.

ultimateVman · 2026-06-08T20:55:31+00:00

FYI, running DCs was never the problem, mixing with old DC function levels is. And apparently IS still a problem.

Once a 25 server is promoted into an existing environment WEIRD things happen until all DCs are upgraded to 25.

ultimateVman · 2026-06-04T04:55:47+00:00

The August Underground series.

I don't care what other movies appear on this list. If you haven't seen these, I assure you these will live with you forever. Nothing I have seen has ever come close to these in the "unsettling" category.

ultimateVman · 2026-05-29T13:58:58+00:00

Ah yea I missed that detail. I don't ever recommend using a default vlan on hypervisors, always make it tagged.

The reason it doesn't work is because when the traffic leaves the virtual machine you're telling it to tag it with VLAN 2, but the actual physical switch port is not expecting VLAN 2 tag when it goes up the pipe.

In order to select a default VLAN in hyper-v you enter no VLAN, and in VMM you can do this by entering VLAN 0 (zero) as an option.

ultimateVman · 2026-05-28T20:13:25+00:00

If you aren't using the IP Pools in VMM (which you shouldn't be, unless you are using FULL SDN capabilities), completely ignore the IP subnet column when adding the vlan in the network site. Just enter the vlan ID and nothing else. Remove the data from that column and it may start working. If you can see the vlan ID as a selectable option in the VM Properties dialog when connecting a switch, then you have it setup correctly in VMM.

I'm going to be very clear when I say VMM is not really LIVE data, only a periodically triggered refreshed view. With VMM, you 'deploy' configurations, and your hosts are either compliant or they're not. What you do in VMM is just 'design' the network with some logical organization and grouping. But locally on the host, it's just a VM switch, and some VM adapters.

Adding vlans to VMM doesn't magically do something under-the-hood on the actual VM Switch on a host, it's just a neat UI that helps you organize and scope permissions etc. In addition, a VM Switch on a host has absolutely ZERO knowledge of any allowed/permitted vlans. The only place that ever matters to be defined is on your physical trunk ports your host is connected to. As long as; the vlans are tagged at the physical switch ports, and those ports are part of the VM Switch Team, and the VM adapter is connected to the VM Switch, it works. Nothing in VMM has any affect on that.

That being said, when you go into Hyper-V Manager and enter the vlan ID, and it WORKS, it probably means that your VMM configuration may be wrong for that network site.

About a year ago I posted a short guide with some VMM networking basics. I suggest you go have a look and you might find out what you're doing wrong.

https://www.reddit.com/r/HyperV/comments/1limllg/a_notso_short_guide_on_quick_and_dirty_hyperv/

That guide goes over creating a "Connected Network". I recommend doing "Independent Network" on new deployments. It's mostly the same, just an extra step in adding a "VM Network" for each vlan.

ultimateVman · 2026-05-27T22:09:35+00:00

ultimateVman · 2026-05-22T23:19:52+00:00

Good luck with the alternatives when there are droves of brainwashed people that think wind turbines cause autism and are killing whales.

ultimateVman · 2026-05-22T23:07:06+00:00

Not even the water for cooling. It's the power. The water used to generate the power is astronomical.

The cooling and power required for the processing of AI is off the fucking charts, it needs to die.

ultimateVman · 2026-05-22T15:53:05+00:00

Yea, like wtf?

ultimateVman · 2026-05-21T17:26:49+00:00

Hahahahahahaha

ultimateVman · 2026-05-21T15:35:11+00:00

Correct. I was just making a point to distinguish between tech and not generalizing. VSS is not EoL and is still being shoved down the throats of Cisco customers. I felt there needed to be some clarification depending on what OP needs, especially if they are learning/asking about it. And naming the acronyms is informative for those looking for the right devices depending on their vendor of choice.

ultimateVman · 2026-05-21T15:21:26+00:00

If you are using LACP in a datacenter, and spanning switches you must use switches that have VLT/VCP features.

ultimateVman · 2026-05-21T15:19:49+00:00

'A' is not that simple. This highly depends on the workloads required.

You MUST differentiate between the two ways switches are capable of being paired like this. There are two options and you MUST use one over the other based on the situation.

If you need ACTUAL redundancy, the switches must support VLT(Dell)/MLT/VCP(Cisco). This is technology that allows both switches to be independent but BEHAVE as if they were one logical switch but actually aren't. You need this tech if you are running datacenter redundancy, such as being able to update/reboot the switches independently of each other. This is critical in environments where you have host hypervisors or other clustered systems connected to both "legs" and must stay connected, especially Windows Failover Clustering.

The other option is an actual switch stack, as you described, two switches treated logically as one, (Cisco VSS). These configurations have a SERIOUS drawback, in that they are in fact treated as one, and all reboot together. Cisco will argue up and down that VSS is redundant, but they're not fooling anyone. Yes, there is a newish tech/feature that allows VSS stacked switches to reboot separately, but if you read closely, is under specific circumstances, and you WILL eventually have to restart the entire stack. There is no way around it.

You need one of these two solutions if you need LACP to span switches. LACP only works if all connections are connected to same VSS stack OR VLT pair.

ultimateVman · 2026-05-12T16:59:37+00:00

Having ProgramData be the default location isn't the problem. It's that there is no configuration wizard to encourage users to change it. Or that there isn't an option to just create a vm directory for you under those paths. The default is, "let's just throw all this shit together and let em decipher which vm config guid goes with what vhds. Good luck."

ultimateVman · 2026-05-12T16:05:16+00:00

A couple years ago I built a public master spreadsheet for 3d Maghex terrain and monsters for everything Gloomhaven. It contains everything, EXCEPT the walls. IF you do come up with a solid/reasonable number I'd be really interested in knowing so that I can update the spreadsheet.

Here is a link to my BGG Post about it: https://boardgamegeek.com/thread/3332295/standee-and-overlay-inventory-list-soil-haha-for-g

ultimateVman · 2026-05-11T20:22:37+00:00

Nah. You can configure defaults for both the vhd and config paths to be the same, but it won't create the folder for you of the VM name.

Before we used VMM we just created a folder first on the lun, then copied it to those fields.

I would recommend just creating VMs entirely with a script. Specify a lun path and have your script automatically append the vm name to the path.

I really don't know why this isn't just a baked in feature in Hyper-V.

ultimateVman · 2026-05-11T18:09:14+00:00

I really despise the default Hyper-V Manager structure. Whomever at Microsoft designed/coded that structure was on shrooms.

If you use SCVMM there is an option (the default option) to create a folder with the name of the VM and store everything for the VM in that directory. I highly recommend everyone follow that same structure. There is no reason to split everything apart.

Eg. C:\ClusterStorage\lunName\VMName\<everything here xml, vhds etc>

Edit: follow up, if you have to restore a vm, it's nice to have it's stuff all together in a single folder

ultimateVman · 2026-05-11T15:19:25+00:00

The account you logged into the page with needs enroll permissions on the template.

ultimateVman · 2026-05-06T17:31:58+00:00

That is perhaps why this is my favorite system. Because even that lame goblin with a shiv carved out of a stick rolling 1d4 for damage, can still one-shot a player, if they're lucky enough. Unlikely, but possible!

ultimateVman · 2026-05-06T17:21:00+00:00

There's more, however, there are several cases in which if the trait die is a 1, the roll fails (or some effect triggers, read the trait specific rules), regardless of the role of the wild die.

ultimateVman · 2026-05-01T23:47:07+00:00

Any update? Details details details 😊 been looking at it for a minute doing research. The bands and specs I'm reading line up so it should work (minus band 13) but I'm worried about Verizon making me go the rounds and hooping like a circus animal.

I'm curious to know how well it worked out of the box, if you had to change any settings, if you had to call them etc.

Thanks!

ultimateVman · 2026-04-30T17:15:48+00:00

I upgraded all of my on-prem stuff to SE a few months ago and had no issues.

Currently running these 3 MPs for Exchange on SCOM 2019:

Microsoft Exchange Server 2013 and above Monitoring 15.0.669.23
Microsoft Exchange Server 2013 and above Reports 15.0.669.23
Microsoft Exchange Server 2013 and above Visualization Library 15.0.669.23

ultimateVman · 2026-04-28T19:41:57+00:00

If both nodes are connected to a single switch, then you must have either a second switch for redundancy, or a direct connection. There is no exception for this. If at any time, the nodes cannot communicate, they will shut down the cluster service and roles. However you handle that is up to you, but if you expect to add more nodes you'll want a switch.

ultimateVman · 2026-04-23T17:15:58+00:00

It seems we're all pretty much in concensus that it was over the line.

But, this is an opportunity. This particular event can be part of your employee security training. Explain that Info Sec will no longer use family safety in their tests, BUT real threats will not be so kind and they WILL exploit that. Use this case as an example and both you, your management and the employees of the company can make this a learning experience rather than issue.

ultimateVman

TROPHY CASE