SCCMinfo

SCCMinfo

Top 25 sccm scenario based interview questions with answers

by

 

Find here not only top 25 SCCM scenario based interview questions in 2021 but there answer as well. This article covers the most commonly asked questioned in the interview using which you should be able to easily crack any interview on SCCM for at least L1 and L2 level.

 

This article is also going to make you aware for basic information about the questions and then their answer would also help you to work in production environment.

 

SCCM Interview Questions and Answers

 

Q. SCCM 2012 not discovering computers

Below could be the reasons for computers not discovering

 

Verify Computers are covered in Boundaries

 

The computers which are not getting discover might not have added in boundaries, to discover computers in SCCM, we need to create the boundaries based on either Active Directory Sites, IP Subnet, or a range IP addresses.

 

To check that in Configuration Manager Console you can go to Administration,

 

And then select Boundaries on the left pane of the console on right hand side,

 

 

Verify if your computers are covered in whatever boundaries you have configuring in list of boundaries available in right pane of the console.

 

If not, you will have to get added here the boundaries based on either Active directory group, IP subnet or IP address ranges.

 

Verify if one of the discovery methods are enabled to discover the computers within the specified boundaries.

 

 

Mainly Active Directory System Discovery and Heartbeat Discovery should be enabled marked in yellow. In my case I have disabled ADSC for some reason.

 

If SCCM infrastructure is properly implemented and Computers which like to get discovered are in the environment of Active Directory Domain Service and considering DNS and required port are configuring correctly then above mentioned should discover the computers in SCCM console.

 

Q. SCCM 2012 computer not showing up in devices

One of the important question in Top 25 sccm scenario based interview questions. This also could be related to not have added the boundaries which are covering computers to discover or if not, then discovery methods might not be enabled which helps to discover computer resources. By following above two steps of adding boundary and enabling discovery methods would start up showing in device collections in SCCM 2012 configuration manager console.

 

Q. SCCM Success program will not rerun

If you would like to rerun the program in case of below two conditions,

 

  • When Program installed successfully
  • When Program failed to install

Then there is one setting on the properties of Package deployment which can be adjusted accordingly, specifically marked in yellow with regards to rerun program,

 

 

Q. How to deploy vbscript SCCM 2012?

  • Create the normal package as usual by giving the UNC path to the vbscript file.
  • Create the program to call the vbscript
  • And when calling vbscript specify wscript then script file name ( for example, wscript test.vbs)

 

Q. SCCM retrieving policy for this computer slow

Generally when you try imaging any systems with SCCM Task Sequence Deployment process, in PXE environment at client side when you press f12 to load boot image and then once boot image loads completely then system goes and try to find the policies and some time it gets stuck on SCCM retrieving policy for this computer and take very long time on this particular stage.

 

The reason for this could be the Management Point in the environment who support to respond to client’s query is not responding in proper manner. There could be several reasons for this, will see particularly with this specific error,

 

  • Load on Management point is too much, you can check on CPU and Memory utilization for the same. Take corrective actions accordingly.
  • Just see if all the logs are getting updated in the Configuration Manager folder under Program files directory.
  • If not, then just look at if the “SMS Executive” service is running properly from the service Manager on the Management Point site system server.
  • If you see if it is running properly then also the log files for different component are not updating very frequently then although the service shows running fine but then in backend it must have got stuck.
  • To overcome this, you can try restarting the service in below three steps,
    • Stop SMS Executive Service
    • Stop SMS Component Service
    • And then start SMS Component Service when would then turn on the SMS Executive as well

 

 And then observe the log files updating moments in the Configuration Manager folder.

 

These steps should resolve the issue of SCCM retrieving policy for this computer slow

 

Q. How to find out if a software installed on a remote system is ideal or in use using SCCM?

We can use the Software Metering for finding out the usages of software installed on the system or group of systems.

 

Software Metering helps to find out

 

  • How many copies of software are there in the organization?
  • Find out any unused copies of the software,
  • Find which one are being used regularly

Particularly software file name with exe can be monitored. Below are the high-level steps for enabling Software Metering,

 

Step1:

 

Create the custom client policy setting in which you need to enabled Software Metering and Schedule Data Collection and deploy it to the collection for which you want to monitor the usages of software.

 

Step2:

 

Create Software Metering Rule with Metering Rule name, File name, Version, Language, Description, Assigned client or all clients

 

Q. How to run a batch file in SCCM task sequence?

Here are the steps to call batch file in SCCM task sequence,

 

  • Create SCCM Standard Package of content which has batch file to be called from Task Sequence
  • Create standard Program which will be calling that batch file under that package.
  • Distribute the content of this Package to the required Distribution Point
  • Then in Task Sequence go to Add – General – Run Command Line as shown below in yellow marked,

 

 

  • One you add step Run Command Line, specify below parameter marked in yellow. Give Step Name, specify batch file name (Complete batch File name with extension) in Command Line and then specify the Package by enabling checkmark on Package and then specifying the Package by doing browse.   

 

 

Click Here to know on how to update Windows 10 in just less than 5 minutes 

 

Q. Top 30 Scenario based questions for SCCM.

