![]() ![]() ![]() You’ll find it here: Putting together the PowerShell Script Fortunately the legend that is Darren White has put together an Automate script to easily generate the token. Note this token is not allowing blanket access to your Automate, it’s just allowing the requester to see things like your agent installer. This token will be utilised in the PowerShell script to allow it to download and install the agent on the machine. Getting Startedįirst you need to generate an installer token. This has the huge benefit of meaning the package in Intune never has to be updated as a newer version of the Agent are released. Instead of putting the agent installer, in the form of EXE or MSI within Intune, we can package up a PowerShell script that always downloads the most up to date agent. There are certainly a number of different ways to approach this, but I have what I think is the most convenient long term solution. I’ve seen this question popping up quite a bit recently and thought it would make a worthwhile blog post.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |