Monthly Archives: August 2012

Disk Cleanup Is Missing On Windows Server 2008 R2

Windows Server 2008 R2 doesn’t include the Disk Cleanup tool by default.   Either install the Desktop Experience feature, which requires a reboot, or copy

C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe

to

%systemroot%\System32

and

C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui

to

%systemroot%\System32\en-US

To start Disk Cleanup type cleanmgr.exe at the command prompt.

Upgrading System Center Operations Manager 2007 R2 To 2012

I needed to upgrade System Center Operations Manager (SCOM) 2007 R2 running on Windows Server 2003 x64 with SQL Server 2005 to System Center Operations Manager 2012.  All SCOM components and SQL Server were installed on the same server.  These are the steps I followed.

  1. Upgrade the drivers and firmware on the server to the latest versions
  2. Backup the SQL databases
  3. Install SQL Server 2005 SP4
  4. Upgrade Windows Server 2003 x64 to Windows Server 2008 R2 SP1
  5. Install the server drivers for Windows Server 2008 R2
  6. Install  SCOM 2007 R2 Cumulative Update 6 (CU6), the latest available update at the time of writing http://support.microsoft.com/kb/2626076
  7. Follow the instructions to enable the SQL Server upgrade to work successfully http://technet.microsoft.com/en-us/library/dd789004.aspx.  This fixes the “No Custom Security Extensions” and “No Custom Authentication Extensions” errors when upgrading SQL Server.  For CU6, SRSUpgradeTool.exe can be found in C:\Program Files (x86)\System Center 2007 R2 Hotfix Utility\KB2449679\SupportTools\amd64
  8. Upgrade SQL 2005 to SQL 2008 R2
  9. Run the SRSUpgradeTool.exe PostSQLUpgrade step
  10. Run the SRSUpgradeHelper program step
  11. Install SQL 2008 R2 SP1
  12. Uninstall SQL 2005 Management Tools
  13. Follow the steps here to upgrade SCOM to 2012 http://technet.microsoft.com/en-us/library/hh205978
  14. Update SCOM 2012 to the latest update rollup, at the time of writing this is System Center Update Rollup 2 http://support.microsoft.com/kb/2706783
  15. Change the SCOM databases to run in SQL 2008 compatibility level http://support.microsoft.com/kb/2700028
  16. If you only have one Management Server, add the registry keys detailed here to fix the “The All Management Servers Pool has not reported availability” error http://support.microsoft.com/kb/2714482
  17. Add the license key to convert the evaluation edition to the full edition.  Run Set-SCOMLicense –ProductID <XXXX> from the Operations Manager Shell
  18. Restart the System Center Data Access Service on all management servers to pickup the license change

SQL Server 2008 R2 Management Tools Installation Fails

Leave a reply

When installing the management tools for SQL Server 2008 R2 I received “SQL Server Setup has encountered the following error: “Unknown property.”

Looking on the web indicated that SQL Server Compact 3.5 could be causing the issue.  Programs and Features showed SQL Server Compact 3.5 was installed, but I couldn’t uninstall, or repair the installation.

I downloaded the installation files here http://www.microsoft.com/en-us/download/details.aspx?id=5783  The installation instructions state that on a 64-bit computer you have to install the 32-bit and 64-bit versions of the files.  Having installed both SSCERuntime_x86-ENU.msi and SSCERuntime_x64-ENU.msi I successfully re-ran the SQL Server 2008 R2 management tools installation.  Both the 64-bit and 32-bit versions of SQL Server Compact are now listed in Programs and Features.

 

UPDATE 08/08/13

I’ve found that in some cases the Microsoft SQL Server Compact 3.5 SP2 x86 (SSCERuntime_x86-ENU.msi) installation can fail.  In this case, open Registry Editor, navigate to HKEY_CLASSES_ROOT\Installer and search for the key relating to Microsoft SQL Server Compact 3.5 SP2 x86.  Backup the key and delete it from the registry.  The installation should now complete successfully.

SharePoint Web Part Error – The Specified Solution Was Not Found

If you develop, release and add a SharePoint 2010 sandboxed solution web part to a page, then change the web part type to non-sandboxed you may see the error: ” Web Part Error: The request could not be completed because the specified solution was not found”.

Just edit the page, delete the web part, then re-add the web part to the page.  This fixes the error.

SharePoint 2010 Menus Hidden Behind Silverlight Web Part

During the development of a Silverlight web part for SharePoint 2010, I found that the drop down navigation menus were hidden behind the web part.

To fix the issue, set the z-index to 0 and add a parameter for windowless and set the value to true.