IT Services

Management Services

 

IT Blog

 

IT planning essentials

Overlooking basic IT planning is the norm at most small businesses. That’s like not having a plan for life—without a plan, a business may end up with anything, or nothing at all.

The basic elements of IT planning include:

  • A Management Information Systems (MIS) Master Plan: This plan contains strategic planning and usually also functional planning, that is, plans for implementing the IT strategic plan.  The MIS Master Plan should be a component of the overall strategic plan for the business if one exists (as it should).

  • A Disaster Contingency Plan: This plan lays out how a business will respond to (and recover from)an IT disaster that destroys the IT infrastructure and/or the data of a business. A fire or a tornado are among the possible disasters that could destroy its IT.

  • An IT budget: A business should have an annual budget for IT. If a business has an Information Services (IS) department, the budget should include all expenses related to IS.  If a business is too small to have an IS department, it should still include the cost of any IT firm or person as well as the cost of labor for the time employees or other consultants spend on IT. A rule of thumb is that 1 percent of gross income should be set aside for IT.  If that amount is unspent during a fiscal year, the funds should be carried over into the next fiscal year and earmarked for future IT expenditures.

  • System development plans: These are plans for specific projects; therefore, for our purposes, they are project plans. A project plan includes the cost estimates (budget), timeline with benchmarks (objectives) and personnel for a project. A project plan is usually the responsibility of the senior project manager. Obviously, it should concur and align with the MIS Master Plan.

Most businesses have an IT infrastructure before getting around to planning.  There are tools for assessing what IT a business currently has, information that is fed into MIS master planning or system development plans. Chief among those tools are:

  • An IT infrastructure study: This is an overall survey of the IT of a business.  It includes not only a survey of hardware and software but also interviews with the principal stakeholders, usually managers. The findings of such a study are presented in a written report and may also be presented orally in a formal meeting using aides such as PowerPoint.

  • Process studies: These studies determine what data is fed into IT, where it originates, how that data is processed, what information is output and who receives it. A common tool for doing a process study is SIPOC analysis.  SIPOC is an acronym for Source, Input, Process, Output and Consumer.  In a larger organization, a SIPOC  analysis is usually done for each department.  In a small business, a SIPOC analysis will include the entire organization.

Zadada is experienced at and fully capable of doing any of the plans or studies mentioned in this posting.

Controlling  IT expenses

Many small businesses are committed to an IT firm, or in some cases, to an IT person, who performs routine maintenance. This is all well and good provided the people or person doing the work knows what he or she is doing, but it can trap a business into unexpected IT expenses if a project comes along. The reason is that the IT person or persons will usually bill at an hourly rate with no estimate. No estimate means no cap on project cost. Businesses should be especially wary if the IT firm proposed the project rather than the business.

A business contemplating any significant project should obtain competing estimates from at least three IT firms. (Hopefully, the business wasn’t naďve enough to sign a contract making granting its IT firm exclusive rights to any IT work.) Obviously, we would like Zadada to be one of the firms providing a proposal.

Don’t expect any IT firm to provide a flat-rate estimate.  Few, if any, experienced firms are willing to work on that basis because of inevitable “scope creep.”  The client usually expects far more from the IT firm than originally envisioned by either party. The estimate will be based on an hourly labor rate but there will be differences from the IT person(s) of a business doing the work and billing the business after the fact.

Firstly, the IT firm or person will be working against an estimate; therefore, the IT person has a responsibility to attempt to keep costs in line with that estimate to a reasonable degree. Secondly, it prevents padding fees in various ways, such as adding “business expenses,” fees for travel time and price mark-ups on any hardware or software required. Thirdly, a proposal should include a timeline for project completion with benchmarks along the way. That will help to prevent an IT supplier from running up the bill by dragging out a project.

In summary, always get competing proposals for projects and ensure the proposals contain the following elements:

  • A good-faith estimate covering all project expenses.

  • The hourly labor rate.

  • A timeline with benchmarks.

  • Explicit language regarding mark-ups on hardware and software.

  • Identification of the person or persons who will do the work, which should correlate with the hourly labor rate.

A business can ensure the proposals contain these elements by specifically requiring them in the request for proposal (RFP), even if it is only an email message.

Another consideration and another reason to request proposals are the qualifications of the IT persons involved. For example, if a project involves a network or security, some specific, high-level skills are needed, skills the average IT guy or gal doesn’t have. Zadada ensures that consultants with the required skills and decades of experience are assigned to any projects it undertakes. And we don’t mean basic skills, just enough to “wing it” through a project.  We mean the most advanced skills that can be found plus 20 or more years of specific IT experience.

One final note on controlling IT expenses: it’s a good idea to have an IT budget.  More about that in our next blog post.

Security

Security is a very important issue for small businesses, especially those accepting credit cards or storing personal data such as patient information. There are few businesses that do not need to be concerned about security.

There are two general categories of security, software-based security and hardware-based security. All businesses need software-based security. You are probably familiar with the leading brands of it: McAfee, Norton and ESET, to name a few. Which is best is debatable; however, Norton is highly rated. The anti-virus/security software Zadada most often install is either Norton Antivirus or Norton Internet Security. On the other hand, some of us find Norton to be unnecessarily intrusive and therefore prefer use to ESET on our personal computers.

Antivirus and security software is relatively inexpensive. A one-year license for Norton Antivirus costs about $19 if ordered online. A one-year Norton Internet Security license costs about $26.

As you no doubt know, antivirus software is sold on a subscription basis with annual renewals. The best antivirus applications also guard against adware and spyware.

The other category of security is hardware-based. It includes the purchase and use of a security appliance. Our technical manager prefers those made by Cisco such as the Cisco SA520. Costing about $700, these devices are not cheap but they are essential for businesses storing highly sensitive data such as credit card numbers and patient information.

Businesses accepting credit cards are now required to verify the data is secure. This is dictated by Payment Card Industry (PCI) standards and administered by intermediaries such as ControlScan.

Verification consists of completing an annual questionnaire plus quarterly security scans. Most of the questions on the questionnaire are very technical and therefore difficult for many businesspersons to answer correctly. Zadada has a network specialist on staff capable of accurately completing the questionnaire for a business. The quarterly scan, on the other hand, is simple. A business need only schedule it and then complete a brief attestation after the scan is completed. The trick is remembering to run the scan on time and then remembering to perform the attestation afterward.

There are no fees involved in verifying PCI compliance; however, there are substantial penalties for failing to do so. Fines can run into the thousands of dollars.

Networks

 

This discussion of networks is primarily a discussion of options. Here are the local area network (LAN) options for a small business:

  1. No network at all. This is not really an option because nearly every business will have multiuser software running on a server. For example, a dental practice will have Patterson Eaglesoft, PEB XLdent or some other practice management and/or digital imaging software running on a server. A network is required to connect the desktop workstations, laptops and notebooks to the server.

  2. A minimal network. This might be entirely Wi-Fi or it might be combination of cabling and Wi-Fi. Cable is preferable because it is faster than Wi-Fi. An example of a minimal network would be cable from the primary Ethernet switch to the server, with the other devices such as network printers and workstations connected via Wi-Fi.

  3. And all-cable network. This option requires the permanent installation of CAT6 Ethernet cable and associated hardware. CAT6 is an abbreviation for category 6, which is a stringent standard for Ethernet cable. This is the preferable option but is relatively expensive. Fully cabling a practice or other business that has half a dozen rooms (drops) costs over $3000. Zadada subcontracts cable insulation to a professional installer.

Most software companies such as Patterson or PEB will expect a client to have a permanent network installed but they will usually tolerate a mix of cable and Wi-Fi. This is especially true of the means of connecting laptops or notebooks, which typically connect via Wi-Fi.

 

This discussion has assumed a network will be Ethernet, which has over time become the standard network. Nearly all new computers have built-in Ethernet connectivity. In the early days of personal computing, there are other types of competing networks such as token ring and NetWare.

