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.

$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

for a single computer add or remove programs info

Select v_Add_Remove_Programs.DisplayName0, v_Add_Remove_Programs.Publisher0, v_Add_Remove_Programs.Version0

FROM v_Add_Remove_Programs

JOIN  v_R_System ON v_Add_Remove_Programs.ResourceID = v_R_System.ResourceID

WHERE v_R_System.Netbios_Name0 = @computername

Hardware Inventory last scanned

SELECT SYS.Netbios_Name0 as 'Computer Name',
SIS.SMS_Installed_Sites0 as 'SMS Site', WS.LastHWScan,
DATEDIFF(day,WS.LastHWScan,GETDATE()) as 'Days Since HWScan'
FROM v_GS_WORKSTATION_STATUS WS INNER JOIN v_R_System SYS
ON WS.ResourceID = SYS.ResourceID INNER JOIN v_RA_System_SMSInstalledSites SIS
ON WS.ResourceID = SIS.ResourceID
WHERE SYS.Client_Type0 = 1 AND SYS.Active0 = 1 AND
WS.LastHWScan < DATEADD([day],+1,GETDATE())

scvmm pre-requsites

Pre-reqs:

Service account

Service account should have local admin privileges

Service account should have access in VMMKKM Container

Service account and  VMMKKM Container should be on same domain

SQL native Client

Cluster name should have access on SCVMM name

(CNO should be properties of VCO security and full control)

SCVMM service name and should have static IP

Service account should have SQL direct access , kind of  DB owner access

Always on should be off incase SQL DB already pre-staged

(always on is a HA solution for the sql DB)

Use sql port 1433

Use all default ports

Logon service group - secpol.msc - should have access to service account 

Pull Dp concept

When a package is distributed to a PullDP, DistMgr creates a PkgXferMgr job and added to the queue.- PkgXferMgr processes the job and creates a PullDP notification in the PullDPs WMI.- PullDP reads the notification and starts the download from a assigned Standard DP based on priority.- Once the notification is written, PkgXferMgr monitors the job for next 10 hours (max value hardcoded). Every 60 mins.- If the status is not received from the PullDP, it will mark the distribution as Failed and it creates a Status Message and DistMgr processes the message.- if a package is successfully downloaded in the PullDP, even after it exceeds the 10 hours, it will send the status to MP and it will drop a file in Distmgr.box.- DistMgr will check the existing status in the PkgStatus table.- Since the PkgXferMgr already dropped a failed status, it will ignore the status which has been sent by PullDP.- So the status will stay as failed. But content is distributed. However clients won’t work due to status marked as failed in Database.-  It is by design in CM12 R2.- Above hardcoded values can be changed in ConfigMgr 2012 R2 SP1 using AdminUI.

SCCM 2012 Application Concepts

SCCM 2012 Application Concepts 

Application
An application is intelligent software that knows if a user is authorized to use it on a particular device, if that device can run it and how it should be made available to the user on that device.  An application in SCCM 2012 is what a package and program(s) is in SCCM 2007.  You can still use the old package-program in SCCM 2012 to deploy software but you won't take advantage of the intelligence in Applications.

Deployment
A deployment in SCCM 2012 is what an advertisement is in SCCM 2007.  A deployment is used to deploy an application.  You can indicate the purpose of a deployment as Required and Available.  Think of Required as the purpose of a mandatory assignment in an SCCM 2007 advertisement.  Think of Available as the purpose of an optional advertisement in SCCM 2007.  You can configure two actions for a deployment: Install and Uninstall.

Deployment Type
A Deployment Type is part of an Application and provides information needed to install the software.  It contains rules to determine if and how software should be installed on a particular device or delivered to a user.  SCCM 2012 has the following deployment types: Windows Installer, Script Installer, Microsoft Application Virtualization, Windows Mobile Cabinet and Nokia SIS file.

Application Catalog
This is a user-friendly web portal for applications that are not forced on devices by making the purpose of a deployment Available and configuring the deployment to target users.  Users can browse to the portal and install or use applications that are available to them (with the option to require approval for specific applications).

Software Center
This is an SCCM client application that replaces the "Run Advertised Programs" control panel applet present in the SCCM 2007 client.  If a deployment targets a device instead of a user, the user can install the application by launching Software Center.

User-Centric Application Management
This is a framework of SCCM features and other technologies that allow the intelligent delivery of applications to users anywhere on any device and at any time.  One example of this is making Microsoft Word available to a user.  Per the administrator's intent, Word will be installed only on the user's primary device, and it will be streamed to the user via App-V on any other device.

User Device Affinity
This is one of the key features in SCCM 2012 that makes User-Centric Application Management possible.  It allows a device to be configured as the primary device for a user.  You can actually have multiple primary users for a device, and multiple primary devices for a user.  For more information on this see

SCVMM Capacity planning

Config that’s required for VMM to manage 300 hosts.

System Center 2012 R2 servers	Processor (min)	Processor (rec)	RAM (min)	RAM (rec)	Hard drive space (min)	Hard drive space (rec)
VMM Management Server (More than 150 hosts)	Pentium 4, 2 GHz (x64)	16-Core 2.66 GHz CPU	4 GB	16 GB	4 GB	10 GB
VMM Console (More than 150 hosts)	Pentium 4, dual processor 2 GHz	2-Core 2 GHz CPU	4 GB	4 GB	4 GB	10 GB
VMM Library Server	Pentium 4 2.8 GHz	4-Core 2.66 GHz CPU	2 GB	4 GB	Varies based on the number and size of the stored files.	Varies based on the number and size of the stored files.