ATX™ 2013 System Requirements: Frequently-Asked Questions
Operating Systems
Networking
RavenDB
Hard Disk Space
DVD vs. CD
Internet Access
Firewalls
Handling Returns from Prior Years
Printers
Certified Software Technicians
Appendix A: Reasons for Changing the Network Structure in ATX™ 2013
ATX™ 2013 – Not Supported / Not Recommended
ATX 2013 System Requirements (chart only)
2
Operating Systems
CCH Small Firm Services products are designed to run on and are tested only on the Windows® operating
systems listed in the System Requirements chart. ATX will not run on non-Windows® systems (such as
Mac, Linux, or UNIX).
If Microsoft discontinues support of Windows® XP before the end of the 2013 tax season, what
does that mean?
Although Microsoft will discontinue support of Windows® XP in April 2014, we will support ATX on the
Windows® XP platform through the end of the 2013 tax season, which is October 15, 2014. To
understand the implications of using an unsupported operating system, read “The Risk of Running
Windows XP After Support Ends.”
NOTE: You must upgrade your Windows® XP workstations after Tax Year 2013. We encourage
you to do this as soon as possible.
Is Windows® Vista supported? It’s not listed in the System Requirements.
Vista’s documented issues–particularly in the area of memory management—prevent us from
recommending its use as an operating system for ATX. Although we don’t prevent installation on Vista
machines, the systems specified in the requirements chart will give ATX users better performance and
potentially fewer OS problems.
What server operating systems are supported?
We will support ATX products on the following Windows® server operating systems:
Windows® Server 2012, also known as Windows® Server 8
Windows® Small Business Server 2011
Do the new ATX 2013 system requirements apply to other ATX products?
When used in conjunction with ATX 2013, other ATX products (such as Payroll Compliance Reporting,
W-2/1099, PaperlessPLUS™, Client Accounting Suite and Fixed Asset Manager) will run smoothly if you
follow the new ATX 2013 system requirements.
Networking
What are the changes to networking?
ATX 2012 used a shared file network setup that did not deliver the performance you needed. For that
reason, starting with tax year 2013 software, ATX will use a traditional client/server configuration.
Client/server networks use a dedicated server from which individual workstations receive data. A
dedicated server offers increased reliability and faster network access with a greater level of security.
Because of this change, we have added separate specifications for the server machine to ATX 2013
system requirements. Meeting or exceeding the server requirements is essential for superior system
performance. To make installation easier, we’ve added more step-by-step decision making to the
program installer. It will guide you through setting up your server machine, and will also guide you
through installation on each workstation without the need to run netsetup.
3
Several things are changing for network users:
Separate system requirements for server machine will support a stronger and faster network.
The server cannot be a Windows® XP machine.
You’ll need to install ATX first on your server.
Once the server installation is complete, you can then install ATX on each workstation (NOTE:
ATX will not be downloaded via netsetup.exe as in prior years).
Each workstation will automatically “discover” the server machine as the server for their
network (or if the server can’t be automatically discovered, the workstation can be manually
configured to point to the server.)
NOTE: We’ve redesigned the product installer to walk you through this step-by-step.
Why didn’t ATX move to a client/server network during the 2012 re-design?
We knew that some ATX customers using network setups had only a shared file system and were not
prepared to make the move to a client/server environment for data sharing. However, after the
challenges of Tax Year 2012, we recognize that continued support of shared file networking will impede
our ability to provide the speed, reliability and consistency our customers expect from ATX. By moving
to the client/server model, we can increase performance, stability and data integrity immediately while
affording us the capacity for continued improvements in the future.
4
What are the differences between a shared file environment and a client/server environment?
Shared File Network
Client/Server Network
Definition Files are copied from one computer to another using shared directory
All files exist in shared directory (includes application files as well as all tax prep data)
Single computer as server, acting as coordinator for workstations (load/save data, give database access, perform backups, etc.)
Setup Each workstation granted specific access to shared directory (conflicts can exist if domains are involved)
Setup is easier because each computer (either workstation or server) has a clearly-defined purpose.
Performance Application startup slow due to local copy of application files
Complex monitoring & file locking activities required for workstation (client) syncing
Workstations must scan shared directory after being offline to get data back in sync
Application resides on workstation (client) no need to copy files
Clients don’t need to scan directory; the server manages data
Stability Local copy of application on each workstation
Removal of local copy and re-installation with every update presents some instability
Installation on workstation (no local copy)
All clients get same update (from server)
No update incompatibility (causing program instability)
Ability to rollback updates on all workstations if necessary
Data Integrity File-based locking
Workstations must monitor shared directory for data changes
Multiple workstations can potentially write to files simultaneously
Data written and read by server (server write)
Far fewer data conflicts amongst clients
Files written once by server
New write is new file w/ version number
Files removed only if “write” is successful
One write at a time reduces opportunity for conflict
Table 1 - Shared File vs. Client/Server Network
5
I’ve had a peer-to-peer setup before. Can’t I do that again this year?
No. Until now, ATX used a Microsoft® Access relational database and a shared file network structure (not peer-
to-peer networking). The potential for complications during setup coupled with the inherent limitations in
performance and stability were key factors in the decision to move to the traditional client/server
model.
If you intend to share system data between computers, you must designate one computer as the server.
In order for your network to function properly, you must establish this client-server relationship. But
don’t be deterred…if your server machine meets the server requirements, the installation process will
walk you through the rest. We have changed the 2013 installation to make it easy for you to specify one
of your computers as the server and then to select the server when you install on the workstations.
I have all Windows® XP systems, but I need to share data. Do I have to buy a new computer for
the server?
Yes. Why? Because Windows® XP just cannot provide the performance needed from a server machine. A
benefit is that when XP is no longer supported in 2014 (by Microsoft in April 2014 or by CCH SFS at the
end of the 2013 season), you won’t have to transfer all your stored data onto a new system.
While you can use Windows XP for ATX 2013 workstations, we highly recommend that you upgrade
these machines this year to avoid slow performance. Bottom line: All machines must be upgraded by the
2014 tax season.
Can I host data on a networked external drive?
Yes. However, you must designate a server to write data to that external drive.
(NOTE: Performance in this type of setup is dependent upon many factors. Please consult your
network administrator or a qualified systems consultant to establish proper performance
expectations.)
RavenDB
What is RavenDB?
The ATX 2012 re-design included implementation of a new transactional database, RavenDB. This same
database is used by a variety of companies, including MSNBC.com and several international financial and
banking corporations—companies who insist upon solid data technology to manage enormous
databases of fast-moving, highly-sensitive information. RavenDB uses as its underlying data store
technology the ESENT database which is implemented by Microsoft and shipped as part of the
Windows® operating system (OS). This data store technology, also known as extensible storage engine
(ESE) or JET Blue, is the same data store technology that Microsoft uses in its Exchange Server and Active
Directory (AD) servers.
Was RavenDB part of the problem in 2012?
The data integrity issues experienced by network users in 2012 were specifically related to the shared
file system discussed earlier in this document and described in Appendix A: Reasons for Changing the
Network Structure in ATX 2013. We are confident that RavenDB played no role in these issues.
6
Hard Disk Space
Why is the recommended available hard drive disk space so high (10GB) and the minimum so
much lower (3GB)?
The recommended space allows for a full set of ATX forms, many more returns, and returns of higher
complexity. If you have a large business that serves more customers with more complex returns, you
can expect better performance if you are close to or have the recommended 10GB of hard disk space
available.
DVD versus CD
Why is ATX on a DVD rather than a CD?
We are distributing ATX 2013 on DVD rather than CD because the formset is quite large and there is
more room on a DVD than a CD. Also, the DVD format can be read faster.
Can a CD-ROM reader read the DVD?
No, a CD-ROM reader will not be able to read a DVD. To verify if your external drive will read a DVD, see
the “How Do I Find this Information” for an External Drive in the System Requirements chart.
Internet Access
I only have access to dial-up service. What’s the difference between dial-up and high-speed?
With dial-up (generally viewed as very slow internet access), any system tasks which require you to
transfer data from or download data to your system will be slow—in some cases, unbearably slow. ATX
program tasks that require the transfer of data via internet connection include receipt of form and
program updates, e-filing (as well as receiving acknowledgements) and Pay-Per-Return (PRS)
authorizations.
What kind of internet speed do I need for good system performance?
A good internet speed is 3 Mbps (Megabits per second) for either downloading or uploading.
How can I test my internet speed?
Use the following free internet speed test1. This will test your computer’s internet speed for downloads
and for uploads.
IMPORTANT: Network users should test internet speed on all workstations that run ATX.
Firewalls
Should I be concerned about firewalls interrupting my downloads?
It depends. Some firewalls may prevent formset downloads. Sometimes, making simple adjustments in
firewall settings will allow you to do what you need to in the product without jeopardizing system
security.
The following firewall articles in our Knowledgebase are a great place to educate yourself about firewalls
and how to change firewall settings in specific environments. Or, you can ask a certified software
technician.
1 Speedtest.net is a copyrighted product of Ookla®.
7
Handling Returns from Prior Years
I have several customers who have returns from previous tax years (2011 and 2010). What do I
do?
Returns from previous years should be opened in the tax software from the year they were created.
Prior year versions of ATX are available from the Download Center on the ATX Support Site.
Will prior year software run on same operating system I use for ATX 2013?
In general, if you are loading prior year ATX tax software, you should look at the system requirements
for that tax year. For example, if you have a brand new Windows® 8 operating system, software from
two or three years ago may not run on it.
Printers
Why is a laser printer required for W-2/1099 forms?
Laser output is required for W-2/1099 forms because of IRS Publication 1179, General Rules and
Specifications for Substitute Forms 1096, 1098, 1099, 5498, and Certain Other Information Returns which
specifies the optimal ink density for OCR (optical scanning) of certain forms.
Do you recommend a brand or type of printer?
Other than specifying that W-2 and 1099 printing must be done on a laser printer (which is an IRS
requirement), we do not recommend particular printers, or printer brands.
Certified Software Technicians
I’m unsure about upgrading my system. Where do I start?
If you’re unsure how to upgrade your system, contact a qualified computer technician in your area.
Appendix A:
Reasons for Changing the Network Structure in ATX™ 2013
We know that 2012 was a tough tax season for ATX customers—especially for those working in networked
environments. To resolve these issues, we’ve updated our system requirements and are making changes to the
ATX 2013 network structure. These changes are one way that we will address the performance, stability, and data
integrity issues you experienced last year in your network environments.
Introduction In 2012, ATX moved to a new platform for the following reasons:
To remove dependencies on unsupported technologies (such as Visual Basic 62)
To create a modern platform upon which all CCH products could run
To deliver new and enhanced functionality requested by customers
In terms of the network environment, however, we could not move forward in 2012. We knew that some ATX
customers using network setups had only a shared file system and were not prepared to make the move to a
client/server environment for data sharing. However, after the challenges of Tax Year 2012, we recognize that
continued support of shared file networking will impede our ability to provide the speed, reliability and
consistency our customers expect from ATX.
We will solve these problems this year by leaving the shared file network setup behind in favor of a traditional
client/server configuration. Client/server networks use a dedicated server from which individual workstations
receive data. A dedicated server offers increased reliability and faster network access with a greater level of
security. Furthermore, a move to the client/server model, by default, will increase performance, stability and data
integrity immediately while affording us the capacity for continued improvements in the future.
In this document, you’ll find the following information about ATX networks:
Background: ATX History of Shared-File Networking
o The Hidden Costs of Shared-File Networking
The Alternative: Client/Server Network
o The Benefits of a Client/Server Network
Summary
2 Microsoft’s support of Visual Basic 6 ended in March, 2008.
9
Background: ATX History of Shared-File Networking Before 2012, ATX used a Microsoft® Access relational database and a shared file network structure. Shared file
networks copy files from one computer to another using a shared directory located either on a computer that is
sharing that directory or on a shared disk that is attached to the network.
In an ATX shared file network:
All files exist in a single shared directory. This includes files that run the program (application files) as well as all the data files relating to tax preparation (returns, backup, etc.).
Whatever the workstation needs—application files or return related data is requested from the shared directory.
Data is copied to each workstation. A copy of the requested data is transferred to the workstation (client), along with changes to other data made by other workstations.
File-based locking. The shared file environment uses file-based locking system to prevent multiple users from making simultaneous changes to data.
Each workstation (client) that is running continuously monitors the shared directory for data and program changes. Changes are transferred to each workstation (client) and used as needed to update the client’s local data or user interface (UI).
The Hidden Costs of Shared-File Networking
Making data readily available on each client using this shared file approach comes at a price. Here are some of the
trade-offs that exist with a shared file network in ATX:
Setup. Initial setup of the shared directory must be done in such a way as to give each workstation (client) access
to the shared directory with the appropriate access rights. Setup is even more complicated if domains are involved
because shared directory rights and domain-level policies can often overlap or present access conflicts.
Performance. Shared file networking presents several issues with regard to performance:
Application startup. When the application is started, specific application files (binaries) must be copied
from the shared directory and then written (copied) to the workstation (client). This is the reason for the
“Loader” in ATX 2012 so that the application files on the network could be updated while the application
might be executing on one or more client workstations.
A complex series of monitoring and locking activities are required to keep data in sync on all
workstations (clients).
Shared directory scanning is required to load data into memory on the workstation (client). Scanning
must be done to ensure that any data on the client is updated while the client may have been
disconnected, as other workstations may have changed other data during this time period. The more
data on the network, the more directory scanning required.
Stability. Shared file networks have problems with application updates because application files are in the shared
directory location. Because each client runs a “local copy” of the application, updating the application necessitates
removal of this copy and re-installation of new application files on each client. In ATX 2012, this removal/re-
installation process caused some incomplete updates, which caused program instability.
10
Data Integrity. Shared file networks struggle with data synchronization problems between workstations (clients).
In spite of file–based locking and scanning of the shared directory for changes, there is still potential for multiple
workstations (clients) to write new data to the directory simultaneously (because every workstation is working off
of a copy). Although the system may display an error message before conflicting changes are committed to the
database, a better solution would prevent multi-user access entirely.3
The Alternative: Client/Server Network A client/server network solves many of the issues that can occur in a shared-file environment. In contrast to a
shared file network, a client/server network involves the following:
A single, designated computer acts as the server. This server acts as the central coordinator for the
workstations (clients) to load and save data, provide access to the database, perform backups, etc.
During installation, the server application is first loaded onto the server.
During installation, the application is loaded directly onto each subsequent workstation (instead of
copied from the shared directory via netsetup.exe).
Each workstation must be “pointed” to the server. (The software can automatically locate the server, but
this can also be configured manually.)
Updates are applied to each individual workstation as required.
All data remains on the server (this includes returns, preparers, companies, payers, billing, etc.)
Data can be backed up using third party backup software. This backup location is also used to store
backups of the database.
The Benefits of a Client/Server Network Setup.
Setup is easier. Each computer (either workstation or server) has a clearly-defined purpose. The installation process can explain which software is being installed on each computer, and why.
Performance.
Application files are no longer copied to the workstation. Eliminating this copy step saves time during startup.
No need to monitor changes in the shared directory. Because the data is managed by the server, direct notification to clients about changes they need to be aware of reduces network traffic substantially instead of having to watch a set of directories for changes.
3 In ATX 2012, conflicts in file locking were generally caused by one of two things: 1) issues in the ATX software; 2) defects in
particular operating system (OS) network stacks (see KB article 13842 “Returns Not Shown in Return/Bank/E-file Manager of XP
Workstations.”)
11
Data directory scanning to ensure that clients that have been offline for a period of time remain in sync is not required. Because the server is always running and is keeping the data current, when a client has been offline for a period of time there is no need to scan for changes because the server has kept things current.
Stability.
The product is installed on each workstation. Because each workstation has the software installed as a normal installation, the software does not need to be copied anywhere. Each workstation (client) gets the same update (downloaded from the server). Because the installation of the software is local to the client computer, the Windows installer can now roll-back updates (if necessary, as long as the update does not make incompatible data changes).
Data Integrity.
Server Writes. Because all data is written and read by the server, there far fewer data conflicts among multiple clients. If they do occur, conflicts can be easily handled by the server (in contrast to the complicated file locking method of controlling data access).
Write Once – Files are “written” by the server one time; each new write creates a new file with a particular version number. If the “write” is a change to existing data, the original file is only removed if the “write” is successful. Since there’s only one place in the code that any file is being written at any given time, it eliminates most write conflicts altogether.
Summary While 2012 was difficult, we have listened to your needs
and are working diligently to address them in ATX 2013.
In regard to networking environments, we are certain
that, by following the system requirements for both
servers and workstations (clients) and thereby
implementing a true client/server setup in your
organization, you will be more than satisfied by the
performance, stability and data integrity of ATX 2013.
NOTE: ATX has both minimum and recommended system
requirements—recommended being the setup for optimum ATX performance. The closer you are to meeting the recommended
system requirements, the better the system performance you can expect from ATX.
For more tools to help you with your network setup, refer to ATX™ 2013 System Requirements.
RavenDB:
A Solid Database for ATX
There has been some concern about a
potential connection between our 2012
data integrity issues and the new
RavenDB.
The root cause of our data issues in a
network environment were related to
supporting the shared-file
configuration described earlier in this
document.
We are confident that data integrity and
other issues described here will be
resolved by migrating to the
client/server network environment
outlined in the ATX 2013 System
Requirements.
ATX™ 2013 – Not Supported / Not Recommended While we do not prevent the use of the following products/environments, we neither support nor recommend their use for the reasons listed in the following chart. Like other software organizations, we cannot support environments that we do not use as part of our product testing. If you choose to use a non-supported product with ATX, you may require additional assistance from a qualified computer technician.
Not Supported/ Not Recommended
Definition Examples Reason(s) Why We Don’t Support Them
Remote Desktop Protocol (RDP), Terminal Services
Technology that allows one computer to remotely take over control or “host” the other computer. It also allows multiple physical locations to remotely access software from a single location.
Windows® Terminal Server or Terminal Services
Citrix® products that enhance Terminal Services
TeamViewer
Bomgar™
WebEx (Cisco)
Access is achieved through internet connection, which can be unstable. The tax software is not developed to run across internet connections for the following reasons:
When connectivity is interrupted, data can be lost;
Connection strength, which is affected by external factors such as network traffic and poor weather conditions, can vary dramatically throughout the day. Poor connection strength means poor performance.
Security risk. The nature of remote access to another computer necessitates stringent security software that may or may not be setup up properly on your network or wireless router. Unless you’ve enlisted the help of a qualified system technician, remote, virtual or wireless setups can present security risks for many tax professionals.
Licensing Agreement. Our current agreement specifies that the software must be purchased for a single “brick and mortar” location only, and not for virtual or remote locations.
Significant additional testing is required to support remote, virtual and/or wireless environments. Because our primary goals in 2013 are performance improvements, product stability, and data integrity, we cannot support these at this time.
Virtual Private Network (VPN)
Technology that allows one computer to remotely access a network (and, consequently, the applications on that network).
Virtualization Technology4 (“virtual machines”)
Technology that allows you to create a virtual machine (operating system) inside a physical computer.
XP Mode on Windows® 7
VMware®
Hyper-V (Microsoft)
Parallels® (Apple - Mac)
VirtualBox (Oracle)
Xen® (Linux)
Wireless Networks Computers are connected by wireless network cards (instead of physical cables) so they can share files, printers and Internet access.
4 If you need to install an older version of ATX and are concerned about compatibility, ATX software as far back as tax year 2006 can be loaded and will run on a Windows® 7 machine.
ATX™ 2013 SYSTEM REQUIREMENTS (For products 1040, 1040 Office, MAX®, Total Tax Office™, Total Tax and Account, PRS, ATX FAM)
Stand-Alone / Single Workstation (or, Workstation(s) Networked to a Server)
Server (in a Network Setup)
How Do I Find This Information?
Minimum Recommended Minimum Recommended
Operating System Windows®XP5 (Service
Pack 3) or Windows®7 Windows®7, 64-bit (SP1 or higher) or Windows®8
Windows®7 or Windows® Server 2008
Windows®7 or higher; Windows® Server 2008 or higher
Usually found in under the Windows® Start menu—Control Panel—System.
Processor 2.8 GHz
(Intel® Core™2 VPro)
3.4 GHz (Intel® Core™ i5 Quad processor or higher)
2.8 GHz
(Intel® Core™2 VPro)
3.4 GHz (Intel® Core™ i5 Quad processor or higher)
How to Find the Speed of Your Computer's CPU
Memory (RAM) 4 GB 4 GB or more 4 GB 4 GB or more How to Find the Amount of RAM in Your System
Available Hard Disk Space6
3 GB 10 GB 3 GB 10 GB How to Check Your Hard Disk Space
Computer Monitor (Display)
1024x768 32-bit 1024x768 32-bit 1024x768 32-bit 1024x768 32-bit
How to Find Out What Your Computer Resolution Is (Win XP and Win7); Get the best display on your monitor (for Windows 8)
Internet Connection7 Broadband Internet Access
Broadband Internet Access
Broadband Internet Access
Broadband Internet Access
How Can I Check My Internet Speed?
Internet Browser8 Internet Explorer® 8.0 (SP1)
Internet Explorer® 8.0 (SP1) or higher
Internet Explorer® 8.0 (SP1) or higher
Internet Explorer® 8.0 (SP1) or higher
Printer9 Inkjet (non- W-2/ 1099
forms); Laser (W-2/1099 forms)
Laser Inkjet (non- W-2/ 1099
forms);
Laser (W-2/1099 forms)
Laser CPP Inkjets Vs. Lasers
External Drive DVD DVD DVD DVD 1) Click Windows® Start menu; right-click Computer; select Manage. 2) Click Device Manager. 3) Under DVD/CD-ROM drives, double-click the device name. The Device Type must include “DVD.”
5 Windows® will not be supported for use with ATX after the 2013 tax season. Read about the risks of running Windows XP after support ends April 2014. 6 The recommended space allows for a full set of ATX forms, many more returns, and returns of higher complexity. If you have a large business that prepares complex returns, follow the recommended requirements. 7 Internet access is required for stand-alone, single workstation, and servers. Hi-speed connection required (DSL, cable modem, T1/T3). 8 All ATX 2013 functionality is tested using Internet Explorer®. Although other browsers will work with ATX, we recommend Internet Explorer for the most dependable browser experience. 9 For the best printing results, use a laser printer. W-2 and 1099 forms must be printed on a laser printer. While Ink jet printers can be used, cost per page is high and print performance is slow.
