Blog Posts

Modern, reliable Hybrid Cloud backup without the cost and complexity

Modern, reliable Hybrid Cloud backup without the cost and complexity

SolarWinds® Backup is the simple, powerful, and affordable cloud-based backup service for your virtual and physical servers. Reduce the cost and complexity of backup without sacrificing speed or reliability. Enjoy a low TCO, with no hidden costs.

  • Cloud-based backups mean no need to worry about storage requirements
  • Protect physical and virtual servers and their applications across major operating systems and hypervisors, with a single product
  • Fast backup, rapid restore of even large machines and databases with built-in compression.
  • A single dashboard lets you verify the status of all your backups at a glance
  • Implementation is as easy as dropping an agent on each server.


SolarWinds® Backup is the best of both worlds, offering a hybrid cloud architecture that meets every need with one solution — and meets them fast. If a physical disaster like a fire takes down your hardware, you can restore fully from the cloud. If you need to recover a large file or data set quickly, you can access the local drive.

What does this mean for your business? Efficiency. SolarWinds® Backup’s hybrid cloud backup lets you manage all of your backups from a single system, so you can streamline your processes. 


Bare Metal Recovery Disasters happen. If you lose entire systems, SolarWinds® Backup provides a bare metal recovery feature that lets you rebuild from the ground up.

With bare metal recovery, you can restore from the BIOS and get your systems back to work with nothing more than a simple bootable USB drive. Their worst-case scenario will become a minor blip on the radar, earning you. Don’t wait around for the worst—prepare for it and try SolarWinds® Backup.


Efficiency wins. That’s why SolarWinds® Backup features True Delta™ data deduplication, which captures byte-level changes instead of the full data set. This leads to shorter backup windows and allows for more efficient bandwidth usage.

After the initial system backup of your data, True Delta deduplication will back up changes only. And it does so at the byte level rather than the file level. Translation: The system backs up smaller amounts of data each time, allowing you to back up more frequently with less system drain. The result? Speed and efficiency, for you. 


When systems fail, recovery speed is everything. Your backup product must enable you to meet your recovery time objectives. That’s where LocalSpeedVault™ in SolarWinds® Backup comes in.

When LocalSpeedVault is enabled, MSP Backup & Recovery will automatically choose whether to restore from the LocalSpeedVault, the cloud, or both—whatever’s fastest. This gives you the quickest path to restoring continuity. Maximize uptime: with SolarWinds® Backup today.


Many organizations don’t back up more than a critical server and maybe a handful of workstations. This leaves their clients at risk of losing critical data. Foras low as $3 per workstation per month, the Backup Documents feature for SolarWinds® Backup will automatically back up your documents on their workstations twice per day. With SolarWinds global cloud network, you can easily restore from your cloud versions to any location.  Backup Documents lets you scale your backup services at an affordable price while providing greater protection against document loss from hardware failures, accidental deletions, or even ransomware.

Contact CCS Sales to see if the SolarWinds Hybrid Cloud Backup Manager is a good fit for your company.

Major credit card brands dropping signature requirement for North America

Major credit card brands dropping the signature requirement for North America

Face it, the payment world is changing. Rapidly! From cryptocurrencies to apple pay, and now there is one more change headed for small business owners in the United States. All of the major credit card brands are dropping a signature requirement for North American purchases.
With signature requirements already gone in many other countries, US is playing catch up with the upgrade to EMV chips. However, come April each card company is adding new rules or relaxing current rules for signatures.

So what does that mean for small business owners?

Almost every American adult is familiar with the obligatory squiggle of your name to complete a transaction. But how secure are those signatures in helping us avoid fraudulent transactions and purchases? Not very. Putting aside all of the hassles of writing your name with a dead pen, getting something that looks somewhat like your name on an electronic signature pad, or having to deal with signatures when traveling abroad in places that are used to chip and PIN, those signatures just don’t do a good job of keeping us safe, and in reality have not been effective for a long time.

If you missed the news, all of the major credit card brands are dropping a signature requirement for North American purchases. Coming on the heels of the upgrade to EMV chips, the card issuers are relying on far better security requirements today. But how does this impact you as a business owner? Let’s take a look at what the end of credit card signatures means for you.

