Monthly Email Newsletter curated by our Top Editors
Part 4 – Time Frame of Endpoint Readiness
Introduction
In the previous post, we covered all of the elements which would build on the overall user experience in which the user would see when it comes to the configuration of their new endpoint and get it prepared to be in a usable state where the allocated user can hit the ground running.
With all of this being said, we now want to focus on an additional part of this process which is primarily around the time frame in which an endpoint is ready. See, the time it takes for a device to be company-standard ready plays a very important part in the overall user experience. No user wants to wait for their device to finish building and not be able to do anything. Not only this, but it would also reflect badly overall to the appointed technician, IT department, and more further up the chain the more this issue occurs.
Part 3 – User Experience
Introduction
In the previous blog post, we went into detail about how and where we define the use and purpose of the Autopilot approach. We talked about whether to use the pre-provisioning (White Glove) vs. the normal method of Autopilot.
Now with that being established we want to dive into the user experience. We want to understand how we can approach and tailor the user experience so that the process is efficient. Let’s follow the instructions on how to setup and access your new managed device.
In a previous blog I explained how to deploy a .msi application with Intune. In this blog let me describe the next cool MEM feature – Win32 application deployment.
Intune supports Win32 x86 and x64 applications meaning you can deploy, from Intune, any application like Adobe Reader, Google Chrome, 7-zip, etc. You can deploy from a command line in silent mode. You just need to know parameters for .exe or .msu for silent installation.
Part 2 – Purpose of Autopilot Profile
Introduction
So with the first part we went into the differences of paths when choosing a method of which way we want to proceed, whether that is a standard Autopilot profile deployment or if we want to use the white glove version of this process to move forward.
While that covered a lot of foundational ground, with this part, we want to dive into another area of interest. This will help our decision making and that stems around the purpose of the autopilot profile we are using or trying to create. Knowing exactly what we want to achieve with it, and how it will be constructed, will also play a factor in how we want our approach to be.
