Hello All,We have a requirement to upgrade our SEPMs OS. Our environment is currently 3 sites with 4 servers. 3 servers use a SQL database and one uses an embedded DB. My thought was to just create 4 new SEPMs on the new OS add them to the respective sites (except for the one with the embedded DB I would create a new site for that). Wait a while to ensure data has been replicated and there aren’t any issues and then slowly pull the old SEPMs out of the various sites. Is there any issue with doing the upgrade this way? Initially I think it would work fine I am just unsure about down the road if there would be any issues when trying to do another upgrade.
Would a better option be to configure new sites and add them in as replication partners? We also have an initiative to upgrade our SQL server. Symantec has steps on how to do this but with the need to update our servers to I wasn’t sure if it would make sense to just build a new SQL server configure the new SEPMs to use that add everything in as new sites wait for replication etc. and pull out the old infrastructure?
I don’t see a problem with doing either as the version of SEPM will remain the same just the OS is changing.
Just planning out a upgrade from 12.x to the latest 14.x version.
The site is very small and I am looking at reclaming a MS SQL license.
Is it possible to update the old version to 14.x then replicate across to the new 14.x version on the internal DB.
The 12.x upgraded version will be using MS-SQL.
I currently have 2 SEPM using 1 SQL server, servicing 1800 clients. Everything is currently running Server 12 R2. I was thinking of spinning up another SEPM to help with the load. I was curious if 1) If it’s possible to run 3+ SEPMS accessing one database. 2) If possible, do I have to stay with 2012R2 or can I use 2016 for the new SEPM?
I appreciate any guidance.