System Center, Operations Manager 2012, SCOM & More › Forums › Operations Manager › OPSMAN 2012 SP1 on Server 2012 Std
February 6, 2013 at 6:05 pm #110130
I was having issues installing OM12 SP1 on Server2012/SQL 2012 in a distributed roll out yesterday in my LAB. Am I missing some new security requirement? The install worked fine on a single server install. Which tells me there is no issues with SQL.
I tried SQL 2012 and SQL 2012 SP1. Verified TCP, updated mof, verified firewall ports, enabled file sharing, turned off UAC.
This should be supported , right?
Disk space: The operational database must have at least 1024 MB free disk space. This is enforced at the time of database creation, and it will likely grow significantly. For information about SQL Server Planning, see Installing SQL Server 2008 or Installing SQL Server 2008 R2.
File system: %SYSTEMDRIVE% must be formatted with the NTFS file system.
Operating System: Windows Server 2008 R2 SP1, Windows Server 2012, or Windows Server 2012 Core Installation.
Processor Architecture: x64.
Windows Installer version: at least Windows Installer 3.1.
Microsoft SQL Server: SQL Server SQL 2008 R2 SP1, SQL Server 2008 R2 SP2, SQL Server 2012, SQL Server 2012 SP1.
SQL Server Full Text Search is required.
.NET Framework 4 is required. For more information, see the following document:March 5, 2013 at 2:49 pm #111192
So SCCM will install on server 2012 SP1 and met the pre-req. However you need to be at CU2 for CONFIGMAN reporting roleto work. I believe SCOM is going to install now as well. More to follow. When I dug deeper into the support documents it indicates this. So I think the pre-req for SCCM has a bug.March 5, 2013 at 3:08 pm #111196
Also I saw a couple SQL 2012 SP1 CU2 when searching for this. One had 3 hotfixes and the other had 4. The link with 4 hotfixes was the one that seemed to work for me.March 8, 2013 at 4:27 pm #111415
If you co-locate SCOM and SCCM I am told it is a good idea to install SCCM as the default instance and SCOM and the named instance. Also don’t forget to turn off dynamic ports and hard set the port for the SCOM named instance.March 15, 2013 at 5:37 pm #111727
I may have spoke too soon. I can do local installs on SQL 2012 and server 2012 but seem to have issues doing remote installs. I give this is just a lab anyways. All in one install wins…March 18, 2013 at 7:42 pm #111783
My co-worked solved the problem with installing SQL on a distributed SCOM install. You have to enable WMI in the firewall to see the database. That explains why the all in one installed worked when the remote install did not. Maybe MSFT could have done a better job with the error message LOL.
You must be logged in to reply to this topic.