I thought that some bugs will be fixed during the time. Ok, sometimes it happens with a new KB :-).
Today I had to upgrade a 2012 R2 ConfigMgr Server to 1606 and then 1610. 1606 is not an big deal as you have the baseline ISO for that. After that you will receive the 1610 in the console. But it hangs still with the status “Downloading”.
As one solution you will find to restart the SMS_Executive. But with restartig the service you won’t still be able to install the CB 1610. Restarting the SMS_Executive restarts also the SMS_DMP_Downloader and you can follow the process using the dmpdwonloader.log under the log folder from your Primary Site server.
In that log you recognize that some cab files can’t be downloaded. All sources will be downloaded to the CM “Program Files\Microsoft Configuration Manager\EasySetupPayload” folder. The log shows you the download link of the mssing root cab file and also the used proxy server. Copy that link to your preferred browser link bar and download the cab file. Place it in the EasySetupPayload folder. – Restart SMS_Executive. The download will continue after 1-2 minutes.
In my case was ConfigMgr not able to download all the prereq tools to the “redist” folder. Some where Ok, but not all. 14 tools where still missing. If you have the same issue, navigate to \EasySetupPayload\”extractedCABName”\SMSSETUP\BIN\x64 and run setupdl.exe to download all the Prereq tools. You can directly download the contet to the \EasySetupPayload\”extractedCABName”\redist folder.
Restart the SMS_Executive Service again. The Configuration Manager 1610 Update should now switch to the status Available.
Have fun installing 1610.
Today I got a support case where I had to restore my first ConfigMgr Current Branch 1602.
No prob, we do have a nice SQL DB backup of the ConfigMgr database.
Let’s do the following:
- Close all consoles
- Stop all SMS Services (will also be done by the recovery wizard)
- Start the setup.exe from the CD.Latest (“Your Install Directory”\Microsoft Configuration Manager\cd.latest\SMSSETUP\BIN\X64)
But here I got stock. The “Recovery Site” option was greyed out. Of course I tried different ways to start the splash.hta or the setup.exe using admin rights. No way. The option was never available.
During research I found that the Site Maintenance job in ConfigMgr is also creating a folder called CD.Latest. But the customer did never activate the Site Maintenance job as they use a third party backup solution to backup the SQL Databases.
However, I configured the Site Maintenance Task and started the SMS_SITE_BACKUP service. This was creating the CD.Latest folder under my backup folder.
With this version of the setup.exe file could restore the database .
What we did:
– Stopped all services
– Detached the no longer needed CM_”SiteCode” database from the SQL Server using the SQL Server Management Studio
– Restored the good database from Sunday (used the SQL option “override existing files”)
– Started CD.Latest from the newly created backup folder (F:\Backup\W01Backup\CD.Latest)
– Used “Site Database that has manually recovered” as we restored it in SQL
Please be aware of a very important change required to your backup strategy in Configuration Manager 1511, 1602 (and later). As you know regular upgrades will be available for the product (every 4 months or so) and you will be able to upgrade using update packages in the “Updates and Servicing” node of the Administration > Cloud Services workspace.
– Make sure you enable the “Site Maintenance” Job for the site.
– Backup the Backup folder as this will allow you to restore the ConfigMgr 1602 server in case of a bare metal restore
This folder will be required when you are recovering a failed site so it must be included in a backup strategy. Note that the built in backup maintenance task will back up this folder automatically. Also note that there is no point in backing up this folder once. It must be ongoing because, when upgrades are installed, Configuration Manager also updates the CD.Latest folder with the current files.
Find more informations on TechNet: