@george1421 According to the documentation, it happens at startup. So the pass would be, as follows.

During the initial boot deploy the profile, and run it or restart. Upon successful deploy and join to MDM (Airwatch, or Hexnode) delete the provisioning profile

I am not currently running Fog. Our current computers are Macs with dual boot, so I deploy Naked Windows with provisioning profile set to execute and enroll into MDM. Then MDM deploys all of the software and compliance policies.

It was decided that OS X is not cost effective in the situations where students are not likely to run OS X. My goal moving forward is to avoid building thick images, for entire fleet, and do provisioning instead. I am very surprised that Provisioning is not as widespread as it should be.

I am all ears regarding possible Fog scenario

So lets start with OS X

In OSX environments we use the following workflow

Prior to IMAC Pro

1. Create basic image with MDM client baked in (Jamf for example)
2. Load the package into Deploy Studio, Imagr or Casper Imaging or Fog Project
3. Netbook the station, deploy the OS package without any software
4. Let MDM do the rest, create user, make configuration profiles

Post Imac Pro

1. Setup DEP with MDM link and erase the station.
2. Let MDM do the rest, create user, make configuration profiles

Windows

On windows the same thing is harder to accomplish
Provisioning profile is not zero touch, it has to be loaded on USB, or station needs to be started and then you can run provision profile. For 200 stations is ok, but when you deal with MASIVE 10K deployments this is not feasible.

There are couple of things that can happen.

• Enrollment into Autopilot, but you need to use AzureAD + MDM (costs skyrocket)
• Airwatch MDM can handle Dell provisioning, HP is coming soon (but you are locked)
• USB or manual enrollment (but will take more user interaction)
• SCCM+Intune (costs are high)
• Fog Project + Image per each configuration (high costs at image creation, you will need to create different sets of drivers and etc)

There is a folder in Windows 10, that is scanned during startup for provisioning profiles. So here is my idea… If it is possible

USE PXE Boot Sequence

Copy provisioning profile to the folder on C drive where the provisioning profiles need to be placed so they are ran on the next boot. The Provisioning Profile would kick on the next boot sequence, and install MDM Agent (Airwatch, Hexnode etc). The MDM would push software to the client station. This would create much lenient system for deploying, removing need for imaging one of the large costs in IT infrastructure…

Hello:

I am trying to figure out if it possible to use Fog to provision windows 10 machines instead of imaging. The idea is as follows. There is a folder on Windows 10 that host provisioning packages that will run upon boot and install Airwatch agent, and then station gets provisionioned with all software that is needed.

I can use USB stick with provisioning package that will surpress all of the dialogs upon boot. What I am trying to find out if I can do the same with PXE

So goal is like this
Brand machine out of the box

1. Boot PXE
2. Select one of the booting workflows
3. Workflow will copy correct provisioning package to the local folder of the machine that is booting
4. System is restarting and the provisioning package is getting deployed.