Difference between revisions of "Using DSA to replace a BigFix Server"
From RiceFamily Wiki
(→Planned Procedure) |
(→Documentation) |
||
| Line 13: | Line 13: | ||
= Documentation = | = Documentation = | ||
| + | * [https://forum.bigfix.com/t/question-about-using-dsa-to-retire-a-bigfix-master-server/26624 Question I asked on Forums] | ||
* [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/DSA%20Disaster%20Recovery DSA Disaster Recovery] | * [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Endpoint%20Manager/page/DSA%20Disaster%20Recovery DSA Disaster Recovery] | ||
* [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Endpoint+Manager/page/Distributed+Server+Architecture Distributed Server Architecture] | * [https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli+Endpoint+Manager/page/Distributed+Server+Architecture Distributed Server Architecture] | ||
Latest revision as of 21:38, 26 July 2018
History
We installed BigFix on two Physical Servers (PHW-TEM-PRI and PHW-TEM-SEC) and now need to replace them with Virtual servers.
Planned Procedure
- (DONE) - Build DSA Server OS
- (REQUESTED) - Have SQL 2016 installations removed and replaced with SQL 2008R2 to match the existing systems
- Install BigFix in Replication mode using existing Masthead
- Ensure accounts and access match in SQL on the new BigFix Server and the Current BigFix server
- Let servers settle and replicate
- Promote New Server to Master status
- Change DNS Registration so that the Masthead still points to the BigFix Master Server
- Test MFA and fix anything that's not working properly.
