Now that Updates Publisher 2011 has released, you may ask yourself what do I need to do to install and configure. Here is a high level to do list to help you get started.
I hope this get everybody started, look for screencasts coming soon covering the entire product.
Chris Nackers has a quick installation guide (with screenshots!)
is SCUP 2011 only in 32bit?
cant seem to fnd a 64bit version?
SCUP 2011 is both x86 and x64. It will install into the x86 folder since there is a single MSI install (which is 32bit based) but when runing SCUP you will see it is running as a 64bit application.
Is the any way to change the path of database file "scupdb.sdf" ? Previous version SCUP allows me to manage updates from any workstation or server. How about that functionality in current version SCUP?
You can try to manually edit the Scup2011.exe.config file (may need to elevate rights) in the installation directory and change the value of the "SSCEDataFile" setting to the location you would like to store the datafile then manually move the datafile to that location. However, manually editing the config file is unsupported.
Note #1 - If any other users log into this computer and run Updates Publisher 2011 they will not get their own database and would instead use the same database that was defined in the config file.
Note #2 - Also note that Updates Publisher 2011 does not support multiple users using the same Updates Publisher or datafile at the same time.
One another question. Does SCUP 2011 support Windows XP or Windows 2003 Server ?
Updates Publisher 2011 only support Windows Vista, Windows 7, Windows Server 2008 and Windows Server 2008 R2. One thing to point out is that Updates Publisher does not need to be installed on the WSUS or ConfigMgr Site System computers, it can be on a desktop and publish to a remote WSUS Server.
The create cert option appears to create a cer, but I cannot find or browse for an exisiting one. I did try to run the application as an admin, but still no luck finding the *.cer. Is this a bug?
It seems that SCUP 2011 lost great functionality. When I duplicate package and edit a new software update and change package source I also lost installable and installed rules and I have to create from the scratch.
Previous SCUP allows you to keep a rules.
The browse and remove buttons are disabled when connected to a remote WSUS server unless connected by SSL as the communication channel must be secure when working with the signing certificate. You are able to create the certificate, but are not able to use your own unless connected by SSL or running locally.
This functionality is by design as we have found problems after duplicating an update from using incorrect rules from the previous update. If you want to use the same rules you now have the ability to save the entire rule set and then add that rule set to you new or duplicated update.
Can i somehow use SCUP 2011 to publich MSU files to WSUS / SCCM?
SCUP 2011 does not support deploying MSU based files. The recommended solution is use Software Distribution to deploy those file types.
Can KB2530678 be installed on all WSUS servers within the hierarchy or only those that currently have .Net 4.0 and WSUS SP2?
I have dozens of WSUS servers that will all be WSUS SP2 however not all will likely have .Net 4.0 currently installed. Ideally I would like to just deploy the hotfix to all WSUS servers and not have to be selective for only those with .Net 4.0 installed which would require followup should .Net 4.0 get installed at a later date.
The update can only be applied to WSUS 3.0 SP2. .Net Framework 4.0 is not a requirement.