Install SMB Share SCVMM 2012 R2 UR5 UI Hotfix

With UR5 there is a bug in the UI that does not show SMB file shares when you try to deploy HA VM or do storage migration to SMB share. Functionality was still working when you use PowerShell. Continue reading “Install SMB Share SCVMM 2012 R2 UR5 UI Hotfix”

Insufficient Permissions on Custom Fields in SCSM 2012 SP1/R2

I’ve recently stumbled on the following error in SCSM 2012 R2: Continue reading “Insufficient Permissions on Custom Fields in SCSM 2012 SP1/R2”

Cumulative Update 1 for System Center 2012 Configuration Manager

CU1 for SCCM 2012 is released. The important thing to notice is that this update is actually marked as hotfix and I recommend to install if you have and want to resolve some of these issues:

Administrator Console
  • When a new distribution point is added to a package that contains more than 100 existing distribution points, the new distribution point cannot be added, and you receive the following error message in the Administrator Console:

    The SMS Provider reported an error.

    When you click Details in the error message, a "Quota Violation" message is displayed that is followed by the details of the stack trace.

  • The link to the online privacy statement for the Customer Experience Improvement Program in the Administrator Console is fixed.
Application Management
  • If a Deployment Type is added or changed before Distribution Manager processes an earlier change, the content may not be sent to a child site.
  • The prestaged content file for a Deployment Type (DT) is not created for remote Distribution Points when there are multiple DTs for the same application. For more information about prestaged content, go to the following Microsoft TechNet website:

    Operations and Maintenance for Content Management in Configuration Manager

Asset Intelligence
  • Volume license editions of Microsoft SQL Server 2012 may be duplicated in the Asset Intelligence Installed_Software_data hardware inventory class.
  • Microsoft SQL Server 2008 R2 Service Pack (SP1) is not listed in the Asset Intelligence License 01D – Microsoft License Ledger Products on a Specific Computer report.
  • The pre-provisioned Asset Intelligence Synchronization Point certificate is updated with a new expiration date.
Client
  • When a dynamic list is used for the Install Application task sequence, not all deployment types will be installed. This issue occurs when one of the deployment types restarts the computer. In this case, any deployment type after the restart is not installed. The state messages that are associated with each application indicate Success. This issue can be seen most clearly in the smsts.log file on the client when the log file is filtered in the CMTrace for entries that contain the text "Installing application."
    The following is an example sequence:

    Installing application ‘App 1’
    Installing application ‘ContentID for App 1′ has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID1}’
    Installing application ‘App 2’
    Installing application ‘ContentID for App 2′ has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID2}’
    Installing application ‘App 3 – Exit Code 3010′
    Installing application ‘ContentID for App 3′ has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID3}’
    Installing application ‘App 4’
    Installing application ‘ContentID for App 2′ has started. Please refer to DCMAgent.log for the details on this job. JobID='{JobID4}’

    Note Both ‘App 2’ and ‘App 4’ share the same content ID. In this example sequence, ‘App 4’ was not installed following the restart that ‘App 3’ triggered.

Out of Band Management
  • Power Control and Clear Audit Log collection-based actions fail for externally provisioned AMT clients. The amptopmgr.log file contains entries that resemble the following entry:

    Error: CSMSAMTDiscoveryTask::Execute, discovery to client_computer failed. General Worker Thread Pool: Error, Can not execute the task successfully. Remove it from task list.

  • Site Database
  • Replication Link Analyzer incorrectly detects a syscommittab system table issue and suggests reinitialization if the SQL Errorlog contains the following string:

    3999

  • A primary device cannot be selected for user-based pre-deployment if the device does not have the Configuration Manager client installed.
Site Systems
  • A Reporting Services Point may not be installed or start if the SQL Reporting Service does not start within one minute. The srssp.log file may contain entries that resemble the following entry:

    Starting service ‘ReportServer’
    Time out has expired and the operation has not been completed.

  • The SMS Executive service may stop unexpectedly if the Exchange Connector PowerShell cmdlet fails. The EasDisc.log file may contain entries that resemble the following entry:

    ERROR: [MANAGED] Cmdlet failed: Starting a command on remote server failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.

  • The Site System Status Summarizer component may cause the SMS Executive service to stop unexpectedly if the site server fully qualified domain name (FQDN) is more than 50 characters, and the default installation path is used. The relevant entries from the Exception Information section of the crash.log files contain the following entry:

    Thread name = SMS_SITE_SYSTEM_STATUS_SUMMARIZER
    Executable = C:\Program Files\Microsoft Configuration Manager\bin\x64\smsexec.exe
    Exception = eeeeffff (EXCEPTION_SMS_FATAL_ERROR)

The hotfix can be downloaded from here.

KB: Operations Manager agents consume 100 percent of CPU resources for the Monitoringhost.exe process

If you see such issue in your SCOM 2007 or 2012 environment you just have to install hotfix on the operating’s systems with this problem. Find out which hotfix on Microsoft knowledge base article KB974051.

QFE Rollup Package 6 for System Center Data Protection Manager 2010 is released

Microsoft released a new hotfix for SCDPM 2010. This hotfix resolves several issues:

  • DPM backup fails for a Microsoft SharePoint farm together with a mirrored content database if the mirrored server name starts with the same name as the principal server name. For example, this issue occurs if the principal server name is "MachineName," the mirrored server name is "MachineName1," and the content database is on a nondefault instance of Microsoft SQL Server. 
    Additionally, you receive the following error message:

    Prepare for backup operation for SQL Server database CONTENT_DB_NAME (mirrored between – SQL PRINCIPAL and SQL MIRROR ) on SQL-PRINCIPAL.FQDN has been stopped because this operation depended on another backup operation which failed or was cancelled. (ID 30200)

  • Expiry dates for valid datasets that are already written to tape are changed when the retention range is changed during a protection group modification.
    A protection group is configured for long-term tape recovery points together with custom long-term recovery goals. Recovery Goal 1 has a smaller retention range than the other recovery goals. In this configuration, if the protection group is changed to remove Recovery Goal 1 and to keep other recovery goals, datasets that were created by Recovery Goal 1 have their retention range changed to the retention range of the other recovery goals.
    To avoid this problem, create the IsDatasetExpiryDateChangeInModifyPgAllowed DWORD value under the following registry key, and then set its value data to 0:

    HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

  • Tapes are not reusable until the day after the day of expiry. This is true because DPM waits until midnight to run the reclamation job that marks tapes as reusable. If a user wants a tape to be reusable on the same day on which it expires, the user should follow these steps: 
    1. Create the following registry key:

      HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MediaManager

    2. Create the ExpireDatasetOnDayStart 32-bit DWORD value, and then set its value data to 1.
  • DPM does not enable browsing of protected folders on a protected server that has an invalid created date and time.
  • A tape backup of millions of files fails, and you receive the following error message: 

    ID 998 Details: The parameter is incorrect (0x80070057).

  • Tape colocation that has a high expiry tolerance mixes retention ranges. This causes tapes to expire earlier than expected.
    Full information and instructions for implementing about this hotfix can be found here.
    The update itself can be downloaded from here.