Addsum web site and general info

Postings here will focus mainly on Advanced Accounting software updates, tips, and related topics. They will also include general comments relating to troubleshooting PC/Windows/network problems and may also include reference to our other software products and projects including any of our various utilities, or to the TAS Premier programming language. We considered setting up separate blogs for different topics so that users/others could subscribe to topics mostly aligned with their interests, but decided that it would be better to keep things simple since some topics cross over into others. We would nonetheless welcome your feedback/input in this regard. Our web site URL is www.addsuminc.com. Call us at 800-648-6258 or 801-277-9240. We also maintain www.advancedaccounting.us so that older Business Tools users in particular have a greater chance to find us. White list noreply@follow.it to ensure you receive notifications once you subscribe.

Wednesday, December 3, 2014

Avast's Browser Cleanup/Firefox nightmare bug fixed

Avast has finally fixed its disastrous Browser Cleanup/Firefox add-ons bug.

When your anti-virus software works against you in a manner almost as destructive as the worst virus, it is a reminder of how dangerous software updates can sometimes be, and also how  new and inadequately tested software features can lead to disaster.

As early as June of 2014 avast! users were reporting a serious problem with the Browser Cleanup (BCU) option and Firefox.   Avast was aware of the reports but could not find a problem with their code.  The reports however kept coming in.   Unfortunately, we were one of the victims in September of 2014 after many other reports had been filed.  And more came after.

Not until November 17, 2014 did Avast finally find a solution and fix the problem which was not announced in the relevant forum until November 24 in which the Avast representative posted:

"Reason was a bug in the BCU which slipped through QA because it happened in some rare conditions only.  After the first reports from our customer it took us quite some time to reproduce and fix the problem."

As a software developer, we certainly understand the problem of needing to reproduce an issue in order to be able to fix it.  In this case however it wasn't a single customer, but many.   And the consequences were dire:  the Browser Cleanup literally went completely rogue when told to cleanup Firefox add-ons within at least a fair number of PC systems (and was not limited to a particular operating system) under some set of conditions, and due to the bug would proceed to delete thousands of local files seemingly indiscriminately in a fashion that can only be likened to a destructive virus.   In our case it reported two never used add-ons as having bad reputations; we did not need them, but made the mistake of telling Browser Cleanup to remove them.  A problem like this was so severe that Avast should have escalated the reports to the highest priority and remoted into systems that were having the issue in order to duplicate and resolve it.

In our case it removed a Delphi 7 program files subdirectory and subfolders completely involving some 5,877 files. It removed Winamp.  It removed Firefox.  It somehow removed avast! itself with 19 small BIN files marked as read only remaining.  It removed CrashPlan.  It removed OpenOffice.  It removed Malwarebytes.  And more.  And these details were reported to Avast.  And it would have removed even more had we not realized something was wrong and shut down the PC.  ("Removed" is intended here to mean deleted.  Folder names remained but files within those folders were all or mostly gone.)  Fortunately the Windows system folders were not impacted.

We were able to recover the missing files but only after hours of work.   The PC thankfully was soon again operational after a day or so of high stress, but there was still no response to our forum posting and no resolution for users.  And others have not been as lucky.

For Avast to blame their QA (Quality Assurance) testers for missing this problem is patently unfair.  Any code that could have had ANY chance of being as malicious as this was should have been foreseen by any experienced programmer.   Whenever you are DELETING local files from a user's system and are using some sort of recursive logic as must have been the case here in view of how the BCU bug was behaving (when the problem was triggered, the removal tool was clearly jumping around the local subdirectory structure of the end user's PC and literally ravaging their local file system) and this should have been caught by the programming staff in the first place.  The blame here must be placed at the source:  the programmer(s).

Programmers have the responsibility to substantially test their programs and not expect their QA departments (or end users) to catch them to the greatest extent possible.  They should also safeguard potentially dangerous code that might otherwise not be capable of easily testing, and/or that a tester might not be aware of.

One commenter indicated that since the users involved were using the "free" version that their expectations should be accordingly low, and tried to shift the blame to users utilizing the free version.  Wrong.  If the software missed reporting a potential virus (none of the anti-virus packages ever detect everything) that might be one thing.   But users do have a right to expect that even free software from a supposedly trusted source will not devastate their system, and clearly Avast is very much culpable in this regard.   Their software, free or not, was never authorized by the end user to delete local files beyond the Firefox add-ons.  Their free software is offering to protect, not harm, an end user system.  Viruses are also free but most users do not intentionally install them.  So here the very software that is being promoted as helping you to protect your PC instead becomes your worst nightmare.   And their BCU likely was behaving the same way with respect to Firefox (under some undisclosed conditions), whether paid for or used as part of the free version.   So this issue of free vs. not free is moot.

And to reiterate:  our PC was never infected with a virus or with malware of any kind other than the avast! Browser Cleanup software, a newer option we don't ever plan to use again and which was enabled by default, and is was one a suite of new things added to the product that is hard to categorize as something desirable or needed.  Its assessment of things that have a "bad reputation" is also certainly questionable.

Some screen shots below show some of the sequence of the initial reports of the problem and the ultimate posting indicating that in fact the problem had been tracked down and resolved by Avast are contained below.

End user beware.


Clips from the avast! user forum relating to this topic:











Sunday, November 30, 2014

Do you want to run this file?

Starting with XP Pro SP2, program and other files downloaded from the web from many of the more commonly used web browsers are individually flagged and subsequently carry a security warning when an attempt is made to open or run (execute) them.  While initially helpful, the warning may persist when flagged executables or equivalent are opened or run from a networked drive, which most users find to be annoying and unnecessary.   In an era where users are increasingly being bombarded by warnings and messages of all kinds, excessive warnings that users continually have to routinely bypass can then lead to users ignoring error messages of true importance.

When an executable file associated with the application is run from a local drive, users have the option to trust that specific application or even all content from a given publisher, and regardless of whether the UAC (User Account Control, applying to Vista and above) is enabled or not.

Open File- Security Warning example, executable downloaded via Internet Explorer 8, Win 7, run from local drive:




But the same is not true when running the same or a similar executable from across an internal network (i.e. the local intranet) .  The “Do you want to run this program?” message occurs in that case without end and without an option to not always ask this question before opening the given file which is available when running from a local drive.

Open File- Security Warning example, same executable downloaded via Internet Explorer 8, Win 7, run from network drive (note the lack of an option to not always "ask" before opening the file):




Do you really want Windows to be constantly asking you if you really, truly want to run a program that you launch every day across a network drive?

Most users do not need nor want the aggravation and annoyance of this yet additional warning message, particularly if they are running the program from an established desktop shortcut and even if the program is located on a non-local drive, since that is after all one of the purposes of a network drive.

Fortunately there are some options available to eliminate this security warning that carry little to no security threat.  (Always discuss the ramifications of changes to your system security with your IT support.)

While this issue can be dealt with by setting group policies (particularly on larger systems and/or those that have in-house IT support) or by trying to manually delete the zone identifiers that may be associated with the file, the approach we stumbled upon quite a few years ago and which is outlined below is typically the simplest and most effective.

