Professional Documents
Culture Documents
What is SCCM?
* SCCM Stands for System Center Configuration Manager
* It is a Microsoft tool with the help of SCCM we can manage the Systems as well as we can
configure the systems.
* SCCM is formally known as SMS (System Management Server).
Why to use SCCM:
* To increase IT productivity and efficiency by reducing manual tasks and letting you focus on
high value projects.
OR
* Increase the overall productivity by providing the right software at the right time.
Features:
* Software Distribution
* Software Updates/ Patching
* OSD (Operating System Deployment)
* Reports
* SCCM Upgrade
* Power Management
* Remote Control
* Inventories
a) Hardware Inventories
b) Software Inventories
* RBAC (Roll-Based Accessed Control)
History of SCCM:
* 1st version of SCCM is SMS 1.0 November 1994
* Latest version of SCCM is MEMCM 2010 (Oct 2020)
* MECM (Microsoft End Point Manager Configuration Manager)
What is the differences between SCCM and SMS?
* SCCM (System Center Configuration Manager).
* With the help of SCCM we can manage the systems as well as we can configure the systems.
* SMS (System Management Server).
* With help of SMS we can manage the systems only. We can’t configure the systems.
Hierarchy of SCCM/Capacity of Planning/Size and Scale of Configuration Manager: or
How many sites are there in SCCM 2012?
1. CAS (Center Administration Site):-
* CAS can manage the systems indirectly.
* One CAS can manage the systems up to 7.5 Lacks indirectly.
* One CAS can support up to 25 Primary sites (PS).
* CAS is optional site, if we are using only one PS.
* CAS is always top level site, if there is exits.
Prepared By Srinivas
NOTE:-When CAS is required?
{more than 1.5 lack system CAS is required and mandatory, less than 1.5 Lack systems CAS is
optional and also more than one primary site CAS is required and less than one primary site CAS
is optional}.
* It requires SQL server database to store configuration information.
* It doesn’t support client assignments (Talking).
* It is used for reporting and administration.
2. Primary Site (PS):-
* It manages clients in well-connected networks.
* PS is very important site in SCCM hierarchy.
* Without PS there is no SCCM.
* PS can manage the systems directly.
* One PS can manage up to 1.5 Lack systems without database and 1Lack systems with database.
* It supports client assignments.
* It requires SQL server database to store the configuration information.
* PS is the heart of SCCM.
3. Secondary Site (S.S):-
* S.S are the optional sites, usually you can go for S.S if there is a slow or unreliable network
bandwidth.
* S.S basically used for remote locations those are more than 500 systems and less than 500
systems go for distribution point and we need to enable Branch cache.
* S.S doesn’t support client assignments.
* S.S also required SQL server expresser or SQL server database to store configuration
information.
Note: - Most of the time SQL server expresser we can use because it is free of cost.
* One S.S can manage up to 15 thousands systems.
Management Point (MP):-
* It is an important site system role in our SCCM hierarchy.
* One MP can manage up to 25 thousands systems/devices.
Roles of MP or Jobs of MP:-
* MP receiving the policies from the top level site and sends to the client systems/devices.
* MP receiving the Status messages from client machines and sends to top level site.
* MP will take care of site assignments.
Distribution Point (DP):-
* It is one of the important site system role in our SCCM hierarchy.
* It is used to store the content of applications, Packages and OSD files information.
* One DP can manage up to 4 thousand devices.
AD (Active Directory) or ADDS (Active Directory Domain Service):-
* AD is a centralized database server by which we can manage the company objects centrally.
Company objects are like,
Prepared By Srinivas
> System Information, User Information, Groups Information, Printers Information, Scanners,
Routers, Cisco Phones, All the Video conference devices.
Components of AD:-
1. Domain
2. DC (Domain Controller)
3. DNS (Domain Naming Service)
4. DHCP (Dynamic Host Configuration Protocol)
1. Domain: - Domain is a logical name which represents company or organization
Ex: -
Company Name ←Facebook.com → Domain
Company Name ← Google.com→ Domain
Company Name ←Wipro.com→ Domain
2. DC (Domain Controller):- DC is a server where the domain is configured.
3. DNS (Domain Naming Service):- DNS is a service which converts Name to IP Address and
IP address to Name
EX: - Aadhar Name → Number
Aadhar Number → Name
Name → IP Address
IP Address → Name
* There are two types of zones are there in DNS
1. Forward Lookup Zone 2. Reverse Lookup Zone
1. Forward Lookup Zone: - It converts Name to IP Address
2. Reverse Lookup Zone: - It converts IP Address to Name
4. DHCP (Dynamic Host Configuration Protocol):- DHCP is a feature which is used to assign
an IP address to the newly systems and also it revokes the IP address from unused systems.
Q) How many sites are there in SCCM 2007?
There are 4 sites are there in SCCM 2007
1. Primary Site 2. Secondary Site 3. Parent Site 4. Child Site
1. Primary Site: - Manages Client’s in well-connected networks.
2. Secondary Site: - Controls content distribution for clients in remote locations across links that
have limited network bandwidth.
3. Parent Site: - It is a top level site in SCCM hierarchy and it does not come under any other
sites.
4. Child Site: - A site which comes under a site in a structure and gives information from that site
(Higher level Site) known as child site.
Prepared By Srinivas
> Typical option then click NEXT
> Installer disc image file option SELECT click on browse and select (Windows server 2012R2
iso file)
> Click on NEXT
> Give virtual machine Name ADS
> Browse and select the drive on PC Make new folder Name AD (E Drive)
> Click on NEXT
> Disk Size (100 GB)
> Single file → Click NEXT
> Click on FINISH
> Click NEXT
> INSTALL NOW
> GUI → NEXT → ∙ I Accept → NEXT → CUSTOM → NEXT → INSTALL
Prepared By Srinivas
> ∙ Select Role-based or feature based installation
> Click on NEXT → Server Selection
> ∙ Select a server from the server pool
> Click on NEXT
> Server Roles here select Active Directory Domain Service → Click on Feature
> Click on NEXT → NEXT → INSTALL
Warning → Promote this server to DC Link
> Select add a new Forest ∙
> Root domain name IT.COM → NEXT → PWD:Welcome@123 → Conform PWD:
Welcome@123 → NEXT → NEXT → NEXT → NEXT →NEXT
> Give the DNS IP Address here 10:10:10:1 then
> Click on Rerun Prerequisite check → INSTALL → CLOSE→CLOSE→ Re-start
automatically
How to Verify DNS is Working or not?
We can verify through command Line i.e. “nslookup” in CMD
How to Register the DNS Forcefully?
Through CMD “ipconfig /registerdns”
Prepared By Srinivas
Q) What are the types of Distribution Points?
There are 4 Types of distribution points
1. Standard DP 2.Pull DP 3. PXE & Multi-cast DP 4. Cloud DP
1. Standard DP: - A Standard DP is used to serve the content to clients.
* There is a limit of 250 DP’s per site (and S.S).
2. Pull DP: - A Pull DP is very similar to Standard DP expect that is gets it content from another
source DP (known as Source DP).
* This minimizes the content distribution load on the site server.
* There is a limit of 2000 Pull DP’s per site and S.S.
3. PXE & Multicast DP: - DP’s can be configured to respond to PXE requests and send multicast
streams as part of OSD scenarios.
* In order to support these features WDS must be installed and enabled on the DP.
* Both Standard DP’s and Pull DP’s Supports PXE & Multicast DP’s.
4. Cloud DP: - A Cloud DP is an Azure hosted DP that can be rapidly scaled up or down to meet
changing requirements.
* Supports for elastic operations such as temporarily large distribution to clients.
Ex: - Roll out of a new CRM tool
* It does not support PXE.
Prerequisites of CAS or Primary Site:
* .Net Framework 3.5.1
* .Net Framework 4.5
* BITS (Background Intelligent Transfer Service)
* RDC (Remote Differential Compression)
* IIS or Web Server (Internet Information Service)
* SQL (Structure Query Language)
* ADK (Assessment Deployment Kit)
Prerequisites of DP, MP and Secondary Site:
* .Net Framework 3.5.1
* .Net Framework 4.5
* BITS (Background Intelligent Transfer Service)
* RDC (Remote Differential Compression)
* IIS or Web Server (Internet Information Service)
Q) What is BITS?
A) BITS is a feature, which resumes where it is interrupted. While transferring the data from one
location to another location.
Q) What is RDC?
A) RDC is feature, it computes the changes between Source and Destination and transfers only
changes to the Destination.
Prepared By Srinivas
STEPS TO INSTALL PREREQUISITES
> SCCM Server → Click on server manager Icon → Click on add roles and features → NEXT →
Roll-based → NEXT → Select server pool → NEXT → Here we need to select .net framework
3.5.2 → NEXT → Here we need to specify an alternate Source Path like sxs folder path
If you want sxs path first we need to install VM tools
How to install VM Tools
First we need to share the folder
> Go to VM Click → Settings → Options →Shared Folder → Click on Add → NEXT → Browse
Siva sir folder → Enable this share every one → Read/Write → Done
Now Install VM Tools
> Go to VM Click → Settings → Options → Install VMWare tools → Double click on VMware
tools / DVD Drive (D) on PC → NEXT → Typical → NEXT → Install → Re-start
Prepared By Srinivas
user NEXT ∙ windows Authentication → Add Current user NEXT ∙ Tabular mode → INSTALL
→ OK
Prepared By Srinivas
Why Extending AD Schema:-
* If you want to store SCCM sites configuration information in AD, we need to Extend Existing
Ad schema.
STEPS TO EXTEND AD SCHEMA
→ Go to SCCM 2017 Dump folder → SMSSETUP folder → Go to BIN → I386 → extadsch.exe
file Right click on it → Run as Administrator → [Go to AD Machine] → Go to Tools ADSI Edit
→ Actions → Connect to →OK→ Expand default naming → Expand DC = Right click on CN =
Systems (Management) → NEW → Object → Container → NEXT → Value: System
Management → NEXT → FINISH → CN = system extend →Right click on CN = System
Management → Go to Properties → Security → Advanced → Add → Select a principal → Object
types (Computer) → SCCM → OK → Full Control → OK.
DISCOVERY METHODS
Discovery Methods are the methods used to discover object information from AD to SCCM
site database.
There are 6 types of discovery methods are there in SCCM.
1. Active Directory Forest Discovery Method [adforestdis.log]
2. Active Directory Group Discovery Method [adsgdis.log]
3. Active Directory System Discovery Method [adsysdis.log]
4. Active Directory User Discovery Method [adusrdis.log]
5. Heartbeat Discovery Method [InventoryAgent.log]
6. Network Discovery Method [networkdis.log]
Path: - C: PM/MCM/LOGS
Prepared By Srinivas
Note:-
* By default Heartbeat discovery method is enabled.
* Heartbeat discovery method which will run from client side and remaining methods are running
from AD side.
* Active Directory Forest Discovery Method is the new discovery method from SCCM 2012
onwards.
LDAP: - Light weighted Access Directory Protocol
LDAP Port Number is 389
Prepared By Srinivas
DDR files contains:-
It contains Systems information, systems name, NetBIOS name of computer, IP address
and IP Subnet of a computer and the computer OS name.
Q) In SCCM 2007 & 2012 what are the Discovery Methods are there?
1. Active Directory System Discovery Method: - It discovers computers from the specified
locations in active directory domain services (ADDS).
2. Active Directory User Discovery Method: - It discovers user accounts from the specified
locations in active directory domain services (ADDS).
3. Active Directory Security Group Discovery Method: - It discovers security groups, including
local, global and universal groups from the specified locations in active directory domain services
(ADDS).
4. Active Directory System Group Discovery Method: - It discovers additional information
about previously discovered computers from the specified locations in (ADDS).
5. Heartbeat Discovery Method: - Used by active configuration manager clients to update their
discovery records in the database.
* Because it is initiated by an active client, it does not discover new resources.
Purpose: - We can create automatic boundaries by using IP Subnet mask and AD Site.
6. Network Discovery Method: - Searches your network infrastructure for network devices that
have an IP address.
7. Active Directory Forest Discovery Method: - Forest discovery method is the new discovery
method from SCCM 2012 onwards.
* Which discovers other forest in the network.
* We can create Automatic Boundaries by using IP subnet mask and AD site and we need to enable
these two (IP subnet mask and AD site).
Note: - What is the port number for WMI = 135
Prepared By Srinivas
Note: - Every boundary must be a part of at least one boundary group.
Q) How to install a client at a time on bulk of machines (New Machines)?
ANS: Create a collection and install client on that collection so that all the machines will be
installed.
COLLECTIONS
Collections are nothing but group of resources (Resources are nothing but either users or
computers)
There are two types’ collections
1. User collections
2. Device collections
1. What are the Default User collections:-
* All user groups
* All users
* All users and user groups
2. What are the Default Device collections:-
* All desktop and server clients
* All mobile devices
* All systems
* All unknown computers
Prepared By Srinivas
Q) How do you conform whether MP is working or not?
ANS: I can verify through the log file i.e. MPCONTROL.Log file
Status code : 200
Text is : OK
HTTP Port No : 80
HTTPS Port No : 443
MP is working fine.
1. SMS_EXECUTIVE
2. SMS_NOTIFICATION_SERVER
3. SMS_SITE_BACKUP
4. SMS_SITE_COMPONENT_MANAGER
5. SMS_SITE_SQL_BACKUP
6. SMS_SITE_VSS_WRITER
CLIENT INSTALLATION
* SCCM is a two tire architecture nothing but there is a server and clients.
* Without client software in the devices the SCCM site server not able to manage the devices.
How Many Ways To Install Client Software:-
1. Client Push Installation
2. Manual Installation
3. Automatic site-wide client installation
4. Through OSD
5. Through Software Updates
6. Using Logon Script
7. Using Group Policy
What are the Pre-requisites or Dependencies of Client Push Installation?
* The site server computer account or client push installation account is a member of the local
administrator’s group on the client computer.
* The site server can resolve the computer name for the client and access the ADMIN$ share.
* The windows firewalls and any other firewalls must be blocked.
* The Management Point (MP) is operational.
Prepared By Srinivas
Note: - Once the client is install three folders are created in C: Windows in the client side
* CCM Setup
* CCM
* CCM Cache
Steps To Provide Computer Account or How to Give Computer Account:-
Open Console → Go to Administrator → Site Configuration → Click on sites → Right click on
particular site → Client Installation Settings → Client Push Installation → Accounts → New or
Existing account → Select → ok → Apply →OK.
Client Push Installation Backend Process:-
* Once the client push installation is completed from the console, it creates CCR Files for each
computer and stores into CCR.Box folder.
* Once CCR files are placed into CCR.Box folder then CCM will trigger and reach the each
CCR and starts the client installation as follows.
* CCM will try to connect to the client machine ADMIN$ Folder [C: Windows] with the given
client push installation account.
* Once it is connected to the ADMIN$ folder then it creates the CCM Setup folder under
ADMIN$ folder and then copies the client binaries from the primary site server.
* The client binaries are CCM Setup.exe & Mobile Client.tcf files.
* It will run the CCM Setup.exe to install the client.
CCM Setup.exe:-
* CCM Setup.exe process will try to contact MP to downloaded other dependency files and install
the client.
* Once the client is installed it creates SMS Agent Host Service in the client machine.
Note:-
* Once the client is installed successfully one services is started i.e. SMS Agent Host Service, one
application is created i.e. Software Center and one icon is created i.e. Microsoft Configuration
Manager Icon.
Prepared By Srinivas
Most of the reasons for client failure:-
* May be client push installation account issue
* Network issues
* System side issues (WMI issue)
* May be MP is not operational
* Platform not supporting issue
Q) If the machine is not in our SCCM console can we install client software?
ANS: Yes, we can install
➢ Automatic site-wide client installation
➢ Client push installation
Q) How to repair the client?
ANS: CCMRepair.exe Path: C: windows/CCM
* It will remove the client and re-install the client
Q) How to uninstall the client?
ANS: CCM Setup.exe /Uninstall Path: C: Windows /CCM Setup
Note: - Whenever the client installation is running one file is created under task manager i.e.
CCMEXEC file
Prepared By Srinivas
SCCM CLIENT ERROR CODES
> Distributing (or) installing the software to Devices or Users is called "Software
Distribution".
> Software distribution allows you to push any software to the client computers in your
enterprise.
> It uses packages to deploy software applications, and within those packages, commands
called programs that tell the client what executable file to run.
> A single package can contain multiple programs, each configured to run differently.
> Packages can also contain command lines to run files already present on the client, without
actually containing additional source files.
> Advertisements are used to specify which collections receive the program and the
package.
Prepared By Srinivas
Package Model:
Steps to create Package:
• Open Console
• Go to Software Library --> Application Management --> Package
Prepared By Srinivas
• Here we need to select the required option to create the program.
• Here Select the Standard Program (If we want to take both devices and users
(Or)
• If we want to take only Devices select Program for Device.
• If you don’t want to create program select do not create program
• Click on Next.
• Here we need to provide the program details and provide the command line to install
/ uninstall the application.
• If we are installing the application use the commad line msiexec.exe /i ( drag the
sorcefile here) /qn.
Prepared By Srinivas
• For unistall program use the command line msiexec.exe /x ( drag the sorcefile
here) /qn.
• For all msi applications silent parameter is /q but it will get changed for .exe
applications.
Run: Normal, Maximize, Minimize, Hidden (Based on requirement we need to select
but always prefer hidden)
Program can run: Only when a user logged on, Whether or not a user is logged on,
only when no user is logged on (Always use whether or not a user is logged on)
• Click on Next.
• Run another program first: If we need to install anything before installing software
we need to select this option otherwise no need to select.
If you want to add any dependency we can add here but we can add only one package
as dependency for one package
• This program can run only on specified platform: We need to install specific
windows we need to select any one other wise no need.
• Estimated Disk Space: As per our requirement or give unknown.
• Maximum allowed run time (Minutes): Here how much time mentioned before that
specified time need to install app otherwise quite the app automatically.
Prepared By Srinivas
Click on Next
• Here will get all details of package
Prepared By Srinivas
• Here successfully created package.
• Click on Close.
Now this package we need to distribute to Distribution point and Deploy to Collection:
• Select Package --> Right click --> Deploy.
Prepared By Srinivas
Click on Deploy.
• Here give the Collection (Based on our requirement) (Before doing all this above steps
we need to create a collection if the collection is not created).
If the collection is already created then we need to deploy it to the existing collection.
• If you click on add option we can add distribution point.
• Click on Next.
Prepared By Srinivas
• Here give the Distribution Point (Click on Add and give the Distribution Point).
• Click on Next.
• Available: If the application is deployed to a user, the user sees the published
package and program in the Application Catalog and can request it on demand. If the
package and program is deployed to a device, the user will see it in Software Center
and can install it on demand.
• Required: Nothing but mandatory deployment, once the machine received policy
the deployment will happen automatically. It means it will not wait for any user’s
interaction.
Prepared By Srinivas
For required mode application will not show in software center in package model.
• Click on Next.
• Click on Next.
Prepared By Srinivas
• Here we have an option called peer cache, it will allow the clients to share content
with other clients on the same subnet. Need to enable this check box
• Click on Next. (Here Deployment options need to select based on our requirement).
Prepared By Srinivas
• Click on Close.
Once finish all the above steps check the Package deployed or not.
Prepared By Srinivas
• Then you can able to see how many devices are success state, how many devices are in
progress State, how many devices are in Error state and how many devices are in
Unknown state.
Once success the above all steps we need to check application available or not.
• See the above picture the 7z and Adobe reader software's were available on Software
Center. If user want this software he can install manually.
• Once user installed software will show status like below diagram.
• Go to Application Status check installed or not.
Prepared By Srinivas
Backend (or) Trouble shooting process for package Model
Application Model:-
An application in Configuration Manager contains the files and information that are required
to deploy software to a device. Applications are similar to packages in Configuration Manager
2007, but contain more information to support smart deployment. An application must
contain one or more deployment types which contain the installation files for a software
package. By using deployment types with applications, you can create one application which
contains multiple installation files for a software package on different platforms such as a
Windows computer or an iOS device. Configuration Manager Can then use rules that you
configure to determine which software package gets installed on which device.
Prepared By Srinivas
user’s device, you can now deploy software to the user and to the device. This functionality
can help you make sure that the most important software is always available on each device
that a specific user accesses. If a user acquires a new computer, you can automatically install
the user’s applications on the device before the user logs on.
For example, if an application is deployed to a collection of users, you can view the
compliance state of the deployment and the deployment purpose in the Configuration
Manager console. You can monitor the deployment of all software by using
the Monitoring workspace in the Configuration Manager console. Software deployments
include software updates, compliance settings, applications, task sequences, and packages
and programs.
• The first step would be creating an Application we will first download the application
& place the setup file in folder and sare the folder
Prepared By Srinivas
➢ Click on Create Application .Select automatically detect information and choose
type as windows installer (native).Specify the location of 7zip.msi file. Here if we
want to do manually we can do by selecting manually option.
• We get to know that the configuration manager couldn’t get the details about the
publisher of 7 zip setup file we will import the file by clicking yes.
Prepared By Srinivas
➢ Verify the details Click on Next.
Prepared By Srinivas
➢ Here we can see detailed summary of application ,after checking this click on next
Prepared By Srinivas
➢ Now the application in available in console under software library→ application
management → applications. We can see all the applications under the application
folder.
Prepared By Srinivas
➢ Click on next
➢ Now we are going to add the distribution points here to which you want to distribute,
by clicking on add option
Prepared By Srinivas
➢ When we click on add will get list of distribution points and choose the required one
from the list.
➢ Click on ok.
➢ Now the distribution point is added.
➢ Click on next.
Prepared By Srinivas
➢ Click on next. Then close.
➢ Now the content is distributed to DP’S.
Prepared By Srinivas
➢ Select Application then go to Deployment Types --> Select Deployment Type -->
Right Click --> Properties.
Deployment types: This is nothing but the way we are executing the application with the
given requirements.
➢ Click on Properties.
Prepared By Srinivas
➢ Click On Programs.
➢ Here the both install & uninstall programs will create automatically according to the
source file and the “q” is silent parameter for all MSI applications, but the silent
parameter for EXE applications is vary by the application.
➢ Silent parameter: which means we are installing the application without user
interaction.
➢ Go to Detection Method: This is the method will try to find out Application Already
installed or not in machine. If application already installed it will exist. Suppose
application was not installed it will continue to next process.
➢ Here we add Clauses there are few types of clauses is there if we want we can set.
Prepared By Srinivas
➢ Click on Add Clause. Will get detection rule window
➢ Here Setting Types: File System, Registry, Windows Installer 3 ways we can set.
➢ Type: File, Folder 2 ways we can set.
➢ Give the Path & Folder Name
➢ Then If we use 2 Clauses in this case we can use 2 types of connectors like AND, OR.
1. File system: we need to browse the path for the application and need to provide
the folder name as well.
2. Registry: we need to provide the paths to detect the application whether it is in 32
bit or 64 bit.
FOR 64BIT: - HKLM-SOFTWARE-MICROSOFT-WINDOWS-CURRENTVERSION-
UNINSTALL-CHECK FOR THE APPLICATION HERE
3. Windows Installer: - Here we will use MSI product codes to detect the application.
Prepared By Srinivas
➢ User Experience
➢ Here we need to look into the maximum allowed run time by default it is 120 min and
we can change it.
Maximum allowed run time: we are giving the particular time to install the application. If
the deployment failed / success within the given time limit it will go for next installation, and
if the run time more than the given time then it will show status as in-progress /failed.
➢ In Requirements
The requirements are nothing but hardware features or the operating system, which
means on which operating system (Ex: win7, win10) the application should install.
Prepared By Srinivas
➢ Click on Add then add Requirements.
➢ Based on Requirement select Category, Condition, Return type, Operator, Value
(MB).
If these requirements will satisfied then only will install application.
➢ Return Codes
We will display the below return code for the status of installation.
Prepared By Srinivas
➢ Dependencies: Here we can add dependencies whatever dependencies we added
before installing our application these dependencies will execute Install/Uninstall.
Here we can add no.of Dependencies.
Prepared By Srinivas
➢ The applications which we are adding as dependencies that should be installed on
machine before the actual application installation. If the dependencies are already
there in machine then it will exit otherwise it will start installation of dependencies
first
➢ If we want give Dependency group name or click on add will get list of applications
and select from the list.
➢ Enable the check box for the selected applications as dependencies. Then click on ok.
Prepared By Srinivas
Follow above steps and add detection methods, Requirements, Dependencies etc… in
Deployment type
➢ Supersedence: Supersedence is the one of the feature in application model it will do
Uninstall older versions and install current versions. And this is new feature from
2012 on words.
Then Go to Application --> Right click --> Properties --> Add Supersedence.
➢ Click on Properties.
➢ Select Supersedence.
Prepared By Srinivas
➢ Click on Add.
➢ Here we need provide the superseded application ,means which is already there in
your machine and select the old deployment type and select the new deployment
type(which you want to replace with) .if you enable the uninstall option it will
uninstall the old one and install the new one, if not enabled the both versions are
available in machine. Then click on ok.
Prepared By Srinivas
Go to Console --> Software Library --> Application Management --> Applications
--> Right click --> Properties --> Deploy.
➢ Click on Deploy. Here we need select the target collection, then click on ok.
➢ If collection is not exist we need to create the collection for the given list of devices.
➢ Here we need to specify the content destination which we distributed the content to
DP’S.
If we missed to distribute content to any DP we can add that distribution point here
by clicking on add option.
Prepared By Srinivas
➢ Click on next
➢ In deployment settings the action always should be install and the purpose we can
give available or required mode.
➢ If it is available mode the application will be available in software centre and
whenever user want to download the application he can download and use the
application.
➢ But after the deployment the application will not show in software centre
immediately because the actual client policy interval time is 60 min, after that only
the application available in software centre.
➢ If you want to display the application in software centre immediately we need to run
the actions from configuration manager. (1.machine policy retrieval and evaluation
cycle, 2. Application deployment evaluation cycle)
➢ If it is in required mode the deployment will happen automatically in machine, and
the application will be available in software centre.
Prepared By Srinivas
➢ If you want to schedule the deployment we can provide the particular time.
This is nothing but maintenance window, we are scheduling the time as per the
requirement.
➢ Click on next.
Prepared By Srinivas
➢ If the installation reached the given deadline we can ignore the maintenance window
by enabling the below check box (software installation).if you enable the system
restart, once the installation completed the restart will happen outside maintenance
window.
➢ Here will get the summary of all the setting that we provided to the application
Prepared By Srinivas
➢ Click on close.
➢ Once the deployment done need to check the deployment status in monitoring
workspace.
Monitoring→deployments
In deployments we can see the status of all the machines. (Status: success, in
progress requirements not met, failed) We need check and trouble shoot the
machines which is under failed, unknown and in-progress.
• Under the deployments we need select the particular deployment and see the
status
Prepared By Srinivas
• To pull the report for this deployment you’ll find this report in the Software
Distribution – Application Monitoring folder in the Reporting node in
the Monitoring workspace.
• There we need provide the application name and collection name then click on
view report. In this report will get list of machines with their status.
Prepared By Srinivas
• Once the deployment successful on machine application is available in software
centre, then the user can download the application.
Prepared By Srinivas
Application Model Troubleshooting Logs:-
> Once we deploy the application on the machine, first we need to check whether the
machine receiving the policy or not, I can verify PolicyAgent.log file.
> Once the machine was receiving the policy, detection method will trigger so the application
was discovered or not so I can verify Appdiscovery.log file.
> If the application was not discovered, then it will goes to next step requirements are met
or not, I can verify AppIntentEvaluator.log file.
> If the requirements are met if the application was not discovered then our machine is found
the DP path or not, I can verify CAS. Log file.
> Once our machine is found the DP path, then I will check content is downloading
successfully on local machine from DP, I can verify ContentTransferManager.log file.
> Once the content is successfully downloaded to CCM cache, then I will check application
successfully installed or not, I can verify AppEnforce.log file.
> These are the log files I will check.
What are the difference between application model and package model?
Package Model Application Model
Package model is the old model Application model is the new feature from
SCCM 2012 onwards
In package model package details we need Here we will get application details
to enter manually like, Package name, automatically from the source folder.
version, language, manufacturer etc.
Here programs need to create manually Here it creates programs automatically
Here for one package we can add only one Here for one application we can add n no.of
package as a dependency, We can’t add applications as a dependency.
more than one package as a dependency.
Detection methods are not there in package Detection methods are there in application
model. model.
Supersedence feature is not there in Supersedence feature is there in
package model. application model.
Requirements are not there in package Requirements are there in application
model. model. Like RAM Space, CPU Speed, Disk
Space, etc.
User approval mechanism is not there in User approval mechanism is there in
package model. package model.
Q) What is detection method and what are the types of detection rules?
ANS: Detection method is the method it will try to find out already application was installed
or not, it will check before deploying, suppose it is already installed it will exit.
Types of Detection Rules:
> File System
> Registry
> Windows Installer
Prepared By Srinivas
Q) What is Supersedence?
ANS: Supersedence is the feature it will uninstall the older applications and install the new
or current versions or applications.
Note:-1 Based on the Package Id we need to verify whether the policy received or not.
Note:-2 Based on Unique Id or scope Id we need to verify whether the policy received or not.
Note: - 3 Application model we can’t support .exe files directly for exe files we need to give
application details manually.
Note: - 4 The content size is more than 5GB to select run program from DP in Package model.
Note: - 5 In application model we need to increase the CCM cache folder size
Double click on client settings
↓
Select client cache settings
↓
Configure cache
↓
Here we need to increase [YES/5120 MB]
Prepared By Srinivas
SOFTWARE UPDATES or PATCHING
Note: - Every month 2nd Tuesday patches are released by Microsoft, those released patches
are available in Microsoft update catalog.
Prepared By Srinivas
STEPS TO INSTALL WSUS
> Open server manager icon
→ Click on NEXT
Prepared By Srinivas
→ ∙ Role-based & click on NEXT
→ Click on NEXT
Prepared By Srinivas
> Select Windows Server Update Services (Add Features).
> Click on Next.
Prepared By Srinivas
> Click on Next
Prepared By Srinivas
> Give the path here will store all software updates.
> Give the Data base name and check connection (It was successful).
> Click on Next.
Prepared By Srinivas
> Click on Install
> WSUS Installed successfully. No need to launch this application (Because we need to do
patching only WSUS itself then only we need to launch).
> Click on Close.
Prepared By Srinivas
> WSUS was installed successfully.
> Go to Search --> Open WSUS
Prepared By Srinivas
> Click on Next
Prepared By Srinivas
> Click on Next
Prepared By Srinivas
> Select Language Click on Next.
> Select Products as per our requirement (Based on selected products patches will
download).
> Click on Next.
Prepared By Srinivas
> Select Classifications (As per our requirement) Bit prefer above 3 updates.
> Click on Next.
> Select Synchronization Manually Click on Next. (Based on requirement Select Above
options).
> Click on Next.
Prepared By Srinivas
> Click on Next.
> Click on Finish
> By Using Above steps we can open WSUS Console.
Warning: - Launch the post installation task we need to click
↓
Failed means
↓
We need to install .Net framework 4.5 and above we need to update
Prepared By Srinivas
What are the pre-requisites for SUP Software Update Point?
* WSUS 3.0
* WSUS 3.0 Administrator Console
* BITS
* Windows Installer
* Windows Update Agent
* Site Server Communication
* Network Load Balancing (NLB)
Prepared By Srinivas
> Use Existing Account
> Click on Next.
Prepared By Srinivas
> No need to select Proxy details.
> Click on Next.
> Here select WSUS Ports 80 and 443 (But in real time Preferred only 8530 and 8531
ports).
Prepared By Srinivas
> Select Allow Intranet-Only Client connections
> Click on Next.
> Click on Use Credentials to connect to the WSUS Serer and give the Existing Account.
> Click on Next.
Prepared By Srinivas
> Select the schedule as per our requirement and Select Alert when synchronization
fails on any site in the hierarchy.
> Click on Next.
Prepared By Srinivas
> Select above option Click on Next.
Prepared By Srinivas
> Select Product Details. (As per our requirement we need to select and download).
> Click on Next.
> Select Language. (As per our requirement need to select languages).
> Click on Next.
Prepared By Srinivas
> Verify the details and click on Next.
Prepared By Srinivas
> See the above picture software update point was installed successfully.
> If we want to edit anything on Software update point.
> Go to Administration --> Site Configuration --> Sites --> Select Primary Site --> Right
Click --> Select Configure Site Component --> Select Software update point.
> Select Software update point here and modify what we want.
> Click on Software update point.
Prepared By Srinivas
> Like above screen shot select any tab and modify
> Then Click on Apply, OK.
> Once finish the above all steps then go to Console.
> Open Software Library --> Software updates (As per our schedule it will trigger and
download the patches from Microsoft. If we want to do manual sync click on?
Synchronize Software updates on top of the console. (It will trigger immediately).
> See the above screen shot once sync was completed as per our requirement all patches was
downloaded and showing above (Here 790 items was found).
> Log file for synchronization trouble shooting: wsyncmgr.log (Path: C: Program files \
MCM\Logs)
Prepared By Srinivas
> Observe the above logs the sync was completed 100% successfully.
Prepared By Srinivas
o Status Message 6705 ---> Means Synchronization In-Progress.
(Current phase is Site Database)
Log Files:
o wsyncmgr.log (Path: C:Program files \ MCM\Logs)
o WSUSctrl.log (Path: C:Program files \ MCM\Logs)
o WCM.log (Path: C:Program files \ MCM\Logs)
Prepared By Srinivas
Q) How do you conform whether the patches are downloaded successfully or not?
ANS: We can verify through the log file i.e. PATCHDOWNLOADER.LOG file.
* It is located under % temp % Windows + R
Q) How do you verify whether the SUP is successfully installed or not?
ANS: We can verify through the log file i.e. SUPSetup.Log file.
PATCHING LIFE CYCLE or END TO END PROCES OF PATCHING
> Every month 2nd Tuesday the patches are released by Microsoft those released patches are
available in Microsoft update catalog.
> On 1st Tuesday we are going to rise two change requests one CR for test group deployment
and 2nd CR for production deployment.
> Every Thursday we have CAB call, we need to attend the CAB call and we need to get the
approval from the CAB (Change Advisory Board).
> Once we are getting the approval from CAB, we perform the patching activity on 2 nd
Tuesday onwards.
> On 2nd Tuesday we need to run the synchronization may be the synchronization will trigger
as per the schedule or manually.
> Once we need to verify that the synchronization successful we will get the update from
Microsoft update catalog to our side database.
> Once we are getting the updates then we will create a software update group with the
required patches.
> Once we are creating a software update group then we need to download the required
patches. When you click on download it will ask to create package and distribute to DP’s as
well.
> Once we conform the patches are successfully downloaded then based on the target
collection we perform the deployment.
> 1st we have an IAT collection, for internal testing we are deploying.
> We have 20 IAT machines so we perform the deployment on IAT machines, if it is not
affected anything means, we will go to perform the deployment on Testing.
> After 5 days we perform the deployment on production during these 5 days we are not
receiving any issues from end users means will move to production and perform the
deployment.
> After deployment will monitoring the deployment status.
Patching Troubleshooting Log files for Client End & Server End:
> I will check PlociyAgent.log file for policy received or not
> For scanning ScanAgent.log file & WUAHandler.log file for scanning is successful or not.
> After that scanning information is stored or not, I can verify UpdatesStores.log file.
> After that Content is downloading or not I can verify ContentTransferManager.log file.
> Once the content is successfully downloaded, after that patches are downloaded or not, I
can verify UpdateHandler.log file.
Prepared By Srinivas
> For Reboot I can verify RebootCordinator.log file.
> Instead of checking all these log files, we have only one log file is there i.e. Is
UpdatesDeployments.log file. These are the log files we will check.
Prepared By Srinivas
WHAT IS MAINTAINANCE WINDOW?
ANS:-
> Maintenance window enable you to define a time when configuration manager
operations can be carried out on a device collection.
> It is a new feature from SCCM 2012 onwards and you can see in the installation status tab
in the software center.
> The following operations supports maintenance window
1. Software Deployments
2. Software Update Deployments
3. Operating System Deployments.
4. Task Sequence Deployments
5. Compliance Settings Deployments
> The maximum duration of a window has to be less than 24 hours.
> The maximum allowed runtime (120 minutes) should not exceeds than maintenance
window time (180 minutes).
RBAC (ROLL-BASED ACCESSED CONTROL):-
> RBAC stands for Role-Based Accessed Control
> It is a new feature from SCCM 2012 onwards, by which we can control the SCCM access
levels of users.
> By default 15 security rolls are there in SCCM
CLIENT SETTINGS
Client settings are the settings from SCCM client agent side to enable or disable the settings.
> There are two types of client settings
1. Default Client Settings 2. Custom Client Settings
1. Default Client Settings:-
Default client settings are the settings that are applied to all the client’s in the
hierarchy and can be modified by custom client settings.
> The priority of default client settings is 10,000.
Note:-
> By default remote tool is disable
> Remote control feature is enable through default client settings.
Prepared By Srinivas
> Through SCCM to AD Remote Control → Open Console → Go to Asserts & compliance →
Device → Right click on particular device → Start → Remote Control.
> Remote control feature is disable through custom client settings → Right click on custom
client settings → Create custom client → Remote Control → Configure (Here we need to
enable or disable).
> Based on the Priority we can enable or disable the client settings.
> Default client settings cannot delete and we can delete custom client settings.
> Deployments required for custom client settings and not required for default client
settings.
> The priority of default client settings is low and custom client settings is high.
Note: - Through Client settings we can increase the CCM Cache Size.
Double click on client settings
↓
Client cache settings
↓
Configure Cache [YES/5120]
Note: - I want to display an organization name, displayed in software center → Go to
Computer Agent client Settings.
Q) What is the Difference between Default Clients & Custom Client Settings?
Default Client Settings Custom Client Settings
* Default client settings are applied to all * Custom client settings are applicable to
the clients in the hierarchy. specific clients in the hierarchy.
* We can’t delete default client settings. * We can delete custom client settings.
* Deployments are not required for default * Deployments are required for custom
client settings. client settings.
* The Priority of default client settings is * The Priority of custom client settings is
low (10,000). high.
Prepared By Srinivas
HARDWARE INVENTORY & SOFTWARE INVENTORY
HARDWARE INVENTORY:-
* Hardware inventory is one of the client setting used to fetch the system information or
client information.
* Use hardware inventory in SCCM to collect the information about the hardware
configurations of client devices in our organization.
EX: - RAM Details, OS Details, Drive details, .etc.
HARDWARE INVENTORY BACKED PROCESS:-
* As per the given schedule hardware inventory agent will trigger on client side.
* As per the given hardware inventory classes, it will query the WMI classes and fetch the
information and these information is stores into XML files.
* This XML file will send to MP by client.
* MP Will send these XML file to MP_Relay component.
* This MP_Relay component converts XML file to MIF file
* This MIF (Management Information Format) file is processed to Database.
Prepared By Srinivas
Client Side Logs Server Side Logs
InventoryAgent.Log MP_Relay.Log, MP_SINV.Log
Path: C: Windows/CCM/Logs Path: C: PF/MCM/Logs
HOW TO CHECK HARDWARE, SOFTWARE INVENTORY DETAILS ON PARTICULAR
MACHINE?
Open Console → Go to Assets & Compliances → Devices → Right click on particular device
→ Go to Start → Resource Explorer
Here we can collect the details like HARDWARE Details, SOFTWARE Details & HARDWARE
History… Etc.
STEPS TO ENABLE HARDWARE & SOFTWARE INVENTORIES:
Open Console → Go to Administrator → Go to client settings → Go to custom or default
client settings properties → Click on H/W or S/W Inventory → Enable the S/w or H/w
inventory clients (YES)
↓
H/w or S/w inventory Schedule Every 7 Days
We can go for Every 1 Day
Maximum custom MIF File size is (KB): 250 KB
BACKUP
> Backup is an important feature or it is a site maintenance task to take SCCM application
data as a backup.
> The site maintenance task section contains information regarding each site.
> This is task provides an automated method to back up the entire site, including site
database, ConfigMgr files, registry key’s, and system’s configuration information.
> By default back up activity is disabled.
What is the log file for back up?
SMSBKUP.log file Server side log file
Path: - C: /PF/MCM/Logs
Here we can see the status message Id’s
* Status message ID: 5056 Means Backup is Successful for good back up.
* Status message ID: 5026 Means Backup is failed.
* Status message ID: 5035 Means Backup is Successful for normal back up.
Prepared By Srinivas
BACKEND PROCESS FOR BACKUP
> Back up task can be triggered as per the given schedule or manual back up.
> Once the backup is triggered the SMS_SITE_BACKUP Service will be started and it
forcefully stops the SMS_EXECUTIVE Service and SMS_SITE_COMPONENT_MANAGER
services.
> Once these services are stopped, this SMS_SITE_BACKUP service will take the backup to
the given location.
> Once backup activity is completed, this SMS_SITE_BACKUP service will go the stop mode
and starts the SMS_EXECUTIVE and SMS_SITE_COMPONENT_MANAGER.
STEPS TO ENABLE BACKUP
Open Console
↓
Go to Administration
↓
Site Configuration
↓
Click on Sites
↓
Right Click on Particular site
↓
Click on site maintenance
↓
Back up site server → Edit
↓
Enable this task (Check box enable) → Set Path
↓
Click on browse→ Under C Driver create new folder called (Backup)
↓
Apply → Ok→ Enable the alerts for backup failures (We need to enable this check box for any
backup failures).
Reasons for Backup Failures:-
> Out of Memory (Space Issues)
> Network Issues
> Permissions Issues
Q) Have You Worked on Backup?
ANS: YES, I worked on backup
Note: - Usually backup is not required for Secondary Site, Management Point & Distribution
Point.
* We can take backup for CAS & Primary Site.
Prepared By Srinivas
Q) What is Branch Cache?
ANS: System’s within the same subnet and separated from a content source to share
downloaded content locally is called branch cache.
Q) What is Peer Cache?
ANS: It will request the Content from other clients is called Peer cache.
SCCM UPGRADE
What are the Pre-requisites for SCCM Upgrade?
1. SCP (Service Connection Point).
2. Need to Check Supported versions of SQL & ADK (1903 for SCCM 1906).
How to Configure SCP:-
Open Console
↓
Administrator
↓
Site Configuration
↓
Servers & Site System Roles
↓
Select Particular Site
↓
Right click on it & Add site system role
↓
Click on set path button
↓
Provide the account details (ʘ User another account)
↓
NEXT→ ADD [SCP]
↓
NEXT
↓
ʘ Online
↓
NEXT
↓
NEXT
↓
CLOSE
> Before performing SCCM Upgrade activity we need to take some precautions, like we
need to check all site maintenance task status should be OFF.
> And if any Re-boot pending, we need to do re-boot first and Replications should be OFF
and Backup of site server.
> Service Connection Point we need to install.
Prepared By Srinivas
How To Disable Site Maintenance Tasks:-
Open Console
↓
Administrator
↓
Site Configuration
↓
Click on Sites
↓
Select Particular Site
↓
Right Click on it & Select Site maintenance
↓
Here we need to disable all site maintenance tasks & we need to Enable Backup
↓
Enable This Task [Checkbox]
[Here we need to give destination folder C:/Backup (We need to create folder in C drive)]
Schedule for Backup : Start after: 2:00 AM
Latest Start Time: 3:00 AM
↓
Enable alerts for backup task failures [Checkbox]
↓
Click on Apply
↓
Click on OK
> After install the SCP, we will get the list of updates to our site database.
How to check the latest updates of configuration manager:-
Open Console
↓
Go to Administration
↓
Updates & Servicing
> Here will get the list of updates of Configuration Manager and Select particular update.
> Initially the latest update status will show as Available to Download.
> Select particular latest update and right click on it and download the content, then the
status will show as Downloading.
> After download completed, status will show as ready to install.
How to check whether the content downloaded or not:-
> I can check DMPdownloader.Log File
> Path: - C: PF/MCM/Logs >>> Server Side log file
> The downloaded content will stored in EasySetupPayload folder.
> Path: - C: PF/MCM/EasySetupPayload
Prepared By Srinivas
Note: - While upgrading the SCCM, we need to upgrade automatically all sites are upgraded.
> Once download is completed, select particular update right click on it and run the Pre-
requisite check, then update status will show as Checking Pre-requisites.
> After pre-requisite check completed, status will show as pre-requisite check Passed.
How to check whether the pre-requisites passed or not:-
> We can verify through the log file i.e. ConfigMgrPrereq.log file.
> Path: - C Drive
> It will show the statement like pre-requisite check Passed.
> After checking all pre-requisites, it will show the statement as pre-requisites check
completed.
> After pre-requisites check, we need to install the updates.
Open Console
↓
Go to Administration
↓
Updates & Servicing
↓
Select the particular update and right click on it
↓
Click on Install update pack
↓
Then the installation will start the new updates
> After installation of new updates, to enable features of that new updates, need to go to
Administration → Updates & Servicing Expand → Select Features.
Prepared By Srinivas
Site Configuration
↓
Click on Sites
↓
Select particular site
↓
In Ribbon bar select hierarchy Settings
↓
Go to Client upgrade Tab
↓
Upgrade All Clients in the hierarchy using production client [Checkbox enable]
↓
Click on Apply
↓
OK
Note: - Post Installation of new update, we need to enable all site maintenance tasks and
Replications should be ON.
How to check the Replication Status:-
Open Console
↓
Go to Monitoring
↓
Site Hierarchy
↓
Here we need to check the Replication Status
REPORTS
Open Console
↓
Go to Monitoring
↓
Reporting
↓
Reports
> To generate the reports, in Configuration Manager, we need to install RSP Site system role.
> The RSP integrate with SQL Server and provides the effective reporting functionality, for
different kind of data sources.
> Where we install the SQL, RSP should be install on the same server.
> When we run the report, RSP component will connect to the configuration manager
database to retrieve the data.
What are the Pre-requisites for Reports?
1. SSRS (SQL Server Reporting Service)
2. RSP (Reporting Service Point)
Prepared By Srinivas
How to install SSRS
Go to Shared Folder
↓
Go to SCCM Folder
↓
SQL 2016R2
↓
Select SQL Server Reporting Service.exe
↓
Right Click on it & Run as Administrator
↓
It will open SSRS window
↓
ʘ Select the Free Edition & Provide the Path
↓
ʘ Accept
↓
Click on Next
↓
Configure Reporting Service
↓
Re-start required.
↓
Click on Connect → Start (Already Started)
↓
Select Account: ʘ Use another Account [Account: Google\Administrator
Password: Welcome@123]
↓
Click on Apply → Task Completed Successfully.
↓
Web Service URL: → Apply →Successfully
↓
Database: → Change Database
↓
Action Tab ʘ Create a new report server database
↓
Click on NEXT → Test Connection → OK
↓
Click on NEXT
↓
Change Database Name: → Report Server
↓
Click on NEXT
↓
Click on NEXT
Prepared By Srinivas
↓
Click on FINISH→OK
↓
Web Portal URL: → Click on Apply → Click on Exit → Re-start
Prepared By Srinivas
Types:-
Open Console
↓
Go to Software Library
↓
Application Management
↓
Global Conditions and Right Click and create Global Condition
> Registry Value
> AD Query
> Assembly
> File System
> IIS Met base
> Script
> SQL Query
> WQL Query
> XPath Query
Q) What is Fall Back Status Point (FSP)?
> It is a one of the site system roll in SCCM.
> It is an optional site system roll.
> If MP is not working or not reachable in that case FSP will try to capture the client
installation failure status and sends to the sites.
> FSP parameter should be passed in client installation properties.
(FSP = SCCM.GOOGLE.COM)
STEPS TO INSTALL FSP:-
Open Console
↓
Administration
↓
Site Configuration
↓
Click on servers & site system role
↓
Right click on Particular server
↓
Add site system roles
↓
We need to give Account → Next
↓
FSP (We need to select) → Next
↓
Next
↓
Close
Prepared By Srinivas
FSP Parameters:-
Open Console
↓
Administration
↓
Sites
↓
Right click on particular server
↓
Client installation settings
↓
Installation Properties
↓
SMSSITECODE=CSP FSP=SCCM.GOOGLE.COM
Prepared By Srinivas
Tell me about yourself & What the Day to Day or Daily Activities
Tell me about yourself:-
> Hi, My Self Sreenivasulu, I have around 4.6 Years of Experience in SCCM, in my total 4.6 years
of experience I worked on different different SCCM versions like SCCM 2012, 1702, 1710, 1810.
> So recently we are upgraded from SCCM 1810 to 1910, so presently I am working on SCCM
1910.
> Currently I am working in Tech Mahindra, Bangalore.
Coming to my Roles & Responsibilities
> SCCM Infrastructure activities like I can install site system roles like Management Point (MP),
Distribution Point (DP) and other site system roles like Software update point (SUP), Service
connection point (SCP), and Report servicing point (RSP), site system role as well.
> And also I can configure discovery methods, boundaries and boundary groups as well.
> And also I can install client software on all workstations by using Client-Push Method and also
I have experience in Manual installation and client remediation activities as well.
> Coming to client settings I have experience on both default client settings and custom client
settings.
> Coming to Software Distribution I have experience on both Package model & Application
Model and troubleshooting part as well.
> Coming to Software Updates i.e. Patching I have experience on Patch creation, Patch
Deployment and Patch troubleshooting part as well.
Prepared By Srinivas
OSD (Operating System Deployment)
1. Wipe & Reload Operating System through SCCM: - We will wipe an existing computer and
we will reload OS on that particular computer.
Prepared By Srinivas
STEP:-2
We need to distribute this image package to DP
Right click on Windows 10 Enterprise 1809
↓
Distribute Content
↓
Click on NEXT
↓
Add→DP [Select Checkbox] →OK
↓
Click on NEXT
↓
Click on NEXT
↓
Click on CLOSE
STEP:-3
Now we need to go to boot images and we need to send these boot images to the DP
Select boot images (X64, X86) and Right click & Distribute Content
↓
Click on NEXT
↓
Add→DP [Select Checkbox] →OK
↓
Click on NEXT
↓
Click on NEXT
↓
Click on CLOSE
STEP:-4
Now we need to create a Task Sequence and deploy this image to target (collection) computer
Steps to Create Task Sequence:-
Open Console
↓
Go to Software library
↓
Task Sequence right click on it and create task sequence
↓
ʘ Install an existing image package
↓
Prepared By Srinivas
Click on NEXT
↓
TS Name: Windows 10 (1809)
Boot Image: → click on Browse → Choose boot image(X64) en-us → OK
↓
Click on NEXT
↓
Image Package: Browse → Choose [Windows Enterprise 1809 en-us] →OK
[Select checkbox]→Partitions format….
ʘ Enable the Account
Password: Welcome@123
Conform Password: Welcome@123
↓
Click on NEXT→ ʘ Join a domain
Domain: GOOGLE.COM → Browse → OK
Domain OU: SCCMS → Browse → OK
Account: → Select → OK
Username: → SCCM Admin → Browse → OK
Password: Welcome@123
Conform Password: Welcome@123
↓
Verify → Test Connection → OK → OK
↓
Click on NEXT
↓
Click on NEXT
↓
[Uncheck two checkboxes]
↓
Click on NEXT
↓
Click on Yellow button [Select checkbox] Google Chrome
[Select checkbox] Remote Desktop Connection → OK
↓
[Select checkbox] If an application installation fails
↓
Click on NEXT → Click on NEXT
↓
Click on CLOSE
Prepared By Srinivas
STEP:-5
Now the Task Sequence is ready, we just have to deploy it to a Target collection.
Right click on Task Sequence
↓
Deploy
↓
Task Sequence Name: Windows10 (1809) → Browse → OK
Collection: [Windows 10 Device collection] → Browse → OK
↓
OK
↓
Click on NEXT
↓
Available → Click on NEXT → Click on NEXT → Click on NEXT → Click on NEXT → Click
on NEXT → Click on CLOSE
> One more thing we need to do,
Go to Administration
↓
Site Configuration
↓
Click on Sites
↓
Select particular site and right click on it
↓
Configure site components
↓
Software distribution
↓
Network access account
↓
ʘ Specify the account → Click on Yellow icon→ Choose Existing account →OK→APPLY
→ OK
Here we need to specify one account which has permission to copy a file from one location to
another location over the network.
> Go to winows10 computer where we have deployed a task sequence here, Software Center
→Click on Operating systems & install it
> It will download all the components from the DP and it will convert this computer form 1803 to
1809.
> Go to Assets & Compliance →Devices →Select the device & right click on it → Start →Remote
Control →We need to enter User name & Password
Prepared By Srinivas
> When it upgrades this computer 1803 to 1809 it disables the remote connection.
Prepared By Srinivas