Bobby-Notes: Difference between revisions

(Undo revision 21214 by LoLa (talk))
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{ZC}}
=Notes=
==backup/restore related zmlocalconfig keys==
Unset/default backup-related zmlocalconfig keys will not appear because the backup-related keys are defined in the backup extension which is not loaded by the zmlocalconfig script's java classpath. ''Jiho: [http://bugzilla.zimbra.com/show_bug.cgi?id=26624#c17 Bug 26624 Comment #17]''


=Information For New Support Customers=
==disabling xen kernel===
 
http://zackofalltrades.com/2008/09/changing-to-a-non-xen-kernel-in-centos-5-so-you-can-run-vmware-server/
==Details On Response Times and What's Supported==
 
Please review the [http://www.zimbra.com/support/support_overview.html Support Overview] and [http://files.zimbra.com/docs/support/SupportPlan2_2008.pdf Support Plan], specifically the "Exclusions" and "Reasonable Use Policy" sections. You can also find a link to the Support Plan document when you log in to your Zimbra Support Portal account (Network Edition Customers). As of 12 August 2008, it includes the following statement:
 
''Requests that are excluded from support include but are not limited to: performing initial installs of customer systems, performing migrations, performing upgrades of customer systems, performing configuration changes to add or remove servers or services, and testing a customer’s system. Zimbra Professional Services may be available to assist with these projects.''
 
==New Network Edition Customers==
 
Your sales contact should already have made a support record for your company and added one or more user accounts for our primary support tool, the [https://support.zimbra.com/supportlogin.php Support Portal]. Please [http://www.zimbra.com/about/contact_us.html Contact Sales] if you are unsure whether you and/or your company have been set up for access to the Support Portal. Additional user accounts can be associated with your support record if necessary by submitting a case to support with the following information:
* Full name of new contact
* Title of new contact
* Email address of new contact
* Best phone number to reach new contact (''this will potentially be used in the event of an email outage'')
 
==Understanding The Support Process For Urgent Issues==
In order to receive the most efficient and timely response, please follow this procedure.
 
#Create a new case via the [https://support.zimbra.com/supportlogin.php Support Portal]
#*In the lower section of the navigation menu on the left, choose Case Menu > Submit A New Case
#*When you need urgent help, '''please open a case through the Support Portal instead of sending email to support@zimbra.com'''. Cases submitted through email will not be assigned the appropriate urgency for an outage or otherwise urgent situation, and they will appear lower in priority in our incoming case queue. When submitting a case through the [https://support.zimbra.com/supportlogin.php Support Portal] you may assign the appropriate urgency level according to scope, impact, and urgency of issue.
#*Please include as much detail as possible to allow us to effectively prepare prior to calling you. Having details of the situation allows us to reach out to any resources (people) we may feel are needed prior to calling you back.
#*Include contact information in the new case record. Desk phone, cell phone, alternate email address, and YahooIM handle are all useful. This allows us to contact you for clarification as needed.
 
#Call the [http://www.zimbra.com/about/contact_us.html Support Phone Line]
#*If you get the voice mail - don't panic or hang up without leaving a voice mail.
#**Give your name and company first
#**Provide the number of the case that you created in the Support Portal
#**Summarize the outage situation
#**Mention your contact information
#Continue to work on the issue yourself.
#*Promptly update the case with all relevant information you discover
#**Left-hand lower section, Case Menu > Case Management
#**If you can't "email", use the Comments section with your case record to input the information.
#If you have not received a response from us, please try updating the case and calling into the [http://www.zimbra.com/about/contact_us.html Support Phone Line] again
#* Note that depending on the day and hour of your outage, time might be needed for the information to route to the on-call staff and for them to get into a position to respond.
 
==How To Communicate Support Need Clearly==
Over the years, open source luminary Eric Raymond has assembled a guide to getting help with technical issues online. Bear in mind that the guide is written with those seeking free help in mind, so the overall guide taken at face value is most applicable for posting to the Zimbra Forums. There is, however, plenty of useful guidance for those submitting support cases. The complete guide is available online as [http://www.catb.org/~esr/faqs/smart-questions.html How To Ask Questions The Smart Way.] Here are a few examples:
* Use meaningful, specific subject headers
* Write in clear, grammatical, correctly-spelled language
* Be precise and informative about your problem
* Describe your problem's symptoms in chronological order
 
Simon Tatham, author of the PuTTY software, wrote a similar guide for [http://www.chiark.greenend.org.uk/~sgtatham/bugs.html How to Report Bugs Effectively.]
 
=Support Tools=
==Bugzilla==
Zimbra uses the [[Bugzilla]] bug database system. This is a critical tool for Zimbra development, and allows anyone with an account to interact directly with Zimbra developers and product managers. It has been suggested that customers who ignore Bugzilla do so <i>at their own peril</i>. That may sound a little over the top, but you will find that Bugzilla provides fascinating insight and connection to the development process. If you'd prefer not to work directly with Bugzilla, Zimbra Support will communicate relevant case information to the developers. On the other hand, if you'd like to get hands-on with the bug database, here are some basics to get you started.
 
===Create a Bugzilla Account===
This is open to anyone. It's not tied to your Network Edition support id.
*http://bugzilla.zimbra.com/createaccount.cgi
 
===Recommended Saved Searches===
Once you've created your account and logged in, create a search to list any bugs whose progress you are following (i.e. you have added your email address to the CC: field).
#Go to http://bugzilla.zimbra.com/query.cgi
#Decide if you want to adjust the highlighted items under "Status:". You might choose to only display bugs that are still not fixed (UNCONFIRMED, NEW, ASSIGNED, REOPENED), or you might choose to display all of them, or you might choose to create two different saved searches to accommodate both cases.
#Under "Email Addresses, Bug Numbers, and Votes", make sure only the checkbox for "a CC list member" is selected. The "contains" field should then include your email address.
#Click on "Search" at the bottom.
#Scroll down to bottom of search results window, type a name of your choice (e.g. "My CC's") in the field for "Remember Search as", and click the "Remember search" button.
 
When you are logged in, your custom searches will show up in the "Saved Searches:" section at the bottom of Bugzilla pages. You can reconfigure or delete them under the "Saved Searches" tab of your Bugzilla Preferences.
 
 
When a support case is related to a given bug or RFE ("request for enhancement"), it will be cross linked internally between Bugzilla and our case management system. Once you know the bug number, you can add yourself to the CC: field and Bugzilla will notify you of changes via email. With the saved search that lists bugs you are following, it will be easy for you to manage those as well.
 
===My Saved Bugs===
 
There is also a default saved search, "My Bugs". This will list any bugs or RFE's that you have created.
 
===Bugs And RFE's Related To Your Support Case===
 
When you have a case that's related to a bug or RFE, the support staff will add the case number to the bug or RFE, which serves to increase its priority (not the Bugzilla "Priority" field). Note that case numbers are not visible publicly.
 
Here's what you can do in addition:
 
*Login to bugzilla and navigate to the page of the bug or RFE in question.
*Add your email address to the CC field and save.
**You will be notified of updates by email.
*Click on the Vote button.
**This is another way to increase the priority.
 
At this point, the issue in question can be tracked through Bugzilla, and the support case will typically be closed.
 
===Use The Advanced Search===
 
* Navigate to http://bugzilla.zimbra.com/query.cgi
* Click on the "Advanced Search" link if you are not already on the Advanced Search page.
* Shift-click all the items under "Status" if you'd like to include bugs that have already been fixed.
** The default search function only queries against "UNCONFIRMED, NEW, ASSIGNED, REOPENED".
* Add search terms
** Use the "Summary:" field to search bug titles.
** Use the "A Comment:" field to search through bug comments.
* You can also narrow your search by choosing from the "Component:" field. This can be useful when you're using generic search terms, but it can be tricky to identify the appropriate component.
 
==Zimbra Forums==
=== Create A Forum Account===
Please create a forum account. There's a wealth of information and experienced Zimbra administrators that are accessible there.
 
Please see:
* http://www.zimbra.com/forums/register.php
 
==Zimbra Wiki==
 
Here's the direct url to create an account on the wiki server:
*http://wiki.zimbra.com/index.php?title=Special:Userlogin&type=signup&returnto=Special:Search
 
Why is this important?
 
*It allows you to participate in improving the wiki articles and content. You need to be logged in to make edits.
**You can make your own articles if you find something missing that might prove useful to others.
**You can improve existing articles.
**You can also add to the "discussion" page for an article. This is a good section to add comments for those less inclined to be '''bold''' and modify the main article.
***You can propose questions and other things here as well.
*You can add article pages to your "watchlist", so you can monitor your favorite articles for changes.
**You can also setup in your preferences to be notified by email in regards to changes.
*You can have your own personal section on the wiki.
**Just use the category of "community sandbox" at the bottom of them.
***<nowiki>[[Category: Community Sandbox]]</nowiki>
**My recommendation if you decide to create articles would be to add your username in front of the topic:
*** Username-Topic , for example - Ajcody-New-Customers
**And then add this under your own user profile page [for example - http://wiki.zimbra.com/index.php?title=User:Ajcody]
*** <nowiki>{{:Special:PrefixIndex/YourUsername}}</nowiki> , for example - <nowiki>{{:Special:PrefixIndex/Ajcody}}</nowiki>
***This will then automatically list out all your articles under your username.
 
==Yahoo! IM==
 
Most of us in support have YahooIM accounts and this can prove useful even when on a telephone call since it speeds up the sharing of information. It's to the discretion of the support staff to offer the IM session.
 
Please see:
* http://messenger.yahoo.com/
 
==Remote Server Access==
 
===Support SSH Keys===
 
If you log into the support portal with your account, you'll find reference to ssh keys that can be used.
 
====Screen Sessions With SSH====
 
Please review the following if you aren't familiar with screen.
 
* http://www.linux.com/feature/56443
* http://www.pixelbeat.org/lkdb/screen.html
 
===Sun Java Shared App===
 
If your a fan of Sun, look at their shared app:
 
* http://www.sun.com/service/sharedshell/
 
=Installation and Migration Planning=
 
===Expectations===
 
Support doesn't do migration for customers, nor do we do migration planning.  We can help if you run into issues during migration. Are there gray areas involved in this? Yes, of course. Some guidelines to follow:
 
* Engage your sales contact about your needs.
** Sales has access to pre-sales engineers and tools that can help plan your Zimbra deployment and migrations.
** If your needs exceed the above, they can determine if our Professional Services group would be a good option for you.
* When you start to engage the Support Team
** Try to have specific questions or issues rather than large open-ended ones - those that imply support is doing the planning or migration for you.
** It would be helpful if you documented your "plan" to the best of your ability and to share that with support as issues  or questions come up.
*** This gives us more "concrete" information to work against.
** Be prepared to know and investigate the technical requirements for the "other" mail server. Support will offer what we can but there is no obligation for us to know all the in's and out's of another mail server product. The exception to this would be when we are working with our tools that we developed for migration. And even then, there is a certain expectation of knowledge we require of the administrator in regards to the other mail system.
* Remember, anyone can use the Zimbra Forums! Advise and help is free and open to everyone on the forums.
 
===First===
 
Please take time to review the Administrators Guide. Noting what features you might want or need for the installation. It would be wise to make notes while your skimming the guide of features your wanting. Depending on the choices you have, it might drastically effect your installation steps. Do you want HSM, Archive & Discovery, Proxies - what type, and so forth.
 
* Official Administration Guide
** http://files.zimbra.com/website/docs/Zimbra%20NE%20Admin%20Guide.pdf
 
===The Basics===
 
====Starting Official Source Guides====
 
* The Main Page
** http://www.zimbra.com/products/documentation.html
* The Release Notes
** http://files.zimbra.com/website/docs/Zimbra%20NE%20Release%20Notes.pdf
* System Requirements
** http://files.zimbra.com/website/docs/Zimbra%20Collaboration%20Suite%20System%20Requirements.pdf
* Quick Start Installation Guide
** http://files.zimbra.com/website/docs/Zimbra%20NE%20Quick%20Start.pdf
 
====Other Resources To Review====
 
General Ways To Find More Specific Information:
 
* Search Zimbra Site
** http://www.zimbra.com/search/
*** Notice that you can refine where your search looks, click on the "Advanced Search" link next to the search button.
* Looking at "Categories" within the Wiki pages. This might be more helpful compared to a general search.
** http://wiki.zimbra.com/index.php?title=Special:Categories
* My wiki notes are actually spread out among multiple pages but I also have them displayed into one page. This makes it easier to search the table of contents or the complete listing using your web browser (usually ctrl-f).
** [[Ajcody-Notes]]
** I had to separate my Server related notes from this table of contents, please search this one as well:
*** [[Ajcody-Server-Topics]]
* Still confused by HSM, see the following:
** [[Ajcody-HSM-Notes]]
* GAL - Global Address Book Items To Consider
** [[Ajcody-Notes-ServerGAL]]
* SSL Certificates
** [[Ajcody-Notes-SSLCerts]]
* Proxy Items
** [[Ajcody-Proxy-Notes]]
* What about Mobility Options?
** [[Ajcody-Mobile-Topics]]
 
====Please Consider Your Backup Issues Before Deploying====
 
Assuming you've consulted the other above resources as well.
 
More items to consider:
* Backup Plans
** [[Ajcody-Server-Topics#What_About_Backups.3F_I_Need_A_Plan|What About Backups? I Need A Plan.]]
* General Backup / Restore Issues
** [[Ajcody-Backup-Restore-Issues]]
 
====Be Aware Of DR Processes====
 
* [[Ajcody-Notes-Multi-Server-Restore-DR]]
* [[Ajcody-Disaster-Recovery-Specific-Notes]]
 
===Multi-Server Installations===
 
Assuming you read or skimmed the above.
 
====Starting Official Source Guides====
 
* Main Page For Them
** http://www.zimbra.com/products/documentation.html
* Multi-Server Installation Guide
** http://files.zimbra.com/website/docs/Zimbra%20NE%20Multi-Server%20Install.pdf
* Migration Wizards, Connectors, and Clusters Guides
** http://www.zimbra.com/products/documentation_additional.html
*** Cluster Guides
**** Single Node Cluster Installation Guide
***** http://files.zimbra.com/website/docs/Single%20Node%20Cluster%20Installation%20Guide.pdf
**** Multi Node Cluster Installation Guide
***** http://files.zimbra.com/website/docs/Multi%20Node%20Cluster%20Installation%20Guide.pdf
* Archiving and Discovery
** http://files.zimbra.com/website/docs/Zimbra%20NE%20Release%20Notes.pdf
 
====Other Resources To Review====
 
* Understanding your hardware issues - work in progress still.
** [[Ajcody-Notes-ServerPlanning]]
* Archiving and Discovery For Multi-servers
** [[Ajcody-Notes-Archive-Discovery]]
* Issues Around LDAP Master And Replica Install/Setups
** [[Ajcody-LDAP-Topics#Can.27t_Setup.2FInstall_LDAP_Replica|Can't Setup Install LDAP Replica]]
 
===Migration Issues===
 
* My Migration Issue Notes
** [[Ajcody-Migration-Notes]]
*** This will also reference other necessary documentation.
* Understanding Mailing List options
** [[Ajcody-MailingLists-And-Mailman]]
* MTA/Postfix differences you might need to be aware of
** [[Ajcody-MTA-Postfix-Topics]]
 
=Yahoo! Hosted Zimbra=
 
Public documentation is at:
*[[Hosted_FAQ]]
 
Customer Documentation is in the support portal. The url is, you'll need a support portal account to login with:
* https://support.zimbra.com/ccaredocs
** Has, as of today (Oct 15, 2008)
*** Hosted Customer Care Application Guide
*** Hosted Integration Guide
**** Branding Instructions are located here.
*** Hosted Zimbra Web Client Guide
*** Support Program Plan
*** Zimbra Hosted Packaging Options
 
===Hosting Bugs And RFE's===
 
Use this url to see the "public" bugs & rfe's that are tied to hosting.
 
*[http://bugzilla.zimbra.com/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=ZCS&component=Hosted&long_desc_type=anywords&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&testcase=&support=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= Hosting Bugs & RFE's]
 
This will pull all of them regardless of their "status".
 
=Quick Tips=
==License issues (Dos/Unix New Lines)==
 
vi file and then
 
:set list
 
Confirm your not getting the ^M characters at the end.
 
[[Category: Community Sandbox]]


test


[[Category:Community Sandbox]]
[[Category:Community Sandbox]]

Latest revision as of 04:25, 21 July 2016

Notes

backup/restore related zmlocalconfig keys

Unset/default backup-related zmlocalconfig keys will not appear because the backup-related keys are defined in the backup extension which is not loaded by the zmlocalconfig script's java classpath. Jiho: Bug 26624 Comment #17

disabling xen kernel=

http://zackofalltrades.com/2008/09/changing-to-a-non-xen-kernel-in-centos-5-so-you-can-run-vmware-server/

test

Jump to: navigation, search