If you are not able, or don’t want to use SCUP as a solution to install the console hotfix, you could make an application of the hotfix instead. With this solution, you only need to deploy the hotfix application, and the console will be fully installed. Below, I will explain all the necessary steps.
1.You need to create an application for .NET Framework 4. (this is necessary for the console)
Create a DeploymentType with commandline: dotNetFx40_Full_x86_x64.exe /q /norestart /ChainingPackage ADMINDEPLOYMENT
For detection method, use the following:
No requirements or dependencies needed.
2. You need to make an application of the SCCM 2012 R2 console. Use adminconsole.msi & consolesetup.exe as sourcefiles.
The sourcefiles for the Adminconsole are located on the Primary Site Server in the Configuration Manager installation folder under Tools\ConsoleSetup.
Create a new application.
Enter general info for the app. Press next until you need to configure Deployment Types. Click Add.
Select Script Installer.
Select a content location for the sourcefiles and specify the install cmd: consolesetup.exe /q TargetDir=C:\ConfigMgrConsole EnableSQM=0 DefaultSiteServerName=sccm.network.int
Uninstall cmd: Consolesetup /uninstall /q
3. Create an application of the Console hotfix.
Use Configmgr2012adminui-r2-kb2905002-i386.msp as sourcefile.
Installation program: msiexec.exe /p configmgr2012adminui-r2-kb2905002-i386.msp /L*v %TEMP%\configmgr2012adminui-r2-kb2905002-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous
uninstall cmd: Consolesetup.exe /uninstall /q
Make sure you distribute all the content to your Distribution Points. Now you can deploy the Console application hotfix, made in step 3. The system will check if the R2 console has been installed along with Netfx4. After that, it will apply the hotfix.
You can easily check the version of CreateTsMediaAdm.dll on the destination pc, to make sure the hotfix has been applied. Browse to the installation folder of the console: .\Bin\I386\CreateTsMediaAdm.dll