thank you very much for your helps. However those guides is not actually good for our end users.A bit technical and also too complete.Some features even they will not use.
That's why we need to customize and also i need to create the guide for administrator . Just for manage some functions only , such as: adding new phone, create new user ,assign phone to user , creating FAC. It's for day to day operations.
Thank you for all helps. Appreciated it you guys can provide above.
Like Rob showed on his document, typically, if you are a professional server provider, you will need to create your own "how to" document because every enviroment changes. Day to day operations changes in every enviroment. You could create a "boiler plate" and then work from there, but as far as i know, Cisco does not have any "boiler plates" I have created my own for each customer I have installed if requested. Most of the time, the admin is supposed to know how to setup a MACI in CCM already. If they do not, they are in big trouble when the handoff happens. I think your bigger issue is to make sure your admins are trained for ccm.
Rob's is an end user guide. What you want is an Admin Guide. Probably a good Cisco Press book may help you But if you are good with Word and screen caputre shots, you can create a pretty good "admin book" for your client. Save it, then updated for the next!
I have attached the user guide that we give to our clients when they receive a new 7940/7960. Please note that I have added xxxx in locations where you will have to insert your specific info. As far as a user guide for admins, you may have to customize that one in-house.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.