An IT Distributor’s Services Division Used a Files.com Custom Domain to Unblock Uploads and Retire Legacy FTP

A global IT distributor, a Fortune 500 company, connects thousands of technology vendors to customers worldwide. Its technology lifecycle services division is the arm that hardware manufacturers hire to deliver field service, depot repair, and technical support on their behalf, for equipment spanning data centers, broadband, medical devices, and semiconductor manufacturing.

That business model puts the services division one step removed from everyone it serves. The equipment belongs to an OEM's end customer. The support relationship belongs to the OEM. The division does the work, all over the world, and nearly every case begins the same way: the end customer sends in logs and sensitive system information so an engineer can diagnose the problem. Every engagement depends on a file arriving from an environment the division does not control.

Support Cases That Stalled at Intake

Several of the division's end customers run corporate security policies that block third-party file-sharing domains. When the division asked one of those customers to upload logs to a file-sharing URL, the customer's own network refused it. The files that would let an engineer start work could not arrive, so the case stalled at intake: the diagnosis waited until the files could arrive.

Alongside those blocked links, the division ran a legacy customer-facing FTP site where end customers sent in the same material. That kept some uploads moving, but it was a second, older intake path to operate, and it did not present the corporate identity that the blocked customers' policies demanded any more than the file-sharing links did.

The Policy Was Not the Division's to Change

The blocked domains were not a misconfiguration the division could ask its customers to fix. Those policies exist for good reasons, and asking each blocked customer's IT department for an exception, account by account, while broken equipment waits, is not a repeatable process for a business serving end customers worldwide.

The durable fix had to work with the policy rather than around it. Uploads had to land at an address that reads as the distributor because it is the distributor: served from the company's own domain, branded as the services division, safe for sensitive system data, and dependable enough that the legacy FTP route could be retired behind it. A generic file-sharing URL can never be that, whoever the vendor is.

Files.com Under the Distributor's Own Domain

The approach came out of an in-person session with Files.com's technical team, where the conversation turned to branding the site and putting it on the company's own domain name.

The division put a Files.com custom domain in front of its upload portal, on the distributor's own domain name. The address bar reads as the distributor. The pages carry the division's branding. To an end customer's security policy, an upload to that address is traffic to the distributor, because it is. There is no third-party file-sharing domain left to block. Behind the domain, Files.com folder permissions and password-protected folders keep each customer's uploads where they belong.

The cutover was staged rather than assumed. The division ran a proof of concept on the custom domain, tested it with real customer uploads, and only then retired the legacy FTP route.

Uploads Arrive, and the FTP Site Is Gone

With the custom domain in production, the division replaced two intake routes, one blocked and one legacy, with a single upload portal that reads as the distributor end to end.

• End customers whose security policies block third-party file-sharing domains now send logs and sensitive system information straight to the division. The block never fires, because the address they reach belongs to the distributor.
• The fix covers every such customer at once. There is no exception to negotiate per account, and the next customer with the same policy needs nothing from the division but the URL.
• The legacy customer-facing FTP site is retired. Customer intake runs through one governed path, with folder permissions deciding who reaches what.

The first result unblocks the work in front of them: a case that used to stall at intake now starts with the files already in hand. The second is the one that compounds. Serving uploads from its own domain settled the question for the division's whole customer base rather than for one account, and it stays settled as new customers arrive.

One Address, Every Customer

The division did not persuade its customers to trust a file-sharing vendor. It made the question disappear: the portal runs on Files.com, and the domain it runs under is the distributor's own. For a services business whose customers' security policies block the upload path, that is the fix that scales. Not an exception per customer, but an address that works with their policy.