Enterprise IT Services · Texas

Managed IT services and IT support for Houston and Texas businesses: from Active Directory to the printer that won't stay online.

Managed IT services and IT support from Houston for small and mid-sized companies: identity, endpoints, the network, the servers, the mailboxes, the tickets — co-managed next to your own IT person or provider, or as scoped projects. It is the layer every software project stands on, and in most companies it has no diagram and one person's memory holding it up. We put it on paper, bring it back into support, and keep it there: on-site across Greater Houston, remote across Texas.

Business hours, US Central. An engineer replies within one business day — no answering service, no handoff to sales.

Sound familiar?

Six things that are quietly running a Texas business

None of them is exotic. Each one is a system with no drawing and no owner, and each one gets fixed the same way: written down first, then repaired at the cause.

The IT person left with the passwords

The domain admin account, the firewall login, the registrar, the copier portal: all in one head, and that head gave notice on a Friday. Nothing has been written down since.

Ex-employees who can still sign in

Offboarding is a sticky note. Active Directory shows sixty enabled accounts for thirty-five staff, three of the extras with domain admin rights, and the tenant still pays for every mailbox.

The printer goes offline every Monday

A reboot fixes it, so a reboot is the procedure. Nobody has asked why, because asking costs more than rebooting — until the Monday it does not come back.

A network nobody has drawn

Unmanaged switches daisy-chained under desks, one flat network for the office, the guest Wi-Fi and the warehouse scanners, and a firewall last reviewed by whoever installed it.

A server under a desk, in hurricane country

On a power strip, backing up to a USB drive in the same room. Beryl cut power to about 2.2 million Houston-area customers in July 2024, some for over a week — the backup went dark with the server.

Windows 10 machines still on the floor

Support ended on October 14, 2025. Half the fleet fails the Windows 11 hardware check, and nobody has raised a plan for those yet.

Capabilities

Eight layers, one inventory

Everything below starts with the same deliverable: a list of what you have, what state it is in, and what it costs to leave alone. The work is scoped from that list.

Active Directory & Entra ID

Identity is the system every other system trusts, so Active Directory and Entra ID administration comes first.

  • Stale users, computers, and groups — no sign-in in 90 days — found and disabled before anything is deleted, with a report of what changed
  • Group Policy consolidated: the forty objects nobody dares touch become the eight that actually apply
  • Hybrid join and Entra Connect, so one account opens the desktop, Microsoft 365, and the VPN (Entra ID is the directory formerly called Azure AD)
  • MFA and conditional access rolled out in stages, with break-glass accounts sealed and tested
  • A tiered admin model: a Domain Admins group with two members rather than twelve, and an everyday account for everything else
  • Onboarding and offboarding as a script that runs the same way at 4:55 on a Friday afternoon

Endpoints, Intune & Patching

Endpoint management done properly: every laptop enrolled, encrypted, patched on a written schedule, and replaceable in an afternoon.

  • Device management (Intune) and Autopilot, so a new machine builds itself out of the box and a lost one is wiped remotely
  • Patch rings — a pilot group first, then the rest — in a window that is written down, not mid-demo
  • BitLocker on every drive, with recovery keys escrowed where the help desk can find them
  • Windows 11 readiness checked per machine — TPM 2.0 and the processor floor — so the refresh is budgeted from a list, not a guess
  • Endpoint detection and response, standard images, and local admin rights removed without a revolt

Networks, Firewalls & Wi-Fi

Network support and firewall management start with a drawing of the network, then a network that matches it.

  • Firewall rules reviewed line by line: the dead ones removed, the rest documented with a reason
  • The firewall itself checked against its vendor's end-of-support date — an edge device that stopped getting patches is the first thing a scanner finds
  • VLANs that separate the office, guests, cameras, printers, and the warehouse scanners from each other
  • Wi-Fi surveys for the warehouse and the yard — racking, forklifts, and metal all argue with radio
  • Site-to-site and remote-access VPN that stays up when the ISP changes the address
  • DNS, DHCP reservations, and switch configurations backed up, so a replacement is a restore rather than a rebuild

Servers, Virtualization & Backup

Server administration, backup, and disaster recovery: the machines you still own, kept in support, and a restore somebody has actually rehearsed.

  • Hyper-V, VMware, and Proxmox hosts sized and patched, with the licensing bill re-read since VMware went subscription-only
  • Every Windows Server tracked against its end-of-support date, with an upgrade path chosen per server
  • 3-2-1 backups — three copies, two media, one off-site and immutable — including Microsoft 365 mail and SharePoint, whose default retention is not a backup until a backup product is switched on
  • Restore drills on a schedule and timed, so the recovery estimate is a measurement rather than a hope
  • UPS runtime matched to a clean-shutdown script, and a generator transfer you have had tested under load by the people who service it