Find here few of the Scenario based questions for SCCM which can help clearing interview rounds or to cross check if you have the basic knowledge on SCCM.

 

  1. Define Process and approach creating and deploying Package (Name ABC for example) to be deployed on the 5000 computers in organization and provide with the report of the deployment status?
  2. Define Process and approach on workflow for coming up with some custom image which would be deployed to 1000 systems in the organization?
  3. SCCM Infra is setup in backend and you would be asked to setup PXE environment for deploying the operating system with Task Sequence. What is that steps you would be following to achieve the same?
  4. Process and steps for installing Distribution Point according to the requirement.
  5. If you have been told to design the SCCM infrastructure for the organization with having 3 offices across worldwide with 1 main office and 2 branch office covering less than 30K users and devices. To support this which SCCM topology you would consider and how would you design the Sites, Site Systems etc.
  6. If you have been told to design the SCCM infrastructure for the organization with having 50 offices across worldwide covering less than 150K users and devices. To support this which SCCM topology you would consider and how would you design the Sites, Site Systems etc.
  7. How you would be troubleshooting computers not booting from PXE for OS deployment to deploy the operating system in production environment. Define the high-level steps here.
  8. Process and workflow for enabling Software Update Point and doing configuration for clients to pick up the software updates from internal software updates point instead from internet.
  9. How to improve SCCM Client health in large scale environment where for some or other reasons numbers of clients becomes unhealthy.
  10. How to build and design custom SQL Query to provide with management required reports.
  11. Design and planning to install Secondary Site in the environment SCCM infra which had already setup Central Administration Site and Primary Site. List of the points to be considered and how to implement them.
  12. How to extend existing Standalone Primary Site to the SCCM infra hierarchy which would have Central Administration Site and multiple Primary Site across world for the organization to support around 2 lac users and systems?
  13. Design and plan on how to migrate from SCCM 2007 hierarchy to SCCM 2012 current branch, list out high-level points to achieve the same in production environment.
  14. Define backend process on package distribution on the distribution point and then how can we troubleshoot or the logs to follow to fix any package distribution related issues.
  15. How can we add the latest models to support for WINPE bootup and process, approach in modifying boot image in production environment without any production impact on operating system deployment via task sequence?
  16. How to setup SQL server and database to installed Central Administration Site and Primary Site? Which parameters to be configured before installing SCCM Sites?
  17. List out the pre-requisites to be checked and fixed any issues before going for the installation of SCCM Central Administration Site and Primary Site.
  18. Specify the purpose of different Sites and their purpose in the Configuration Manager and the number of clients per site supports.
  19. How may site systems are there and their purpose and role?
  20. Process and workflow on how to capture WIM file of windows 10?
  21. Whare are the security scopes and roles are available to suffice the different kind of security requirement needed in production environment?
  22. How to extend active directory schema and process of the same and describe how it benefits the SCCM?
  23. Describe on what is the difference between Install, Upgrade and Update in SCCM?
  24. What is the difference between Driver Store and Driver Package? How to Create driver package for system model to be supported during operating system deployment?
  25.  What are the main four services of SCCM most of the organizations are using in their environment?
  26. What are the collections in SCCM and difference between user collection and device collection?
  27. What are the applications in SCCM and how can we create an application which would met specific condition for installation or uninstallation of application?
  28. How to install Software Update Point and configure the same to download the updates from Microsoft to on-premises SCCM infra? Then how to create the deployment Software Update package to install updates on client devices?
  29. How to build different SQL/SCCM queries or custom reports on the status for different deployments targeted in the organization?
  30. What are the different types of boundaries are available? What are the different types of discoveries are available in SCCM?

 

Q. SCCM task sequence local administrator password not working

Whatever password we are setting up in Task Sequence Step for local administrator should work without fail provided SCCM Client install step is enabled.

 

Below are the observations from the experience I have got working with designing and developing task sequence which could be related to above mention SCCM task sequence local administrator password not working question.

 

Reason for this is when you are installing Operating System with help of Task Sequence as per default behaviour at the end of Operating System installation process for security reason the local administrator account gets disable and if you do not have SCCM install step then you will not be able to log in to the windows post Task Sequence deployment process is completed successfully.

 

To install SCCM Client during Task Sequence operating system deployment process, Install SCCM client step first enable the Administrator Account in backend and then install the SCCM Client. So, this way you would be able to log to windows with the local administrator account on the system which is imaged with Task Sequence Operating System deployment process.

 

Q. Computer not showing in SCCM console

It could be that it is not covered in the specified boundary group in the SCCM console which can be discovered by the specified discovery methods.

 

To install SCCM client the computers must be discovered by SCCM, which is once discovered would show in Device collections in the console.

 

Q. How to find advertisement ID in SCCM 2012 console?

 

In SCCM 2012 advertisement ID is nothing but deployment ID and it can be found by below method,

 

Open Microsoft Endpoint Configuration Manager Console è Click Monitoring Node of left pane of the console (Left Bottom Corner) è Select Deployments è Right Click on the bar below Search option as shown below in yellow marked and choose Deployment ID to be available as new column available on the right pane of the Console where we can see the Deployment ID of the all Deployments we have in console.

 

 

After Clicking Deployment ID, it would be available as below,

 

 

Q. How to find collection ID in SCCM 2012?

Open Microsoft Endpoint Configuration Manager Console è Click Asset and Compliance Node of left pane of the console (Left Bottom Corner) è Go to Device Collection on the left pane of the console è Select Device Collection Node or any Folder under it è Right Click on the bar below Search option as shown below in yellow marked and choose Collection ID to be available as new column available on the right pane of the Console where we can see the collection ID of the collections.

 

 

After Clicking Collection ID, it would be available as below,

 

 

Q. How to get IP address in SCCM?

There are many ways to get the IP address of the systems in SCCM. I shall brief here one of the easiest methods in few steps below with the help of Queries in SCCM console,

 

Step1:

 

Open Microsoft Endpoint Configuration Manager Console è Click Monitoring Node of left pane of the console (Left Bottom Corner) è Select Monitoring Node

 

Step2:

 

Create Query, either you can create any specific folder under Queries and right click on it or you can directly right click on Queries and Select New Query

 

 

On the wizard put name for the Query as IP Address (You can put whatever you want) and click Edit Query Statement

 

 

Click on Star option under General tab as marked in yellow,

 

 

Click Select for the attribute to be selected

 

 

Select Attribute Class System Resource and Attribute IP Addresses from the drop-down menu and Click OK

 

 

Click OK twice on General Page

 

And then this would bring back to the very first page of the wizard on which if you want to set limit the collection, you can do that else leave that as it is and click Next

 

Confirm the Settings on Summary Page and Click Next

 

 

You would get below page on completion of creating query and click Close to Exit the wizard

 

 

Finally, we would have the query created with the name given on the right Pane of the console.

 

 

Now to Run the query right Click on the query and Click Run

 

 

Results for the query would appear under the Query Node and the IP address would show in the right pane of the console.

 

 

Q. How to get SCCM 2012 Attribute class list?

When you create any Queries or create any query-based collection while clicking Edit Query Statement you will get all list of Attribute class in drop down menu as shown below,

 

 

Q. How to SCCM check which DP a client is using

Below methods can be used to see which DP client connect to,

 

From Server Side:

 

We can get the IP address of Client and then see what boundary group it belongs to in Configuration Manager Console. And then see which DP it has been assigned to that boundary group.

 

From Client Side:

 

If the Client is recently imaged with operating system by using Task Sequence deployment method, then we can see the entries for the client picking up the content from the Distribution point. Entries like below would be there in the SMSTS.log file,

 

 

Q. Configuration Manager cannot delete the object in Active Directory

When we setup the Configuration Manager infrastructure in the active directory domain environment, to discover computers in Configuration Manager console we use discovery methods available to discover the computers in the environment. One of the discovery methods is Active Directory System Discovery using which we can discover the objects available in Active Directory for organization domain.

 

And in the Configuration Boundary we have option available to set OU (Organization Unit) from which the object would be discover with the help of discovery methods enabled in Configuration Manager environment. Once the computer objects start discovering in the Configuration Manage console then we go and deploy or install the Configuration Manager Client on them and push the configuration manager policies we have set with the help of assigned Management Point. So, this way we start managing the client in the environment in the terms of deploying applications, software updates, getting hardware and software inventory, deploying operating system deployment, etc.

 

Now for some or other reason after some time some of the configuration manager client becomes absolute and we need to delete their entry from the SCCM database. Deleting computers entry from SCCM Database does not delete the entry for the respective configuration manager client device computer object from Active Directory as Active directory database is different from the SCCM configuration manager Database.

 

So, this is the reason Configuration Manager cannot delete the computer object in Active Directory and separate clean up activity has to be run depending up on how the active directory is setup to mark the device (Computer Object) inactive.

 

Q. ConfigMGR is no longer managing Windows GPO set to default values

GPO is Group Policy Object managed by Group Policy Management console which is one of the Active Directory Management tools for managing group polices set for the objects in Active Directory environment. Configuration Manager does not manage those policies, rather there are some setting to be there on client devices for Configuration Manager client to be worked properly which can be set with the help of Windows GPO like, Which Management point configuration Manager client should talk to, Software Update server location, Site Code, etc.

 

Q. Where does Configuration Manager store software updates?

Either we can download the software updates manually or we can set ADR (Automatic deployment rule) to download the software updates in organizations on-premises Configuration Manager infrastructure environment. Software Updates gets downloaded in content library on the Site server. And then when we create the software deployment package and distribute the deployment package to required distribution point then associated updates with the respective deployment package would get copied to content library on the distribution point.

 

Q. Configuration Manager is not coming in C

Server Side: Standard practice for the installing configuration manager site would not be in C drive ( which is system drive ) instead we should always user other partition then system partition where Operating system is installation on site server. So, for this reason Configuration Manager is not coming in C. At the time of Site server installation, we can set different path then system drive path which is always other than C

 

Client Side: By default, configuration manager client gets installed in devices in path of c:\windows\ccm. At the time of installing client it downloads all the contents in C:\windows\CCMsetup folder and then starts the installation in C:\windows\CCM directory so you would not find the Configuration Manager is not coming in C

 

Q. What is SCCM technology?

SCCM is device management solution product from Microsoft which helps to manage Desktops, Laptops, servers on the network or on internet.

 

Q. What is SCCM called now?

SCCM is now called as Microsoft Endpoint Manager Configuration Manager

 

Q. What are the types of collection in SCCM?

There are two types of collections. Static and Dynamic.

  • Static – Need to add hostname/computer name manually.
  • Dynamic – Is based on query.

 

Q. Why is SCCM important?

SCCM plays very important role in most of the organization as it manages large number of devices on the network in terms of deployment operating system, software updates, applications, getting hardware and software inventory, compliance, reporting, etc.

 

Q. What is SCCM primary site?

Primary site is the site in SCCM infrastructure hierarchy where all the configuration manager clients gets assigned and registered.

 

To know more on SCCM Primary Site Click Here

 

Q. What is SCCM distribution point?

Server or system, having distribution point role configured for configuration manager clients to access contents for the targeted deployment.

 

Summary

These top 25 sccm scenario based interview questions would definitely gives some idea on basic information around the question asked which would also helped in answering the question even if interviewer would tweak the questions.

Understanding SCCM OSD Step by Step Basic Concept

by

 

Are you the one who would want to understanding SCCM OSD step by step basic concept in just span of 10 to 15 minutes then your search ends here? Mostly this would be your article which would give you all basic concepts on the terminology used in SCCM OSD step by step.

 

Once you read this carefully not only you would be able to clear the interview questions asked on SCCM OSD but you would be able to implement the SCCM OSD solutions in any production environment without any doubt on your own. So why to wait and continue reading further.

 

What is SCCM OSD meaning?

SCCM (System Center Configuration Manager) is very popular product from Microsoft which helps to manage large numbers of users and devices from single management console. SCCM OSD (Operating System Deployment) is one of the management solutions of SCCM family which can be used to deploy operating system on large number of systems in any organization’s network at a time.

 

We can configure this SCCM OSD solution in such a way that along with operating system deployment, system would be ready with all required softwares and settings which user would want on their system to work without putting any extra administrative overhead and efforts.

 

This helps to save lot of time and organizations resources which is then turn in to saving cost for the organization.

 

Get almost all understanding SCCM OSD Step by Step interview questions here

Find here the list of the question which can be asked in interview questions and if you know all the basic information around the questions listed there then any given point of time you would be able to implement the solutions in production environment without any difficulties that is for sure.

 

  • What are the Prerequisites to implement SCCM OSD?
  • What is OS WIM file and how to capture the same?
  • What is Task Sequence and how to add Task Sequence (steps) for actions to be executed which runs during operating system deployment?
  • What is PXE and why it is needed and how to enable the same?
  • What is Boot Image? And Why you need it? How to add required component to be available in WINPE mode?
  • What is Driver Package and how to import drivers in SCCM and create the package for the required devices?
  • How to create Boot Image and OS Package in SCCM?
  • What are the required things should be in placed in SCCM infrastructure to deploy operating system over the network?
  • What is WDS and how to install the same on SCCM site system?
  • Process on how operating system deployment works start to end in SCCM infrastructure?
  • How and what all DHCP options to be configured for PXE server?
  • How to build reference computer and capture image of the same?
  • At client side to troubleshoot which log file to refer?
  • How to deploy SCCM OSD Task Sequence?

 

What are the Prerequisites OSD?

Either you deploy the operating system over the network or manually on a single system you would always need to have below prerequisites met before you go and install it,

 

  • Boot Image
  • OS Image
  • Driver Package
  • Software Package

Let us see more descriptive manner for understanding SCCM OSD prerequisites,

 

  • Need boot image to start the operating system deployment process on the devices and in some cases will have to add the network drivers to boot image.
  • Enable PXE on the Distribution Site system
  • Configured all required DHCP Scope option for PXE server
  • Capture the image of reference computer either by capture task sequence or manual way by using DISM utility.
  • Import capture image to SCCM and then distribute to distribution points.
  • Create required package to be added in deployment task sequence.
  • Distribute boot image, add on packages to distribution points.
  • Add drivers for the identified device to the SCCM, create driver package and distribute to distribution points.
  • Create task sequence with adding step for boot image, OS image, driver’s packages and add on other packages.
  • Deploy task sequence to require collection.
  • Monitor the deployment for the status.

 

Different Scenarios and Methods for understanding SCCM OSD Step by Step

Multiple scenarios for operating system deployment:

 

  • Upgrade existing operating system to latest available version.
  • Refresh existing operating system to latest available version.
  • Install latest version on new system. (Bare Metal)
  • Replace existing computer with new computer and transfer data, applications, and settings.

Different methods to deploy operating system:

 

  • Deploy operating system using PXE role of SCCM
  • Standalone bootable Media (Offline ISO)
  • Bootable media (Which connect to SCCM over the network)
  • Software Center (Over the network)

SCCM understanding OSD Step by Step or Deep Dive

To understand SCCM OSD step by step let us assume SCCM infrastructure is already installed and implemented in the organization and you have been appointed to work on the project of enabling the SCCM OSD solution service so that the computers on the network can be imaged. So, considering this will see here the high-level step by step in sequential order to see how to go ahead with this.

Let us break this down with 2 main stages,

 

Stage 1 – SCCM OSD Step by Step Planning and Designing Workflow

In this very first stage of SCCM OSD step by step you would be working on gathering information to plan and design the workflow according to the points mentioned below

 

Choose the SCCM Site and Site system for pilot deployment

According to production environment you would first go gather information on doing the selection of site or location where you would first implement this solution as pilot. For this on selected site systems under any site you would follow below process.

 

Gather information on what all Windows Roles and Features to be enabled

Get to know on how to enable the required windows deployment service on the site system server for PXE to be enabled, most of the cases it would be the site system having role installed of Distribution Point. Because on the properties of distribution point only you would have option to enable PXE.

 

Gather information on how to enable PXE option

How to enable the PXE features on the Distribution Properties and choose option for known and unknown computers.

 

Gather information on DHCP options to be enabled

Next on DHCP server what are the components to be enabled like Boot Server Host Name to put the entry of PXE server with FQDN which would be the computer name of the server where PXE is enabled

 

Gather information on how to create boot image and enable required component into it

In most of the time you would need x64 Boot Image to be booted from Client device. For which you would create the Boot Image Package. Make sure to make boot image compatible for supported model required device drivers, set wallpaper for WINPE environment background, enable command prompt support for troubleshooting, add component to support for running HTA, PowerShell and Vbscript file.

 

Gather information on how to create reference computer and capture image of the same

Reference computer’s Image to be captured with help of DISM command. DISM command would be available in WAIK, it would be already installed on site server, from its installation path you can obtain DISM command. Make sure to installed needed operating system in reference computer along with latest update and required standard application to be part of WIM file. And at the end before capturing the Image make sure to clean up the unwanted stuff like, windows temp files, IE temp files, Run History, remove unwanted users from device management, etc.

 

Gather information on how to create Operating system Package

Gather information on how to  import capture WIM file in to SCCM Console and then create the Operating system Install Package and distribute to required DP.

 

Gather information on how to create Driver Package

Gather information on how to import the required models’ devices drivers in the SCCM console and create the driver package for each model for which you want drivers to get installed during operating system deployment process. Distribute all drivers’ packages to the required distribution point.

 

Gather information on how to create Application Package

Gather information on to create required applications packages which you can not make part of WIM file, but you would want them to install during operating system deployment process. Add these application packages to the required distribution points

 

Gather information on how to create Task Sequence and add required step under it

Gather information on how to create custom Task Sequence and add created packages in sequential order, like Add Operating system Package, add step for Windows configuration like pc name, admin password etc, then add required Install Driver Packages, Add network configuration step for putting system to Domain or keeping it in Workgroup according to the requirement, then add step for installing Configuration Manager client installation, after this add all required application packages to be installed along with operating system deployment process.

 

Gather information on how to Deploy SCCM OSD Task Sequence to required collection

Once done with creation of Task Sequence, this is the time to deploy the task sequence to Know and Unknown collections. Make sure to select the Available option during Task Sequence deployment wizard.

 

Stage 2 – Understanding SCCM OSD step by step Starting implementation

Once we are done with gathering all the information and designing workflow according to the SCCM OSD Stage 2, will now look at implementing the SCCM OSD process in this Stage 2. Setting up the configuration from SCCM Server Infrastructure Side according to the designed workflow in Stage 1.

 

Enabling PXE and Setting up DHCP Scope Option

Up on selection of the site server or site system, you would first install the Windows Deployment Server Service from Windows Role and Feature options.

 

Once done with that if you do not have already distribution point site system role added, you would add that and then you would enable the PXE option on the Distribution Point server properties.

 

During enabling PXE option make sure to enable to support for known and unknown systems for PXE to respond. If you want, you can set password also for security purpose.

 

Then after this you would be getting Boot Server Host Name options configured on DHCP Scope server option, so that along with IP address clients would also receive information on PXE server name or IP address. So, if some one press F12 to boot from Network for operating system deployment, client would be directed to PXE server to download boot image.

 

Working with Boot Image

By default, two boot images would be available in SCCM console x86 and x64. You can use default boot image, but you would prefer to go for custom one as default might not suit to your requirement. If you have latest WAIK (Windows Automated Installation Kit) already installed, then in its installation path latest boot image would be available which you can take as reference and build custom boot image which suffice your requirement.

 

Please make sure to add compatible WINPE LAN card driver for all models which you like to be supported to boot from WINPE, Add Organization standard wallpaper, Enable command support for troubleshooting during WINPE Environment, Enable respective component to support for running VBScript, PowerShell and HTA during WINPE Environment.

 

What is Reference Computer?

Reference computer is nothing but the computer having required operating system installed with latest patches, it would have required standard application already installed with the some of the organization setting already done which we would like to get capture in WIM file. So that using same WIM file we can create the Operating system package to deploy on the computers. So, whatever we capture in WIM file from reference computer would be available on the deployed computers.

 

After adding all the things in reference computer which we would like to be part of WIM file then use DISM command to capture the WIM file of the reference computer. We can have this WIM file saved on network drive.

 

