Installation of system center. - where F:\sources\sxs is the path to the Win2016 NET image files


System Center Configuration Manager, let's spend a little time on a couple of points. Firstly, what is this product for? Secondly, it is very important not to skip some preparatory work. Otherwise you simply won't be able to run necessary programs and utilities. We will immediately warn you that the process will take quite a long time - if you are in a hurry, then do not proceed with the steps. Installing System Center Configuration Manager 2012 r2, how to launch, configure and uninstall this configuration manager client is discussed below (if you have already prepared your system).

System Center Configuration Manager 2012 r2 is very good program, which will help you manage your resources more productively

System Center Configuration Manager 2012 r2 provides a scope for managing IT infrastructure based on Microsoft Windows and related devices. What can a user or developer do in this system? For example, you can regulate updates, deploy software and operating systems, manage remote access and do other similar things. To date latest version This product is a 2012 release - this is System Center Configuration Manager 2012 r2. It is using this version as an example that today we will consider all the nuances of using the software. First, we will do some preparatory work. So to speak, let’s bring the “soil” to the desired consistency before planting the seeds there.

Preparatory settings

Adding Roles and Features

  1. First, you need to decide system requirements programs: you must have Windows Server 2008 or SQL Server 2008 with relevant updates. The same applies to supported client operating systems- Windows XP, Vista, 7, 8, Server 2003, 2008, 2012 or MacOS. The latest software updates required for SCCM operation must be installed everywhere.
  2. Secondly, we will need to add special components for correct operation. To do this, launch “Server Manager” (or server) on your computer or laptop.
  3. On top panel tools, click on the “Manage” button and select “Add roles and components” in the list that appears.
  4. Now the Add Roles and Features Wizard dialog box will open in front of you. After reading the presented text, click “Next”.
  5. Since we do not need to install Remote Desktop Services, we select the first item, “Install roles and features.” We confirm our choice with the already familiar “Next” button.
  6. On the next page we will need to select a server from the server pool. Click once on the one we need special list in the table and click on “Next”.
  7. In the server roles window, by default there is a checkmark in the file services and storage item. We do not mark anything else additionally and click “Next” to go to the next page.
  8. In the selection of components, we will already have to select several more items, in addition to the standard one marked - functions NET Framework 5, background intelligent transmission service, remote diversity compression and facilities remote administration Server. Then you can move on.
  9. The ninth step opens the ISS installation wizard, in which you will need to check ASP.NET5 and 4.5. Also note Windows authentication, WMI and IIS6 compatibility. Click “Next”.
  10. So, we have reached the finish line, where we need to click the long-awaited “Install” button. Now we just have to wait for the process to finish, after which we can start preparing SQL.

Setting up SQL 2012

  1. First, let's launch installation file. This will open the SQL Server Installation Center window. Click on “Install”.
  2. Naturally, this is ours new installation isolated instance, so we select the appropriate item in the list.
  3. Next, the support rules will define some errors or problems that may appear in the future. If you don’t have any, then click OK. Otherwise, you will need to fix these problems yourself.
  4. At the next stage, the program will require you to maintain product keys. After entering, click on “Next”.
  5. Read the license terms for the installed software. If you agree with them, check the box below and click “Next”.
  6. Now check the box to enable SQL Server update (if the program itself prompts), then click “Next”.
  7. We wait for the operation to complete and move on to the next window, where you will need to install the components. Check the box, mark the items below and click “Next”.
  • Database Engine Services
  • Reporting Services
  • Controls
  1. We don’t touch anything in the instance window and move on to the next requirements window and free space. Here the fact of the possibility of installation on HDD. Therefore, we can move on.
  2. Select the name from which the service will be launched and go to the next dialog box.
  3. So, the window with the server configuration. There will be two tabs here: service accounts and sorting options. Click on the second one and enter the following Database Engine there: SQL_Latin1_General_CP1_CI_AS. Let's move on.
  4. Now we assign SQL server administrators using the “Add” button and move on to the next section.
  5. The Reporting Services main mode should be set to Install and Configure. Go ahead.
  6. You can optionally select the option to send errors to Microsoft. This is optional, so it is at your discretion.
  7. We check the installation configuration rules window and click “Next” if there are no errors.
  8. Well, the penultimate step is to look at the report of the selected parameters and click the coveted “Install” button.
  9. After completing the installation process, close the program. To complete this, you will need to install SP and CU for SQL Server yourself, and then integrate with AD.

Installing and configuring System Center Configuration Manager 2012 r2

How to install?

  1. Run the installation file. In the welcome window, read the text and move on to the next one.
  2. In the new window, check the first box next to “Install the Configuration Manager Primary Site” and click Next.
  3. Now select the license type for the product you are installing. If you have a special key that you previously purchased, then check the installation of the licensed version. Otherwise, choose the first option.
  4. The next window will show you license agreement, which we accept by checking the appropriate box and clicking on the “Next” button. Please note that you will need to repeat a similar process next.
  5. So we got to the loading necessary components. Select the appropriate item with a tick and move forward.
  6. If you chose the method of downloading new files from the network, then wait until the downloader downloads the necessary documents that are available for viewing in the folder.
  7. Then two windows for selecting the languages ​​of the program and the client will appear in turn - mark the ones you need and move on.
  8. The installation wizard requires you to specify the site code, which cannot be corrected later. That is why it is recommended not to write it just like that, but only after thinking carefully about the password. Also write the name of the site, check the console installation box at the bottom of the window and click “Next”.
  9. In the primary site installation window, select the second item (as a standalone site). If you already have a certain hierarchy, then mark the first option and write the complete Domain name(administration center site server).
  10. Fill out the fields in the database details window as needed and move on.
  11. Write the name of the server where you will need to connect the SMS provider.
  12. It's time to set the communication parameters: if HTTPS protocol you are not going to use it as a direct method, then put a circle on the second point. Otherwise - on the first. Go ahead.
  13. Now specify whether the wizard should install a management point or a distribution point by filling in the fully qualified domain name.
  14. In the next window you will see a summary of the parameters, which it is advisable to double-check so as not to bite your elbows for your mistakes later. Click “Next” and wait for the installation process to complete.
  15. If you encounter any errors at this time, you should definitely eliminate them. Only then try again.

How to setup?

To set the basic settings, you need to run System Center Configuration Manager 2012 r2. Here you will need to configure some detection types, namely:

  1. Heartbeat, which is turned on automatically by default.
  2. An AD forest discovery method that allows you to set AD site boundaries and IP subnets automatically.
  3. AD groups whose method is used to retrieve them.
  4. The active directory detection system provides the user with information about the PC, namely its name, address, AD site and other data.
  5. AD users. Their detection provides information about user accounts.
  6. Network resources, the source of information for which is a special router via the SNMP protocol.

Any of these detections can be easily configured by clicking right click mouse using the selected method. Then select “Properties” and check the enable box. You can also set configuration parameters here if necessary and click OK.

How to remove Configuration Manager Client

  1. To remove Configuration Manager Client you need to run the command line.
  2. To do this, open the bottom toolbar on the desktop of your computer or laptop.
  3. In the search field, enter “Command Prompt” and use the found application shortcut to launch the executable file.
  4. In the program window, enter: Ccmsetup.exe /uninstall.
  5. Now press the Enter key.
  6. Please note that you will not see the deletion itself occur. That is, no sliders, percentages of work completed or other indicators of process progress will appear in front of you. To verify that you were able to uninstall System Center Configuration Manager 2012 r2, look for CCMSetup.log, located in the "ccmsetup" folder at %windir%\system32\. This file will contain all the necessary information.

Applies to: System Center 2012 SP1 - Data Protection Manager, System Center Data Protection Manager 2010, System Center 2012 - Data Protection Manager, System Center 2012 R2 Data Protection Manager

When you install System Center 2012 - Data Protection Manager (DPM), you must install the DPM application and the required DPM software. The DPM Installation Wizard allows you to set DPM configuration options and automatically installs the required software or provides links to install it as part of the comprehensive DPM installation process. If you have any questions at any time while working, please contact Help.

The DPM Installation Wizard allows you to install the required DPM software from the DPM product DVD. To use retail copies of one or more products required to install DPM, install them manually before running the DPM Installation Wizard.