Printers, Scanners & Peripherals

The device everyone has learned to reboot, fixed at the cause instead of the symptom.

  • A DHCP reservation and a standard TCP/IP port on 9100 instead of a WSD port, so the queue survives a lease change
  • One print server and one driver per model deployed by Group Policy — or Universal Print, which removes the server and the driver question — rather than thirty local installs
  • Sleep, firmware, and status-polling (SNMP) settings that stop a printer vanishing overnight
  • Scan-to-folder that broke when Windows 11 24H2 began requiring SMB signing, fixed on the copier rather than by weakening the PCs
  • Label printers on the warehouse floor — ZPL, the Zebra label language, print-and-apply, and the scanners that feed them
  • The copier dealer, the toner contract, and the vendor's support line chased on your behalf — the lease itself stays yours

Microsoft 365 & Email Administration

The tenant reconciled, the mail authenticated, and permissions somebody can explain.

  • Licence reconciliation: every paid seat matched to a person who still works here
  • SPF, DKIM, and DMARC set and monitored, so quotes stop landing in the customer's spam folder
  • Shared mailboxes, distribution groups, and retention policies documented rather than inherited
  • SharePoint and Teams permissions untangled from the sprawl that grew while nobody was watching
  • On-premises Exchange, out of support since October 14, 2025, moved to Exchange Online or Exchange Server Subscription Edition

Help Desk & User Lifecycle

An IT help desk with a ticket that gets answered, a first day with the laptop ready, and a last day that closes every door.

  • A ticket queue with response times written down, answered by a person rather than an auto-reply
  • Onboarding: account, licence, laptop, groups, and printers ready before the new hire walks in
  • Offboarding in the right order, the same day: sign-in blocked, sessions revoked, MFA reset, mailbox made shared, files handed over, licence reclaimed
  • Co-managed: you keep your IT person and the desk; we take Active Directory, the firewall, patching, and the projects that keep getting pushed off
  • Runbooks for the ten things that go wrong most, so the fix stops depending on who is in that day

Security Baseline, Documentation & Vendors

A cybersecurity baseline — the controls Texas law now expects of a small business — written down and kept current.

  • A written security baseline sized to the company: CIS Controls Implementation Group 1 as the floor, NIST CSF 2.0 above it
  • An asset inventory and a network diagram that match what is racked and plugged in today
  • A company password manager, with the admin logins finally out of the shared spreadsheet
  • ISP, copier, phone, and software vendors managed: renewals tracked, support calls made for you
  • Incident and breach-notification steps rehearsed against the Texas 60-day and 30-day clocks

Not on this page: consumer PC and laptop repair, copier leasing and managed-print contracts, structured cabling (we bring in a cabling contractor), staffing, and training courses. Printer work here is configuration, drivers, queues, and the network; the hardware stays with the dealer who leased it.

Who this is for

Six kinds of Texas company that call about this

Twenty to five hundred people, an IT generalist or an existing provider, and infrastructure nobody has drawn. The estates below are where the work in the case files came from.

3PL and warehouse operations

Label printers on the floor, scanners that roam between aisles, Wi-Fi that has to survive racking and forklifts, and a WMS that stops when the network does. Most of our printer work began here.

Manufacturing and fabrication shops

Shop-floor PCs that run one machine and must never be patched mid-shift, a network where the office and the machine controllers finally sit on separate VLANs, and a file server holding twenty years of drawings.

Field-service contractors

Fire alarm, electrical, HVAC, and inspection companies: technicians on tablets, laptops that leave the building every morning, and records a customer or an authority can ask for at any time.

Professional services and back offices

Accounting, engineering, legal, and staffing firms living in Microsoft 365: SharePoint permissions nobody can explain, shared mailboxes with no owner, and offboarding that has to close every door the same day.

Software companies selling to Texas agencies

A product that runs on your own servers meets TX-RAMP on your identity setup, your patching, and your logs. We bring the infrastructure side up to what the questionnaire asks.

Multi-site companies across Texas

A head office in Houston, a yard in Dallas–Fort Worth, a plant outside San Antonio, a sales office in Austin: one directory, one tenant, site-to-site VPN, and a schedule for the visits that need hands.

How it runs

How a co-managed or project engagement runs

