I'm currently dealing with a migration from a Windows 2008R2 environment to Windows 2019 and have hit a wall with the software installation policies. After decommissioning the old domain controller and file server, I've found that any MSI installations fail because they still point to the old server. I've tried to edit the generated .ass files for the GPO, but Microsoft documentation feels inadequate. It's frustrating that it seems there's no straightforward way to adjust these paths via a GUI or even command line, leading to concocting temporary GPOs to generate new .ass files. Is there a better solution or a best practice for handling this? I'm also considering revising how we handle software installations entirely since using installation scripts seems simpler in comparison. Any insights would be greatly appreciated!
1 Answer
I totally feel you; I'm about to do something similar with a domain controller setup. I'm upgrading one from 2012 R2 to 2019 while another is running 2022. I'm trying to figure out if it will be as tricky. Any advice you have learned along the way would be helpful too!
It mainly depends on whether you're using FRS or DFS for replication. If you're serious about this upgrade, just make sure you have your permissions set correctly. It can be a bit complicated, but following the proper steps should ease some of those transitional pains!