Launch the installation program.

    On installation media right-click setup.exe and then select Run as administrator.

    On the list Install select Data Protection Manager.

    On the Microsoft Software License Agreement Terms page, select the I accept the terms of the license agreement to start the installer. Then click the button OK. If you do not accept the terms, click the button Cancel to close the installer. The terms of the license agreement can be copied and pasted into text editor for subsequent printing. Once installation is complete, click About DPM in the DPM Administration Console to access the terms of the license agreement.

    On the welcome page, click the button Further.

    On the Verify Readiness for Installation page, click Check and install to make sure your computer meets the installation program requirements. Before you run the installation readiness check, you must specify the SQL Server instance that will be used for the DPM database as follows:

    On the Product Registration page, enter the credentials used to register your copy of DPM as follows:

    • In field Username enter your name. When installing DPM, enter the DPM server administrator username. A username is required to continue the installation.

      In field Company If necessary, enter the name of the organization.

      In field Product Key Enter the key that came with the DVD.

      In field Client licenses Enter the number of licenses purchased to activate protection for client computers (laptop and desktop).

      In field Standard licenses Enter the number of licenses purchased to enable file share and system state protection.

      In field Corporate licenses Enter the number of licenses purchased to enable protection of file and application resources.

    After entering your identification information, click the button Further.

    On the Installation Options page, specify where to install the program files and DPM database. Please note the following conditions:

    1. These files can only be installed on local disk. They cannot be installed in read-only folders, hidden folders or directly to local Microsoft folders Windows, such as "Documents and Settings", "Windows NT" or "Program Files". (However, the files can be installed in a subfolder of the "Program Files" folder.)

      Files can only be installed on the partition with the file NTFS system. To make recovery easier in case of failure boot partition, install DPM on a partition that is not bootable.

      In chapter Program files click the button Change to change the default installation location program files DPM.

      In chapter Database files click the button Change to change the default installation location for DPM database files.

      In chapter Disk space requirements, check that the selected drives have enough space for installation.

    After entering the installation parameters, click Further.

    On the Security Settings page, set a password for the DPM and SQL Server service accounts.

    • In field Password enter strong password for limited MICROSOFT$DPM$Acct and DPMR$ accounts<имя компьютера>. For security purposes, DPM runs an instance Microsoft SQL Server and the SQL Server Agent service under the MICROSOFT$DPM$Acct account that DPM Setup creates during installation. To securely generate reports, DPM creates a DPMR$ account<имя компьютера>. Please note the following conditions:

      • A SQL Server service account is not created if you plan to use a remote instance of SQL Server

        A strong password is required for system security. A password is considered strong if it is at least six characters long, does not include all or part of the user account name, and contains at least three of the following types of characters: capital letters, lower case, decimal digits and symbols such as !, @, #.

        This password does not expire.

        As a password system administrator for SQL instance Server program DPM sets the same password that was set for the MICROSOFT$DPM$Acct account.

    After confirming the password, click the button Further.

    On the Microsoft Update Usage page, you can sign up to use the Microsoft Update server. To do this, check the box Use Microsoft Update when checking for updates. Please note that subscribing to this service not only allows you to receive DPM updates, but also all important and necessary updates from the Microsoft Update Catalog.

    Once you have decided to sign up for Microsoft Updates, click Further.

    On the Customer Experience Improvement Program page, indicate your ability to participate in the program. CEIP is used to collect data about the use of Microsoft applications in order to identify possible improvements. To participate, check the box Yes, I want to participate anonymously in this program. To unregister, click No, remind me later. You can change your decision to participate in CEIP at any time in the DPM Administration Console.

    On the Summary page, confirm your installation options and click Install, to continue.

    The Installation page allows you to monitor the progress of the installation program. To exit the installer at any time, click Cancel. When installation is complete, click Ready to close the DPM Installation Wizard.

To check whether Configuration Manager is ready to install, we will use the application Prereqchk.exe, which is located on installation disk in folder SMSSETUP\BIN\X64.Documentation for working with Prereqchk.exe is available here https://docs.microsoft.com/ru-ru/sccm/core/servers/deploy/install/prerequisite-checker
To check the readiness of the first server for installing a Primary site with SQL on a separate server, run

