Symantec system center not updating

For quality change management you should always opt for the least amount of complexity, which means a centralized in-house system for pushing out patches, software, antivirus updates and configuration settings.

This will allow you to the best opportunity to track your systems and plan out your changes, as well as reporting on the results.

We didn't have the budget for an official clustering or load balancing solution, so I developed a failover plan with a backup server: This meant the backup server could "become" the primary server very easily just by updating the associated DNS record and users could be redirected to it in short order (many wouldn't even notice the interruption).

This included drive mappings and file share access.

Change management (also known as configuration management) isn't always safe or easy.

Whether a file server, email server, storage device, or something else, you should always migrate to a new system leaving the old one intact until you've pronounced the change complete. For instance, if updating a Windows 2008 file server to a Windows 2012 system copy all the data (with permissions!I didn't mind this step since I felt fortunate to have the old system available for use!I grew up in the 1970's and greatly enjoyed the show "The Dukes of Hazzard." I especially liked the scenes where the good old Duke boys jumped a river or canyon in the General Lee – since the police were usually chasing them they generally had no choice but to try to make that jump. Climbing through the window of the General Lee is no way to start a change project in the data center.When patching servers, for instance, don't patch the second set of systems until several days have passed to give you some time to spot and correct any issues…during which you'll need to rely on the systems which are still functional.

Leave a Reply