Credit card signatures expiration date

Each of the major four card brands in the United States, Visa, MasterCard, American Express, and Discover, is implementing a change to credit card signatures effective April 2018. Starting that day, each card company is adding new rules or relaxing current rules for signatures. They may not go away instantly or all at once, but starting in April, you can expect far fewer credit card signatures at checkout.


Two years later, and the chips are doing their job at point-of-sale purchases where the card is present. They can’t do much for fraud online, but for offline fraud, the chip was a great step forward. Now, it seems the time has come to say goodbye to credit card signatures as our next phase of credit card processing in the United States.

Different rules for different cards

Visa is the biggest of the card brands. To say credit card signatures are going away completely in April 2018 would be a little misleading. According to a blog post from Visa at its official Tumblr page, the signatures won’t be going away everywhere, and merchants still have some leeway to decide for themselves whether or not to make customers sign. Only merchants with an active chip reading terminal are exempt from signatures, so stores and checkouts that don’t take chips will still need to take signatures for most purchases.

This means that at grocery stores, gas stations, drug stores, and other large chains, you can expect the signature to effectively vanish on the April effective date. However, smaller businesses that have not spent the money to upgrade their card reading terminals to chip readers may still continue to ask for signatures for a while yet. New terminals run up to $1,000, so many small businesses won’t rush out to buy one, particularly if they don’t take many credit cards.

Why merchants should upgrade to EMV chip readers ASAP

While that $500-$1,000 expense isn’t exciting, a new card reader that takes chip-enabled cards is probably worth the cost. On October 1, 2015, the liability for card fraud shifted from the banks to the merchants unless the merchant is using an EMV chip reader. The liability shift is a significant occasion for any business that accepts credit cards in person. Starting on that date, any fraud caused by the business has to be paid for by the business if they don’t have the updated chip card reader. Think of the newer chip card terminals as an insurance policy against paying for the fraud that originated at your business’s card processing system.

Because Visa is still requiring signatures for some merchants that don’t have the chip reading terminals, your business is not getting the benefit of the end of credit card signatures unless you have a chip reader, which you should anyway to protect your customers from fraud and yourself from paying.

Join the next century of credit card processing

The real future of card payments likely involves no card at all and instead relies on a digital wallet with a system like Android Pay or Apple Pay, but in the meantime, customers continue to use plastic credit cards to make everyday purchases. Thankfully, starting soon, that checkout process will get a little easier thanks to the end of credit card signatures.

This article was originally published on and

A Great Way To Get Rid Of Merchandise

A Great Way To Get Rid Of Merchandise

You want to free up the cash in those slow-movers to buy new, better-selling items for spring AND you want to lower stock levels, so you don’t have as much to count during your physical inventory.

One particularly useful markdown at this time of the year is a “buy-one-get-one-free” (BOGO). This promotion accomplishes two major goals:

1. Deep discount (up to 50%) encourages customers to buy

2. Moves twice as much merchandise to lower stock levels

Here are some ways to use the BOGO deal to get rid of your slow-moving stock strategically.

• You have a lot of one particular item: Do the standard, buy one widget, get one widget free. For most shoppers, this is a no-brainer.

• You have some slow-moving colors in an item: Buy an aquamarine widget (the slow-moving color), get a second widget of any color free. BOGO will help move all widgets, but specifically the aqua widget.

• You have some slow-moving sizes: Buy a large widget (the slow-moving size), get your choice of small or medium widget for free. This one’s good because the markdown will be less than 50% and you will be pushing that least popular size.

• You have two similar items that are overstocked: Buy a widget, get a thing-a-ma-jig for free. Great for gift givers who want to give similar but different gifts to 2 sisters, two teachers, two neighbors – or buy one for me, one for you!

• You have a bunch of unrelated, but slow-moving items and not enough of just one to do a good single item BOGO: Buy any one item on this table, and get a second item from the table for free. Bargain hunters love this one, and you’ll move a lot of merchandise in a hurry!

Have fun with this one and watch your cash accumulate while your leftover inventory disappears!

The Disadvantages of Using Duplicate Document Numbers

The Disadvantages of Re-using Document Numbers

