
This new and complete WorkSHOP ( 9 hours) will give you the Power to manage all the admin aspects of System Center Configuration Manager (SCCM) with Powershell !!
In this WorkSHOP, you will be a Powershell Master by learning how to use the SCCM Powershell MODULE to Manage the site settings of your Primary site, configure the methods for discovering your devices and users, create your device collections.
We will then focus on how to configure the push Method for installing the SCCM Client. We will after manage the client settings and create custom settings. We will then see how to manage client notification so you will never have to go on your device and refresh the policy !!
After, we will go deep dive in the prerequisite to install packages and applications, We will see how to customize the DP for deploying Pkg and Application. We will see how to install a package and after how to install an application. We will then deploy it to the collections or device.
After all that, we will see how to manage and deploy Software updates, We will see in the interaction with WSUS and the ports to use. We will create software updates groups and finally create the package to push on your collections. We will finish with the automatic deployment rules.
We will also manage the compliance futures. How to add Items to check settings and then deploy them by creating BaseLines.
We will then start the big part : OSD. We will see the WDS/PXE interaction, modify your boot files WINPE, import drivers. We will then import your operating system and of course create the Task Sequence to deploy the OS to your devices.
You will also learn the different Roles that you can add, how to manage their settings and modify those Roles.
After that we will see the RBAC and how add new security Roles, Scopes and Admin users.
We will then see the Endpoint protection Role and how to create the policy for Anti Walware detection
Finally we will see the monitoring aspects and how to create Alert
The last module will be automation. We will see with a simple example how to create a script to push Apps or Pkgs.
We will visit the Powershell Gallery to see the scripts created by the community
Its really a fantastic WorkShop and the first on SCCM. you will never have the opportunity to follow more then 8 hours of
deep dive Powershell for SCCM
Enjoy !!!
You can run Configuration Manager cmdlets and scripts by using the Configuration Manager console or by using a Windows PowerShell session. When you run Configuration Manager cmdlets by using the Configuration Manager console, your session runs in the context of the site.
You can load the module directly in the SCCM Console.
You can also Remotly access the module with Enter-Pssession
The Powershell Module is in : CD 'C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin'
Go on this folder and type : Import-Module .\ConfigurationManager.psd1
Configuration Manager Cmdlets : https://docs.microsoft.com/en-us/powershell/module/configurationmanager/?view=sccm-ps
Resource discovery detects and acquires information about network resources. By using resource discovery, you can search a network for resources that you can use and manage with Configuration Manager.
A resource is an object that is discovered by one of the available Configuration Manager discovery methods. During resource discovery, resource information can come from a variety of sources, including:
· Active Directory objects such as users, groups, and computers
· Site systems
· Routers
· Printers
· Other IP-addressable devices on your network
You can use the discovered resources to create custom queries and to organize resources into collections that you can use for management tasks, such as software deployments.
We will use CmdLET like Get-CMDiscoveryMethod, Set-CMDiscoveryMethod and Invoke-CMSystemDiscovery.....
Second Part of the discovey Methods, We will see how to customize system discovery and add special OU.
We will use CmdLet like Set-CMDiscoveryMethod -ActiveDirectorySystemDiscovery, New-CMSchedule ....
Creating and using collections is a fundamental aspect of Configuration Manager. Within Configuration Manager, collections represent resource groups that consist of devices, such as computers and mobile devices, or users and user groups from all of the hierarchy’s sites.
You can use collections to accomplish several management and configuration tasks, including:
Organizing resources into manageable units to create an organized and logical structure of resources.
Organizing collections of target resources to simultaneously perform Configuration Manager operations on multiple resources. Configuration Manager operations can include application deployments and the installation of software updates.
Targeting groups of computers with specific configurations, such as:
Client settings.
Power management settings.
Maintenance window settings.
Organizing computers based on their compliance status, with a specific baseline.
Integrating with role-based administration to specify collections that a specific administrative user can access.
We will use CmdLet like New-CMDeviceCollection, New-CMUserCollection, New-CMDeviceCollection ....
A site boundary is a network location that contains one or more devices you want to manage or resources you want to provide to clients. Often, your network infrastructure is separated into several network locations, each of which contains network clients.
Boundary groups assemble boundaries into logical groups for management. All combined boundaries within a single boundary group are assumed to have a high-speed connection between them. Boundary groups provide Site assignment and locate the DP, SUP, State migration and MP
In this lecture, we will how to manage Boundaries and how to manage Managing Boundary Group.
We will use CmdLet like New-CMBoundary, Get-CMBoundary, Set-CMBoundary, Remove-CMBoundary...
Client push installation. This method pushes the Configuration Manager client software to client computers.
You can automate this deployment method so that client installation occurs on systems assigned to the site, or you can manually initiate a client push installation to any discovered system supported for client installation.
This method uses a client push installation account which is configured in the Configuration Manager console. Client push installation also requires exceptions to the Windows Firewall. If the site server cannot contact the client computer, or the setup process cannot be started, it will repeat the installation attempt every hour for up to 7 days.
We will use Cmdlet like get-CMClientPushInstallation, Install-CMClient ....
The client settings are features that you enable or not on your collections.
You configure the Default Client Settings object with settings that will apply to all clients. The Default Client Settings object always has a priority of 10,000, and you cannot change this setting.
The Default Client Settings object is applied first and custom settings overrides the default settings when you assign them to collections. You can configure custom settings for any of the categories—or a combination of those categories—found in the Default Client Settings object.
We will use CmdLet like Get-CMClientSetting, New-CMClientSetting, Set-CMClientSetting, Remove-CMClientSetting ....
SCCM client makes regular calls to its MP to download policies to tell to the client what feature will be enable or disable.
These calls are made at 60 minute intervals . You can run a invoke command to download updated policy rather than going on the device and run a refresh action
Configuration Manager provides content to clients through distribution points. Before you can use Configuration Manager to deploy software to a client device, you must have at least one distribution point that the client can access. You then can implement additional distribution points as necessary to provide efficient access to content as client devices install deployed software.
Distribution points host content files for Applications, Packages, Software updates and Operating system deployments
Configuration Manager distribution points store files that Configuration Manager clients use. A Configuration Manager client needs access to at least one distribution point. You can deploy distribution points to computers that run server operating systems, such as Windows Server 2016, to computers that run client operating systems, such as Windows 10, and to Microsoft Azure with your Azure subscription.
The content library hosts content files. These files include software updates, operating-system deployment images, and files related to packages and applications. Each site server and distribution point hosts a content library.
We will use CmdLet like New-CMSiteSystemServer, Add-CMDistributionPoint .....
This new and complete WorkSHOP ( 9 hours) will give you the Power to manage all the admin aspects of System Center Configuration Manager (SCCM) with Powershell !!
In this WorkSHOP, you will be a Powershell Master by learning how to use the SCCM Powershell MODULE to Manage the site settings of your Primary site, configure the methods for discovering your devices and users, create your device collections.
We will then focus on how to configure the push Method for installing the SCCM Client. We will after manage the client settings and create custom settings. We will then see how to manage client notification so you will never have to go on your device and refresh the policy !!
After, we will go deep dive in the prerequisite to install packages and applications, We will see how to customize the DP for deploying Pkg and Application. We will see how to install a package and after how to install an application. We will then deploy it to the collections or device.
After all that, we will see how to manage and deploy Software updates, We will see in the interaction with WSUS and the ports to use. We will create software updates groups and finally create the package to push on your collections. We will finish with the automatic deployment rules.
We will also manage the compliance futures. How to add Items to check settings and then deploy them by creating BaseLines.
We will then start the big part : OSD. We will see the WDS/PXE interaction, modify your boot files WINPE, import drivers. We will then import your operating system and of course create the Task Sequence to deploy the OS to your devices.
You will also learn the different Roles that you can add, how to manage their settings and modify those Roles.
After that we will see the RBAC and how add new security Roles, Scopes and Admin users.
We will then see the Endpoint protection Role and how to create the policy for Anti Walware detection
Finally we will see the monitoring aspects and how to create Alert
The last module will be automation. We will see with a simple example how to create a script to push Apps or Pkgs.
We will visit the Powershell Gallery to see the scripts created by the community
Its really a fantastic WorkShop and the first on SCCM. you will never have the opportunity to follow more then 8 hours of
deep dive Powershell for SCCM
Enjoy !!!
Fabrice IT Lover