I've had some real struggles with coming up with a good system for managing software updates in SCCM since we went live back in mid-2012. Its taken over a year with. Installing Prerequisites for Configuration Manager 2012 R2 In this post we will see the steps for Installing Prerequisites for Configuration. · So, searched high and low, and have yet to find a solution. Have some xp sp2 pc's that either don't register as having the SCCM Client in place or showing. We have a WSUS server in our environment that works through Microsoft System Center 2012. I have a large amount of updates that I am attempting to send to a. SCCM 2. 01. 2 Distribution Point Installation. In the first part of this SCCM 2. ![]() SCCM 1. 51. 1 blog series, we planned our hierarchy, prepared our SCCM Server and Active Directory. In part 2, we installed and configured SQL in order to install SCCM. In part 3, we installed a stand- alone SCCM Primary site. In the next 1. 6 parts, we will describe how to install the numerous site systems roles available in SCCM 2. R2 and SCCM 1. 51. Role installation order is not important, you can install roles independently of others. In this part, we will describe how to perform a SCCM 2. ![]() SCCM 1. 51. 1 distribution point installation. I saw a lot of posts recently on the Technet forum which leads me to think that there’s a lack of documentation explaining this. Introduction. Several distribution points can provide better access to available software, updates, and operation systems. A local Distribution Point also prevents the installation thought the WAN. Pre- Requisites. Functional SCCM 2. SCCM 2. 01. 2 Admin console access. RDP access on the Distribution Point server. The required level of security in the SCCM console. Distribution point server configuration. Prevent package from replication on the wrong drive. Logon locally on the target machine with remote desktop. Create an empty file called NO_SMS_ON_DRIVE. SMS on the root of each drive where SCCM should NOT write. If any)Local Administrator group. On the DP, add a group that contains your site system computer account in the Administrators group. I like to create a SCCM system groups that contains all my distribution points. Open Server Manager. Expand Local Users and Groups. Click on Groups. Double- click on “Administrators”Add the security groups that contain the SCCM computer account. Windows Server configuration – Roles and Features. Configuration Manager requires some roles and features to be installed on the server prior to the DP installation. Remote Differential Compression. Open Server Manager, on the Features node, starts the Add Features Wizard. On the Select Features page, select Remote Differential Compression. IISIIS needs to be installed on the server but it will automatically be installed using the site installation wizard. For Windows Server 2. IIS manually. Windows Deployment Service. For Windows Server 2. R2, 2. 01. 2 and 2. R2, WDS is installed and configured automatically when you configure a distribution point to support PXE or Multicast. For Windows Server 2. WDS manually. BITSWith System Center 2. Configuration Manager, the distribution point site system role does not require Background Intelligent Transfer Service (BITS). When BITS is configured on the distribution point computer, BITS on the distribution point computer is not used to facilitate the download of content by clients that use BITSMicrosoft Visual C++ 2. Redistributable. You can run the Microsoft Visual C++ 2. Redistributable Setup from the Configuration Manager installation at: < Config. Mgr. Installation. Folder> \Client\x. For Configuration Manager SP1, vcredist_x. PXE. Powershell 3. For Windows 2. 01. Powershell 3. 0 (or further) before installing the distribution point. Firewall. Ensure that your firewall is set correctly. DP site server installation. Reboot your server to avoid case where your server is in “Reboot pending State” which will result in unexpected reboot during distribution point installation. Now that the Distribution point server is ready to receive a new role, we need to add the server to the site server list. Add new distribution point server to the SCCM console – Site System. In the Configuration Manager console, click Administration. In the Administration workspace, expand Site Configuration, and then right click Servers and Site System Roles. Select Create Site System Server. The Create Site System Server Wizard opens. On the General page, specify the Name for the site system server. Select the Site Code and Click Next. Do not specify a proxy server, click Next. Select Distribution point in the role selection screen, click Next. Check Install and configure IIS if required by CMAdd a description if needed. Select HTTPSelect Create self- signed certificate, click Next. Set drive configuration to your needs. This is where the SCCMContent. Lib will be created so select a drive with enough storage space, click Next. Do not configure a pull distribution point, click Next. Do not configure PXE for now, click Next. Do not enable multicast for now, click Next. Enable content validation to occur where it fits your environment, click Next. Add the boundary group that needs to be associated with this DP and Uncheck the Allow fallback source location for content, click Next. Review the summary page and complete the installation, click Next. WARNING Your remote server may reboot if there’s a missing requirement. At this point, the major part of installation a distribution point server is completed. Verification. Logs. You can track the installation progress in 2 logs: Distmgr. Smsdpprov. log on the distribution point. Installation. Drive\SMS_DP$\SMS\Logs)Windows Explorer. At this point, you will the SCCM file structure created on the site server. Console. You can also track the installation progress in the SCCM console under Monitoring / Distribution Status / Distribution Point Configuration Status. Click on your DPClick the detail tab on the bottom. Check for green check mark on all components. Note: Error on the IIS Virtual directory is normal at the start of the process. SCCM is making a check as if IIS is installed at the start of the process even if you tell SCCM to enable you IIS for you. That results in errors but be patient and the installation should succeed anyway. Verify the status of your new DP in Administration / System Status / Site Status. Replicate content. You can now replicate your content to your newly created DP. Replicate manually all your content or add your DP in an existing DP group. Replicate a package or Application to your newly created site system. Verify that the content is well replicated in the SCCM Console. That’s it ! You’re done creating your DP. Monitoring. If you have multiple Distribution Point, I suggest you to read our post on 8 ways to monitor your distribution points. This post explain in details the various options to make sure that your DP are healthy. You can also check our custom report about Distribution Point Monitoring to display all your DP status using a single click. Founder of System Center Dudes. Based in Montreal, Canada, Senior Microsoft SCCM Consultant, 4 times Enterprise Mobility MVP. Working in the industry since 1. His specialization is designing, deploying and configuring SCCM, mass deployment of Windows operating systems, Office 3. Intunes deployments. SCCM 2. 01. 2 Distribution Point Installation. CCMSetup Install Switches. How to Install Config. Mgr Client. With this post I want to explain the CCMSetup install switches as I get asked a lot how and when to use them. The Configuration Manager client is installed by launching ccmsetup. This happens to all client installations, even if client push installation from the Configuration Manager console and task sequence installations with the setup windows and configuration manager step. The first thing ccmsetup. Net Framework 4. 0. Ccmsetup. exe is a bootstrapper for the Config. Mgr client installation, and client. Ccmsetup. exe takes several paramters, some are used by ccmsetup. CCMSetup Install Switches. Here is an example of an installation string I use in an environment with multiple domains and Configuration Manager sites. These ccmsetup install swithes makes sure my configuration manager clients are always installed and connected to the right site. SMSSITECODE=P0. 1 SMSMP=cm. FSP=cm. 01. lab. net DNSSUFFIX=lab. Force. Install. 1ccmsetup. SMSSITECODE=P0. 1 SMSMP=cm. FSP=cm. 01. lab. net DNSSUFFIX=lab. Force. Install. This installation string tells the Configuration Manager client installation the following: SMSSITECODE=P0. Client. msi use P0. SMSMP=cm. 01. lab. Client. msi use cm. FSP=cm. 01. lab. net. Client. msi use cm. DNSSUFFIX=lab. net. Config. Mgr client will use this domain for all connections where domain name is not specified./MP: CCMSetup. Force. Install CCMsetup. CCMSetup. exe parameters/MP/FSP/Logon/Force. Install. Any parameter prefixed with “/” is a ccmsetup install switch and is used by CCMSETUP itself. They only control the behavior of CCMSETUP bootstrapper and do not affect the configuration of the installed configuration manager client. Specifying /MP sets the management point that CCMSETUP will use to lookup the distribution point for the installation, it do not in any way configure the management point used by the installed configuration manager client. You can specify several management points with /MP. It is also considered best practice to specify the FQDN (Fully Qualified Domain Name) when you specify the management point. Management points that use secure communication must be specified with HTTPS prefix in the url. Config. Mgr Client parameters. SMSSITECODESMSMPFSPDNSSUFFIXCCMSetup install switches that are all capital letters without the prefix “/” are passed directly to Client. CCMSETUP bootstrapper. These settings directly affects the Config. Mgr client and its configuration. They don’t have to be capital letters but is considered best practice to write them like that as it is easier to read. By specifying SMSMP and SMSSITECODE you tell the installed configuration manager client to use a specific management point and assign itself to a specific site instead letting the client look it up and discover it itself, thus saving time. For some customers of mine, this is the only way to make sure the sccm client connects and configures itself to the right site. This is espeically important in multiple domain / site environments or when you want to manage a computer that is in a workgroup and not part of any domain. Note that you can only specify one management point with SMSMP as the Configuration Manager client can only connect to one. SMSMP=https: //cm. SMSSITECODE=P0. 11ccmsetup. SMSMP=https: //cm. SMSSITECODE=P0. 1In this post I only touched a few of the many parameters available. Check out Microsoft Tech. Net for more install switches for both ccmsetup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |