Though some may feel this is unnecessary, there are more and more posts lately that do not fit these few basic mores. This brief How To will help provide guide lines about creating a post that will not only help us help you, but help you get an answer for your question.<\/p>\n
Search before you post<\/p>\n<\/div>\n
Don’t title your post PLEASE HELP!!! or ITS BROKEN!!! I can’t speak for other members of the community, but I tend to ignore posts with these titles. I want to know exactly what the post is about before I click on the link.<\/p>\n
Instead title your post, Problem scanning Windows 7 computers, or How do you track… Be specific, but keep it brief and explanitory<\/p>\n<\/div>\n
This is where you will give details on your issue. For example:
\nAre you using a remote collector?
\nIs it wide spread or confined to a single machine?
\nDo you get any error messages? (post the error)<\/p>\n
You get the picture. Again try to keep it brief and explanatory, I don’t like having to dig through an essay to find the details that will help solve your problem<\/p>\n<\/div>\n
dnt abreviate. its anying. lk omg ttly. This is a professional community full of professionals. I try to write as if i were communicating with my boss.<\/p>\n
ALL CAPS ARE LIKE YOU ARE YELLING THROUGH THE
\nCOMPUTER<\/p>\n
Standard acronyms such as DNS and POP don’t need explanation, most of the time, but there are some out there that do. If there is any question, explain it.<\/p>\n
Please use proper punctuation and caps (See above)<\/p>\n<\/div>\n
Posting your anti-virus problems in the water cooler or spiceworks support is not going to help you, or us.<\/p>\n<\/div>\n