How to Move databases for SCCM 2012

How to Move databases for SCCM 2012

1.       On SCCM Site Server

a.       Stop site server using  (Configuration Manager site installation folder)\bin\X64\00000409\preinst.exe /STOPSITE

2.       On Reporting Server

a.       Backup the encryption key using Reporting Services Config tool

b.      Stop the Report Server service using the Reporting Services Config tool

3.       On Wsus server

a.       Stop IIS Admin Service

b.      Stop Update Services Service

4.       On SQL Server for WSUS DB

a.       Detach SUSDB – single user rollback immediate

b.      Move both files (mdf and ldf)

c.       Attach SUSDB to new SQL server

d.      Verify Wsus server machine account  has login permissions and is member of webService Role

5.       On SQL Server for Reporting Services DB

a.       Detach SCCM_ReportServer

b.      Detach SCCM_ReportServerTempDB

c.       Move all 4 files (2 mdf and 2 ldf)

d.      Attach both databases

e.      Verify that RSExecRole is a database role on both SCCM_ReportServer and SCCM_ReportServerTempDB.

                                                               i.      If not, create role per http://msdn.microsoft.com/en-us/library/cc281308.aspx

6.       On SQL Server for SCCM DB

a.       Detach CM_(Site Code)

b.      Move both files (mdf and ldf)

c.       Attach CM_(Site Code) to new SQL Server run the following stored procedure as a query: sp_configure ‘clr enabled’,1; reconfigure.

d.      Enable common language runtime (CLR) integration

e.      Verify SCCM Site servers are Local Administrators on the SQL server

f.        Add the site server system account as login account with admin rights to SQL

7.       On Wsus server

a.       Edit Backend Database registry key to point to new name/instance

                                                               i.      HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlServerName. In the Value text box, type [BEName]\[InstanceName], and then click OK. If the instance name is the default instance, type [BEName].

                                                             ii.      HKEY_LOCAL_MACHINE\Software\Microsoft\Update Services\Server\Setup\wYukonInstalled. In the Value text box, type 0, and then click OK. This indicates that Windows Internal Database is not used.

                                                            iii.      Locate the following key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\UpdateServices\Server\Setup\SqlInstanceIsRemote. In the Value text box, change the value to 1, and then click OK.

b.      Start IIS Admin Service

c.       Start Update Services Service

8.       On Report Server

a.       Open Reporting Services Config tool

b.      On Database page, select the new SQL server instance and click connect.

c.       Select the report server database and click apply

d.      On encryption key page click restore

e.      Setup the execution account

f.        Restart Report Server

9.       On SCCM Server

a.       Run Configuration Manager Setup Wizard using Setup.exe from  (Configuration Manager site installation folder)\BIN\X64\setup.exe.  Not from install media- you won't have the same options.

b.      Choose site maintenance or reset site

c.       Select Modify SQL Server configuration

d.      After wizard finishes restart SCCM site server

e.      In SCCM console update the properties of the Reporting Services Point role to use the SCCM Databse on the new server.  Administration>Servers and Site System Roles>Pick the server with the Reporting Services  Point Role>Pick Reporting services point>Right click and choose properties>Change Site Database Server name.

Sccm 2012 install error

Following the windows-noob setup guide at:  http://www.windows-noob.com/forums/index.php?/topic/4422-using-sccm-2012-rc-in-a-lab-part-1-installation/


And came across this unusual error during setup:

Fail to create SQL Server Certificate, ConfigMGR installation cannot be completed.

Looking at the setup logs I see this only slightly more descriptive error:

Failed to get SID for user (NT Service\MSSQLSERVER)
ERROR: Failed to get the buffer size for LookupAccountName. Error = 1722

After much googling found this link from Yuri that suggests temporarily changing SQL to run under local system instead of the NT Service\MSSQLSERVER account. Worked great!

http://itbl0b.blogspot.com/2011/11/strange-error-while-installing.html

windows 7 bootable USB

Don't forget, you can extract the Windows 7 iso onto a bootable USB.  Makes the install much quicker:

   1. diskpart

   2. select disk 1 (if disk 1 is your USB stick)

   3. clean

   4. create partition primary

   5. select partition 1

   6. active

   7. format fs=fat32   (ntfs also works).

   8. assign

   9. exit

10. Extract the ISO

11. xcopy d:\*.* /s/e/f e:\ (Copy Windows 7 iso content to the Flash Drive E:)

Windows 7 RC is on MSDN now

If you have access to MSDN, go grab it!  Remember that your February Beta keys will still work.  If you need to regenerate them then these instructions will help:

http://www.neowin.net/news/main/09/01/10/psstheres-how-to-get-your-windows-7-beta-key

ConfigMgr.next revealed at MMS09

The MMS09 State of the Union session revealed what the next version of SCCM will look like.  The MMC is gone in favor of the Outlook-esqe toolbar (wonder-bar) as seen in SCOM 2007.  It also requires Server 2008 64-bit as well as SQL 2008 64-bit.  The other big piece of news is the elimination of ASP web reports in favor of SQL Server reporting services only.  See all the screen shots and read more about it on Kenneth van Surksum's blog:

http://www.techlog.org/archive/2009/04/29/mms_2009_information_about_mic

Vista SP2 and Server 08 SP2 RTM'd

SP2 for vista and server 08 have gone RTM.  Additionally the block offering SP1 is being removed (your GPO to block SP1 will no longer work). 

http://windowsteamblog.com/blogs/windowsvista/archive/2009/04/28/windows-vista-sp2-rtm-windows-vista-sp1-blocker-tool-removed.aspx

All the SP2 goodness can be found here:

http://technet.microsoft.com/en-us/windows/dd767387.aspx

Office 2007 SP2 is out

Just released:

http://www.microsoft.com/downloads/details.aspx?FamilyID=b444bf18-79ea-46c6-8a81-9db49b4ab6e5&displaylang=en

time to download, test and deploy!

windows 7 will have near complete xp compatibility

A new feature being announced is XP mode for Windows 7.  XP mode is essentially an application running in a Virtual PC virtual environment.  Installing the application in the virtual pc environment will result in it being published to windows 7 as an application.  The requirements for this technology includes processor virtualization support (Intel VT or AMD-V).  It will be a separate out of band update released in final form to coincide with the release of windows 7 (so it's not actually built in).  Paul Thurrott has a nice set of screen shots on the whole thing here: http://www.winsupersite.com/win7/xp_mode_pre_shots.asp

Unable to import AI license file

So our software licensing team asked about using SCCM's Asset Intelligence to track software license usage at our company. After going through all of our normal internal testing we were ready to import our xml formated license file into our site. However when we tried to import it on our production server we received a single message:

error

Unable to connect to the site database

Not very useful since my console and site server were obviously talking to the site database just fine. I spent many hours troubleshooting this one myself before calling Premier support. At which time I spent many more hours troubleshooting on the phone with them and fearing that the issue would be unresolved. We went through all kinds of troubleshooting of both my SQL server setup and my site server setup.

The only error message with any meaning behind it was when we tried to run the import manually:

D:\SMSPROV\bin\i386>mvlsimport.exe /file //server/share/MSLtest.xml

Failed to get Site Database configuration information.Failed to get Site Database connection.Failed to intialize.

Yes, those are forward slashes, per explicit instructions by Microsoft Support.

My gut told me it was a bug in SCCM, but how my site differed eluded both me and Microsoft support. Ultimately, by sheer luck a stumbled across the steps that would enable me to reproduce the bug on my own. My site had an unrelated hardware failure and I had to rebuild and recover it. As I rebuilt it I tried the import several times along the way, until it finally failed. Once I was able to reproduce the bug I let Microsoft know how my site differed from a working site. Turns out there is a bug importing the license file if the smsprovider is installed on another computer other than the site server. Support was then finally able to confirm that this was a bug that they could reproduce and would notify the development team. In the absence of an actual fix, they provided me with a workaround. The workaround is to export the sql node of the sms registry key from the site server and import it onto the smsprovider computer. If you are switching architecture you will have to update the key to compensate for wow6432node as well.

Export this key from your 32-bit site server: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\SQL Server]

Import this key into your 32-bit smsprovider computer.

Or, if your provider is 64-bit, find and replace \software\Microsoft\ with \software\wow6432node\Microsoft

Key will now be in this format:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\SMS\SQL Server]

Now import the new key onto your 64-bit smsprovider computer.

wsutil to change your wsus server's ports

Following up on my recovery of a sccm site.  My original recovery doc did not specify that during the wsus install, wsus needs to be setup to use its own custom website on ports 8530 (for http) and 8531 (for https).  I later found that if you miss this step  (When you notice your site fails to sync with its wsus database) then there is a simple utility installed with wsus that will allow you to change it.  From the command line:

wsusutil.exe usecustomwebsite true

Also, if your site just isn't syncing for no apparent reason, I've found that a wsus reset may help:

wsusutil.exe reset

You can find wsutil on the wsus server in the program files\Update Services\Tools folder.