Try the Configuration Manager Technical Preview Branch We would love to hear your thoughts about the latest Technical Preview! Send us feedback directly from the console.ĭocumentation for Configuration Manager Technical Previews Technical Preview Branch releases give you an opportunity to try out new Configuration Manager features in a test environment before they are made generally available. For new installations, the 2202 baseline version of Microsoft Endpoint Configuration Manager Technical Preview Branch is available on the Microsoft Evaluation Center.
Update 2203 for Technical Preview Branch is available in the Microsoft Endpoint Configuration Manager Technical Preview console.
PowerShell release notes preview - These release notes summarize changes to the Configuration Manager PowerShell cmdlets in this technical preview release.įor more details and to view the full list of new features in this update, check out our Features in Configuration Manager technical preview version 2203 documentation. This new option makes sure that the device is fully protected by BitLocker when the task sequence completes, and that you can recover the OS volume immediately. Previously, you had to escrow to Active Directory, or wait for the Configuration Manager client to receive BitLocker management policy after the task sequence.
Learn more about the dark theme for the console.Įscrow BitLocker recovery password to the site during a task sequence - You can now configure the Enable BitLocker step of a task sequence to escrow the BitLocker recovery information for the OS volume to Configuration Manager. Using a console theme can help you easily distinguish a test environment from a production environment or one hierarchy from another. Select Switch console theme again to return to the light theme. To use the theme, select the arrow from the top left of the ribbon, then choose Switch console theme. The Configuration Manager console now offers a dark theme. Woot woot.Update 2203 for the Technical Preview Branch of Microsoft Endpoint Configuration Manager has been released. Open your Git config in a text editor, copy/paste, save, done. Wouldn’t it be even simpler to just copy/paste once? Behold! I offer you this gist containing all the necessary settings. Even though the instructions I referred to above for configuring Git with DiffMerge are straightforward, they still require multiple copy-paste-enter’s.
I prefer GitHub For Windows and the command line. Personally, I’m trying to get away from SourceTree.
If you’re so inclined you can test my theory.
(I didn’t actually confirm it, so it remains just a guess.) If you want to continue using DiffMerge with SourceTree, you’ll probably need two separate difftool and mergetool sections: one for use with the command line and the other for SourceTree. Now, my guess is that SourceTree does, in fact, need the and/or sections in order to work correctly with DiffMerge. (If that doesn’t work, sorry you’re off to your sixth, seventh, or twenty-first post…) Are your DiffMerge settings listed under and/or ? Yes? Then try replacing “sourcetree” with “diffmerge” and see what happens. Run git config -global -e and see what comes up. You’ve already done everything you think you need to do in order to get DiffMerge and Git playing nicely together, right? I mean, the first two hits for “git diffmerge” provide instructions that are pretty straightforward, are they not?Ĭould it be, that you’ve previously used SourceTree? If so, did you configure it to use DiffMerge? Because if you did, that might be the problem. Or: “The merge tool diffmerge is not available as ‘diffmerge’”. Or why git mergetool -tool-help tells you “blah blah blah The following tools are valid, but not currently available: blah blah diffmerge blah blah”. If you’ve reached this post by way of a search engine, I’m guessing it’s at least the fifth, sixth, or twentieth one you’ve looked at trying to understand why the hell git mergetool doesn’t launch DiffMerge.