Windows Autopilot - Initial Setup | IT Partner

IT Partner

Building a future with Microsoft Cloud Technologies

Windows Autopilot - Initial Setup

category by product:
category by type:
  • Duration: 3 weeks;
  • Price: $1950;
  • SKU: ITPWW290IMPOT;

 , , ,

We will plan, design and implement a Windows Autopilot – the future of device deployment designed to allow you to setup, pre-configure and repurpose the devices for your environment, with little or no infrastructure in place. You would be able to deploy Windows automatically, without an image, to PCs anywhere in the world at anytime.

  1. IT Partner responsibilities:
  2. Client responsibilities:
  3. Prerequisites :
  4. Additional cost items not provided by the project:
  5. Plan:
  6. Success criteria

Windows AutoPilot is a cloud-based deployment technology available in Windows 10. It allows to deploy and configure devices over the internet with no interaction as an administrator or IT-specialist. It is built on existing modern management technologies like Azure Active Directory and Mobile Device Management to manage and configure devices by their automatically enrolling in these solutions at their first bootup, right out of the box.

Deployment of devices with Windows Autopilot enables a number of capabilities for the deployment process and configuration of the devices deployed. These features transform the way that devices are deployed by enabling customization of the first boot experience and providing automated configuration of deployed devices. Windows Autopilot also enables benefits from modern management solutions, such as:
  • Presenting organization branding to users at the first prompt to log in via organization branding configured in AAD
  • Automatic enrollment in Microsoft Intune or an alternate MDM solution with the configuration of automatic enrollment in AAD
  • Device configuration, policies, and apps defined by Intune or an alternate MDM solution begin applying to a device immediately upon the first logon, setting up the device for the user to begin working with and using the device

Our objective is devices being configured and ready to work for your users without requiring reconfiguration of the devices, access to on-network resources, or even physical presence in your organization’s buildings or offices.

IT Partner responsibilities:

Please note: We do not require administrative access to the customers AAD or MDM environment to register devices.

  1. Kickoff Meeting.
  2. Creating a project plan and schedule.
  3. Communication with hardware provider to obtain the necessary information.
  4. One-time purchase or DaaS model.
  5. Collecting the hardware IDs from the existing devices.
  6. Configuration of Autopilot profiles and profile settings.
  7. User assignment to the specific Autopilot-enabled devices.
  8. Escalation of issues to Microsoft support, if needed.
  9. Client advice on implementation issues.
  10. Project Closure and Acceptance.

Client responsibilities:

  1. Coordinate Client resources and staff schedules.
  2. Provide a dedicated point of contact responsible for working with IT Partner.
  3. Coordinate any outside vendor resources and schedules.
  4. Configure all network equipment, if necessary, such as load balancers, routers, firewalls, and switches.
  5. Review and approve engagement deliverables in a timely manner.
  6. Request and approve all change management tickets (if available) in the Client environment.
  7. Provide access to physical and virtual servers as needed. Provide necessary remote and/or physical access to the facility and systems needed in order to complete the work.
  8. Unbox new devices, plug them in and turn them on, connect them to a wireless or wired network with internet access.
  9. Provide information about PC setup requirements and software requirements.
  10. Resolution of basic tickets which may be resolved by following end-user adoption instructions provided by Microsoft is the Client’s responsibility.
  11. End-user support

Prerequisites :

  1. One of the following subscriptions provisioned in to your Azure AD tenant:
    1. Enterprise Management and Security (EM+S) (E3 or E5) – includes Azure Active Directory Premium and Microsoft Intune or
    2. Microsoft 365 Enterprise (E3 or E5) – includes Enterprise Management and Security, Azure Active Directory Premium, Microsoft Intune, and Office 365 ProPlus or
    3. Microsoft 365 Business – (excluding Office 365 Business which can’t be configured by Windows Autopilot – Office ProPlus is required for that) and a select set of Azure Active Directory Premium and Microsoft Intune features.
  2. Sufficient rights to the Azure portal.
  3. Intune service, or another MDM solution, to manage devices.
  4. Sufficient rights for the Windows Store for Business.
  1. The devices used for Autopilot should be supported by Microsoft for Windows Autopilot.
  2. Windows 10 version 1809 or higher is required.
  3. The following editions are supported:
    • Windows 10 Pro
    • Windows 10 Pro Education
    • Windows 10 Pro for Workstations
    • Windows 10 Enterprise.
    • Windows 10 Education.
    • Windows 10 Enterprise 2019 LTSC.
  4. Network configuration must match the requirements listed on Microsoft Web Site – https://docs.microsoft.com/en-us/windows/deployment/windows-autopilot/windows-autopilot-requirements-network

Additional cost items not provided by the project:

  • Microsoft Intune implementation – please check this service: Microsoft Intune – Initial Setup.
  • Migration of local documents and data from current devices (migration to OneDrive or SharePoint may be included additional to this project, if desired).
  • Windows 10 upgrade is outside of the scope and could be performed as a separate project.
  • Support for existing Windows 7 and Windows 8 devices.
  • Installation of firmware on desktops or network hardware devices.
  • End-user teams Training.
  • The IT Partner team will perform all the work remotely. The on-site presence may be arranged by request and will be invoiced separately at the rate of $1,900 per business day.
  • Hardware, software and Office 365/Azure subscription costs that may be required to complete this engagement are not included in this Statement of Work.
  • Any items not specifically mentioned as in scope.
  • Upon completion of the project, we will provide a project closeout report. This document will indicate the final project status including evidence of matching acceptance criteria, outstanding issues and the final budget. If you require more extensive documentation, it can be provided for an additional fee.  

Plan:

The plan may vary depending on your needs.
  1. Kickoff meeting.
  2. Project schedule review and revisions.
  3. Planning and developing.
  4. Interaction with hardware provider.
  5. Collecting existing device information.
  6. Creating and managing Autopilot profiles.
  7. Test device deployment and lifecycle.
  8. Production deployment monitoring.
  9. Possible problem-solving.
  10. Providing the use case documentation.

Success criteria

  1. Implementation plan developed and approved.
  2. Client’s Office 365 tenant and Azure services configured to support Windows Autopilot functionality.
  3. Windows Autopilot can be used to deploy, repurpose, break-fix, and retire all the supported devices configured for the Autopilot service.
  4. One month of post-implementation consulting and support period started.