Prepare Reference Computer and Capture WIM

Once you are done with Boot image you would need to have the Image Package for deployment of operating system on computers. For this we need to have the captured WIM file of reference computer.

 

Create Operating system install Package

Once we have the captured WIM ready with us then we can create the network share to store the WIM file which can be used as source location for the Operating system install Package. In SCCM console create the operating system install Package and then distribute this Image package to required Distribution point.

 

Import drivers for required models in SCCM driver store and create driver package

Next you would want all compatible device drivers to be installed during operating system deployment process then we would like to have the driver package to be created for all hardware models for which we want to support. According to the hardware model and vendor download drivers from the vendor site and import them in to SCCM console. Then create the separate driver packages for each model and distribute them to the require Distribution point.

 

Create Software or Application packages to be added in Task Sequence

Now to add as add on packages or applications in Task Sequence step create needed application packages and software’s packages which you can not made part of WIM and you want them to be installed during operating system deployment process. Distribute them to the required distribution point.

 

Create SCCM OSD Task Sequence and add require steps in it

Once you are ready with packages for Boot image, OS image, Driver Packages and Software/Application you will have to either create MDT task sequence or Custom Task Sequence and then add packages created in sequential order as Boot Image, OS Image, Driver Package and then Application Package.

 

Note: Make sure to add Configuration Manager Client Package rite after stage of network configuration to install configuration Manager client during Operating system deployment process.

 

Deploy SCCM OSD Task Sequence

Once you design and create task sequence and after added required packages in it, now is the time to deploy the Task Sequence to Unknown and Known collection ad available. Please do not make it as Mandatory as there could be risk of staring OS deployment by user accidentally press F12 or start the Task Sequence from Software Manager which might wipe the data because of having the step of Partitioning Hard Disk in Task Sequence.

Although there is option to make the Operating system Task Sequence Deployment available to only PXE.

 

Check SCCM OSD Task Sequence Deployment at Client device

Now you are almost done everything which is needed to be done to deploy operating system on client device with help of Task Sequence, it is now time to test at client device.

 

To test SCCM OSD Task Sequence deployment process, follow below step,

 

  • Switch on the computer
  • Press F12 to load boot image over the network
  • Verify if you get the deployed Tasks Sequence is listed in Task Sequence Wizard
  • If yes, then enter on it and see if deployment start

 

Final Words on the topic

At any given point of time if you came across to work on the SCCM OSD solutions then basic concept and terms mentioned here in this article should help you as it covers all the aspect of the understanding SCCM OSD step by step starting from general questions asked on understanding SCCM OSD up to how to plan, design workflow and according to workflow how to implement the SCCM OSD solution in production environment.

 

Related Article :

 

Interested to know on how to update Windows 10 to latest version in just 5 Minutes Click Here

To Know more on infrastructure requirement for SCCM OSD Click Here

SCCM 20H2 Enablement Package to update Windows 10 2004

by
Update Windows 10 2004 to 20H2 Windows 10

 

SCCM Windows 10 20H2 enablement package can be used to update Windows 10 2004 to reduce downtime as Enablement Package only takes less than 5 minutes to complete the update process.

 

If you update Windows 10 by traditional way then it would take around 20 minutes excluding the time it requires to download 4GB of feature update media package to system and then install the update.

 

Interesting facts about SCCM 20H2 Enablement Package for Windows 10 2004

What is Enablement Package?

It is small package having size less than 100 MB which has command or switch to enable Windows 10 features which are already there in dormant or inactive state.

 

To understand how SCCM 20H2 Enablement Package works, we are going to take example of updating Windows 10 2004 to Windows 10 20H2 here. What Microsoft did is that they have added the features of Windows 10 20H2 in Windows 10 2004 quality update but kept them in dormant or inactive state.

 

This enablement package helps to reduce the downtime up to 70 to 80% when we compare it to traditional windows feature update method.

 

How long does Windows 10 version 20H2 take?

In case with using enablement package for windows 10 2004 it takes less than 5 minutes. And in traditional method it should take around 20 minutes.

 

Should I download Windows 20H2?

No, If you are using SCCM enablement package which is less than 100 MB (Standalone Installer or Software Update Deployment Package) then you do not required to download complete 20H2 feature update which is around 4GB.

 

Incase if you want to update from Windows 10 1909 to Windows 10 20H2 then you require to download complete win10 20H2 feature update installable source.

 

SCCM 20H2 Enablement Package Download?

This enablement package is not available to download directly as it is only available via Windows Update and Microsoft Update or Windows Server Update Services (WSUS)

 

Enablement Package size is less than 100 MB only.

 

How to use SCCM 20H2 Enablement Package to update Windows 10 2004

Before going to use any of the below mentioned methods to apply SCCM Windows 10 20H2 Enablement Package Click Here for the prerequisites and detailed information.

 

Using Software Update Deployment Package in SCCM

In this method you would be following the same process which we generally follow for the installation of other regular monthly Microsoft updates within SCCM. Will describe the steps in-short here,

 

  • Log in to Microsoft Endpoint Manager administration console and go to Windows 10 Servicing
  • Find for this particular update named Feature Update to Windows 10 Version 20H2 x64-based systems 2020-12 via Enablement Package
  • Create the deployment package of this particular update and distribute to required distribution point
  • Create the collection of the systems which are eligible to get this 20H2 feature updates with enablement package
  • Create the deployment to target this package on the required collection

SCCM 20H2 Enablement Package Standalone Installer (Manual Installation)

Here will see how can we update system having windows 10 2004 to windows 10 20H2 manually,

 

  • Log in to Microsoft Endpoint Manager administration console and go to Windows 10 Servicing
  • Find for this particular update named Feature Update to Windows 10 Version 20H2 x64-based systems 2020-12 via Enablement Package
  • Create the deployment package of this particular update enablement package in SCCM console, Software Update node
  • Go to properties of this deployment package and click tab content location to get the actual source file. When you go to the content location you would find the Windows10.0-KB4562830-x64.cab file which can be packaged in to MSI or MSU.
  • This MSI or MSU file will be used to install the windows 10 20H2 manually on Windows 10 2004 system. (This would treat as the standalone installer)
  • Simply you have to copy this MSI or MSU on local system or it can be called from network shared location as well
  • Execute the MSI or MSU file to start the installation on Windows update standalone installer wizard
  • Click Next to continue
  • Click Restart to complete the installation
  • Post restart you would have WIndows 10 20H2 showing in Winver Command.

SCCM Windows 10 20H2 Upgrade Task Sequence

WIll see steps to be followed for the adding of Windows 10 20H2 enablement package to the existing Windows 10 2004 task sequence deployment. This would become your Windows 10 20H2 Upgrade Task Sequence to upgrade Windows 10 2004 to 20H2.

 

Step1 : Obtain original source file from Enablement Package

 

  • Go to Software Update or Windows 10 Servicing node in Microsoft Endpoint Endpoint Manager console and choose Feature Update to Windows 10 Version 20H2 x64-based systems 2020-12 via Enablement Package to download.
  • Once you have downloaded this particular update then go to Properties of this Deployment Package and click Content Location Tab. you will have the cab file named with Windows10.0-KB4562830-x64.cab there in the source folder.

Step2 : Create standard Package in SCCM Console

 

  • Create Folder and copy the Windows10.0-KB4562830-x64.cab file in to it.
  • Now in Microsoft Endpoint Endpoint Manager console create the legacy Package for this cab file (Windows10.0-KB4562830-x64.cab)
  • No need to create the program here. And distribute the Package to require Distribution Points.

Step3 : Add this Package to existing Task Sequence of Windows 10 2004 using Dism command

 

  • Now open your Windows 10 2004 deployment Task Sequence and add one Run Command Line Step right below Apply Operating System Image step. Give simple Name to the step which you can easily identify the purpose of this step later on.
  • Now in command line box add command “DISM.exe /image:%OSDisk%\ /ScratchDir:%OSDisk%\windows\TEMP /Add-Package /PackagePath:Windows10.0-KB4562830-x64.cab”
  • And then enable the check mark on Package Option and browse to the Package you have just created with cab file Windows10.0-KB4562830-x64.cab
  • Now Click Apply and OK and here you would have your Windows 10 20H2 Upgrade Task Sequence ready to use

Note :

 

Simply following above mentioned 3 steps would save lot of your time and administrative overhead of coming up with new fresh upgrade Task Sequence for updating Windows 10 2004 to 20H2. Believe this does not take more than 10 minutes to set up 20H2 enablement package in current Windows 10 2004 Deployment Task Sequence.

 

Snapshot for the reference:

 

Summary

To reduce downtime and administrative overhead wherever possible we should always take the advantage of using SCCM enablement package. This Package is available to use via SCCM software update, Windows Update, and also can be used with task sequence to update Windows 2004 to Windows 20H2 during deployment of Windows 2004.

 

Related Articles:

Understanding SCCM OSD Step by Step Click Here

SCCM 2012 distribute content vs update distribution points

by

 

People always gets confused when they look at the options available on the properties of the any package type available in the SCCM 2012 for the distribution. Whenever they try to distribute content, up on right click they see below two options available which we will try our best to clear any doubt on the same.

 

After right click on Package we get,

 

  • Distribute content
  • Update Distribution points

 

 

Let us first see on Distribute Content:

 

Distribute content as name suggest is for distributing contents of the package to the distribution points which are not already available for SCCM client to use for deployment. Which means whenever you create any package and trying to put content of that package to the distribution point very first time, we should always use Distribute Content.

 

In this we must select the Distributions Point where package to be added.

 

When we select Distribute content, we get list of the distribution point to select as shown in below screen,

 

 

Now let us see Update Distribute Point:

 

Update Distribute point should be used to update the contents which are already available on Distribution points. Lets us say there is one package which source files have to be modified for some reason then as package is already available on the DP’s and we want updated source package contents to be updated on distribution points then use the Update Distribution Point option. Up on selecting update distribution point all the Distribution point would be updated wherever package is already distributed.

 

In this rather selecting distribute content, we must select update distribution point up on right click on package.

 

When we select Update Distribution point we get below screen, Click OK to continue to update all Distribution Points in which package is already added.

 

 

Here important to note that once you click OK on above dialog box, process of updating package would start on all Distribution points on which Package is already added. 

So in simple language if we have to understand this, then whenever we create any package use distribute content for first time to add package to Distribution Point and later on for some reason when we modify the content of the source of the same package then we have to use update distribute point.

 

Please share feedback in the comment box.

SCCM SQL Query – Part1

by

 

Here we are giving some SQL queries which can help to get common management required reports for ongoing jobs to be done, also it helps to get quick information on the report which is been looking for. These queries should work straight away by copying and pasting in SQL management studio and give output as mentioned for each query. There could be chances it may not work because changes in either SQL table or SQL Views. These queries also can be used as reference queries to build other queries for desired data reports.

 

SCCM SQL query Add Remove Programs? Or SCCM query Add Remove Programs display name and version? Or SCCM query for Add Remove Programs? Or SCCM query all software installed on all computers?

 

This query is going to give detailed information on software installed on client computers from Add Remove Program List. It would show Computer Name, Software Name, Username, Software Publisher, Software Name, Software Version.

 

 select sys.Netbios_Name0 , sys.User_Name0, arp.publisher0, arp.displayname0, arp.version0
 from v_R_System_Valid sys
 join v_gs_Add_Remove_programs arp on arp.ResourceID=sys.ResourceID

 

SCCM SQL query for specific software installed?

 

This query is going to give detailed information on specific software’s installed on client computers from Add Remove Program List. It would show Computer Name, Software Name, Username, Software Publisher, Software Name, Software Version.

 

 select sys.Netbios_Name0 , sys.User_Name0, arp.publisher0, arp.displayname0, arp.version0
 from v_R_System_Valid sys
 join v_gs_Add_Remove_programs arp on arp.ResourceID=sys.ResourceID
 where (ARP.DisplayName0 like '%(App Name A)%' and ARP.DisplayName0 like '% App Name B%')

 

SCCM SQL query software not installed?

 

This query is going to give detailed information on specific software not installed on client computers from Add Remove Program List. It would show Computer Name, Username, Software Publisher, Software Name, Software Version.

 

 select sys.Netbios_Name0 , sys.User_Name0, arp.publisher0, arp.displayname0, arp.version0
 from v_R_System_Valid sys
 join v_gs_Add_Remove_programs arp on arp.ResourceID=sys.ResourceID
 where (ARP.DisplayName0 Not like '%(App Name A)%' and ARP.DisplayName0 Not like '% App Name B%')

 

SQL query to get serial number SCCM?

 

