PowerShell script to check WDS Service status against of List of servers.

Below is a PowerShell script, this will list WDS Service status against of List of servers.

Below is a powershell script will list WDS Service status againest of List of servers.

$InPutComputersList = get-content "c:\MyScripts\list.txt"
$OutPutFile = "c:\MyScripts\WDS_ServiceStatus.csv"
$NotReachble = "c:\MyScripts\NonPingSystems.csv"
$listResult = @()
foreach($ForEverComputerIntheTextFilelinebyLine in $InPutComputersList) {
if (test-path \$ForEverComputerIntheTextFilelinebyLine\c$\windows\write.exe)
{
$objService = Get-Service WDSServer -ComputerName $ForEverComputerIntheTextFilelinebyLine | select machinename, status, name, displayname

$objResult = New-Object PSObject -Property @{
ComputerName = $ForEverComputerIntheTextFilelinebyLine
ServiceStatus = $objService.Status
ServiceDisplayName = $objService.DisplayName
ServiceName = $objService.Name

}
$listResult += $objResult
}
Else
{
Write-Output "$ForEverComputerIntheTextFilelinebyLine,NotReachable" | out-file $NotReachble -append
}
}
$listResult| Export-Csv -Path $OutPutFile

SCCM 2012 Replication – What is replicated in each type From where to where

 

There are TWO types of replication can happen

1) Database Replication
2) File-Based Replication

