Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Migrating Altiris CMS 7.1 and database to new server

Created: 08 Aug 2012 • Updated: 09 Aug 2012 | 6 comments
This issue has been solved. See solution.

I need to move our Altiris CMS 7.1 installation to a newer server. I would like to move the database to the new server also.

The current server is running Windows 2008 R2 and SQL 2008 R2, the new server would be running the same. The only reason we are needing the upgrade is for performance issues and disk space.

I could leave the database on the current server, but I would like to move both CMS 7.1 and the database to the same server.

Thanks in advance for any assistance.

 

 

Comments 6 CommentsJump to latest comment

Zac H's picture

For performance reasons, it's almost always advisable to have SQL off-box.  So why not take this opportunity to do just that?

MavLS's picture

So my question would be if I leave the SQL on the old server, would I just need to install another instance of CMS 7.1 on the new box and point it to the SQL server on the old box ? Also what about uninstalling CMS from the old box ?

david_winmill's picture

So my question would be if I leave the SQL on the old server, would I just need to install another instance of CMS 7.1 on the new box and point it to the SQL server on the old box ? Also what about uninstalling CMS from the old box ?

 

First you'll want to setup a redirect for Agents, so that they can get to the 'new SMP server' without any real hassle or reinstalls required. Since the FQDN would be changing, this would have to be done to ensure they are automatically redirected instead of having to script out a change through a GPO.

Then you would install CMS 7.1 with the same solutions and versions (updates, SP's etc) as were on the existing server. I would recommend installing to a blank DB at this point, so that you don't cause any conflict with the existing DB or corrupt any data. Once you have that up and working (ie you can get into the console and no major errors), then redirect to the existing DB.

After you've redirected the new server to the DB and functionality is restored, you should be able to disconnect the old system and uninstall CMS.

 

SOLUTION
Zac H's picture

I notice that you didn't mention things like the Software Library.  I'd assume that directory structure would be have to mirrored and moved to the new NS as well, correct?  

Additionally, since Altiris can be pretty DB intensive, have you fully determined the cause of the performance bottleneck?  It's possible that you may benefit more from moving the DB to the new (and assuming more powerful) server.

MavLS's picture

Thank you both you have got me pointed in the right direction, I really appreciate your help.

 

MavLS's picture

Our Software library is pointed to another server and not that extensive. It is not that the NS server is that bad it is more a case of the server we are running is about 6 years old and  I have a newer server running 15K hard drives in a Raid 10 config. Newer processors and serveral more cores running along with 26 gig of ram that I ordered to replace the old server. I may indeed move the DB to the new server,