Jump to content


Search the Community

Showing results for tags 'Deployment Types'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • 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

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. Is there a way to create multiple Deployment Types under one application. I am using Add-CMScriptDeploymentType and get an error on the second one. Add-CMScriptDeploymentType : ConfigMgr Error Object: instance of SMS_ExtendedStatus { Description = "The digest is not valid"; ErrorCode = 1078462235; File = "..\\sspconfigurationitem.cpp"; Line = 1980; Operation = "PutInstance"; ParameterInfo = ""; ProviderName = "ExtnProv"; SQLMessage = "[42000][3998][Microsoft] [SQL Server]Uncommittable transaction is detected at the end of the batch. The transaction is rolled back."; SQLSeverity = 16; SQLStatus = 3998; StatusCode = 2147749889; }; At C:\Install\CreateTKA.ps1:252 char:11 + Add-CMScriptDeploymentType -ApplicationName $ApplicationNam ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (Microsoft.Confi...mentTypeCommand:AddScriptDeploymentTypeCommand) [Add-CM ScriptDeploymentType], WqlQueryException + FullyQualifiedErrorId : UnhandledException,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.AddScriptDe ploymentTypeCommand
  2. Hi, I'm in the process of deploying Windows 10 (x64 Enterprise Build 1809) at a customer site using Configuration Manager Current Branch (1806 + Hotfix). Office 365 Click-to-Run is a Tier 1 application that I am installing during deployment of the OS to the endpoint machine. In order to ensure the O365 C2R content is the latest "Semi-Annual Channel" version (client is bound by regulation to patch applications, so testing this with Office) I've setup the following: "Content" for the Application in CM is JUST setup.exe plus XML files for the install. Two XML files for install for two different locations (one of which is on at a low-speed WAN site). Each XML refers to source content in an open share on the Distribution Point servers - one of which is at the low-speed WAN site. Two deployment types in the Application - one for each XML. Setup a Scheduled Task on the Distribution Point servers to update the share (not the Application content) on a regular basis So my plan was then to use a "Requirement" on the application using a custom Global Condition that determines the Active Directory site (created using PowerShell). The idea then being that during deployment, the application installs using the latest available SAC version and administrators don't need to worry about the Application content being updated. And of course, the XML file then tells it to grab the content from the local site, which is highly connected. Works wonderfully well in Software Center in my testing. BUT, doesn't seem to work in OSD Task Sequence ☹️. If I am reading error logs right, it seems as though the PowerShell in the Global Condition is not being allowed to run (even when I set Execution Policy to "Bypass" earlier in the Task Sequence. So, perhaps I am making things more complex than they should be. Simplest thing to do would be to create two separate applications using the same method (i.e. not just two deployment types) and use a Dynamic Variable in the Task Sequence that installs one or the other dependent upon gateway IP. However, throwing it out there for some thoughts on how I could do this using the multiple deployment methods on the single app. Thanks, Matt
  3. Hi All, I have create a Boolean global condition which checks if Outlook.exe is running. I then used this as a requirement for an application so that it would install the application only if outlook was closed. I tested this by making a required deployment to a test machine this failed and did not retry the install once I closed outlook below is the error I received. Category: Evaluation Failed Error Description: The handle is invalid Is there any was I can have this global condition as a requirement so that when the user closed outlook the application will install Thanks
  4. OK, so here's my scenario. I've created two Applications each of which have more than 1 Application Type. When I created and tested them both with a deployment to a collection and during OSD with PXE they work fine. What is "special" I think about them though is that I have made the dependencies for the Application Types are in the same Application. When I try to run the Task Sequence on a Stand-Alone USB drive is NOT connected to the network these two Applications do not install. If I run the same Task Sequence on the same Stand-Alone USB drive the TS fails. So in case I'm not clear on how the Application\Deployment Type is set up let me try and diagram it Application 1 -Deployment Type 1 - Patch .0.5 -Deployment Type 2 - Patch .1 -Deployment Type 3 - MSI v1 The application is called Patch .05 is called and has a dependency of Patch .1 Patch .1 has a dependency of the MSI The MSI is installed, then Patch .1 is installed, then Patch .05 is installed resulting in a fully patched version of the original MSI v1.1.5 Application 2 is pretty much the same logic as Application 1, just with only 2 Deployment Types. My question is, why will these run correctly when the client machine is connected to the network, but when run on a Stand-Alone USB and not connected they fail? I have other applications that call other applications in the same TS and those work fine, so it seems that SCCM doesn't like the dependency being in the SAME application. If I have to I will break them out into separate applications, but that seem pretty silly! I can provide SMSTS and AppEnforcement logs or whatever logs I can get from the client if needed.
×
×
  • Create New...