Has anyone seen any issues with 2511 and VDA's retaining the identity of the maintenance VDA? The process we are following is: Create new version (Server 2019 vdisk) > boot maintenance VDA > upgrade VDA to 2511, upgrade TD to 2511 > seal with BISF + CTXO > promote to Test > boot test VDA. Connect to the test VDA and the GPO's from the maintenance VDA are applying, looking in GPRESULT and its showing as if its still the maintenance VDA.

i always check the pvs tray icon to confirm the Vdisk is in R/W mode before starting any config changes as been bitten before. I also check what PVS server it is streaming from and what server the new MM version files have been created on and sometimes i turn off load balancing on the Vdisk while doing versioning changes and only present it from one PVS server. Maybe your maintenance target device connected to PVS01 and created the pvp/avhd on PVS01 but you thought it would be PVS02 and there was already a version 3 on PVS02 in the vdisk store (old version someone created and removed but left the version 3 files) you then copied the version 3 files from PVS02 to PVS01 overwriting the actual proper version 3 files on PVS01

Hey John, yeah I have also been bitten by that before. I have double checked and it 100% was R/W and can confirm the changes are on the test VDA. The strange thing is that hostname brings back the correct name, gpresult /r brings back the correct name but the incorrect GPO's.

so test machine has correct hostname and is in correct OU but is getting GPO's applied that should apply to a different machine (maintenance machine) ? you double checked OU memberships / computer Group membership ect? What the RSOP/group policy results wizard saying ? I am wondering if anything to do with the recent Microsoft SID changes

Confirmed hostname is in the correct OU, created a fresh VM using the wizard just to confirm same behaviour. GPResults HTML output is showing the maintenace VDA hostname, but gpresult /r is showing the correct test VDA hostname but the wrong GPO's. I was also looking at that article but we are on Server 2019 and that only applies to W11/Server 2025

maybe run psgetsid on both maitenance machine / test machine and see if the computer sid is the same or use powershell to check

Get-ADComputer -Identity "ComputerName" -Properties SID | Select-Object SID

Can confirm the SID is different between the maintenance and the test VDA's however the MachineGuid in registry is the same.