Contents
How to list all installed APPX packages with their display name?
Remember that you asked exactly ” List all installed APPX packages, along with their display name”. Many programs like “Clock” are part of the OS and not displayed as APPX packages. You can probably find a WMI class that can return these items. You can also see that “Alarms & Clocks” is installed as APPX package.
What does find-package do in PackageManagement?
Forces the command to run without asking for user confirmation. Indicates that Find-Package forces PackageManagement to automatically install the package provider. Specifies the headers for the package. Indicates that this cmdlet includes package dependencies in the results. Specifies whether Find-Package should find all packages within a category.
Are there any APPX packages installed by MSI?
Programs installed by MSI and other methods are no APPX packages. @jrv Your script fails to expose commonly installed apps such as Alarms & Clocks, Paint 3D, Calculator, Camera, Maps, or Snip & Sketch. Already, 3rd-party utilities can easily collect this information, hence it must be possible.
How to find the latest version of a package?
This command finds the newest version of a package from a specified package source. If a package source isn’t provided, Find-Package searches each installed package provider and its package sources. Use Get-PackageSource to get the source name.
How to get the SSIS package name, job description?
[optional but nice to have] SSIS Job agent description. I’m able to pull all 3 of these pieces of information with no problems using the following tables: msdb.dbo.sysjobs gives me the Job name and Job description. msdb.dbo.sysssispackages gives me the SSIS Package name.
How to get the folder path of a package?
— Get the folder path of the package that a job points to. This brings it all together. Thanks for contributing an answer to Stack Overflow! Please be sure to answer the question. Provide details and share your research! But avoid … Asking for help, clarification, or responding to other answers.
Where is the packageid stored in SQL Server?
Thanks! This appears to be a glaring hole by Microsoft – it would be much nicer if the PackageId were stored in the msdb.dbo.sysjobsteps table, instead of having to parse the information from the Command column. As the OP correctly pointed out, this can be problematic when package names are the same.