←
Thorsten E.24,799 posts
Thorsten E. avatar

Thorsten E.

@endi24

Citrix, Windows Administrator, AppV, Automation, EUC, Application Packaging, Security, Virtualization, PowerShell

◷ Joined September 2009▧ 322 Photos and videos
@rnabmitra avatar
⟳ Thorsten E. retweeted
@rnabmitra@rnabmitra·Nov 17

#MSIntune can now manage #Servers big announcement from #MSIgnite ✅ Configurations ✅ Compliance policies ✅ Deploy apps ✅ Manage Updates techcommunity.microsoft.com/…

Horizon Secured avatar
⟳ Thorsten E. retweeted
Horizon Secured@horizon_secured·Nov 12

🔒 𝗦𝗲𝗰𝘂𝗿𝗲 𝗕𝗶𝘁𝘀 💡 𝗡𝗧𝗟𝗠 𝗦𝗶𝗴𝗻𝗶𝗻𝗴: 𝗡𝗲𝘄 𝗪𝗶𝗻𝗱𝗼𝘄𝘀 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗖𝗵𝗮𝗻𝗴𝗲𝘀 With the November 2026 Patch Tuesday updates, Microsoft introduced new NTLM signing protections addressing 𝗖𝗩𝗘-𝟮𝟬𝟮𝟲-𝟭𝟭𝟴𝟳𝟯𝟳. The goal is to ensure NTLM authentication establishes a cryptographic session key and negotiates actual message signing instead of relying on the legacy ALWAYS_SIGN behavior ⚠️. The changes are being introduced in two phases: 🔹 𝗡𝗼𝘃𝗲𝗺𝗯𝗲𝗿 𝟮𝟬𝟮𝟲: Windows clients offer NTLM signing by default, while servers continue accepting connections without signing. 🔹 𝗠𝗮𝘆 𝟮𝟬𝟮𝟳: Windows servers will require NTLM signing by default. Clients that don't negotiate signing will be rejected. 🔎 𝗛𝗼𝘄 𝘁𝗼 𝗰𝗵𝗲𝗰𝗸 𝘆𝗼𝘂𝗿 𝗲𝗻𝘃𝗶𝗿𝗼𝗻𝗺𝗲𝗻𝘁? With 𝗡𝗧𝗟𝗠 𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝗟𝗼𝗴𝗴𝗶𝗻𝗴 enabled, you can inspect the following events in Microsoft-Windows-NTLM/Operational: • 𝗖𝗹𝗶𝗲𝗻𝘁: Events 4020 and 4021 • 𝗦𝗲𝗿𝘃𝗲𝗿: Events 4022 and 4023 • 𝗗𝗼𝗺𝗮𝗶𝗻 𝗖𝗼𝗻𝘁𝗿𝗼𝗹𝗹𝗲𝗿: Events 4032 and 4033 (same-domain authentication) In the 𝗡𝗧𝗟𝗠 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 section, check: ✅ 𝗡𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗲𝗱 𝗙𝗹𝗮𝗴𝘀: SIGN (0x10) and KEY_EXCH (0x40000000) should be present according to Microsoft's readiness criteria. ✅ 𝗦𝗲𝘀𝘀𝗶𝗼𝗻 𝗞𝗲𝘆 𝗦𝘁𝗮𝘁𝘂𝘀: Present ⚠️ 𝗗𝗼𝗻'𝘁 𝗿𝗲𝗹𝘆 𝗼𝗻 𝘁𝗵𝗲 𝗘𝘃𝗲𝗻𝘁 𝗜𝗗 𝗼𝗿 𝗪𝗮𝗿𝗻𝗶𝗻𝗴 𝗹𝗲𝘃𝗲𝗹 𝗮𝗹𝗼𝗻𝗲. Event 4023 can appear even when NTLM signing is negotiated. Similarly, Channel Binding: Not Supported does not mean NTLM signing is missing. The screenshot shows a successful NTLM negotiation with both flags and a session key present. One complication is that 𝗡𝗲𝗴𝗼𝘁𝗶𝗮𝘁𝗲𝗱 𝗙𝗹𝗮𝗴𝘀 is a hexadecimal bitmask. You won't necessarily see 0x10 directly in the event. You need to decode the value to check whether the SIGN bit is set. Microsoft provides a PowerShell script in 𝗞𝗕𝟱𝟭𝟯𝟱𝟱𝟱𝟳 to identify authentications where the SIGN bit is missing. 🔎 Start auditing NTLM usage now and identify clients that may be affected when enforcement begins in May 2027. 📚 Microsoft KB5135557 in the comments. #NTLM #WindowsSecurity #ActiveDirectory #PatchTuesday