They are numerous reasons for not doing this as follows:

Typically, in most software applications, a document number is considered a Primary Key, so it should be considered “Unique” and would not be duplicated. However, there are some programs where it might be a Secondary key where multiples might be allowed, such as using a sequence Number, such as when using duplicate entries and historical tables such as Check History (e.g. checks, voids for the same checks, or manual payments, EFT transactions, etc.).

Even in situations where the programming might allow for this sort of thing, a duplication might cause other issues with software functionality, As examples.

  • GAAP – According to GAAP (Generally Accepted Accounting Practice) document numbers should also be considered unique. This also makes auditing easier. If an auditor sees a lot of duplicate documents, it may prompt the auditor to dig deeper looking for other accounting irregularities, thereby artificially extending the length of the audit.
  • The same Ticket/Invoice number exists in history multiple times – A user runs a report on ticket #20324 without having specified a date or date range. The subsequent report returns eight documents created over a period of 10 years.
  • Problems posting – I have seen examples where end-users have used the same invoice number dozens of times. When they try to post a new voucher using the same invoice number, the program may hang or crash while it attempting multiple times to create a “New” document for one that already exists to previously. As an example, the program might attempt to write the same document into history 10 times, and then just stop the attempts to write the new data.

The worst example of this that I have seen so far, is with one vendor that 21 manual payments on file using an invoice and check number of “SUPPLIES” – In this case, a better example would create the numbers would be something like “SUPMMDDYY” (e.g. SUP031518).

If you have any questions or need assistance with the creating your own document number assignment schema, please contact the CCS Retail Systems Support department.

– John

Signature Capture Devices



Signature Capture Devices.

Would you like to have your customers signature show up on Invoices and Order printouts?

There are a couple devices that can be used to do this.

One is the Ingenico ISC250 Pin Pad, it combines a signature capture device, along with a Pin Pad and MSR for processing credit/debit card payments. It will capture the customers signature, which can then be used to print on receipts, invoice and order forms and also be looked up in ticket history without printing.

There is also the Topaz signature capture device. It will only capture the customer signature that can then be printed on receipts, invoices, and order forms.

The signature will not automatically print on the forms with these devices and will need to be added to the form of your choice.

The Topaz is a useful device if you are processing payments outside of Counterpoint (i.e. Standalone Credit Card Terminal), or would still like to capture signatures for A/R charge type sales/returns or any transaction that you set as requiring a signature.

There is a little setup required, and there are specific device models that can be used, so if you are interested, please contact the CCS Retail Systems Support or Sales Department at 800.672.4806 for help determining the right model for your system.


Recalculating Inventory in a Counterpoint Multi-site Environment

Recalculating Inventory in a Counterpoint Multi-site Environment

If you are using Counterpoint in a multi-site environment, care must be taken when it comes to running the Inventory Recalculate Quantities procedure. This procedure checks several of the quantity fields in the inventory tables, against the data in the rest of the tables. Fields such as quantity-committed, quantity-on-po, and quantity-on-transfers, among others, are checked and corrected if necessary. Note, that it will not adjust quantity-on-hand. That must be done via inventory adjustments.

The issue in a multi-site environment relates to how replication works. When a replication session starts with a remote site, it does not take a snapshot of the database. Rather, it goes through the list of tables and makes the appropriate updates as it processes the various tables. What this means as to the inventory quantity recalculations, is that after finishing replication, all of the data is not consistent as to the point in time that it represents, due to ongoing user activity.

To illustrate, let us look at the purchasing process and inventory quantities. The purchasing tables are processed by replication in the first half of the list of tables, while the inventory tables themselves are processed nearly at the end. This process leads to the possibility that a replication session will start, and get through the purchasing tables. Then while replication processes other tables, a user at the remote site posts a new purchase order. A bit later, the replication processes the inventory tables. In this case, after the replication is finished, the hub site has no records of the purchase order that was posted at the remote site. However, it does have updated inventory records showing a quantity-on-po. In the Inventory Recalculate Quantities is run at the hub at that point, the result would be to set the quantity-on-po to zero for all items on the purchase order that was posted (assuming that they are not on any other purchase orders). When replication runs again to the remote site, the purchase order will then be transferred to the hub. Also, the quantity-on-po that was set to zero at the hub will be sent to the remote. Now both the remote and the hub have an open purchase order, while the quantity-on-po for all of the items on that purchase order will be zero.

