Jump to content

Search the Community

Showing results for tags 'Client Package'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 2 results

  1. Hi guys, I have come up with another issue that I have discovered and I have no Idea how this happen or how to resolve it. I actually have a case open with MSFT and it has been two days and they seem to be stuck on this. I notice that the Client Package that was created during the SCCM build is constantly updating. I have image of what i'm talking about below: I know the source version should not be that high and the client should not be updating constantly, seem to be every 4hrs or less its updating. What I have highlighted is the original package that was created during the SCCM build and the one below "SCCM 2012 Configuration Manager Client" is what I created manually which is working and not having a constant update. Thanks,
  2. Hey all, a week or so ago, I started removing old content from distribution points as part of a site clean up. I made a major mistake by not querying which packages are needed by task sequences. At some point, the number for the Configuration Manager Client Package and the Upgrade Package got changed from the default of XXX00003 and XXX00004 to something else and I didn't notice the name. I removed the packages from two DPs using PowerShell. Seeing they were missing, I attempted to redistribute. No luck. Not only do they not redistribute but every half hour or so they are 'successfully removed' from the two DPs: Distribution Manager successfully removed package "XXX0001F" from distribution point "["Display=\\DISTRIBUTIONPOINT\"]MSWNET:["SMS_SITE=WHQ"]\\DP.FQDN.LOCAL\". I've attempted to add 'client.acu' into the Hman Inbox, I've added a .txt file to the package source to make the package different so it would redistribute, and I've tried to force the distribution with PowerShell. No luck. Any ideas? I'm tempted to try this solution but wanted to get all of your thoughts first. Thanks! distmgr.log
  • Create New...