Friday, May 9, 2014

Mz Computers - Software Management In SCCM 2012

The redirecting page will be displayed and immediately replaced by “MzComputers.com”. With this zero-delay, many users will not even notice the presence of the redirecting page.
Application Lifecycle Management With System Center Configuration Manager 2012


Packages
Application
Program (Command line for execution)
Deployment Types
Advertisement
Deployment (state based – deployment methods)
Collection Rules for targeting devices
Requirement targeting users and devices
No User targeting
User Device Affinity
Run Advertised Program
Software Center
No web catalog
Software Catalog
Limited Content Management
Content library
Application Model











State-based Application Management

´ Detection Method
´ Enable systems to determine whether or not an application is already present on a system
´ Many system attributes play into presence of an application on a system (registry, file versions, MSI database, etc.)
´ Detection is the key to any state based software distribution system
´ In ConfigMgr 2007
´ Collection rule targeting and status messages
´ Fire and forget software deployment model
´ Run once or schedules
´ Download and execution even if the software is already installed
´ In ConfigMgr 2012
´ Rules determine applicability of software
´ Presence determines if any action should take place on device
´ Regular evaluation to check for and enforce compliances



Requirement Rule in 2012
State-based Application Management

´ Properties of users and/or devices that makes delivering software appropriate
´ Rules are per deployment types
´ Evaluated in real time on clients
´ Evaluated before content is downloaded


Dependencies

´ Other deployment types that must be present in order for the current application deployment type to be installed
´ Dependencies are modeled as applications and can also be deployed independently
´ Two dependency uses:
´ Dependency not present, dont install application
´ Dependency not present, auto install dependent applications

Content Distribution

´ Distribution Point Groups
´ Can be linked to Collection for workflow optimization
´ Automatic distribution of content for distribution point added to the group

´ Distribute Content Wizard
´ Send multiple packages to multiple distribution points or groups at once
´ Detect Application dependencies and add them to the distribution
´ Select a task sequence and distribute all related content

´ Content Library
´ One source for multiple application, packages, update packages, etc.
´ Only files required by the distribution point are distributed over the network.
´ Bandwidth Control
´ Customize time and bandwidth utilization on distribution points



Deployment

´ Replaces Advertisement from Configuration Manager 2007
´ Created when an Application is deployed to the Collection
´ Due to applications being state based, only deploy to a collection once
´ Provides setting for Pre-deployment feature when targeting user or user security group collections


User Device Affinity

´ User Centric Software Distribution
´ Provides the ability to define a relation between a user and a device
´ Allows the admin to think user first, while also ensuring the application not installed everywhere the user logs on
´ Configuration Manager 2012 supports
´ Single primary user to primary device
´ Multiple primary device per user
´ Multiple primary users per device
´ The system allows both administrator and user to define this relationship
Introducing Application Uninstall

´ Uninstall is now part of Application Model
´ State-based application deployment includes removal of software in addition to installation
´ The App model defines an uninstall method for each Deployment type of an Application.
´ If a user or device is the recipient of both an install and uninstall deployment, then the install wins and the application is not removed


Application Supersedence

´ The ability for the admin to create a relationship and declare one application newer than another previous application. Ultimately resulting in the newer application replacing the older application.
´ Supersedence relationship is defined at both application level and deployment type.
´ Relationship Manager shows supersedence relationship


Thursday, May 8, 2014

Mz Computers - Software Update Management

The redirecting page will be displayed and immediately replaced by “MzComputers.com”. With this zero-delay, many users will not even notice the presence of the redirecting page.
Patch Deployment & Management with System Center Configuration Manager 2012


Key Investment in Update Management

§  Configuration
§  Superseded update support
§  SUM admin role
§  Client admin settings
§  Migration from SCCM 2007
§  Deployment
§  Simplified update groups
§  Automated deployments
§  End user experience
§  Maintenance
§  In-console view and monitoring
§  In-console alerts
§  Reporting
§  Content library and cleanup


Configure: Superseded Update

§  Publisher can expire or supersede software updates
§  SCCM 2007 automatically expires superseded updates
§  Update Publisher can control supersedence behavior
§  Supersedence rule can be created either to
§  Immediately expire a superseded update
§  Extend expiry of a superseded update for specific period

Configure: Migration from SCCM 2007

§  Migrate packages, deployment, list and templates
§  All the packages migrated could be seen under Software Updates and could be used to create new deployments
§  Persist update content availability from SCCM 2007 through Distribution Point sharing

Wednesday, May 7, 2014

Mz Computers - Cumulative Update 4 for System Center 2012 Configuration Manager

The redirecting page will be displayed and immediately replaced by “MzComputers.com”. With this zero-delay, many users will not even notice the presence of the redirecting page.

Software distribution
- Packages are listed as Unknown in the Content Status node of the Administrator Console. This occurs after a Configuration Manager 2007 distribution point is upgraded and assigned to a Configuration Manager 2012 secondary site.
- Internet-based clients cannot download content from an Internet-facing distribution point after first they first encounter a failure to reach Windows Update. The DataTransferService.log file on the client will record errors that resemble the following:
Failed to set proxy to bits job for url 'https:// site.configmgr.com:443/SMS_DP_SMSPKG$/{pkg_id}'. Error 0x87d00215
All proxy types and no proxy have been tried for times but failed.
2913703 (http://support.microsoft.com/kb/2913703/) Applications that use dynamic variable lists are not installed in System Center 2012 Configuration Manager
- Adding or deleting a deployment to a software update group results in policy evaluation for all deployments within the group instead of the deployment that changed.
Operating system deployment
- The wrong software update for an operating system image may be selected the list of items that are returned in the Schedule Updates Wizard is sorted.
2894539 (http://support.microsoft.com/kb/2894539/) A post-CU3 update is available for System Center 2012 Configuration Manager SP1.
Task sequences that contain Windows 8.1 as a condition on the Options tab generate an exception when they are changed or accessed. Details of the exception are displayed in text that resembles the following:
System.Reflection.TargetInvocationException
Exception has been thrown by the target of an invocation.
- Child sites will not process the content for a task sequence that was changed after migration from another site. The Distmgr.log file on the child site will contain entries that resemble the following, and the package state will not change:
Package {Package_ID} is in Pending state and will not be processed...
Note This fix applies only to task sequences that are not yet migrated. Task sequences that were migrated before you applied CU4 should be deleted and then migrated again.
- After the update is installed on site servers, any operating system boot images should be updated. To update boot images after the hotfix is applied, follow these steps:
  1. In the Configuration Manager console, click Software Library.
  2. In the Software Library workspace, expand Operating Systems, and then click Boot Images.
  3. Select the boot image that you want to update.
  4. Right-click and then select the Update Distribution Points action.
    Note This action updates all distribution points and may have an adverse effect on an environment that contains many distribution points.
  5. Repeat steps 3 and 4 for all boot images that were previously distributed.
For more information about how to update boot images, see the "How to Manage Boot Images in Configuration Manager” topic on the Microsoft TechNet website.
Administrator console
2894539 (http://support.microsoft.com/kb/2894539/) A post-CU3 update is available for System Center 2012 Configuration Manager SP1
The "All Windows RT" and "All Windows RT 8.1 Preview" entries should not appear in the supported platform list for new configuration items.
Application Virtualization
This cumulative update adds support for Microsoft Application Virtualization (App-V) 5.0 Service Pack 2 (SP2). The following issues are seen only in App-V 5.0 SP2 environments earlier than CU4.
- With App-V 5.0 SP2, when a new version of an App-V package supersedes an earlier version, and that earlier version is being used, the package will be listed as not published. Errors that resemble the following are seen in the AppEnforce.log and AppDiscovery.log files
AppEnforce.log:
Publish-AppvClientPackage : A publish operation has been scheduled, pending
the shutdown of all applications in the package or the connection group.

Publishing Package is successful but one one of the Virtual Package is currently in use. Close this Virtual Package to get the changes into effect
Performing detection of app deployment type TestApp - Microsoft Application Virtualization 5(ScopeId_0C7279F0-1490-4A0E-A7A3-32A000CEF76D/DeploymentType_d1adf427-ac14-4ee1-9e51-415af7675383, revision 2) for system.
AppDiscovery.log:
Required component [{AppVPackageRoot}]\TestApp.exe is not published
- With App-V 5.0 SP2, App-V packages that are being used cannot be uninstalled. Errors that resemble to the following will appear in the AppEnforce.log file:
CVEWorker::UninstallConnectionGroup() failed
Endpoint Protection
2907566 (http://support.microsoft.com/kb/2907556/) November 2013 anti-malware platform update for Endpoint Protection clients
Site Server
- Adding or removing a deployment from a Software Update group results in increased load on the Object Replication Manager component of the SMS Executive service. This can lead to delays in distributing software updates in a hierarchy.
=====
For all the details and download instructions, please see the following:
KB2922875 - Description of Cumulative Update 4 for System Center 2012 Configuration Manager Service Pack 1 (http://support.microsoft.com/kb/2922875)


Technet Blog: 

Tuesday, May 6, 2014

Mz Computers - Component with Error: SMS_MIGRATION_MANAGER

The redirecting page will be displayed and immediately replaced by “MzComputers.com”. With this zero-delay, many users will not even notice the presence of the redirecting page.
SMS Executive detected that this component stopped unexpectedly.
Possible cause: The component is experiencing a severe problem that caused it to stop unexpectedly.
Solution: Refer to your ConfigMgr Documentation or the Microsoft Knowledge Base for further troubleshooting information.



















Steps to resolve the error:
  • Go to the Central or Primary server (server without the above error)
  • Copy microsoft.configurationmanagement.migrationmanager.dll
  • Place the file under (InstallDir)\Microsoft Configuration Manager\bin\X64\ replacing existing file.
  • Open command prompt with admin privileges and navigate to C:\Windows\Microsoft.NET\Framework64\v4.0.30319\
  • Run command


RegAsm.exe (InstallDir)\Microsoft Configuration Manager\bin\X64\ microsoft.configurationmanagement.migrationmanager.dll /codebase