Software Update

 This is a test.

Comments

Post a Comment

Popular posts from this blog

Azure AD (Microsoft Entra) Bulk Token Troubleshooting

Image
 I had an issue with trying to create an AAD bulk token via the Windows Configuration Designer  . The error message I had: Checking the log located here: {Replace Kyle with your username} C:\Users\Kyle\Documents\Windows Imaging and Configuration Designer (WICD)\Project_Name\ICD.log 9/13/2023 3:37:53 PM Info Project 'New' created successfully and added to workspace 9/13/2023 3:37:53 PM Info Loading scenario ID: xxxxx-xxxxxxx-xxxxxx-xxxxxxx, URI: http://localhost:9098/Scenarios/xxxxxxx-xxxxxxx-xxxxxx-xxxxx/Index.html 9/13/2023 3:38:36 PM Error Bulk token retrieval failed: {"error":"server_error","error_description":"AADSTS90092: Non-retryable error has occurred.\r\nTrace ID: caxxxxxx-xxxxxxx-xxxxxx-xxxxxx\r\nCorrelation ID: xxxxxx-xxxxxx-xxxxxx-xxxxxxx\r\nTimestamp: 2023-09-13 20:38:36Z","error_codes":[90092],"timestamp":"2023-09-13 20:38:36Z","trace_id":"xxxxxx-xxxxxxx-xxxxxxx-xxxxxx",...
Read more

Vanta mass deployment

Image
I recently encountered a client with the need to deploy the Vanta agent to multiple macOS devices. Surprisingly, there was no officially supported method for this, even after consulting with Vanta support. However, through some reverse engineering, I managed to devise a solution. Let's begin by outlining the prerequisites for making this script work effectively. 1. A paid Vanta subscription and an admin account. 2. Your  VANTA_KEY= from here:  Setup Instructions - Vanta   3. Region of Vanta instance 4. Method to get email of the user you want to assign this agent to (optional) Ok now that we have this info we can edit my script. These are the values we need to update: AGENT_KEY="" OWNER_EMAIL="" REGION="" Examples: AGENT_KEY="rtvgbh5rvcnn928h2ag5ten11148q3ucwfj3f8zkr2grdk696rt0" OWNER_EMAIL="kyle@ericsontech.com" REGION="us" Here is the full script you can edit. https://raw.githubusercontent.com/kylejericson/JAMF/master/S...
Read more

Setup Device Compliance with Jamf and Intune

Image
  Requirements: Azure user group created Jamf Pro Smartgroup created Global admin rights in Azure AD Admin account in Jamf Pro Steps to setup Device Compliance 1. Login to Jamf Pro and go to: Global-->Device Compliance-->Pick your Compliance Group (Jamf Pro Smartgroup)-->Pick your Applicable Group (Smart group containing all computers Jamf Pro uses to send a compliance status to Microsoft Intune.) 2. Enable the setting in Jamf Pro and you will be redirected to Azure permissions page. Click Accept on each one. 3. Click the Open Microsoft Endpoint Manager button 4. Click the Add compliance partner button 5. Pick Jamf Device Compliance 6. Click Add groups and add your user group you created in Azure AD. I created one called "All Users" 7. You should see a screen like this. 8. Click Confirm 9. Now wait for the activation to apply. 10. Now the connection is complete and you can start registering devices via Company Portal. 11. Important with the new workflow Macs only sho...
Read more