Download System Requirements (PDF format)

Procare v10 Technical Information

Minimum Computer Requirement

• Processor: 600Mhz (1GHz or faster highly recommended)
  x86 (32-bit) or x64 (AMD64 or Intel EM64T) processor required
  [Note: IA64 (Itanium) not supported]
• Memory: 1 GB (2GB recommended)
• Free Hard Drive Space: 2 GB (1 GB for client only)
• Network Card (NIC) required
• Monitor Display for Procare itself: 800 x 600, 256 colors (1024 x 768 high color, 16-bit or more highly recommended)
• Monitor Display for a Check In Computer: 800 x 576, 256 colors

Operating System
Compatible with 32 and 64-bit versions of Windows.

• Windows 7
• Windows Vista (SP1 or later)
• Windows XP SP3
• Windows Server 2011 (Small Business Server or Home Server)
• Windows Server 2008 (SP1 or later)
• Windows Server 2003 (SP1 or later)

Note: Macintosh / Apple Computers ... read more

• .NET Framework 2.0 SP2 or later (distributed with Procare)
• SQL Server 2005 Express Edition SP3 or later (distributed with Procare). Note: SQL Express has a 4 GB limit on the size of the database.
• Optional: Use your own SQL Server 2005 SP3 or later

Data Hosting

• No wireless AirCards® (3G, 4G, etc.)
• The primary internet connection to your facility must be WIRED using a cable modem, DSL, fiber, etc. Secondary connections may be wireless as long as they meet bandwidth requirements.
• Minimum available bandwidth:  1.5 mbs/1,500 kbps (download) and 512 kbps (upload).  Test Your Upload/Download Speed

Important! If classroom cameras or other devices/programs share your bandwidth you may not have enough "available" bandwidth for Procare to run effectively. Make sure you have enough total bandwidth to accommodate all your needs.

• Data Hosting is NOT COMPATIBLE with Terminal Services or any version of Microsoft Windows Server.

Security Features

• Centralized database capability (multiple locations hosted in one database).
• Requires Procare client software to access database - not exposed through a simple file share.
• Database does not store any credit card or bank account numbers.
• Hierarchical configuration with granular control over User Groups and permissions.
• Passwords created by each individual user (not by a supervisor) and are never visible to anyone.
• System Supervisor can see who’s logged in and from where they are logged in.
• System Supervisor can kick connected users off system (or send a log off request).

File Location:
Procare is installed to the 'Program Files' directory on drive C of the local machine, for example C:\Program Files\Procare. Note: If you are using your own SQL Server (rather than the supplied SQL Express Edition) the database will install to the default location configured within SQL (beginning in version 10.1.3720).

How is it installed?
Installation is based on the ‘‘role’’ each computer will play. A computer will either host the data or be a client that accesses the data. Some computers will play both roles.

Single Computer Only
Roles: both host and client (install database server, licensing server, and client software)
Note: By default, this local database will not be available for connection over a network - may be changed if needed.

Peer Network - Roles:
peer server = both host and client (install database server, licensing server, and client software)
other computers = client (install client software only)

Server Based Network - Roles:
dedicated server = host (install database server & licensing server)
other computers = client (install client software only)

Wide Area Network - Roles: 
dedicated server = host (install database server & licensing server)
other computers = client (install minimal set of client files --- see note 1)
Bandwidth for hosted data: (see above)

Notes:

1. Client software automatically updates based on whatever client files the server has available. This ensures all clients are running the same version.
2. The firewall at the server location must allow SQL traffic as well as Procare licensing traffic. Clients maintain a constant connection to the licensing server and make/use many connections to the SQL database. See: Firewall Article