Softwarovi inzenyri zapomneli, co vlastne delaji a v cem jsou nejlepsi. Myslim, ze naopak programovani jim v urcitych oblastech mozna dokonce snizilo kognitivni schopnosti a omezilo a zhorsilo jejich puvodni inzenyrske dovednosti.
Inzenyr je clovek, ktery dokaze vyresit problem. Hleda nejlepsi, nejrychlejsi, nejefektivnejsi nebo treba nejlevnejsi reseni daneho problemu.
Programovani bylo jen nutne zlo a prostredek k tomu, jak dany problem vyresit.
Predstavte si, ze chcete postavit dum.
V drevnich dobach assembleru museli inzenyri "programovat" samotnou maltu, vyrabet rucne jednotlive cihly. Slo to pomalu a horko tezko dokazali velky dum postavit. Zvladlo to jen velmi malo lidi, kteri byli schopni pracovat se striktnimi logickymi limity danych systemu.
S prichodem vyssich programovacich jazyku, uz inzenyri nemuseli vyrabet cihly ani maltu atd. Uz to meli hotove a skladali cihly pekne na sebe a brali jiz hotovou maltu, s modernejsimi jazyky a nadstavbami a hotovymi komponenty klidne montovali i cele panely a diky tomu uz dokazali stavet opravdu velke domy stale rychleji, snadneji, levneji. To uz zvladlo vice lidi.
S prichodem AI a LLM uz inzenyri nemusi travit cas na stavbe. Stavaji se z nich vedouci projektove kancelare, ktery rozhoduje, co se bude stavet a proc. Postavi toho mnohem vice a hlavne mnohem vetsi a sofistikovanejsi struktury, protoze najednou maji mnohem vice casu na detaily, ale i sirsi souvislosti, na ktere drive nemeli cas.
AI je jen dalsi vrstva abstrakce reseni problemu.
A diky tomu, ze zmizely "limity" vstupu, kdy uz neni nutne psat podle nejake presne logiky a staci psat normalnim jazykem, se schopnost resit treba i globalni problemy otevira pro vsechny, kteri problemy chteji resit.
Zlepsujte svet. Uz nejste nijak omezeni. Tedy pokud vam zrovna nedojdou tokeny :)
@AdamGell User-less Autopilot scenarios fall into the Default "All Users" restriction policy. So you need to have Windows enabled there if you use them. Otherwise you get enrollment error.
@Kazzan@MyNameIsMurray@KPCS_CZ MS just postponed the Enforcement to Feb 11, 2025 giving us (and themselves) an additional 15 months to solve this. So far, we focused on doing the strong mapping manually into altSecId. attribute as https://t.co/YSWkDWYMaX mentions and have barebones script that does just this.
@DeviceDeploy Speaking of WDAC, the reboot-less way of deploying it from Intune is not covered under the Endpoint Protection workload and the Device Configuration must be switched (see https://t.co/rUZM4mHXvw). Any possibility of WDAC deployment from Intune scenarios getting better?
@bdam555@bytenerd That would be strange behavior, but who knows. I'd say it's just slow. And that the Intune Windows data is required to enable as roughly two days after I enabled it first data showed up. Albeit still not complete. I'm deploying more clients to have bigger sample size.
@byteben@MSEndpointMgr Nice work. Love your writing style. You always manage to answer the question I'm asking myself in the following paragraph. Can't wait for part 2.
@AndrewZtrhgf True that. But what are the other options? On Windows it's something custom you are probably starting to work on. For Android and iOS AFAIK there's nothing.
@AdamGrossTX Hi Adam, nice work, thanks. I tried to run the script but caught two small typos in it which needed to be corrected so the script would run correctly. I created corresponding issues on the file in your repo.
@manelrodero If I understand, your problem. Create collection hierarchy based on AD OU structure. Then use ConfigMgr RBAC with built-in Security role Application admin., Custom scope and collection from step 1. We have 7 departments each delegated to distinct OU tree within single domain.