From the Control Panel, proceed to Internet Options then click on the Security tab.   With XP Pro you will find Internet Options as a top level option.  With Windows 7 and Windows 8, first select Network and Internet and then  Internet Options.   (Note: you can also access Internet Options from within Internet Explorer itself.  Launch IE, click on Tools - or if you can't see the menu try ALT-F then Tools or ALT-T to go directly to Tools - then choose Internet Options at the end of the menu or just press O and finally click on the Security tab.  Yet another method is to run inetcpl.cpl.)

Click on the Security tab.   Then select/click on Local intranet.   Then click on the Sites button.  When the Local intranet screen appears, click on the Advanced button.




Under “Add this website to the zone:”  type in the drive mapped letter/path or UNC path to the network drive.  It can include the actual executable file; however, that is not important and the executable name will be stripped off.   Despite the reference to a “website” on this screen (the wording here referring to these local intranet paths solely as "websites" is wrong and confusing), what will be entered here is a locally shared network path on another networked PC.

We used to always uncheck the "Automatically detect intranet network" option and then also uncheck "Include all network paths" option; however, adding a "site" to the zone is supposed to take precedence over the general Local intranet settings. Sometimes we have found that in order for the security warning to go away we have nonetheless still had to uncheck the "Include all network paths" option.  So if your warning message persists after following the above, try making those additional changes.

Click on Add and in the "Websites" list box  you will see a reference such as the one above or with the server name, e.g. file://computername (where computername is the name of your in-house server or other PC with a shared drive that you want to add to this zone).   Click on Close and then OK on each of the prior forms/screens.

Repeat on each PC in your network.

You do not have to restart or re-boot for these settings to take place.  Exit out of Internet Options (or out of Internet Explorer if the changes are made there) and then try your desktop icon to see if the warning message is gone.

If the same executable file is replaced in the future by a downloaded file via a browser that attaches a zone identifier or is replaced by a file from somewhere else on your system that has an attached identifier, then even with the security options above in place and regardless of how the UAC has been set, the user will see a warning like the one below.

Open File- Security Warning example, same exact executable re-copied from a local drive where the "Always ask" had not been unchecked, or which had been re-downloaded via IE, with now local intranet settings referencing the PC mapped as drive S: in place:





This warning then is identical to an executable first run on a user's local drive and notice that now
the user will similarly be able to choose to open it in the future without the warning (but still with the ability to at least verify that is it from the same publisher but not much more).  This does not guarantee that the file is completely safe but that job is best left to other procedures and protocols.

A better solution than the above would be to allow end users to "trust" individual files including executables regardless of their location (and especially if the executable has been digitally signed and therefore involves a known/verified publisher) and then using file verification (such as a file hash which would need to take into account alternate data streams associated with the file) technology to detect changes in a file that could then trigger a new one-time warning (with more information about the nature of the changes that might be helpful) to appear should a change occur that a user with no additional privileges would be allowed to then stop from continuing to occur as in the last example above.   This could be set as a property of the icon by a user with administrative privileges, i.e. "trust this file."   This is also not a perfect solution but an approach of this nature in combination with other security software and related protocols and procedures would provide a better balance between security and ease of use.

Some additional technical details:  Zone identifiers are alternate data streams (ADS) which came into existence with Windows NT (first introduced in 1993) and are sometimes referred to as NTFS ("new technology file system") streams.  These allow the same exact file to be associated with more than a single data stream and only occur on NTFS drives. These additional data streams however are not readily viewable without special tools such as Microsoft's Streams (a Sysinternals utility) or now with the Windows PowerShell.  Unfortunately malware can also take advantage of these alternate data streams, but ADS features are built into systems that use NTFS and cannot be disabled.

Internet Zones discussed in the context of Internet Explorer 11:
http://technet.microsoft.com/en-us/library/dd346863.aspx

Security Zones:
http://technet.microsoft.com/en-us/library/dd361896.aspx

Note these definitions/discussion from the above:

Local intranet zone:  "The Local intranet zone includes all sites inside an organization's firewall (for computers connected to a local network). "

Include all network paths option:  "Include all network paths (UNCs). Network paths (for example, \\servername\sharename\file.txt) are typically used for local network content that should be included in the Local intranet zone. If some of your network paths should not be in the Local intranet zone, clear this check box and then use other means to designate the Local intranet zone membership. In certain Common Internet File System (CIFS) configurations, for example, it is possible for a network path to reference Internet content. "

Firefox browser: Firefox had an option in its about:config settings to remove zone information when files were downloaded in a number of older releases.  The setting which could be set to false was:

browser.download.saveZoneInformation 

However that has since been removed in the latest Firefox releases and can no longer be set.  Since January of 2014, Firefox only marks executable file types with a zone identifier indicating Internet origin.

Scanners: A free scanner that can detect otherwise invisible alternate data streams (you can also choose whether to show or ignore "safe" ADS content and you can also remove either kind including the safe type which triggers the "Do you want to run file?" message):

http://www.pointstone.com/products/ADS-Scanner/

There are other free scanners such as Microsoft's Streams:

http://technet.microsoft.com/en-us/sysinternals/bb897440






Wednesday, October 15, 2014

CryptoLocker ransomware: educate your e-mail users before it is too late

Ransomware is not new but in the past year has entered into an entirely new era with the advent of the CryptoLocker virus. Just in the last two days in different parts of the country two of our accounting software users have encountered this virus and it has created havoc. Neither paid any ransom but rather were able to thwart the virus by taking fast action; nonetheless it caused an interruption in business of these users along with technical support expenses, and considerable angst.

Once a system is infected, the virus spreads very quickly and easily jumps around and onto shared network drives. On one system it jumped to a server drive from a client PC that only had basic, non-administrative user rights and within less than two hours had copied its ransom notice files into every folder on that drive. So any PC (or other device) connected to your network server could spread it.

Additional morphs of CryptoLocker have also recently appeared.

Your anti-virus program may not be able to detect CryptoLocker or its morphs. Therefore, it is critical to focus on the education of your end users NOT to click on links or open e-mail attachments from unknown, untrusted or suspicious sources that may be disguised in any number of ways.

It is not clear whether the virus is able to encrypt files that are in active use; but it does not seem to discriminate in terms of what files it goes after. One user's first notification was when a simple JPEG file could not be loaded and was essentially corrupted by the virus.

General background information about the CryptoLocker trojan can be found on Wikipedia.

A Virus Bulletin Ltd. blog mentions a recent tool that may be able to provide the decryption phrase in some circumstances as a result of a joint effort between FireEye and Fox-IT (the PDF maker). See:


Some further helpful technical details:


As is discussed in greater detail in a related blog, lack of end user awareness of potential serious infections as a result of careless e-mail use is a significant part of the problem. And hackers know this.

Recovery requires an off-line backup that was made prior to the infection. So in addition to strongly reminding end users about e-mail and related dangers, revisiting your backup strategies is also in order.




Wednesday, July 16, 2014

Resolving “yourexecutable.exe” has stopped working: sometimes bigger is better

Early in the life cycle of the development of TAS Professional and Advanced Accounting 7.x, it seemed to us that it would be a good idea to compress our executable files primarily to reduce the download time of installation files, and subsequent updates involving those EXE's.   At the time, producing lean and mean EXE files also seemed virtuous and in the best interest of our users.

An unfortunate consequence of packing or compressing executable files (which is something very different than packing a data file via a rebuild or reindex and also in this context very different from other kinds of file compression), however, is that they can lead to being falsely identified by anti-virus programs as containing malware. And, when attempting to execute programs under these circumstances, the executable can be completely stopped dead in its tracks.


The process of decompressing an executable actually leads to it taking more computer memory when run, causes it to also initially run more slowly, and can create other performance bottlenecks. Counter-intuitively, the larger-sized files can therefore actually run faster (modern executable files are typically not completely read and placed into memory all at once, so even very large executable sizes usually lead to little to no loss in execution time even across a network). In our testing after removing compression, we found that they in fact did not run slower, and this solved the problem of potential false positives with respect to some third party anti-virus and related software.

So, in 2012, we abandoned the practice of compressing executable files.

If you receive a message like this and you in fact trust the source (and also inspect the properties of the underlying file,  and also conduct some on-line research), you could temporarily disable your anti-virus software to see if the “has stopped working” message is overcome (or, better, add the executable as an exclusion; your anti-virus software should - and in fact must - have the ability to add exceptions including telling it to not scan data files in order to improve performance and false positives that could lead to data loss, etc.).

In the case of our executable files, the best solution is to simply contact us for a replacement. The easiest way to accomplish this is to simply update to a more current version that contains the uncompressed executable.

Despite our wanting to shrink our executable files and provide smaller files to end users to decrease download times, in this case it turned out that bigger is better.

Friday, June 20, 2014

Pervasive/Btrieve status (error) code 20

Error code 20 is often experienced by end users. The cause depends in part on the Btrieve/Pervasive environment in which the software is running.

Btrieve 6.15 systems

In Btrieve 6.15 installations (which includes XP Pro, Windows 7, Windows 8 and corresponding server versions), a file open error such as one of the following may be encountered when first running a program.   Examples:






First ensure that the program can be run from the server/gateway PC (i.e. the PC on which the software is installed) when logged in as administrator.

If you do not receive this error code when logging in from the workstation as an administrator but you do get it when logged in from a different profile (but can “force” the program to work by manually first running Btrieve 6.15's microkernel engine w32mkde.exe), chances are that the user is a part of a standard or limited group on their local PC. The user will need to be placed into a power user/administrative group* on the local workstation to resolve.  Even if the user has full rights to the shared folder on the server, due to the legacy 32-bit nature of Btrieve 6.15 they must also have similar rights on their local PC.  One of the reasons for this is because Btrieve 6.15 places its registry entries under HKEY_LOCAL_MACHINE\Software.

*Power user or above was necessary with Win 2000 and XP Pro.  For Win 7 and above, users may have to be given local administrator privileges in addition to setting the icon properties to "run as administrator"  (see below) unless two default registry settings are changed:






In addition, absent being given administrator rights, on 32-bit PC's, the My Computer\HKEY_LOCAL_MACHINE\Software\Btrieve Technologies key should be made accessible to all users.  On 64-bit PC's, the key is instead located at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Btrieve Technologies.


Wow6432Node on a Windows 7 64-bit PC


Right click on the Btrieve Technologies branch, choose "Permissions" and set  Users/Everyone to have full control.

With these settings changed to permitted local application data paths and appropriate rights granted to the Btrieve Technologies registry key, then even with Windows 7,8 and 10, users can be placed in a power user group rather than administrative group and still invoke the engine as was possible with XP Pro.  The Addsum Btrieve 6.15 Setup program allows an end user to establish these settings in a more flexible way.

It should be kept in mind that Btrieve 6.15 was never tested on XP much less on Win 7 nor Win 8, etc.  so it is in one sense amazing that it continues to work at all.   If this however poses an unacceptable security risk to put the user in a power user group with respect to local PC rights, then the alternative is to update to an appropriate version of the newer Pervasive engines, and then local user privileges can be restricted as desired.

In establishing the appropriate Btrieve 6.15 settings in the first place on each PC where the software will run, on Windows 7 and 8 and equivalent systems it is essential that the workstation configuration programs including the BTRSETUP.EXE are “run as administrator.” On these systems it may also be necessary to change the icon that launches the software be set to “run as administrator” when launching software that uses the Btrieve 6.15 engine (see below) unless some of the default microkernel registry entries have been changed as discussed above (and which can be managed with the Addsum Btrieve 6.15 Setup utility.





If the error 20 instead occurs during software operation and not in the context of opening a file, another reason for this error message in 6.15 installations relates to inadequate user "delete" rights such that the user is unable to delete 6.15 LCK files; if the LCK files can be moved and the error 20 goes away, this indicates a user rights issue.

In rare situations, users have received error 65516 which also appears to be linked to a certain Btrieve DLL's no longer being present (for example if the 6.15 wbtrv32.dll installed in the application folder in the case of Btrieve 6.15 installations was inadvertently deleted or removed by some process or is prevented from being loaded).

Terminal services (RDP/Remote services) environments and Btrieve 6.15

Status code 20's have been widely reported when attempting to remotely access Btrieve 6.15 data via RDP.   Typically the first user can be made to work, as long as the application is run with elevated administrator privileges to resolve initial status code 20 issues, but the second user will then commonly receive a status code 20 until the first user exits the application (and after the w32mkde.exe process unloads itself from memory a short time later).  While tweaks to the Terminal Services registry and/or to the Btrieve 6.15 registry keys have been reported to allow more than single user access, a newer database engine is needed in a remote access situation involving multiple users not only to avoid giving users full administrative access but also to provide faster and more robust file handling, as well as to better interface with modern backup approaches, and since newer "Btrieve" engines have been designed with RDP in mind.  Therefore, the best approach is to upgrade the "Btrieve" component to a newer version.

Pervasive systems

When running Pervasive database engine environments, the error 20 can be returned if the Pervasive workgroup or other engine is running and the Btrieve 6.15 components exist in the application folder where the executable software (e.g. tp7runtime.exe) is being invoked (or they exist in the Windows path, which we never install to, or some other path available to the user).

The Pervasive engine and the Btrieve 6.15 engine cannot be active at the same time. They can exist or available on the same system, but both engines cannot be run concurrently from the same desktop.

To resolve, either all PC's should first be running the same Pervasive engine and the REMOVE615.EXE (provided by us) should be run to remove the Btrieve 6.15 components from the application path if the intent is to use the engine with the Advanced Accounting or other TAS-based software. If the Pervasive was installed as part of some other software, then a solution would include uninstalling the Pervasive workgroup engine if is not going to continue to be used (if related to a demo install for example) or to stop the Pervasive engine  (how that is accomplished depends on the Pervasive version; newer versions usually run as a service) before trying to run the application using Btrieve 6.15.

Incorrect or mismatched DLL's may also be the case of an error 20 in Pervasive environments.



Monday, April 21, 2014

New Wisconsin state withholding tax rates as of April 1, 2014


The state of Wisconsin implemented new state income tax withholding tax tables and rates to be implemented on/after April 1, 2014.

As is often the case, a change in a state's withholding tax rates often does not require an Advanced Accounting software update due to the ability of the end user to maintain standardized tables, particularly when a state follows an approach similar to that of the Internal Revenue Service's annualized rates and related formula structure.

Wisconsin is somewhat unique in providing two alternative annualized methods, referred to as Method A and Method B. The rates computed by these methods produce similar, but not exactly the same, withholding amounts. These calculations in turn will not exactly match, but will be close, to amounts listed in withholding tables for manual look-up.

Since at least 1988, Advanced Accounting has used Wisconsin's Method B approach since it most closely approximates the typical annualized schedule logic. And, as is also typical, there is a separate rate withholding schedule for employees that have a withholding status of “Single” versus “Married.”

The only piece of hard coded programming logic in Wisconsin’s formula involves a $22 amount per state exemption claimed that is deducted from the amounts computed by the standardized annualized tables (after which the calculated amount based on previously annualized wages is then de-annualized based on the number of days in the current pay period). We could also make that an end user managed value, but this $22 amount has been the same since at least 2004.

We also could have just as easily (and in fact initially did) use Method A to meet the April 1, 2014 changes for Wisconsin, but it would have involved using more internally hard coded logic compared to Method B, and would therefore make the system less flexible for future changes. So we have reverted those changes to again rely on a Method B withholding schedule structure.

Advanced Accounting users that have employees that are subject to Wisconsin state income tax withholding therefore only need to update the WIS (Wisconsin Single) and WIM (Wisconsin Married) tax codes in payroll (PR) module option K (Maintain Tax Tables) as outlined on page 45 of the Wisconsin Withholding Tax Guide Effective for Withholding Periods Beginning On or After April 1, 2014, Publication W-166 (1/14). 

For end user convenience, a link to a PDF that shows what these should look like from within the Advanced Accounting software is contained below.









Tuesday, April 8, 2014

XP Users: The sky is not falling

With Microsoft retiring its official support for XP today, many users are in panic mode.  Users of XP however should not despair nor does immediate upgrade action need to be necessarily taken.   But, users should educate themselves on what this means going forward.

Some 20% to 30% of the worldwide Windows PC user base still uses some flavor of XP, typically XP Pro. It has been a good run, and XP Pro has been a reliable, relatively annoying-free operating system (and remains our favorite).

Behind the scenes, Microsoft will be continuing to update XP Pro for some customers privately, particularly in the financial sector.  If a critical update becomes obvious, it would be surprising if that is not released in some fashion to the general public, although one's strategy in going forward should not bank on that happening.

Upgrading a given PC from XP Pro to Windows 7 Pro typically isn't really feasible (and even less for a Windows 8 Pro transition).   It isn't just a matter of installing some update to an existing PC (or laptop) after which all of your currently installed programs will simply function in a way that you just go forward and never look back.

While we have no reservations about using Windows 7 Pro or Windows 8 Pro and/or corresponding server versions with our software generally, there can be various kinds of other compatibility issues, and since it effectively requires a full replacement of an existing PC (both in terms of likely hardware upgrades required, plus the PC running XP is likely old and not worth spending the time and money to refurbish it) , the cost of migrating software to a new PC is very high unless the end user runs very few software applications.   For some users, you could easily budget the true cost of a new PC to include some four to six hours of time per PC (minimum) PLUS the actual cost of the hardware, to make a migration.   For some PC /server migrations, it could take quite literally days to effect a full migration and that PC/server still would not contain everything that that the prior one did.  And even then, some third party application may not work and/or important information overlooked and lost.

Depending on end user and other software requirements, compliance with HIPAA or other industry specific standards, whether the software used most is on-premises or cloud-based, and depending on the compatibility of critical software used and equipment age, it may be best to simply plan on replacing PC's in connection with current retirement schedules, but not otherwise act right now simply because Microsoft has stopped providing security updates and not succumb to some of the scare tactics that are being circulated.

Exploits relating to the use of the Internet Explorer (IE) web browser have been known for a very long time and are not new.  While there are some government or financial web sites where you still might have to use IE to gain all functionality, it would be best to now restrict the use of IE (and even then, only if you have to use it) on updated Win 7/Win 8 PC's to the extent available (in a mixed network environment for example) and completely avoid using IE on your XP Pro PC's.  (Do not however attempt in any event to ever remove or uninstall IE from a PC running Windows!).

Automatic Windows updates have also often caused as many problems as they have purported to cure.  We are not suggesting never updating, but we have seen numerous problems with automatic updates.   This is something then that XP Pro users will no longer have to worry about!   We frankly do NOT recommend setting your computer system to automatically update for operating system related changes and updates; instead apply the updates when you can monitor their progress, and watch them being installed.   This will avoid many bad Mondays.

It will remain important to be vigilant about all PC use and to continue to update your browser and anti-virus software.   Opera, Mozilla Firefox and Google Chrome (at least until 2015) have all indicated that they will continue to support XP.   So, if you have not already done so, we would strongly suggest installing both the latest versions of Chrome and Firefox (because sometimes Chrome doesn't get the job done) on your PC's or laptops running XP Pro and keep them updated.  The same of course is true with anti-virus and malware software since most anti-virus software publishers (including Avast which we like) have indicated that they will continue to support XP Pro (in the case of Avast, for at least the next three years).

If you already have installations of Firefox or Chrome on your battle-proven XP Pro machine, make sure they are the latest versions (some older versions of Firefox for example do not support the latest XP Pro through SP3). 

Ensure also that you have anti-virus software in place that is being updated (but which is set with appropriate exclusions; it should not be scanning database files for example in real-time).   If you are using Microsoft Security Essentials, Microsoft says that they will continue to provide updates for a “limited time” after XP's official retirement to allow for a transition, so plan on disabling that and installing some other anti-virus program on impacted PC's in the very near future.

Continue to educate end users as to best practices and safe web surfing.  Continue to consider issues that relate to physical access as well as your firewall, and restricting what can and cannot be done on a given PC.   Continue to monitor the effectiveness of your data back-up strategies and ensure that they are actually made, and that you know how to restore files should that become necessary.

An overlooked security tip:  when your PC or laptop isn't being used for an extended period of time and all other things being equal, turn it off.  While there are certainly exceptions, most PC's do NOT need to be left on overnight.  Nor should they be unless needed for remote access or on-line back-up (they should even in that event be scheduled to shut off at some point during the night, other than perhaps the "server" which still needs to be periodically powered down).  And if you are going to be gone from the office for several hours during the day, why not turn your desktop PC off as well?

When upgrading your PC's, if you use Microsoft Terminal Services, consider replacing your in-house PC's not with yet more PC's, but rather with Winterms.  We cannot understand why that approach has never gained traction; it isn't appropriate necessarily for every user on your network, but would be a very effective approach for many in-house users and substantially reduce not only current and future costs but also increase security.   So the only upgrade path for your XP Pro device is not limited to moving to Win 7 or Win 8. 

The sky is not falling and many users will continue to make good use of their PC's running XP Pro for at least the next several years.    Early last year we assisted a user running a legacy version of our software on a Windows 98 PC.  Somehow they had survived running in that fashion since 1997.  The technology cycle continues to shorten and so we are not suggesting that users should continue using XP Pro longer than perhaps another year or two; but we will also not be surprised to encounter users still successfully and happily still running it many years from now.

Postscript:  A Microsoft security blog relating to the above that you should read if you have XP PC's and plan to stay on XP for a while is here.   Even though we don't agree with everything that is stated there, this may help you to arrive at own conclusions.  It is important to note that sometimes getting the latest and greatest updates, especially when they are relatively new, is not hardly any guarantee of better protection.  An example is the so-called Heartbleed bug.  It was only the newer released OpenSSL DLL's that had the issue.  DLL's released in 2011 for example did not have the problem. Again, we are not suggesting never updating nor keeping current up to a point, but that was in essence a two-year old bug that only just recently came to light and it was the newer updates that caused the problem, and it simply speaks to the fact that the overall security of your system involves far greater issues often than just whether or not you can obtain automatic updates.  Sometimes being on the bleeding edge isn't so great and exposes you to greater risk.  Yet, this is rarely discussed or written about.

A pertinent April 21, 2014 avast! blog:  So you’re sticking to Windows XP? Here’s how to protect yourself: It’s the end of Microsoft support, not the end of the world.