Because many new computers have built-in Wi-Fi as well as built-in Ethernet connectivity, the minimal cost for a network consisting entirely of Wi-Fi is usually only the labor cost for configuration; however, as stated above, CAT6 cable is much preferred due to the faster speed.

 

In addition to the local area network (LAN) discussed above, a practice or business has the option of separate Wi-Fi, if the LAN is cable, and also another separate Wi-Fi for the use of clients, if desired.

 

Related to the LAN, because it is a way to connect to the server, is remote access, which is typically VPN, an abbreviation for virtual private network, that is, a network that uses a public communication medium, usually the Internet, to securely connect to an organization’s LAN from remote locations. VPN is usually installed on portable devices such as laptops. VPN is entirely optional.

Don't sign an IT contract until…

Most clients quickly read contracts before signing them, basically to see if there is anything really unacceptable about the contracts. Don't sign a one-sided contract or one that omits important stipulations. Check the contract for the following:

 

  • The basic information such as the IT firm's name and address and your business name and address is correct.

  • The scope of the project is clearly defined, either in the contract language or in the requirements definition document the contract refers to.

  • The contract should clearly define when it expires. If it expires on project completion, then project completion should be defined. Also, you should be able to cancel the contract by providing notice in writing to that effect. You may have to negotiate whether to allow the IT firm to cancel the project after it has begun, which would be undesirable to you in most cases.

  • The contract should state whether the IT firm can elect to use subcontractors that are not its employees. The use of subcontractors may or may not be acceptable to you.

  • Either the contract or the estimate it refers to should clearly state that the estimate is a good-faith estimate. You may also wish to have the contract state how much deviation from the estimated cost is acceptable.

  • If the IT firm is going to purchase software or hardware for you, the terms for reimbursement should be clearly stated. The contract should also state whether the IT firm can mark up the price of purchases it makes for you.

  • The labor rate and the invoice terms (for example, net/30) should be clearly stated.

  • There should be a provision requiring a written change order if the IT firm will perform work outside the scope of the project, as defined by the contract.

  • The contract should state whether the IT firm charges time portal-to-portal for trips to your business location and whether it charges for mileage. If there are going to be charges for anything other than labor, those charges should be clearly spelled out.

  • The IT firm should carry liability insurance and the contract should state that it does and what amount of insurance is in effect. Liability insurance does not cover mistakes or other non--performance issues.

  • The contract should address the confidentiality of your data as well as the confidentiality of documents generated by the IT firm such as the cost estimate.

This is not legal advice; it is IT advice. Even if the contract meets these criteria, you may wish to have your attorney review it. Whether you do that or not will depend on your comfort level with the IT firm and the contract as well as any past experience you have had with the firm.

How much should IT cost?

This discussion of the cost of IT is based on our real-world experience performing all aspects of IT infrastructure projects for small to medium-size organizations.

 

Considerations:

 

To begin with, the hourly rate quoted by an IT firm tells the client almost nothing, except that a very high hourly rate is obviously going to multiply times hours billed into a costly amount. The hourly rate for an experienced consultant typically runs anywhere from $75-150 per hour. That may seem like a high rate but the consultant must subtract taxes and overhead plus non-billable time and other expenses. The biggest factor affecting a consulting firm’s gross income is the work on the project is usually intermittent, that is, it is not study work. Many clients prefer to do IT projects in phases to spread out the cost, which results in down time for the consulting firm.

 

A prospective client should also consider what the IT firm will provide at no charge. For example, Zadada provides the requirements definition (what is needed), the specifications and the cost estimate at no charge. We also do not bill for any research we need to do to support specific software or hardware. In addition, we do not normally bill for any time spent contacting technical support for a specific product, even if the problem is with the product. You should also ask whether the IT firm bills portal to portal, meaning for travel time, and whether it bills for mileage. Zadada does not bill for either.

 