Four steps, each priced before it starts, and each one a place you can stop. The first conversation is free and usually settles which of the four you need.

  1. 1

    Inventory and diagram

    Fixed price, one to two weeks. Every account, device, server, share, printer, licence, and firewall rule listed, and the network drawn as it is actually cabled. You keep the document whether or not there is a step two.

  2. 2

    A list with a price on each line

    What the inventory turned up, ranked: urgent, worth this quarter, safe to leave for years. Each project is quoted fixed-price from that list, so nothing is estimated on a system nobody has read.

  3. 3

    Projects, staged

    The cleanup, the migration, the segmentation, the printer fixed at the cause. Old systems keep running beside new ones until the new ones have earned trust, and every change is written up as it lands.

  4. 4

    A retainer you can end

    Business-hours support from the engineers who did the work, response time in writing, sized to headcount and device count. Leaving hands you back your documentation, your passwords, and every runbook.

Support is quoted from the inventory rather than from a rate card: sized to headcount and device count, with the response time written into the retainer. The questions at the bottom of the page say how, and what it does not include.

Why now

The dates that start this conversation

Most IT projects arrive as a support deadline. These are the ones on the calendar for the software most Texas offices still run — Microsoft's published dates, checked September 2026.

Product Support ends Status Where that leaves you
Windows 10 October 14, 2025 Ended Paid Extended Security Updates for business, a year at a time through October 2028; the consumer extension does not license a business PC. Microsoft 365 Apps keep their security fixes on Windows 10 until October 10, 2028.
Exchange Server 2016 & 2019 October 14, 2025 Ended Exchange Online, or Exchange Server Subscription Edition if mail has to stay on premises — the only on-premises edition still receiving updates. 2019 upgrades in place; 2016 moves side by side.
Office 2016 & 2019 October 14, 2025 Ended Microsoft 365 Apps on the licence most tenants already pay for, or Office LTSC for the machine that must stay offline.
SQL Server 2016 July 14, 2026 Ended Upgrade in place or move the database; Extended Security Updates are the bridge, not the destination. Usually the line-of-business application decides the version.
Windows Server 2012 R2 (paid updates) October 13, 2026 Ending Support ended in 2023; the third and last year of paid Extended Security Updates ends on that date, and there is no fourth. Anything still on it gets rebuilt beside the old machine, not upgraded in place twice.
Windows Server 2016 January 12, 2027 Ending An upgrade path per server, not per fleet: in-place for the simple ones, a rebuild beside the old machine for the ones carrying a legacy application.
Windows Server 2019 January 9, 2029 Ending Time to plan rather than panic. Most of these get replaced with the hardware they run on, which is the cheaper order to do it in.

"Ended" means no more security fixes, not that the machine stops. A server or a desktop past its date is the first thing an inventory turns up and the first thing we quote. Moving one is a staged migration with the old machine kept running until the new one has earned trust — never a single-weekend job. The two server dates are worked through, server by server, in the Windows Server 2012 R2 and 2016 guide.

Texas

What is different about running IT in Texas

Four statutes and the weather. The first four narrow from every business down to local government; the last two apply to anyone with a server in the state. A provider from anywhere can patch a server; these are what the baseline has to be written against here.

Every business: two clocks after a breach

Business & Commerce Code §521.053: affected Texans are notified within 60 days of determining a breach occurred, and the Attorney General within 30 days when 250 or more Texans are affected. The Attorney General publishes every report it receives, so the second clock is also a reputation clock.

Under 250 employees: the SB 2610 safe harbor

Since September 1, 2025, a Texas business with fewer than 250 employees cannot be ordered to pay exemplary damages after a breach if it can show it had implemented and maintained a cybersecurity program conforming to a recognized framework — NIST CSF and the CIS Controls among them. The expected rigor scales with headcount, the program has to be yours, and it has to be in place before the breach, not written afterwards.

Selling cloud software to the state: TX-RAMP

Government Code §2054.0593: state agencies may only buy cloud services certified under TX-RAMP, run by the Department of Information Resources — Level 2 (moderate and high impact) required for contracts since January 1, 2022, Level 1 (low impact) since January 1, 2024. Both align to NIST SP 800-53, and a certification is valid three years. If your product runs on your own infrastructure, those controls land on your servers and your identity setup.

Cities, counties, and school districts

Government Code §2054.5191: local-government employees and officials who have access to a local-government system and use a computer for at least a quarter of their duties complete a DIR-certified cybersecurity course every year, and the government certifies completion to DIR. The parallel contractor rule, §2054.5192, binds state-agency contractors; a city can only write the same requirement into your contract.

