I recently ran into an article by Pieter Wigleven, based on an original idea of Jan Van Meirvenne that I simply have to share, and expand upon.
When you go cloud first, and do light MDM management of your Azure AD Joined Windows 10 devices, you will likely enable a Bitlocker policy in Intune. What you’ll quickly discover, is that your policy will not automatically enforce/enable Bitlocker on non-InstantGo capable devices.
So, I expanded upon Jan and Pieter’s script to automatically enable Bitlocker on Windows 10; it has additional error handling, local logging and it will eject removable drives prior to immediately (vs reboot) encrypting your system drive. After this is started, it will register your recovery key in AzureAD. Of course all credit for the original idea goes to Jan van Meirvenne.
Powershell source file
enableBitlockerAndRegisterInAAD.ps1 (right click, save as)
enableBitlockerAndRegisterInAAD_v0.2.msi(right click, save as)
As Intune won’t let you deploy a Powershell script, I’ve also wrapped the script in an MSI file with Advanced Installer for you. What this will do;
- Deploy the PS1 file to the machine
- Register a scheduled task to run this PS1 file at logon each time
- Kick off the scheduled task once so a first reboot isn’t required
Advanced installer package (.aip)
enableBitlockerAndRegisterInAAD.zip (right click, save as)
- Windows 10, AzureAD Joined
- TPM chip
- User should be local admin
Onedrive for Business’s client, the new Next Generation Sync client, is awesome. Obviously.
So you want it on your devices, but Microsoft distributes it as .exe. Nasty, because I want to manage Windows 10 as mobile devices through Intune, and that only allowes me to distribute as MSI.
I created an MSI for Onedrive for Business’s Next Generation Client using Advanced Installer. Because I’m not allowed to redistribute Microsoft’s .exe, this MSI downloads the .exe from Microsoft’s website, it uses /silent and /takeover as installation switches. Continue reading Deploying the new Onedrive Next Generation Sync client as MSI through Intune to Windows 10
Considering to move to an Anywhere, Anyplace, Anytime lightweight IT environment? Throwing out all local IT?
No more Domain Services, just AzureAD? Windows10, or any other mobile modern client? Here’s a short checklist I sometimes use for clients when assessing their intentions / plan:
- Intune tenant created and policies have been set, including Conditional Access
- All my non single MSI applications I want to deploy to my clients have been repackaged
- All my application servers/services have been moved to SaaS or to RemoteApp or the like
- My identities have been synchronized or copied to Azure AD
- All users have an Intune or EMS license
- I have enabled Azure AD automatic MDM enrollment
- I have enabled Enterprise State Roaming in Azure AD
- I have published my internal web sites using Azure Application Proxy and added these sites to Intune as Apps
- DLP policies have been setup for any sensitive data types/locations in my company
- Personal data has been migrated to Onedrive for Business
- Group data has been moved to Office 365 Groups or Sharepoint Online
Just to get you started! 🙂
So, a while back Intune got the ability to deploy native MSI’s to MDM enrolled Windows 8.1 and Windows 10 clients. No Intune client is required, which gives a really awesome out of the box experience.
However, we can only deploy single MSI’s, and we can’t patch them with MSP’s, or deploy installers that are only available as .exe.
To spare us having to repackage them, please vote on my uservoice idea to extend MDM enrollment in Intune.
You may have been reading up on the Enterprise Mobility Suite by Microsoft. Especially now that Windows 10 has been released, it seems like everything is becoming easier and simpler for end users, managers and admins alike while Microsoft is really pushing the Anywhere, Anyplace, Anytime concept.
Let me state first off that I believe these advancements are incredible, and I really feel Microsoft is heading in the right direction, but there are quite a few ‘gotcha’s’ that you probably don’t know about that could hurt your implementation, they may not always apply to you.
In my opinion, as EMS currently stands as a suite, when used to manage Windows 10 laptops / tablets and desktops, is only suitable for very ‘light’ management situations unless there is an additional device management authority such as SCCM fully configured and implemented as Internet Facing for true device and application management.
The Enterprise Mobility Suite as a standalone product for full Windows 10 is NOT suitable for almost all Application Deployment scenario’s.
Continue reading Is Enterprise Mobility (EMS) and Windows 10 by Microsoft going to make you happy?