I have migrated my blog to a WordPress site, please check the new site at https://paddymaddy.com
I have migrated my blog to a WordPress site, please check the new site at https://paddymaddy.com
Sccm 2012 sp1 writefilters for think clients
Worth reading this http://blogs.technet.com/b/configmgrteam/archive/2012/11/26/managing-embedded-devices-with-write-filters-in-configuration-manager-service-pack-1.aspx
System Center 2012 Configuration Manager Support Center
System Center 2012 Configuration Manager Support Center has been released on the Client Management Connect site to the ConfigMgr Open Beta community. You can download Configuration Manager Support Center here:http://connect.microsoft.com/ConfigurationManagervnext/Downloads/DownloadDetails.aspx?DownloadID=52192.
Configuration Manager Support Center helps you to gather information about System Center 2012 Configuration Manager clients so that you can more easily address issues with those clients when working with product support specialists. Configuration Manager Support Center includes a tool that gathers a bundle of log files, and also a tool that is used by product support specialists to examine log files and other client data for in-depth analysis of issues with Configuration Manager clients.
Configuration Manager Support Center helps you to gather information about System Center 2012 Configuration Manager clients so that you can more easily address issues with those clients when working with product support specialists. Configuration Manager Support Center includes a tool that gathers a bundle of log files, and also a tool that is used by product support specialists to examine log files and other client data for in-depth analysis of issues with Configuration Manager clients.
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
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
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
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