![]() ![]() On the other hand, this thresh skin, even on SR, is not for old champion (thresh is pretty recent and his base looks good), but it looks terrible and that mask he has clearly doesn't fit. As long as they do not maim his general idea.Īlso, udyr's design, even for base skin, isn't actually that bad, conception-wise. He's getting reworked anyway and he'll receive visual update, so the difference between base and SGU would drop. ![]() Of course rito did not release SGU for the lolz, but for the cash it provided, but it's not this exact case. SGU as ultimate skin introduced new model which had to be appealing, while base one was refreshed just a bit once or twice. Udyr is the case when base skin simply got old, as it's a champ from 2009. We see it a lot with new hires and then we have to reset their PC so they have to do the whole set-up again.Īs a fully WFH business, we actually see this issue so much that we assign a JR SysAdmin to be in the New Hire orientation because even one person with this issue can hold up the whole thing. ![]() It's actually a pretty common issue we see that autopilot will let users use any MS account to log into a PC if it doesn't have an internet connection, when it does this then Autopilot does not do anything and the user basically has access to an unimaged, fairly useless PC. If it was only machine tied, then your whole Organization would have permissions to Autopilot even if you didn't want them to.Īutopiloy does not work properly without an internet connection. If it has a working internet connection, Autopilot should prevent anyone who is not assigned to that SG from logging. Are you sure you have actually done troubleshooting with Autopilot PCs?īoth the machine and user have to be assigned to the Security Group that assigns the Autopilot role. "Oops you got fired because you overlooked this stupid thing we did? To bad, you should be more careful how you use the tools we constantly are screwing with for maximum ROI in subtle hidden ways that sometimes verge on purposely malicious." All because they didn't want to maintain 2 separate contact lists and/or because Microsoft "helpfully" merged them all into a single pane of glass without telling you and their autocomplete algorithm selected the most frequent contact. Those kinds of things is how someone ends up accidentally sending an off color meme to their boss named Fred Smith instead of their childhood friend Fred Stewart and getting fired. It makes me shudder every time I encounter someone using their work calendar for personal events, let alone anything even more integrated that some people do. I also think it is grossly irresponsible of them to advocate for people to intermix their work and personal accounts at all. ![]() Here is some store credit for the data mining, thanks." Just tell the truth MS, "we want to be able to more easily connect the dots around what people do at home vs at work with our products and services. The former implies it is "opt-in" and the later means "opt-out". "Offers the ability to link" and "will be enabled by default" are conflicting concepts in my opinion. So many stupid calls our T1 guys have to deal with because of that shit. The whole Personal/Work or School thing with Teams and OneDrive was a goddamned tragedy that should have never been allowed to happen. I can't tell you how often someone retires from one of the orgs we handle, we kill their access, and then holy shit does the sky come crashing down because they've been using that email address for all their personal business for decades.all their banking info is tied to it, all their bills funnel through it, all their login accounts to various storefronts and shit run through it. Like it or not, no matter how many times you tell people, they're going to use their work email for personal shit. If they had a personal O365 subscription under their work email it was a total clusterfuck untangling it. So many people use their work emails for their Xbox Live accounts and shit and then MS would freak the fuck out because the account technically already existed. We actually ran into problems with this a lot when migrating clients off of on-prem exchange to O365 over the last couple years. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |