Archive: Posts Tagged ‘What’s’

SCCM 2012 | Update to add Apple iOS 10 to the Supported Platforms list for System Center Configuration Manager, version 1606 !

Commentaires fermés septembre 16th, 2016

Hi to all :-)   ,

A new update has been released that adds the following platforms to the supported platforms list for Microsoft System Center Configuration Manager current branch, version 1606:

This update adds the following platforms to the supported platforms list for Microsoft System Center Configuration Manager current branch, version 1606:

  • All iOS 10 iPhone or iPod Touch devices
  • All iOS 10 iPad devices

These iOS 10 devices may be targeted as client platforms for features such as Application Deployment, Compliance Settings, and Company Resource Access.

After you install this update, the Supported Platforms tab of policy settings has an All iOS 10 iPhone or iPod Touch devices option in the iPhone category and an All iOS 10 iPad devices option in the iPad category.

Policies that previously had the root category (iPhone or iPad) selected now have iOS 10 automatically selected together with all earlier iOS versions. Previously, when individual iOS versions, such as All iOS 7 IPad devices, were selected but the corresponding top level category was not selected, the policies did not automatically have iOS 10 selected.

Update information for System Center Configuration Manager, version 1606

This update is available for installation in the Updates and Servicing node of the Configuration Manager console if the following conditions are true:

This update also applies to Configuration Manager consoles. For more information, see the Updates for System Center Configuration Manager TechNet topic.

Restart information

You do not have to restart the computer after you apply this update.

Update replacement information

This update does not replace any previously released update.
source

System Center 2012 WORLD Community Social Network !

VIDEO ARCHIVES :-)

SCCM 2012 – How to install and configure SCCM 2012 – Central Administration Site (CAS)

SCCM 2012 | Configuration Manager and the Windows ADK for Windows 10, version 1607 available !

Commentaires fermés septembre 9th, 2016

Hi to all, :-)

Configuration Manager and the Windows ADK for Windows 10, version 1607 AVAILABLE !

The Windows Assessment and Deployment Kit (ADK) for Windows 10, version 1607, is available on the Microsoft Hardware Dev Center (adksetup.exe file version 10.1.14393.0).

This version of the ADK has been primarily tested and is supported starting with the most recent release of the Configuration Manager current branch, version 1606. As noted in the above FAQ (which you already read, right?) we have limited support for Windows 10, version 1607, in Configuration Manager version 1602. Customers that are still on this version of Configuration Manager and will be deploying the newer version of Windows 10 can upgrade the ADK to the latest version if desired, or remain with the prior version, Windows ADK for Windows 10, version 1511. Beyond that, we do not support deployment of Windows 10, version 1607, with older versions of Configuration Manager , so the need for this new version of the Windows ADK does not apply.

If you’ve read that last paragraph a few times and are still scratching your head, let’s try the same in tabular format:

Windows 10 ADK Version
ConfigMgr Version 1507 1511 1607
1511 Supported Supported
1602 Supported Supported 1 Supported 2
1606 Supported 1 Supported

1 The Windows ADK for Windows 10, version 1511, provides basic forward compatibility and can be used for image capture, image apply, driver injection, and offline update servicing of Windows 10, version 1607, if absolutely necessary. We strongly recommend upgrading to the latest ADK version, but basic forward compatibility is supported during the transition period.

2 The newer ADK is only needed if deploying Windows 10, version 1607.

Frequently Asked Questions

Q. Does this include the hotfix 3143760 for the Windows 10 ADK, version 1511?

As noted in support article 3143760, that hotfix only applies to version 1511. The underlying problem requiring the hotfix is not present in the Windows 10 ADK, version 1607.

Q. What’s the process to update? Do I need to restart the server?

Use the following process to update the Windows ADK on your site server(s):

  1. Uninstall the previous Windows ADK from Programs/Features control panel.
  2. Install the Windows ADK for Windows 10, version 1607.
    • NOTE: We do not recommend using a custom installation path for the Windows ADK when used in conjunction with Configuration Manager.
  3. Restart the server. (You may not be prompted to restart, and some will suggest that this is not required. The best practice to ensure all components are properly registered, especially the WIMGAPI filter driver used by DISM, is to restart.)
  4. Refresh the package for the User State Migration Tool for Windows. Select the package and click Update Distribution Points.

Q. Do I need to update boot images and media?

Yes, any Windows 10-based boot image will need to be regenerated to consume the new version of Windows PE. (Updating the boot image just rebuilds from a cached copy, injecting the latest Configuration Manager binaries, drivers, etc.) There is not (yet) currently a process in the console to regenerate boot image with the latest winpe.wim (as this was traditionally handled by the Configuration Manager setup process), so it does require triggering the ExportDefaultBootImage WMI method against the target boot images. Here is a Windows PowerShell script (RegenerateBootImageWinPE10.ps1), written by Wilhelm Kocher and Herbert Fuchs from Microsoft Premier, to automate and simplify this process. Run the script from an elevated Windows PowerShell prompt.

Q. I’m upgrading from Configuration Manager version 1511/1602 to version 1606. Should I upgrade the Windows ADK first?

The in-console servicing updates do not currently regenerate the default boot images, just update them with the latest Configuration Manager binaries. You can use the ADK install process above to upgrade the Windows ADK before or after updating the site to 1606, but you also must use the process above to regenerate the default boot images so that they are using the latest version of Windows PE.

Q. My site version is currently System Center 2012 R2 Configuration Manager SP1 and I plan on upgrading to current branch version 1511 and then immediately updating the site to version 1606. When should I upgrade the Windows ADK?

The default boot images will be regenerated from the installed Windows ADK during the CD-based setup process when upgrading to the current branch baseline build. While we do not support the use of the Windows ADK for Windows 10, version 1607, with any version of System Center 2012 R2 Configuration Manager, we recommend upgrading the Windows ADK first (immediately before upgrading the site) so that the latest Windows PE is consumed at that time.

Q. What about Configuration Manager Technical Preview sites?

Yes, the Windows ADK for Windows 10 should be upgraded to version 1607 with Configuration Manager Technical Preview version 1606 and later.

Q. What about the Microsoft Deployment Toolkit (MDT)?

We have done limited testing with MDT 2013 Update 2 and the Windows ADK for Windows 10, version 1607, thus support this usage. There will be an update to MDT coming later this fall.

Source


VIDEO ARCHIVES :-)

SCCM 2012 – How to install and configure SCCM 2012 – Central Administration Site (CAS)

SCCM 2012 | Update Rollup 1 for System Center Configuration Manager current branch, version 1606 available !!

Commentaires fermés septembre 8th, 2016

Hi to all, :-)

Great news, the Update Rollup 1 for System Center Configuration Manager current branch, version 1606 is available for download !!!!

What’s new in this update ?

Additional changes included in this update

Windows Server 2016 is now available in the supported platform list for Content Distribution, Software Update Management, and Settings Management!


Issues that are fixed

Administrator Console

The System Architecture section of the Choose Updates pane in the Schedule Updates Wizard incorrectly shows x86 as the platform instead of x64.

Updates and servicing

Update packages installed through the Updates and Servicing node of the console show a status of « In progress » for installation when there are no redistributable files to validate.

Client

Software center incorrectly displays a status of Waiting to install when it should display « Waiting for next available maintenance schedule. »
Clients installed through Configuration Manager Operating System deployment may take longer than expected to start to install device-targeted deployments. This issue occurs if the SMS Agent Host (ccmexec.exe) restarts after installation while policy data is being downloaded. Messages that resemble the following are recorded in the PolicyAgent.log file on the client:
Policy [...]is pointing to invalid DTS job [{GUID}]. Will attempt to re-download

Configuration Manager Clients installed on Windows Embedded POS Ready 2009 computers cannot download content for application deployments. Errors that resemble the following are recorded in the ExecMgr.log file on the client:
CoCreateInstance ContentAccessService failed 0×80040154

Inventory data that is received from a Mac client computer may not be processed as expected on the site server. This issue occurs when the inventory data contains an unexpected carriage return. Additionally, error messages that resemble the following are logged in the SMS_DM.log file, even though the client certificate is correct:
Send status message: DMPMSG_ERROR_CLIENT_CERTIFICATE_PROBLEM
An existing device CN=User_name needs to re-register.

Software updates

Attempts to service a server group (cluster patching) on a child primary site that has a remote management point result in errors. Error messages that resemble the following are logged in the MP_ClientID.log file:
CMPDBConnection::ExecuteSQL(): ICommandText::Execute() failed with 0×80040E09
MPDB ERROR – EXTENDED INFORMATION
MPDB Method : ExecuteSP()
MPDB Method HRESULT : 0×80040E09
Error Description : The EXECUTE permission was denied on the object ’spGetLockState’, database ‘CM_PRI’, schema ‘dbo’.

A software update group that contains Microsoft Office updates may not always replicate to a secondary site. Messages that resemble the following are recorded in the PkgXferMgr.log file on the site server:
Invalid object name ‘v_UpdateContents’

Note This issue only affects the delta replication of Office updates.

Site Systems

Inventory views are not updated to reflect the removal of applications uninstalled from mobile devices.

Operating System Deployment

Task sequences that contain the Install Software Update step cannot be imported in Configuration Manager, version 1606. Additionally, you receive an error message that resembles the following, and the error is recorded in the SMSAdminUI.log file:
System.NullReferenceException
Object reference not set to an instance of an object.

The Install Application task sequence step, when it is applied to pre-staged media, downloads content from a distribution point instead of using the content that is stored on the media. This issue increases the time for task sequence execution from pre-staged media.

Windows Store for Business

Offline license information for Windows Store for Business applications is not replicated in a Configuration Manager hierarchy.
,
When you click the Content Status link for the deployment of an online Windows Store for Business application, you receive the following error message in the Administrator Console:
system.NullReferenceException

Not all expected applications are synchronized during synchronization of applications from the Windows Store for Business. Errors that resemble the following are recorded in the WsfbSyncWorker.log file:
There was a problem with the configuration for Windows Store for Business.
Exception: [System.ArgumentException: Content location does not exist or user does not have access.

The Create Date field in the Administrator Console is empty for Online Windows Store for Business applications.

Software distribution and content management

Redistributing a package to a remote distribution point at a secondary site results in all distribution points for that site receiving the package. This issue occurs when the secondary site was recovered, and the original database was lost.

Endpoint Protection

.EPP files remain in the \EpMgr.box\process folder after all files are successfully processed into the database. Additionally, errors that resemble the following are recorded in the EPMgr.log file on the site server:
Failed to check if file \\?\E:\Microsoft Configuration Manager\inboxes\epmgr.box\process\\mi26ckw8.EPP exists with error 123

Sources

VIDEO ARCHIVES :-)

SCCM 2012 – How to install and configure SCCM 2012 – Central Administration Site (CAS)