Superb information from Jason Sandys in relation to ConfigMgr 2012 upgrade to SP1. Well worth checking out:
It seems that there is a possible issue when applying Windows Server 2008 R2 SP1 which effects Remote Desktop Connections.
I won’t go into the full details as a lot of information exists around it on technet forums (essentially the issue is linked to the installation of SP1 when the hotifx kb2667402 is present: http://support.microsoft.com/kb/2667402).
There are quite a number of different documented fixes for this, some of them weird and wonderful.
I came accross the issue on a few servers which are hosted remotely and therefore could not easily resolve ‘by hand’.
It can be fixed remotely by means of running the following command (to uninstall the hotfix):
wmic /node:<servername> process call create “powershell wusa /uninstall /kb:2667402 /quiet /forcerestart”
You can now access the server by RDP and re-apply the hotfix kb2667402 again if desired, without any problems.
SCCM / ConfigMgr 2012 How to Change the SQL Server Collation without Reinstallation of SQL Server (2008 R2)
One of the things that is distinctly different when installing ConfigMgr 2012 as opposed to it’s 2007 predecessor is that the SQL instance that the ConfigMgr database is hosted on, must be configured with a SQL collation of
Now then, if you’re like me and you are used to installing SQL Server for ConfigMgr and just hitting the ‘next’ button when prompted with the SQL Server Collation type then it is quite possible that you have run through the ConfigMgr 2012 Assess Server Readiness tool you are currently face to face with this little baby:
Required SQL Server Collation; Error; Configuration Manager requires that you configure your SQL Server instance and Configuration Manager site database (if already present) to use the SQL_Latin1_General_CP1_CI_AS collation, unless you are using a Chinese operating system and require GB18030 support. For information about changing your SQL Server instance and database collations, see http://go.microsoft…./?LinkID=234541. For information about enabling GB18030 support, see http://go.microsoft…./?LinkId=234542.
At this point it is worth mentioning at this point that I am no SQL DBA. I don’t believe that the workaround below causes any issues, certainly if you are yet to attach any user databases (live databases that are not the default DBs) then this method works fine. If you do have live databases on the server then it goes without saying do not use this method without reviewing the necessary steps documented on the links below. I am performing these changes in my lab so it is low impact.
In my case I have installed SQL 2008 R2 (with the incorrect collation at this point), and I have a new WSUS DB present, as well as the SQL Reporting Services databases. Going ahead to rectify this using a command line, here are the steps I performed in order to change the collation to the correct type that SCCM 2012 requires.
Launch the command prompt and run the SQL 2008 R2 setup again, using the following command:
Setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts [/SAPWD= StrongPassword ] [ /SQLCOLLATION=CollationName]
So in my case, the command was:
setup.exe /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=MSSQLSERVER /SQLSYSADMINACCOUNTS=”NT AUTHORITY\SYSTEM” ”BUILTIN\ADMINISTRATORS” “LAB\ConfigMgrAdmin” /SQLCOLLATION=SQL_Latin1_General_CP1_CI_AS
This link provides some great info around the parameters of the command:
The command should take a minute or so to complete.
If you did have any databases attached such as WSUS or Reporting Services, as did I, then you will now need to re-attach these databases, as they will have been dropped. Launch SQL Management Studio > Right-click ‘Databases’ > Select ‘Attach’
Browse to each database and attach them.
You should be good to go now. You can check the collation of SQL Server by right-clicking the server name in the Management Studio console, selecting properties.
Just thought I’d put up a quick post about (what I think is) a fantastic tool, and incredibly useful for any ConfigMgr admin out there.
Essentially what the tools does is to monitor for packages that are in transition from one SCCM site to other SCCM site(s). The tool works by reading information from the sender.log on the source site.
I think it’s an excellent way of getting an overview on packages which are currently being sent, and one of the great things that it does is to provide the user with a percentage of transferred and remaining data …. How cool is that?!
Anyway here is the link to Dan Riching’s blog post http://www.danrichings.com/?p=90
Just a quick one which had me slightly puzzled earlier today when attempting to register the SPN entries for the SCOM 2007 SDK Data Access Service.
Any of the literature which you will come across online states that you should register the SPNs by means of the following commands:
Setspn.exe –A MSOMSdkSvc/<FQDN> domain\SDKServiceAccount
Setspn.exe –A MSOMSdkSvc/<NetBIOS Name> domain\SDKServiceAccount
Now… while this is completely true, just something to watch out for is that if you attempt to copy and paste this command line, the dash character (-) which command prompt likes is replaced with the Microsoft-wordy-type-one and on attempting to run the command you will receive an error message which states
Unknown parameter MSOMSdkSvc/<hostname> Please check your usage.
You can fix this by replacing the Setspn –A with Setspn /A …. Or just replace the dash within the command prompt itself.
Came accross an issue when attempting to set up an SRS RP on SCCM 2007 . When browsing the SQL Reporting Services website (http://localhost/reports) Internet Explorer will throw a http 500 internal server error when we attempt to load the SRS webpage.
Upon investigation within the Reporting Services logs (\MSRS10_50.MSSQLSERVER\Reporting Services\LogFiles\) we see the following error messages:
e ERROR: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
e ERROR: HTTP status code –> 500
e ERROR: System.Web.HttpException: Error executing child request for Error.aspx. —> System.Web.HttpUnhandledException: Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
At the time of writing this, Microsoft state the issue as follows on a published troubleshooting article for SRS:
Report Manager fails after you enable FIPS compliant algorithms in Local Security Policy
After you enable the Local Security Policy “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing”, you are not able to use Report Manager. When you open Report Manager, your browser will be empty or show an “HTTP 500 Internal Server Error”. A SQL Server 2008 R2 or later version of the report server will add an error message similar to the following in the report server service log file:
ui!ReportManager_0-1!1708!02/27/2010-08:02:03:: e ERROR: System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
To work around this issue: At this time, there is no known work around. Report Manager does not support the Local Security Policy “System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing”. If you want to use Report Manager you need to disable the setting and restart the report server service.
This issue applies to: SQL Server 2008 Reporting Services and SQL Server 2008 R2 Reporting Services.
So you have two options. Modify the security policy locally or using a GPO. Alternatively we can modify one of the configuration files used by SRS, which is explained here:
- Open the following file in notepad on the SRS Instance \MSRS10_50.MSSQLSERVER\Reporting Services\ReportManager\web.config
- Add the following text into the <system.web> section of the config file <machineKey validationKey=”AutoGenerate,IsolateApps” decryptionKey=”AutoGenerate,IsolateApps” validation=”3DES” decryption=”3DES”/>
- Close and save the file, and then restart the SRS Service
- (Please note that if you copy and paste line 2 above into notepad, you will need to replace the quotation special characters within the ‘pasted’ code, as for some reason these are replaced on this blog site with the ‘curly’ quote marks – you’ll see what I mean if you compare a new quotation mark in notepad and the copied and pasted line from above)
Your web.config file should look something like this
Launch the SQL Reporting Services web page once more and all should be well!
Excellent source of information on ConfigMgr 2012: