When we first setup BigFix, we had our masthead to use our server name. ie bigfix.company.com
We now need to migrate to a new server (Windows 2016 → Windows 2022). Rather than rename the new server as part of the migration, could we build it as bigfix_2022.company.com and alias bigfix.company.com to bigfix_2022? It is really that simple or am I missing something? And I realize we need to migrate a bunch of stuff over, I’m just thinking about avoiding renaming servers at this point.
Yes, the server name can be it’s own hostname and can have the name in the masthead as an alias. The issue with this will be that both servers can’t be online/reachable at the same time for content/clients migration etc. Some steps to help with this:
Export/Save content and move them out of the old root server
Isolate the old root server during the migration, follow rest of the server migration steps and confirm the functioning of the new root server
If I'm understanding the question correctly, you should not have to perform a masthead switch. As long as you're able to point the name in the existing masthead to the new server (via a DNS alias for instance), then you can continue to use the same masthead.
Documentation references:
Let us know if you have any questions/concerns here. We can go into a lot more specifics if you'd like...