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.
Friday, September 11, 2015
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
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
Thursday, July 9, 2015
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.
|
CM2012 Build Versions
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 |
query to see package status in numbers
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%'
Monday, July 6, 2015
Subscribe to:
Posts (Atom)
SCCM to Tanium
SCCM transition Options: of course intune otherwise Deployment, Patching - Tanium Image - Tazier Inventory - Tanium Remote Control - Zoom ...
-
When a package is distributed to a PullDP, DistMgr creates a PkgXferMgr job and added to the queue. - PkgXferMgr processes the job and cre...
-
How to fix the SMS client GUID issue 1.If the client status unknown in the SMS console after installing the SMS client (make sure that ...
-
Below is a PowerShell script, this will list WDS Service status against of List of servers. $InPutComputersList = get-content "c:\M...