anyweb

can you explain this part of your original post "I have multiple language packs installed in my reference image"

looks ok to me, but are all computers using the same timezone ? have you tried condensing it (and speeding up testing) into a test run in a lab, by changing the 'weeks' into 'hours' for example...

well I think it's broken, I've submitted a bug on Connect, please vote it up or comment on it too if you want, Microsoft will fix this https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/3118154/mvp-bug-get-cmalert-is-not-working-as-designed cheers niall

I get weird results too both with SCCM 1606CB and SCCM 1610CB, i'm checking with Microsoft PG and will come back to you

have you tried grabbing the unattend.xml after it's modified after the apply operating system step and before the restart computer step ?

the file in the associated application/package you are deploying most likely....

this is how my SCCM 1610 CB vm looks like now....

i've just turned on that lab again (SQL 2016/Server 2016/SCCM 1610CB) and will let it 'catch up' with itself for a bit and then check the cpu usage, right now it's high but that's expected when resuming a vm from a saved state..... i'm using hyperv are you too ?

the error translates to Failed to verify the executable file is valid or to construct the associated command line. Source: System Center Configuration Manager ----- you can use Cmtrace to convert these errors into meaningful text

does it fail consistently or randomly ? what version of MDT is it occurring with ?

i'd suggest you open a ticket with Microsoft CSS, did you have any replication issues prior to the upgrade ?

thanks for clarifying that, I never got around to it due to time constraints and went the eval route for my blog post, along with a follow up here > How can I change System Center Configuration Manager from an Eval edition to a Licensed edition ? I've also added this point to the guide, thanks again !

yes but you might want to upgrade it at some point Windows Server 2008 R2 with SP1 (x64) - Standard, Enterprise, DatacenterWindows Server 2008 R2 is now in extended support and no longer in mainstream support, as detailed by the Microsoft Support Lifecycle. For more information regarding future support for these operating systems as site system servers with Configuration Manager, see Removed and deprecated features for System Center Configuration Manager. Site servers: Central administration site Primary site Secondary site Site system servers: Application Catalog web service point Application Catalog website point Asset Intelligence synchronization point Certificate registration point Distribution point Distribution points support several different configurations that each have different requirements and in some cases support installation not only on servers, but on client operating systems. For more information about the options available for distribution points, see Manage content and content infrastructure for System Center Configuration Manager. Endpoint Protection point Enrollment point Enrollment proxy point Fallback status point Management point Reporting services point Service connection point Site database server Site database servers are not supported on a read-only domain controller (RODC). For more information, see You may encounter problems when installing SQL Server on a domain controller in the Microsoft Knowledge Base. Additionally, secondary site servers are not supported on any domain controller. SMS_Provider Software Update point State migration point Windows Server 2008 with SP2 (x86, x64) - Standard, Enterprise, DatacenterWindows Server 2008 is now in extended support and no longer in mainstream support, as detailed by the Microsoft Support Lifecycle. For more information regarding future support for these operating systems as site system servers with Configuration Manager, see Removed and deprecated features for System Center Configuration Manager. Site servers: Central administration site Primary site Secondary site Site system servers: Application Catalog web service point Application Catalog website point Asset Intelligence synchronization point Certificate registration point Distribution point Distribution points on this operating system do not support Multicast. Distribution points on this operating system are supported for PXE, but do not support network booting of client computers in EFI mode. Client computers with BIOS or with EFI booting in legacy mode are supported. Distribution points support several different configurations that each have different requirements and in some cases support installation not only on servers, but on client operating systems. For more information about the options available for distribution points, see Manage content and content infrastructure for System Center Configuration Manager. Endpoint Protection point Enrollment point Enrollment proxy point Fallback status point Management point Reporting services point Service connection point Site database server Site database servers are not supported on a read-only domain controller (RODC). For more information, see You may encounter problems when installing SQL Server on a domain controller in the Microsoft Knowledge Base. Additionally, secondary site servers are not supported on any domain controller. SMS_Provider Software Update point State migration point https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/supported-operating-systems-for-site-system-servers

here's the process https://www.windows-noob.com/forums/index.php?/topic/4683-using-sccm-2012-rc-in-a-lab-part-12-updating-an-operating-system-image-using-offline-servicing/ however it does not apply to office updates

I like offline servicing myself, what OS are you interested in patching ?

to support Windows 10 servicing, your software update point (SUP) needs to be running WSUS 4.0 or later, and that means Windows Server 2012 or later, with SCCM CB 1610 you can do an in place upgrade of the operating system from Server 2008 to Server 2012R2 see > https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/whats-new-in-version-1602#site-infrastructure also take note of the Warning... WarningBefore you upgrade to Windows Server 2012 R2, you must uninstall WSUS 3.2 from the server. For information about this critical step, see the New and changed functionality section in Windows Server Update Services Overview in the Windows Server documentation.

it doesn't work that way, you can only upgrade to a newer version of Windows 10 using the upgrade task sequence, or using a frontend HTA to 'refresh' while in WinPE, but that would mean having to define your own USMT ruleset, i'd suggest if you want to upgrade, then do it in Windows or instead of applying the 1511 wim why not simply apply the 1607 wim ?

are you referring to updating the WIM files using offline servicing ? that process is covered in step 4 in the first guide linked below: How can I use the Upgrade Task Sequence in System Center Configuration Manager (Current Branch) ? A deeper look at the Upgrade task sequence in System Center Configuration Manager (Current Branch) if you have any issues let me know

thanks and welcome to windows-noob.com

what version of configuration manager are you running, on what server os ?

I'm afraid not, i just checked this and... Central administration site and Primary sites: The site database must use a full install of SQL Server.

hi, so you didn't try the fix above ?

what drivers are not installed in device manager ? did you download a SCCM cab file from Lenovo for this task ?

ok could be this, please try the suggested workaround below An update is stuck with a state of Downloading in the Updates and Servicing node of the Configuration Manager consoleDuring the automatic download of updates by an on-line service connection point, an update can become stuck with a stat of Downloading. When the download of an update is stuck, entries similar to the following appear in the indicated log files: DMPdownloader log: ERROR: Failed to download redist for 037cd17e-4d7b-40e1-802b-14bb682364c7 with command /RedistUrl http://go.microsoft.com/fwlink/?LinkID=724436 /LnManifestUrl http://go.microsoft.com/fwlink/?LinkID=724434 /RedistVersion 112015 /NoUI "D:\ConfigMgr\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\redist" ConfigMgrSetup.log: Error: failed to verify 'd:\ConfigMgr\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\redist\sqlncli.msi' authenticode signature. Error: file signature check failed for 'd:\ConfigMgr\EasySetupPayload\037cd17e-4d7b-40e1-802b-14bb682364c7\redist\sqlncli.msi Workaround: On the site server, modify the following registry key to match the following, and then either restart the SMS_Executive service, or wait up to 24 hours for the next automatic download cycle. Key to edit: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing Value for State: Set to 146944 Decimal or 0x00023e00 Hexadecimal

is the client computer in a collection targeted by the ADR ?