Jump to content


Search the Community

Showing results for tags 'package deployment'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • 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
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests

Found 3 results

  1. In SCCM 2012 R2 I have a Package Deployment (Could not get this particular deployment to work as an Application Deployment). Its an exe with switches to run quietly and no restart. I've noticed when I monitor this deployments node that the machines that already have the program installed end up with a 10006 message id and description of 60004 under the error tab. Can I do something to have them instead show up as success, compliant?
  2. Hello everyone! I've wrote very simple script to shutdown Workstations. Then I've created the collection for certain OUs in domain and simply scheduled to deploy this script to collection as package at 22:00 . I've realized my mistake when some of these workstations rebooted at morning (they were powered down already). So, what is the best way to do it right with SCCM? Should I schedule, i.e. the distribution of this package daily at 21:50 with deadline at 21:55 and create maintenance window for collection from 22:00 to 22:05? Will this work or there is more easier way? I've found some articles about maintenance windows, but can not realize the clear algorithm for myself. Thank you for your attention.
  3. I'm trying to import and distribute a captured wim file but it fails when creating a snapshot. The wim file is on a network share that all the site systems have access to(verified). The wim is 145GB(I know, it is an absurd size) The primary site only has 50GB free between 2 drives. But since the content isn't being distributed to that server I don't think the space is an issue. Even if it creates a hash on that server it should be fill up any one of those drives. The DP I'm trying to distribute the wim has one drive that has 429GB free and another drive that has 1.8TB free. Quota's aren't enabled on the distribution point. I have tested with the default windows wim which is roughly around 3GB and that distributes fine to all the DPs. Here are the log entries from distmgr.log from the primary site: DPConnection::Connect: For $(PrimarySite), logged-on as $(SMSserviceAccount) SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:23 AM 10072 (0x2758) DPConnection::Disconnect: For $(PrimarySite), reverted to SYSTEM context SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:23 AM 10072 (0x2758) Failed to find space for 145000776127 bytes. SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) CFileLibrary::FindAvailableLibraryPath failed; 0x8007050f SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) CFileLibrary::AddFile failed; 0x8007050f SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) CContentDefinition::AddFile failed; 0x8007050f SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) Failed to add the file. Please check if this file exists. SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) SnapshotPackage() failed. Error = 0x8007050F SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=$(PrimarySite) SITE=$(Site) PID=4524 TID=10072 GMTDATE=Wed Jul 22 12:24:24.107 2015 ISTR0="$(share)\images\Win7\Lab\x64\Windows 7x64 Lab F2015R00.wim" ISTR1="Windows 7x64 Lab F2015R00" ISTR2="$(PackageID)" ISTR3="30" ISTR4="60" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="$(PackageID)" SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) CDistributionSrcSQL::UpdateAvailableVersion PackageID=$(PackageID), Version=1, Status=2302 SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=$(PrimarySite) SITE=$(Site) PID=4524 TID=10072 GMTDATE=Wed Jul 22 12:24:24.248 2015 ISTR0="Windows 7x64 Lab F2015R00" ISTR1="$(PackageID)" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="$(PackageID)" SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) Failed to process package $(PackageID) after 40 retries, will retry 60 more times SMS_DISTRIBUTION_MANAGER 7/22/2015 8:24:24 AM 10072 (0x2758) Any help would be greatly appreciated. Thanks
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.