The Gulf Coast: Beryl was only a Category 1

Hurricane Beryl made landfall on July 8, 2024 and cut power to about 2.2 million CenterPoint customers; 1.28 million were still without power two days later, and some waited more than a week. A server without a UPS, a shutdown script, and an off-site copy is a continuity plan that assumes good weather.

The whole grid: Uri was in February

Winter Storm Uri in February 2021 was not a storm surge but a generation failure: more than 4.5 million Texas customers lost power, some for four days, in the cold. The lesson is the same statewide — what has to keep working through an outage is decided before the forecast, and it is usually the mailbox, the files, and the logins, not the box under the desk.

Where we come to you

On-site as a matter of course: Houston, The Woodlands, Conroe, Sugar Land, Katy, Pearland, and the Greater Houston metro. Scheduled site visits: Dallas–Fort Worth, Austin, and San Antonio — each a day trip from Houston, planned for the work that needs hands rather than promised for the same afternoon. Remote, which is most of this work: everywhere else in Texas.

The statutes are summarized from their text, with dates and section numbers, so you can check them: Business & Commerce Code §521.053, Chapter 542 (SB 2610), and Government Code §2054.0593 and §2054.5191. None of it is legal advice: the baseline document goes to your counsel, who decides what it means for you. What the safe harbor asks of a company of forty, tier by tier, is in the guide on what Texas SB 2610 asks of a 40-person company. Selling software to Texas agencies yourself? The Contactio page covers how those bids are found; this page covers the infrastructure they will ask you about.

Two honest answers nobody puts on the page

The first: we are not a 24-hour network operations center, and we will not sell you one. What we are is the engineering half of IT: the cleanup, the migration, the network drawn and segmented, the printer fixed at the cause, followed by support during business hours from the people who set the systems up. If part of your operation genuinely needs a night shift, that part gets a provider with one, and we work beside them.

The second: most IT pain is a documentation problem wearing a hardware costume. The printer, the VPN, the account that still works a year after the resignation — each is a system with no drawing and nobody's name on it. Every engagement here ends with the documentation the estate never had, and you keep it whether the next call is to us or to nobody.

Where it pairs well

  • Mail or file shares moving between tenants, or a server moving into the cloud, is a legacy modernization and migration job — parallel run, reconciliation, rollback
  • The service account, the firewall rule, and the DNS record an interface needs are system integration seen from the infrastructure side
  • Once the platform is stable, the application on top of it gets the assessment-first treatment on the code rescue page
  • A brand-new company needs the domain, the mailboxes, and the laptops before it needs any of this — that is starting a business
  • When the answer is a small internal tool rather than another licence, that becomes custom software on the same terms
  • How your admin credentials and data are handled, and the NIST CSF 2.0 practice this baseline is built on, is written down on the confidentiality page
  • Label printers, scanners, and the Wi-Fi they ride on are part of the warehouse floor on the 3PL and warehouse software page, which is where most of our printer work started
  • The case studies include eight warehouse label printers that stopped locking up and a kiosk fleet kept alive through Intune

Your accounts, your passwords

Admin logins live in a password manager you own. We are a collaborator you can remove in a minute, and the offboarding checklist applies to us too.

A diagram before a quote

The first deliverable is the network drawn, the assets listed, and the identity estate counted — a map you keep whether or not the next step is us.

Fixed at the cause

A printer that needs a weekly reboot is not fixed. We find the cause, fix that, and write down what it was.

Support you can leave

A retainer with the response time in writing and an exit that hands back access and documentation. The runbooks are written so your next hire can run them.

Toolkit

What we work in

Vendor-neutral where the job allows it. If your firewall or hypervisor is not listed, ask — the list is what we have worked in lately, not a boundary.

Active Directory Entra ID (formerly Azure AD) Entra Connect & hybrid join Group Policy PowerShell Intune & Autopilot Windows 11 Windows Server Hyper-V VMware Proxmox Microsoft 365 Exchange Online SharePoint & OneDrive Google Workspace Conditional Access & MFA BitLocker Defender for Endpoint Fortinet SonicWall Meraki Ubiquiti UniFi pfSense & OPNsense VLANs & 802.1X IPsec & WireGuard VPN DNS & DHCP Veeam Immutable & off-site backup UPS & generator transfer Print servers & Universal Print ZPL label printers Password managers RMM & ticketing NIST CSF 2.0 CIS Controls Network diagrams & runbooks
Questions we get

