Search the Community
Showing results for tags 'SQL Server 2012'.
Found 10 results
-
Installing SQL Server first is not required, as DPM will automatically install SQL Server for you as part of the application installation process. Since I install SQL on the local System Center server for each product, my example will allow DPM to install SQL on its own. If anyone is looking for instructions on installing SQL Server, please see my personal blog: http://adinermie.wordpress.com/lab-environment/system-center-2012-sp1-in-a-lab-installation-part-d-install-sql-server/ -
In our last post we installed SCVMM Reporting. By default, you should now have all the SCVMM reports available in SCOM’s Reporting space. However, there is an additional set of reports that is not made available by default. These are the Forecasting Analysis reports, and the only way to be able to use them is with SQL Server Analysis Services (SSAS). Since SCVMM using the reporting feature of SCOM, we need to have SSAS installed on the SCOM Reporting server. In our lab example, we have SQL DB and Reporting installed on the same server that is running SCOM. So, we’re going to go thro
-
Install SQL Server At this point, since we will be installing SQL Server on the same server that we will be installing our System Center product, it is expected that you have the VM created, the OS is installed, the appropriate networking has been configured, and it is joined to your lab domain. To avoid a specific installation error (see the end of the Install SQL Server section), you have to install the .NET Framework 3.5. So we’re going to complete this first before we start the installation of SQL. .NET Framework Installation To install the specific version of .NET that we requir
-
In our last post, we installed Active Directory. Now we will install SQL Server. Install SQL Server At this point, since we will be installing SQL Server on the same server that we will be installing SCOM, it is expected that you have the VM created, the OS is installed, the appropriate networking has been configured, and it is joined to your lab domain. To avoid a specific installation error (see the end of the Install SQL Server section), you have to install the .NET Framework 3.5. So we’re going to complete this first before we start the installation of SQL. .NET Framework Inst
-
I am having nothing but trouble with my SCCM 2012. I am running Server 2012 Standard, SQL server 2012 and SCCM with Endpoint Protection SP1. The install looks like it goes well but when i start to try and use client push i start to get all types errors. Under site status i have a critical staus for the Management point. And under component status my SMS_MP_CONTROL_MANAGER and SMS_NOTIFICATION_SERVER components have a critical stauts as well. I already have tried reinstalling a total of three time. If any one had any help or insight into my issues please help!!! I have attatched my log files. -
Install SQL Server At this point, since we will be installing SQL Server on the same server that we will be installing App Controller, it is expected that you have the VM created, the OS is installed, the appropriate networking has been configured, and it is joined to your lab domain. To avoid a specific installation error (see the end of the Install SQL Server section), you have to install the .NET Framework 3.5. So we’re going to complete this first before we start the installation of SQL. .NET Framework Installation To install the specific version of .NET that we require (ve
-
In our last post, we installed Active Directory. Now we will install SQL Server. Install SQL Server At this point, since we will be installing SQL Server on the same server that we will be installing Orchestrator, it is expected that you have the VM created, the OS is installed, the appropriate networking has been configured, and it is joined to your lab domain. To avoid a specific installation error (see the end of the Install SQL Server section), you have to install the .NET Framework 3.5. So we’re going to complete this first before we start the installation of SQL. .NET
-
In our last post, we installed Active Directory, now we need to install SQL. At this point, since we will be installing SQL Server on the same server that we will be installing SCVMM, it is expected that you have the VM created, the OS is installed, the appropriate networking has been configured, and it is joined to your lab domain. To avoid a specific installation error (see the end of the Install SQL Server section), you have to install the .NET Framework 3.5. So we’re going to complete this first before we start the installation of SQL. .NET Framework Installation To install
-
Hey All, I just installed SCCM 2012 in my test environment, with a remote sql 2012 server. However, as I read more documentation on 2012, experts or so call experts say I should install SQL server 2012 locally on the same primary site server. The main reason they say is for permissions simplicity. However, when I install 2012 in production should I install SQL 2012 server local or on remote server. Current Site Hierarchy Primary Site 3 Secondary Sites at remote locations Total Clients: 500-1000 at each site. Thanks, Paul
-
Hi I have to configure AlwaysOn Availability Groups and for that every node has to be a part of the WSFC. (Please correct me if i am wrong) I was wondering if you could post about how one can set up a windows server failover cluster starting from scratch. I tried to create WSFC, i had created three virtual machines (using VirtualBox, OS: Windows Server 2008 R2 with SP1, Installed SQL server 2012 Enterprise Edition) and installed the Faliover cluster feature. I also added the three machines to a common domain. Now, when i tried to make the cluster, the validation part gave me a huge l
