SCCM Package not distributing

When Rebooting Is Not The Answer

So I had to delete a package off a distribution point and redistribute yesterday and ran into an issue where it would not distribute.  I continued to read my logs and noticed that the distmgr.log continually retried the package but never actually distributed it.  It just kept saying no action specified for package.  Well after a ton of research I came across a blog post detailing how resolve that.

First check your action and updatemask

This particular distribution point had an update mask and action totally different than any of the other servers.

snip_20180515141509

I then deleted that record.

Once I did that I was able to finally redistribute the content.

Thanks a bunch to Daniel Eyer’s blog.

http://www.danieleyer.com/blog/2012/07/19/sccm-keeps-processing-package/

View original post

Getting email alert when imaging is finished

When Rebooting Is Not The Answer

I wanted to get some details every time a machine was imaged for my own details.  Mostly for asset tracking purposes I set up the below script to run at the end of my task sequence.

It is really nice to get all this info.

PC imaged is PCname with Serial R9ZRLB8 and Make and Model LENOVO 23594LU.  Processor is Intel(R) Core(TM) i5-3230M CPU @ 2.60GHz.  Ram is 8.00 GB.  Operating System is Microsoft Windows 10 Pro 10.0.15063

I suppose this could also be modified so that the tech imaging the machine could also get the email.  Maybe basing it off of the machine’s OU.  Hopefully someone finds this useful but I have found it quite handy.  I have also finished a script to gather logs when the task sequence fails and send them to me but I am still testing that out and will save that for my next…

View original post 46 more words

Getting email alert and smsts log when imaging fails via PowerShell

When Rebooting Is Not The Answer

So in follow up to my last post I have been testing a script to look for the smsts log when the task sequence fails and send me an email with the smsts.log as attachment.

I set this up in my MDT task sequence under the gather logs and statestore on failure section so that way whenever the task sequence has an error I get the logs.

I have a nice array of locations of the smsts log and a foreach loop to look through them test if they exist using Test-Path cmdlet and attach them to my email.

Seems to work well from what I have seen so far.

View original post

OSD Pro Tip: How to stop your OSD task sequences from causing mass destruction

Colin Ford

There have been improvements over the years within SCCM to help prevent OSD admins from deploying career changing task sequences to entire environments and wiping out thousands systems. Namely, the ability to limit within the console which collections you are able to deploy an OSD task sequence to, based on the number of members of that collection. The introduction of this feature likely shows that this event was occurring probably way too often.

View original post 382 more words

Prevent users from logging After Task sequence reboot the machine

Prevent users from logging After Task sequence reboot the machine There could be some requirement that machine must be reboot during the task sequence execution, however, we do not allow the user to log in immediately as some other part of task sequence or other steps to be executed. To stop the user login after … Continue reading Prevent users from logging After Task sequence reboot the machine

No software updates available after ConfigMgr site upgrade

SCCMentor - Paul Winstanley

I helped out a good friend of mine recently when he reported that the All Software Updates node in the SCCM console reported ‘No items found’ after a site upgrade from 1710 to 1802.

SU1802-001.JPG

We attempted a few troubleshooting methods before hitting on the source of the problem and the smsprov.log provided the nugget of information that we could work from.

The following error occured:

