SCCM Issue Tracker

To day I have faced a issue to install one of secondary site using push method from primary server .  After push it from primary server. I have seen in installation folder that Secondary server log folder only 4 log files are there. and the sitecomp.log file shows that below... Bootstrap failed..  After a couple of web searches I have found one solution :: which is work for me  I have run this command from command prompt  lodctr /r:c:\windows\system32\perfstringbackup.ini and then push again and after some time it will work fine for me . Help link : http://myitforum.com/cs2/blogs/jsandys/archive/2009/01/12/i-don-t-have-grey-hair-yet.aspx

Today I have faced a problem which is might be help full some of buddies who is new like me ...:) I create a user in SQL db and assigned a schema dbdatareader .  But when I will try to delete the user I am facing some issue. So my work around this :  Run this query first :- USE <dbname>; SELECT s.name FROM sys.schemas s WHERE s.principal_id = USER_ID('username'); Run this 2nd query :- ALTER AUTHORIZATION ON SCHEMA::db_datareader TO dbo; Help link : http://blog.sqlauthority.com/2011/12/26/sql-server-fix-error-15138-the-database-principal-owns-a-schema-in-the-database-and-cannot-be-dropped/

System Center 2012 Configuration Manager SP1 – Don’t install it in production if downloaded from MSDN or Technet, wait until General Availability. This blog is copied from  Niall C. Brady, Configuration Manager MVP. There’s been a lot of talk lately about  System Center 2012 Configuration Manager Service Pack 1  being released to MSDN and Technet and I (like a lot of people) have downloaded and installed it in my lab. The key part of that sentence above is ‘ in my lab ‘. It is  not permitted  by Microsoft to install System Center 2012 Configuration Manager SP1  in production  if you downloaded it from either of these two locations:- MSDN Technet but why ? The answer is found  here  on Microsofts’ MSDN site and it explains that you are not permitted to install this software in Production (highlighted in red below). In fact what you can also clearly see from the screenshot above  is that you are better off using...