Skip to main content

Software Update Management- SCCM 2012

The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1.  WSUS Server (WSUS 3.0 SP2 ) should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This  link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled(will be enabled by default) and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. ...

Get-ADUserMembership --- Retrieves friendly group names of a given AD user


Import-Module ActiveDirectory            
            
Function Get-ADUserMembership {            
<#

.SYNOPSIS
    Retrieves friendly group names of a given AD user.
.DESCRIPTION
    It retrieves the group membership of the user AND helps in scenarios where you just need the group names without distinguished name to send the output as input to other functions or scripts.
.PARAMETER name
    Name of the Active Directory user to query
.NOTES
    Name: Get-ADUserMembership
    Author: Santhosh Durgam
    Email : santhosh.durgam@hotmail.com
    DateCreated: 8th August 2019

.EXAMPLE
    Get-ADUserMembership -User "sccmadmin"

Description

-----------

It returns the friendly names of the groups to which the queried user belongs to.
#>              
    [cmdletbinding()]            
    param(            
    [Parameter(Mandatory=$true, position = 0)]            
    [string]$User            
    )            
            
    begin             
        {            
            Write-Verbose "Querying group membership for the user $User"            
        }            
    process            
        {                     
            $ADUserExists = Get-ADUser -Identity $User -ErrorAction SilentlyContinue            
            if($ADUserExists)            
                {            
                    Get-ADUser -Identity $User -property memberof | Select-Object -ExpandProperty memberof | ForEach-Object {($_.split(",")[0]).split("=")[1]}            
                }                            
            else            
                {            
                    Write-host "User $User is not found in AD"            
                }            
        }            
    end            
        {            
                        
        }            
}            


Comments

Popular posts from this blog

Software Update Management- SCCM 2012

The below post explains the end to end process of software updates management in SCCM 2012 Pre-requisites: 1.  WSUS Server (WSUS 3.0 SP2 ) should be installed on the SCCM site server or if you want to install WSUS on another server, it is important that you install WSUS administration console as the SCCM Server uses API. This  link explains the step by step procedure to install WSUS 3.0 SP2 2. Install SUP-Software Update Point on the SCCM Server . 3. Reporting Services Point: Install reporting services point role as described in this link . 4. Client agent: The software update client agent should be enabled(will be enabled by default) and the settings have to specified as per the requirement. On SCCM console, go to Administration>Site Configuration>Client settings>Right click on Default client settings> Click on Properties. If required, we can create custom client settings and then enable client settings for that settings. ...

Operating System Deployment-SCCM 2007 Step By Step Procedure

This post explains the step by step by procedure (flow) to build, capture and deploy Operating System to a bare metal machine. It covers: A] Preparing SCCM Server for OSD B] Building and capturing OS image C] Deploying Operating Systems. There are two methods to capture OS image. a] Using Task sequence to capture  the OS from a reference machine.(Automating BUILD as well) b] Using Manual method.( build an operating system and then capture using SCCM) Here, I am building and capturing the image through Task Sequence. And also not using any USMT to migrate data since it is a plain bare metal deployment, not an upgrade. A]. Preparing SCCM Server for OSD: 1. Install WDS server role WDS 2. Install and configure PXE service point. PXE Service Point 3. General Supported Configurations. 4. Create and set Network access account.  5. Create and distribute the Configuration Manager 2007 package, all the relevant KB updates as packages. This post helps to create...

Consistency validation for SQL Server registry keys failed error -SQL for SCCM

During installation of SQL server, "Consistency validation for SQL Server registry keys failed” error pops up in the below scenarios. 1.   Previous installation of SQL exists. 2.   Inappropriate permissions on the registry keys of Microsoft SQL server. Solution that worked me is explained below. A. Identify the issue: 1. Go to %Program Files%\Microsoft SQL Server\100\SetupBootstrap\Log\”date  and time of installation” 2. Search (in Detail_GlobalRules.txt) for lines containing the following string "Could not fix registry key" 3. Run “regedit”, s et full control permissions for the appropriate registry keys mentioned in "Detail_GlobalRules.txt" file. Re-run the installation. B. Modifying the registry: 1. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server in registry. (To open registry, run “regedit”) 2. Right click and go to Permission 3. Click on Advance tab and c heck the below options.     i. Include i...