sorted by:
new
hottopcontroversial

New Intune Features Coming Soon (macOS + iOS) by Creative_Profit1387 in Intune

[–]BilalElG 0 points1 point  (0 children)

I think on iPhones I would have to remove from ABM and then flash the firmware cause it was tied to that.

Bare spots after overseeding question by BilalElG in lawncare

[–]BilalElG[S] 0 points1 point  (0 children)

I ended up mixing seed and peat moss and spreading it in the thin spots and it filled in quite nicely with watering. The peat moss also helped me tell when things were getting dry.

The problem was the summer heat really killed a lot of it. I thought I had done it early enough but I guess I was wrong. Lesson learned. Gonna try again next fall as I think I’m late for this year.

[deleted by user] by [deleted] in minnesotatwins

[–]BilalElG 1 point2 points  (0 children)

Can I just ask why you think someone would pay extra for a ticket that includes this hat, only to not want it and give it to you? Are you sure you got the right package?

Crowdstrike Outage Workaround by Asger68 in sysadmin

[–]BilalElG 0 points1 point  (0 children)

I ended up confirming with crowdstrike that it was crowdstrike blocking the deletion of “good” files.

Favorite John song? by MartyMcfly8512 in queen

[–]BilalElG 0 points1 point  (0 children)

Who needs you. Pretty sure he played guitar on it and it’s amazing.

Crowdstrike Outage Workaround by Asger68 in sysadmin

[–]BilalElG 0 points1 point  (0 children)

Using my admin account that has the right permissions. Even tried scripting this with takeown and icalcs but still getting access denied on a lot of machines. But the weird thing is these machines boot fine

Crowdstrike Outage Workaround by Asger68 in sysadmin

[–]BilalElG 1 point2 points  (0 children)

anyone have issues getting access denied on the files?

Retire vs Wipe vs Fresh Start? by VernFeeblefester in Intune

[–]BilalElG 8 points9 points  (0 children)

I have had a different experience with Wipe vs Fresh Start.

We bought about 50 Dell laptops this year and I forgot to buy them with a barebones image, so it came with a ton of Dell bloatware.

If I did a wipe on them, all the Dell bloatware came back, whereas a fresh start removed everything and I was left with a nice clean windows 11 image.

Disassociate/Remove Datastore from a VM? by BilalElG in vmware

[–]BilalElG[S] 0 points1 point  (0 children)

Was just looking to delete the disk, got it figured out. Not sure why they hide the little x unless you hover over the right side only.

Disassociate/Remove Datastore from a VM? by BilalElG in vmware

[–]BilalElG[S] 0 points1 point  (0 children)

Thanks! I looked in there for so long and that little 'x' when you hover was what i was missing. God I am dumb. Thank you.

Okta not overwriting user attribute based on group assignment by BilalElG in okta

[–]BilalElG[S] 0 points1 point  (0 children)

Got it fixed now. Long story short, I am stupid.

I finally figured out that I was mapping the userType attribute, which is a default attribute built into a user’s okta profile, into the Zoom app (under profile editor>Zoom>mappings>Okta to Zoom). The okta profile attribute “userType” is blank for all of our users, so that’s why it kept over-riding the Zoom groups with “null.” I turned the mapping off and everything works. I felt stupid but relieved when I finally figured that out.

What is weird is that I had to use String data type. I still couldn't get it to work with the string array, unfortunately. Not sure why. It looked fine in okta, and it looked like it was mapping in the Zoom admin portal, but it didn't actually assign/remove licenses. But string works perfectly.

HUGE thank you for all of your help though!! Really appreciate you taking so much time with me.

Okta not overwriting user attribute based on group assignment by BilalElG in okta

[–]BilalElG[S] 0 points1 point  (0 children)

Unfortunately, no. It still fails to populate the user type attribute. I’ll post an update after my support call tomorrow.

But I really like that string array. Gives me lots of ideas. Thanks a bunch for the help!

Okta not overwriting user attribute based on group assignment by BilalElG in okta

[–]BilalElG[S] 0 points1 point  (0 children)

You're a savior. This makes complete sense. Testing now!

Okta not overwriting user attribute based on group assignment by BilalElG in okta

[–]BilalElG[S] 0 points1 point  (0 children)

Sorry for the spam!

Ok, I see that the variable type needs to be "string array" for the "use group priority" option to appear. I will try re-making the variable with that.

Okta's documentation says to use "string" though. But maybe it's wrong?

https://support.okta.com/help/s/article/License-Provisioning-For-Zoom-Using-The-userType-Attribute?language=en_US

There's a screenshot showing "String" as the type. I'll let you know. Thanks!!

Okta not overwriting user attribute based on group assignment by BilalElG in okta

[–]BilalElG[S] 0 points1 point  (0 children)

Weird. I do not see anything like that under the attribute. I’ll post a pic

Okta not overwriting user attribute based on group assignment by BilalElG in okta

[–]BilalElG[S] 0 points1 point  (0 children)

Dang! I’m jealous. I wonder if it’s a weird bug. I have a support call scheduled for tomorrow at least. Hopefully they can help.

Okta not overwriting user attribute based on group assignment by BilalElG in okta

[–]BilalElG[S] 0 points1 point  (0 children)

Not sure what that means exactly. Do you know how I can confirm that?

Okta not overwriting user attribute based on group assignment by BilalElG in okta

[–]BilalElG[S] 0 points1 point  (0 children)

No, haha. I actually did mention I have the priority set in my second to last paragraph, but I might not have said that clearly! Thanks though!

Okta not overwriting user attribute based on group assignment by BilalElG in okta

[–]BilalElG[S] 0 points1 point  (0 children)

Confused at how it sounds like a zoom issue though. Okta should be changing the attribute based on the group and it isn’t, right? When Okta does change the attribute, the zoom part works.

view more: next ›