Sasidhar Konduru - SCCM Expert

--DP content status: use sms SELECT     v_PackageStatusDistPointsSumm.PackageID,                       v_Package.Name, v_PackageStatusDistPointsSumm.InstallStatus, v_PackageStatusDistPointsSumm.SiteCode, v_PackageStatusDistPointsSumm.ServerNALPath,                       v_PackageStatusDistPointsSumm.SourceVersion, v_PackageStatusDistPointsSumm.State, v_PackageStatusDistPointsSumm.LastCopied,                       v_PackageStatusDistPointsSumm.SourceNALPath, v_PackageStatusDistPointsSumm.SummaryDate FROM         v_PackageStatusDistPointsSumm INNER JOIN                       v_Package ON v_PackageStatusDistPointsSumm.PackageID = v_Package.PackageID WHERE     (v_PackageStatusDistPointsSumm.ServerNALPath LIKE '%XXX%')---and InstallStatus <> 'Package Installation complete' --WHERE     (v_PackageStatusDistPointsSumm.ServerNALPath LIKE '%.stores.target.com%')and InstallStatus <> 'Package Installation complete' --and Name like '%neil%&

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

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

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())

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 

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 d

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 inform

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.

Release/Update Version Build ConfigMgr 2012 RTM 5.00.7711.0000 7711 ConfigMgr 2012 SP1 5.00.7804.1000 7804 ConfigMgr 2012 SP1 CU1 5.00.7804.1202 7804 ConfigMgr 2012 SP1 CU2 5.00.7804.1300 7804 ConfigMgr 2012 SP1 CU3 5.00.7804.1400 7804 ConfigMgr 2012 SP1 CU4 5.00.7804.1500 7804 ConfigMgr 2012 SP1 CU5 5.00.7804.1600 7804 ConfigMgr 2012 SP2 5.00.8239.1000 8239 ConfigMgr 2012 R2 5.00.7958.1000 7958 ConfigMgr 2012 R2 CU1 5.00.7958.1203 7958 ConfigMgr 2012 R2 CU2 5.00.7958.1303 7958 ConfigMgr 2012 R2 CU3 5.00.7958.1401 7958 ConfigMgr 2012 R2 CU4 5.00.7958.1501 7958 ConfigMgr 2012 R2 CU5 5.00.7958.1604 7958 ConfigMgr 2012 R2 SP1 5.00.8239.1000 8239

SELECT DPSI . Name , DPSI . NumberInstalled , DPSI . NumberInProgress , DPSI . NumberErrors , DPSI . NumberUnknown FROM vSMS_DPStatusInfo DPSI WHERE ( DPSI . NumberErrors > 0 OR DPSI . NumberInProgress > 0 OR DPSI . NumberUnknown > 0 ) and name like '%XXX%'

Re-generate the certificate to work

https://technet.microsoft.com/en-us/sqlserver/ff803383.aspx

select SMS_R_System.ResourceId, SMS_R_System.ResourceType, SMS_R_System.Name, SMS_R_System.SMSUniqueIdentifier, SMS_R_System.ResourceDomainORWorkgroup, SMS_R_System.Client from  SMS_R_System where SMS_R_System.IPAddresses >= "192.168.1.1" and SMS_R_System.IPAddresses <= "192.168.1.50"

Q: How can I check which SQL Server instance my SCVMM installation is using? A:  The easiest way to check which SQL Server instance your SCVMM installation is using is to look at the registry on the SCVMM server: Start the registry editor (regedit.exe). Move to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager Server\Settings\Sql. Look at the InstanceName and DatabaseName values for the SQL Server instance and database name. The ConnectionString value shows the complete combination. Close the registry editor.

Nice post on different things to try, http://sccmbrokeit.blogspot.com/2013/10/sccm-2012-client-troubleshooting.html   http://www.adaptiva.com/onesite/ http://blogs.msdn.com/b/scstr/archive/2012/05/31/configuration_2d00_manager_2d00_2012_2d00_sizing_2d00_considerations.aspx

if the reports struck , you can delete the dash board and re-scan the same

Security compliance manager helps to create 2012 server scan template in SCCM 2012