๐ฅท I'm a security consultant with a strong background in topics around endpoint management (from configuration manager to Intune via co-management), identity and security
๐ญ I really love to build new things, automate existing processes and build useful helpers
๐ฑ I'm currently focusing on security topics around the Microsoft security stack and have a big passion for identity threat detection and response
๐โ Learn more and find me online at my blog and on medium as well
When I enter the URL of the custom .ico to be used and the app is deployed, no icon is shown on the newly created desktop shortcut. When opening the shortcut's properties and clicking the Change Icon... button you're prompted with the following error message stating that Windows can't find the file. The URL of the .ico file is accessible on the web and hosted in an Azure blob.
Hi,
First of all thanks for the effort. I have a few questions:
Get-AzureADDirectoryRole does not seem to list all the built-in roles I do see in the Azure Portal? Moreover role names returned by this applet do not always correspond with the names in the Azure Portal?
In which PS1 library can I find [Microsoft.Open.Azure.AD.CommonLibrary.AzureSession]?
It would be nice if the possibility to where the shortcut would appear can be added as a parameter.
For example, sometimes it is needed to set a shortcut to the users own personal startmenu and/or desktop and sometimes we need it to go to the public startmenu and/or desktop. It would be nice if that could be defined in the install parameters.
HI, me again, I've tested the script and it works perfect after I've corrected my mistake in the detection script but only on one user. The second user that logs on the device get's no shortcut diploid. The shortcut app is assigned to computers no to users. If you don't mind helping with this again. Thx :)
which is a synced sharepoint site produces a broken link on the desktop (doesn't have target at all). Using the script as the user works just fine so just the intune deployment is broken when using environment variables.
Whilst implementing your script in our environment, I was seeing that a lot of BitLocker settings seemed to be missing in the JSON variable, for example the deviceConfiguration--windows10EndpointProtectionConfiguration_bitLockerSystemDrivePolicy. Upon investigation I noticed that this was resolved with removing the | Where-Object { $null -eq $_.value } where settingsDelta is declared in the object.
I found that without checking for null values, there did not seem to be any empty values in the JSON (in my example). I fixed this in our implementation, but this may be useful information for you.