Introduction
I noticed the following on Twitter announcing yet another release of ConfigMgr,
this time version 2503, with hundreds of amazing new features, oh wait, no that was bugfixes.
The 350 bugs identified and fixed bit is explained in the post below:
I guess this blog post is for bug #351 but here we go.
Upgrade time
I decided to upgrade my lab using the early ring script available from here.
And once it was downloaded I ran the prerequisite checker. It wasn’t a happy bunny. the failure was:
[Failed]:Install the Microsoft ODBC driver 18 for SQL setup from https://go.microsoft.com/fwlink/?linkid=2220989
After attempting to install the MSI from that link if failed as a newer version was already installed.
Next, I looked at the the C:\ConfigMgrPrereq.log file which contained some more details about the actual failure along with not one, but two urls.
The first URL linked to another (newer) ODBC driver which I installed, and this time, the prerequisites checker was happy.
my buddy Johan Arwidmark checked the two ODBC drivers from those urls and concluded that the newer one was version: 18.4.1.1
After sorting out my prerequisites issues I installed the update, and it installed without any further problems. Not only that, but now I no longer have two Configuration Manager 2409 installs staring at me when I launch the console :-).
To summarize the ODBC client versions:
- https://go.microsoft.com/fwlink/?linkid=2220989 – bad ODBC client
https://go.microsoft.com/fwlink/?linkid=2299909 – good ODBC client
https://go.microsoft.com/fwlink/?linkid=2226618 – more info
Untrusted certificate
After the upgrade I tested PXE boot and it did not work. I checked the SMSPXE.log file and it had a load of interesting certificate errors even though no I have expired certs in my PKI infrastructure or on the DP.
This lab was definitely free of certificate issues as I recently re-issued them, and verified they were all happy prior to starting the upgrade, so this was an odd error.
a reboot solved it.
PXE password getting set if none set ?
I’ve had several people contact me saying that PXE was enabled on their DP post upgrade where none was set. I had mine set so couldn’t replicate this in my lab. If you encounter this issue let me know. The fix is a new hotfix available in the console (KB32480179, released on the 23rd of April. Thanks Holger (in the comments below) for the heads up.
until the next time !
cheers
niall
After updating our primary site to 2503 no configuration item can be created.
Error: Not found . property = SDMPackageXML
SQL Server 2016
Applications cannot be created: Invald operation
Microsoft had fixed 350 bugs but implemented (of course) new one.
Anyone have an idea, maybe?
Thanks!
did you use the fast ring script to get the upgrade or are you using the latest (GA) version ?
No, was released yesterday globally.
But, a reboot after the update and after like 1 hour the issue is gone
I’m glad it’s working for you, I also noticed some oddities in my site before rebooting the primary
PXE now requere password
its a bug.
you are the second person that has reported this, i didnt see it as i already had a password set on the dp.
have you tried setting a new password on the dp, then apply, then remove it ?
Thank you for this. This is the only place I’ve seen mention of this bug. I can now confirm this issue as well. I was unable to PXE boot to the task sequence wizard after upgrading to 2503 and did not have a PXE password set.
After adding a PXE password, the device booted and presented me with the Task Sequence Wizard. Removing the password requirement just re-introduces the issue for me.
hi Justin
please apply the hotfix that I show in the console above, that will hopefully fix it (for fast rings at least)
I have the PXE requiring a password now too.
I have tried to setting a password, and afterwards removing it again, but that “fix” is not working for me…
interesting,
so can you tell me are you on the fast ring version of 2503 or did you go with the slow ring (GA release) ?
I enabled fast ring.
But it was the day before the slow ring was released to the world, so maybe I was too quick?
Hi again!
Yeah, isn’t it weird?
I enabled fast ring the day before it was released to GA… Bad luck i guess…
But i would still like to have the issue resolved. Do you have any ideas?
so do you have one or more dp’s ?
i can try and replicate in my lab…
I only have 1 DP, which is on my primary
The SCCM 2504 hotfix, KB32480179, released on the 23rd of apriol fixed the problem for me. It turned up today in my SCCM console and figured that installing it wouldn’t hurt. So know you know.
awesome, thanks for sharing !
Configuration Manager 2503 needs ADK 10.1.26100.2454 (Updated Dec 2024) and corresponding ADK-PE otherwise Tasksequence will not start any more.
We still had the ADK 10.1.26100.1 from May 2024 installed when we updated the Configuration Manager to 2503. After that our Task Sequence did not load any more. Solution was to Install the new ADK 10.1.26100.2454 from December and build an new PE from the December ADK and change it in the Task Sequence. After that everything worked as normal.
After upgrading to ConfigMgr 2503, we also had problems starting the task sequence. After building a new WinPE boot image and including the necessary drivers, the task sequence started properly. We use ADK 10.1.2600.1 from May 2024.