This query is going to get the serial number of computers with column Computer Name, Username, Serial Number.

 

 select sys.Netbios_Name0 , sys.User_Name0, bios.SerialNumber0
 from v_R_System_Valid sys
 join v_GS_PC_BIOS bios on bios.ResourceID=sys.ResourceID

 

SCCM SQL query to find OS version?

 

This query is going to get the OS version of computers with column Computer Name, OS Name, OS Version, OS Install Date.

 

 select sys.Netbios_Name0, os.Caption0 as OS_Name, os.Version0 as OS_Version ,os.InstallDate0
 from v_GS_OPERATING_SYSTEM os
 join v_R_System sys on sys.ResourceID=os.ResourceID
 join v_R_System_Valid sysv on sysv.ResourceID=sys.ResourceID

 

SCCM SQL query to find Chassis Type?

 

This query is going to get the Chassis Type of computers with column Computer Name, Chassis Type.

 

 select distinct sys.Netbios_Name0, CASE en.ChassisTypes0 WHEN 8  THEN'Laptop' WHEN 9  THEN'Laptop'  
 WHEN 10 THEN'Laptop' WhEN 11 THEN'Laptop' WHEN 12 THEN 'Laptop' WHEN 14 THEN 'Laptop' WHEN 
 18 THEN 'Laptop' WHEN 21 THEN 'Laptop' WHEN 3 THEN 'Desktop' WHEN 4 THEN 'Desktop' WHEN 5 
 THEN 'Desktop' WHEN 6 THEN 'Desktop' WHEN 7 THEN 'Desktop' WHEN 15 THEN 'Desktop' end as  
 'Types' 
 from v_R_System_Valid as sys
 join v_GS_SYSTEM_ENCLOSURE as en on en.ResourceID=sys.ResourceID

 

SCCM SQL query collection members?

 

This query is going to get all members from specified collection ID with column Collection Name, Resource ID.

 

 select fscol.name, fscol.resourceid
 from v_cm_res_coll_(Collection ID) fscol

 

Note: Replace “(Collection ID)” with collection ID

 

SCCM SQL query installed patches?

 

This query is going to get MS Update status with column Computer Name, Deployment Name, Collection ID, Assignment Name, Collection Name, Reboot Status, Username.

 

 select distinct sys.netbios_name0, cl.name, cm.collectionid, cs.AssignmentName, cs.CollectionName,  
 cst.LastEnforcementIsRebootSupressed, cst.UserID
 From v_r_system_valid sys
 join v_fullcollectionmembership cm on cm.resourceid=sys.resourceid
 join v_collection cl on cl.collectionid=cm.collectionid
 join v_CIAssignment cs on cs.CollectionID=cm.CollectionID
 join v_CIAssignmentStatus cst on cst.ResourceID=sys.ResourceID
 where cs.AssignmentName like '%Microsoft_Updates_%'

 

SCCM SQL query for installed updates? And SCCM SQL query to find KB installed?

 

Here is another query to get the software installed details with column Computer Name, Bulletin ID, Article ID, Title Name, Patch Month, Status, Assignment Name.

 

 SELECT distinct SYS.Netbios_name0 , UI.BulletinID, UI.ArticleID, UI.Title,datename(year, UI.datecreated)+'-'+ datename (MONTH, UI.datecreated) as 'PatchMonth'  ,CASE when UCS.Status=2 then 'Required' WHEN UCS.Status=3 then 'Installed' when UCS.Status=0 then 'Unknown'  end as 'Status' ,UDS.AssignmentName
 FROM v_R_System_valid AS SYS
 LEFT OUTER JOIN v_Update_ComplianceStatusAll UCS ON SYS.ResourceID = UCS.ResourceID 
 Left outer JOIN v_UpdateInfo UI ON UCS.CI_ID = UI.CI_ID
 left outer join v_FullCollectionMembership CM on cm.ResourceID=sys.ResourceID 
 left outer join v_UpdateDeploymentSummary UDS on uds.CI_ID=ui.CI_ID
 left outer join v_Collection cl on cl.CollectionID=cm.CollectionID

 

SCCM SQL query to find active clients

 

This query help to get information of client is active or Obsolete with column name Name, Obsolete, Active, Domain

 

 select name , IsObsolete, IsActive, Domain 
 from v_CM_RES_COLL_(Collection ID)

Note: Replace “(Collection ID)” with collection ID

 

 

SCCM query all systems with specific software product name?

 

This query is going to give detailed information on particular software’s installed on client computers from Add Remove Program List. It would show Computer Name, Software Name, Username, Software Publisher, Software Name, Software Version.

 

 select sys.Netbios_Name0 , sys.User_Name0, arp.publisher0, arp.displayname0, arp.version0
 from v_R_System_Valid sys
 join v_gs_Add_Remove_programs arp on arp.ResourceID=sys.ResourceID
 where arp.displayname0 like ‘%Inte%’

 

Note: Replace “Inte” with wild characters of the product name looking for.

 

Find here the link for the SQL table and views.

 

Please share your inputs or if any help required in comment box.

SCCM Server Setup Wizard – List installation requirements

by

To save time, confusion and to have clarity, please consider below inputs and be ready with the information in handy for installing Configuration Manager Central Administration Site or Primary Site.

 

  1. Decide on Site to be selected, Central Administration Site or Primary Site
  2. Be ready with the license product key to be entered
  3. Be ready with setup downloaded file with Setup Downloader. With this you do not require to download at the time of Site installation, you can select previously downloaded files by giving path of those files.
  4. Server Language selection would be by default as English which cannot be changed.
  5. Client Language selection would be by default as English which cannot be changed.
  6. Be ready with the Site Code to be used. Each Site code must be unique.
  7. Be ready with the friendly and easily identifiable Site Name accordingly to the Site you would want to be known.
  8. Decide on folder path for the installation as it cannot be changed later.
  9. Be ready with SQL server FQDN (Fully Qualified Domain Name), Instance Name, Database Name, and SSB (by default it uses 4022) port.
  10. Be ready with the path for SQL server data file and the SQL server log files.
  11. In case if you decide to install SMS Provider to be remote server then be ready with FQDN of the same else by default it takes site server’s name. Additional SMS provider server can be configured later.
  12. Be ready with input to give for client communication to site server on HTTP or HTTPS, in case to go for HTTPS for secure communication client’s computer must have valid PKI certificate.
  13. Decide on which server to be act as Management Point and Distribution Point Site System, and then be ready with FQDN for the servers.
  14. Service Connection Point to be selected in case of installing CAS or stand-alone Primary Site, at the time of installing child Primary Site this can be skipped.

 

