anyweb

IntroductionMicrosoft has released yet another update for System Center Configuration Manager (Current Branch), this time it’s version 1610, that means that since System Center Configuration Manager’s (Current Branch) first release there have been the following releases: 1511 (Initial release, soon to be unsupported) 1602 1606 followed by Update rollup 1 1610 So what’s new ? Windows 10 Upgrade Analytics integration allows you to assess and analyze device readiness and compatibility with Windows 10 to allow smoother upgrades. Office 365 Servicing Dashboard and app deployment to clients features help you to deploy Office 365 apps to clients as well as track Office 365 usage and update deployments. Software Updates Compliance Dashboard allows you to view the current compliance status of devices in your organization and quickly analyze the data to see which devices are at risk. Cloud Management Gateway provides a simpler way to manage Configuration Manager clients on the Internet. You can use the ConfigMgr console to deploy the service in Microsoft Azure and configure the supported roles to allow cloud management gateway traffic. Client Peer Cache is a new built-in solution in Configuration Manager that allows clients to share content with other clients directly from their local cache with monitoring and troubleshooting capabilities. Enhancements in Software Center including customizable branding in more dialogs, notifications of new software, improvements to the notification experience for high-impact task sequence deployments, and ability for users to request applications and view request history directly in Software Center. New remote control features including performance optimization for remote control sessions and keyboard translation. This release also includes new features for customers using Configuration Manager connected with Microsoft Intune. Some of the new feature include: New configuration item settings and improvements now only show settings that apply to the selected platform. We also added lots of new settings for Android (23), iOS (4), Mac (4), Windows 10 desktop and mobile (37), Windows 10 Team (7), Windows 8.1 (11), and Windows Phone 8.1 (3). Lookout integration allows to check device’s compliance status based on its compliance with Lookout rules. Request a sync from the admin console improvement allows you to request a policy sync on an enrolled mobile device from the Configuration Manager console. Support for paid apps in Windows Store for Business allows you to add and deploy online-licensed paid apps in addition to the free apps in Windows Store for Business. Upgrading to 1610You can upgrade directly to System Center Configuration Manager (Current Branch) 1610 from 1511, 1602 or 1606. If you are however upgrading from System Center Configuration Manager 2012 (SP1 or R2SP1) then you must upgrade to 1606 first. Below you can see the process of upgrading from 1606 to 1610. Click on Check for Updates if nothing appears today (2016/11/18) run the PowerShell script to get into the fast ring for this release. Once it’s found by the sub-system, the console will list the update in a state of downloading. and the dmpdownloader.log will reveal the Generating state message 6 and it’s corresponding guid. Once it’s downloaded the console will list it as state available. Installing the UpdateRight click on the update and choose Install Update Pack when the Wizard appears, make your choice for pre-reqs and click next. review list of Features included in this update pack, only one was selected when I ran this, so I selected the other two. Before clicking next at the Client update settings please see this post and review the EULA, Accept and continue close that wizard when done Note: The CMUpdate.log will take some time to start logging the installation of the update, so be patient if nothing appears to happen, it will. Once the update is installed you’ll see a HMAN notification. at which point you can upgrade the console to the latest version once done, the console version also sports a new Support ID

hi Peter, please post the smsts.log file so we can determine why it failed, first thoughts would be to verify the cdkey and/or unattend.xml references

have you tried integrating MDT into ConfigMgr and using what it provides ?

you can use maik kosters web services to achieve that, have you looked at them at all ?

what does distmgr.log tell you ?

from log1 that means it cannot communicate with the mp due to network issues (no ip, or dns problems), so you need to pause the task sequence mid action, and verify if it indeed is able to communicate with the dp/mp otherwise of course it will fail most likely cause, lack of network drivers in the boot image for the hardware involved cheers niall

what doesn't work exactly, can you attach your smsts.log file so i can take a look ?

you must always use the correct language pack cab file for the respective version of Windows, so Windows 10 1607 needs the 1607 cab files, and same for Windows 10 1511, it needs the 1511 language cab files and so on...

is sql running on a separate server ? what do the event viewer logs tell you ?

that's the way it works with Windows 10, see > http://rzander.azurewebsites.net/how-to-change-the-welcome-screen-language-in-win10/

are the client settings to enable SCEP management correctly deployed to the target collection ?

i'll happily help you with getting your frontend working, feel free to add me to skype or whatever

hi Art and welcome, glad you are here :-) cheers niall

can you attach your smsts.log please

hi and welcome take a look at these posts they should get you started, you'll need to incorporate web services to get that functionality it's all covered in the windows-noob OSD book in great details by the way https://www.windows-noob.com/forums/topic/1064-step-by-step-guides-system-center-configuration-manager-2007/#entry11753

can you attach your dmpdownloader.log and cmupdate.log please

have you tried restarting the SMS_Executive component ?

it will hide if you use the correct version (architecture) of windowhide.exe for those boot images.

are you sure it's using the specified customsettings.ini ?

what version of SCCM are you running exactly ?

a standard user is fine, the permissions are not for changing the time, but to contact Active Directory via Net Time .

have you seen this post from Paul ? it's for 1602 but it should be the same scenario

so to summarize, you have captured the Windows 7 wim using SCCM correct ? and when you deploy it using a task sequence Windows ends up on D: ? when using the osdpreservedriveletter=false, what drive letter does Windows end up on ? cheers niall

hi, look at your logs again, it's ok if you missed it, so did I Feature update to Windows 10 <SKU>, version 1607, <language> are the actual updates for Windows 10 1607, so it's working fine ! i.e. the Windows 10 upgrades are now known as Feature Updates... cheers niall

i havn't tried it yet but hope to do so this weekend, i'll ask Microsoft to comment in the meantime