If the IT firm is going to provide ongoing support after the project, and it should, you should also ask about any minimum rate it charges for on-site visits. Some IT firms charge as much as $300 minimum to go to a client site regardless of the purpose of the visit. Zadada charges a minimum fee of $50 per site visit for providing requested support. Unlike many IT firms, we do not charge a monthly retainer for support.

 

You are advised not to ask for a flat rate for a project. Flat rates are notoriously impossible to abide by due to inevitable changes in scope or differences in expectations between the IT firm and the client. Few if any experienced IT firms will be willing to work a project on a flat rate. If an IT firm quotes an exceptionally low hourly rate or it is willing to work a project flat rate, then most likely it is relatively inexperienced or it is desperate. You get what you pay for.

 

Ballpark cost:

 

Based on our experience putting IT infrastructure into dental practices and other small businesses, basic IT infrastructure for a small office usually costs $10,000-13,000. Why so much, you may ask? The answer is twofold. Firstly, there is considerable hardware and software involved in even a small office infrastructure, including a server, one or more workstations, network hardware, security hardware, cabling and peripherals, plus all the application and utility software other than the core system (for example, practice management or client contact software). Secondly, acquiring, installing, configuring, testing and documenting all of that hardware and software takes time.

 

The way Zadada bills is an exception from the way most IT firms bill clients. We normally bill about 50-60 percent of our quoted rate per hour if we perform a task the client might have been able to perform but which the client preferred we do. Most IT firms are going to bill any time spent on the project at the quoted hourly rate.

 

When discussing cost, another important factor is whether or not the IT firm marks up the price of any hardware or software it acquires for the client, assuming it provides that service. You can expect substantial mark-ups for hardware from core system vendors and usually lesser but significant markups for hardware from original equipment manufacturers (OEMs). Zadada does not mark  up prices. It provides hardware software to clients at whatever its cost was.  It makes every effort to minimize that cost by using established connections to vendors and their sales representatives that it knows and frequently does business with.

 

A rough estimate of the total cost of the project can be derived by adding $1300 per workstation for each workstation beyond the first one to a base cost of $11,000. For example, a server and three workstations on a Wi-Fi network will cost approximately $11,000 plus $2,600 for a total of $13,600. However, we recommend installing cabling is the client is going to occupy the space for a considerable time due to speed and security advantages. Cabling can add $2,000-4,000 to the cost of a new infrastructure. (Zadada has experienced cable installers available.) Workstations do not cost $1,300 but adding one costs that much when everything is considered: a USB backup drive, cabling, software, an uninterrupted power supply (UPS), a monitor and labor.

 

Zadada usually acquires and pays for the hardware and software needed for a project and then seeks reimbursement from the client on a net/15 basis. It invoices for labor weekly, also on a net 15 basis. These terms are negotiable.

 

Innovations:

 

IT is moving towards handheld devices, cloud computing and other

 innovations. Projects can take these into consideration but depending on the core software the IT infrastructure is designed to run, a client may or may not be able to utilize these innovations immediately. For example, dental practices using XLDent can currently use handheld devices in conjunction with that software but only one brand, and it is not Apple. That means your iPhone or iPad is useless insofar as interfacing with XLDent. Other dental practice management software may or may not interface with any handheld devices at this time.

 

Another consideration is whether the core software has been updated to run on the latest version of Windows. Most of the major dental practice management or other core system software modules for other types of businesses now run on Windows 7 but Windows 8 is just around the corner. Microsoft has released beta versions of Windows 8 for testing. The current versions of XLDent, Eaglesoft, etc. may or may not work under Windows 8 prior to being modified. New computers currently come with Windows 7 installed, either the Home version or the Professional version. Zadada upgrades Windows to the Professional or Ultimate versions if the Home version is installed. It remains to be seen whether software vendors can update their software to run under Windows 8 by the time new computers are shipped with Windows 8 installed.

 

Budgets:

 

