Forums on Intune, SCCM, and Windows 11

Welcome to the forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your topics and posts, as well as connect with other members through your own private inbox!

SOLVED SCCM 2409 upgrade fails at install files step

  • Thread starter Thread starter psanaga
  • Start date Start date
  • Replies Replies 30
  • Views Views 9K
Status
Not open for further replies.

psanaga

Member
Messages
18
Solutions
1
Reaction score
2
Points
3
Hi,
I have been trying to install the v2409 update, with no luck in Air-Gap environment using ServiceConnectionTool.
I am able to download the updates, transfer files and import to SCCM server without any issue.
After importing to SCCM, able to download, Ran pre-req check(passed - All Green) and Installed Update pack, then it failed at Install Files. Please find the attached screenshot.

I have rebooted the server.
I have used cmupdatereset to try and reset / download the update.

Any help would be appreciated

Pratap
 

Attachments

  • Install Files Error.png
    Install Files Error.png
    67.3 KB · Views: 31
Solution
Solved the issue. Using the tool on a device with internet seems not to be sufficient.

In my POC lab I used the online ConfigMgr for downloading the files. When I used a VM I got the same errors during the download of the redist files.

Today I did the same in the environment of my customer. When I transfer the files to the online configuration manager server and run the tool from there, the download is OK.

Long story short:


You need to install the ODBC requirement also on the device with internet. This is also the case if you run setupdl.exe up...
I believe that it is failing because you are air gapped. The upgrade needs the internet to check for any missing components and download them. I would recommend connecting this server to the internet, perform the upgrade(s), and then disconnecting it from the internet.
 
I believe that it is failing because you are air gapped. The upgrade needs the internet to check for any missing components and download them. I would recommend connecting this server to the internet, perform the upgrade(s), and then disconnecting it from the internet.
Isn't no solution for air gap environment!!
I do upgrade earlier using "Server Connection Tool" option from 2211 to 2309 and now trying same from 2309 to 2409 but this time didn't work.
I can't connect to internet even for small amount of time to get rid of this problem, that's a very strict requirement not to connect to internet.
 
Isn't no solution for air gap environment!!
I do upgrade earlier using "Server Connection Tool" option from 2211 to 2309 and now trying same from 2309 to 2409 but this time didn't work.
I can't connect to internet even for small amount of time to get rid of this problem, that's a very strict requirement not to connect to internet.
Then I am not sure how we can help you. No offence intended but SCCM needs the internet to download the setup files and anything it needs to upgrade.

IMHO, running on air gapped does not make much sense to me. Sorry. Just sharing my opinion.
 
Then I am not sure how we can help you. No offence intended but SCCM needs the internet to download the setup files and anything it needs to upgrade.

IMHO, running on air gapped does not make much sense to me. Sorry. Just sharing my opinion.
Np.. Got it, Thanks AaronZ.
mean while i keep continue working and will update this thread once i have the solution.
 
Np.. Got it, Thanks AaronZ.
mean while i keep continue working and will update this thread once i have the solution.
Airgapped is fully supported:

'
  • In online mode, the service connection point automatically connects to the Microsoft cloud service and downloads applicable updates.

    By default, Configuration Manager checks for new updates every 24 hours. Manually check for updates in the Configuration Manager console. Go to the Administration workspace, select the Updates and Servicing node, and choose Check for Updates in the ribbon.
  • In offline mode, the service connection point doesn't connect to the Microsoft cloud service. To download and then import available updates, use the Service Connection Tool.
'

I'm having the same issue in an airgapped environment. Also with the 2503 upgrade.

Already contacted with Microsoft to check what can be done. Will keep you posted if they have a solution for this issue.
 
Airgapped is fully supported:

'
  • In online mode, the service connection point automatically connects to the Microsoft cloud service and downloads applicable updates.

    By default, Configuration Manager checks for new updates every 24 hours. Manually check for updates in the Configuration Manager console. Go to the Administration workspace, select the Updates and Servicing node, and choose Check for Updates in the ribbon.
  • In offline mode, the service connection point doesn't connect to the Microsoft cloud service. To download and then import available updates, use the Service Connection Tool.
'

I'm having the same issue in an airgapped environment. Also with the 2503 upgrade.

Already contacted with Microsoft to check what can be done. Will keep you posted if they have a solution for this issue.
Thank you so much Peter.
 
In the same boat here updating to 2503- file version error on the NDP package. @psanaga- this thread has been marked as Solved, did you find a way through the issue?
 
Still in contact with Microsoft for this issue. If there is a known solution, I will share it here.

Setup a poc environment. Except from starting from 2403 and not 2203, there is no difference. The upgrade succeeds.

Need to check the staging directory for the redist files. In the poc, the file hash was checked from this folder and the setup continued.
 
Still in contact with Microsoft for this issue. If there is a known solution, I will share it here.

Setup a poc environment. Except from starting from 2403 and not 2203, there is no difference. The upgrade succeeds.

Need to check the staging directory for the redist files. In the poc, the file hash was checked from this folder and the setup continued.

I have run into this issue a couple of times when trying to download the offline bits. What I have noticed is in the folders that get created there is a sub folder redist and it is empty. This is why we are getting the error message when it is looking for those files.

I was able to this issue resolved by using an older serviceconnectiontool from 2107 build and use the downloadall flag. Hope this helps you all out. The download is just shy of 40GB sadly, but it allows doe the redist folders to be populated correctly.
 
Solved the issue. Using the tool on a device with internet seems not to be sufficient.

In my POC lab I used the online ConfigMgr for downloading the files. When I used a VM I got the same errors during the download of the redist files.

Today I did the same in the environment of my customer. When I transfer the files to the online configuration manager server and run the tool from there, the download is OK.

Long story short:


You need to install the ODBC requirement also on the device with internet. This is also the case if you run setupdl.exe up front of a new installation.
 
Solution
Status
Not open for further replies.

Forum statistics

Threads
7,061
Messages
27,592
Members
17,830
Latest member
hitchingsb
Back
Top