So, recently a customer installed the Intune client in an image, as my previous post details, causing the client to enter a bricked state.
Reinstallation of the client can fix this, but we wanted minimum user interaction as a large number of machines was already distributed.
For those who remember Winrar, it is a fantastic ZIP tool that can create a self-extracting archive (.EXE) which auto-self elevates (admin rights) and can automatically start a file from the archive after extraction.
Include the Intune setup file and the certificate Microsoft includes, and this script (as .bat), and your Intune installation will be ‘cleaned up’. Note that you may see some file protection dialogs.
This script is an addition to O365Datacleaner and will allow you to run the original script over many target locations simultaneously, using a CSV file as input.
This is the simplest and most reliable method currently available to make, for example, all the data on your fileservers spread out over homedirectories completely compliant with Onedrive for Business or Sharepoint Online’s requirements.
In organisations that have moved to Office 365, or are moving to Office 365 while using a hybrid setup with an on-premises Exchange 2010, 2013 or 2016 server and/or Lync/Skype, your helpdesk tools and scripts need to be adjusted.
While previously, you would provision your account in Active Directory, the mailbox on the onpremises Exchange Server and voip functionality on the Lync/Skype server, after your migration, you no longer need to provision mailboxes or lync accounts on premises. After a user has been migrated to Office 365, his ‘user type’ in the Exchange on premises server is ‘Remote Mailbox’. But for new users, this is not set automatically.
If you’re using scripting or tools like ADManager, you can use some simple Powershell commands to set the correct properties on a newly created user.