The 5 IT Problems Rockland County Businesses Call About First

The five things Rockland businesses call their IT provider about most are passwords, printers, a file or email that has gone missing, Outlook, and QuickBooks, in that order.

None of those are dramatic. None of them are specific to Rockland either, and that second part matters a lot more than it sounds like it should.

Nothing About Rockland Makes These Worse

I want to deal with the local angle honestly before anything else, because most articles like this one handle it badly.

People expect a piece about local IT problems to name something regional. Storms that knock out the power on Route 9W. Some quirk of the internet service between Nyack and Suffern. A pattern that only shows up here. I have been doing this work in Rockland for over twenty years, and across all of that time I cannot point to a single failure mode that belongs to this area rather than to small offices generally. I have looked. The infrastructure around here is stable. When we lose internet locally it’s because something genuinely major happened, and that is very, very seldom. No asterisk on that. I would rather say so plainly than invent a regional hazard to make an article feel more local.

So what’s actually local about this list? Who’s calling. The businesses running managed IT services across Rockland are mostly 5 to 60 people, they mostly run Microsoft 365 and QuickBooks, and a lot of them have a file server or a printer that’s been in the same closet since before the current office manager started. That mix produces a very predictable set of phone calls. Same five, year after year. Answering them across Rockland, from Nanuet to Haverstraw, is what makes me confident about the order below.

Passwords, and It Is Not Close

Number one. Not by a small margin either.

Somebody’s locked out, somebody’s password expired overnight, somebody changed it on their laptop and now their phone won’t stop asking. It’s the most common ticket in almost every small business I’ve worked with, and here’s the uncomfortable part. Self-inflicted, mostly.

Most offices are still running a password policy somebody set up in 2011. Expire every 90 days, require an uppercase letter, a number, and a symbol. That policy is why your staff writes passwords on sticky notes and why your ticket queue looks the way it does. It’s also, as of the final 2025 revision, the opposite of what the federal standard says to do. NIST Special Publication 800-63B now states that verifiers “SHALL NOT require subscribers to change passwords periodically” and “SHALL NOT impose other composition rules” like mixing character types. What it asks for instead is length, a minimum of 15 characters when a password is doing the work alone, and a forced change only when there’s actual evidence something was compromised. Length beats symbols.

Read that again if you’re the person who set the 90-day rule. You’re not being careless by dropping it. You’re catching up.

The practical fix is boring and it works. Turn off scheduled expiry, get everyone on multi-factor authentication so a leaked password stops being a crisis, and put the credentials somewhere they don’t have to be remembered. BitWarden is our recommended system for that last part. If you’re weighing options there, we went through what actually matters in a password manager for a small team in more detail.

Printers. Ask Any IT Person.

Ask any technician which part of this job is the worst to troubleshoot. Same answer, every time. Printers. It is a running joke, and it is also completely sincere.

There’s a real reason it earns second place. A printer is the only device in a small office that has to satisfy four separate things at once, and any one of them can quietly break without the others noticing. Each workstation carries its own driver, which Windows likes to replace during updates. Then the print spooler, a piece of software old enough to vote. It shows. The network is its own category, because a printer that took its address from DHCP will happily move to a different one after a power cut and stop answering to the old one. Firmware sits underneath all of that, almost nobody updates it, and it occasionally decides a document is too complicated to render. Not rare enough.

Add a second office, a few people printing from laptops that roam between home and work, and one shared device that three departments think of as theirs, and you get a support ticket that’s genuinely hard to reproduce.

Static addresses for shared printers. That one change removes more printer calls than anything else I can recommend in a sentence.

It Was Here a Minute Ago

Third on the list is the one people describe rather than name. An email is gone. A file was on the desktop yesterday and isn’t now. A whole folder is missing off the shared drive and two people swear they didn’t touch it.