Inventory quantities should only be recalculated after replicating with the remote sites when no activity is occurring at those sites for the entire duration of the replication, avoiding this timing problem. Typically, this means that the recalculation must be run well after the remote site closes, or before they begin processing in the morning. Remember, it is not enough that the remote site has closed, and everyone has gone home. A replication must occur after they have closed and gone home. Only then will the recalculation routine have data that truly reflects the state of the data at the remote site. Most of the time, this means that the best time to run the recalculation is in the morning before users at the remote site start doing anything with Counterpoint.


How to Help Us Help You!

How to Help Us Help You!

When we receive calls for support help, we want to assist you as quickly as possible. For that reason, we assign numbers to each request as it is received. These numbers appear on work orders (or tickets) that are given to the technician who will provide the service to you.

Many of our customers have multiple sites, and sometimes we get calls for support from several of these sites all at the same time. Because this happens, a technician may be working simultaneously on multiple issues for the same company, but for different sites. Each issue, however, will have a separate assigned number. This number can be given to you by the technician on the initial call.

When it’s necessary for you to return a call to a technician on an open issue, it saves a lot of time and confusion if you mention the open ticket number of the issue. Therefore, you won’t have to explain the entire problem again before the call is put through.

One other reminder—be sure to provide the phone number where you want to be called if it’s necessary for the technician to call you back. Customers call us from their office, from home, and from cell phones. If you think the tech “has your number,” it might not be the one you want to be used today.

We’re here to help you at 425-672-4806 or email us.


Physical Count Procedures and Equipment

Distribution Systems

Physical Count Procedures and Equipment

It’s that time of year again, Physical Count Time, and having the right equipment will help with quick and accurate counts.

CCS used to advise using an Optimus SP5500 PDT to do counts. It is simple, quick, and easy to use. Unfortunately, it has been discontinued and although there are still a few out there, they are getting harder to find.

CCS has been testing many different devices and have finally found one that is even easier to use. It is the AML LDX 10. There are many features that can be used that the Optimus did not have.

For example, with the AML device, it can be programmed to only allow keypad entry only for quantities, which eliminates barcodes scanned in as quantities, the user interface is easier to read and bigger and brighter.

It runs a compact version of the Windows OS, so it will also be more familiar looking to your users. It also has a touchscreen interface with bigger buttons for ease of use.

It also has a programmable barcode scanner and is USB connected for easy installation. Downloading of the information is also much more user-friendly and intuitive and multiple files can be saved for downloading all at once or one at a time.

Reviewing your work is also much easier and intuitive with on-screen directions and buttons for deleting and editing.

If you are ready to get your Physical Counts done quickly, contact the CCS Retail Systems Support Department at 800.672.4806 or email us for pricing. We also have units available to rent with advanced notice.


New TLS Patch Coming for


ViewPoint Newsletter | NCR
New TLS Patch Coming for V8.5.2.1 March 6th

Payment Card Industry Data Security Standards (PCI DSS) require all PA-DSS validated payment applications to discontinue the use of “early TLS” (i.e., all versions of SSL and TLS 1.0) by June 30th, 2018. For more information on this, please refer to the TLS 1.2 transition document. 

To comply with this requirement, NCR Secure Pay will no longer accept early TLS connections after 2:30 A.M. on June 5th, 2018. In addition to the previously mentioned updates to NCR Counterpoint V8.5.4 and V8.4.6, we will also be releasing a patch for V8.5.2.1 . Releases will are scheduled as follows: 

  • V8.5.4 Patch 002: Scheduled for 2/20/2018
  • V8.4.6.19 Service Pack: Scheduled for 3/6/2018
  • V8.5.2.1 Patch: Scheduled for 3/6/2018

We do not plan to release patches or Service Packs to support TLS 1.2 in other versions of NCR Counterpoint.

To prepare for the transition to TLS 1.2, you must first ensure that TLS 1.2 is supported and enabled on your workstations by following the appropriate steps for your operating system, as outlined in our TLS 1.2 transition document. 


