none
How to ask a question efficiently in TechNet forum RRS feed

  • General discussion

  • Thank you for posting in TechNet forum. The online problem solving can be relatively time consuming because it may demand several messages back and force to fully understand the symptom and background, especially at the very beginning. Here are a few suggestions that help you get the best answer to your question as quickly as possible.

     

    When You Ask

     

    1. Selecting a good title which summarizes the specific problem you have. It will be the one of the main driving forces for others to want to actually read your item. Choosing a badly-formatted title will drive people away, thinking that since the title is so badly written, so must be the information and the question within the thread.

     

    2. Provide all the necessary information in your initial post. The following information would be very helpful:

    - Symptom description: Detailed description of the problem. If you receive any error messages, please let us know the exact error WORD BY WORD.

    - Environment: The system environment, such as your OS/application version, your network topology, and your domain environment, etc.

    - Any recent relevant configuration change(s): If the issue started to occur after installing any application/updates or changing the configuration, please let us know.

    - Any additional information. Tell what you have done prior to asking your question. This will help us understand that you've done so far.

     

    3. Write in a clear language. Avoiding spelling mistakes or grammatical errors. Don't type IN ALL CAPS, which in most cases is read as shouting and considered rude.

     

    4. Keep with the same thread. Do not refer to a post you made last year, and above all, Please come back. There are hundreds and thousands of posts where we have seen people given great and wonderfully long answers yet no reply from the original poster.

     

    5. Be courteous to reply, even if it's to say. "I've given up" or thanks that worked. (This helps the whole community when you do this, and makes the people who donate time, warm and fuzzies.)

     

    When answered

     

    Give Positive Feedback. Once you've received a correct answer to your question, either from a Microsoft employee, an MVP, or the community in general, pleases replies that the issue or question has been answered. And if possible mark the solution as answered: This step is important, since it lets other people benefit from your posts.


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, October 14, 2011 2:52 AM

All replies

  • Few other tips for having good and many replies:

    Never state you tried everything, as it is probably not true and it might stop people from posting a possible solution. Instead be honest  and  list those things you investigated, or did not investigate and why, and the result of your investigation. This will help answerers giving good solutions.

    Be polite and humble: in fact you are looking for voluntary assistance from people who know more about the subject than you. For example, stating that you are a very experienced guru, might lower the amount of answers you get, because less expierenced people are less inclined to think along. The same goes for swearing or abusive behaviour. Allthough you may not (or no longer) like the product, you are looking for a specialist for the product, and he will probably like it (else he probably wouldn't be specialist...). Stating the product is crap or should never have been sold, might be true, but it will seldom raise positive feelings on the side of the specialist.

     

     


    MCP/MCSA/MCTS/MCITP
    • Edited by SenneVL Tuesday, October 18, 2011 3:16 PM
    Tuesday, October 18, 2011 3:14 PM
  • migrating to linux i dont care i cant have any help
    Friday, August 10, 2012 6:19 PM