The following SCCM server naming convention will be used in the CONTOSO: (G:)(50gb+) RAID 1 for transaction logs,UserDBlog, SQL TempDB logs, SCCMBackup (64k BlockSize, ReFS) (F:)(40gb+) RAID 5 for SQL DB (64k BlockSize, ReFS) (E:)(150gb+) DP Content, SUP/WSUS, MDT, SCCMShare, WADK (4k, NTFS) (D:)(100gb+) RAID 1 SCCM Inboxes, SCCMContentlib, (4k, NTFS) (C:)(60gb+) RAID 1 for OS, page file (4k, NTFS) Microsoft Windows Server 2019, Enterprise (4) 64 bit Single Processor 2.0 Ghz or HigherĢ x Gigabit Ethernet network adapter (redundant) Refer to SCCM hardware requirements for the best hardware configuration for your installation. The hardware used is outlined in the table below. The example below is for demonstration purposes only. In this document ALL SCCM ROLES will be installed on a Single Server. The configuration below of a RAID 1 configuration is only a recommendation. Note virtual servers will be used in the CONTOSO environment but the settings below applies to physical and virtual machines. Supported Configurations for Configuration Manager Windows Assessment and Deployment Kit (W ADK v1903)ĭownload the ADK from the following link: Visual C++ Redistributable Packages for Visual Studio 2013 SQL Server Management Studio release ( SSMS 18.3)įrom URL…. SQL Server Enterprise Edition 2017 64 BitĬumulative Update Package 16 for SQL Server 2017 - KB4508218 System Center Config Mgr (current branch 1902) The following table outline the server specification that will be used to build the SRV-CM-01 server. The scripts included in this document can also be added to MDT to automate the install of SCCM CB 1902. These steps can be used on a disconnected network. The document outlines the steps required to install SCCM CB 1902 with SQL 2017 using PowerShell. In no event shall Microsoft, its authors, or anyone else involved in the creation, production, or delivery of the scripts be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample scripts or documentation, even if Microsoft has been advised of the possibility of such damages. The entire risk arising out of the use or performance of the sample scripts and documentation remains with you. Microsoft further disclaims all implied warranties including, without limitation, any implied warranties of merchantability or of fitness for a particular purpose. The sample scripts are provided AS IS without warranty of any kind. The sample scripts are not supported under any Microsoft standard support program or service. 2.2 - HARDWARE AND DISK LAYOUT REQUIREMENTĤ.1 - WHY EXTEND THE ACTIVE DIRECTORY SCHEMA FOR SCCMĤ.2.2 - Identify Forest Root Domain Controller Schema MasterĤ.2.3 - Log on to Forest Root Domain Schema MasterĤ.2.5 - Verify Successful Schema ExtensionĤ.2.6 - Verify DOMAIN Replication to Domain Controllersĥ.1.1 - Create the System Management Container (Manaully)ĥ.1.2 - Set Security on the System Management Container (Manually)Ħ - BUILD PRIMARY SCCM CB 1902 SITE (VP1)Ħ.1 - PRIMARY SITE SERVER NAMES AND ROLESĦ.2 - PREP FOR SCCM AUTOMATED INSTALLATIONĦ.2.1 - Overview of SCCM PowerShell Install ScriptĦ.2.2 - Create SCCM Staging Folders for Automated DeploymentĦ.2.4 - Set Windows Firewall ports for SQLĦ.2.6 - Create the SQL 2017 Reporting Service PS ScriptsĦ.2.7 - Create the Set Service Acct PS ScriptsĦ.2.8 - Create Report Server Encryption KeyĦ.2.9 - Download the Windows ADK 10 Files for Offline UseĦ.2.10 - Download Windows PE_1903 as Separate Add-onĦ.2.11 - Download SCCM CB v1902 Prerequisite FilesĦ.2.12 - Create the SCCM Setup.ini File for The Unattended InstallĦ.4 - INSTALL THE SCCM REPORTING SERVICES POINTĦ.4.1 - Test SCCM Reports and SSRS Web siteĦ.4.2 - Configure Reporting Server Database Recovery Model
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |