Wednesday, April 16, 2014

Failed to initiate install of WSUS updates, error = 0x800b0109

SCUP 2011 is integrated with SCCM 2012 R2. SCCM deploy the Adobe Reader X! updates but failed with error 0x800b0109. First thing I checked is whether the WSUS certificate is installed in the Trusted Root Certification Authorities and Trusted Publishers of Local Computer. Yes, the WSUS certificate is installed!!

Browsing the internet and saw there is a requirement to set GPO to enable the setting below:
"Administration Templates -> Windows Components -> Windows Update -> 'Allow Signed updates from an intranet Microsoft update service location'

After I enabled the settings, the Adobe Reader updates installed successfully.

Thursday, April 10, 2014

Configuration Manager Client Upgrade Package Distribution Failed

Whenever you setup a new distribution point, the system will automatically distribute 2 packages to the distribution point.
1. Configuration Manager Client Package
2. Configuration Manager Client Upgrade Package

But somehow the Configuration Manager Client Upgrade Package failed to distribute to the distribution point. The upgrade package is hidden, hence unable to redistribute the upgrade package like normal package. Therefore, we have to trick the system to redistribute the packages.

Trick:
1. Open an empty notepad and save it as client.acu
image
2. Copy the client.acu to the inboxes\hman.box folder at the top-level site
3. Monitor the hman.log to check whether the Client Upgrade package gets updated

Friday, March 14, 2014

OSD Error Code: 0x80220005

I’ve done Computer Name prompt for the OSD. But somehow I entered a computer name that’s too long, hence prompted me the error code 0x80220005 during the OSD running. After I rerun the OSD and entered a shorter name, there isn’t any more error code.

Monday, March 10, 2014

Fail to Capture Windows 7 SP1 x64 via Capture Media; Failed to create the Shared Environment object. Code(0x800705AF)

Recently I bumped into this error when I try to capture the Windows 7 SP1 x64 reference image. The reference machine was installed on a HyperV VM. Actually there are two reference image I try to capture; Windows 7 SP1 x86 & Windows 7 SP1 x64. Both also installed on the HyperV VM. Both assigned with the same resources, 1 VCpu, 512 Mb Memory RAM. But turned out the x86 version successfully captured and the x64 version failed with the error message “Failed to create the Shared Environment object. Code(0x800705AF)”. the error code basically means “The paging file is too small for this operation to complete”

My colleague asked me to assign more Memory RAM juice to the Windows 7 Sp1 x64 VM and retry. This time I assign 1024 Mb Memory RAM to the VM and give it a try. The error no more appear and the image is captured successfully.

Tuesday, March 4, 2014

SCCM 2012 R2 Primary Site to join SCCM 2012 SP1 CAS

I was doing some experiment yesterday to try out the scenario above. I’ve setup a SCCM 2012 SP1 CAS, then install a SCCM 2012 R2 primary site and try to join to the CAS 2012 SP1 hierarchy. Guess what…… It failed…… The setup wouldn't allow the setup to continue because it detected the new installation version is newer than the version installed on the CAS.
Untitled

Wednesday, February 26, 2014

Prerequisites Check Failed: Configuration Manager requires a dedicated SQL Server instance to host its site database

An old SCCM Primary site was setup in the same SQL instance before. The old SCCM SQL DB was corrupted and cannot be recovered. A new SCCM is setup using the same SQL instance that the old SCCM used. The prerequisites check detected the SQL instance is hosting another SCCM site, which is the old SCCM site. I’ve deleted the corrupted DB of the old SCCM, but there must be something that are still hidden and detected by the prerequisites checker.

Browsing through the internet and found that SCCM installation will create records in the SQL server registry. Yes, it is correct. There are still some leftover SCCM registry found in the SQL server registry, HKLM\Software\Microsoft\SMS. I deleted the SMS key and then rerun the prerequisites checker. The prerequisites checker passed and then SCCM installation succeeded. :)

Wednesday, January 29, 2014

SCCM 2012 SP1 CU4 is now available

Microsoft has just released CU4 for SCCM 2012 SP1. The update can be obtained from http://support.microsoft.com/kb/2922875.

According to the support article, below are the issues fixed.

Issues that are fixed
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

    (http://technet.microsoft.com/en-us/library/hh397288.aspx)

    " 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.