Moving the SCUP database after installation

After installing System Center Updates Publisher (SCUP) 2011 configuration must be done. SCUP can be connected to a WSUS or SCCM/ConfigMgr 2007 and/or 2012 installation. Just use Update Server or ConfigMgr Server for that. Something else that must be done is moving the SCUP database. This because the database is placed in the active user profile. Oops! In this blogpost I will explain (in a few steps) what must be done.
 

 

By default the SCUPDB.SDF is placed in the [C:\Users\<username>\AppData\Local\Microsoft\System Center Updates Publisher 2011\5.00.1727.0000] folder. This can be checked at Advanced options. To move the database just close the SCUP console. Open the Scup2011.exe.config file, which can be found in the SCUP installation folder.
 

For example: Beneath <Scup.Properties.Settings> and <setting name="SSCEDataFile" serializeAs="String"> add the following line:

<value>D:\SCUP2011\5.00.1727.0000\scupdb.sdf</value>



This way the database is expected on another location. Just move the SCUPDB.SDF file to the same location configured in the Config file. After configuring both steps start the SCUP console again. Have a look at Advanced options again, and see above results. The database is moved to a better place now!

Integrate System Center Updates Publisher (SCUP) 2011 with ConfigMgr

With System Center Configuration Manager (ConfigMgr) and WSUS integrated, it's possible to install and use System Center Updates Publisher (SCUP) 2011 also (free usage). With SCUP 2011 you can create and install packages that's not in WSUS by default. That way updates from DELL, HP and ADOBE (for example) can be used in your existing WSUS installation for deploying to clients. By default there are some catalogs that can be imported in SCUP 2011. Manually created packages from JAVA (for example) can be used also.

First download and install SCUP 2011 from the following website:
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=11940
Microsoft DotNet 4.0 is needed on the server to have SCUP 2011 installed.

After that install the following hotfix on the server (needed for the Signing certificate):
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=20689 (x86)
or http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=12390 (x64)

When SCUP 2011 is installed successfully choose Options. Choose "Enable publishing to an update server" and create an Signing certificate also. On the next tab select "Enable Configuration Manager integration". Now open a Management Console with the Certificates component in it.

The Signing certificate created will be available in the WSUS Certicate folder after configuraton. Choose copy, and past in on both "Trusted Root certification" and "Trusted Publishers". There is also the choice to save a local copy from it. That way it can be published bij Group Policy if needed for client computers. The Management Console can be closed after that.

Best thing now is to reboot the server, and open the SCUP 2011 console again. Now it's time to import the default catalogs and create additional packages yourself. After synchronization these updates will be available in ConfigMgr. Just select the updates needed, choose Assign and Publish to create them. When synchronization with WSUS is done, they will be available in ConfigMgr.

Kent Agerlund, ConfigMgr MVP, wrote a great getting starting guide to System Center Updates Publisher 2011 up on his blog. Check it out here
http://blogs.technet.com/b/jasonlewis/archive/2011/06/13/scup-2011-installation-amp-configuration-guide.aspx

Integration with Configuration Manager 2007/2012

With System Center Configuration Manager (ConfigMgr) 2007 there is many functionality available by default. With ConfigMgr 2012 this becomes even better, even MORE functionality will be in it. With both solutions there is the possibility to extend ConfigMgr with additional functionality. In this blog I will describe the most important ones.

Microsoft Deployment Toolkit (MDT) 2010: Adding new Task Sequences, new options in Task Sequences, new Boot images and all build-in scripts in ConfigMgr. Have a look at this blogpost(s) for more information about this:
http://henkhoogendoorn.blogspot.com/2010/12/mdt-integration-in-configmgr-2007.html
http://henkhoogendoorn.blogspot.com/2011/06/microsoft-deployment-toolkit-mdt-2010.html

Application Virtualization (App-V): Adding App-V streaming functionality in ConfigMgr, so no App-V Management and/or Streaming server is needed anymore. Just publish and update App-V packages from within the ConfigMgr console! Have a look at this blogpost(s) for more information:
http://henkhoogendoorn.blogspot.com/2010/12/configmgr-2007-with-app-v-integration.html
http://henkhoogendoorn.blogspot.com/2011/06/configmgr-2012-beta-2-with-app-v.html

ForeFront Endpoint Protection (FEP) 2010: It is possible to fully manage ForeFront from within the ConfigMgr console. Just deploy the ForeFront clients and manage policies with ConfigMgr. Definition files can be downloaded with WSUS integration in ConfigMgr. More about that on TechNet: http://technet.microsoft.com/en-us/library/cc161958.aspx

User State Migration Tool (USMT) 4.0: With USMT it is possible to store files and/or settings during OS deployment migrations. With hard-link migration it is possible to migrate user accounts, files and settings in less time using megabytes of disk space instead of gigabytes. More about that can be found here: http://technet.microsoft.com/en-us/library/dd560752(WS.10).aspx

Windows Server Updates Services (WSUS): Manage Software updates in ConfigMgr instead of WSUS, with even more control during installation. That way all management can be done in one single console, and additional ConfigMgr functionality as Maintenance Windows can be used. Have a look at this blogpost for this:
http://henkhoogendoorn.blogspot.com/2011/04/patch-management-in-configmgr-2012-beta.html

System Center Updates Publisher (SCUP) 2011: When ConfigMgr and WSUS is used (both together), SCUP can be installed for non-Windows patches. That way patches from HP, Dell, Adobe and Java (for example) can be managed and deployed in WSUS integration in ConfigMgr! How to setup, is explained here: http://blogs.technet.com/b/jasonlewis/archive/2007/11/30/how-to-setup-scup-and-configmgr-2007-to-deploy-custom-updates.aspx

System Center Configuration Manager 2007 Toolkit V2: The Configuration Manager 2007 Toolkit V2 contains 11 downloadable tools to help you manage and troubleshoot Configuration Manager 2007. It can be downloaded here: http://www.microsoft.com/download/en/details.aspx?id=9257

Right Click Tools or SCCM Console Extensions: The Right Click Tools or SCCM Console Extensions installation adds additional functionaly for server and client management. It becomes very handy during management and troubleshooting. More information can be found here:
http://myitforum.com/cs2/blogs/rhouchins/archive/2008/04/09/sccm-right-click-tools.aspx
http://myitforum.com/cs2/blogs/direland/pages/sccm-console-extensions.aspx

System Center Client Center: This tool is designed for IT Professionals to troubleshoot SMS/SCCM Client related Issues. The SCCM Client Center provides a quick and easy overview of client settings, including running services and SCCM settings in a good easy to use, user interface. Download it here:
http://sourceforge.net/projects/smsclictr/

With these tools more possiblities becomes available in ConfigMgr. Hopefully you have experienced new ideas with these products, and maybe more enthousiastic now to extend ConfigMgr functionality! Stay tuned for more later.