I’m not as familiar with hybrid join. My district went straight from AD to AAD. I don’t believe there is a way to go back to the out of box experience after you provision the device. I would either push the apps through intune after the fact, or when creating your provision package add the app installs to the provision package.
I’m not as familiar with hybrid join. My district went straight from AD to AAD. I don’t believe there is a way to go back to the out of box experience after you provision the device. I would either push the apps through intune after the fact, or when creating your provision package add the app installs to the provision package.
Yes, but whenever you create and add the provision package in the next step on my article, it automates the setup.
You may be able to create the provision with only the script to get your desired experience, but then you will need to finish the setup manually and domain join it manually.
I’m not as familiar with hybrid join. My district went straight from AD to AAD. I don’t believe there is a way to go back to the out of box experience after you provision the device. I would either push the apps through intune after the fact, or when creating your provision package add the app installs to the provision package.
But here in the last step it said that after reboot OOBE will start
https://github.com/tabs-not-spaces/Intune.USB.Creator
This is not possible because we have a connection to the local domain through Intune so we must have OOBE.
Yes, but whenever you create and add the provision package in the next step on my article, it automates the setup.
You may be able to create the provision with only the script to get your desired experience, but then you will need to finish the setup manually and domain join it manually.