nazimb

I just upgraded to 1703 using a Servicing Plan in SCCM, however I lost all the pinned program from the Start menu. Also, I had to re-install the RSAT update. Wondering if you anyone had the same issue? Thanks,

How about changing the SP Deployment setting from Required available in The Software Update Groups ?

any clue?

Hello, I was wondering if there is a way to set a servicing plan deployment to Available instead of Required, so the users can trigger it manually. Also I'm missing the "Upgrade to Windows 10 1703" , all the upgrades available are for 1511 and 1607 ,any idea why?

Here is the PkgXferMgr.log Found send request with ID: 33548, Package: SE1000CD, Version:9, Priority: 2, Destination: TORMGMT.INT.sweet.COM, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:25 AM 15896 (0x3E18) Created sending thread (Thread ID = 0xD10) SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:25 AM 15896 (0x3E18) No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:25 AM 15896 (0x3E18) Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:25 AM 15896 (0x3E18) Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:25 AM 15896 (0x3E18) Sending thread starting for Job: 33548, package: SE1000CD, Version: 9, Priority: 2, server: TORMGMT.INT.sweet.COM, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:45 AM 3344 (0x0D10) Sent status to the distribution manager for pkg SE1000CD, version 9, status 0 and distribution point ["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\ SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:46 AM 3344 (0x0D10) Sending legacy content SE1000CD.9 for package SE1000CD SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:46 AM 3344 (0x0D10) Fail to get volume information of drive Z:\. SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:46 AM 3344 (0x0D10) Redistribute=1, Related= SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:46 AM 3344 (0x0D10) Fail to get volume information of drive Z:\. SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:46 AM 3344 (0x0D10) Sending file '\\TORMGMT.int.sweet.com\SMS_DP$\1E5CC0139198B0F251EF0D57DDC2277C33A2EB79F72D5EBED5F8A876B6EEBB66-SE1000CD.9.temp' SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:50:46 AM 3344 (0x0D10) Adding REF-Win10x64.wim file in SE1000CD.9. SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:52:45 AM 3344 (0x0D10) user(NT AUTHORITY\SYSTEM) runing application(SMS_PACKAGE_TRANSFER_MANAGER) from machine (SESCCM.int.sweet.com) is submitting SDK changes from site(SE1) SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:56:23 AM 3344 (0x0D10) Finished sending SWD package SE1000CD version 9 to distribution point TORMGMT.INT.sweet.COM SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:56:25 AM 3344 (0x0D10) STATMSG: ID=8200 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=3344 GMTDATE=Wed Nov 09 16:56:25.787 2016 ISTR0="SE1000CD" ISTR1="9" ISTR2="TORMGMT.INT.sweet.COM" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="SE1000CD" AID1=410 AVAL1="9" SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:56:25 AM 3344 (0x0D10) Sent status to the distribution manager for pkg SE1000CD, version 9, status 3 and distribution point ["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\ SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:56:25 AM 3344 (0x0D10) STATMSG: ID=8210 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=3344 GMTDATE=Wed Nov 09 16:56:25.797 2016 ISTR0="SE1000CD" ISTR1="9" ISTR2="TORMGMT.INT.sweet.COM" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="SE1000CD" AID1=410 AVAL1="9" AID2=404 AVAL2="["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\" SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:56:25 AM 3344 (0x0D10) Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 11/9/2016 11:56:25 AM 3344 (0x0D10)

Adding package 'SE1000CD' to package processing queue. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 12828 (0x321C) Currently using 0 out of 3 allowed package processing threads. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 12828 (0x321C) Started package processing thread for package 'SE1000CD', thread ID = 0x4B64 (19300) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 12828 (0x321C) Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 12828 (0x321C) STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=19300 GMTDATE=Wed Nov 09 16:50:00.812 2016 ISTR0="SE - EN - Windows 10 Enterprise (Test)" ISTR1="SE1000CD" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SE1000CD" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 19300 (0x4B64) Processing package SE1000CD (SourceVersion:9;StoredVersion:9) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 19300 (0x4B64) No action specified for the package SE1000CD, however there may be package server changes for this package. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 19300 (0x4B64) Start updating package SE1000CD on server ["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\... SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 19300 (0x4B64) Created DP processing thread 8332 for addition or update of package SE1000CD on server ["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\ SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 19300 (0x4B64) DP Thread: Attempting to add or update package SE1000CD on DP ["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\ SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 8332 (0x208C) STATMSG: ID=2342 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=8332 GMTDATE=Wed Nov 09 16:50:00.840 2016 ISTR0="SE - EN - Windows 10 Enterprise (Test)" ISTR1="["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="SE1000CD" AID1=404 AVAL1="["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 8332 (0x208C) Waiting for all DP threads to complete for package SE1000CD processing thread. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:00 AM 19300 (0x4B64) The current user context will be used for connecting to ["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:01 AM 8332 (0x208C) Successfully made a network connection to \\TORMGMT.int.sweet.com\ADMIN$. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:01 AM 8332 (0x208C) Ignoring drive \\TORMGMT.int.sweet.com\C$\. File \\TORMGMT.int.sweet.com\C$\NO_SMS_ON_DRIVE.SMS exists. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:01 AM 8332 (0x208C) Ignoring drive \\TORMGMT.int.sweet.com\Z$\. File \\TORMGMT.int.sweet.com\Z$\NO_SMS_ON_DRIVE.SMS exists. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:01 AM 8332 (0x208C) user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine (SESCCM.int.sweet.com) is submitting SDK changes from site(SE1) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:01 AM 8332 (0x208C) CreateSignatureShare, connecting to DP SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:02 AM 8332 (0x208C) Signature share exists on distribution point path \\TORMGMT.int.sweet.com\SMSSIG$ SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:02 AM 8332 (0x208C) Ignoring drive \\TORMGMT.int.sweet.com\C$\. File \\TORMGMT.int.sweet.com\C$\NO_SMS_ON_DRIVE.SMS exists. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:02 AM 8332 (0x208C) Ignoring drive \\TORMGMT.int.sweet.com\Z$\. File \\TORMGMT.int.sweet.com\Z$\NO_SMS_ON_DRIVE.SMS exists. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:02 AM 8332 (0x208C) Share SMSPKGE$ exists on distribution point \\TORMGMT.int.sweet.com\SMSPKGE$ SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:02 AM 8332 (0x208C) user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine (SESCCM.int.sweet.com) is submitting SDK changes from site(SE1) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:02 AM 8332 (0x208C) Created package transfer job to send package SE1000CD to distribution point ["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:03 AM 8332 (0x208C) STATMSG: ID=2357 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=8332 GMTDATE=Wed Nov 09 16:50:03.812 2016 ISTR0="SE1000CD" ISTR1="["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=2 AID0=400 AVAL0="SE1000CD" AID1=404 AVAL1="["Display=\\TORMGMT.int.sweet.com\"]MSWNET:["SMS_SITE=SE1"]\\TORMGMT.int.sweet.com\" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:03 AM 8332 (0x208C) Performing cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:03 AM 8332 (0x208C) Cancelling network connection to \\TORMGMT.int.sweet.com\ADMIN$. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:03 AM 8332 (0x208C) Currently using 1 out of 3 allowed package processing threads. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:05 AM 12828 (0x321C) Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:05 AM 12828 (0x321C) DP thread for package SE1000CD with thread handle 0000000000004450 and thread ID 8332 ended. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:05 AM 19300 (0x4B64) No DMP found.. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:10 AM 12828 (0x321C) Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:10 AM 12828 (0x321C) All DP threads have completed for package SE1000CD processing thread. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:10 AM 19300 (0x4B64) Package SE1000CD does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:11 AM 19300 (0x4B64) The package and/or program properties for package SE1000CD have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:11 AM 19300 (0x4B64) CDistributionSrcSQL::UpdateAvailableVersion PackageID=SE1000CD, Version=9, Status=2301 SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:11 AM 19300 (0x4B64) StoredPkgVersion (9) of package SE1000CD. StoredPkgVersion in database is 9. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:11 AM 19300 (0x4B64) SourceVersion (9) of package SE1000CD. SourceVersion in database is 9. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:11 AM 19300 (0x4B64) STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=19300 GMTDATE=Wed Nov 09 16:50:11.422 2016 ISTR0="SE - EN - Windows 10 Enterprise (Test)" ISTR1="SE1000CD" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SE1000CD" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:11 AM 19300 (0x4B64) Exiting package processing thread for package SE1000CD. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:11 AM 19300 (0x4B64) Currently using 0 out of 3 allowed package processing threads. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:16 AM 12828 (0x321C) Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:16 AM 12828 (0x321C) Created policy provider trigger for ID 4 SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:35 AM 9132 (0x23AC) Adding package 'SE100003' to package processing queue. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:40 AM 12828 (0x321C) Adding package 'SE100004' to package processing queue. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:40 AM 12828 (0x321C) Adding package 'SE100126' to package processing queue. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:40 AM 12828 (0x321C) Adding package 'SE100127' to package processing queue. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:40 AM 12828 (0x321C) Currently using 0 out of 3 allowed package processing threads. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:40 AM 12828 (0x321C) Started package processing thread for package 'SE100003', thread ID = 0x890 (2192) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:41 AM 12828 (0x321C) Started package processing thread for package 'SE100004', thread ID = 0x3604 (13828) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:41 AM 12828 (0x321C) Started package processing thread for package 'SE100126', thread ID = 0x2A50 (10832) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 12828 (0x321C) Used all 3 allowed processing threads, won't process any more packages. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 12828 (0x321C) Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 12828 (0x321C) STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=13828 GMTDATE=Wed Nov 09 16:50:42.037 2016 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="SE100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SE100004" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=2192 GMTDATE=Wed Nov 09 16:50:42.039 2016 ISTR0="Configuration Manager Client Package" ISTR1="SE100003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SE100003" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=10832 GMTDATE=Wed Nov 09 16:50:42.043 2016 ISTR0="Configuration Manager Client Piloting Package" ISTR1="SE100126" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SE100126" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) Processing package SE100003 (SourceVersion:8;StoredVersion:8) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) No action specified for the package SE100003, however there may be package server changes for this package. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) Processing package SE100126 (SourceVersion:1;StoredVersion:1) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) No action specified for the package SE100126, however there may be package server changes for this package. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) All DP threads have completed for package SE100003 processing thread. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) All DP threads have completed for package SE100126 processing thread. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) Processing package SE100004 (SourceVersion:7;StoredVersion:7) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) No action specified for the package SE100004, however there may be package server changes for this package. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) All DP threads have completed for package SE100004 processing thread. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) Package SE100126 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) The package and/or program properties for package SE100126 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) CDistributionSrcSQL::UpdateAvailableVersion PackageID=SE100126, Version=1, Status=2301 SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) Package SE100003 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) The package and/or program properties for package SE100003 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) CDistributionSrcSQL::UpdateAvailableVersion PackageID=SE100003, Version=8, Status=2301 SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) Package SE100004 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) The package and/or program properties for package SE100004 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) CDistributionSrcSQL::UpdateAvailableVersion PackageID=SE100004, Version=7, Status=2301 SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) StoredPkgVersion (1) of package SE100126. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) SourceVersion (1) of package SE100126. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) StoredPkgVersion (8) of package SE100003. StoredPkgVersion in database is 8. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) SourceVersion (8) of package SE100003. SourceVersion in database is 8. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=10832 GMTDATE=Wed Nov 09 16:50:42.707 2016 ISTR0="Configuration Manager Client Piloting Package" ISTR1="SE100126" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SE100126" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) StoredPkgVersion (7) of package SE100004. StoredPkgVersion in database is 7. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) SourceVersion (7) of package SE100004. SourceVersion in database is 7. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=2192 GMTDATE=Wed Nov 09 16:50:42.731 2016 ISTR0="Configuration Manager Client Package" ISTR1="SE100003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SE100003" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) Exiting package processing thread for package SE100003. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 2192 (0x0890) STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=13828 GMTDATE=Wed Nov 09 16:50:42.759 2016 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="SE100004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SE100004" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) Exiting package processing thread for package SE100004. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 13828 (0x3604) Exiting package processing thread for package SE100126. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:42 AM 10832 (0x2A50) Currently using 0 out of 3 allowed package processing threads. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:47 AM 12828 (0x321C) Started package processing thread for package 'SE100127', thread ID = 0xED0 (3792) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:47 AM 12828 (0x321C) Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:47 AM 12828 (0x321C) STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SESCCM.int.sweet.com SITE=SE1 PID=13840 TID=3792 GMTDATE=Wed Nov 09 16:50:47.575 2016 ISTR0="Configuration Manager Client Piloting Upgrade Package" ISTR1="SE100127" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="SE100127" SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:47 AM 3792 (0x0ED0) Processing package SE100127 (SourceVersion:1;StoredVersion:1) SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:47 AM 3792 (0x0ED0) No action specified for the package SE100127, however there may be package server changes for this package. SMS_DISTRIBUTION_MANAGER 11/9/2016 11:50:47 AM 3792 (0x0ED0) All DP threa

Hi, We are currently running SCCM 1606, and have a mix of Win7 and Win10 images. The probleme is the updated WIM file is not being updated on the DP, there is no error message, it shows up updated time stamp, however the image is not updated and keeps the same size. I'm thinking to delete the current image from the DP then distributing the new one Have you ever seen that before?

Hello, We are currently running Windows Defender client version is 4.10.14393.0, however in Programs and Features it showes System Centre Endoint Protection 4.7.214.0. Please note that we are pushing the SCEP policies via sccm Here is the screen captures : Any ideas?

Hello, I'm wondering if there is a way to update the Windows 10 applications (downloaded from the Windows Store for Business) via SCCM ,to we can manage and distribute the updates like any regular software. Thanks,

Nevermind, the Win10 machines were part of another collection that has a maintenance window setup.

Hello, We are running SCCM CB (1511) and I'm trying to push an package more than 70 workstations ,it's a mix of Win7 and Win10 . The package installs fine on the Win7 machines but not on the WIn10 workstation, the Deployment Status shows that it's "Waiting for a Service Window" I checked the execmgr.log and it shows : Succesfully raised SoftDistWaitingForServiceWindowEvent event for program AirMedia execmgr 8/8/2016 6:14:25 PM 6196 (0x1834) Execution Request for advert SE1200A5 package SE100121 program AirMedia state change from Ready to WaitingServiceWindow execmgr 8/8/2016 6:14:25 PM 6196 (0x1834) Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="SE100121",ProgramID="AirMedia", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l execmgr 8/8/2016 6:14:25 PM 6196 (0x1834) CServiceWindowEventHandler::Execute - Received SERVICEWINDOWEVENT : START Event execmgr 8/9/2016 9:27:02 AM 4080 (0x0FF0) CServiceWindowEventHandler::Execute - Received SERVICEWINDOWEVENT : END Event execmgr 8/9/2016 9:27:02 AM 7060 (0x1B94) CExecutionRequestManager::OnServiceWindowEvent for START execmgr 8/9/2016 9:27:03 AM 4080 (0x0FF0) Auto Install is set to false. Do Nothing. execmgr 8/9/2016 9:27:03 AM 4080 (0x0FF0) Any idea what might be the issue ?

I can't do that, we're still using the Win 7 images. I actually changed the deployment settings to make it available to "Only Media and PXE" , i was on "Configuration namager clients, Media and PXE" before.

Hello, As mentionned in the title, when I install a win 10 image ,a software center notification pops up to advise that there is a software ready to be installed ,when i opened it it was the the WIndows 7 TS. Is there a way to disable it ? Thanks,

no clue ?

Hello, I'm building a Windows 10 image, so far everything is ok except that my TS won't push the Drivers to my Surface Pro 4. I don't have any error message ,It detects it as a tablet, and the task finishes successfully, but no drivers are installed. See below : The task sequence execution engine started the group (Apply Tablet Drivers). The task sequence execution engine successfully completed the action (Apply Driver Package) in the group (Apply Tablet Drivers) with exit code 0 Action output: ... 6.0 The operation completed successfully. Process completed with exit code 0 Dism successfully added drivers to the offline driver store. Successfully added "C:\_SMSTaskSequence\Packages\SE1000EF\77486B10-EC84-479D-BC68-8A9B73B08884" to the Windows driver store. Adding "C:\_SMSTaskSequence\Packages\SE1000EF\8D062E93-EBDF-426F-A326-F7B02AEF32CA" to Windows driver store. Setting %SystemRoot% to "C:\WINDOWS" GImage Version: 10.0.10586.0 The operation completed successfully. Process completedwith exit code 0 Dism successfully added drivers to the offline driver store. Successfully added "C:\_SMSTaskSequence\Packages\SE1000EF\8D062E93-EBDF-426F-A326-F7B02AEF32CA" to the Windows driver store. Successfully applied driver package "SE1000EF".ReleaseSource() for C:\_SMSTaskSequence\Packages\SE1000EF. reference count 1 for the source C:\_SMSTaskSequence\Packages\SE1000EF before releasing Released the resolved source C:\_SMSTaskSequence\Packages\SE1000EF Exiting with return code 0x00000000. The task sequence execution engine successfully completed the group (Apply Tablet Drivers). Any idea what could be the reason ?

Nevermind, the serialnumber was over 15 characters, hence Windows won't accept it.

Hi there, I'm trying to set the computername for a Surface Pro 4 based on the serialnumber. I added the variable to my CustomSetting file as follow : ComputerName=MTLSP%SerialNumber%, but my task sequence fails when it comes to assign the name. Am I missing something ? PS : we use the assettag variable for desktops|laptops and it works like a charm.

Hello, Our SUP is not syncing with WSUS, for the last few days. Here is the erro we are getting from the WCM.log System.Net.WebException: The request failed with HTTP status 401: Unauthorized.~~ at Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer(Object[] args)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.ConnectToWSUSServer(String ServerName, Boolean UseSSL, Int32 PortNumber) Any Idea ^

Thx

Hi There , We just upgraded our SCCM to the latest 1511 version, along with MDT 2013 Update 2. My OSD task sequences are working just fine as before, we didn`t need to update them. I want to create a new MDT Boot image for my future Windows 10 task sequences ,and wondering if I can get 2 boot images (the Old and new one ) I can choose from during the PXE boot. Thanks,

Hey Zeze, are you saying that my current MDT Boot Images have to be recreated ?will it affect my current OSD task sequences?

Hi Everybody, We're about to upgrade our SCCM to 1511, of course with Windows 10 ADK and MDT 2013 Update 2. I would like to know if : 1- We should redo the SCCM\MDT integration after the upgarde. 2- Will the OSD task sequences be affected by the update? should we update the CustomeSettings.ini, Unattend.xml ? Thanks,

Hello , I was reviewing our OSD task Sequences and noticed that some steps are duplicated, specially the once for the Disk Format and Partitions, the steps are set under the Initialization Group and duplicated under the Preinstall. (see attached screenshots) I did a quick search on internet but didn't find a similar template, I'm wondering if you have any idea why those steps were duplicated? is it a best practice to do it this way ? Thanks,

Hello, I'm running the query below to pull all the Google Chrome versions installed on our workstations, however i'm getting duplicates results as some workstations have 2 file versions . I was trying to filter the result by MAX SMS_G_System_SoftwareFile.ModifiedDate and Group by SMS_R_System.Nam, however the MAX function doesn`t work in WQL. select distinct SMS_R_System.Name, SMS_G_System_SoftwareFile.FileVersion, SMS_G_System_SoftwareFile.ModifiedDate from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FileName = "Chrome.exe" Any idea how to display the max date ? Thanks,

not sure which driver was causing the slowness in my case, however it went through after an hour or so.