Software Systems Documentation

Document your Microsoft Windows software systems configurations.

If you seriously want to drive down your computer support costs, maintaining software configuration consistency is just as important as PC hardware standardization.

Consistency Breeds Predictability and Reliability

By applying the same desktop PC and notebook configuration settings across the board, you’ll avoid reinventing the wheel every time you do a PC upgrade.

At the same time, your computer support predictability and reliability will improve dramatically.

Software Systems Documentation: A Valuable Troubleshooting Tool

By developing this configuration consistency into some kind of system documentation, you’ll build up a checklist to use when troubleshooting problems. In addition, this checklist becomes invaluable when you’re planning a major upgrade to the next version of Microsoft Windows. This documentation is also crucial for cross-training a second internal guru, or hiring a new computer consultant, if the need should arise.

Suggestions for Getting Started with Software Systems Documentation

This documentation does not even need to be a huge project.

You can start by consolidating and organizing all your notes on how you configure various PC hardware, software and networking products. Place these notes into a numbered, step-by-step Microsoft Word document or Microsoft Excel worksheet. Just as important, be sure to revise this living document periodically to reflect any changes to your company’s PC standards.

For most small businesses, you’ll likely have a slightly different set of configuration settings for each geographic location, such as your main office and any branch offices or field locations.

Software Systems Documentation Action Items

How consistently do you install and configure various software applications, utility programs and user profile settings on the desktop PCs and notebooks in your company?

Do you have any troubleshooting checklists that you use for common software problems?

Have you developed and do you maintain any written documentation (i.e. master build documentation) for how desktop PCs and notebooks are configured?

Can a backup person easily follow this documentation when the internal guru is out of the office?

Does your documentation include system-wide items such as the default administrator account and password, file system, virtual memory paging file size and location, as well as OS and software application service pack and service releases?

How well documented are your standard conventions for peripheral configurations, for items such as battery backup units, modems and printers?

Do you have adequate documentation of networking and user profile standards such as Desktop Shortcuts, e-mail configuration, drive letters, custom Registry entries, Startup Group items, virus protection software defaults and Web browser settings?

 

Linux vs. Windows : Next >>