Getting Ready For Transport Security Layer (TLS) 1.2


Payment Card Industry Data Security Standards (PCI DSS) require all PA-DSS validated payment applications to discontinue the use of “early TLS” (i.e., all versions of SSL and TLS 1.0) by June 30th, 2018.

To comply with this requirement, NCR Secure Pay will no longer accept early TLS connections after 2:30 A.M. on June 5th, 2018. In addition, updates to NCR Counterpoint V8.5.4 and V8.4.6 that will require the use of TLS 1.2 for payment transactions processed through NCR Secure Pay will be released as follows:

  • V8.5.4 Patch 002: Scheduled for 2/20/2018
  • V8.4.6.19 Service Pack: Scheduled for 3/6/2018

We do not plan to release patches or Service Packs to support TLS 1.2 in other versions of NCR Counterpoint. To prepare for the transition to TLS 1.2, you must first ensure that TLS 1.2 is supported and enabled on your

workstations by following the appropriate steps for your operating system, as outlined below.

 Do NOT disable early TLS on your workstations, as NCR Counterpoint Services (CPServices) requires TLS 1.0 for internal communications. Because PCI DSS prohibits the use of early TLS for the external communication of payment transactions only, using TLS 1.0 with CPService does not violate PCI-DSS compliance.

CPServices will be updated to use TLS 1.2 in a future NCR Counterpoint release.

Once TLS 1.2 is enabled, you can install V8.5.4 Patch 002 or the V8.4.6.19 Service Pack—depending on which version of NCR Counterpoint you are using—to begin using TLS 1.2 for all communications with NCR Secure Pay.

  V8.5.4 Patch 002 and the V8.4.6.19 Service Pack will only work with TLS 1.2. If you install these updates on a workstation for which TLS 1.2 is not supported and enabled, NCR Counterpoint will be unable to connect to NCR Secure Pay and you will be unable to process payments.

W I N D O WS 8. 1/ W I N D O W S 1 0 / W I N D O W S  S E R V E R 2 01 2 R 2

By default, TLS 1.2 is supported and enabled in Windows 8.1, Windows 10, and Windows Server 2012 R2. Thus,

no additional configuration is required to use TLS 1.2 with these operating systems.

W I N D O S 7/ W I N D O W S  E M B E D D E D  P O S  R EA D Y  7 / W I N D O W S  S E R V E R  2 0 0 8 R 2

If your NCR Counterpoint workstations are running Windows 7, Windows Embedded POSReady 7, or Windows

Server 2008 R2, first ensure that you have installed all current Service Packs, updates, and security patches.

To enable TLS 1.2, create the registry setting entries (in the Client subkey) that are specified in the TLS 1.2

section of the Transport Security Layer (TLS) registry settings page in the Microsoft documentation library


Every effort has been made to ensure the accuracy of this document. NCR makes no representations or warranties with respect to any of the information contained in this document and specifically disclaims any express or implied warranties of merchantability or fitness for a particular purpose with respect to such information. NCR shall not be liable for any errors or for incidental, indirect or consequential damages in connecting with the furnishing, performance or use of this document.

V E R I FY I N G  T H A T  T L S 1 .2  I S  E N A B L E D

If you are using Windows 7, Windows Embedded POSReady 7, or Windows Server 2008 R2, you can verify whether TLS 1.2 is supported and enabled on each of your NCR Counterpoint workstations by using Microsoft Internet Explorer to access the How’s My SSL? Website (

Only use Internet Explorer to verify that your workstation is using TLS 1.2; other browsers do not use the Windows TLS system and may display incorrect results.

The Version section of the page should indicate that your client is using TLS 1.2, as illustrated below.

W I N D O W S  E M B E D D E D  P O S  R E A D Y  2 0 0 9

NCR does not currently plan to test or support TLS 1.2 with Windows Embedded POSReady 2009. Although Microsoft has indicated that an update will be made available to support TLS 1.2 with Windows POSReady 2009 ( xp-posready-2009/), merchants who wish to continue using POSReady 2009 must do so at their own risk.

We strongly recommend upgrading any workstation that is running Windows POSReady 2009 to a newer, supported operating system.