E:\SMSSETUP\BIN\X64\prereqchk.exe /PRI /SQL sqlserver.domain.com /SDK cm01.domain.com /MP cm01.domain.com /DP cm01.domain.com /ssbport

sqlserver.domain.com - FQDN SQL server, cm01 is the first site server whose readiness we are checking.
/PRI Verifies that the local computer meets the requirements of the primary site.
/SQL<полное_доменное_имя_SQL_Server> Verifies that the specified computer meets the SQL Server requirements associated with hosting the Configuration Manager site database.
/SDK<полное_доменное_имя_поставщика_SMS> Verifies that the specified computer meets the requirements of the SMS provider.
/MP<полное_доменное_имя_точки_управления> Verifies that the specified computer meets the requirements for the management point site system role.
/DP<полное_доменное_имя_точки_распространения> Verifies that the specified computer meets the requirements for the distribution point site system role.
/Ssbport Verifies that the firewall exception that allows connections on the SSB port is active. The default port is SSB 4022.

When the command is executed it will start GUI, which will indicate the requirements and recommendations for installation point by point:

Let's go through the main ones.

Install .Net framework 3.5:

Install-WindowsFeature Net-Framework-Core -source f:\sources\sxs

f:\sources\sxs - folder on the installation Windows disk Server 2016

Install the remaining OS components:

Install-WindowsFeature -Name UpdateServices-Ui Install-WindowsFeature Web-Windows-Auth Install-WindowsFeature Web-ISAPI-Ext Install-WindowsFeature Web-Metabase Install-WindowsFeature Web-WMI Install-WindowsFeature BITS Install-WindowsFeature RDC Install-WindowsFeature NET-Framework -Features Install-WindowsFeature Web-Asp-Net Install-WindowsFeature Web-Asp-Net45 Install-WindowsFeature NET-HTTP-Activation Install-WindowsFeature NET-Non-HTTP-Activ Install-WindowsFeature WDS

Install-WindowsFeature -Name UpdateServices-Ui installs the WSUS administration tools. I will not install the WSUS role itself on this server, because... I plan to deploy Software Update Point on the second server of the CM02 site.

ADK Installation

Download and install ADK 10 https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit
I used Windows ADK for Windows 10, version 1703.
The following components are sufficient for Configuration Manager to work:
Deployment Tools
Windows PE,
USMT
If necessary, you can install additional components. I also installed ICD and Configuration Designer.

We re-run the readiness check:


There are still active comments on configuring the SQL server. One of them reports that it is not recommended to use SQL authentication on the server. I deliberately chose this configuration, so I will ignore this warning. The other two warnings are related to the fact that the upper and lower bounds for memory consumption of the database server are not set. The lower minimum limit for a Primary site should be 8 GB. I'll set the lower limit to 16 GB and the upper limit to 20 GB. You can do this in SQL Server Management Studio:



We run the readiness checker again and make sure that there are no obstacles to installing the first server of our site.

Installing the first site server

Mount the Configuration Manager disk image and run the splash.hta file:

We indicate the type of site that needs to be installed:


Next, the wizard will ask you to enter license key and accept the license agreement. The installer will then download the required installation files to the specified location. In the next two steps, we indicate the languages ​​that need support in the server part (Configuration Manager Console and reports) and in the client part:


If the client OS language is Russian, then all warnings and the SCCM client interface will be in Russian.


Add support required languages possible after installation. To do this, you need to run the installation again and select “ Perform Site Maintenance» in the installation wizard.
At the next step, you need to specify the site code, which will identify it in the site hierarchy. The site code cannot be changed subsequently!

As in previous versions, the site name must be three-letter and comply with the following rules: the site name must contain only standard characters(A-Z, a-z, 0-9, and the hyphen “-”), and be unique within your Configuration Manager infrastructure. Reserved names cannot be used: SMS, CON, PRN, AUX, NUL, OSD, SRS, FCS.


Next, we indicate whether the site should be added to the existing hierarchy or a Stand-alone site should be created:


A warning window will appear indicating that we have selected a Stand-alone site. But unlike the ConfigMgr 2012 version, this warning informs us that if we need to create a site hierarchy, we can do this by installing the Central Administration site:


In the next step, we will indicate the name of the SQL server that we prepared. We leave the instance name empty, because When installing the SQL server, we left it by default. We also leave the port 4022:


