Request a quote
Emergency SectorsCareers About us Blog Get in touch
Technician unpacking a new laptop at a desk with a monitor and cardboard boxes, with canal houses outside the window

Zero touch provisioning: a device that sets itself up, and what has to be right first

Zero touch provisioning means a laptop, switch or access point goes straight from the supplier to where it will be used and enrols and configures itself the first time it is switched on. It only works if the chain behind it is right: who registers the serial number, where the device checks in and what it needs from the network to do so. That is what this article covers, not the policies you apply afterwards.

8 min read Written by the ITproposal team
Short answer

Zero touch provisioning starts at purchase, not at the device: the serial number must already be linked to your organisation before the box leaves the warehouse.

A laptop checks in with an enrolment service run by the operating system vendor; a switch or access point fetches its configuration over the network or checks in with a cloud controller. Both need a working connection on first boot.

End of life is part of it: a device that is never deregistered stays tied to your organisation and is useless to whoever owns it next.

What zero touch provisioning is, and what it is not

With zero touch provisioning, no engineer handles the device before the user has it. The laptop goes in its box to the employee’s home, the switch to the branch, and on first power-on the device knows who it belongs to and where to fetch its configuration.

It is not a way of configuring but a way of starting. What ends up on the device afterwards, the policies, the software, the settings, is set in your management platform, and that is a separate subject. Zero touch solves one thing: there is no manual work left between the factory and the user.

That is why it applies to two very different kinds of device, and why searches for it cover both:

  • End-user devices: laptops, tablets and phones, through the enrolment services from Microsoft (Windows Autopilot), Apple (Apple Business Manager) and Google (Android zero-touch enrolment).
  • Network equipment: switches, access points, firewalls and routers, which fetch a configuration on first boot or check in with a cloud controller.

The chain before first power-on

Zero touch is a chain of four links, and a rollout stalls on the weakest one.

  • Registration at purchase. The reseller or manufacturer links the serial number (for Windows, the hardware identity) to your organisation in the enrolment service. Only a reseller you have authorised can do that. Buy a device on its own from a web shop and that step is missing, so someone has to do it by hand afterwards.
  • Assignment to a profile. In your management platform the device is attached to a profile: which type of user, which department, which language. A device without a profile starts like any consumer device.
  • A working connection on first boot. The device has to reach the internet to find out who it belongs to.
  • The right user or site. A laptop is signed into by the employee with their own account; a switch needs the cloud controller to know which site it belongs to.

So the first question to ask is: who registers the devices at purchase, and how can you see it has been done before they ship? A list of serial numbers showing in your management platform before the boxes leave is the only proof that counts.

Laptops: what the user sees when unboxing

The employee switches the laptop on, picks a wifi network, signs in with their work account and waits. During that wait the device pulls down policies, security settings and the required software. How long it takes depends mostly on how much has to be installed before the desktop appears. A long list makes the first fifteen minutes slow and fragile; keep it to what is needed from the first minute.

Two choices to make in advance:

  • Done entirely by the user, or pre-provisioned. With a slow home connection or a heavy build, a supplier can run most of the setup in the warehouse so that the user only completes their own part. That still involves no manual configuration, but someone does open the box.
  • What happens if it fails halfway. A user who gets stuck at home calls the service desk. Make sure the desk can see remotely which step the device is on, and that there is a way to start again without the laptop being sent back.

How to build the workplace itself so that zero touch makes sense is covered in our article on standardising the Windows workplace.

Switches and access points: zero touch at a new site

For network equipment, zero touch provisioning has the same name but works differently. There are broadly two routes:

  • Fetching a configuration over the local network. On first boot the device gets an address via DHCP along with the location of a configuration file or script, and downloads it. That needs a working DHCP server and a reachable configuration server at the site or behind it.
  • Checking in with a cloud controller. The device is linked to your management platform by serial number, calls out on first boot and receives its configuration from there. That only needs an outbound internet connection, which is why it is the usual route for branches with no IT staff on site.

The chicken-and-egg problem sits in the first switch. An access point can only check in once the switch above it works, and the switch only once the router or firewall provides the connection out. So plan the order: the outbound connection first, then the core switch, then the rest. And make sure the port a new device comes up on sits in a network segment that is allowed out; a port that only carries the guest network or an isolated segment leaves a new switch waiting forever.

On site, someone then only does what a person has to do: mount it, plug cables into the right ports, power it up. A fitter with no networking knowledge can do that, provided a port plan comes in the box.

Where zero touch gets stuck in practice

Most failed zero touch rollouts do not fail on the technology but on one of these five:

  • Not registered. The device was bought through another channel, or the reseller had no authorisation. It then starts as a blank device.
  • A connection that asks for something first. A hotel network or guest wifi with a sign-in page, or a proxy the device does not know, silently blocks the first step.
  • Old factory firmware or software. A switch that sat on a shelf for months may carry a version the cloud controller no longer accepts, and a laptop has to update before the rest arrives.
  • The wrong profile. A field engineer’s laptop gets the office build, or a switch lands on the wrong site. This is admin, and it is the most common mistake.
  • Dead on arrival. A device that arrives faulty is only noticed when the user switches it on. Agree how quickly a replacement arrives, because there is no engineer standing next to it.

A small pilot before the main rollout catches the first four: ten devices, at the real sites and on real home connections, not on IT’s test bench.

End of life: deregistering is part of the job

A registered device stays linked to your organisation after it has been wiped. That is the security benefit: a stolen laptop that is reset checks in with you again. But it also means that a device you sell, donate or return must first be removed from the registration. If it is not, the next owner is stuck with an organisation they do not know, and the refurbisher receives a device they cannot use.

So put deregistration in your disposal procedure, next to data wiping, and ask your supplier how it is handled for returns and warranty swaps. A replacement unit from a warranty swap has to be registered in turn; otherwise the first repair is also the end of zero touch for that device.

Five questions for your supplier

  • Can you link devices to our organisation at purchase, for laptops and network equipment alike, and how do we see that it has been done?
  • What authorisation do you need from us for that, and can we revoke it ourselves?
  • What do you do when a device does not check in: who contacts the user or the site, and how quickly is there a replacement?
  • Do you pre-provision heavy builds, and if so, what still happens in the warehouse?
  • How do you deregister devices on return, warranty swap and disposal, and do we get confirmation?

A supplier with no concrete answer to the first and last questions is delivering devices, not zero touch.

Where our work stops

What we do. We supply laptops and network equipment, register them to your organisation at purchase where the manufacturer allows it, prepare the profile and configuration, ship directly to the user or site, and handle the on-site work ourselves, with our own local engineers in every country. On disposal and warranty swaps, we deregister.

What we do not do. The management platform, the tenant and the enrolment accounts remain your organisation’s; we work in them with the rights you grant, and you can revoke those. We are not the manufacturer: whether a device supports zero touch and what warranty it carries is up to the manufacturer. And the internet connection at a site comes from an operator or network provider; we advise on and supply the connection, but the infrastructure underneath is theirs.

Frequently asked

Questions we get about this

The five that come up most often.

What is zero touch provisioning?

Zero touch provisioning is a way of putting devices into service without manual work. The serial number is linked to your organisation at purchase, and on first power-on the device enrols itself and fetches its configuration. It works for laptops, tablets and phones as well as network equipment such as switches and access points.

What is the difference between zero touch provisioning and zero touch deployment?

In practice the two terms are used interchangeably. Provisioning is more common for network equipment that fetches a configuration, deployment for laptops that set themselves up. The principle is the same: no engineer between the factory and the user.

Can existing laptops be set up with zero touch?

Yes, but not without registering them first and usually wiping them. A laptop already in use has to be added to your management platform and then reset. For devices due for replacement soon, it is often simpler to wait for the new ones.

What does a switch need to configure itself?

A working connection on first boot. With a cloud controller that means an outbound internet connection; with configuration over the local network, a DHCP server and a reachable configuration server. The equipment upstream, router or firewall and core switch, therefore has to work first.

Do I need to deregister a device before selling it?

Yes. A registered device stays linked to your organisation after wiping and will check in with you again for its next owner. Make deregistration a fixed step in your procedure for disposal, returns and warranty swaps, alongside data wiping.

Related services

Further reading

What zero touch connects to.

Brands

The brands above, one page each

What the brand makes, which lines we supply and what we do around it.

Shall we plan your next rollout with no manual work?

Tell us how many devices, at which sites and what is already registered. We will tell you which link in the chain is still missing.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call