• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 113
  • Last Modified:

SCCM updating Application deployment

In SCCM I created an application rather than a package for deploying Office. I have a change to an XML file for the deployment. I copied to my source directory and need to update my Distribution Point (Only have one). If I had created a Package, then I could just highlight, right click and choose "update Distribution Points". Seeing applications don't have that, I tried the following:

Update-CMDistributionPoint -ApplicationName "Microsoft Office Professional Plus 2016" -DeploymentTypeName "Deploying Office 2016"

To get there, I ran
Get-Wmiobject -Namespace "root\SMS\Site_FCB" -Class SMS_Application
and for -application name I used
LocalizedDisplayName: Microsoft Office Professional Plus 2016

for DeploymentTyeName I used
LocalizedDescription : Deploying Office 2016

However I get the following error:

PS FCB:\>Update-CMDistributionPoint -ApplicationName "Microsoft Office Professional Plus 2016" -DeploymentTypeName "Dep
oying Office 2016"
At line:1 char:1
 Update-CMDistributionPoint -ApplicationName "Microsoft Office Professional Plus  ...
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   + CategoryInfo          : InvalidArgument: (Microsoft.Confi...ionPointCommand:UpdateDistributionPointCommand) [Upd
  ate-CMDistributionPoint], ArgumentException
   + FullyQualifiedErrorId : ArgumentException,Microsoft.ConfigurationManagement.Cmdlets.Osd.Commands.UpdateDistribut
  ionPointCommand

am I using the wrong fields?
0
fcbc
Asked:
fcbc
  • 3
  • 3
1 Solution
 
Mike TLeading EngineerCommented:
Hi,

That looks fine to me, as per https://technet.microsoft.com/en-us/library/jj850071(v=sc.20).aspx.
You need to be careful/aware that some cmdlets just don't work mind. I could not get creating ISOs to work no matter what I did until that is I got the latest version. This is entirely a standalone update for PowerShell CM, not an upgrade.

The latest version is 5.0.8373.1189, which is for the 1604 release

PowerShell cmdlet library for ConfigMgr

Mike
0
 
fcbcAuthor Commented:
There IS a gui option -
   Software Library -> Applications -> Highlight Application -> Bottom window choose deployment types -> right click -> update complete

(Thanks Microsoft tech support)
0
 
Mike TLeading EngineerCommented:
I thought this was a PowerShell question, rather than "where's the update button". My answer was specifically how to get the PowerShell cmdlet to work. I doubt the OP tried it but can't tell.
0
[Webinar] Improve your customer journey

A positive customer journey is important in attracting and retaining business. To improve this experience, you can use Google Maps APIs to increase checkout conversions, boost user engagement, and optimize order fulfillment. Learn how in this webinar presented by Dito.

 
fcbcAuthor Commented:
I did update the poweshell commands to the latest version, and the content of the error changed, a little more descriptive, but it still error-ed out. The original question was how to update the contents of the package. I tried Powershell because I could not find the way to update. But the purpose of the question was how to update.
0
 
Mike TLeading EngineerCommented:
Fair enough - I missed that bit amongst all the PowerShell. Wish I had noticed as I could have saved you the MS call.
0
 
fcbcAuthor Commented:
Answer provided by MS tech support
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now