The Complete SCUP 2011 installation and configuration guide
10th June 2011 20:40
The latest version of System Center Custom Updates Publisher 2011 is released and ready for download. SCUP 2011 is a freeware tool from Microsoft that can assist you in authoring and publishing 3rd. party updates to Configuration Manager and System Center Essentials.
To get you started you can download the complete SCUP 2011 installation and configuration guide here I hope the guide can save you a few hours of work and get you up and running with SCUP today.
In my guide I have references to two files used to deploy the needed certificates. Those are:
Certutil.exe and certadm.dll, both files are part of the Windows Server 2003 Administration Tools Pack.
Happy “Scuping”
Subscribe to Kent's RSS Feed
[...] Pour plus d’informations et obtenir le guide, rendez-vous sur : http://blog.coretech.dk/kea/the-complete-scup-2011-installation-and-configuration-guide/ [...]
[...] Read his original post here. [...]
Thanks for the guide.
This PDF is exceptionally helpful and it allowed me to delpoy Java 1.6B26. However I did hit a snag with the 64 bit version of Java as it uses the same registry paths on a 64 os as the 32 bit version of Java on a 32 bit OS. The update would install, however the end result would always report a fail as the evaluation was conducted against the 64 bit version regsitry key as opposed to the 32 bit version of Java held under the SysWowNode key.
Naturalyl the 64 version registry key would not have changed… hence the Fail result.
In the end, I created three updates. 32 bit Java on 32 bit OS (checking key HKLM\Software\Javasoft\Java Runtime Environment\1.6.0_26), 32 bit Java on 64 bit OS (checking HKLM\SOFTWARE\Wow6432Node\JavaSoft\Java Runtime Environment\1.6.0_26) and 64 bit Java (checking HKLM\Software\Javasoft\Java Runtime Environment\1.6.0_26). Each update also had an extra Installable Rule of either x86 or x64.
Hello
I have a 32 bit os and a 32 bit java, but it doesn’t work with Installable Rule (either x86 or x64) and Installed Rule (checking key HKLM\Software\Javasoft\Java Runtime Environment\1.6.0_26). Does anybody have an idea why?
Hi Sandra. I was somewhat premature with my apparent success! I was still unable to get all three variants to work, the 32 bit version of Java on a 64 bit OS is just an utter pig.
What I did in the end was to create a 32 bit Java update for 32 bit OS’s and a 64 bit Java update for 64 bit OS’s. I did hit another major snag, in that sometimes Java would fail to install and then wipe itself. It left a slight footprint in the registry though, so I adjusted the Applicability rule to check higher up the tree.
This has now worked fine for the past 6 months
Applicability x86:
Registry Key ‘HKLM\Software\Javasoft’ exists.
NOT: Registry key ‘HKLM\Software\Javasoft\Java Runtime Environment\1.6.0_31’ exists.
File: ‘C:\windows\system32\ccm\logs\cas.log’ exists
Installed x86:
Registry key ‘HKLM\Software\Java Runtime Environment\1.6.0_31’ exists.
Not sure if anyone is still having a problem with the Java rules for 32 bit and 64 bit but I have managed to come up with a working solution by creating 3 updates with rules, one for 32 bit Java on 32 bit machines, one for 64 bit Java on 64 bit machines and one for 32bit Java on 64 bit machines. This method also allows you to jump from version 6 to 7 as well if required. It might be possible to simplify this by combining the two 32 bit Java installs into one but I was just happy to get it working!
I used the registry folder Wow6432Node to know if it was a 32 or 64 bit machine and to know where to install the correct version. This is how I updated all our machines from various version 6 and 7 Java up to the latest Java 7 Update 13:
32bit Java on 32bit Machines:
Installable Rules:
Registry Key ‘HKLM\Software\Javasoft\Java Runtime Environment’ exists.
NOT Registry Key ‘HKLM\Software\Javasoft\Java Runtime Environment\1.7.0_13′ exists.
NOT Registry Key ‘HKLM\Software\Wow6432Node’ exists.
Installed Rules:
Registry Key ‘HKLM\Software\Javasoft\Java Runtime Environment\1.7.0_13′ exists.
64bit Java on 64bit Machines:
Installable Rules:
Registry Key ‘HKLM\Software\Javasoft\Java Runtime Environment’ exists.
NOT Registry Key ‘HKLM\Software\Javasoft\Java Runtime Environment\1.7.0_13′ exists.
Registry Key ‘HKLM\Software\Wow6432Node’ exists.
Installed Rules:
Registry Key ‘HKLM\Software\Javasoft\Java Runtime Environment\1.7.0_13′ exists.
32bit Java on 64bit Machines:
Installable Rules:
Registry Key ‘HKLM\Software\Wow6432Node\Javasoft\Java Runtime Environment’ exists.
NOT Registry Key ‘HKLM\Software\Wow6432Node\Javasoft\Java Runtime Environment\1.7.0_13′ exists.
Installed Rules:
Registry Key ‘HKLM\Software\Wow6432Node\Javasoft\Java Runtime Environment\1.7.0_13′ exists.
I hope this helps anyone that is still having a problem with getting Java to install across 32 and 64 bit machines.
I am using WSUS 3.0 SP2, SCUP 2011 and Local Update Publisher in replace for SCCM which is just overcomplicated if you just want it for deploying updates.
Thanks Kent.
Your guides helped me a lot.
Regards,
Ben.
[...] Coretch, que tem um guia excelente para a configuração, preparação e integração com SCUP com o ConfigMgr. [...]
Kent, Im having problems to get SCUP to connect to remote ConfigMgr Site server to validate connection in SCUP setup wizard in Configuration Manager Integration section.
Error message says to verify that current user has REQUIRED access. Im not sure what that required access is. Is it on dB layer or should be added to some local group?
thanks for reply.
Right click and run scup as admin.
Do I need Configuration Manager 2007 in order to run SCUP 2011?
Is there any specific reason to use SCCM package to distribute WSUS publisher certificate? Isn’t it easier to just add it to the same GPO where we allow signed custom updates?
Andrew,
No, there is no specific reason except that I (as a consultant) often do not have access to AD and GPO’s.
[...] [...]
Hi Kent,
first, thanks to this post.
In our company we want to update our HP Servers (HP ProLiant DL380 G6/G7/Gen8) with SCUP 2011.
But it seems that HP does not update their “proliant.cab” file (Download: ftp://ftp.hp.com/pub/softlib/software10/COL25555/sy-65640-1/ProLiant.cab).
The latest version is from 25/06/2012 which means since that date, all drivers and firmware are not included/available.
There is no statement from HP about that.
With this fact, it makes no sense to use this great tool.
Do you know, if HP is still “supporting/concerning” SCUP or is there another utility where we can reach my aim?
Thanks for you support.
Kind regards Haecki
In the guide when you do the second Test Connection against the server does the same warning about the certificate appear? If so could you update your documentation to reflect this. It is important to know because I keep getting that error. If it doesn’t give you the error then I’ll re-re-re-review the information.