The money to fund IT projects is often a challenge for small and medium-sized businesses. Businesses should, but usually don't, budget for IT. The lifespan of most IT hardware and software is about three years. Some hardware may last twice that long but not servers or workstations, which will be outmoded in three years. It follows that if your office has a server and three workstations, the cost of replacing your IT infrastructure will be roughly $13,600 at this time, so you ought to be setting aside one-third of that amount each year. If you do not budget and that amount is greater than your spare cash on hand, you may have to finance IT at interest. Even though it is costly, keeping your IT infrastructure current is essential because it translates into efficiency. There is a high return on the investment (ROI) that may be difficult to quantify but nevertheless exists.

Mistakes organizations make when evaluating IT project cost

  • They assume that an estimate from an IT firm is accurate and “in good faith.”  The estimate is accurate and in good faith if the IT firm is both experienced at estimating and reputable.

  • They asked for a flat rate. Flat rates are notoriously unworkable due to changes in project scope and differences in understanding about what was included in the project.

  • They are willing or obligated to pay the IT firm to correct its mistakes or research necessary know-how that it should have had in advance, including some (but not all) calls to product technical support.

  • They purchase the basic IT infrastructure hardware from the software vendor at a substantial mark-up, or they purchase hardware from original equipment manufacturers (OEMs) at list price.  (This is often symptomatic of the, “No one ever got fired for buying IBM” mentality.)

  • They fail to obtain multiple proposals (three or more).

  • They assume the quoted hourly rate is a fair and reasonable going rate, even if it is ridiculously high.  Also, they don’t consider that what sounds like a high rate might not be all that lucrative to the IT firm due to non-billable time, taxes, overhead, etc.

  • They don’t negotiate the availability and terms of ongoing support after project completion.

  • They assume their internal staff can maintain the completed system.  That is essentially impossible due to both the skill level required and the knowledge of the specific system needed.

  • They proceed without an adequate requirements definition that spells out what the objective is and what is specifically needed to achieve it.

  • There is no master IT plan; consequently, innovations such as handheld devices and cloud computing are not taken into account.

  • They fail to understand the necessity of making a substantial investment in data security, including backups and software and hardware firewalls.

  • They don’t include project-related costs such as training, disaster contingency planning and technical and end-user documentation.

  • They don’t consider that the cost of software and hardware could change prior to purchase due to close-outs, sales, new versions or models, availability, etc.

  • They think internal employees can do some of the project themselves.  This is any IT firm’s worst nightmare.  It ought to be prohibited.

  • There is no agreement on what consultants from, or subcontracted to, the IT firm will do the work.  Will it be principal or senior consultants or relative newbies?

Our primary business process

Zadada utilizes multiple business processes, but our primary process is illustrated by the following diagram. Obviously, it applies to IT infrastructure projects versus ongoing maintenance or one-time tasks.

 

 

The critical point in this process is the decision to initiate or not initiate the project, a decision that is based on the requirements, specifications and cost estimate.

Phasing in a new IT infrastructure

The following is a phased, step-by-step approach to upgrading or replacing the IT infrastructure of a small business, one with approximately a dozen terminals and workstations.  It begins at project initiation, that is, after the project has been given the go-ahead.  With the exception of phase 1, there is some flexibility in the sequence of the phases.  For example, workstations could be inspected prior to inspecting terminals and vice versa.

 

This is an example, not a rigid prescription for any business.  Although it is intended to apply to a small business, it could be applied to a medium or large business.

 

Phase

Title

Steps

1

Backups

Inspect PCs

 

 

Develop a backup plan

 

 

Purchase h/w & s/w

 

 

Implement backup plan

2

Network

Inspect network

3

Internet

Inspect ISP and modem

4

Server

Inspect server

 

 

Install Norton Anti-Virus or Norton Internet Security on server.

 

 

Install PC Tools Registry Mechanic on server.

 

 

Move applications and data to new server if applicable.

 

 

Configure server

 

 

Install uninterrupted power supply (UPS)

5

 

Install h/w firewall

6

Terminals

Inspect terminals

7

Workstations

Inspect workstations

 

 

Replace workstations

 

 

Replace monitors

 

 

Install uninterrupted power supplies (UPS units)

8

 

Update software

 

 

Update QuickBooks

 

 

Office productivity software

 

 

Symantec Ghost

 

 

PC Tools Registry Mechanic

 

 

Norton Anti-Virus or Norton Internet Security

9

 

Inspect printers

10

 

Inspect scanners

11

 

Inspect any other IT infrastructure component

Three useful utilities

Two useful utilities that we use on our Zadada computers and also on the computers of clients are Registry Mechanic from PC Tools (www.pctools/registry-mechanic/) and Driver Update from SlimWare Utilities (www.driverupdate.net). Both are licensed for one year for up to three PC's. They cost $29.99 and $29.97 respectively.

 

The functions these two utilities perform – cleaning up the registry and checking for driver updates – would be impossible to do manually, for practical purposes.

 

If you have 4-6 computers, you'll need two licenses, 7-9 computers three licenses, etc. Both of the utilities are downloads that are relatively simple to install. In each case, the user creates an account that can be accessed to download additional copies to other PCs.

 

Updating drivers is not necessarily a flawless procedure. Driver Updates has very occasionally downloaded a driver that crashed the computer when the driver tried to install itself. That is not the fault of Driver Update.  The utility offers the user the option of creating a restore point.  It's a very good idea to do so in case you encounter an incompatible driver that crashes the PC or causes a device to stop working correctly.

 

Driver Update doesn't only download and install driver updates. It also downloads and installs updates to the Microsoft Windows operating system and to application software such as Microsoft Office.

 

