Parameterize Script for Get List of Stale Devices and Remove them for automation purposes

[subbzz]

Hi MrTechGadget,

As discussed via mail. I am wondering if we can have a new script to identify and remove stale entries (from all OGs) beyond x number of days (say devices that did not show up over 25 days). This script can run on a daily basis. The date and time can be pegged from the server this script is running.

Thanks,
SS

[MrTechGadget]

@subbzz , thanks for opening this. I'm thinking about this and would like some additional info.

1. Does it matter the status of the device? (Enrolled, Unenrolled, Pending Enterprise Wipe, Device Wipe Initiated, etc.)
2. Do you want to wipe enrolled devices first or just delete the record?
   2b. If yes, would it be different for employee vs company owned, and different for DEP supervised devices?
3. What device details are important to log before deletion?

[subbzz]

Hi Mr TechGadget, Many thanks for your response. Basically I modified your code and now I am able to get it working the way I wanted. I completed the testing only last evening. Many thanks again. Cheers Siva

…

On Wed, Apr 10, 2019, 06:56 Joshua Clark ***@***.***> wrote: @subbzz <https://github.com/subbzz> , thanks for opening this. I'm thinking about this and would like some additional info. 1. Does it matter the status of the device? (Enrolled, Unenrolled, Pending Enterprise Wipe, Device Wipe Initiated, etc.) 2. Do you want to wipe enrolled devices first or just delete the record? 2b. If yes, would it be different for employee vs company owned, and different for DEP supervised devices? 3. What device details are important to log before deletion? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AdjvnEjeBNwYtOMkvKApZu1ItL7iiELLks5vfP5tgaJpZM4cZjw7> .

[MrTechGadget]

Awesome, glad to hear it. If you would like to contribute those back to this project, contributions are always welcome.

[subbzz]

Sure. I will add it to your collection over the weekend. Just wanted to check with you something for another use case, I wanted to fetch user id for an user, and I am using username but the api is returning not the exact match with user name. I am getting results all values match multiple results. For example, User1 (Andrew.jackson@email.com / ajack) and User 2 (Alex.jackson@email.com / ajack1), api query with username is returning both results. Any ideas to get the results based on exact match of username? Cheers, Siva

…

On Wed, 10 Apr 2019 at 21:47, Joshua Clark ***@***.***> wrote: Awesome, glad to hear it. If you would like to contribute those back to this project, contributions are always welcome. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AdjvnNELtt5TeBRwm44AL7G9MLmSxYYWks5vfc8zgaJpZM4cZjw7> .

[MrTechGadget]

Yes, username query returns partial matches and this field is not unique. You have to perform string comparisons (be sure to remember case) on the results to grab the exact match.

…

On Mon, Apr 15, 2019 at 6:04 AM subbzz ***@***.***> wrote: Sure. I will add it to your collection over the weekend. Just wanted to check with you something for another use case, I wanted to fetch user id for an user, and I am using username but the api is returning not the exact match with user name. I am getting results all values match multiple results. For example, User1 ***@***.*** / ajack) and User 2 ***@***.*** / ajack1), api query with username is returning both results. Any ideas to get the results based on exact match of username? Cheers, Siva On Wed, 10 Apr 2019 at 21:47, Joshua Clark ***@***.***> wrote: > Awesome, glad to hear it. If you would like to contribute those back to > this project, contributions are always welcome. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #7 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AdjvnNELtt5TeBRwm44AL7G9MLmSxYYWks5vfc8zgaJpZM4cZjw7 > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#7 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AQVLdSOOA0wcM0GmxqCGrb5vP02ARvoIks5vhE6sgaJpZM4cZjw7> .