Friday, June 13, 2014

SCCM 2012 Limited Support on IPv6

SCCM 2012 is not fully support on IPv6 yet. Below are some of the features that are not IPv6 ready. I was working on OSD and randomly getting error “Failed to download policy” with generic error code 0x80004005. I opened a case with Microsoft and the engineer find out that SCCM 2012 is not fully ready on IPv6 yet. We disabled the IPv6 configuration from the server and the error seems to went away.

image

Technet reference:

  1. http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigIpv6
  2. http://technet.microsoft.com/en-us/network/hh994905.aspx

Tuesday, June 10, 2014

Moving, Changing, Migrating, Restoring of your SCCM 2012 SQL Database?

Are you performing any one of the actions above to your SCCM 2012 SQL database? After you did that, please make sure that the new SQL server configuration is correct. Especially the Allow Snapshot Isolation, Is read Commited Snapshot On, Trustworthy, Broker Enabled. and Honor Broker Priority settings. All these settings need to be set as TRUE. If these settings are not configured correctly, you might end up getting errors “Microsoft SQL Server Reported SQL Message 50000, Severity 16: *** Unknown SQL Error!” from SMS_POLICY_PROVIDER Component or this error. Please also ensure that the owner of the database is SA!!!

image 

image
To alter the settings above:

ALTER DATABASE <CM_XXX>
SET ALLOW_SNAPSHOT_ISOLATION ON

ALTER DATABASE <CM_XXX>
SET READ_COMMITTED_SNAPSHOT ON

--- Enable the SQL Broker on the Site database

USE master;
GO
ALTER DATABASE CM_XXX SET ENABLE_BROKER
GO

--- SET the Site Database as trustworthy

USE master;
GO
ALTER DATABASE CM_XXX SET TRUSTWORTHY ON
GO

--- SET the Database to honor the HONOR_BROKER_PRIORITY

USE master;
GO
ALTER DATABASE CM_XXX SET HONOR_BROKER_PRIORITY ON;
GO

image
To change the owner to “sa”
EXEC sp_changedbowner ‘sa’

Thanks for reading…

References:

  1. http://blogs.technet.com/b/configurationmgr/archive/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server.aspx
  2. http://support.microsoft.com/kb/2709082/en-us

Monday, June 2, 2014

SMS WSUS Configuration Manager failed to configure upstream server settings on WSUS Server

Lately, I helped a customer to check the WSUS error above on SCCM 2007 mixed mood environment.

First thing I did is to check WCM.log. From the log I found out that the server is using ParentWSUSPort = 8531, SSLToParentWSUS = 1. Usually for mixed mood environment, the server will use Port 8530 and without SSL.

The next thing I did is to check the Software Update Point Component settings. On the General tab of the settings, the Enable SSL for this WSUS server is uncheck by default, but somehow this is now checked.

So I UNCHECK the Enable SSL for this WSUS server setting and apply the settings. Next, I delete the Software Update Point and reinstall it once after it is deleted. After the reinstallation of the Software Update Point, the SCCM server can now sync the latest updates from Microsoft and the WCM.log is showing that the server is using ParentWSUSPort = 8530, SSLToParentWSUS = 0