Usually it is recoverable. Usually the person calling has no idea they could have done it themselves in about thirty seconds. Outlook has a Recover Deleted Items function that pulls back things emptied out of the Deleted Items folder. Most people have never opened that menu. Worth a look.

What matters far more, and what almost nobody knows, is that the recovery window is shorter than people assume and it starts the moment the thing disappears, not the moment somebody notices. Rarely the same day.

Retention windows per Microsoft’s published documentation, September 2026.

Those numbers come straight from Microsoft. The Exchange deleted item retention documentation puts the default at 14 days with a hard ceiling of 30. The SharePoint data deletion documentation confirms the 93 days spans both stages rather than resetting, that second-stage deletions are “purged immediately,” and that an item removed through the API “isn’t recoverable from the site or site collection Recycle Bins” at all.

That last row is the one that catches businesses out. A backup tool, a document management add-on, or a migration utility doesn’t delete the way a person clicking delete does. It bypasses the bin. Nobody finds out until somebody goes looking for a file that was never in a recoverable state to begin with. Too late by then.

Outlook and QuickBooks Break More Than Everything Else Combined

Fourth and fifth belong together, because in my experience they have always traveled together. Those two applications generate more issues than any other programs a small business runs. Not close.

Outlook’s problem is that it keeps a local copy of everything. That cached file grows for years, it gets corrupted, the profile it belongs to picks up settings from three previous configurations, and the fix is very often to tear the profile down and build a fresh one rather than repair what’s there. Add-ins make it worse. Every toolbar somebody installed to send faxes or track emails is another thing loading into the same process. They add up.

QuickBooks is a different shape of the same story. The desktop version wants the company file on a machine running its own hosting service, and it is particular about how that gets shared. Multi-user mode drops. A workstation loses its map to the file. Somebody opens it over a VPN and it crawls, because the file was never designed to be read across a slow link. None of it is exotic. Fiddly, all of it. Fiddly is exactly the kind of work that goes fast for somebody who has seen it twenty times and slowly for somebody meeting it fresh.

The reason these two dominate isn’t that they’re badly built. It’s that they’re old, they hold state locally, and they’re wired into everything else you run. That combination generates tickets.

The List Stops at Five

I’ve been asked what number six is. There isn’t one worth naming.

After those five, everything else shares a bit of the pie. A scanner that stopped scanning. A monitor that won’t wake. Someone’s Teams audio. It flattens out into a long tail with no clear ranking, and anyone who hands you a tidy list of ten is padding. Ten is marketing.

Worth saying that this list answers a specific question, which is what a business calls its provider about on an ordinary Tuesday. That’s a different question from what finally makes a business fire its provider and go looking for a new one. We covered that second one separately, using the problems that trigger a first call from a professional services firm, and the two lists barely overlap. Day-to-day friction and switching triggers aren’t the same animal.

What Changes When Somebody Owns These

Here’s the thing about a list this boring. Every item on it is solvable, and none of them get solved by buying software. Software is not the lever.

Passwords stop generating tickets when somebody changes the policy and rolls out a manager. Printers stop moving when somebody assigns static addresses. Missing files stop being emergencies when somebody has already confirmed what your actual recovery windows are, before anything goes missing. In every one of those sentences the operative word is somebody. That’s the whole argument for having a provider rather than a person who is good with computers.

My team’s standard is a response within 15 minutes during business hours, and honestly it’s often quicker than that. A ticket comes in, a couple of minutes to triage and route it, a call back inside five. That standard applies whether the ticket is a jammed printer or something that actually looks serious, because from the caller’s side you can’t always tell which one you’ve got. Help desk and remote support is where nearly all of these get resolved without anyone driving anywhere.

Managed IT with VJNetworks starts at $995 a month for the businesses we typically work with, 5 to 60 employees across the Tri-State area. Over twenty years in, we’ve kept 97% of our clients. I’d argue that number has more to do with the boring five than with anything impressive.

Before You Pick Up the Phone