The ConfigMgr Technical Preview 2103 is out and this is the second technical preview release in the same month. We did see SCCM technical preview 2102 release the same month.
Honestly I was expecting this technical preview version to be 2102.2 because last year we saw TP 2002 release and in the same month 2002.2 was also released. It doesn’t matter much because at the end all we want to know is what’s new in ConfigMgr Technical preview 2103 release.
ConfigMgr Technical Preview 2103 includes new features and some changes in the way you install the updates. You will find that out when we install the 2103 update.
Refer the following post for previous technical preview build numbers and installation guides.
Installing ConfigMgr Technical Preview 2103
To install Configuration Manager Technical Preview 2103 update.
- In the ConfigMgr console, go to Administration > Updates and Servicing.
- Right click Configuration Manager Technical Preview 2103 update and click Install Update Pack.
Ignore the prerequisite check warnings and install the technical preview 2103 update. Click Next.
This is the first time you will see the cloud attach option added to configuration manager updates wizard. The annoying part is it doesn’t allow you to proceed until you sign-in. If you don’t have an account, you cannot install this update anymore.
I also posted this question on twitter asking if there was any way to skip this step and install the update but the answer is NO. In the ConfigMgr Technical preview 2103 documentation I found the answer.
If you opt out of cloud attach during the Updates Wizard, you still need to sign in on the Cloud attach page. It doesn’t enable cloud attach features if you don’t select them, but you can’t continue the wizard unless you authenticate.
Ok so with that note, what I understand is a sign in is must however it doesn’t enable cloud attach features. In my opinion this should have been really an optional step. Alright lets sign in and continue the update installation.
I have signed in with an organizational account. Click Next.
On the Completion window, click Close.
When the updates installs, the last step is to perform the console upgrade. Click OK to begin the console upgrade from version 5.2103.1053.1000 to 5.2103.1057.1000.
If you have installed TP 2103, you should find the following details when you check About Configuration Manager.
- Version 2103 for Technical Preview
- Console version – 5.2103.1057.1000
- Site version – 5.0.9047.1000
SCCM Technical Preview 2103 New Features
Let’s go through some new features that are included with SCCM technical preview 2103 release.
Community hub support for configuration baselines
With ConfigMgr Technical Preview 2103 release, the Community hub now supports contributing and downloading configuration baselines including the child configuration items.
You can also contribute and download the configuration baselines which is also available for current branch versions of Configuration Manager.
Cloud attach during site upgrade
Microsoft has added the cloud attach option during the site upgrade. The same prerequisites apply as for SCCM tenant attach. You can perform the cloud attach when you update the site from technical preview branch version 2102 or later.
New CMG deployments use TLS 1.2
Starting in SCCM technical preview 2103 release, new deployments of the cloud management gateway (CMG) by default enable the option to Enforce TLS 1.2. If you have already setup the CMG, it doesn’t affect. This change doesn’t affect existing deployments. While not recommended, if you need to use the less secure TLS protocol versions, you can still disable this option.
New PowerShell CMDLETS
We have a new PowerShell cmdlet Remove-CMClientSettingDeployment. You can use this cmdlet to remove a specific deployment of a client setting.
Tenant attach: Antivirus policy supports exclusions merge
When a tenant attached device is targeted with two or more antivirus policies, the settings for antivirus exclusions will merge before being applied to the client.
This change results in the client receiving the exclusions defined in each policy, allowing for more granular control of antivirus exclusions.
Looks like the cloud sign-in is a ‘Known Issue’. Hopefully that means MS will fix this by allowing you to continue the install without signing in.
This will cause issues for those of us that have servers that don’t connect to the internet. How are we supposed to get past this hurdle?
Is there a way of changing the cloud attach instance after the fact? I didn’t check either of the two boxes and just signed up for a 30 day trial. I’ve since gotten access to a better account but can’t find anywhere to change the account.