Post attachment
NeowinFeed avatar
⟳ Thorsten E. retweeted
NeowinFeed@NeowinFeed·Nov 12

Microsoft shares some new details about its OneDrive command line tool, which it unveiled last month, including when we will finally see the utility. #Microsoft #OneDrive #CLI neowin.net/news/microsoft-sh…

Allie K. Miller avatar
⟳ Thorsten E. retweeted
Allie K. Miller@alliekmiller·Nov 11

Haven't seen anyone post about the new Fable 5.2 score on the Remote Labor Index benchmark. We were at only 2.5% a year ago. Fable 5.1 was 17.9%. Fable 5.2 is 41.3%. The doubling time is about 3 months.

Post attachment
Center for AI Safety avatar
⟳ Thorsten E. retweeted
Center for AI Safety@CAIS·Nov 10

When we launched the Remote Labor Index a year ago with @ScaleAILabs , the best AI could fully automate 2.5% of real freelance projects. Fable 5.2 now automates 41.3%. The automation rate is doubling every ~3 months. AIs may soon be able to do all remote work faster and more cheaply than humans.

Post attachment
Mr. Claude avatar
⟳ Thorsten E. retweeted
Mr. Claude@claudeskills101·Nov 11

BREAKING: Claude Fable 5.2 finished 41.3% of 240 paid freelance projects at a level a client would accept. Fable 5.1 managed 17.9%. Hand Claude the job with these 7 prompts:

Yarchi avatar
⟳ Thorsten E. retweeted
Yarchi@undefinedKi·Nov 11

Anthropic just published the full prompting guide for Claude Fable 5.2. A new models read the same words differently, so your prompt has to change with it: 1. Tell it the code is yours. Add one line like "This codebase is yours and you'll keep building on it." Without it, the model piles new code on top of the old and only reports problems it sees nearby. With it, it cleaned up repeated code in half the tries instead of under 1 in 10. 2. It quits long tasks too early, especially at low and medium effort. Tell it to keep going and work through ordinary errors and timeouts on its own. That cut unfinished sessions in half. 3. "Answer directly, don't overthink" doesn't work anymore. It thinks anyway. If simple requests are slow, lower the effort level instead. 4. Clean out old notes and memory files. One old "never retry" note dropped retries from almost always to 4 in 10. 5. Say exactly what you approve. "Yes, run the migration on staging" works better than "go". 6. High effort is enough for most work. Almost all the gain is already there, and going higher mostly just burns tokens. 7. Strict rules for its reports backfire. Tell it "max 20 words per sentence" and it follows that so exactly that the summary of what it did turns into choppy fragments nobody can follow. Drop the rules you don't really need. The model got much better at listening. The problem is that most of our prompts were written for models that didn't, so they're full of old warnings it now takes seriously.

Post attachment

Yarchi @undefinedKi Aug 29 Article How to Set Up Claude Once and Get 10x Out of It (You Have No Idea What Your Chat Can Actually Do) There is a version of Claude that already knows who you are, and you are one evening away from it. Right now you probably open a chat, explain who you are, explain the project, paste the same context,