Secondary-Site-Installation-Status-2.png' alt='Sccm 2012 Secondary Site Installation Log File' title='Sccm 2012 Secondary Site Installation Log File' />Default outofthebox booting on WinPE with SCCM 20122016 is quite slow Ive seen boot times up to 20 minutes.This is because System Center Configuration.Tutorial Upgrading from ADFS 2.Server 2008 R2 to ADFS 3 Server 2012 R2 Henrik March 10, 2014 at 853 am.Hi In step 11. Dear Experts, Here in my organization SCCM 2012 is configured.With the help of Expert Exchange Experts i have configured WSUS then Software updates.TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/99/57/metablogapi/16_2D1F634A.jpg' alt='Sccm 2012 Secondary Site Installation Log File' title='Sccm 2012 Secondary Site Installation Log File' />SCCM 2.R2 Step by Step Installation Guide SCCMentor Paul Winstanley.Check out my new SCCM 1.The following guide will take you through the installation of SCCM 2.R2 with a simple Primary Server approach and with the SQL server located on the same device.It assumes that no earlier version of SCCM is installed in the Active Directory domain it is being installed into.Before installing SCCM 2.R2 you will need to run through some prep work to get the Active Directory configured and extended, along with some application and rolefeature installs.Prepare Active Directory for Configuration Manager.Create the System Management Container in ADConnect to a domain controller and load ADSI Edit.Under the System OU create a new Object.Choose Container and click Next.Enter the name System Management and click Next.Complete the wizard and close ADSIEdit.Delegate control to the SCCM site server to the newly created container in AD Users and Computers.Create a custom task to delegate and choose This folder, existing objects in this folder and creation of new objects in this folderCheck all Permission boxes and complete the wizard.Extend the Schema.From the SCCM 2. 01.D7162F.png' alt='Sccm 2012 Secondary Site Installation Log File' title='Sccm 2012 Secondary Site Installation Log File' />SMSSetupBinx.Domain Controller holding the Schema Master Role.Ensure the account used is a member of the Schema Admins group in AD.Right click the Extadsch.Run as Administrator.A log file Ext. ADSch.C Drive. Check for the entry Successfully extended the Active Directory schema.Successfully extended the Active Directory schema.To check what Extadsch.Active Directory then open up the file Config.Mgradschema. ldf that is located in the same folder.Install Site Server Prerequisites.The following roles and features need to be installed onto the SCCM Site Server prior to installation BITSRemote Differential Compression.IIS Components. Net Framework 3.Add the following IIS components.Common HTTP Features.Static Content. Default Document.Directory Browsing.HTTP Errors. HTTP Redirection.Application Development.ASP. NET. NET Extensibility.ASPISAPI Extensions.ISAPI Filters. Health and Diagnostics.HTTP logging. Logging tools.Request Monitor. Tracing.Security. Basic Authentication.Windows Authentication.URL Authorization.Request Filtering.IP and Domain Restrictions.Performance. Static Content Compression.Management Tools.IIS Management Console.IIS Management Scripts and Tools.Management Service.IIS 6 Management Compatibility.IIS 6 Metabase Compatibility.IIS 6 WMI Compatibility.IIS 6 Scripting Tools.IIS 6 Management Console.Install Windows Assessment and Deployment Kit Windows ADK for Windows 8.Go to http www. ADK 8.Run the adksetup.Accept the licence agreement.This will download and install.Net Framework 4. 5.Restart the system when prompted.After the restart setup will resume.Accept the default location for installation and click Next.Select whether to join the CEIP and click Next.Accept the licence agreement.Install the following components and then click Install.User State Migration Tool USMTWindows Deployment Tools.Windows Pre. Installation Environment Windows PEOnce complete click Close.Install SQL Server.SQL Server 2. 01.SP1 is being installed as the SCCM database.Run the setup. exe.Install a new stand alone installation of SQLClick Ok.Install the product key or run in evaluation mode.Click Next. Accept the licence agreement and click Next.Include any product updates.Click Next. Click Next.Choose the feature installation and click Next.Install the selected features and click Next.Click Next. Leave as the default instance and click Next.Click Next at the disk space requirements screen.Set any account to run the SQL services, in this instance the defaults have been selected.Once confirmed, click the Collation tab.Click the Customize button.Choose the SQL Collation, used for backwards compatibility option and choose SQLLatin.GeneralCP1CIAS. Click Ok.Click Next. Use Windows authentication and Add the current user.Click Next. Set Reporting Services to install only.Click Next. Set error reporting preferences and click Next.Click Next. Click Install to begin the installation process.Once installed open up SSMS and limit the amount of RAM SQL can use to 5.RAM. Set the value for both max and min.Set SQL to run with either a named domain account, network service or local system account.If using a named account grant the log on as a service right via gpedit.GPO. Install SCCM 2.R2. Begin the install of SCCM 2.R2 by running splash.Click Install. Click Next.Choose to install a primary site in this instance.Click Next. Enter a licence key or evaluate.Click Next. Accept the licence agreement and click Next.Accept pre req licences and click Next.Create a folder to store install updates and point the SCCM install to that location.Click Next. Updates will download and install.Select any language requirements for the SCCM server and click Next.Select any client language requirements and click Next.Enter a 3 digit site code and description and click Next.Be aware of Microsoft list of pre reserved site code names.Choose whether to run the primary as stand alone or join to an existing hierarchy.Click Next. In this instance a stand alone primary is being installed.Click Yes to accept.Accept the database default configuration and click Next.Specify the path to the SQL database file and log file.In this instance it is the defaults.Click Next. Click Next to set the current server as the SMS Provider.Set Configure the communication method on each site system role as a PKI infrastructure is not being used.Click Next. Install both a MP and a DP onto the site server.Click Next. Choose whether to join the CEIP.Click Next. Click Next at the Summary screen.The following warnings can be ignored at the pre req check screen.Click Begin Install. Adobe Pdf Reader Download For Windows 8 . SCCM will begin the installation.Click close when complete.Launch the SCCM Console.Ensure the site and database report as healthy in the Monitoring workspace under System Status Site Status.Managing inactive clients in SCCM 2.Without proper client cleanup and repair, your SCCM database will be cluttered and less useful.This article covers obsolete client removal and eventual client reinstallation.One of the unfortunate aspects of being an SCCM administrator is client maintenance.When deploying applications, monitoring installations, and performing inventories, having up to date client records is very important.Inactive clients in SCCMWhen a client is no longer communicating with SCCM, you have a couple of options.But first, lets learn why our clients become inactive and how to find them.Why are my SCCM clients inactive The easiest way to explain this is to understand how a client remains active.A client remains active if it is discoverable and if it communicates with your SCCM servers.Communication can include Heartbeats.System Discovery.Network Discovery.So a client can be marked as inactive if it fails to update SCCM due to issues such as loss of connection, restrictive firewall settings, and client corruption.We are going to tackle this last problem in a bit.When dealing with inactive clients, you might run across false positives.These are Active Directory computer accounts that have gone stale no longer linked to a physical computer.When the System Discovery process runs, these objects are imported into SCCM.To avoid this issue, it is important to regularly clean stale computer accounts.How can I clean up stale records in SCCM Two Site Maintenance tasks control stale record deletion in SCCM.Within the Configuration Manager console, these can be accessed under AdministrationSite ConfigurationSites Site Maintenance.Site Maintenance is located within the top toolbar.Within Site Maintenance, you will see two tasks named Delete Aged Discovery Data and Delete Inactive Client Discovery Data.Both of these tasks should be enabled for inactive client data deletion.Site Maintenance.While you can edit the scheduled run time, be sure to keep the task run time greater than the heartbeat discovery time.By default, the heartbeat discovery runs once every 7 days.Failure to do so will result in zero clients and make client management very boringCreating a stale client Collection Because the SCCM client can occasionally mess up, it is important to have a method for reinstallation.Step 1 in this process is building a stale client collection.Under Assets and ComplianceDevice Collections, create a new collection named Client Activity Inactive.Edit the collection and make a note of the Collection ID.Then select Membership Rules.My collection ID is GC1.ECreate a new query and paste the following in as the query statement.SMSRSYSTEM. Resource.ID,SMSRSYSTEM. Resource.Type,SMSRSYSTEM. Name,SMSRSYSTEM.SMSUnique. Identifier,SMSRSYSTEM.Resource. Domain.ORWorkgroup,SMSRSYSTEM.Client from SMSRSystem inner join SMSGSystemCHClient.Summary on SMSGSystemCHClient.Summary. Resource.Id SMSRSystem. Resource.Id where SMSGSystemCHClient.Summary. Client. Active.Status 0. 1select SMSRSYSTEM.Resource. ID,SMSRSYSTEM.Resource. Type,SMSRSYSTEM.Name,SMSRSYSTEM. SMSUnique.Identifier,SMSRSYSTEM.Resource. Domain.ORWorkgroup,SMSRSYSTEM.Client from SMSRSystem inner join SMSGSystemCHClient.Summary on SMSGSystemCHClient.Summary. Resource.IdSMSRSystem. Resource.Id where SMSGSystemCHClient.Summary. Client. Active.Status0. This query simple checks to see if the Client Activity Status is equal to zero.After the collection membership updates, you should have a list of every inactive client within your organization.Exporting to Active Directory Most SCCM admins might initiate a client push to take care of any on line but inactive clients.I prefer to automate things a bit.This process will assume that you deploy the SCCM client with Group Policy and that you have that GPO scope to a specific security group.Within the SCCM console, select the down arrow top right of console.Then select Connect via Windows Power.Shell. Connect via Windows Power.Shell. Once Power.Shell launches, you will need to import the Quest AD Management cmdlets or modify this script to use the Active Directory cmdlets.Copy the script below.You will need to modify the collection.ID and modify the Add QADGroup.Member line to reflect your security group.Collection. Members Get CMDevice Collection.Id GC1. 00. 25. E Select Property Name Sort Object Name.Collection. Member in Collection.Members. Add QADGroup.Member Identity APPSCCM 2.SP1 Client Member Collection.Member. name. Collection.MembersGet CMDevice Collection.Id GC1. 00. 25. ESelect Property.NameSort Object. Name foreachCollection.Member inCollection.Members Add QADGroup.Member IdentityAPPSCCM 2.SP1 Client MemberCollection.Member. name After running the script, you should now have a Security Group that contains all of your inactive clients.This group is scoped within a GPO that installsreinstalls the SCCM client.The only step remaining is to remove the client from the group after the GPO has processed once.Because you are likely using Group Policy scripts for installation, add a second script that contains the following.Set obj. ADSys. Info Create.ObjectADSystem. Info.Set obj. Group Get.ObjectLDAP CNAPPSCCM 2.SP1 Client,OUSoftware Distribution,DCTest,DClocal.Group. RemoveLDAP obj.ADSys. Info. Computer.NameSet obj. ADSys.InfoCreate. ObjectADSystem.InfoSet obj. GroupGet.ObjectLDAP CNAPPSCCM 2.SP1 Client,OUSoftware Distribution,DCTest,DClocalobj.Group. RemoveLDAP obj.ADSys. Info. Computer.NameBe sure to modify the Get.Object command to match your group location.You will also need to delegate the ability for SELF to remove itself from the group.This will allow the computer to automatically un scope itself after the GPO applies once.The end result will be a repaired client.Collection. Members Get CMDevice Collection.Id GC1. 00. 25. E Select Property Name Sort Object Nameforeach Collection.Member in Collection.MembersAdd QADGroup.Member Identity APPSCCM 2.SP1 Client Member Collection.Member. nameWin the monthly 4sysops member prize for IT pros.Related Posts. SCCM and Group Policy update rings make updates easier.Pushing HP BIOS settings and updates with SCCM.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |