In case anyone missed the big announcement yesterday.
Helping customers shift to a modern desktop – Microsoft 365 Blog
Windows 10 Enterprise customers will get 30 month support (change from the 18 month). Those on current 1607, 1703, 1709, and 1803 will be extended to 30 months as well.
Future releases for Sept will have 30 months (starting with 1809) and spring releases (starting 1903) will still be 18 months for those that was faster cadences.
This is great news for Enterprise customers. For those on Pro version, might want to reconsider to move to Enterprise unless you can do the 18 month.
There are other announcements but this is the biggest as there were many concerns on the 18 month cycles.
In 1802 TP, when you create a upgrade Task Sequence, now there will be additional groups created that is based on recommendations what Microsoft and others have seen done in the field. These groups are just recommendations and the actual tasks/scripts to do the checks, installs, etc. will need to be done by you. Several example scripts are out on the next that can help you get started.
Some examples and additional recommendations are available here https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1802
One of the new features of the CM 1802 TP is the ability to create deployment templates for Task Sequences and then use that to apply to existing task sequences to create new deployments.
To create a template, during the deployment of a TS, in the Summary screen, there is a new button in the upper righthand corner “Save As Template…”.
Once you select that, you have a new popup box to select what you want included in the template and name the template.
In this case, I chose all of it and named it Win 10 Deployment.
Now to apply the template in a new deployment, in the first dialog, you have the Select Deployment Template button (above the Comments area).
Once clicked, you can select the template of your choice.
Update to registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WcmSvc\wifinetworkmanager\config
Or via Login Script or during the task sequences in Configuration Manager or MDT (post image install)
reg add HKLM\SOFTWARE\Microsoft\WcmSvc\wifinetworkmanager\config /t REG_DWORD /v AutoConnectAllowedOEM /d 0
Modify Unattend.xml to add Microsoft-Windows-WiFiNetworkManager
Set WiFiSenseAllowed to 0
For Windows 10 build 1511 or later
Configure the Group Policy Object Allow Windows to automatically connect to suggested open hotspots, to networks shared by contacts, and to hotspots offering paid services under
Computer Configuration\Administrative Templates\Network\WLAN Service\WLAN Settings\.
Some of us have been waiting a long time for these.
ThinkPad Driver Packs for ConfigMgr are self-extracting executables with drivers in the folder structure and format so they can imported into ConfigMgr 2007 or 2012 and used in an Operating System Deployment task sequences for deployments.
If the links above don’t work, driver packs are a bit harder to locate than they are for Dell and HP. You have to hit the Drivers & Software page on the Lenovo site, then walk through their wizard to identify the model of PC for which you want drivers. Once you do that, you can jump to the Enterprise Management spot and grab the ConfigMgr Packs for the various processor types.