Templates can help to significantly simplify the process of developing a Wiki article.
The objective of this article is to provide you with instructions on how to write Wiki article about troubleshooting an issue.
It is based on the Microsoft KB schema.
This template is a work in progress, please feel free to add to it.
It is a best practice to leave an area that you cannot currently fill in blank.
This way others can fill it in if they have the information.
This is called "stubbing" on the wiki.
Describe the problem.
What actions were you trying to complete?
What systems and software were you using?
What error messages are shown?
Please include screenshots.
Include any related symptoms that typically occur.
Tell the reader which event logs to check, and typical things to scan for.
It is a best practice to use keywords of the symptom and/or the actual error number in the title of the troubleshooting article.
This helps folks with the issue find the troublehsooting article.
If known, describe the cause of the problem, or the steps to take to determine the cause, including diagnostic tools to use and messages/errors to watch for.
What did you do to fix the issue?
Include permissions required and procedural steps/sample scripts/commandline actions.
Feel free to add screenshots and flowcharts>
Links to similar problems or solutions.
Link Related Issues you have seen on a TechNet forum.
This section provides links to other related solutions, examples and/or information anywhere on the internets.
You should also provide links to helpful material consulted while working on the topic.
It is always a good idea to add a feedback box to a Wiki troubleshooting article.
Below are examples for feedback boxes for Windows Azure AD and FIM ScriptBox scripts.