Note: This information is not for installing Secondary Site as it does not support installation using Setup Wizard or by command lines. Installation of Secondary Site happens with in Configuration Manager Console.

 

Please share feedback in comment box.

 

SCCM Prerequisites Checker to install Configuration Manager Site and Site systems

by

 

There is small utility available in the installation media named prereqchk.exe which help us to find out the readiness details on the site server or remote site server. Make sure to use this utility from the same version of configuration manager which would be used to install site. It identifies and fix the issues which may cause site installation to fail.

 

It is not mandatory to run this utility before site installation, as at the time of installation it runs by default, but it is best practice to run this before site installation to fix any issues avoid any roadblock.

 

Up on starting this utility it first checks for any site is already exist and if yes, then it checks for upgrade reediness. And if it does not find any site then it performs all required checks.

 

It records all the information in the log file name ConfigMgrPrereq.log under root drive.

 

There are some commands line option which can be used to perform the readiness according to the site or site systems role we are going to install.

 

Here we see some command line options with their purpose in brief:

 

/CAS

 

This verifies the local computer meets all requirement for installing Central Administration Site server.

 

/MP

 

This verifies the local computer meets all requirement installing site systems role of Management point.

 

/DP (FQDN of Computer)

 

This verifies the local computer meets all requirement installing site systems role of Distribution point.

 

/SQL (FQDN of Computer)

 

This verifies the local computer meets all requirement to install SQL to host site database.

 

/PRI

 

This verifies the local computer meets all requirement for installing Primary Site server.

 

/INSTALLSQLEXPRESS

 

This verifies the local computer meets all requirement for installing SQL Server Express.

 

Note: This application or utility can be found in Configuration Manager Installation Media\SMSSETUP\BIN\X64 or Configuration Manager Installation Path\BIN\X64  

 

Please share feedback on this topic in comment section.

List SCCM installation requirements

by

 

Find here the top information in list manner to have an idea on before going doing the installation of SCCM site in production environment

  1. Before starting to install site please make sure you have decided on the topology.
  2. Choosing installation method would be depend on the type of site you may want to opt.
  3. The first site you install always going to be either Stand alone Primary Site or Central Administration Site.
  4. Whenever installing first site always use baseline version.
  5. After installing baseline version, it can be updated to latest one from in-console update.
  6. As installation method we can either use Configuration Manager Setup Wizard or scripted command line tool.
  7. After installation of first site, one or more site can be added any time.
  8. To install secondary site use configuration manager console as installation method of CAS or Primary are not supported to install secondary site
  9. Make sure the basic task like updating computer with latest patches, install and configure SQL server for database, hardening of server OS, preparing network environment are completed before to go for site installation.
  10. Make sure to decide on site names and codes.
  11. Be aware of limits and restriction post installation of sites like, you can not change site code, site description and installation directory. Also, you can not move primary site from hierarchy.
  12. Setup Downloader can be used to pre-download the content before installation of site.
  13. Run prerequisites checker to identify and fix the issues before start of site installations.
  14. Optional port can be identified to use to secure communication between configuration manager sites and clients.

Please share feedback in comment section

SCCM Migration Workflow Chart

by

 

Find here quick basic information on configuration manager migration process.

 

Basic Migration Workflow Chart

 

Quick Points on Migration

  • An existing Configuration Manager 2007 SP2 infrastructure hierarchy can be migrated to Current Branch of Configuration Manager.
  • All or some of the supported data can be migrated from old source site.
  • Data can be migrated from single source site to several different sites in new destination hierarchy of current branch.
  • Data can be moved from multiple sources sites to single destination site in new hierarchy  

What exactly happens in configuration manager migration?

In Configuration Manager migration data would be transferred from database of old hierarchy to database of new current branch hierarchy.

 

Migration does not do any changes in database of source hierarchy; it discovers data to be copied and provisions copy of the same in database of new hierarchy.

 

Terms used in Migration:

Source Hierarchy

This is the hierarchy which is running with supported version of Configuration Manager and which has data to be transferred to new database in destination hierarchy. In migration once we specify source hierarchy, the top-level site in destination hierarchy data gathering process to identify the data to be transferred from the database of designated source site.

 

Destination Hierarchy

This is the site where migration process runs to transfer the data from old hierarchy.

 

Data Gathering

This is the process of identifying data in the source hierarchy to be transferred to new destination hierarchy. This process can be schedule and it can detect the changes in the data which was migrated earlier and might be needed to update in new hierarchy.

 

Migration Jobs

This is the process of specifying the object to be migrated and then manage them in new destination hierarchy.

 

Client Migration

In this data would be transferred which configuration manager client uses in database of old hierarchy to database of new current branch destination hierarchy.

 

Shared Distribution Point

These are the distribution point from old hierarchy which would be use in new destination hierarchy during migration period.

 

Monitoring migration

The progress and success of the migration can be monitored from the Migration node in the management console.

 

Stop gathering data

When there is no data to be transferred from old hierarchy then option can be configured on destination hierarchy to stop the data gathering process.

 

Clean up migration data

To complete migration activity clean up migration data process should be run to remove information of old hierarchy from new destination hierarchy.

 

Please share feedback in comment box.

Windows Server Roles and Features for SCCM Site Server and Site System

by

 

Before to start installation of any site server or site system’s role of Configuration Manager it is better to have below Windows server features and roles installed and enabled as it requires system restart.

Here are the information on basic feature and roles listed out in tabular format to understand better.

 

Require Windows Server features to be installed and enabled:

 

FeaturesSite Systems
.Net Framework
ASP.Net
HTTP Activation
Non-HTTP Activation
Windows Communication Foundation
Background Intelligent Transfer Services (BITS)Management Point
BranchCacheDistribution Point
Data DeduplicationDistribution Point
Remote Differnerials Compressions (RDC)Site Server or Distribution Point

 

Require Windows Server roles to be installed and enabled:

 

RolesSite Systems
Windows Deployment Services (WDS)PXE Point (For OS deployment)
Windows Server Update Services (WSUS)Software Update Point (For Software Update deployment)
Web Server IIS
Common HTTP Features
Application Development
Management Tools
Security		Distribution Point
Management Point
State Migration Point
Fallback Status Point
Software Update point

Please share feedback in comment section