Straight answers

Are you a managed service provider?

In the co-managed and project sense, yes; in the sense of a staffed 24-hour desk, no — and we would rather say that than sell it. What we run is project and co-managed IT: the cleanup, the migration, the network that finally gets drawn, the printer fixed at the cause — and then a retainer, with a response time in writing during business hours, for the systems we set up. If your operation needs someone awake at 3am every night, you need a provider with a night shift; we will say which parts of your estate genuinely do, and we work next to plenty of them.

Why does our network printer keep going offline?

Usually it is addressing, not hardware. The printer took its address from DHCP, the lease changed over the weekend, and every PC's queue still points at the old one — or Windows added it as a WSD device, which finds the printer by broadcast and loses it whenever the printer sleeps. The fix is a reserved address, a standard TCP/IP port, one driver deployed from a print server, and power settings that leave the network interface awake. A reboot fixes it too, which is exactly why it has never been fixed. Most of this is done remotely; the copier's own hardware stays with the copier dealer.

Who looks after Active Directory when the one person who knew it leaves?

Whoever inherits the domain admin password, which is the problem. Start with an inventory rather than a hire: every enabled account, every group, every Group Policy object and what it actually changes, every service account and which application breaks if it is disabled. Most domains we read have accounts for people who left years ago and policies that cancel each other out. Once that map exists, the day-to-day is a short runbook a generalist can follow, and the parts that need an expert are the parts we keep on a retainer.

Should we still run on-premises Active Directory, or go Entra ID only?

It depends on what is on the floor. If the estate is laptops, browsers, and Microsoft 365, cloud-only Entra ID with Intune is simpler and cheaper to run. If you have file servers, a line-of-business application that authenticates against the domain, warehouse scanners, or a print server, on-premises Active Directory stays and Entra Connect joins the two — most mid-sized estates we see are hybrid for exactly that reason. The decision is made by an inventory of what authenticates where, so that is what we produce first.

Windows 10 is out of support. What happens to the machines that cannot run Windows 11?

They keep booting and stop receiving security fixes; support ended on October 14, 2025. A business can buy Extended Security Updates a year at a time for up to three years, which is a bridge rather than a plan. We put every machine on one list — passes the Windows 11 check, needs a firmware setting changed to pass, or is genuinely too old — and the refresh gets budgeted from that list instead of from a guess. Microsoft 365 Apps keep getting security updates on Windows 10 until October 10, 2028, which buys time for the replacement schedule, not a reason to skip it.

What does Texas law actually expect of a small business's cybersecurity?

Two things worth knowing, stated as the statutes read rather than as legal advice. Since September 1, 2025, Senate Bill 2610 shields a business with fewer than 250 employees from exemplary damages after a breach if it can show it maintained a cybersecurity program conforming to a recognized framework — NIST CSF or the CIS Controls among them — with the expected rigor scaling by headcount. And Business & Commerce Code §521.053 sets the clocks after a breach: affected Texans within 60 days, the Attorney General within 30 when 250 or more are affected. The baseline we build is written against those two, and the document goes to your lawyer as well as your IT closet.

Is NIST CSF 2.0 a certification you hold?

No — NIST does not certify anyone against it. The Cybersecurity Framework is something an organization adopts, not an audit it passes; a 'NIST CSF certificate' is a private assessor's attestation, not a standing with NIST. We run our own practice on CSF 2.0 and say exactly that on our confidentiality page. For a client, the baseline we write uses the 56 safeguards of CIS Controls Implementation Group 1 as the floor for a company under a hundred people, and maps to CSF 2.0 for larger ones; that is also the shape SB 2610 asks a program to take. If a customer or insurer wants an audited attestation, that is a SOC 2 engagement with an auditor, and we help you prepare for it rather than pretend to be one.

How do we keep working when the power is out for a week?

By deciding in advance which things must survive an outage and which just need to come back cleanly. Mail, files, and identity in Microsoft 365 mean a dark office is not a dark business — people work from wherever has power. The on-premises servers get a UPS sized to run a clean shutdown script, not to keep the lights on, and a generator transfer that has been tested under load. Backups go off-site and immutable, and the restore has been rehearsed with a stopwatch. Beryl in 2024 and Winter Storm Uri in 2021 both proved the same thing: the plan has to exist before the forecast does.

Do you come on-site outside Houston?

Yes, on a schedule. We are based in Houston and on-site across the Greater Houston metro as a matter of course, warehouses included. Dallas–Fort Worth is about three and a half hours up I-45, and Austin and San Antonio are similar trips west. A visit there is a day we plan for the work that needs hands — a rack, a Wi-Fi survey, a cutover weekend — rather than a same-day promise. Most of the rest — identity, Microsoft 365, patching, monitoring, the help desk — is remote work wherever the office is, and we do it for companies across Texas.

What does IT support cost, and how is it quoted?

Without a number, because every honest one depends on the count: how many people and machines, how many sites, which hours are covered, how much security tooling and documentation you need, and how much cleanup the estate needs before anyone can support it. So it is quoted in that order. The inventory and diagram come first, at a fixed price. Each project they turn up is quoted at a fixed price too. Ongoing support is a monthly retainer sized to headcount and device count, and you can end it. What you will not get is a flat monthly figure with nothing behind it.

We already have an IT company. What would you add?

Usually the problems that fall between the software vendor and the IT provider: the printer the provider calls a software issue and the vendor calls a network issue, the integration waiting on a service account nobody will create, the Active Directory cleanup that keeps slipping behind the ticket queue. We take those as scoped projects, write up what we did, and hand it back. If the relationship is working we make it easier; if it is not, an assessment says so with specifics rather than a pitch.

Guides

Guides written from the same tickets

The problems this page gets called about most, each answered in full: what is actually happening, the settings or the order of work, and when it is worth a call. Every one links back to the row above that does the work.

Printers, Scanners & Peripherals

Why a network printer keeps going offline in the office, and the four settings that fix it

Usually addressing, not hardware: a reserved address, a standard TCP/IP port, one driver from one place, and power settings that leave the network interface awake.

Read the guide →
Servers, Virtualization & Backup

Windows Server 2012 R2 gets its last updates on October 13, 2026 and 2016 on January 12, 2027: the per-server decision

Two deadlines four months apart, and a decision that is made one server at a time: in place, rebuilt beside the old one, or retired with the share that moved.

Read the guide →
Active Directory & Entra ID

Your only IT person quit. What to lock down in the first 48 hours

Nothing needs rebuilding today. The order of work for two days: the accounts that own everything, the leaver's own access, what would break next, and what to write down.

Read the guide →
Active Directory & Entra ID

Hybrid Active Directory or Entra ID only: the inventory that decides it

The decision is not a preference. It is a list of what authenticates where, and the list usually says hybrid for now and cloud-only for the next fleet.

Read the guide →
Security Baseline, Documentation & Vendors

What Texas SB 2610 actually asks of a 40-person company

The safe harbor is earned before the breach, in writing. Where a 40-person company lands in the tiers, what CIS Controls Implementation Group 1 is in practice, and what evidence looks like.

Read the guide →
Printers, Scanners & Peripherals

Shared printers and scan-to-folder vanished after a Windows 11 update: SMB signing, guest access, and KB5065426

Three different failures with one symptom: SMB signing now required, guest access refused on Pro, and cloned PCs refusing each other after KB5065426. Each is fixed on the device, not by weakening the PCs.

Read the guide →
Servers, Virtualization & Backup

A hurricane-season IT checklist for a Houston office

The office rarely floods; it goes dark. What to decide before June 1, what the server closet needs, which backups have to leave the building, and what to check the morning after.

Read the guide →
Networks, Firewalls & Wi-Fi

Why the Wi-Fi drops in the warehouse and not in the front office

Same access points, different building: racking, inventory that changes height, and scanners roaming at forklift speed. The five causes in the order they turn up, and what a survey actually produces.

Read the guide →
Active Directory & Entra ID

The only domain controller died. What still works, what doesn't, and the order to bring it back

Cached sign-ins keep working for a while; DNS stops at once. What runs, what stops, restore or rebuild, and the order to bring it back, then the second one so it never repeats.

Read the guide →
Get in touch

Name the device you reboot, or the date on your calendar.

The printer, the VPN, the server under the desk — or the support date coming up — and roughly what the office runs on. You get back what we would look at first, what an inventory of the whole estate would involve, and whether it needs a site visit or a remote session.

Prefer to talk?

Call 832-598-8234 or email msco@stoneagesoftware.com. Houston, Texas — serving Houston, The Woodlands, Conroe, Sugar Land, Katy, Pearland, and the Greater Houston metro.

What happens next

We read your message, an engineer replies with questions or a straight answer, and if it's worth a call we book one. No drip campaign, no handoff to sales.

No obligation — we reply within one business day. This form sends your details to Stone Age Software LLC so we can respond to you. See our privacy policy for how we handle them. This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.