hello, I couldn't find an answer on how this differs from performing a Server upgrade but in your environment, IT wants us to switch the domain that the Server is hosted on. Is there documentation on how to perform this?
Or do we just run Server backups, allow IT to perform the Domain change, and then perform the Server Recovery using these same steps?
And then update the users inside the Mongo DB?: https://knowledge.alteryx.com/index/s/article/How-To-Manually-Change-A-Domain-User-To-New-Domain
We are on Server 2022.3.
I'm just curious if there's anything else to know or consider before migrating, thanks!
Solved! Go to Solution.
Hello @patrickmckenna88!
I think this may be a good candidate to report through Mission Control (my.alteryx.com) to ensure Customer Support is aware and can provide insight into resolution. The case submission process will also search the Knowledge Base in case there is a known solution.
Yep, agree with Matt. This would most likely be the equivalent of changing Authentication method. Although you will still use the same authentication method, it will be on a new domain and so functionally the same as that, without the added complication of different tables in the Mongodb.
I believe (and this is just my opinion as I can't back it up with any evidence currently), that solution to change a single user is maybe a "fix" not a solution. I'm not sure if it's advised for an entire user base. But Support will be able to at least confirm/deny that.
Reasons to try this fix are that you may not have to change API keys and links to workflows on the server. And so I can see the advantage if this works for the whole user base. But I wouldn't do it without confirming with support that it will work well.
Hello, in case anyone looking for this topic here's what I received from Alteryx Support:
To migrate Alteryx Server to a different domain, you will need to follow a specific process that differs from a standard server upgrade.
Backup Current Configuration and Data:
Ensure you have a complete backup of your Alteryx Server environment, including workflows, schedules, user configurations, and any custom settings. This step is critical to safeguard against data loss during the migration.
Update DNS Settings:
Verify that the new domain is correctly configured in your DNS. This involves updating the DNS records to point to the new domain and ensuring the server's Fully Qualified Domain Name (FQDN) aligns with the new settings.
Reconfigure Alteryx Server:
After migrating to the new domain:
Update server settings to reflect the new domain, including server name and FQDN.
Reconfigure authentication methods, such as updating Active Directory integration for user authentication.
Review and adjust user permissions to ensure they remain consistent under the new domain.
Test the New Setup:
After completing the migration, thoroughly test the server to confirm that:
Workflows run as expected.
Schedules are intact and operational.
User access and permissions are correctly configured.
External integrations or APIs function properly.
Here is the help document that might assist you:
https://help.alteryx.com/20232/en/server/best-practices/server-upgrade-best-practices.html#section-5...
User | Count |
---|---|
4 | |
1 | |
1 | |
1 | |
1 |