anyweb

you are looking at the SCCM client logs, you need to look at the server logs

both work, give it a go

no not yet, but post here and we'll help !

if it's missing on Server 2012r2 then you must not have the correct updates applied to the server, double check the updates i've listed and see did you miss any

of course you can do it using ConfigMgr, most people do it using MDT as it's quick and easy and well documented

we patch office after the task sequence is finished

we use offline servicing in Configmgr to patch the install.wim file with the latest available CU

we are just using the default install.wim and not capturing anything, we deploy that with whatever changes we need in the upgrade and deploy task sequences what deployment scenarios are you dealing with and why do you think you need to capture an image ?

are the clients reported as healthy ? can you do a teamviewer session so i can take a look ?

sounds like you have enabled dual scan which means your computers will download updates from the internet (microsoft) instead of your SCCM SUP, read this to see how to fix it https://blogs.technet.microsoft.com/windowsserver/2017/01/09/why-wsus-and-sccm-managed-clients-are-reaching-out-to-microsoft-online/ long story short, you can work around this by enabling a gpo to disable the ability to download from microsoft however, this will block the download of driver updates and Windows store...

can you go into more detail about 'it does not work', have you configured any boundaries ? what do the logs and component status tell you ?

i need the logs from the client only, but more than likely it is your AV software 'blocking' the upgrade, this can be seen by examining the xml files created in the C:\$WINDOWS.~BT\Sources\Panther\ folder if it fails again, inlcude the log+xml files in a zip from that folder and attach them here

that is not the smsts.log that is another one with the date/time added to it, which happens often when logs are rolled over and a new one is generated, the original log file must be there somewhere (probably c:\windows\ccm\logs\smstslog) can you double check (there can be two) smsts-yyyymmdd-hhmmss.log smsts.log

where is the other smsts.log it probably contains the actual failure message

ok your windowsupdate log is garbage, you need to clear the cache out and try again, read below to fix it If you encounter problems decoding the Windows Update log (for example, if you have multiple "GUID" entries that are displayed in the final text log), you may have to delete and then update your symbol cache. You can do this by deleting everything under the %temp%\windowsupdatelog folder. via > https://support.microsoft.com/en-us/help/3036646/how-to-read-windows-update-logs-in-windows-10-version-1607

run the powershell cmdlet get-windowsupdatelog on the client and attach the log here...

set it to a few hours and see what happens

right then the logic would have to change in the script, so that it knows if it's booted via standalone, and if so, skip the checkfornetwork step check for the following variable _SMSTSLaunchMode Specifies the task sequence launch method. The task sequence can have the following values: SMS - specifies that the task sequence is started by using the Configuration Manager client. UFD - specifies that the task sequence is started by using USB media and that the USB media was created in Windows XP/2003. UFD+FORMAT - specifies that the task sequence is started by using USB media and that the USB media was created in Windows Vista or later. CD - specifies that the task sequence is started by using a CD. DVD - specifies that the task sequence is started by using a DVD. PXE - specifies that the task sequence is started from PXE. HD – specifies that the task sequence was started from a hard disk (prestaged media only). and based on the value it returns do the above...

there's two way's to look at Intune, standalone (cloud based) or hybrid (mixture of SCCM on premise and cloud based backend) so for your needs you can do both, there are free trials available just sign up !

yes you should start with the current branch releases, very few companies use SCCM 2007

works fine for me, what happens when you click on it ?

Now... i'm sometimes using a standalone image, using the same boot image, is there a way in the script to detect it (or prestaged media) and bypass the network detection in this case? can you expand on this please ?

so you are setting this up in Server 2016 or ? where are the upgrades missing exactly, in WSUS or in the SUP ?

hi Alv2005 can you email me your cmupdate.log and any additional details and i'll see what i can find out cheers niall

well Windows 10 WSUS requirements are listed here https://docs.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wsus Requirements for Windows 10 servicing with WSUS To be able to use WSUS to manage and deploy Windows 10 feature updates, you must have WSUS 4.0, which is available in the Windows Server 2012 R2 and Windows Server 2012 operating systems. In addition to WSUS 4.0, you must install the KB3095113 and KB3159706 patches on the WSUS server. so have you fulfilled those requirements ?