Great stuff. was waiting on this. now we just need to wait unti v 2.129 is stable. May look to get on the beta version. Thanks for the content, great stuff!
Excellent guide as always Connor. Love your work mate. I was wondering if you had any recommendations on how we can add to the powershell script to pull the Outlook Email Address as well? We have a customer where the UPN and Email accounts are different each time. Maybe add another Ninja custom field and add to Halo.
Great and useful video Connor. I was stoked until I got to the end and heard the user and asset site need to match... Not sure why that is a Halo requirement, this would work for us if they only had to match at the client level. Some of us might not be getting that granular with users in AAD, but we are getting granular with the assets and their location for various reasons.
We've ran some testing this morning, if the device is located at a specific site, but the user is not located in that site, then it won't match unfortunately. We'll see what HaloPSA says and to see if there is anything that can be added to alter this behaviour.
Good Afternoon, seems like it, but wanted to confirm. Does this work for v2.162.62 ? I tried it and it does not work, but assumed that is the reason. Thank you!
Great stuff. was waiting on this. now we just need to wait unti v 2.129 is stable. May look to get on the beta version. Thanks for the content, great stuff!
Excellent guide as always Connor. Love your work mate. I was wondering if you had any recommendations on how we can add to the powershell script to pull the Outlook Email Address as well? We have a customer where the UPN and Email accounts are different each time. Maybe add another Ninja custom field and add to Halo.
Great and useful video Connor. I was stoked until I got to the end and heard the user and asset site need to match... Not sure why that is a Halo requirement, this would work for us if they only had to match at the client level. Some of us might not be getting that granular with users in AAD, but we are getting granular with the assets and their location for various reasons.
We've ran some testing this morning, if the device is located at a specific site, but the user is not located in that site, then it won't match unfortunately. We'll see what HaloPSA says and to see if there is anything that can be added to alter this behaviour.
@@RenadaSolutions thanks Connor.
This is currently only available if you're running HaloPSA BETA V2.129
Wish you had a video for SyncroMSP integration…
Hopefully one day!
any idea, how this can be achieved with mac computers as well?
Good Afternoon, seems like it, but wanted to confirm. Does this work for v2.162.62 ? I tried it and it does not work, but assumed that is the reason.
Thank you!
This should work in all versions. This is basically just matching an E-mail Address in HaloPSA to an E-mail Address from Ninja (in a custom field)
@ I was able to get it functional. :) thank you! User error as always….
Your doco is now different to this video
But an awesome help nonetheless