Samstag, 20. November 2010
Install SCCM 2007 on Windows Server 2008 R2
In order to install SCCM 2007 there are a number of prerequisites that are required to be installed on the machine.
WebDAV is required to support management point and BITS-enabled distribution point site system computers.
RDC is required for site server and branch distribution point computers
SCCM primary sites must constantly communicate with a Microsoft SQL Server hosting the site database. Typically, performance is better if the SCCM site server and the site database are installed on the same server however, if a high-availability, high-bandwidth connection is present leveraging SQL on a remote server is an option. Since AT run a number of different Beta products we have decided to run a local installation of sql 2008 sp2
1. SQL 2008 requires the installation of .Net 3.51 which can be installed from the features section in server manager. On the Windows Server 2008R2 computer, navigate to Start / All Programs / Administrative Tools / Server Manager to start Server Manager. In Server Manager, select the Features node and click Add Features to start the Add Features Wizard.
2. On the Select Features page of the Add Features Wizard and select .Net Framework 3.5.1
3. On the Add feature popup select add required features
4. Click Install
5. Insert the SQL Server 2008 CD and click on Install Server Components, if the splash screen does not appear, run Splash.hta from the .\Servers directory.
6. After launching the Sql 2008 setup select installation from the left menu
7. Select New SQL Server stand-alone installation
8. Click OK on the setup support rules
9. Enter the product key and select Next
10. Click I Accept the license terms and then click Next
11. Click Install on the Setup Support files page
12. Click Next on the Setup Support Rules page
13. On the feature selection page select the following: Database Engine, Full Text Search, Reporting Services, Management Tools Complete
14. We will be installing our SQL information to the D: drive and click Next
15. Accept the defaults on the instance configuration page (validate D: drive for the root directory) and click Next
16. Select Next on the disk space requirements page
17. On the server configuration page enter the Service account that we previously created (see table1)
18. On the Database Engine configuration leave Windows Integrated and add the appropriate account for SQL Admin and click NEXT
19. On the Reporting Services Configuration leave the default of Install Native Mode default configuration
20. On the Error Reporting page accept the defaults and click NEXT
21. Make sure all the rule have passed then click NEXT
22. Click INSTALL on the Ready To Install page
23. On the Install Progress page click NEXT
24. Click CLOSE on the completion page
1. Double click the SQL SP1 installation file En_SQL_Server_2008_SP1_x64.exe
2. On the Welcome screen click NEXT
3. Accept the License terms and click NEXT
4. on the Selection Features click NEXT
5. On the Check files in Use page click NEXT
6. Click UPDATE on the Ready to update screen
7. On the update progress page click NEXT
8. Click CLOSE on the completion page
When installing the site database on a remote SQL Server computer, the logged on user and site server machine account require administrative rights to the remote SQL Server computer. If installing the site database on a SQL Server cluster instance, the logged on user and site server machine account require administrative rights to all SQL Server cluster instance node computers.
The TCP/IP protocol is required for SQL Server network communications to allow Kerberos authentication. The named pipes protocol is not required for SCCM site database operations and should only be used to troubleshoot any Kerberos authentication issues encountered when using TCP/IP protocol communication. By default, SQL Server uses TCP port 1433 to listen on TCP/IP. To change the port, or network communication protocol used, start the SQL Server Configuration Manager, and click Protocols for
Configuration Manager 2007 Setup automatically creates the site database, using SQL Server defaults, on the SQL Server computer and instance specified during setup. If the configured SQL Server default settings are not sufficient to manage your site database, it is recommended that you pre-create the database and set the required settings. If you are using a remote SQL Server to host the site database, you should ensure that the site server’s computer account has sufficient privileges on the SQL Server computer to create the site database before beginning the installation process.
If you configure a domain user account to run the SQL Server service instead of the local system account a Service Principal Name (“SPN”) must be configured for the domain user account in Active Directory Domain Services.
setspn –A MSSQLSvc/
The following section outlines the installation process to install the core SCCM software, additional site system roles and, supporting components.
Extending the Active Directory schema is not required for installing SCCM or using most of the product features however, by extending the schema for SCCM all features can be leveraged with the least amount of administrative overhead. Extending the schema for SCCM also offers the most secure solution for storing configuration information. To extend the schema for SCCM in a Windows Server 2008 environment execute the following steps.
Note: The Setup command line option Setup /download
can be used to download client prerequisite component files without running the complete Configuration Manager Setup wizard.
After installing the SCCM Central Site, additional site system roles are required to support ABM functional requirements.
A MP is required to transfer information between SCCM clients and SCCM servers, without a functional MP, clients cannot be managed.
Server locator points (“SLP”) are used to complete client site assignment on the intranet and help clients find management points when they cannot find that information through AD. Clients must use a server locator point if the AD schema is not extended for SCCM, the site is not published to AD, or if clients do not belong to the same AD forest as the site server’s forest. The SLP role will not be implemented initially but this section is included to account for potential ABM SCCM environmental for growth.
Adding the SLP to Wins is only required if you have non AD joined machines that you want to be managed by SCCM or you plan to manage systems in remote directories.
*This task should be run from a Server that has the Wins Role installed*
Problem Ein frischer Windows Server 2016 (oder 2012/2012R2) WSUS-Server funktioniert nicht. Clients werden in der WSUS-Console zwar aufge...
Wie man das neue Microsoft Office 2013 aktiviert via Kommandozeile, das werde ich euch in dem folgenden Beitrag Schritt für Schritt erkläre...
Hat heute ein Problem mit WSUS unter Windows Server 2008 R2 bei einem Kunden. Das Problem - die Clients konnten keinen Verbindung zum W...