At the next step, we specify the paths to the database and transaction log on the SQL server.
Now we indicate the server on which the SMS provider should be installed. In our case, this is the same cm01 server:


The next step is to configure how clients interact with site roles. I choose the option of setting up the interaction method separately on each site role, because... I plan to configure the PKI infrastructure for clients and site roles later. Checking the “Clients will use HTTPS when they have a valid PKI certificate and HTTPS-enabled site roles are available” checkbox allows clients to select a site system configured to connect via HTTPS with priority.


Next, we indicate the names of the servers on which you need to install the management point and distribution point. In our case, this is the same server on which we ran the installation:


Next, you need to configure Configuration Manager update settings. In new versions of Configuration Manager, it itself receives updates through the Configuration Manager cloud service. To do this, the “Service Connection Point” site role is used, which, among other functionality, downloads updates applicable to your SCCM infrastructure.
We indicate the server on which to deploy Service Connection Point and, if required, proxy server settings for Internet access:


At the next step “Settings Summary”, we check all the specified parameters in the installation wizard again and click next, after which the compliance check of the prepared infrastructure will start to continue the installation.
In my case, I received a warning that the SQL server is configured for the “Mixed Mode” authentication mode, but because... This is intentional, I ignore this warning and continue with the installation:


We check the success of the installation on all points:


You can also check the System Management container for site and management point entries:


This completes our Primary Stand-alone site.

What's available:
TL-SCOM - Win2016 Standart server
SQL 2016 Enterprise
SCOM 2016
Preparing the installation environment.
1. Install Windows 2016 Standard, add it to the domain
We create the required Accounts in AD And add them to TL-SCOM Administrators:
I created a security group SCOM_admin, in which I included the following logins
Mr_SCOM_Admin
Mr_SCOM_DataAccess
Mr_SCOM_DataReader
Mr_SCOM_Writer
Mr_SCOM_SQL
2. Install NET Framework 3.5
— connect the Win2016 image and execute the command in PoSh:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:F:\sources\sxs
- where F:\sources\sxs is the path to NET files Win2016 image
4. Install the following roles and components:
Add-WindowsFeature NET-WCF-HTTP-Activation45,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering ,Web-Stat-Compression,Web-Mgmt-Console,Web-Metabase,Web-Asp-Net,Web-Windows-Auth –Restart
5. Register ASP.NET 4.0 in IIS
in CMD we execute:
%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe –r


Reboot the server
6. Open the IIS management snap-in, go to the ISAPI and CGI Restrictions setting and allow (check the permission) the execution of ASP.NET v4.0.30319

SQL Installation Server 2016
7. Installing SQL 2016 (everything according to Next + changed the paths to the databases to D:\MSSQL):
! SQL Server Feature Installation
- Datedase Engine Services
- Reporting Services
- Full-Text and Semantic Extractions for Search








+ download and install SQL Server Management Studio (SSMS) https://msdn.microsoft.com/en-us/library/mt238290.aspx
Download, run the distribution, Install, wait for the installation to complete.
Upon completion, restart the server
9. Remote Registry Service: must be enabled and running.
— in PoSh we do:
Set-Service remoteregistry -StartupType Automatic Start-Service RemoteRegistry
10. Install SQL CRL 2014
https://www.microsoft.com/en-ca/download/details.aspx?id=42295
11. Install MICROSOFT REPORT VIEWER 2015
https://www.microsoft.com/en-us/download/confirmation.aspx?id=45496
Installing the first Management Server
12. Unpack the SCOM 2016 installation disk image, run the SETUP.EXE file and select Install

13. Select the required roles for installation - select all SCOM roles

14. Leave the default installation path

15. We are waiting for all prerequisites to be verified.

16. The next step is to create the first management server. Specify the name of the management group

17. We accept the terms of the license agreement.
18. At the step of specifying the parameters of the created operating base SCOM data we will indicate the name of the SQL Server server, instance and port. In our case, the default instance (MSSQLSERVER) is used, so it can be omitted. The name of the operational database and its initial size are left at the default value.

19. At the step of specifying parameters created base For SCOM storage data, we will specify the SQL Server server name, instance and port. If, as in our case, the default instance (MSSQLSERVER) is used, then it can be omitted. The Create a new data warehouse database parameter determines that we are creating a new database.

20. Click Next on the reporting service location

21. Leave the default value – Default Web Site is the name of the IIS site existing on our server, which will be used to host the Web console.

22. At the step of selecting an authentication method for the SCOM web console, select mixed mode - Use Mixed Authentication, since we plan to use this website only internally local network and we want the method of end-to-end verification of credentials (SSO) available to us

This article describes the procedure for centrally deploying the enterprise 32-bit version Microsoft Office Professional Plus 2016 to client computers using System Center Configuration Manager 2012 R2. Let's look at the process of preparing your own MSP package with Office settings, creating the program on the SCCM server and installing the program on client computers.

Download and place a VL copy of Office 2016 Pro Plus in the directory that will be the source of files for the SCCM package (for example, \\msk-distr01\Applications\Office 2016)

Along with Office 2016, Microsoft released new version MS Office Deployment Tool, which allows you to create custom scripts Office installations 2016. With the help this tool administrator can configure Office installation settings and options, predefine product settings, language settings etc.

Note. This deployment procedure will only work for the Enterprise (VL) edition of Office 2016

Download Office 2016 Deployment Tool and run the file OfficeDeploymentTool.exe. Specify the directory where you want to unpack the files setup.exe And Configurationxml.

Run the Office Customization Tool (OCT) with the /admin parameter:

setup.exe /admin

The Office 2016 installer will run in a special mode in which we will specify the settings that should be used when deploying to users' computers. As a result, the program will create an MSP file containing all specified settings, which will need to be saved to the “.\Updates” directory of the Office distribution.

Note. Keep in mind that the MSP file is tied to the product architecture, i.e. x86 and x64 editions will require their own MSP files.

We'll create an MSP file that allows you to install Office silently without the need for user interaction.

Select Create a new setup customization file for the following product, check the desired product revision and click OK.

In chapter Install location and organization name provide information about the organization.

Then in the section Licensing and user interface, select option Use KMS client key(if you will use or ), or manually specify the MAK key by selecting Enter another product key.

Enable the checkbox in sectionI accept the terms in the license agreement, In chapter Display level please indicate Basic, and select Suppress modal And No cancel. With these settings, the user does not have to enter any license information or confirm the license agreement.

In chapter Modify Setup properties click Add, and add a parameter named SETUP_ REBOOT and meaning Never.

Let's disable the initial setup wizard for users when they first start by changing in the section Modify user settings -> Microsoft Office 2016 -> Privacy— > Trust Center. Parameter value Disable Opt-in Wizardon first run on Enabled.

Let's save the received settings ( File -> Save As) to an MSP file in the distribution directory Updates. The Office installer automatically checks this folder for the presence of the MSP file; if it is missing, the full installation starts. Close the OCT utility.

The next stage is creating an SCCM application.

Open the SCCM console and in the section Software Library -> Application Management -> Applications create a new application (Create Application).

Select Automatically detect information and specify the UNC path to the file proplusww.msi

The application will be imported from the msi file. Click Next.

We will provide information about the application. We will leave the installation line unchanged for now (by default, msiexec /i “proplusww.msi” /q). In point Install behavior let's choose Install for system.

Let's close the application creation wizard.

Open the properties of the created application, on the tab Deployment Types select MSI file and go to edit mode ( Edit). On the tab Content specify the path to the directory with the Office 2016 distribution.

On deposit Programs change the installation line ( Installation Program) on setup.exe. Save your changes.

All that remains is to distribute the application to the required Distribution Points and publish the program to a collection of user computers. In the master DeploySoftwareWizard specify the action: Action – Install, Purpose – Available

On the user side, in a few minutes the new application will be available in Software Center. The user can select Microsoft Office Professional Plus 2016 from the list of applications and start its installation by clicking Install Selected.

The detailed installation log is in the file. You can use this file to monitor the installation status.

The application will be downloaded to the client's computer and installed. As we can see, the installation status has changed to Installed, which means Office 2016 was installed correctly.

For automatic installation Office 2016 in silent mode on computers of a certain collection, you need to create a separate Advertisement.


2024 gtavrl.ru.