NCM is nice if you have the same auto attendants, etc all around. It automates patching (meaning you can roll patches out on a schedule after hours). It's also nice for centralizing backups.
You can't do "set admin" though, meaning make programming changes to sets, etc. You can make a "template" which is handy if you roll out more systems.
NCM is nice for a really large environment (50 sites or more). I would say with 12 sites, if your environment is fairly static (meaning not a lot of changes, etc), pass on NCM.
I have 60 BCM sites and I maintain then without an NCM, I do all the changes from the home office. each site has a seperate server that I send a backup to each night at 11:59 PM and a backup on each E: harddrive. I control everthing including resetting Vmail password and MAC's.
I prefer FTP because it's offsite and you don't have to worry about shared drive permissions.
All of my customer BCM's (and Contivity's and anything else that will handle it) all backup to 1 FTP server as a value add to their service contract (schedule varying based on the level of service the subscribe to.) They can schedule their own backups to their own devices and worry about their own permissions etc, but I maintain an offsite backup.
It's worked a treat for the 2 customers whose Hard Drives have needed to be replaced/reimaged.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.