A third utility we recommend is Sticky Password from Lamantine Software (http://stickypassword-usa.com/), marketed via cleverbridge.  First marketed in 2001, Sticky Password is among the best password managers available.  The downloaded version costs $24.99.

 

It will initially import your saved passwords from whatever browser you're using; there is no need to enter them into the utility.  Once you've done that, Sticky Password pops in user names and passwords when you bring up a web page.  It will also auto-fill forms.  It's quick, simple and so much easier than remembering and entering user names and passwords over and over.

 

Sticky Password uses complex encryption to protect the passwords it stores.  It can be unlocked to access those passwords by entering a master password.

 

Backups: Step 1 of any IT project

It is good IT management to ensure that, prior to doing any IT work, adequate system and data backups exist and are being run on a regular basis according to a plan. From our perspective as consultants, good backups are also important to protect us from liability for lost system or data files.

 

We don't recommend a do-it-yourself approach to IT, including designing and executing a backup plan, but for organizations that insist on doing it themselves, the following factors should be considered.

  • What PCs or other devices have data on them that should be backed up? The answer will typically include any existing server and any workstations, including desktop PCs, laptops, notebooks, etc.

  • If there are multiple identical PCs, do each of them have the same system image (AKA system configuration) as the others?

  • How many bytes of operating system and program files are on the server?

  • The same question for each workstation.

  • How many bytes of data are on the server?

  • The same question for each workstation that has data on it that needs to be backed up.

  • Can server data be archived and, if it can, how old must it be?

  • If server data can be archived, how many bytes of data will remain on the server?

  • Can workstation data be archived and, if so, how old must it be?

  • If workstation data can be archived, how many bytes of data will remain on each workstation?

  • If server data cannot be archived, how many bytes of data are being added to the server each year? Based on that calculation, how many bytes of data will be on the server three years from now?

If you can answer the above questions, you have most of the information you need to determine how to do proper backups.

 

If you're creating a system backup, which is an exact image of a drive, a USB drive is the most convenient option. The amount of used space on the PC drive dictates what capacity the USB drive must have. They typically come in the following sizes: 500 GB, 750 GB, 1 TB and 1.5 TB and range in price, depending on capacity, from $100-$190. They are sometimes cheaper when on sale.

 

A system backup for a server may require considerably more storage space than a system backup for a PC workstation. A quick check of the space required can be performed by going to the drive in Windows Explorer and then right clicking and selecting Properties. That will tell you the amount of space being used on the drive.

 

An alternative for small amounts of data is online backup. Although advertised as a flashier, more modern way to backup a computer, it is only practical if you have a fast Internet connection, at least 2 MB per second upload speed. The disadvantages are it may take longer to back up files and there may be a subscription fee for the storage website. The advantages are convenience and the fact that the data is stored off-site.

 

There are several options for data backup. If you're backing up no more than 32 GB of data from a PC, you have the option of using a flash drive. A 32 GB flash drive typically costs about $70 but sometimes costs considerably less on sale. Sixty-four GB flash drives are available but they are expensive, $130 or more, compared to a higher-capacity, portable USB drive,

 

If you are backing up more than 32 GB of data, the most convenient method of backing up data is a portable USB drive.

 

Having determined the amount of space needed for creating a system or data backup, one can obtain the necessary storage devices or subscribe to online backup. It is good practice to have two USB drives for server data and rotate them off-site, meaning one is always off-site and one is always on-site except while in transit. A third USB drive is needed for the server system backup.

 

One USB drive is needed for each unique workstation image, for each unique system backup. One of the three alternatives – online backup, a flash drive or USB drive – is needed to back up each workstation that has important data on it. It may be possible to back up data from multiple workstations on the same USB drive but that is impractical.

 

Regarding cost, a typical organization having a server attached to terminals plus workstations, the latter all with the same system image on them, would require three high-capacity USB drives for the server backups, one USB drive for the workstation system backup and probably several flash drives, one for each desktop workstation. If there are half a dozen desktop workstations, the total cost would probably be somewhere in the $700-$900 range. If there is more than 32 GB of data on some of the workstations, USB drives will be required instead of flash drives, increasing the cost about $200.

 

Backup devices and good intentions are worthless unless there is a backup plan that is rigidly adhered to. How often you backup data depends on how important the data is and how frequently it changes or is added to. Typically, a server should be backed up daily. The daily backup is taken off-site to a secure location. In addition, there should be a system backup for the server and each unique desktop workstation image that is kept off-site and updated as needed, which will be whenever the operating system or application programs are modified.

 

Rather than a full data backup, one can optionally do an incremental backup, backing up only data that has changed or been added since the most recent full backup; however, this approach requires two storage devices, one for a periodic full backup and one for the incremental backup.

 

The frequency of workstation data backups depends on how critical the date is and how often it changes. If the data is highly critical, like server data usually is, you may wish to have an off-site backup to guard against a disaster such as a tornado or fire. Also, you may wish to backup data every day.

 

Although Windows has an integrated backup accessory, we prefer Symantec Ghost, which costs about $24 per PC.

 

The cost of backup devices plus the time it takes to do the backups is an expense, but not nearly as expensive as losing either your data or your ability to operate due to the loss of critical system or application files.

 

If the initial setup of backups and a backup plan are either too difficult or too time-consuming for you, that is one of the services Zadada offers. In fact, as stated at the outset of this blog entry, we insist on a client having good backups before we touch anything else.

 

See http://en.wikipedia.org/wiki/Backup for more information about backups and storage devices.

 

Upgrade to Windows 7

We upgraded one of our offices from Windows Vista Ultimate 32-bit © to Windows 7 Professional 32-bit ©. (One cannot upgrade directly from a 32-bit operating to a 64-bit operating system.)  This upgrade required backing up and reloading all data and also reinstalling all software, because the installation essentially wipes clean the hard drive.

 

Several issues arose, including the need to update peripheral device drivers and a required update to QuickBooks 2010 from an earlier version. We were unable to get the Windows 7 32-bit driver for one nearly new scanner to install, nor could the manufacturer's technical support team, despite several attempts. The temporary solution was to connect the scanner to an older laptop running Windows XP.

 

Upgrading to Windows 7 will not necessarily be seamless; however, regardless of what version of Windows you have installed now, we are well-informed about upgrading to any version (technically possible) of Windows 7 and also updating application software and device drivers.

© 2011-2012 C. Harstad Associates, Inc. All Rights Reserved

Linkedin

Contact | FAQs | Site Map | About

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Hit Counter