# Intune Enroll Limit of 15 – how to get around and resolve this limit

A client had to roll out 100+ laptops and choose Intune for this. It wasn’t certain who was getting what laptop so the choice was made to use an admin account to enroll the devices before giving them to the user.

Intune has a Enroll Limit of 15 so after 15 you start having issues

In Intune you can actually setup Device Enrollment Managers who can actually Enroll 1000+ machines

1. In Intune in the Azure portal, choose Device enrollment > Device enrollment managers.

3. On the Add User blade, enter a user principal name for the DEM user, and select Add. The DEM user is added to the list of DEM users.

https://docs.microsoft.com/en-us/intune/device-enrollment-manager-enroll

GD Star Rating
GD Star Rating

$appname = "Microsoft Edge" ((New-Object -Com Shell.Application).NameSpace('shell:::{4234d49b-0245-4df3-b780-3893943456e1}').Items() | ?{$_.Name -eq $appname}).Verbs() | ?{$_.Name.replace('&','') -match 'Unpin from taskbar'} | %{$_.DoIt();$exec = $true} GD Star Rating loading... GD Star Rating loading... # Add Local Printers via Powershell for Intune  Add-PrinterDriver -Name "HP LaserJet 500 color MFP M570 PCL6 Class Driver" add-printerport -name "HP500" -printerhostaddress "10.0.100.21" add-printer -name "HP" -drivername "HP LaserJet 500 color MFP M570 PCL6 Class Driver" -port "HP500" Set-PrintConfiguration -PrinterName "AAL-MEL-PR-01(HP)" -PaperSize A4 -Color$false -DuplexingMode TwoSidedLongEdge

Add-PrinterDriver -Name "Lexmark CX920 Series Class Driver"

add-printer -name "Lexmark" -drivername "Lexmark CX920 Series Class Driver" -port "Lexmark"

Set-PrintConfiguration -PrinterName "AAL-MEL-PR-02(Lexmark)" -PaperSize A4 -Color $false -DuplexingMode TwoSidedLongEdge GD Star Rating loading... GD Star Rating loading... # How to deploy Project 2010 or other Office 2010 apps with Intune and setup.exe installer Extract the ISO to a folder and run from the root folder setup.exe /admin to open this Go through all the options especially above for the CD Key information and accepting License and Display Level None Once this is done , Save this as an MSP file with any name in the UPDATES folder of the CD ( The installer runs all the MSP’s in here ) Next create a config.xml file in the same directory as setup.exe with the below config <Configuration Product="PrjPror"> <!-- <Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" /> --> <!-- <Logging Type="standard" Path="%temp%" Template="Microsoft Office Project Professional Setup(*).txt" /> --> <!-- <USERNAME Value="Customer" /> --> <!-- <COMPANYNAME Value="MyCompany" /> --> <!-- <INSTALLLOCATION Value="%programfiles%\Microsoft Office" /> --> <!-- <LIS CACHEACTION="CacheOnly" /> --> <!-- <LIS SOURCELIST="\\server1\share\Office;\\server2\share\Office" /> --> <!-- <DistributionPoint Location="\\server\share\Office" /> --> <!-- <OptionState Id="OptionID" State="absent" Children="force" /> --> <!-- <Setting Id="SETUP_REBOOT" Value="IfNeeded" /> --> <!-- <Command Path="%windir%\system32\msiexec.exe" Args="/i \\server\share\my.msi" QuietArg="/q" ChainPosition="after" Execute="install" /> --> <Display Level="None" CompletionNotice="No" SuppressModal="No" AcceptEula="Yes" /> <Setting Id="SETUP_REBOOT" Value="Never" /> < /Configuration> Next use IntuneWinAppUtil.exe to package the App Up c:\TempPath\Intune-Win32-App-Packaging-Tool-master>IntuneWinAppUtil.exe Please specify the source folder: “F:\Project2010\” Please specify the setup file: setup.exe Please specify the output folder: C:\TempPath\Project2010 ### Intune Settings Install Command : setup.exe /config config.xml Unintall Command : Setup.exe /uninstall 90140000-00B4-0409-0000-0000000FF1CE Detection Rule ( Check File ) : C:\Program Files (x86)\Microsoft Office\Office14\WINPROJ.EXE GD Star Rating loading... GD Star Rating loading... # Copy file to workstations with Windows Intune **If you want to deploy a file from an Azure Blob Location for Files that need changing frequently see here ** Seems one of the only ways to copy files to PC’s in Intune seems to be to create an MSI file to deploy them which requires a MSI packager ( Laboursome) . However, this can also be done using Windows app (Win32) container Copy.bat File rem Copy Files copy off.ini c:\Windows\System32\off.ini copy BSPECIAL.DLL c:\Windows\System32\BSPECIAL.DLL copy BSPECIAL.DLL c:\Windows\SysWOW64\BSPECIAL.DLL rem Set Permissions icacls "c:\Windows\System32\BSPECIAL.DLL" /grant Everyone:M icacls "c:\Windows\SysWOW64\BSPECIAL.DLL" /grant Everyone:M You will need to make sure the folder exists before you copy files to it such as below , or you can use the XCOPY function instead of copy if not exist C:\Temp\Test mkdir if not exist C:\Temp\Test  del.bat file del c:\Windows\System32\off.ini del c:\Windows\System32\BSPECIAL.DLL del c:\Windows\SysWOW64\BSPECIAL.DLL Next run the IntuneWinAppUtil.exe File c:\TempPath\Intune-Win32-App-Packaging-Tool-master>IntuneWinAppUtil.exe Please specify the source folder: F:\Config Files Please specify the setup file: copy.bat Please specify the output folder: C:\TempPath\BuildsoftAppps Create a new Windows app (Win32) App in Intune , upload the copy.intunewin and use the commands below Detection Rules GD Star Rating loading... GD Star Rating loading... # How to diagnose issues with Powershell Scripts Running in Intune Following on from this great article The Powershell Script History and logs are stored in the following registry location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Policies You will need to navigate to a subtree in their GUID ### How do I get the GUID for my Intune Script? ## Diagnosing Failures A result was coming Failed with the below ï¿½ï¿½$ : The term 'ï¿½ï¿½$' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.At C:\Program Files (x86)\Microsoft Intune Management Extension\Policies\Scripts\ee7f18e5-b666-4c11-be72-9d5490a49e23_a39275a0-659c-45a9-9f1a-d312ae484eda.ps1:1 char:1+ ï¿½ï¿½$

On running the scripts get copied here briefly then run and deleted : C:\Program Files (x86)\Microsoft Intune Management Extension\Policies\Scripts

You have to be fast but you can copy the .ps1 file to e.g. C:\Temp and check what the machine was getting , to resolve this issue I had to recopy the file into Powershell ISE and resave and upload.

### How to Run the Scripts Manually

Change DownloadCountand ErrorCode to 0 and set Result and ResultDetails to nothing (empty string). After this we just restart the Microsoft Intune Management Extension Service (IntuneManagementExtension) and the script will rerun again on this device

### Log Directory

C:\ProgramData\Microsoft\IntuneManagementExtension\Logs

GD Star Rating