Execute WQL =SELECT ci.* FROM SMS_SoftwareUpdate ci WHERE ci.CI_ID NOT IN ( SELECT CI_ID FROM SMS_CIAllCategories WHERE CategoryInstance_UniqueID=’UpdateClassification:3689bdc8-b205-4af4-8d4a-a63924c5e9d5′) AND ci.CI_ID NOT IN (SELECT CI_ID FROM SMS_CIAllCategories WHERE CategoryInstance_UniqueID=’Product:30eb551c-6288-4716-9a78-f300ec36d72b’) ORDER BY DateRevised DESC SMS Provider 23/04/2018 23:14:06 5900 (0x170C)
Execute SQL =select all ci.CI_ID,ci.LocaleID,ci.ApplicabilityCondition,ci.ArticleID,ci.BulletinID,ci.CI_ID,ci.CI_UniqueID,ci.CIType_ID,ci.CIVersion,ci.CMTag,ci.CMTagName,ci.ConfigurationFlags,ci.CreatedBy,ci.CustomSeverity,ci.CustomSeverityName,ci.DateCreated,ci.DateLastModified,ci.DatePosted,ci.DateRevised,ci.EffectiveDate,ci.EULAAccepted,ci.EULAExists,ci.EULASignoffDate,ci.EULASignoffUser,ci.IsUserCI,ci.InUse,ci.IsBroken,ci.IsBundle,ci.IsChild,ci.IsContentProvisioned,ci.IsDeployable,ci.IsDeployed,ci.IsEnabled,ci.IsExpired,ci.IsHidden,ci.IsLatest,ci.IsMetadataOnlyUpdate,ci.IsOfflineServiceable,ci.IsQuarantined,ci.IsSuperseded,ci.IsUserDefined,ci.LastModifiedBy,ci.LastStatusTime,ci.Description,ci.DisplayName,ci.CIInformativeURL,ci.LocaleID,ci.MaxExecutionTime,ci.ModelID,ci.ModelName,ci.NumMissing,ci.NumNotApplicable,ci.NumPresent,ci.NumTotal,ci.NumUnknown,ci.ObjectPath,ci.PercentCompliant,ci.PermittedUses,ci.PlatformType,ci.RequiresExclusiveHandling,ci.RevisionNumber,ci.SDMPackageVersion,ci.SedoObjectVersion,ci.Severity,ci.SeverityName,ci.SourceSite from fn_ListUpdateCIs(2057) AS ci where (ci.ModelName not in (select all Folder##Alias##810314.InstanceKey from vFolderMembers AS Folder##Alias##810314 where Folder##Alias##810314.ObjectTypeName = N’SMS_SoftwareUpdate’) AND (ci.CI_ID not in (select all SMS_CIAllCategories.CI_ID from fn_ListCICategoriesAll(2057) AS SMS_CIAllCategories where SMS_CIAllCategories.CategoryInstance_UniqueID = N’UpdateClassification:3689bdc8-b205-4af4-8d4a-a63924c5e9d5′) AND ci.CI_ID not in (select all SMS_CIAllCategories.CI_ID from…

View original post 269 more words

Syncing your Microsoft Store for Business apps with Intune

SCCMentor - Paul Winstanley

I recently published a guide on how to deploy a Store app via Intune to a Windows 10 device. I found the mechanism to get a valid Appstore URL a little messy to say the least and the Microsoft documentation didn’t add anything to assist. So how could we make life easier and what if we had a whole bunch of apps that we need to bring into Intune?

Thankfully, we can sync our Microsoft Store for Business (MSfB) apps with Intune (and other management tools) and make all your purchased applications available for assignment in minutes.

Conditions to consider

  • Intune must be the MDM authority within your organisation
  • You must have a MSfB account and this account cannot be changed post link.
  • Once the link is in place, apps purchased cannot be manually added or remove and must be synced.
  • Your devices must be Active Azure Directory or workplace joined…

View original post 397 more words

SCCM crashes before task sequence on usb boot media

When Rebooting Is Not The Answer

Ok, so just wanted to post this real quick post that might help someone since I had a lot of trouble finding the answer.  I couldn’t use pxe and needed to be able to boot at a location with usb bootable media.  So easy I’ll just create some.  Thing was I would have it reboot as soon as I would put in the password for the boot media.  No errors network showed connected which is a typical issue with drivers not being in your boot media.  So I continued to restart and study my smsts.log and came across the below.

Failed to run unattended because there is no mandatory deployment.

After thinking about it a while I remembered I had set it to allow unattended deployment.  Well it turns out if no deployments are deployed to the machine as required that option doesn’t let it choose a task sequence.  So just…

View original post 11 more words

Disable SCCM Automatic Client Remediation during Windows 10 In-Place Upgrades

Colin Ford

I ran into an issue the other day during a W10 1703 to 1709 in-place upgrade where the upgrade task sequence bombed after Windows setup had completed. The OS had upgraded successfully to 1709 and SetupDiag also reported all was well in that area, however the remainder of the task sequence never ran, not a single-step post the upgrade task, so the device was missing some post-setup customisations.

Analysis

Analysing the SCCM client logs on the local machine this is what I saw:

20/07/2018 09:20:xx AM – (execmgr.log) Windows 1709 upgrade TS started
20/07/2018 09:41:xx AM – (smsts.log) Windows 1709 upgrade Windows setup.exe completes and initiates reboot of system to complete upgrade
20/07/2018 09:59:xx AM – (ccmsetup.log) CCM setup starts a re-install of 1802 client, stopping CCMExec and un-registering components
20/07/2018 10:00:20 AM – (smsts.log) Windows 1709 upgrade starts task sequence initialization to resume upgrade process
20/07/2018 10:00:21 AM –…

View original post 221 more words