Database Replication Includes Global Data & Site Data

  • Global data that replicates by using database replication.
  • Site data that replicates by using database replication.

    Note:- Apart from above two there is local data this is just to specific to the local site.

    Global data includes below : these are flow from CAS to below the Hierarchy

    Alert rules
    Client discovery
    Collections rules and count
    Configuration Items metadata
    Deployments
    Operating system images (boot images and driver packages)
    Package metadata
    Program metadata
    Site control file
    Site security objects (security roles and security scopes)
    Software updates metadata
    System Resource List (site system servers)

     

    Site Data Replication: These are from Client to reporting/assigned Site

    Alert messages

    Asset Intelligence client access license (CAL) tracking data
    Client Health data
    Client Health history
    Collection membership results
    Component and Site Status Summarizers
    Hardware inventory
    Software distribution status details
    Software inventory and metering
    Software updates site data
    Status messages
    Status summary data

    File-Based Replication: Earlier products there was only one type of Replication and this is file type. Now with SCCM 2012 this was limited two below types, Mainly used for Software packages and software updates.

    File content that replicates by using file-based replication.

    File based Data To the Destination
    Package files used by deployments Sent to primary and secondary sites.
    Data from secondary sites Sent to the primary site (parent) of the secondary site.
    Fallback status point state messages Forwarded to the assigned site when only a single fallback status point is in use.
    Discovery data records Forwarded to the assigned site when not processed at the site where they are generated.

  • SCCM 2012 Client Push – Pre Requirement (HotFix)

     

    The hotfix described in KB2552033 must be installed on site servers that run Windows Server 2008 R2 when client push installation is enabled.

    For package pre-stage in 2012

    On dp take the check box as pre stage

    From package right click create "prestage content file" to create the package
    This will create the .pkgx file.
    Get the file extractcontent.exe from bin/x64

    Run the below command

    extractcontent.exe /p:e:\path of .pkgx files /s

    These two steps will distribute the package as pre-stage method






    Setupwpf.exe /script

    Configmgrautosave.ini

    Script to check the drive space in the server against the threshold value and triggers an alert

    Script to check Disk Space
    #Purpose: Script to check the drive space in the server against the threshold value and triggers an alert
    #powershell script for disk space monitoring
    $computer = get-content -path .\list.txt #get-content env:computername; #Get the server name
    $percentWarning = 50; # Store the percentage warning threshold
    $disks = Get-WmiObject -ComputerName $computer -Class Win32_LogicalDisk -Filter "DriveType = 3";
    $mailbody = "The following drive(s) have less than $percentWarning% free sapce in Server,Please cleanup: $computer`n`n";
    $mailbody+="Drive`t`tTotalspace(GB)`t`t`Freespace(GB)`n ________________________________________________________________________ `n";
    $drivedata="";
    $emailsubject="$computer - Low Disk Space Alert!";
    # Code to send email to the File Server Owners
    function SendEmail([string]$msg)
    {
     $SMTPClient = new-object System.Net.Mail.smtpClient;
     $SMTPClient.host = "smtp.Domain.com"
     $MailMessage = new-object System.Net.Mail.MailMessage;
     $MailMessage.Subject = $emailsubject;
     $MailMessage.Body = $msg;
     $MailMessage.From = "
    SCOMN_No_Reply@Domain.com";
     $MailMessage.To.add("
    ToJhon@Domain.com");
     $SMTPClient.Send($MailMessage);
    }

    #The following block performs the core functionality
    foreach($disk in $disks)
    {
     $deviceID = $disk.DeviceID;
     [float]$size = $disk.Size;
     [float]$freespace = $disk.FreeSpace;  
     $percentFree = [Math]::Round(($freespace / $size) * 100, 2);
     $sizeGB = [Math]::Round($size / 1073741824, 2);
     $freeSpaceGB = [Math]::Round($freespace / 1073741824, 2);  
     if($percentFree -lt $percentWarning)
     {
      $drivedata += "$deviceID`t`t $sizeGB`t`t`t$freeSpaceGB`n";
     }
    }
    #Email to be sent only if any drive has free space less than threshold value
    if($drivedata.length -gt 0)
    {
     $msg=$mailbody+$drivedata;
     SendEmail($msg);
    }

    Source:- http://www.sharepointdiary.com/2012/11/drive-space-monitoring-using-powershell.html

    Migrate reports from SCCM 2007 to SCCM 2012

    sync SSRS report between two report servers:

    The built-in migration wizard in ConfigMgr 2012 can migrate most objects but not reports. In ConfigMgr 2012 classical ASP reports (as we know them from earlier versions) are no longer supported.
    Migrate the classical reports to SQL Reporting Services in SCCM 2007
    Below is a walk thru of how you migrate your existing classical reports to SQL reporting Services in SCCM 2007. Notice that you will still be able to run all classical reports after the migration.

    1. On you SCCM 2007 site server install either SCCM 2007 R2 or SCCM 2007 R3, both will add SQL Reporting Services support for SCCM 2007.
    2. In the ConfigMgr. console, navigate to Site Database, Site Management, A01 (where A01 is the sitecode), Site Systems. Right click the Site system server that will become a Reporting Services Point and click New Roles. Select Reporting Services Point and finish the wizard using the default values.
    3. In the ConfigMgr. console, navigate to Site Database, Computer Management, Reporting, Reporting Services, and expand the node.
    4. Right-click SCCM1 (where SCCM1 is the name of your server), and then click Properties.
    5. On the Data Source Settings tab, specify SCCM1 as the database server and SMS_A01as the database name (where SMS_A01 is the name of your SCCM 2007 database. ClickTest.
    6. On the Data Source Authentication tab, select Windows integrated security.
    7. Click OK.
    Copy reports to SQL Reporting Services

    1. Right-click SCCM1, and select Copy Reports to Reporting Services.
    2. On the Data Source Settings page, accept the default settings, and click Next.
    3. On the Data Source Authentication page, accept the default settings, and click Next.
    4. On the Select Reports page, accept the default settings, and click Next.
    5. On the Security page, accept the default settings, and click Next.
    6. On the Summary page, click Next.
    7. On the Progress page - once all of the reports have copied - click Next and then clickClose.
    Migrate the SCCM 2007 reports to SCCM 2012
    You can’t use the built-in migration tools to migrate reports from SCCM 2007 to SCCM 2012. This leaves you with two choices; 1) Download each RDL file one by one from SCCM 2007 and upload them to SCCM 2012 or 2) Use one of the free community tools that can download multiple folders at the time. In my last project I used this tool – ReportSync - to assist me.

    1. Launch ReportSync
    2. In Source server type in the name of the SCCM 2007 Report server in form of http://CM01/ReportServer. Provide credentials and click Load
    3. In Destination server type in the name of the SCCM 2012 Report server in form of http://CM02/ReportServer. Provide credentials and click Load
      ka021301.jpg
    4. Select the folders or individual reports you want to migrate and click Sync
      ka021302.jpg
    5. Once the process is finished click OK and your reports are now ready in SCCM 2012.
    6. This tool keeps the old Data source which will generate an error the first time you run the report.
      ka021303.jpg
    7. Open the report properties (by clicking on the report link)
    8. Select Data Sources, click Browse and select the shared SCCM 2012 data source. The data source is found in Home\ConfigMgr_Sitecode. The data source is the object with long GUID. Select the data source click OK and Apply.
    9. Run the report and verify that it works. There is no guarantee the all SCCM 2007 reports work out of the box in SCCM 2012.
      ka021305.jpg


    Download link : http://code.google.com/p/reportsync/downloads/list

    All credits goes to Kent.

    SCCM 2012 Replication Data

    From SCCM 2012 site to site replication is moved to SQL replication, Where as in SCCM 2007 it was file based.

    Below chart explains the What kind of Data type will be replicated between sites with Replication Types.

    image

    What is there in Global Data & Site Data ?

    image

    When do we need a CAS (Central Administration) 2012 Site

    • If you have more than one Primary Site in a single hierarchy
    • For Central Reports and administration for your primary sites management.

    Question:- Can i install CAS on existing SCCM 2007 Server?

    No it is recommended to install on new (hardware) box

    When do we need a local Distribution Point? In SCCM 2012?

     

    Below are the three key points to consider a local distribution Point’s

    • BITS not enough to control the WAN traffic
    • Multicast for Operating System Deployment
    • To stream APP-V Applications

    Ok..  Now when we do not need a local Distribution points in SCCM 2012?

    Below are the key considerations…

    • Clients are well managed with-in BITIS provided control for WAN traffic
    • If BranchCache deployed(below points are pre-requirements for BranchCache)
      • DP’s on 2008 R2
      • Vista Sp2 with KB960568 and above OS’s(windows7 & 8)

    Note:- Distribution Point role can be enabled on Client OS or Server OS.
    Note:- Branch Distrubution Point Role is removed in SCCM 2012.

    When do we need a Secondary Site – SCCM 2012

     

    Below are the three key considerations to setup a secondary site.

    • To manage Upward-flowing WAN traffic
    • Tiered content Routing for deep network topologies
    • No local administrators

    When do I need SCCM 2012 Primary Site?

    To Manage Clients/Devices
    Add More Primary sites for

    • To scale more than 100,000 Clients
    • Reduce impact of primary site failures in case of DR(Disaster recovery)
    • Local Point of Connectivity for Administration & Political Reasons
    • Content Regulations

    Ok….. When you do not need a primary site compared with SCCM 20007 ?

    • Decentralized administration
    • Logical data segmentation
    • Client settings
    • Language Settings
    • Content routing for deep hierarchies

    What is Empower Users in SCCM 2012

    image

    Enabling any device from any where

    Changes from SCCM 2012 to SCCM 2012 SP1


    Below are the changes from SCCM 2012 to SCCM 2012 SP1

    image

    What is Windows To Go?

    Windows To Go is a feature in Windows 8 Enterprise that allows Windows 8 Enterprise to boot and run from mass storage devices such as USB flash drives and external hard disk drives.It is a fully manageable corporate Windows 8 environment. Using Group Policy, Windows Store can be enabled for a Windows To Go workspace (limited to one PC) and Store apps can be used on that workspace.

    Is windows 8 supported for sccm ?

    Yes from sccm 2012 sp1. The bad news is windows xp no more supported.

    Read this related to windows 8 support .... Into

    One of the most significant changes is support for Windows 8 for Configuration Manager clients. Configuration Manager SP1 supports Windows 8 in the following ways:

    You can install the Configuration Manager client on Windows 8 computers and deploy Windows 8 to new computers or to upgrade previous client operating versions. Configuration Manager also supports Windows To Go.

    You can configure user data and profiles configuration items for folder redirection, offline files, and roaming profiles.

    You can configure new deployment types for Windows 8 applications, which support stand-alone applications (.appx files) and links to the Windows Store.

    Configuration Manager supports Windows 8 features, such as metered Internet connections and Always On Always Connected.

    What is not changed in sccm 2012 when compared with sccm 2007 ?

    Wake on LAN

    Windows Embedded devices

    The Active Directory schema extensions for System Center 2012 Configuration Manager are unchanged from those used by Configuration Manager 2007. If you extended the schema for Configuration Manager 2007, you do not need to extend the schema again for System Center 2012 Configuration Manager.

    What is Application management in sccm ?

    Provides a set of tools and resources that can help you create, manage, deploy, and monitor applications in the enterprise.

    Why you want sccm ?

    You can perform all below with help of sccm:

    Deploy operating systems, software applications, and software updates.

    Monitor and remediate computers for compliance settings.

    Monitor hardware and software inventory.

    Remotely administer computers.