├── MDTApplicationTools.psd1
├── Tests
    └── Module.Tests.ps1
├── Media
    ├── ModuleInstallation.png
    └── PSGalleryInstallation.png
├── appveyor.yml
├── docs
    ├── Import-MDTModule.md
    ├── Get-MDTDrive.md
    ├── Set-MDTDrive.md
    ├── Find-MDTApplicationContent.md
    ├── Get-MDTApplicationSupportedPlatform.md
    ├── Get-MDTApplication.md
    ├── Get-MDTApplicationDependency.md
    ├── Rename-MDTApplication.md
    └── Set-MDTApplicationSupportedPlatform.md
├── LICENSE.md
├── README.md
├── MDTApplicationTools.format.ps1xml
├── MDTApplicationTools.psm1
└── en-US
    └── MDTApplicationTools-help.xml


/MDTApplicationTools.psd1:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/JohnForet/MDTApplicationTools/HEAD/MDTApplicationTools.psd1


--------------------------------------------------------------------------------
/Tests/Module.Tests.ps1:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/JohnForet/MDTApplicationTools/HEAD/Tests/Module.Tests.ps1


--------------------------------------------------------------------------------
/Media/ModuleInstallation.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/JohnForet/MDTApplicationTools/HEAD/Media/ModuleInstallation.png


--------------------------------------------------------------------------------
/Media/PSGalleryInstallation.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/JohnForet/MDTApplicationTools/HEAD/Media/PSGalleryInstallation.png


--------------------------------------------------------------------------------
/appveyor.yml:
--------------------------------------------------------------------------------
1 | build: false
2 | 
3 | install:
4 |   - cinst pester
5 | 
6 | test_script:
7 |   - ps: Invoke-Pester -EnableExit
8 | 


--------------------------------------------------------------------------------
/docs/Import-MDTModule.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | external help file: MDTApplicationTools-help.xml
 3 | online version: 
 4 | schema: 2.0.0
 5 | ---
 6 | 
 7 | # Import-MDTModule
 8 | ## SYNOPSIS
 9 | {{Fill in the Synopsis}}
10 | 
11 | ## SYNTAX
12 | 
13 | ```
14 | Import-MDTModule
15 | ```
16 | 
17 | ## DESCRIPTION
18 | {{Fill in the Description}}
19 | 
20 | ## EXAMPLES
21 | 
22 | ### Example 1
23 | ```
24 | PS C:\> {{ Add example code here }}
25 | ```
26 | 
27 | {{ Add example description here }}
28 | 
29 | ## PARAMETERS
30 | 
31 | ## INPUTS
32 | 
33 | ### None
34 | 
35 | 
36 | ## OUTPUTS
37 | 
38 | ### System.Object
39 | 
40 | ## NOTES
41 | 
42 | ## RELATED LINKS
43 | 
44 | 


--------------------------------------------------------------------------------
/docs/Get-MDTDrive.md:
--------------------------------------------------------------------------------
 1 | ---
 2 | external help file: MDTApplicationTools-help.xml
 3 | online version: 
 4 | schema: 2.0.0
 5 | ---
 6 | 
 7 | # Get-MDTDrive
 8 | ## SYNOPSIS
 9 | {{Fill in the Synopsis}}
10 | 
11 | ## SYNTAX
12 | 
13 | ```
14 | Get-MDTDrive [-Name] <Object>
15 | ```
16 | 
17 | ## DESCRIPTION
18 | {{Fill in the Description}}
19 | 
20 | ## EXAMPLES
21 | 
22 | ### Example 1
23 | ```
24 | PS C:\> {{ Add example code here }}
25 | ```
26 | 
27 | {{ Add example description here }}
28 | 
29 | ## PARAMETERS
30 | 
31 | ### -Name
32 | {{Fill Name Description}}
33 | 
34 | ```yaml
35 | Type: Object
36 | Parameter Sets: (All)
37 | Aliases: 
38 | 
39 | Required: True
40 | Position: 0
41 | Default value: 
42 | Accept pipeline input: False
43 | Accept wildcard characters: False
44 | ```
45 | 
46 | ## INPUTS
47 | 
48 | ### None
49 | 
50 | 
51 | ## OUTPUTS
52 | 
53 | ### System.Object
54 | 
55 | ## NOTES
56 | 
57 | ## RELATED LINKS
58 | 
59 | 


--------------------------------------------------------------------------------
/LICENSE.md:
--------------------------------------------------------------------------------
 1 | The MIT License (MIT)
 2 | =====================
 3 | 
 4 | Copyright (c) 2016 John Foret
 5 | 
 6 | Permission is hereby granted, free of charge, to any person obtaining a copy
 7 | of this software and associated documentation files (the "Software"), to deal
 8 | in the Software without restriction, including without limitation the rights
 9 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
10 | copies of the Software, and to permit persons to whom the Software is
11 | furnished to do so, subject to the following conditions:
12 | 
13 | The above copyright notice and this permission notice shall be included in all
14 | copies or substantial portions of the Software.
15 | 
16 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
17 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
18 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
19 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
20 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
21 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
22 | SOFTWARE.
23 | 


--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
 1 | # MDT Application Tools
 2 | A PowerShell module to provide enhanced functionality around the querying and manipulation of MDT applications.
 3 | 
 4 | [![Build status](https://ci.appveyor.com/api/projects/status/github/JohnForet/mdtapplicationtools?branch=master&svg=true)](https://ci.appveyor.com/project/JohnForet/mdtapplicationtools/branch/master)
 5 | 
 6 | ### Motivation
 7 | This module was created to provide some advanced functionality around the manipulation of MDT applications. Some of the Functions included are:
 8 | 
 9 | * Get-MDTApplication
10 |   * Retrieves MDT applications, either by name/guid, or just all of them.
11 | * Get-MDTApplicationDependency
12 |   * Retrieves either the parent or child dependencies of an MDT application. Can either return one depth, or can recurse the entire depth of the dependency tree
13 | * Get-MDTApplicationSupportedPlatform
14 |   * Queries MDT applications to see if they have the SupportedPlatform attribute set.
15 | * Set-MDTApplicationSupportedPlatform
16 |   * Sets the SupportedPlatform attribute on MDT applications
17 | * Find-MDTApplicationContent
18 |   * Searches through either the installcmd attribute or the install scripts themselves of all the MDT applications in a share for the specified string(i.e "pause", "powershell.exe", "C:\Program Files (x86)", etc.)
19 | * Rename-MDTApplication
20 |   * Renames MDT applications, optionally renaming their source directory in MDT as well.
21 | 
22 | ### Prerequisites
23 | 
24 | In order to run this module, you'll need to at least have the **Microsoft Deployment Toolkit** installed. As of this writing the module has only been tested with **MDT 2013 Update 1** and **Update 2**, but may possibly work with earlier iterations of the toolkit. This module was developed on **Windows 10** using **PowerShell 5**. It will probably work just fine with earlier versions of Windows and PowerShell, but bear in mind those scenarios are untested.
25 | 
26 | ###### MDT 2013 Update 1
27 | http://www.microsoft.com/en-us/download/details.aspx?id=48595
28 | 
29 | ###### MDT 2013 Update 2
30 | http://www.microsoft.com/en-us/download/details.aspx?id=50407
31 | 
32 | 
33 | ### Installing
34 | 
35 | In order to install this module, just copy the module folder `MDTApplicationTools` (in order for the module to be imported it's contents must be in this folder) to one the folders in `$env:PSModulePath`.
36 | Here's an example of what it should look like:
37 | 
38 | ![Module Installation Directory](Media/ModuleInstallation.png)
39 | 
40 | If you have PowerShell 5, you can also install it directly from the PowerShell Gallery.
41 | 
42 | ![PowerShell Gallery Installation](Media/PSGalleryInstallation.png)
43 | 
44 | ### Updating Help
45 | The help in this module is maintained with [platyPS](https://github.com/PowerShell/platyPS), which is a powershell module that lets you generate external powershell help files from easily maintained markdown file(s). In order to update the help in this module, simply edit the markdown file for the function in `.\docs` in the module's root directory, afterwards running `New-ExternalHelp .\docs -OutputPath en-US\ -Force`. This command will update the external help file for the module, `.\en-US\MDTApplicationTools-help.xml`.
46 | 
47 | ### Authors
48 | 
49 | * **John Foret** - *Initial work* - [JohnForet](https://github.com/JohnForet)
50 | 
51 | ### License
52 | 
53 | This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details
54 | 
55 | ### Acknowledgments
56 | 
57 | Hat's off to Don Jones and Jeffrey Hicks *Learn Powershell Toolmaking in a Month of Lunches*, which helped me write this module. Also, kudos to Johan Arwidmark and Mikael Nystrom, both for the book *Deployment Fundamentals Vol 4: Deploying Windows 8 and Office 2013 Using MDT 2012 Update 1*, and for the support they provide to the windows deployment community.
58 | 


--------------------------------------------------------------------------------
/docs/Set-MDTDrive.md:
--------------------------------------------------------------------------------
  1 | ---
  2 | external help file: MDTApplicationTools-help.xml
  3 | online version: https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Set-MDTDrive.md
  4 | schema: 2.0.0
  5 | ---
  6 | 
  7 | # Set-MDTDrive
  8 | ## SYNOPSIS
  9 | Creates an MDT drive.
 10 | 
 11 | ## SYNTAX
 12 | 
 13 | ```
 14 | Set-MDTDrive [-Name] <Object> [-Path] <Object> [-Force] [-WhatIf] [-Confirm]
 15 | ```
 16 | 
 17 | ## DESCRIPTION
 18 | The Set-MDTDrive function creates an MDT drive using the MDTProvider for powershell. This function is actually just a wrapper for New-PSDrive with the MDTProvider. For example this:
 19 | 
 20 | `PS C:\>Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$"`
 21 | 
 22 |  is actually the same command as this:
 23 | 
 24 | `PS C:\>New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\\FILESERVER\MDTProduction$" -NetworkPath "\\FILESERVER\MDTProduction$" -Scope Global`
 25 | 
 26 | ## EXAMPLES
 27 | 
 28 | ### Example 1: Create an MDT drive
 29 | ```
 30 | PS C:\> Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$"
 31 | ```
 32 | 
 33 | Creates an MDT Drive with a name of `MDTProduction` and a path of `"\\FILESERVER\MDTProduction$"`
 34 | ### Example 2: Create an MDT drive, overwriting previous drives
 35 | ```
 36 | PS C:\> Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$" -Force
 37 | ```
 38 | 
 39 | Creates an MDT Drive with a name of `MDTProduction` and a path of `"\\FILESERVER\MDTProduction$"`, overwriting any previous drives with the name `MDTProduction`.
 40 | ### Example 3: Shows what will happen if the command is run
 41 | ```
 42 | PS C:\> Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$" -WhatIf
 43 | ```
 44 | 
 45 | Shows what will happen if you try to create an MDT Drive with a name of `MDTProduction` and a path of `"\\FILESERVER\MDTProduction$"`
 46 | ## PARAMETERS
 47 | 
 48 | ### -Confirm
 49 | The confirm preference. If left alone, will just let the command run as normal. If $true is specified, will prompt you before creating the drive.
 50 | 
 51 | 
 52 | ```yaml
 53 | Type: SwitchParameter
 54 | Parameter Sets: (All)
 55 | Aliases: cf
 56 | 
 57 | Required: False
 58 | Position: Named
 59 | Default value:
 60 | Accept pipeline input: False
 61 | Accept wildcard characters: False
 62 | ```
 63 | 
 64 | ### -Force
 65 | If specified, will create MDT drive even if one with same name already exists(in case one wants to create a drive of the same name with a different path)
 66 | 
 67 | ```yaml
 68 | Type: SwitchParameter
 69 | Parameter Sets: (All)
 70 | Aliases:
 71 | 
 72 | Required: False
 73 | Position: Named
 74 | Default value:
 75 | Accept pipeline input: False
 76 | Accept wildcard characters: False
 77 | ```
 78 | 
 79 | ### -Name
 80 | Specifies what name you would like to give to the drive you want to create. This is the share name you'll reference later on when querying the share.
 81 | 
 82 | ```yaml
 83 | Type: Object
 84 | Parameter Sets: (All)
 85 | Aliases:
 86 | 
 87 | Required: True
 88 | Position: 0
 89 | Default value:
 90 | Accept pipeline input: False
 91 | Accept wildcard characters: False
 92 | ```
 93 | 
 94 | ### -Path
 95 | {{Fill Path Description}}
 96 | 
 97 | ```yaml
 98 | Type: Object
 99 | Parameter Sets: (All)
100 | Aliases:
101 | 
102 | Required: True
103 | Position: 1
104 | Default value:
105 | Accept pipeline input: False
106 | Accept wildcard characters: False
107 | ```
108 | 
109 | ### -WhatIf
110 | If specified, will output what changes the command will make without making them.
111 | 
112 | ```yaml
113 | Type: SwitchParameter
114 | Parameter Sets: (All)
115 | Aliases: wi
116 | 
117 | Required: False
118 | Position: Named
119 | Default value:
120 | Accept pipeline input: False
121 | Accept wildcard characters: False
122 | ```
123 | 
124 | ## INPUTS
125 | 
126 | ### None
127 | 
128 | 
129 | ## OUTPUTS
130 | 
131 | ### System.Object
132 | 
133 | ## NOTES
134 | 
135 | ## RELATED LINKS
136 | 


--------------------------------------------------------------------------------
/docs/Find-MDTApplicationContent.md:
--------------------------------------------------------------------------------
  1 | ---
  2 | external help file: MDTApplicationTools-help.xml
  3 | online version: https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Find-MDTApplicationContent.md
  4 | schema: 2.0.0
  5 | ---
  6 | 
  7 | # Find-MDTApplicationContent
  8 | ## SYNOPSIS
  9 | Searches MDT shares for applications whose content contain specified text.
 10 | 
 11 | ## SYNTAX
 12 | 
 13 | ```
 14 | Find-MDTApplicationContent [-ShareName] <Object> [[-String] <Object>] [-ParseScript]
 15 | ```
 16 | 
 17 | ## DESCRIPTION
 18 | The Find-MDTApplicationContent function retrieves MDT applications from the specified MDT share that contain the string specified. It can query either just the CommandLine attribute of the application, or it can also query the install scripts themselves if the ParseScript switch is specified.
 19 | 
 20 | ## EXAMPLES
 21 | 
 22 | ### Example 1
 23 | ```
 24 | PS C:\> Find-MDTApplicationContent -ShareName MDTProduction -string "setup.exe /s"
 25 | ```
 26 | 
 27 | This command searches the MDT share MDTProduction, and returns any applications where the "CommandLine" attribute matches "setup.exe /s" exactly.
 28 | 
 29 | ### Example 2
 30 | ```
 31 | PS C:\> Find-MDTApplicationContent -ShareName MDTProduction -string *.bat*
 32 | ```
 33 | 
 34 | This command searches the MDT share MDTProduction, and returns any applications that call a .bat file in their "CommandLine" attribute
 35 | ### Example 3
 36 | ```
 37 | PS C:\> Find-MDTApplicationContent -ShareName MDTProduction -string "C:\Program Files\*" -ParseScript
 38 | ```
 39 | 
 40 | This command searches the MDT share MDTProduction, and returns any applications that call a .bat file in their "CommandLine" attribute
 41 | 
 42 | ## PARAMETERS
 43 | 
 44 | ### -ParseScript
 45 | **IF NOT** specified, the only part of the apps that are searched are the "CommandLine" attribute, which is the initial command that gets launched at install time to install the app(it can reference either an executable or an install script path). **IF** specified, the script will actually go through the applications working directory, and parse through any install scripts to see if they contain the specified string. It searches the following files:
 46 | 
 47 | ".bat",".cmd",".vbs",".wsf",".ps1",".psm1",".psd1"
 48 | 
 49 | ```yaml
 50 | Type: SwitchParameter
 51 | Parameter Sets: (All)
 52 | Aliases:
 53 | 
 54 | Required: False
 55 | Position: Named
 56 | Default value:
 57 | Accept pipeline input: False
 58 | Accept wildcard characters: False
 59 | ```
 60 | 
 61 | ### -ShareName
 62 | Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 63 | 
 64 | `PS C:\>New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\\FILESERVER\MDTProduction$" -NetworkPath "\\FILESERVER\MDTProduction$" -Scope Global`
 65 | 
 66 | or
 67 | 
 68 | `PS C:\>Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$"`
 69 | 
 70 | ```yaml
 71 | Type: Object
 72 | Parameter Sets: (All)
 73 | Aliases:
 74 | 
 75 | Required: True
 76 | Position: 0
 77 | Default value:
 78 | Accept pipeline input: False
 79 | Accept wildcard characters: False
 80 | ```
 81 | 
 82 | ### -String
 83 | Specifies the string to search for in MDT applications. If typed explicitly (i.e. "setup.exe /s"), it will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like \*powershell.exe\* would return all the applications that have powershell.exe in their commandline or install script(depending on whether the ParseScript parameter was used).
 84 | 
 85 | ```yaml
 86 | Type: Object
 87 | Parameter Sets: (All)
 88 | Aliases:
 89 | 
 90 | Required: False
 91 | Position: 1
 92 | Default value:
 93 | Accept pipeline input: False
 94 | Accept wildcard characters: True
 95 | ```
 96 | 
 97 | ## INPUTS
 98 | 
 99 | ### None
100 | 
101 | 
102 | ## OUTPUTS
103 | 
104 | ### System.Object
105 | 
106 | ## NOTES
107 | 
108 | ## RELATED LINKS
109 | 


--------------------------------------------------------------------------------
/docs/Get-MDTApplicationSupportedPlatform.md:
--------------------------------------------------------------------------------
  1 | ---
  2 | external help file: MDTApplicationTools-help.xml
  3 | online version: https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Get-MDTApplicationSupportedPlatform.md
  4 | schema: 2.0.0
  5 | ---
  6 | 
  7 | # Get-MDTApplicationSupportedPlatform
  8 | ## SYNOPSIS
  9 | Gets the SupportedPlatform attribute of or more MDT applications
 10 | 
 11 | ## SYNTAX
 12 | 
 13 | ### GUIDFilter
 14 | ```
 15 | Get-MDTApplicationSupportedPlatform [-ShareName <Object>] -GUID <Object> -SupportedPlatformSet <Object>
 16 | ```
 17 | 
 18 | ### NameFilter
 19 | ```
 20 | Get-MDTApplicationSupportedPlatform [-ShareName <Object>] -Name <Object> -SupportedPlatformSet <Object>
 21 | ```
 22 | 
 23 | ### NoFilter
 24 | ```
 25 | Get-MDTApplicationSupportedPlatform [-ShareName <Object>] -SupportedPlatformSet <Object>
 26 | ```
 27 | 
 28 | ## DESCRIPTION
 29 | The Get-MDTApplicationSupportedPlatform function can either return the SupportedPlatform attribute of a queried application(via the name or GUID) parameter, return it for all applications, or return just applications that have it set(or not).
 30 | 
 31 | ## EXAMPLES
 32 | 
 33 | ### Example 1: Get all applications where the SupportedPlatform attribute is set(to anything)
 34 | ```
 35 | PS C:\> Get-MDTApplicationSupportedPlatform -ShareName TESTSHARE -SupportedPlatformSet Yes
 36 | ```
 37 | 
 38 | Returns all applications where SupportedPlatform is set.
 39 | ### Example 2: Get all applications where the SupportedPlatform attribute is NOT set.
 40 | ```
 41 | PS C:\> Get-MDTApplicationSupportedPlatform -ShareName TESTSHARE -SupportedPlatformSet No
 42 | ```
 43 | 
 44 | Returns all applications where SupportedPlatform is NOT set.
 45 | ### Example 3: Get SupportedPlatform attribute of specific application.
 46 | ```
 47 | PS C:\> Get-MDTApplicationSupportedPlatform -ShareName TESTSHARE -Name "Install - Google Chrome -x64" -SupportedPlatformSet All
 48 | ```
 49 | 
 50 | Returns the queried application along with it's SupportedPlatform attribute
 51 | 
 52 | ## PARAMETERS
 53 | 
 54 | ### -GUID
 55 | Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 56 | 
 57 | ```yaml
 58 | Type: Object
 59 | Parameter Sets: GUIDFilter
 60 | Aliases:
 61 | 
 62 | Required: True
 63 | Position: Named
 64 | Default value:
 65 | Accept pipeline input: True (ByPropertyName)
 66 | Accept wildcard characters: True
 67 | ```
 68 | 
 69 | ### -Name
 70 | Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\*adobe\*" would return all the applications that have adobe in their name.
 71 | 
 72 | ```yaml
 73 | Type: Object
 74 | Parameter Sets: NameFilter
 75 | Aliases:
 76 | 
 77 | Required: True
 78 | Position: Named
 79 | Default value:
 80 | Accept pipeline input: True (ByPropertyName)
 81 | Accept wildcard characters: True
 82 | ```
 83 | 
 84 | ### -ShareName
 85 | Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 86 | 
 87 | `PS C:\>New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\\FILESERVER\MDTProduction$" -NetworkPath "\\FILESERVER\MDTProduction$" -Scope Global`
 88 | 
 89 | or
 90 | 
 91 | `PS C:\>Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$"`
 92 | 
 93 | ```yaml
 94 | Type: Object
 95 | Parameter Sets: (All)
 96 | Aliases:
 97 | 
 98 | Required: False
 99 | Position: Named
100 | Default value:
101 | Accept pipeline input: False
102 | Accept wildcard characters: False
103 | ```
104 | 
105 | ### -SupportedPlatformSet
106 | Specifies in the query whether to return just Applications that have it set(Yes), just Applications that do NOT have it set(No), or to return Applications that both states(All).
107 | 
108 | ```yaml
109 | Type: Object
110 | Parameter Sets: (All)
111 | Aliases:
112 | Accepted values: Yes, No, All
113 | 
114 | Required: True
115 | Position: Named
116 | Default value: All
117 | Accept pipeline input: False
118 | Accept wildcard characters: False
119 | ```
120 | 
121 | ## INPUTS
122 | 
123 | ### System.Object
124 | 
125 | 
126 | ## OUTPUTS
127 | 
128 | ### System.Object
129 | 
130 | ## NOTES
131 | 
132 | ## RELATED LINKS
133 | 


--------------------------------------------------------------------------------
/docs/Get-MDTApplication.md:
--------------------------------------------------------------------------------
  1 | ---
  2 | external help file: MDTApplicationTools-help.xml
  3 | online version: https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Get-MDTApplication.md
  4 | schema: 2.0.0
  5 | ---
  6 | 
  7 | # Get-MDTApplication
  8 | ## SYNOPSIS
  9 | Gets one or more MDT applications
 10 | 
 11 | ## SYNTAX
 12 | 
 13 | ### GUIDFilter
 14 | ```
 15 | Get-MDTApplication [-ShareName <Object>] [-Location <Object>] -GUID <Object>
 16 | ```
 17 | 
 18 | ### NameFilter
 19 | ```
 20 | Get-MDTApplication [-ShareName <Object>] [-Location <Object>] -Name <Object>
 21 | ```
 22 | 
 23 | ### NoFilter
 24 | ```
 25 | Get-MDTApplication [-ShareName <Object>] [-Location <Object>]
 26 | ```
 27 | 
 28 | ## DESCRIPTION
 29 | The Get-MDTApplication function retrieves MDT applications from the specified MDT share. It can be used to either retrieve all the applications at once, or just by the applications Name or GUID of the wanted application.
 30 | 
 31 | ## EXAMPLES
 32 | 
 33 | ### Example 1: Get all applications
 34 | ```
 35 | PS C:\>Get-MDTApplication -ShareName MDTProduction
 36 | ```
 37 | 
 38 | This command returns all applications from the MDT share.
 39 | ### Example 2: Get only applications in a certain directory
 40 | ```
 41 | PS C:\>Get-MDTApplication -ShareName MDTProduction -Location "APPBUNDLES"
 42 | ```
 43 | 
 44 | This command returns all applications from the MDT share that are located in a folder called "APPBUNDLES" (located under the Applications root folder).
 45 | ### Example 3: Get application by name
 46 | ```
 47 | PS C:\>Get-MDTApplication -ShareName MDTProduction -Name "Install - Java 8 - x64"
 48 | ```
 49 | 
 50 | This command returns the application with the name "Install - Java 8 - x64" from the MDT share.
 51 | ### Example 4: Use wildcards to search for applications
 52 | ```
 53 | PS C:\>Get-MDTApplication -ShareName MDTProduction -Name *java*
 54 | ```
 55 | 
 56 | This command returns any applications that have the word java somewhere in their name from the MDT share.
 57 | ### Example 5: Get application by GUID
 58 | ```
 59 | PS C:\>Get-MDTApplication -ShareName MDTProduction -GUID "{4deefc41-71c2-4f59-bcf7-89fd4629a025}"
 60 | ```
 61 | 
 62 | This command returns the application with the GUID "4deefc41-71c2-4f59-bcf7-89fd4629a025" from the MDT share.
 63 | 
 64 | ## PARAMETERS
 65 | 
 66 | ### -GUID
 67 | Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 68 | 
 69 | ```yaml
 70 | Type: Object
 71 | Parameter Sets: GUIDFilter
 72 | Aliases:
 73 | 
 74 | Required: True
 75 | Position: Named
 76 | Default value:
 77 | Accept pipeline input: True (ByPropertyName)
 78 | Accept wildcard characters: True
 79 | ```
 80 | 
 81 | ### -Location
 82 | Specifies that the query be restricted to a folder located within the Applications folder. Specifying "Install\Broken" for example would restrict the search to the folder "Applications\Install\Broken" in the MDT share.
 83 | 
 84 | ```yaml
 85 | Type: Object
 86 | Parameter Sets: (All)
 87 | Aliases:
 88 | 
 89 | Required: False
 90 | Position: Named
 91 | Default value:
 92 | Accept pipeline input: False
 93 | Accept wildcard characters: False
 94 | ```
 95 | 
 96 | ### -Name
 97 | Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\*adobe\*" would return all the applications that have adobe in their name.
 98 | 
 99 | ```yaml
100 | Type: Object
101 | Parameter Sets: NameFilter
102 | Aliases:
103 | 
104 | Required: True
105 | Position: Named
106 | Default value:
107 | Accept pipeline input: True (ByPropertyName)
108 | Accept wildcard characters: True
109 | ```
110 | 
111 | ### -ShareName
112 | Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
113 | 
114 | `PS C:\>New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\\FILESERVER\MDTProduction$" -NetworkPath "\\FILESERVER\MDTProduction$" -Scope Global`
115 | 
116 | or
117 | 
118 | `PS C:\>Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$"`
119 | 
120 | ```yaml
121 | Type: Object
122 | Parameter Sets: (All)
123 | Aliases:
124 | 
125 | Required: False
126 | Position: Named
127 | Default value:
128 | Accept pipeline input: False
129 | Accept wildcard characters: False
130 | ```
131 | 
132 | ## INPUTS
133 | 
134 | ### System.Object
135 | 
136 | 
137 | ## OUTPUTS
138 | 
139 | ### System.Object
140 | 
141 | ## NOTES
142 | 
143 | ## RELATED LINKS
144 | 


--------------------------------------------------------------------------------
/docs/Get-MDTApplicationDependency.md:
--------------------------------------------------------------------------------
  1 | ---
  2 | external help file: MDTApplicationTools-help.xml
  3 | online version: https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Get-MDTApplicationDependency.md
  4 | schema: 2.0.0
  5 | ---
  6 | 
  7 | # Get-MDTApplicationDependency
  8 | ## SYNOPSIS
  9 | Gets the application dependencies of or more MDT applications
 10 | 
 11 | ## SYNTAX
 12 | 
 13 | ### GUIDFilter
 14 | ```
 15 | Get-MDTApplicationDependency [-ShareName <Object>] [-DependencyType <Object>] [-Recurse] -GUID <Object>
 16 | ```
 17 | 
 18 | ### NameFilter
 19 | ```
 20 | Get-MDTApplicationDependency [-ShareName <Object>] [-DependencyType <Object>] [-Recurse] -Name <Object>
 21 | ```
 22 | 
 23 | ## DESCRIPTION
 24 | The Get-MDTApplicationDependency function either returns all the applications that the application is dependent upon(applications that need to be installed before installing the queried application), or applications upon which the queried application is a dependency. It can go back either just one application, or can recurse the entire depth of the dependency tree.
 25 | 
 26 | ## EXAMPLES
 27 | 
 28 | ### Example 1: Get any direct parent dependencies of an app
 29 | ```
 30 | PS C:\> Get-MDTApplicationDependency -ShareName MDTProduction -Name "Install - Java Development Kit - x64"
 31 | ```
 32 | 
 33 | Returns only applications that will be installed **directly before** the Java JDK is installed.
 34 | ### Example 2: Get any direct child dependencies of an app
 35 | ```
 36 | PS C:\> Get-MDTApplicationDependency -ShareName MDTProduction -Name "Install - Java Development Kit - x64" -DependencyType ReturnChild
 37 | ```
 38 | 
 39 | Returns only applications that will install the Java JDK **directly after** they themselves are installed
 40 | ### Example 3: Get **all** parent dependencies of an app
 41 | ```
 42 | PS C:\> Get-MDTApplicationDependency -ShareName MDTProduction -Name "Install - Java Development Kit - x64" -Recurse
 43 | ```
 44 | 
 45 | Returns all applications that need to be installed **before** the Java JDK is installed.
 46 | ### Example 4: Get **all** child dependencies of an app
 47 | ```
 48 | PS C:\> Get-MDTApplicationDependency -ShareName MDTProduction -Name "Install - Java Development Kit - x64" -Recurse -DependencyType ReturnChild
 49 | ```
 50 | 
 51 | Returns all applications that will be installed **after** the Java JDK is installed
 52 | 
 53 | ## PARAMETERS
 54 | 
 55 | ### -DependencyType
 56 | Specifies whether to return the parent dependencies of the queried application(applications that need to be installed before installing the queried application), or to return the child dependencies of the queried application(applications where the queried application needs to be installed first). Possible options are ReturnParent and ReturnChild. Default value is ReturnParent.
 57 | 
 58 | ```yaml
 59 | Type: Object
 60 | Parameter Sets: (All)
 61 | Aliases:
 62 | Accepted values: ReturnParent, ReturnChild
 63 | 
 64 | Required: False
 65 | Position: Named
 66 | Default value: ReturnParent
 67 | Accept pipeline input: False
 68 | Accept wildcard characters: False
 69 | ```
 70 | 
 71 | ### -GUID
 72 | Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 73 | 
 74 | ```yaml
 75 | Type: Object
 76 | Parameter Sets: GUIDFilter
 77 | Aliases:
 78 | 
 79 | Required: True
 80 | Position: Named
 81 | Default value:
 82 | Accept pipeline input: True (ByPropertyName)
 83 | Accept wildcard characters: True
 84 | ```
 85 | 
 86 | ### -Name
 87 | Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\*adobe\*" would return all the applications that have adobe in their name.
 88 | 
 89 | ```yaml
 90 | Type: Object
 91 | Parameter Sets: NameFilter
 92 | Aliases:
 93 | 
 94 | Required: True
 95 | Position: Named
 96 | Default value:
 97 | Accept pipeline input: True (ByPropertyName)
 98 | Accept wildcard characters: True
 99 | ```
100 | 
101 | ### -Recurse
102 | If specified recurses the dependency tree until it reaches the last dependency. If not, only finds dependencies that are one depth away.
103 | 
104 | ```yaml
105 | Type: SwitchParameter
106 | Parameter Sets: (All)
107 | Aliases:
108 | 
109 | Required: False
110 | Position: Named
111 | Default value:
112 | Accept pipeline input: False
113 | Accept wildcard characters: False
114 | ```
115 | 
116 | ### -ShareName
117 | Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
118 | 
119 | `PS C:\>New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\\FILESERVER\MDTProduction$" -NetworkPath "\\FILESERVER\MDTProduction$" -Scope Global`
120 | 
121 | or
122 | 
123 | `PS C:\>Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$"`
124 | 
125 | ```yaml
126 | Type: Object
127 | Parameter Sets: (All)
128 | Aliases:
129 | 
130 | Required: False
131 | Position: Named
132 | Default value:
133 | Accept pipeline input: False
134 | Accept wildcard characters: False
135 | ```
136 | 
137 | ## INPUTS
138 | 
139 | ### System.Object
140 | 
141 | 
142 | ## OUTPUTS
143 | 
144 | ### System.Object
145 | 
146 | ## NOTES
147 | 
148 | ## RELATED LINKS
149 | 


--------------------------------------------------------------------------------
/docs/Rename-MDTApplication.md:
--------------------------------------------------------------------------------
  1 | ---
  2 | external help file: MDTApplicationTools-help.xml
  3 | online version: https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Rename-MDTApplication.md
  4 | schema: 2.0.0
  5 | ---
  6 | 
  7 | # Rename-MDTApplication
  8 | ## SYNOPSIS
  9 | Renames an MDT application.
 10 | 
 11 | ## SYNTAX
 12 | 
 13 | ### GUIDFilter
 14 | ```
 15 | Rename-MDTApplication [-ShareName <Object>] -GUID <Object> [-NewName <Object>] [-RenameSource] [-Force]
 16 |  [-WhatIf] [-Confirm]
 17 | ```
 18 | 
 19 | ### NameFilter
 20 | ```
 21 | Rename-MDTApplication [-ShareName <Object>] -Name <Object> [-NewName <Object>] [-RenameSource] [-Force]
 22 |  [-WhatIf] [-Confirm]
 23 | ```
 24 | 
 25 | ## DESCRIPTION
 26 | The Rename-MDTApplication function renames an MDT application, optionally also renaming the source directory if the applications source files have been imported into MDT. Applications to be renamed can be specified by either their Name or their GUID.
 27 | 
 28 | ## EXAMPLES
 29 | 
 30 | ### Example 1: Rename an application
 31 | ```
 32 | PS C:\> Rename-MDTApplication -ShareName MDTProduction -Name "APP1" -NewName "APP2"
 33 | ```
 34 | 
 35 | Renames APP1 to APP2(changes the "Name" and "ShortName" attributes)
 36 | ### Example 2: Rename an application, also renaming it's source directory
 37 | ```
 38 | PS C:\> Rename-MDTApplication -ShareName MDTProduction -Name "APP1" -NewName "APP2" -RenameSource
 39 | ```
 40 | 
 41 | Renames APP1 to APP2, also changing the source directory name from APP1 to APP2(changes the "Name", "ShortName", "Source", and "WorkingDirectory" attributes, also renaming the source directory itself)
 42 | ### Example 3: Rename an application, also renaming it's source directory
 43 | ```
 44 | PS C:\> Rename-MDTApplication -ShareName MDTProduction -Name "APP1" -NewName "APP2" -Force
 45 | ```
 46 | 
 47 | Renames APP1 to APP2, with the Force parameter disabling the check to see if the application to be renamed exists in the MDT share, and also the check to see if the New Name is already in use by another MDT application. Use with caution.
 48 | 
 49 | ## PARAMETERS
 50 | 
 51 | ### -Confirm
 52 | The confirm preference. If left alone, will prompt you before modifying each application. If set to $false, it just goes through.
 53 | 
 54 | ```yaml
 55 | Type: SwitchParameter
 56 | Parameter Sets: (All)
 57 | Aliases: cf
 58 | 
 59 | Required: False
 60 | Position: Named
 61 | Default value: $true
 62 | Accept pipeline input: False
 63 | Accept wildcard characters: False
 64 | ```
 65 | 
 66 | ### -Force
 67 | If specified, disables the checks to verify that 1: the app to be renamed exists and 2: that new name isn't already in use. Use carefully.
 68 | 
 69 | ```yaml
 70 | Type: SwitchParameter
 71 | Parameter Sets: (All)
 72 | Aliases:
 73 | 
 74 | Required: False
 75 | Position: Named
 76 | Default value: $false
 77 | Accept pipeline input: False
 78 | Accept wildcard characters: False
 79 | ```
 80 | 
 81 | ### -GUID
 82 | Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 83 | 
 84 | ```yaml
 85 | Type: Object
 86 | Parameter Sets: GUIDFilter
 87 | Aliases:
 88 | 
 89 | Required: True
 90 | Position: Named
 91 | Default value:
 92 | Accept pipeline input: True (ByPropertyName)
 93 | Accept wildcard characters: False
 94 | ```
 95 | 
 96 | ### -Name
 97 | Specifies the Name of an application to query the MDT share for. Alternate to GUID Parameter.
 98 | 
 99 | ```yaml
100 | Type: Object
101 | Parameter Sets: NameFilter
102 | Aliases:
103 | 
104 | Required: True
105 | Position: Named
106 | Default value:
107 | Accept pipeline input: True (ByPropertyName)
108 | Accept wildcard characters: False
109 | ```
110 | 
111 | ### -NewName
112 | Specifies what the new name of the application will be once renamed. Rename-MDTApplication will check the existing applications to make sure there are no duplicates before making any changes.
113 | 
114 | ```yaml
115 | Type: Object
116 | Parameter Sets: (All)
117 | Aliases:
118 | 
119 | Required: True
120 | Position: Named
121 | Default value:
122 | Accept pipeline input: False
123 | Accept wildcard characters: False
124 | ```
125 | 
126 | ### -RenameSource
127 | If specified, will also rename the actual application source folder inside of the MDT share. This parameter will only process if the application has it's source files located within the MDT share(the three MDT app types are "apps with source files", "apps with sources on network or elsewhere", and "app bundles". this parameter only processes the first of these three).
128 | 
129 | ```yaml
130 | Type: SwitchParameter
131 | Parameter Sets: (All)
132 | Aliases:
133 | 
134 | Required: False
135 | Position: Named
136 | Default value: $false
137 | Accept pipeline input: False
138 | Accept wildcard characters: False
139 | ```
140 | 
141 | ### -ShareName
142 | Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
143 | 
144 | `PS C:\>New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\\FILESERVER\MDTProduction$" -NetworkPath "\\FILESERVER\MDTProduction$" -Scope Global`
145 | 
146 | or
147 | 
148 | `PS C:\>Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$"`
149 | 
150 | ```yaml
151 | Type: Object
152 | Parameter Sets: (All)
153 | Aliases:
154 | 
155 | Required: True
156 | Position: Named
157 | Default value:
158 | Accept pipeline input: False
159 | Accept wildcard characters: False
160 | ```
161 | 
162 | ### -WhatIf
163 | If specified, will output what changes the command will make without making them.
164 | 
165 | ```yaml
166 | Type: SwitchParameter
167 | Parameter Sets: (All)
168 | Aliases: wi
169 | 
170 | Required: False
171 | Position: Named
172 | Default value:
173 | Accept pipeline input: False
174 | Accept wildcard characters: False
175 | ```
176 | 
177 | ## INPUTS
178 | 
179 | ### System.Object
180 | 
181 | 
182 | ## OUTPUTS
183 | 
184 | ### System.Object
185 | 
186 | ## NOTES
187 | 
188 | ## RELATED LINKS
189 | 


--------------------------------------------------------------------------------
/docs/Set-MDTApplicationSupportedPlatform.md:
--------------------------------------------------------------------------------
  1 | ---
  2 | external help file: MDTApplicationTools-help.xml
  3 | online version: https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Set-MDTApplicationSupportedPlatform.md
  4 | schema: 2.0.0
  5 | ---
  6 | 
  7 | # Set-MDTApplicationSupportedPlatform
  8 | ## SYNOPSIS
  9 | Sets the SupportedPlatform attribute of or more MDT applications
 10 | 
 11 | ## SYNTAX
 12 | 
 13 | ### GUIDFilter
 14 | ```
 15 | Set-MDTApplicationSupportedPlatform [-ShareName <Object>] -GUID <Object> [-SetSupportedPlatformTo <Object>]
 16 |  [-WhatIf] [-Confirm]
 17 | ```
 18 | 
 19 | ### NameFilter
 20 | ```
 21 | Set-MDTApplicationSupportedPlatform [-ShareName <Object>] -Name <Object> [-SetSupportedPlatformTo <Object>]
 22 |  [-WhatIf] [-Confirm]
 23 | ```
 24 | 
 25 | ### NoFilter
 26 | ```
 27 | Set-MDTApplicationSupportedPlatform [-ShareName <Object>] [-SetSupportedPlatformTo <Object>] [-WhatIf]
 28 |  [-Confirm]
 29 | ```
 30 | 
 31 | ## DESCRIPTION
 32 | The Set-MDTApplicationSupportedPlatform function sets the SupportedPlatform attribute on one or more MDT applications. It can either set the attribute to Null, or can set it to one of the predefined OS's. The OS restriction types are a bit more granular when setting this attribute via MDT's GUI, so due to the complexity behind scripting each one, broader "catch-all" types are used. At the moment this tool also disregards any previous settings of the attribute, so any previous settings will be overwritten with the new data specified by the command.
 33 | 
 34 | ## EXAMPLES
 35 | 
 36 | ### Example 1: Remove OS restriction for ALL applications in MDT Share
 37 | ```
 38 | PS C:\> Set-MDTApplicationSupportedPlatform -ShareName MDTProduction -SetSupportedPlatformTo Null
 39 | ```
 40 | 
 41 | Removes the OS restriction for ALL applications in MDTProduction (add a -confirm:$false on the end to remove prompts for each application)
 42 | ### Example 2: Set ALL applications in share to Windows 7
 43 | ```
 44 | PS C:\> Set-MDTApplicationSupportedPlatform -ShareName MDTProduction -SetSupportedPlatformTo Windows7Only
 45 | ```
 46 | 
 47 | Set OS restriction for ALL applications in MDTProduction to Windows 7(add a -confirm:$false on the end to remove prompts for each application)
 48 | ### Example 3: Set one application to windows 10
 49 | ```
 50 | PS C:\> Set-MDTApplicationSupportedPlatform -ShareName MDTProduction -Name "Install - Java Runtime Environment -x86" -SetSupportedPlatformTo Windows10Only
 51 | ```
 52 | 
 53 | Set OS restriction for "Install - Java Runtime Environment -x86" in MDTProduction to Windows 10
 54 | 
 55 | ## PARAMETERS
 56 | 
 57 | ### -Confirm
 58 | The confirm preference. If left alone, will prompt you before modifying each application. If set to $false, it just goes through.
 59 | 
 60 | ```yaml
 61 | Type: SwitchParameter
 62 | Parameter Sets: (All)
 63 | Aliases: cf
 64 | 
 65 | Required: False
 66 | Position: Named
 67 | Default value: $true
 68 | Accept pipeline input: False
 69 | Accept wildcard characters: False
 70 | ```
 71 | 
 72 | ### -GUID
 73 | Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 74 | 
 75 | ```yaml
 76 | Type: Object
 77 | Parameter Sets: GUIDFilter
 78 | Aliases:
 79 | 
 80 | Required: True
 81 | Position: Named
 82 | Default value:
 83 | Accept pipeline input: True (ByPropertyName)
 84 | Accept wildcard characters: True
 85 | ```
 86 | 
 87 | ### -Name
 88 | Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\*adobe\*" would return all the applications that have adobe in their name.
 89 | 
 90 | ```yaml
 91 | Type: Object
 92 | Parameter Sets: NameFilter
 93 | Aliases:
 94 | 
 95 | Required: True
 96 | Position: Named
 97 | Default value:
 98 | Accept pipeline input: True (ByPropertyName)
 99 | Accept wildcard characters: True
100 | ```
101 | 
102 | ### -SetSupportedPlatformTo
103 | Specifies what OS restriction to apply to the application(or to remove the restriction by selecting Null). The OS restriction types are a bit more granular when setting this attribute via MDT's GUI, so due to the complexity behind scripting each one, broader "catch-all" types are used. At the moment this tool also disregards any previous settings of the attribute, so any previous settings will be overwritten with the new data specified here.
104 | 
105 | ```yaml
106 | Type: Object
107 | Parameter Sets: (All)
108 | Aliases:
109 | Accepted values: Null, Windows7Only, Windows8Only, Windows8.1Only, Windows10Only
110 | 
111 | Required: False
112 | Position: Named
113 | Default value:
114 | Accept pipeline input: False
115 | Accept wildcard characters: False
116 | ```
117 | 
118 | ### -ShareName
119 | Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
120 | 
121 | `PS C:\>New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\\FILESERVER\MDTProduction$" -NetworkPath "\\FILESERVER\MDTProduction$" -Scope Global`
122 | 
123 | or
124 | 
125 | `PS C:\>Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$"`
126 | 
127 | ```yaml
128 | Type: Object
129 | Parameter Sets: (All)
130 | Aliases:
131 | 
132 | Required: False
133 | Position: Named
134 | Default value:
135 | Accept pipeline input: False
136 | Accept wildcard characters: False
137 | ```
138 | 
139 | ### -WhatIf
140 | If specified, will output what changes the command will make without making them.
141 | 
142 | ```yaml
143 | Type: SwitchParameter
144 | Parameter Sets: (All)
145 | Aliases: wi
146 | 
147 | Required: False
148 | Position: Named
149 | Default value:
150 | Accept pipeline input: False
151 | Accept wildcard characters: False
152 | ```
153 | 
154 | ## INPUTS
155 | 
156 | ### System.Object
157 | 
158 | 
159 | ## OUTPUTS
160 | 
161 | ### System.Object
162 | 
163 | ## NOTES
164 | 
165 | ## RELATED LINKS
166 | 


--------------------------------------------------------------------------------
/MDTApplicationTools.format.ps1xml:
--------------------------------------------------------------------------------
  1 | <?xml version="1.0" encoding="utf-8" ?>
  2 | <Configuration>
  3 |     <ViewDefinitions>
  4 |         <View>
  5 |             <Name>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationDependency.ParentDependency</Name>
  6 |             <ViewSelectedBy>
  7 |                 <TypeName>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationDependency.ParentDependency</TypeName>
  8 |             </ViewSelectedBy>
  9 |             <TableControl>
 10 |                 <TableHeaders>
 11 |                     <TableColumnHeader>
 12 |                         <Label>Name</Label>
 13 |                     </TableColumnHeader>
 14 |                     <TableColumnHeader>
 15 |                 	<Label>ParentDependency</Label>
 16 |                     </TableColumnHeader>
 17 |                 </TableHeaders>
 18 |                 <TableRowEntries>
 19 |                     <TableRowEntry>
 20 |                         <TableColumnItems>
 21 |                             <TableColumnItem>
 22 |                                 <PropertyName>Name</PropertyName>
 23 |                             </TableColumnItem>
 24 |                             <TableColumnItem>
 25 |                                 <PropertyName>ParentDependency</PropertyName>
 26 |                             </TableColumnItem>
 27 |                         </TableColumnItems>
 28 |                     </TableRowEntry>
 29 |                  </TableRowEntries>
 30 |             </TableControl>
 31 |         </View>
 32 | 
 33 |         <View>
 34 |             <Name>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationDependency.ChildDependency</Name>
 35 |             <ViewSelectedBy>
 36 |                 <TypeName>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationDependency.ChildDependency</TypeName>
 37 |             </ViewSelectedBy>
 38 |             <TableControl>
 39 |                 <TableHeaders>
 40 |                     <TableColumnHeader>
 41 |                         <Label>Name</Label>
 42 |                     </TableColumnHeader>
 43 |                     <TableColumnHeader>
 44 |                 	<Label>ChildDependency</Label>
 45 |                     </TableColumnHeader>
 46 |                 </TableHeaders>
 47 |                 <TableRowEntries>
 48 |                     <TableRowEntry>
 49 |                         <TableColumnItems>
 50 |                             <TableColumnItem>
 51 |                                 <PropertyName>Name</PropertyName>
 52 |                             </TableColumnItem>
 53 |                             <TableColumnItem>
 54 |                                 <PropertyName>ChildDependency</PropertyName>
 55 |                             </TableColumnItem>
 56 |                         </TableColumnItems>
 57 |                     </TableRowEntry>
 58 |                  </TableRowEntries>
 59 |             </TableControl>
 60 |         </View> 
 61 | 
 62 |         <View>
 63 |             <Name>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.SupportedPlatform</Name>
 64 |             <ViewSelectedBy>
 65 |                 <TypeName>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.SupportedPlatform</TypeName>
 66 |             </ViewSelectedBy>
 67 |             <TableControl>
 68 |                 <TableHeaders>
 69 |                     <TableColumnHeader>
 70 |                         <Label>Name</Label>
 71 |                     </TableColumnHeader>
 72 |                     <TableColumnHeader>
 73 |                 	<Label>SupportedPlatform</Label>
 74 |                     </TableColumnHeader>
 75 |                 </TableHeaders>
 76 |                 <TableRowEntries>
 77 |                     <TableRowEntry>
 78 |                         <TableColumnItems>
 79 |                             <TableColumnItem>
 80 |                                 <PropertyName>Name</PropertyName>
 81 |                             </TableColumnItem>
 82 |                             <TableColumnItem>
 83 |                                 <PropertyName>SupportedPlatform</PropertyName>
 84 |                             </TableColumnItem>
 85 |                         </TableColumnItems>
 86 |                     </TableRowEntry>
 87 |                  </TableRowEntries>
 88 |             </TableControl>
 89 |         </View> 
 90 | 
 91 |         <View>
 92 |             <Name>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationContent.ParseScript</Name>
 93 |             <ViewSelectedBy>
 94 |                 <TypeName>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationContent.ParseScript</TypeName>
 95 |             </ViewSelectedBy>
 96 |             <TableControl>
 97 |                 <TableHeaders>
 98 |                     <TableColumnHeader>
 99 |                         <Label>Name</Label>
100 |                     </TableColumnHeader>
101 |                     <TableColumnHeader>
102 |                 	<Label>Script</Label>
103 |                     </TableColumnHeader>
104 |                     <TableColumnHeader>
105 |                 	<Label>LinesFound</Label>
106 |                     </TableColumnHeader>
107 |                 </TableHeaders>
108 |                 <TableRowEntries>
109 |                     <TableRowEntry>
110 |                         <TableColumnItems>
111 |                             <TableColumnItem>
112 |                                 <PropertyName>Name</PropertyName>
113 |                             </TableColumnItem>
114 |                             <TableColumnItem>
115 |                                 <PropertyName>Script</PropertyName>
116 |                             </TableColumnItem>
117 |                             <TableColumnItem>
118 |                                 <PropertyName>LinesFound</PropertyName>
119 |                             </TableColumnItem>
120 |                         </TableColumnItems>
121 |                     </TableRowEntry>
122 |                  </TableRowEntries>
123 |             </TableControl>
124 |         </View>
125 | 
126 |         <View>
127 |             <Name>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationContent.InstallCmd</Name>
128 |             <ViewSelectedBy>
129 |                 <TypeName>Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationContent.InstallCmd</TypeName>
130 |             </ViewSelectedBy>
131 |             <TableControl>
132 |                 <TableHeaders>
133 |                     <TableColumnHeader>
134 |                         <Label>Name</Label>
135 |                     </TableColumnHeader>
136 |                     <TableColumnHeader>
137 |                 	<Label>CommandLine</Label>
138 |                     </TableColumnHeader>
139 |                 </TableHeaders>
140 |                 <TableRowEntries>
141 |                     <TableRowEntry>
142 |                         <TableColumnItems>
143 |                             <TableColumnItem>
144 |                                 <PropertyName>Name</PropertyName>
145 |                             </TableColumnItem>
146 |                             <TableColumnItem>
147 |                                 <PropertyName>CommandLine</PropertyName>
148 |                             </TableColumnItem>
149 |                         </TableColumnItems>
150 |                     </TableRowEntry>
151 |                  </TableRowEntries>
152 |             </TableControl>
153 |         </View>          
154 |     </ViewDefinitions>
155 | </Configuration>
156 | 


--------------------------------------------------------------------------------
/MDTApplicationTools.psm1:
--------------------------------------------------------------------------------
  1 | Function Import-MDTModule {
  2 |     $MDTModuleInstallLocation = "C:\Program Files\Microsoft Deployment Toolkit\Bin\MicrosoftDeploymentToolkit.psd1"
  3 |     if (!(Get-Module MicrosoftDeploymentToolkit)) {
  4 |         if (Test-Path $MDTModuleInstallLocation) {
  5 |             Import-Module $MDTModuleInstallLocation
  6 |         } else {
  7 |             Write-Error "MDT module not working. Microsoft Deployment Toolkit may need to be installed."
  8 |         }
  9 |     }
 10 |     $return = Get-Module MicrosoftDeploymentToolkit
 11 |     return $return
 12 | }
 13 | 
 14 | Function Get-MDTDrive {
 15 |     [CmdletBinding()]
 16 |     param(
 17 |         [Parameter(Mandatory=$true)]    
 18 |         $Name
 19 |     )
 20 |     PROCESS{
 21 |         if(Import-MDTModule) {
 22 |             $drive = Get-PSDrive -Name $Name -PSProvider MDTProvider
 23 |             return $drive
 24 |         }
 25 |     }
 26 | }
 27 | 
 28 | Function Set-MDTDrive {
 29 |     [cmdletbinding(
 30 |         SupportsShouldProcess=$true
 31 |     )]
 32 |     param(
 33 |         [Parameter(Mandatory=$true)]
 34 |         $Name,
 35 |         [Parameter(Mandatory=$true)]
 36 |         $Path,
 37 |         [Parameter()]
 38 |         [switch]$Force
 39 |     )
 40 |     BEGIN {
 41 |         $mdtdrive = Get-MDTDrive -Name $Name -ErrorAction:SilentlyContinue
 42 |         if (Import-MDTModule) {
 43 |             if ($mdtdrive) {
 44 |                 Write-Verbose "$Name already exists"
 45 |                 if ($Force) {
 46 |                     if ($PSCmdlet.ShouldProcess($env:COMPUTERNAME,"Creating MDT drive $Name with path $Path")) {
 47 |                         Write-Verbose "Force switch specified. Overwriting drive $Name"
 48 |                         New-PSDrive -Name $Name -PSProvider MDTProvider -Root $Path -NetworkPath $Path -Scope Global
 49 |                     }
 50 |                 }
 51 |             } elseif (!($mdtdrive)) {
 52 |                 if ($PSCmdlet.ShouldProcess($env:COMPUTERNAME,"Creating MDT drive $Name with path $Path")) {
 53 |                     Write-Verbose "Creating new drive: $Name : $Path"
 54 |                     New-PSDrive -Name $Name -PSProvider MDTProvider -Root $Path -NetworkPath $Path -Scope Global
 55 |                 }
 56 |             }
 57 |         }
 58 |     }
 59 | }
 60 | 
 61 | Function Get-MDTApplication {
 62 |     [cmdletbinding()]
 63 |     param(
 64 |         [Parameter(Mandatory=$true)]
 65 |         [Parameter(ParameterSetName='NoFilter')]
 66 |         [Parameter(ParameterSetName='NameFilter')]
 67 |         [Parameter(ParameterSetName='GUIDFilter')]
 68 |         $ShareName,
 69 |         [Parameter(ParameterSetName='NoFilter')]
 70 |         [Parameter(ParameterSetName='NameFilter')]
 71 |         [Parameter(ParameterSetName='GUIDFilter')]
 72 |         $Location,
 73 |         [Parameter(Mandatory=$true,
 74 |                    ValueFromPipelineByPropertyName=$true,
 75 |                    ParameterSetName='NameFilter')]
 76 |         $Name,
 77 |         [Parameter(
 78 |                    Mandatory=$true,
 79 |                    ValueFromPipelineByPropertyName=$true,
 80 |                    ParameterSetName='GUIDFilter')]
 81 |         $GUID
 82 |     )
 83 |     BEGIN {
 84 |         $mdtdriveworking = Get-MDTDrive -Name $ShareName
 85 |         if ($mdtdriveworking) {
 86 |             if ($null -eq $location) {
 87 |                 $getchilditemquery = Get-ChildItem -Path $ShareName`:\Applications -Recurse | Where-Object {$_.NodeType -eq "Application"}
 88 |             } else {
 89 |                 $getchilditemquery = Get-ChildItem -Path $ShareName`:\Applications\$location -Recurse | Where-Object {$_.NodeType -eq "Application"}
 90 |             }
 91 |         }
 92 |     }
 93 |     PROCESS {
 94 |         if ($mdtdriveworking) {
 95 |             switch ($PSCmdlet.ParameterSetName) {
 96 |                 "NameFilter" {
 97 |                     $appobject = $getchilditemquery | Where-Object {$_.Name -like $Name}
 98 |                     Write-Output $appobject
 99 |                 }
100 |                 "GUIDFilter" {
101 |                     if($GUID -notmatch "{*}") {
102 |                         $GUID = ("{" + $GUID + "}")
103 |                     }
104 |                     $appobject = $getchilditemquery | Where-Object {$_.GUID -like $GUID}
105 |                     Write-Output $appobject
106 |                 }
107 |                 "NoFilter" {
108 |                     Write-Output $getchilditemquery
109 |                 }
110 |             }
111 |         }
112 |     }
113 | }
114 | 
115 | Function Get-MDTApplicationDependency {
116 |     [cmdletbinding()]
117 |     param(
118 |         [Parameter(Mandatory=$true)]
119 |         [Parameter(ParameterSetName='NameFilter')]
120 |         [Parameter(ParameterSetName='GUIDFilter')]
121 |         $ShareName,
122 |         [Parameter(ParameterSetName='NameFilter')]
123 |         [Parameter(ParameterSetName='GUIDFilter')]
124 |         [ValidateSet("ReturnParent","ReturnChild")]
125 |         $DependencyType = "ReturnParent",
126 |         [Parameter(ParameterSetName='NameFilter')]
127 |         [Parameter(ParameterSetName='GUIDFilter')]
128 |         [switch]$Recurse,
129 |         [Parameter(Mandatory=$true,
130 |                    ValueFromPipelineByPropertyName=$true,
131 |                    ParameterSetName='NameFilter')]
132 |         $Name,
133 |         [Parameter(
134 |                    Mandatory=$true,
135 |                    ValueFromPipelineByPropertyName=$true,
136 |                    ParameterSetName='GUIDFilter')]
137 |         $GUID
138 |     )
139 |     BEGIN {
140 |         switch ($PSCmdlet.ParameterSetName) {
141 |             "NameFilter" {
142 |                 $sourceapp = Get-MDTApplication -ShareName $ShareName -Name $Name
143 |             }
144 |             "GUIDFilter" {
145 |                 if($GUID -notmatch "{*}") {
146 |                     $GUID = ("{" + $GUID + "}")
147 |                 }
148 |                 $sourceapp = Get-MDTApplication -ShareName $ShareName -GUID $GUID
149 |             }
150 |         }
151 |         if ($DependencyType -eq "ReturnChild") {
152 |             $allapplications = Get-MDTApplication -ShareName $ShareName
153 |         }
154 |     }
155 |     PROCESS {
156 |         switch ($DependencyType) {
157 |             "ReturnParent" {
158 |                 foreach ($app in $sourceapp.dependency) {
159 |                     $appobject = Get-MDTApplication -ShareName $ShareName -GUID $app | Add-Member NoteProperty ParentDependency($sourceapp.Name) -PassThru
160 |                     $appobject.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationDependency.ParentDependency')
161 |                     Write-Output $appobject
162 |                     if ($Recurse -and $appobject.dependency) {
163 |                         Get-MDTApplicationDependency -ShareName $ShareName -GUID $app -DependencyType ReturnParent -Recurse
164 |                     }
165 |                 }
166 |             }
167 |             "ReturnChild" {
168 |                 foreach ($app in $allapplications) {
169 |                     if ($app.Dependency -contains $sourceapp.guid) {
170 |                         $appobject = Get-MDTApplication -ShareName $ShareName -GUID $app.guid | Add-Member NoteProperty ChildDependency($sourceapp.Name) -PassThru
171 |                         $appobject.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationDependency.ChildDependency')
172 |                         Write-Output $appobject
173 |                         if ($Recurse -and $appobject.dependency) {
174 |                             Get-MDTApplicationDependency -ShareName $ShareName -GUID $app.guid -DependencyType ReturnChild -Recurse
175 |                         }
176 |                     }
177 |                 }
178 |             }
179 |         }
180 |     }
181 | }
182 | 
183 | Function Get-MDTApplicationSupportedPlatform {
184 |     [cmdletbinding()]
185 |     param(
186 |         [Parameter(Mandatory=$true)]
187 |         [Parameter(ParameterSetName='NoFilter')]
188 |         [Parameter(ParameterSetName='NameFilter')]
189 |         [Parameter(ParameterSetName='GUIDFilter')]
190 |         $ShareName,
191 |         [Parameter(Mandatory=$true,
192 |                    ValueFromPipelineByPropertyName=$true,
193 |                    ParameterSetName='NameFilter')]
194 |         $Name,
195 |         [Parameter(
196 |                    Mandatory=$true,
197 |                    ValueFromPipelineByPropertyName=$true,
198 |                    ParameterSetName='GUIDFilter')]
199 |         $GUID,
200 |         [ValidateSet("Yes", "No", "All")]
201 |         $SupportedPlatformSet = "All"
202 |     )
203 |     PROCESS {
204 |         switch ($PSCmdlet.ParameterSetName) {
205 |             "NoFilter" {
206 |                 $basequery = Get-MDTApplication -ShareName $ShareName
207 |                 switch ($SupportedPlatformSet) {
208 |                     "Yes" {$appobject = $basequery | Where-Object {$_.SupportedPlatform -like "*"}}
209 |                     "No" {$appobject = $basequery | Where-Object {[string]$_.SupportedPlatform -like ""}}
210 |                     "All" {$appobject = $basequery}
211 |                 }
212 |                 $appobject.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.SupportedPlatform')
213 |                 Write-Output $appobject
214 |             }
215 |             "NameFilter" {
216 |                 $basequery = Get-MDTApplication -ShareName $ShareName -Name $Name 
217 |                 switch ($SupportedPlatformSet) {
218 |                     "Yes" {$appobject = $basequery | Where-Object {$_.SupportedPlatform -like "*"}}
219 |                     "No" {$appobject = $basequery | Where-Object {[string]$_.SupportedPlatform -like ""}}
220 |                     "All" {$appobject = $basequery}
221 |                 }
222 |                 $appobject.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.SupportedPlatform')
223 |                 Write-Output $appobject
224 |             }
225 |             "GUIDFilter" {
226 |                 if($GUID -notmatch "{*}") {
227 |                     $GUID = ("{" + $GUID + "}")
228 |                 }
229 |                 $basequery = Get-MDTApplication -ShareName $ShareName -GUID $GUID
230 |                 switch ($SupportedPlatformSet) {
231 |                     "Yes" {$appobject = $basequery | Where-Object {$_.SupportedPlatform -like "*"}}
232 |                     "No" {$appobject = $basequery | Where-Object {[string]$_.SupportedPlatform -like ""}}
233 |                     "All" {$appobject = $basequery}
234 |                 }
235 |                 $appobject.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.SupportedPlatform')
236 |                 Write-Output $appobject
237 |             }
238 |         }
239 |     }
240 | }
241 | 
242 | Function Set-MDTApplicationSupportedPlatform {
243 |     [cmdletbinding(
244 |         SupportsShouldProcess=$true,
245 |         ConfirmImpact="High"
246 |     )]
247 |     param(
248 |         [Parameter(Mandatory=$true)]
249 |         [Parameter(ParameterSetName='NoFilter')]
250 |         [Parameter(ParameterSetName='NameFilter')]
251 |         [Parameter(ParameterSetName='GUIDFilter')]
252 |         $ShareName,
253 |         [Parameter(Mandatory=$true,
254 |                    ValueFromPipelineByPropertyName=$true,
255 |                    ParameterSetName='NameFilter')]
256 |         $Name,
257 |         [Parameter(
258 |                    Mandatory=$true,
259 |                    ValueFromPipelineByPropertyName=$true,
260 |                    ParameterSetName='GUIDFilter')]
261 |         $GUID,
262 |         [Parameter(Mandatory=$true)]
263 |         [Parameter(ParameterSetName='NoFilter')]
264 |         [Parameter(ParameterSetName='NameFilter')]
265 |         [Parameter(ParameterSetName='GUIDFilter')]
266 |         [ValidateSet("Null", "Windows7Only", "Windows8Only", "Windows8.1Only", "Windows10Only")]
267 |         $SetSupportedPlatformTo
268 |     )
269 |     BEGIN {
270 |         Switch ($SetSupportedPlatformTo) {
271 |             "Null" {$code = @()}
272 |             "Windows7Only" {$code = @('All x86 Windows 7 Client', 'All x64 Windows 7 Client')}
273 |             "Windows8Only" {$code = @('All x86 Windows 8 Client', 'All x64 Windows 8 Client')}
274 |             "Windows8.1Only" {$code = @('All x86 Windows 8.1 Client', 'All x64 Windows 8.1 Client') }
275 |             "Windows10Only" {$code = @('All x86 Windows 10 Client', 'All x64 Windows 10 Client') }
276 |         }
277 |     }
278 |     PROCESS {
279 |         switch ($PSCmdlet.ParameterSetName) {
280 |             "NoFilter" {
281 |                 $app = Get-MDTApplication -ShareName $ShareName
282 |                 if ($PSCmdlet.ShouldProcess($ShareName,"Setting Supported Platform to $SetSupportedPlatformTo on all applications")) {
283 |                     $appobject = $app | ForEach-Object  {Set-ItemProperty -Path ([string]$_.PsPath -replace 'MicrosoftDeploymentToolkit\\MDTProvider::',"") -Name SupportedPlatform -Value $code}
284 |                     $appobject.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.SupportedPlatform')
285 |                     Write-Output $appobject
286 |                 }
287 |             }
288 |             "NameFilter" {
289 |                 $app = Get-MDTApplication -ShareName $ShareName -Name $Name
290 |                 $appname = $app.Name
291 |                 if ($PSCmdlet.ShouldProcess($ShareName,"Setting Supported Platform to $SetSupportedPlatformTo on $appname")) {
292 |                     $appobject = $app | ForEach-Object {Set-ItemProperty -Path ([string]$_.PsPath -replace 'MicrosoftDeploymentToolkit\\MDTProvider::',"") -Name SupportedPlatform -Value $code}
293 |                     $appobject.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.SupportedPlatform')
294 |                     Write-Output $appobject
295 |                 }
296 |             }
297 |             "GUIDFilter" {
298 |                 if($GUID -notmatch "{*}") {
299 |                     $GUID = ("{" + $GUID + "}")
300 |                 }
301 |                 $app = Get-MDTApplication -ShareName $ShareName -GUID $GUID
302 |                 $appname = $app.Name
303 |                 if ($PSCmdlet.ShouldProcess($ShareName,"Setting Supported Platform to $SetSupportedPlatformTo on $appname")) {
304 |                     $appobject = $app | ForEach-Object  {Set-ItemProperty -Path ([string]$_.PsPath -replace 'MicrosoftDeploymentToolkit\\MDTProvider::',"") -Name SupportedPlatform -Value $code}
305 |                     $appobject.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.SupportedPlatform')
306 |                     Write-Output $appobject
307 |                 }
308 |             }
309 |         }
310 |     }
311 | }
312 | 
313 | Function Find-MDTApplicationContent {
314 |     [cmdletbinding()]
315 |     param(
316 |         [Parameter(Mandatory=$true)]
317 |         $ShareName,
318 |         $String,
319 |         [switch]$ParseScript
320 | 
321 |     )
322 |     BEGIN {
323 |         $apps = Get-MDTApplication -ShareName $ShareName
324 |         $filetypes = @(".bat",".cmd",".vbs",".wsf",".ps1",".psm1",".psd1")
325 |         $sharepath = (Get-PSDrive -Name $ShareName).Root
326 |     }
327 |     PROCESS {
328 |         if($ParseScript) {
329 |             foreach ($app in $apps) {   #goes through all apps in share
330 |                 if ($app.Source -notlike $null) {   #makes sure app has files to search for
331 |                     $apppath = ($app.Source.ToString()).substring(1)
332 |                     $apppath = "$sharepath$apppath"
333 |                     if (Test-Path $apppath) {   #makes sure apppath exists
334 |                         $appcontents = Get-ChildItem -Path $apppath #gets list of files in $apppath
335 |                         foreach ($item in $appcontents) {   #goes through each item in $apppath
336 |                             $itemfound = $false
337 |                             $lineobj = @()
338 |                             foreach ($filetype in $filetypes) {
339 |                                 if ($item -like "*$filetype*") {    #selects only items with filetype defined in $filetypes
340 |                                     $itemcontent = Get-Content -Path $item.FullName #gets content of item
341 |                                     foreach ($line in $itemcontent) {   #goes through each line in item content,
342 |                                         if ($line -like $String) {  #and outputs if string matches
343 |                                             $itemfound = $true
344 |                                             $line  = $line.ReadCount.ToString() + ': ' + $line.Trim()   #prepends the line number to the beginning of the found string
345 |                                             $lineobj += $line
346 |                                         }
347 |                                     }
348 |                                     if ($itemfound) {
349 |                                         $app.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationContent.ParseScript')
350 |                                         $app = $app | Add-Member NoteProperty Script($item) -PassThru| Add-Member NoteProperty LinesFound($lineobj) -PassThru
351 |                                         Write-Output $app
352 |                                     }
353 |                                 }
354 |                             }
355 |                         }
356 |                     }
357 |                 }
358 |             }
359 |         } else {
360 |             $app = Get-MDTApplication -ShareName $ShareName | Where-Object {$_.CommandLine -like "$String"}
361 |             $app.PSObject.TypeNames.Insert(0,'Microsoft.BDD.PSSnapIn.MDTObject.MDTApplicationTools.ApplicationContent.InstallCmd')
362 |             Write-Output $app
363 | 
364 |         }
365 |     }
366 | }
367 | 
368 | function Rename-MDTApplication {
369 |     [cmdletbinding(
370 |         SupportsShouldProcess=$true,
371 |         ConfirmImpact="High"
372 |     )]
373 |     param(
374 |         [Parameter(Mandatory=$true)]
375 |         [Parameter(ParameterSetName='NameFilter')]
376 |         [Parameter(ParameterSetName='GUIDFilter')]
377 |         $ShareName,
378 |         [Parameter(Mandatory=$true,
379 |                    ValueFromPipelineByPropertyName=$true,
380 |                    ParameterSetName='NameFilter')]
381 |         $Name,
382 |         [Parameter(
383 |                    Mandatory=$true,
384 |                    ValueFromPipelineByPropertyName=$true,
385 |                    ParameterSetName='GUIDFilter')]
386 |         $GUID,
387 |         [Parameter(Mandatory=$true)]
388 |         [Parameter(ParameterSetName='NameFilter')]
389 |         [Parameter(ParameterSetName='GUIDFilter')]
390 |         $NewName,
391 |         [Parameter(ParameterSetName='NameFilter')]
392 |         [Parameter(ParameterSetName='GUIDFilter')]
393 |         [switch]$RenameSource,
394 |         [Parameter(ParameterSetName='NameFilter')]
395 |         [Parameter(ParameterSetName='GUIDFilter')]
396 |         [switch]$Force
397 |     )
398 |     PROCESS {
399 |         $prevappcheck = Get-MDTApplication -ShareName $ShareName -Name $NewName
400 |         if(!$prevappcheck -or $Force) {
401 |             switch ($PSCmdlet.ParameterSetName) {
402 |                 "NameFilter" {
403 |                     $app = Get-MDTApplication -ShareName $ShareName -Name $Name
404 |                 }
405 |                 "GUIDFilter" {
406 |                     if($GUID -notmatch "{*}") {
407 |                         $GUID = ("{" + $GUID + "}")
408 |                     }
409 |                     $app = Get-MDTApplication -ShareName $ShareName -GUID $GUID
410 |                 }
411 |             }
412 |             if($app -or $Force){
413 |                 $appname = $app.Name                                                               #variable needed to display name in shouldprocess statements
414 |                 $apppath = ([string]$app.PsPath -split "::")[1]                                    #path used for set-itemproperty statements
415 |                 if ($app.CommandLine -notlike "") {
416 |                     if ($app.Source -notlike "") {
417 |                         $apptype =  "APPSOURCE"
418 |                     } else {
419 |                         $apptype = "APPNOSOURCE"
420 |                     }
421 |                 } else {
422 |                     $apptype = "APPBUNDLE"
423 |                 }
424 |                 if ($RenameSource -eq $false -or $apptype -eq "APPBUNDLE" -or $apptype -eq "APPNOSOURCE") {
425 |                     if ($PSCmdlet.ShouldProcess($ShareName,"Renaming $appname to $NewName")) {
426 |                         Set-ItemProperty -Path $apppath -Name ShortName -Value $NewName
427 |                         Set-ItemProperty -Path $apppath -Name Name -Value $NewName
428 |                     }
429 |                 } else {
430 |                     $mdtdriveroot = Get-PSDrive -Name $ShareName | Select-Object -ExpandProperty Root
431 |                     $origfullpath = $mdtdriveroot + $app.Source.TrimStart(".")
432 |                     $oldsourcename = $app.Source.split("\") | Select-Object -Last 1
433 |                     $newsourcepath = $app.Source.Replace($oldsourcename,$NewName)                   #path used when changing source path property
434 |                     if ($PSCmdlet.ShouldProcess($ShareName,"Renaming $appname to $NewName, and renaming source directory from $oldsourcename to $NewName")) {
435 |                         try {
436 |                             Rename-Item -Path $origfullpath -NewName $NewName -ErrorAction Stop
437 |                             Set-ItemProperty -Path $apppath -Name Source -Value $newsourcepath
438 |                             Set-ItemProperty -Path $apppath -Name WorkingDirectory -Value $newsourcepath
439 |                             Set-ItemProperty -Path $apppath -Name ShortName -Value $NewName
440 |                             Set-ItemProperty -Path $apppath -Name Name -Value $NewName
441 |                         } catch {
442 |                             Write-Error "issue renaming directory. no changes have been made."
443 |                         }
444 |                     }
445 |                 }
446 |             } else {
447 |                 switch ($PSCmdlet.ParameterSetName) {
448 |                     "NameFilter" {
449 |                         Write-Error "no app with Name $Name exists"
450 |                     }
451 |                     "GUIDFilter" {
452 |                         if($GUID -notmatch "{*}") {
453 |                             $GUID = ("{" + $GUID + "}")
454 |                         }
455 |                         Write-Error "no app with GUID $GUID exists"
456 |                     }
457 |                 }
458 |             }
459 |         } else {
460 |             Write-Error "An app with the name $NewName already exists"
461 |         }
462 |     }
463 | }


--------------------------------------------------------------------------------
/en-US/MDTApplicationTools-help.xml:
--------------------------------------------------------------------------------
   1 | <?xml version="1.0" encoding="utf-8"?>
   2 | <helpItems schema="maml">
   3 | 
   4 | <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
   5 | <command:details><command:name>Find-MDTApplicationContent</command:name>
   6 | <command:verb>Find</command:verb>
   7 | <command:noun>MDTApplicationContent</command:noun>
   8 | <maml:description><maml:para>Searches MDT shares for applications whose content contain specified text.
   9 | </maml:para>
  10 | </maml:description>
  11 | </command:details>
  12 | <maml:description><maml:para>The Find-MDTApplicationContent function retrieves MDT applications from the specified MDT share that contain the string specified. It can query either just the CommandLine attribute of the application, or it can also query the install scripts themselves if the ParseScript switch is specified.
  13 | </maml:para>
  14 | </maml:description>
  15 | <command:syntax><command:syntaxItem><maml:name>Find-MDTApplicationContent</maml:name>
  16 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="0" aliases="none"><maml:name>ShareName</maml:name>
  17 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
  18 | </maml:para>
  19 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
  20 | </maml:para>
  21 | <maml:para>or
  22 | </maml:para>
  23 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
  24 | </maml:para>
  25 | </maml:Description>
  26 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
  27 | <dev:type><maml:name>Object</maml:name>
  28 | <maml:uri /></dev:type>
  29 | <dev:defaultValue></dev:defaultValue>
  30 | </command:parameter>
  31 | <command:parameter required="false" variableLength="true" globbing="true" pipelineInput="False" position="1" aliases="none"><maml:name>String</maml:name>
  32 | <maml:Description><maml:para>Specifies the string to search for in MDT applications. If typed explicitly (i.e. "setup.exe /s"), it will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like \ powershell.exe\ would return all the applications that have powershell.exe in their commandline or install script(depending on whether the ParseScript parameter was used).
  33 | </maml:para>
  34 | </maml:Description>
  35 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
  36 | <dev:type><maml:name>Object</maml:name>
  37 | <maml:uri /></dev:type>
  38 | <dev:defaultValue></dev:defaultValue>
  39 | </command:parameter>
  40 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ParseScript</maml:name>
  41 | <maml:Description><maml:para>IF NOT specified, the only part of the apps that are searched are the "CommandLine" attribute, which is the initial command that gets launched at install time to install the app(it can reference either an executable or an install script path). IF specified, the script will actually go through the applications working directory, and parse through any install scripts to see if they contain the specified string. It searches the following files:
  42 | </maml:para>
  43 | <maml:para>".bat",".cmd",".vbs",".wsf",".ps1",".psm1",".psd1"
  44 | </maml:para>
  45 | </maml:Description>
  46 | <dev:type><maml:name>SwitchParameter</maml:name>
  47 | <maml:uri /></dev:type>
  48 | <dev:defaultValue>False</dev:defaultValue>
  49 | </command:parameter>
  50 | </command:syntaxItem>
  51 | </command:syntax>
  52 | <command:parameters><command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ParseScript</maml:name>
  53 | <maml:Description><maml:para>IF NOT specified, the only part of the apps that are searched are the "CommandLine" attribute, which is the initial command that gets launched at install time to install the app(it can reference either an executable or an install script path). IF specified, the script will actually go through the applications working directory, and parse through any install scripts to see if they contain the specified string. It searches the following files:
  54 | </maml:para>
  55 | <maml:para>".bat",".cmd",".vbs",".wsf",".ps1",".psm1",".psd1"
  56 | </maml:para>
  57 | </maml:Description>
  58 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
  59 | <dev:type><maml:name>SwitchParameter</maml:name>
  60 | <maml:uri /></dev:type>
  61 | <dev:defaultValue>False</dev:defaultValue>
  62 | </command:parameter>
  63 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="0" aliases="none"><maml:name>ShareName</maml:name>
  64 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
  65 | </maml:para>
  66 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
  67 | </maml:para>
  68 | <maml:para>or
  69 | </maml:para>
  70 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
  71 | </maml:para>
  72 | </maml:Description>
  73 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
  74 | <dev:type><maml:name>Object</maml:name>
  75 | <maml:uri /></dev:type>
  76 | <dev:defaultValue></dev:defaultValue>
  77 | </command:parameter>
  78 | <command:parameter required="false" variableLength="true" globbing="true" pipelineInput="False" position="1" aliases="none"><maml:name>String</maml:name>
  79 | <maml:Description><maml:para>Specifies the string to search for in MDT applications. If typed explicitly (i.e. "setup.exe /s"), it will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like \ powershell.exe\ would return all the applications that have powershell.exe in their commandline or install script(depending on whether the ParseScript parameter was used).
  80 | </maml:para>
  81 | </maml:Description>
  82 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
  83 | <dev:type><maml:name>Object</maml:name>
  84 | <maml:uri /></dev:type>
  85 | <dev:defaultValue></dev:defaultValue>
  86 | </command:parameter>
  87 | </command:parameters>
  88 | <command:inputTypes><command:inputType><dev:type><maml:name>None</maml:name>
  89 | </dev:type>
  90 | <maml:description><maml:para>
  91 | </maml:para>
  92 | </maml:description>
  93 | </command:inputType>
  94 | </command:inputTypes>
  95 | <command:returnValues><command:returnValue><dev:type><maml:name>System.Object</maml:name>
  96 | </dev:type>
  97 | <maml:description><maml:para>
  98 | </maml:para>
  99 | </maml:description>
 100 | </command:returnValue>
 101 | </command:returnValues>
 102 | <maml:alertSet><maml:alert><maml:para>
 103 | </maml:para>
 104 | </maml:alert>
 105 | </maml:alertSet>
 106 | <command:examples><command:example><maml:title>Example 1</maml:title>
 107 | <dev:code>PS C:\&gt; Find-MDTApplicationContent -ShareName MDTProduction -string "setup.exe /s"</dev:code>
 108 | <dev:remarks><maml:para>This command searches the MDT share MDTProduction, and returns any applications where the "CommandLine" attribute matches "setup.exe /s" exactly.
 109 | </maml:para>
 110 | </dev:remarks>
 111 | </command:example>
 112 | <command:example><maml:title>Example 2</maml:title>
 113 | <dev:code>PS C:\&gt; Find-MDTApplicationContent -ShareName MDTProduction -string *.bat*</dev:code>
 114 | <dev:remarks><maml:para>This command searches the MDT share MDTProduction, and returns any applications that call a .bat file in their "CommandLine" attribute
 115 | </maml:para>
 116 | </dev:remarks>
 117 | </command:example>
 118 | <command:example><maml:title>Example 3</maml:title>
 119 | <dev:code>PS C:\&gt; Find-MDTApplicationContent -ShareName MDTProduction -string "C:\Program Files\*" -ParseScript</dev:code>
 120 | <dev:remarks><maml:para>This command searches the MDT share MDTProduction, and returns any applications that call a .bat file in their "CommandLine" attribute
 121 | </maml:para>
 122 | </dev:remarks>
 123 | </command:example>
 124 | </command:examples>
 125 | <command:relatedLinks><maml:navigationLink><maml:linkText>Online Version:</maml:linkText>
 126 | <maml:uri>https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Find-MDTApplicationContent.md</maml:uri>
 127 | </maml:navigationLink>
 128 | </command:relatedLinks>
 129 | </command:command>
 130 | <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
 131 | <command:details><command:name>Get-MDTApplication</command:name>
 132 | <command:verb>Get</command:verb>
 133 | <command:noun>MDTApplication</command:noun>
 134 | <maml:description><maml:para>Gets one or more MDT applications
 135 | </maml:para>
 136 | </maml:description>
 137 | </command:details>
 138 | <maml:description><maml:para>The Get-MDTApplication function retrieves MDT applications from the specified MDT share. It can be used to either retrieve all the applications at once, or just by the applications Name or GUID of the wanted application.
 139 | </maml:para>
 140 | </maml:description>
 141 | <command:syntax><command:syntaxItem><maml:name>Get-MDTApplication</maml:name>
 142 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
 143 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 144 | </maml:para>
 145 | </maml:Description>
 146 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 147 | <dev:type><maml:name>Object</maml:name>
 148 | <maml:uri /></dev:type>
 149 | <dev:defaultValue></dev:defaultValue>
 150 | </command:parameter>
 151 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Location</maml:name>
 152 | <maml:Description><maml:para>Specifies that the query be restricted to a folder located within the Applications folder. Specifying "Install\Broken" for example would restrict the search to the folder "Applications\Install\Broken" in the MDT share.
 153 | </maml:para>
 154 | </maml:Description>
 155 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 156 | <dev:type><maml:name>Object</maml:name>
 157 | <maml:uri /></dev:type>
 158 | <dev:defaultValue></dev:defaultValue>
 159 | </command:parameter>
 160 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 161 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 162 | </maml:para>
 163 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 164 | </maml:para>
 165 | <maml:para>or
 166 | </maml:para>
 167 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 168 | </maml:para>
 169 | </maml:Description>
 170 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 171 | <dev:type><maml:name>Object</maml:name>
 172 | <maml:uri /></dev:type>
 173 | <dev:defaultValue></dev:defaultValue>
 174 | </command:parameter>
 175 | </command:syntaxItem>
 176 | <command:syntaxItem><maml:name>Get-MDTApplication</maml:name>
 177 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Location</maml:name>
 178 | <maml:Description><maml:para>Specifies that the query be restricted to a folder located within the Applications folder. Specifying "Install\Broken" for example would restrict the search to the folder "Applications\Install\Broken" in the MDT share.
 179 | </maml:para>
 180 | </maml:Description>
 181 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 182 | <dev:type><maml:name>Object</maml:name>
 183 | <maml:uri /></dev:type>
 184 | <dev:defaultValue></dev:defaultValue>
 185 | </command:parameter>
 186 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
 187 | <maml:Description><maml:para>Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\ adobe\ " would return all the applications that have adobe in their name.
 188 | </maml:para>
 189 | </maml:Description>
 190 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 191 | <dev:type><maml:name>Object</maml:name>
 192 | <maml:uri /></dev:type>
 193 | <dev:defaultValue></dev:defaultValue>
 194 | </command:parameter>
 195 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 196 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 197 | </maml:para>
 198 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 199 | </maml:para>
 200 | <maml:para>or
 201 | </maml:para>
 202 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 203 | </maml:para>
 204 | </maml:Description>
 205 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 206 | <dev:type><maml:name>Object</maml:name>
 207 | <maml:uri /></dev:type>
 208 | <dev:defaultValue></dev:defaultValue>
 209 | </command:parameter>
 210 | </command:syntaxItem>
 211 | </command:syntax>
 212 | <command:parameters><command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
 213 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 214 | </maml:para>
 215 | </maml:Description>
 216 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 217 | <dev:type><maml:name>Object</maml:name>
 218 | <maml:uri /></dev:type>
 219 | <dev:defaultValue></dev:defaultValue>
 220 | </command:parameter>
 221 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Location</maml:name>
 222 | <maml:Description><maml:para>Specifies that the query be restricted to a folder located within the Applications folder. Specifying "Install\Broken" for example would restrict the search to the folder "Applications\Install\Broken" in the MDT share.
 223 | </maml:para>
 224 | </maml:Description>
 225 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 226 | <dev:type><maml:name>Object</maml:name>
 227 | <maml:uri /></dev:type>
 228 | <dev:defaultValue></dev:defaultValue>
 229 | </command:parameter>
 230 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
 231 | <maml:Description><maml:para>Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\ adobe\ " would return all the applications that have adobe in their name.
 232 | </maml:para>
 233 | </maml:Description>
 234 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 235 | <dev:type><maml:name>Object</maml:name>
 236 | <maml:uri /></dev:type>
 237 | <dev:defaultValue></dev:defaultValue>
 238 | </command:parameter>
 239 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 240 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 241 | </maml:para>
 242 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 243 | </maml:para>
 244 | <maml:para>or
 245 | </maml:para>
 246 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 247 | </maml:para>
 248 | </maml:Description>
 249 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 250 | <dev:type><maml:name>Object</maml:name>
 251 | <maml:uri /></dev:type>
 252 | <dev:defaultValue></dev:defaultValue>
 253 | </command:parameter>
 254 | </command:parameters>
 255 | <command:inputTypes><command:inputType><dev:type><maml:name>System.Object</maml:name>
 256 | </dev:type>
 257 | <maml:description><maml:para>
 258 | </maml:para>
 259 | </maml:description>
 260 | </command:inputType>
 261 | </command:inputTypes>
 262 | <command:returnValues><command:returnValue><dev:type><maml:name>System.Object</maml:name>
 263 | </dev:type>
 264 | <maml:description><maml:para>
 265 | </maml:para>
 266 | </maml:description>
 267 | </command:returnValue>
 268 | </command:returnValues>
 269 | <maml:alertSet><maml:alert><maml:para>
 270 | </maml:para>
 271 | </maml:alert>
 272 | </maml:alertSet>
 273 | <command:examples><command:example><maml:title>Example 1: Get all applications</maml:title>
 274 | <dev:code>PS C:\&gt;Get-MDTApplication -ShareName MDTProduction</dev:code>
 275 | <dev:remarks><maml:para>This command returns all applications from the MDT share.
 276 | </maml:para>
 277 | </dev:remarks>
 278 | </command:example>
 279 | <command:example><maml:title>Example 2: Get only applications in a certain directory</maml:title>
 280 | <dev:code>PS C:\&gt;Get-MDTApplication -ShareName MDTProduction -Location "APPBUNDLES"</dev:code>
 281 | <dev:remarks><maml:para>This command returns all applications from the MDT share that are located in a folder called "APPBUNDLES" (located under the Applications root folder).
 282 | </maml:para>
 283 | </dev:remarks>
 284 | </command:example>
 285 | <command:example><maml:title>Example 3: Get application by name</maml:title>
 286 | <dev:code>PS C:\&gt;Get-MDTApplication -ShareName MDTProduction -Name "Install - Java 8 - x64"</dev:code>
 287 | <dev:remarks><maml:para>This command returns the application with the name "Install - Java 8 - x64" from the MDT share.
 288 | </maml:para>
 289 | </dev:remarks>
 290 | </command:example>
 291 | <command:example><maml:title>Example 4: Use wildcards to search for applications</maml:title>
 292 | <dev:code>PS C:\&gt;Get-MDTApplication -ShareName MDTProduction -Name *java*</dev:code>
 293 | <dev:remarks><maml:para>This command returns any applications that have the word java somewhere in their name from the MDT share.
 294 | </maml:para>
 295 | </dev:remarks>
 296 | </command:example>
 297 | <command:example><maml:title>Example 5: Get application by GUID</maml:title>
 298 | <dev:code>PS C:\&gt;Get-MDTApplication -ShareName MDTProduction -GUID "{4deefc41-71c2-4f59-bcf7-89fd4629a025}"</dev:code>
 299 | <dev:remarks><maml:para>This command returns the application with the GUID "4deefc41-71c2-4f59-bcf7-89fd4629a025" from the MDT share.
 300 | </maml:para>
 301 | </dev:remarks>
 302 | </command:example>
 303 | </command:examples>
 304 | <command:relatedLinks><maml:navigationLink><maml:linkText>Online Version:</maml:linkText>
 305 | <maml:uri>https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Get-MDTApplication.md</maml:uri>
 306 | </maml:navigationLink>
 307 | </command:relatedLinks>
 308 | </command:command>
 309 | <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
 310 | <command:details><command:name>Get-MDTApplicationDependency</command:name>
 311 | <command:verb>Get</command:verb>
 312 | <command:noun>MDTApplicationDependency</command:noun>
 313 | <maml:description><maml:para>Gets the application dependencies of or more MDT applications
 314 | </maml:para>
 315 | </maml:description>
 316 | </command:details>
 317 | <maml:description><maml:para>The Get-MDTApplicationDependency function either returns all the applications that the application is dependent upon(applications that need to be installed before installing the queried application), or applications upon which the queried application is a dependency. It can go back either just one application, or can recurse the entire depth of the dependency tree.
 318 | </maml:para>
 319 | </maml:description>
 320 | <command:syntax><command:syntaxItem><maml:name>Get-MDTApplicationDependency</maml:name>
 321 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>DependencyType</maml:name>
 322 | <maml:Description><maml:para>Specifies whether to return the parent dependencies of the queried application(applications that need to be installed before installing the queried application), or to return the child dependencies of the queried application(applications where the queried application needs to be installed first). Possible options are ReturnParent and ReturnChild. Default value is ReturnParent.
 323 | </maml:para>
 324 | </maml:Description>
 325 | <command:parameterValueGroup><command:parameterValue required="false" variableLength="false">ReturnParent</command:parameterValue>
 326 | <command:parameterValue required="false" variableLength="false">ReturnChild</command:parameterValue>
 327 | </command:parameterValueGroup>
 328 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 329 | <dev:type><maml:name>Object</maml:name>
 330 | <maml:uri /></dev:type>
 331 | <dev:defaultValue>ReturnParent</dev:defaultValue>
 332 | </command:parameter>
 333 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
 334 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 335 | </maml:para>
 336 | </maml:Description>
 337 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 338 | <dev:type><maml:name>Object</maml:name>
 339 | <maml:uri /></dev:type>
 340 | <dev:defaultValue></dev:defaultValue>
 341 | </command:parameter>
 342 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Recurse</maml:name>
 343 | <maml:Description><maml:para>If specified recurses the dependency tree until it reaches the last dependency. If not, only finds dependencies that are one depth away.
 344 | </maml:para>
 345 | </maml:Description>
 346 | <dev:type><maml:name>SwitchParameter</maml:name>
 347 | <maml:uri /></dev:type>
 348 | <dev:defaultValue>False</dev:defaultValue>
 349 | </command:parameter>
 350 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 351 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 352 | </maml:para>
 353 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 354 | </maml:para>
 355 | <maml:para>or
 356 | </maml:para>
 357 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 358 | </maml:para>
 359 | </maml:Description>
 360 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 361 | <dev:type><maml:name>Object</maml:name>
 362 | <maml:uri /></dev:type>
 363 | <dev:defaultValue></dev:defaultValue>
 364 | </command:parameter>
 365 | </command:syntaxItem>
 366 | <command:syntaxItem><maml:name>Get-MDTApplicationDependency</maml:name>
 367 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>DependencyType</maml:name>
 368 | <maml:Description><maml:para>Specifies whether to return the parent dependencies of the queried application(applications that need to be installed before installing the queried application), or to return the child dependencies of the queried application(applications where the queried application needs to be installed first). Possible options are ReturnParent and ReturnChild. Default value is ReturnParent.
 369 | </maml:para>
 370 | </maml:Description>
 371 | <command:parameterValueGroup><command:parameterValue required="false" variableLength="false">ReturnParent</command:parameterValue>
 372 | <command:parameterValue required="false" variableLength="false">ReturnChild</command:parameterValue>
 373 | </command:parameterValueGroup>
 374 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 375 | <dev:type><maml:name>Object</maml:name>
 376 | <maml:uri /></dev:type>
 377 | <dev:defaultValue>ReturnParent</dev:defaultValue>
 378 | </command:parameter>
 379 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
 380 | <maml:Description><maml:para>Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\ adobe\ " would return all the applications that have adobe in their name.
 381 | </maml:para>
 382 | </maml:Description>
 383 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 384 | <dev:type><maml:name>Object</maml:name>
 385 | <maml:uri /></dev:type>
 386 | <dev:defaultValue></dev:defaultValue>
 387 | </command:parameter>
 388 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Recurse</maml:name>
 389 | <maml:Description><maml:para>If specified recurses the dependency tree until it reaches the last dependency. If not, only finds dependencies that are one depth away.
 390 | </maml:para>
 391 | </maml:Description>
 392 | <dev:type><maml:name>SwitchParameter</maml:name>
 393 | <maml:uri /></dev:type>
 394 | <dev:defaultValue>False</dev:defaultValue>
 395 | </command:parameter>
 396 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 397 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 398 | </maml:para>
 399 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 400 | </maml:para>
 401 | <maml:para>or
 402 | </maml:para>
 403 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 404 | </maml:para>
 405 | </maml:Description>
 406 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 407 | <dev:type><maml:name>Object</maml:name>
 408 | <maml:uri /></dev:type>
 409 | <dev:defaultValue></dev:defaultValue>
 410 | </command:parameter>
 411 | </command:syntaxItem>
 412 | </command:syntax>
 413 | <command:parameters><command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>DependencyType</maml:name>
 414 | <maml:Description><maml:para>Specifies whether to return the parent dependencies of the queried application(applications that need to be installed before installing the queried application), or to return the child dependencies of the queried application(applications where the queried application needs to be installed first). Possible options are ReturnParent and ReturnChild. Default value is ReturnParent.
 415 | </maml:para>
 416 | </maml:Description>
 417 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 418 | <dev:type><maml:name>Object</maml:name>
 419 | <maml:uri /></dev:type>
 420 | <dev:defaultValue>ReturnParent</dev:defaultValue>
 421 | </command:parameter>
 422 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
 423 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 424 | </maml:para>
 425 | </maml:Description>
 426 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 427 | <dev:type><maml:name>Object</maml:name>
 428 | <maml:uri /></dev:type>
 429 | <dev:defaultValue></dev:defaultValue>
 430 | </command:parameter>
 431 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
 432 | <maml:Description><maml:para>Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\ adobe\ " would return all the applications that have adobe in their name.
 433 | </maml:para>
 434 | </maml:Description>
 435 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 436 | <dev:type><maml:name>Object</maml:name>
 437 | <maml:uri /></dev:type>
 438 | <dev:defaultValue></dev:defaultValue>
 439 | </command:parameter>
 440 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Recurse</maml:name>
 441 | <maml:Description><maml:para>If specified recurses the dependency tree until it reaches the last dependency. If not, only finds dependencies that are one depth away.
 442 | </maml:para>
 443 | </maml:Description>
 444 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
 445 | <dev:type><maml:name>SwitchParameter</maml:name>
 446 | <maml:uri /></dev:type>
 447 | <dev:defaultValue>False</dev:defaultValue>
 448 | </command:parameter>
 449 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 450 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 451 | </maml:para>
 452 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 453 | </maml:para>
 454 | <maml:para>or
 455 | </maml:para>
 456 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 457 | </maml:para>
 458 | </maml:Description>
 459 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 460 | <dev:type><maml:name>Object</maml:name>
 461 | <maml:uri /></dev:type>
 462 | <dev:defaultValue></dev:defaultValue>
 463 | </command:parameter>
 464 | </command:parameters>
 465 | <command:inputTypes><command:inputType><dev:type><maml:name>System.Object</maml:name>
 466 | </dev:type>
 467 | <maml:description><maml:para>
 468 | </maml:para>
 469 | </maml:description>
 470 | </command:inputType>
 471 | </command:inputTypes>
 472 | <command:returnValues><command:returnValue><dev:type><maml:name>System.Object</maml:name>
 473 | </dev:type>
 474 | <maml:description><maml:para>
 475 | </maml:para>
 476 | </maml:description>
 477 | </command:returnValue>
 478 | </command:returnValues>
 479 | <maml:alertSet><maml:alert><maml:para>
 480 | </maml:para>
 481 | </maml:alert>
 482 | </maml:alertSet>
 483 | <command:examples><command:example><maml:title>Example 1: Get any direct parent dependencies of an app</maml:title>
 484 | <dev:code>PS C:\&gt; Get-MDTApplicationDependency -ShareName MDTProduction -Name "Install - Java Development Kit - x64"</dev:code>
 485 | <dev:remarks><maml:para>Returns only applications that will be installed directly before the Java JDK is installed.
 486 | </maml:para>
 487 | </dev:remarks>
 488 | </command:example>
 489 | <command:example><maml:title>Example 2: Get any direct child dependencies of an app</maml:title>
 490 | <dev:code>PS C:\&gt; Get-MDTApplicationDependency -ShareName MDTProduction -Name "Install - Java Development Kit - x64" -DependencyType ReturnChild</dev:code>
 491 | <dev:remarks><maml:para>Returns only applications that will install the Java JDK directly after they themselves are installed
 492 | </maml:para>
 493 | </dev:remarks>
 494 | </command:example>
 495 | <command:example><maml:title>Example 3: Get **all** parent dependencies of an app</maml:title>
 496 | <dev:code>PS C:\&gt; Get-MDTApplicationDependency -ShareName MDTProduction -Name "Install - Java Development Kit - x64" -Recurse</dev:code>
 497 | <dev:remarks><maml:para>Returns all applications that need to be installed before the Java JDK is installed.
 498 | </maml:para>
 499 | </dev:remarks>
 500 | </command:example>
 501 | <command:example><maml:title>Example 4: Get **all** child dependencies of an app</maml:title>
 502 | <dev:code>PS C:\&gt; Get-MDTApplicationDependency -ShareName MDTProduction -Name "Install - Java Development Kit - x64" -Recurse -DependencyType ReturnChild</dev:code>
 503 | <dev:remarks><maml:para>Returns all applications that will be installed after the Java JDK is installed
 504 | </maml:para>
 505 | </dev:remarks>
 506 | </command:example>
 507 | </command:examples>
 508 | <command:relatedLinks><maml:navigationLink><maml:linkText>Online Version:</maml:linkText>
 509 | <maml:uri>https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Get-MDTApplicationDependency.md</maml:uri>
 510 | </maml:navigationLink>
 511 | </command:relatedLinks>
 512 | </command:command>
 513 | <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
 514 | <command:details><command:name>Get-MDTApplicationSupportedPlatform</command:name>
 515 | <command:verb>Get</command:verb>
 516 | <command:noun>MDTApplicationSupportedPlatform</command:noun>
 517 | <maml:description><maml:para>Gets the SupportedPlatform attribute of or more MDT applications
 518 | </maml:para>
 519 | </maml:description>
 520 | </command:details>
 521 | <maml:description><maml:para>The Get-MDTApplicationSupportedPlatform function can either return the SupportedPlatform attribute of a queried application(via the name or GUID) parameter, return it for all applications, or return just applications that have it set(or not).
 522 | </maml:para>
 523 | </maml:description>
 524 | <command:syntax><command:syntaxItem><maml:name>Get-MDTApplicationSupportedPlatform</maml:name>
 525 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
 526 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 527 | </maml:para>
 528 | </maml:Description>
 529 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 530 | <dev:type><maml:name>Object</maml:name>
 531 | <maml:uri /></dev:type>
 532 | <dev:defaultValue></dev:defaultValue>
 533 | </command:parameter>
 534 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 535 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 536 | </maml:para>
 537 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 538 | </maml:para>
 539 | <maml:para>or
 540 | </maml:para>
 541 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 542 | </maml:para>
 543 | </maml:Description>
 544 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 545 | <dev:type><maml:name>Object</maml:name>
 546 | <maml:uri /></dev:type>
 547 | <dev:defaultValue></dev:defaultValue>
 548 | </command:parameter>
 549 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>SupportedPlatformSet</maml:name>
 550 | <maml:Description><maml:para>Specifies in the query whether to return just Applications that have it set(Yes), just Applications that do NOT have it set(No), or to return Applications that both states(All).
 551 | </maml:para>
 552 | </maml:Description>
 553 | <command:parameterValueGroup><command:parameterValue required="false" variableLength="false">Yes</command:parameterValue>
 554 | <command:parameterValue required="false" variableLength="false">No</command:parameterValue>
 555 | <command:parameterValue required="false" variableLength="false">All</command:parameterValue>
 556 | </command:parameterValueGroup>
 557 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 558 | <dev:type><maml:name>Object</maml:name>
 559 | <maml:uri /></dev:type>
 560 | <dev:defaultValue>All</dev:defaultValue>
 561 | </command:parameter>
 562 | </command:syntaxItem>
 563 | <command:syntaxItem><maml:name>Get-MDTApplicationSupportedPlatform</maml:name>
 564 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
 565 | <maml:Description><maml:para>Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\ adobe\ " would return all the applications that have adobe in their name.
 566 | </maml:para>
 567 | </maml:Description>
 568 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 569 | <dev:type><maml:name>Object</maml:name>
 570 | <maml:uri /></dev:type>
 571 | <dev:defaultValue></dev:defaultValue>
 572 | </command:parameter>
 573 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 574 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 575 | </maml:para>
 576 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 577 | </maml:para>
 578 | <maml:para>or
 579 | </maml:para>
 580 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 581 | </maml:para>
 582 | </maml:Description>
 583 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 584 | <dev:type><maml:name>Object</maml:name>
 585 | <maml:uri /></dev:type>
 586 | <dev:defaultValue></dev:defaultValue>
 587 | </command:parameter>
 588 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>SupportedPlatformSet</maml:name>
 589 | <maml:Description><maml:para>Specifies in the query whether to return just Applications that have it set(Yes), just Applications that do NOT have it set(No), or to return Applications that both states(All).
 590 | </maml:para>
 591 | </maml:Description>
 592 | <command:parameterValueGroup><command:parameterValue required="false" variableLength="false">Yes</command:parameterValue>
 593 | <command:parameterValue required="false" variableLength="false">No</command:parameterValue>
 594 | <command:parameterValue required="false" variableLength="false">All</command:parameterValue>
 595 | </command:parameterValueGroup>
 596 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 597 | <dev:type><maml:name>Object</maml:name>
 598 | <maml:uri /></dev:type>
 599 | <dev:defaultValue>All</dev:defaultValue>
 600 | </command:parameter>
 601 | </command:syntaxItem>
 602 | </command:syntax>
 603 | <command:parameters><command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
 604 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 605 | </maml:para>
 606 | </maml:Description>
 607 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 608 | <dev:type><maml:name>Object</maml:name>
 609 | <maml:uri /></dev:type>
 610 | <dev:defaultValue></dev:defaultValue>
 611 | </command:parameter>
 612 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
 613 | <maml:Description><maml:para>Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\ adobe\ " would return all the applications that have adobe in their name.
 614 | </maml:para>
 615 | </maml:Description>
 616 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 617 | <dev:type><maml:name>Object</maml:name>
 618 | <maml:uri /></dev:type>
 619 | <dev:defaultValue></dev:defaultValue>
 620 | </command:parameter>
 621 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 622 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 623 | </maml:para>
 624 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 625 | </maml:para>
 626 | <maml:para>or
 627 | </maml:para>
 628 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 629 | </maml:para>
 630 | </maml:Description>
 631 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 632 | <dev:type><maml:name>Object</maml:name>
 633 | <maml:uri /></dev:type>
 634 | <dev:defaultValue></dev:defaultValue>
 635 | </command:parameter>
 636 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>SupportedPlatformSet</maml:name>
 637 | <maml:Description><maml:para>Specifies in the query whether to return just Applications that have it set(Yes), just Applications that do NOT have it set(No), or to return Applications that both states(All).
 638 | </maml:para>
 639 | </maml:Description>
 640 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 641 | <dev:type><maml:name>Object</maml:name>
 642 | <maml:uri /></dev:type>
 643 | <dev:defaultValue>All</dev:defaultValue>
 644 | </command:parameter>
 645 | </command:parameters>
 646 | <command:inputTypes><command:inputType><dev:type><maml:name>System.Object</maml:name>
 647 | </dev:type>
 648 | <maml:description><maml:para>
 649 | </maml:para>
 650 | </maml:description>
 651 | </command:inputType>
 652 | </command:inputTypes>
 653 | <command:returnValues><command:returnValue><dev:type><maml:name>System.Object</maml:name>
 654 | </dev:type>
 655 | <maml:description><maml:para>
 656 | </maml:para>
 657 | </maml:description>
 658 | </command:returnValue>
 659 | </command:returnValues>
 660 | <maml:alertSet><maml:alert><maml:para>
 661 | </maml:para>
 662 | </maml:alert>
 663 | </maml:alertSet>
 664 | <command:examples><command:example><maml:title>Example 1: Get all applications where the SupportedPlatform attribute is set(to anything)</maml:title>
 665 | <dev:code>PS C:\&gt; Get-MDTApplicationSupportedPlatform -ShareName TESTSHARE -SupportedPlatformSet Yes</dev:code>
 666 | <dev:remarks><maml:para>Returns all applications where SupportedPlatform is set.
 667 | </maml:para>
 668 | </dev:remarks>
 669 | </command:example>
 670 | <command:example><maml:title>Example 2: Get all applications where the SupportedPlatform attribute is NOT set.</maml:title>
 671 | <dev:code>PS C:\&gt; Get-MDTApplicationSupportedPlatform -ShareName TESTSHARE -SupportedPlatformSet No</dev:code>
 672 | <dev:remarks><maml:para>Returns all applications where SupportedPlatform is NOT set.
 673 | </maml:para>
 674 | </dev:remarks>
 675 | </command:example>
 676 | <command:example><maml:title>Example 3: Get SupportedPlatform attribute of specific application.</maml:title>
 677 | <dev:code>PS C:\&gt; Get-MDTApplicationSupportedPlatform -ShareName TESTSHARE -Name "Install - Google Chrome -x64" -SupportedPlatformSet All</dev:code>
 678 | <dev:remarks><maml:para>Returns the queried application along with it's SupportedPlatform attribute
 679 | </maml:para>
 680 | </dev:remarks>
 681 | </command:example>
 682 | </command:examples>
 683 | <command:relatedLinks><maml:navigationLink><maml:linkText>Online Version:</maml:linkText>
 684 | <maml:uri>https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Get-MDTApplicationSupportedPlatform.md</maml:uri>
 685 | </maml:navigationLink>
 686 | </command:relatedLinks>
 687 | </command:command>
 688 | <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
 689 | <command:details><command:name>Get-MDTDrive</command:name>
 690 | <command:verb>Get</command:verb>
 691 | <command:noun>MDTDrive</command:noun>
 692 | <maml:description><maml:para>{{Fill in the Synopsis}}
 693 | </maml:para>
 694 | </maml:description>
 695 | </command:details>
 696 | <maml:description><maml:para>{{Fill in the Description}}
 697 | </maml:para>
 698 | </maml:description>
 699 | <command:syntax><command:syntaxItem><maml:name>Get-MDTDrive</maml:name>
 700 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="0" aliases="none"><maml:name>Name</maml:name>
 701 | <maml:Description><maml:para>{{Fill Name Description}}
 702 | </maml:para>
 703 | </maml:Description>
 704 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 705 | <dev:type><maml:name>Object</maml:name>
 706 | <maml:uri /></dev:type>
 707 | <dev:defaultValue></dev:defaultValue>
 708 | </command:parameter>
 709 | </command:syntaxItem>
 710 | </command:syntax>
 711 | <command:parameters><command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="0" aliases="none"><maml:name>Name</maml:name>
 712 | <maml:Description><maml:para>{{Fill Name Description}}
 713 | </maml:para>
 714 | </maml:Description>
 715 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 716 | <dev:type><maml:name>Object</maml:name>
 717 | <maml:uri /></dev:type>
 718 | <dev:defaultValue></dev:defaultValue>
 719 | </command:parameter>
 720 | </command:parameters>
 721 | <command:inputTypes><command:inputType><dev:type><maml:name>None</maml:name>
 722 | </dev:type>
 723 | <maml:description><maml:para>
 724 | </maml:para>
 725 | </maml:description>
 726 | </command:inputType>
 727 | </command:inputTypes>
 728 | <command:returnValues><command:returnValue><dev:type><maml:name>System.Object</maml:name>
 729 | </dev:type>
 730 | <maml:description><maml:para>
 731 | </maml:para>
 732 | </maml:description>
 733 | </command:returnValue>
 734 | </command:returnValues>
 735 | <maml:alertSet><maml:alert><maml:para>
 736 | </maml:para>
 737 | </maml:alert>
 738 | </maml:alertSet>
 739 | <command:examples><command:example><maml:title>Example 1</maml:title>
 740 | <dev:code>PS C:\&gt; {{ Add example code here }}</dev:code>
 741 | <dev:remarks><maml:para>{{ Add example description here }}
 742 | </maml:para>
 743 | </dev:remarks>
 744 | </command:example>
 745 | </command:examples>
 746 | <command:relatedLinks></command:relatedLinks>
 747 | </command:command>
 748 | <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
 749 | <command:details><command:name>Import-MDTModule</command:name>
 750 | <command:verb>Import</command:verb>
 751 | <command:noun>MDTModule</command:noun>
 752 | <maml:description><maml:para>{{Fill in the Synopsis}}
 753 | </maml:para>
 754 | </maml:description>
 755 | </command:details>
 756 | <maml:description><maml:para>{{Fill in the Description}}
 757 | </maml:para>
 758 | </maml:description>
 759 | <command:syntax><command:syntaxItem><maml:name>Import-MDTModule</maml:name>
 760 | </command:syntaxItem>
 761 | </command:syntax>
 762 | <command:parameters></command:parameters>
 763 | <command:inputTypes><command:inputType><dev:type><maml:name>None</maml:name>
 764 | </dev:type>
 765 | <maml:description><maml:para>
 766 | </maml:para>
 767 | </maml:description>
 768 | </command:inputType>
 769 | </command:inputTypes>
 770 | <command:returnValues><command:returnValue><dev:type><maml:name>System.Object</maml:name>
 771 | </dev:type>
 772 | <maml:description><maml:para>
 773 | </maml:para>
 774 | </maml:description>
 775 | </command:returnValue>
 776 | </command:returnValues>
 777 | <maml:alertSet><maml:alert><maml:para>
 778 | </maml:para>
 779 | </maml:alert>
 780 | </maml:alertSet>
 781 | <command:examples><command:example><maml:title>Example 1</maml:title>
 782 | <dev:code>PS C:\&gt; {{ Add example code here }}</dev:code>
 783 | <dev:remarks><maml:para>{{ Add example description here }}
 784 | </maml:para>
 785 | </dev:remarks>
 786 | </command:example>
 787 | </command:examples>
 788 | <command:relatedLinks></command:relatedLinks>
 789 | </command:command>
 790 | <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
 791 | <command:details><command:name>Rename-MDTApplication</command:name>
 792 | <command:verb>Rename</command:verb>
 793 | <command:noun>MDTApplication</command:noun>
 794 | <maml:description><maml:para>Renames an MDT application.
 795 | </maml:para>
 796 | </maml:description>
 797 | </command:details>
 798 | <maml:description><maml:para>The Rename-MDTApplication function renames an MDT application, optionally also renaming the source directory if the applications source files have been imported into MDT. Applications to be renamed can be specified by either their Name or their GUID.
 799 | </maml:para>
 800 | </maml:description>
 801 | <command:syntax><command:syntaxItem><maml:name>Rename-MDTApplication</maml:name>
 802 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="cf"><maml:name>Confirm</maml:name>
 803 | <maml:Description><maml:para>The confirm preference. If left alone, will prompt you before modifying each application. If set to $false, it just goes through.
 804 | </maml:para>
 805 | </maml:Description>
 806 | <dev:type><maml:name>SwitchParameter</maml:name>
 807 | <maml:uri /></dev:type>
 808 | <dev:defaultValue>$true</dev:defaultValue>
 809 | </command:parameter>
 810 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Force</maml:name>
 811 | <maml:Description><maml:para>If specified, disables the checks to verify that 1: the app to be renamed exists and 2: that new name isn't already in use. Use carefully.
 812 | </maml:para>
 813 | </maml:Description>
 814 | <dev:type><maml:name>SwitchParameter</maml:name>
 815 | <maml:uri /></dev:type>
 816 | <dev:defaultValue>$false</dev:defaultValue>
 817 | </command:parameter>
 818 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
 819 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 820 | </maml:para>
 821 | </maml:Description>
 822 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 823 | <dev:type><maml:name>Object</maml:name>
 824 | <maml:uri /></dev:type>
 825 | <dev:defaultValue></dev:defaultValue>
 826 | </command:parameter>
 827 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>NewName</maml:name>
 828 | <maml:Description><maml:para>Specifies what the new name of the application will be once renamed. Rename-MDTApplication will check the existing applications to make sure there are no duplicates before making any changes.
 829 | </maml:para>
 830 | </maml:Description>
 831 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 832 | <dev:type><maml:name>Object</maml:name>
 833 | <maml:uri /></dev:type>
 834 | <dev:defaultValue></dev:defaultValue>
 835 | </command:parameter>
 836 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>RenameSource</maml:name>
 837 | <maml:Description><maml:para>If specified, will also rename the actual application source folder inside of the MDT share. This parameter will only process if the application has it's source files located within the MDT share(the three MDT app types are "apps with source files", "apps with sources on network or elsewhere", and "app bundles". this parameter only processes the first of these three).
 838 | </maml:para>
 839 | </maml:Description>
 840 | <dev:type><maml:name>SwitchParameter</maml:name>
 841 | <maml:uri /></dev:type>
 842 | <dev:defaultValue>$false</dev:defaultValue>
 843 | </command:parameter>
 844 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 845 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 846 | </maml:para>
 847 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 848 | </maml:para>
 849 | <maml:para>or
 850 | </maml:para>
 851 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 852 | </maml:para>
 853 | </maml:Description>
 854 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 855 | <dev:type><maml:name>Object</maml:name>
 856 | <maml:uri /></dev:type>
 857 | <dev:defaultValue></dev:defaultValue>
 858 | </command:parameter>
 859 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="wi"><maml:name>WhatIf</maml:name>
 860 | <maml:Description><maml:para>If specified, will output what changes the command will make without making them.
 861 | </maml:para>
 862 | </maml:Description>
 863 | <dev:type><maml:name>SwitchParameter</maml:name>
 864 | <maml:uri /></dev:type>
 865 | <dev:defaultValue>False</dev:defaultValue>
 866 | </command:parameter>
 867 | </command:syntaxItem>
 868 | <command:syntaxItem><maml:name>Rename-MDTApplication</maml:name>
 869 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="cf"><maml:name>Confirm</maml:name>
 870 | <maml:Description><maml:para>The confirm preference. If left alone, will prompt you before modifying each application. If set to $false, it just goes through.
 871 | </maml:para>
 872 | </maml:Description>
 873 | <dev:type><maml:name>SwitchParameter</maml:name>
 874 | <maml:uri /></dev:type>
 875 | <dev:defaultValue>$true</dev:defaultValue>
 876 | </command:parameter>
 877 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Force</maml:name>
 878 | <maml:Description><maml:para>If specified, disables the checks to verify that 1: the app to be renamed exists and 2: that new name isn't already in use. Use carefully.
 879 | </maml:para>
 880 | </maml:Description>
 881 | <dev:type><maml:name>SwitchParameter</maml:name>
 882 | <maml:uri /></dev:type>
 883 | <dev:defaultValue>$false</dev:defaultValue>
 884 | </command:parameter>
 885 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
 886 | <maml:Description><maml:para>Specifies the Name of an application to query the MDT share for. Alternate to GUID Parameter.
 887 | </maml:para>
 888 | </maml:Description>
 889 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 890 | <dev:type><maml:name>Object</maml:name>
 891 | <maml:uri /></dev:type>
 892 | <dev:defaultValue></dev:defaultValue>
 893 | </command:parameter>
 894 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>NewName</maml:name>
 895 | <maml:Description><maml:para>Specifies what the new name of the application will be once renamed. Rename-MDTApplication will check the existing applications to make sure there are no duplicates before making any changes.
 896 | </maml:para>
 897 | </maml:Description>
 898 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 899 | <dev:type><maml:name>Object</maml:name>
 900 | <maml:uri /></dev:type>
 901 | <dev:defaultValue></dev:defaultValue>
 902 | </command:parameter>
 903 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>RenameSource</maml:name>
 904 | <maml:Description><maml:para>If specified, will also rename the actual application source folder inside of the MDT share. This parameter will only process if the application has it's source files located within the MDT share(the three MDT app types are "apps with source files", "apps with sources on network or elsewhere", and "app bundles". this parameter only processes the first of these three).
 905 | </maml:para>
 906 | </maml:Description>
 907 | <dev:type><maml:name>SwitchParameter</maml:name>
 908 | <maml:uri /></dev:type>
 909 | <dev:defaultValue>$false</dev:defaultValue>
 910 | </command:parameter>
 911 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 912 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 913 | </maml:para>
 914 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 915 | </maml:para>
 916 | <maml:para>or
 917 | </maml:para>
 918 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 919 | </maml:para>
 920 | </maml:Description>
 921 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 922 | <dev:type><maml:name>Object</maml:name>
 923 | <maml:uri /></dev:type>
 924 | <dev:defaultValue></dev:defaultValue>
 925 | </command:parameter>
 926 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="wi"><maml:name>WhatIf</maml:name>
 927 | <maml:Description><maml:para>If specified, will output what changes the command will make without making them.
 928 | </maml:para>
 929 | </maml:Description>
 930 | <dev:type><maml:name>SwitchParameter</maml:name>
 931 | <maml:uri /></dev:type>
 932 | <dev:defaultValue>False</dev:defaultValue>
 933 | </command:parameter>
 934 | </command:syntaxItem>
 935 | </command:syntax>
 936 | <command:parameters><command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="cf"><maml:name>Confirm</maml:name>
 937 | <maml:Description><maml:para>The confirm preference. If left alone, will prompt you before modifying each application. If set to $false, it just goes through.
 938 | </maml:para>
 939 | </maml:Description>
 940 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
 941 | <dev:type><maml:name>SwitchParameter</maml:name>
 942 | <maml:uri /></dev:type>
 943 | <dev:defaultValue>$true</dev:defaultValue>
 944 | </command:parameter>
 945 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Force</maml:name>
 946 | <maml:Description><maml:para>If specified, disables the checks to verify that 1: the app to be renamed exists and 2: that new name isn't already in use. Use carefully.
 947 | </maml:para>
 948 | </maml:Description>
 949 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
 950 | <dev:type><maml:name>SwitchParameter</maml:name>
 951 | <maml:uri /></dev:type>
 952 | <dev:defaultValue>$false</dev:defaultValue>
 953 | </command:parameter>
 954 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
 955 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
 956 | </maml:para>
 957 | </maml:Description>
 958 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 959 | <dev:type><maml:name>Object</maml:name>
 960 | <maml:uri /></dev:type>
 961 | <dev:defaultValue></dev:defaultValue>
 962 | </command:parameter>
 963 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
 964 | <maml:Description><maml:para>Specifies the Name of an application to query the MDT share for. Alternate to GUID Parameter.
 965 | </maml:para>
 966 | </maml:Description>
 967 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 968 | <dev:type><maml:name>Object</maml:name>
 969 | <maml:uri /></dev:type>
 970 | <dev:defaultValue></dev:defaultValue>
 971 | </command:parameter>
 972 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>NewName</maml:name>
 973 | <maml:Description><maml:para>Specifies what the new name of the application will be once renamed. Rename-MDTApplication will check the existing applications to make sure there are no duplicates before making any changes.
 974 | </maml:para>
 975 | </maml:Description>
 976 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
 977 | <dev:type><maml:name>Object</maml:name>
 978 | <maml:uri /></dev:type>
 979 | <dev:defaultValue></dev:defaultValue>
 980 | </command:parameter>
 981 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>RenameSource</maml:name>
 982 | <maml:Description><maml:para>If specified, will also rename the actual application source folder inside of the MDT share. This parameter will only process if the application has it's source files located within the MDT share(the three MDT app types are "apps with source files", "apps with sources on network or elsewhere", and "app bundles". this parameter only processes the first of these three).
 983 | </maml:para>
 984 | </maml:Description>
 985 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
 986 | <dev:type><maml:name>SwitchParameter</maml:name>
 987 | <maml:uri /></dev:type>
 988 | <dev:defaultValue>$false</dev:defaultValue>
 989 | </command:parameter>
 990 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
 991 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
 992 | </maml:para>
 993 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
 994 | </maml:para>
 995 | <maml:para>or
 996 | </maml:para>
 997 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
 998 | </maml:para>
 999 | </maml:Description>
1000 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1001 | <dev:type><maml:name>Object</maml:name>
1002 | <maml:uri /></dev:type>
1003 | <dev:defaultValue></dev:defaultValue>
1004 | </command:parameter>
1005 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="wi"><maml:name>WhatIf</maml:name>
1006 | <maml:Description><maml:para>If specified, will output what changes the command will make without making them.
1007 | </maml:para>
1008 | </maml:Description>
1009 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
1010 | <dev:type><maml:name>SwitchParameter</maml:name>
1011 | <maml:uri /></dev:type>
1012 | <dev:defaultValue>False</dev:defaultValue>
1013 | </command:parameter>
1014 | </command:parameters>
1015 | <command:inputTypes><command:inputType><dev:type><maml:name>System.Object</maml:name>
1016 | </dev:type>
1017 | <maml:description><maml:para>
1018 | </maml:para>
1019 | </maml:description>
1020 | </command:inputType>
1021 | </command:inputTypes>
1022 | <command:returnValues><command:returnValue><dev:type><maml:name>System.Object</maml:name>
1023 | </dev:type>
1024 | <maml:description><maml:para>
1025 | </maml:para>
1026 | </maml:description>
1027 | </command:returnValue>
1028 | </command:returnValues>
1029 | <maml:alertSet><maml:alert><maml:para>
1030 | </maml:para>
1031 | </maml:alert>
1032 | </maml:alertSet>
1033 | <command:examples><command:example><maml:title>Example 1: Rename an application</maml:title>
1034 | <dev:code>PS C:\&gt; Rename-MDTApplication -ShareName MDTProduction -Name "APP1" -NewName "APP2"</dev:code>
1035 | <dev:remarks><maml:para>Renames APP1 to APP2(changes the "Name" and "ShortName" attributes)
1036 | </maml:para>
1037 | </dev:remarks>
1038 | </command:example>
1039 | <command:example><maml:title>Example 2: Rename an application, also renaming it's source directory</maml:title>
1040 | <dev:code>PS C:\&gt; Rename-MDTApplication -ShareName MDTProduction -Name "APP1" -NewName "APP2" -RenameSource</dev:code>
1041 | <dev:remarks><maml:para>Renames APP1 to APP2, also changing the source directory name from APP1 to APP2(changes the "Name", "ShortName", "Source", and "WorkingDirectory" attributes, also renaming the source directory itself)
1042 | </maml:para>
1043 | </dev:remarks>
1044 | </command:example>
1045 | <command:example><maml:title>Example 3: Rename an application, also renaming it's source directory</maml:title>
1046 | <dev:code>PS C:\&gt; Rename-MDTApplication -ShareName MDTProduction -Name "APP1" -NewName "APP2" -Force</dev:code>
1047 | <dev:remarks><maml:para>Renames APP1 to APP2, with the Force parameter disabling the check to see if the application to be renamed exists in the MDT share, and also the check to see if the New Name is already in use by another MDT application. Use with caution.
1048 | </maml:para>
1049 | </dev:remarks>
1050 | </command:example>
1051 | </command:examples>
1052 | <command:relatedLinks><maml:navigationLink><maml:linkText>Online Version:</maml:linkText>
1053 | <maml:uri>https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Rename-MDTApplication.md</maml:uri>
1054 | </maml:navigationLink>
1055 | </command:relatedLinks>
1056 | </command:command>
1057 | <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
1058 | <command:details><command:name>Set-MDTApplicationSupportedPlatform</command:name>
1059 | <command:verb>Set</command:verb>
1060 | <command:noun>MDTApplicationSupportedPlatform</command:noun>
1061 | <maml:description><maml:para>Sets the SupportedPlatform attribute of or more MDT applications
1062 | </maml:para>
1063 | </maml:description>
1064 | </command:details>
1065 | <maml:description><maml:para>The Set-MDTApplicationSupportedPlatform function sets the SupportedPlatform attribute on one or more MDT applications. It can either set the attribute to Null, or can set it to one of the predefined OS's. The OS restriction types are a bit more granular when setting this attribute via MDT's GUI, so due to the complexity behind scripting each one, broader "catch-all" types are used. At the moment this tool also disregards any previous settings of the attribute, so any previous settings will be overwritten with the new data specified by the command.
1066 | </maml:para>
1067 | </maml:description>
1068 | <command:syntax><command:syntaxItem><maml:name>Set-MDTApplicationSupportedPlatform</maml:name>
1069 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="cf"><maml:name>Confirm</maml:name>
1070 | <maml:Description><maml:para>The confirm preference. If left alone, will prompt you before modifying each application. If set to $false, it just goes through.
1071 | </maml:para>
1072 | </maml:Description>
1073 | <dev:type><maml:name>SwitchParameter</maml:name>
1074 | <maml:uri /></dev:type>
1075 | <dev:defaultValue>$true</dev:defaultValue>
1076 | </command:parameter>
1077 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
1078 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
1079 | </maml:para>
1080 | </maml:Description>
1081 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1082 | <dev:type><maml:name>Object</maml:name>
1083 | <maml:uri /></dev:type>
1084 | <dev:defaultValue></dev:defaultValue>
1085 | </command:parameter>
1086 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>SetSupportedPlatformTo</maml:name>
1087 | <maml:Description><maml:para>Specifies what OS restriction to apply to the application(or to remove the restriction by selecting Null). The OS restriction types are a bit more granular when setting this attribute via MDT's GUI, so due to the complexity behind scripting each one, broader "catch-all" types are used. At the moment this tool also disregards any previous settings of the attribute, so any previous settings will be overwritten with the new data specified here.
1088 | </maml:para>
1089 | </maml:Description>
1090 | <command:parameterValueGroup><command:parameterValue required="false" variableLength="false">Null</command:parameterValue>
1091 | <command:parameterValue required="false" variableLength="false">Windows7Only</command:parameterValue>
1092 | <command:parameterValue required="false" variableLength="false">Windows8Only</command:parameterValue>
1093 | <command:parameterValue required="false" variableLength="false">Windows8.1Only</command:parameterValue>
1094 | <command:parameterValue required="false" variableLength="false">Windows10Only</command:parameterValue>
1095 | </command:parameterValueGroup>
1096 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1097 | <dev:type><maml:name>Object</maml:name>
1098 | <maml:uri /></dev:type>
1099 | <dev:defaultValue></dev:defaultValue>
1100 | </command:parameter>
1101 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
1102 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
1103 | </maml:para>
1104 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
1105 | </maml:para>
1106 | <maml:para>or
1107 | </maml:para>
1108 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
1109 | </maml:para>
1110 | </maml:Description>
1111 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1112 | <dev:type><maml:name>Object</maml:name>
1113 | <maml:uri /></dev:type>
1114 | <dev:defaultValue></dev:defaultValue>
1115 | </command:parameter>
1116 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="wi"><maml:name>WhatIf</maml:name>
1117 | <maml:Description><maml:para>If specified, will output what changes the command will make without making them.
1118 | </maml:para>
1119 | </maml:Description>
1120 | <dev:type><maml:name>SwitchParameter</maml:name>
1121 | <maml:uri /></dev:type>
1122 | <dev:defaultValue>False</dev:defaultValue>
1123 | </command:parameter>
1124 | </command:syntaxItem>
1125 | <command:syntaxItem><maml:name>Set-MDTApplicationSupportedPlatform</maml:name>
1126 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="cf"><maml:name>Confirm</maml:name>
1127 | <maml:Description><maml:para>The confirm preference. If left alone, will prompt you before modifying each application. If set to $false, it just goes through.
1128 | </maml:para>
1129 | </maml:Description>
1130 | <dev:type><maml:name>SwitchParameter</maml:name>
1131 | <maml:uri /></dev:type>
1132 | <dev:defaultValue>$true</dev:defaultValue>
1133 | </command:parameter>
1134 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
1135 | <maml:Description><maml:para>Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\ adobe\ " would return all the applications that have adobe in their name.
1136 | </maml:para>
1137 | </maml:Description>
1138 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1139 | <dev:type><maml:name>Object</maml:name>
1140 | <maml:uri /></dev:type>
1141 | <dev:defaultValue></dev:defaultValue>
1142 | </command:parameter>
1143 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>SetSupportedPlatformTo</maml:name>
1144 | <maml:Description><maml:para>Specifies what OS restriction to apply to the application(or to remove the restriction by selecting Null). The OS restriction types are a bit more granular when setting this attribute via MDT's GUI, so due to the complexity behind scripting each one, broader "catch-all" types are used. At the moment this tool also disregards any previous settings of the attribute, so any previous settings will be overwritten with the new data specified here.
1145 | </maml:para>
1146 | </maml:Description>
1147 | <command:parameterValueGroup><command:parameterValue required="false" variableLength="false">Null</command:parameterValue>
1148 | <command:parameterValue required="false" variableLength="false">Windows7Only</command:parameterValue>
1149 | <command:parameterValue required="false" variableLength="false">Windows8Only</command:parameterValue>
1150 | <command:parameterValue required="false" variableLength="false">Windows8.1Only</command:parameterValue>
1151 | <command:parameterValue required="false" variableLength="false">Windows10Only</command:parameterValue>
1152 | </command:parameterValueGroup>
1153 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1154 | <dev:type><maml:name>Object</maml:name>
1155 | <maml:uri /></dev:type>
1156 | <dev:defaultValue></dev:defaultValue>
1157 | </command:parameter>
1158 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
1159 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
1160 | </maml:para>
1161 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
1162 | </maml:para>
1163 | <maml:para>or
1164 | </maml:para>
1165 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
1166 | </maml:para>
1167 | </maml:Description>
1168 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1169 | <dev:type><maml:name>Object</maml:name>
1170 | <maml:uri /></dev:type>
1171 | <dev:defaultValue></dev:defaultValue>
1172 | </command:parameter>
1173 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="wi"><maml:name>WhatIf</maml:name>
1174 | <maml:Description><maml:para>If specified, will output what changes the command will make without making them.
1175 | </maml:para>
1176 | </maml:Description>
1177 | <dev:type><maml:name>SwitchParameter</maml:name>
1178 | <maml:uri /></dev:type>
1179 | <dev:defaultValue>False</dev:defaultValue>
1180 | </command:parameter>
1181 | </command:syntaxItem>
1182 | </command:syntax>
1183 | <command:parameters><command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="cf"><maml:name>Confirm</maml:name>
1184 | <maml:Description><maml:para>The confirm preference. If left alone, will prompt you before modifying each application. If set to $false, it just goes through.
1185 | </maml:para>
1186 | </maml:Description>
1187 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
1188 | <dev:type><maml:name>SwitchParameter</maml:name>
1189 | <maml:uri /></dev:type>
1190 | <dev:defaultValue>$true</dev:defaultValue>
1191 | </command:parameter>
1192 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>GUID</maml:name>
1193 | <maml:Description><maml:para>Specifies the GUID of an application to query the MDT share for. Alternate to Name Parameter.
1194 | </maml:para>
1195 | </maml:Description>
1196 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1197 | <dev:type><maml:name>Object</maml:name>
1198 | <maml:uri /></dev:type>
1199 | <dev:defaultValue></dev:defaultValue>
1200 | </command:parameter>
1201 | <command:parameter required="true" variableLength="true" globbing="true" pipelineInput="True (ByPropertyName)" position="named" aliases="none"><maml:name>Name</maml:name>
1202 | <maml:Description><maml:para>Specifies the name of an application to search the MDT share for. If typed explicitly (i.e. "Install - Adobe Flash Player - x64"), will only return applications that have that exact name. The parameter also supports wildcards though, so typing something like "\ adobe\ " would return all the applications that have adobe in their name.
1203 | </maml:para>
1204 | </maml:Description>
1205 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1206 | <dev:type><maml:name>Object</maml:name>
1207 | <maml:uri /></dev:type>
1208 | <dev:defaultValue></dev:defaultValue>
1209 | </command:parameter>
1210 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>SetSupportedPlatformTo</maml:name>
1211 | <maml:Description><maml:para>Specifies what OS restriction to apply to the application(or to remove the restriction by selecting Null). The OS restriction types are a bit more granular when setting this attribute via MDT's GUI, so due to the complexity behind scripting each one, broader "catch-all" types are used. At the moment this tool also disregards any previous settings of the attribute, so any previous settings will be overwritten with the new data specified here.
1212 | </maml:para>
1213 | </maml:Description>
1214 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1215 | <dev:type><maml:name>Object</maml:name>
1216 | <maml:uri /></dev:type>
1217 | <dev:defaultValue></dev:defaultValue>
1218 | </command:parameter>
1219 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>ShareName</maml:name>
1220 | <maml:Description><maml:para>Specifies the name of the MDT share to query. In order to query by name, the MDT share must be mounted using either New-PSDrive or Set-MDTDrive. Here are some examples that should get you up and running:
1221 | </maml:para>
1222 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
1223 | </maml:para>
1224 | <maml:para>or
1225 | </maml:para>
1226 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
1227 | </maml:para>
1228 | </maml:Description>
1229 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1230 | <dev:type><maml:name>Object</maml:name>
1231 | <maml:uri /></dev:type>
1232 | <dev:defaultValue></dev:defaultValue>
1233 | </command:parameter>
1234 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="wi"><maml:name>WhatIf</maml:name>
1235 | <maml:Description><maml:para>If specified, will output what changes the command will make without making them.
1236 | </maml:para>
1237 | </maml:Description>
1238 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
1239 | <dev:type><maml:name>SwitchParameter</maml:name>
1240 | <maml:uri /></dev:type>
1241 | <dev:defaultValue>False</dev:defaultValue>
1242 | </command:parameter>
1243 | </command:parameters>
1244 | <command:inputTypes><command:inputType><dev:type><maml:name>System.Object</maml:name>
1245 | </dev:type>
1246 | <maml:description><maml:para>
1247 | </maml:para>
1248 | </maml:description>
1249 | </command:inputType>
1250 | </command:inputTypes>
1251 | <command:returnValues><command:returnValue><dev:type><maml:name>System.Object</maml:name>
1252 | </dev:type>
1253 | <maml:description><maml:para>
1254 | </maml:para>
1255 | </maml:description>
1256 | </command:returnValue>
1257 | </command:returnValues>
1258 | <maml:alertSet><maml:alert><maml:para>
1259 | </maml:para>
1260 | </maml:alert>
1261 | </maml:alertSet>
1262 | <command:examples><command:example><maml:title>Example 1: Remove OS restriction for ALL applications in MDT Share</maml:title>
1263 | <dev:code>PS C:\&gt; Set-MDTApplicationSupportedPlatform -ShareName MDTProduction -SetSupportedPlatformTo Null</dev:code>
1264 | <dev:remarks><maml:para>Removes the OS restriction for ALL applications in MDTProduction (add a -confirm:$false on the end to remove prompts for each application)
1265 | </maml:para>
1266 | </dev:remarks>
1267 | </command:example>
1268 | <command:example><maml:title>Example 2: Set ALL applications in share to Windows 7</maml:title>
1269 | <dev:code>PS C:\&gt; Set-MDTApplicationSupportedPlatform -ShareName MDTProduction -SetSupportedPlatformTo Windows7Only</dev:code>
1270 | <dev:remarks><maml:para>Set OS restriction for ALL applications in MDTProduction to Windows 7(add a -confirm:$false on the end to remove prompts for each application)
1271 | </maml:para>
1272 | </dev:remarks>
1273 | </command:example>
1274 | <command:example><maml:title>Example 3: Set one application to windows 10</maml:title>
1275 | <dev:code>PS C:\&gt; Set-MDTApplicationSupportedPlatform -ShareName MDTProduction -Name "Install - Java Runtime Environment -x86" -SetSupportedPlatformTo Windows10Only</dev:code>
1276 | <dev:remarks><maml:para>Set OS restriction for "Install - Java Runtime Environment -x86" in MDTProduction to Windows 10
1277 | </maml:para>
1278 | </dev:remarks>
1279 | </command:example>
1280 | </command:examples>
1281 | <command:relatedLinks><maml:navigationLink><maml:linkText>Online Version:</maml:linkText>
1282 | <maml:uri>https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Set-MDTApplicationSupportedPlatform.md</maml:uri>
1283 | </maml:navigationLink>
1284 | </command:relatedLinks>
1285 | </command:command>
1286 | <command:command xmlns:maml="http://schemas.microsoft.com/maml/2004/10" xmlns:command="http://schemas.microsoft.com/maml/dev/command/2004/10" xmlns:dev="http://schemas.microsoft.com/maml/dev/2004/10" xmlns:MSHelp="http://msdn.microsoft.com/mshelp">
1287 | <command:details><command:name>Set-MDTDrive</command:name>
1288 | <command:verb>Set</command:verb>
1289 | <command:noun>MDTDrive</command:noun>
1290 | <maml:description><maml:para>Creates an MDT drive.
1291 | </maml:para>
1292 | </maml:description>
1293 | </command:details>
1294 | <maml:description><maml:para>The Set-MDTDrive function creates an MDT drive using the MDTProvider for powershell. This function is actually just a wrapper for New-PSDrive with the MDTProvider. For example this:
1295 | </maml:para>
1296 | <maml:para>`PS C:&gt;Set-MDTDrive -Name MDTProduction -Path "\FILESERVER\MDTProduction$"`
1297 | </maml:para>
1298 | <maml:para> is actually the same command as this:
1299 | </maml:para>
1300 | <maml:para>`PS C:&gt;New-PSDrive -Name MDTProduction -PSProvider MDTProvider -Root "\FILESERVER\MDTProduction$" -NetworkPath "\FILESERVER\MDTProduction$" -Scope Global`
1301 | </maml:para>
1302 | </maml:description>
1303 | <command:syntax><command:syntaxItem><maml:name>Set-MDTDrive</maml:name>
1304 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="0" aliases="none"><maml:name>Name</maml:name>
1305 | <maml:Description><maml:para>Specifies what name you would like to give to the drive you want to create. This is the share name you'll reference later on when querying the share.
1306 | </maml:para>
1307 | </maml:Description>
1308 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1309 | <dev:type><maml:name>Object</maml:name>
1310 | <maml:uri /></dev:type>
1311 | <dev:defaultValue></dev:defaultValue>
1312 | </command:parameter>
1313 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="1" aliases="none"><maml:name>Path</maml:name>
1314 | <maml:Description><maml:para>{{Fill Path Description}}
1315 | </maml:para>
1316 | </maml:Description>
1317 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1318 | <dev:type><maml:name>Object</maml:name>
1319 | <maml:uri /></dev:type>
1320 | <dev:defaultValue></dev:defaultValue>
1321 | </command:parameter>
1322 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="cf"><maml:name>Confirm</maml:name>
1323 | <maml:Description><maml:para>The confirm preference. If left alone, will just let the command run as normal. If $true is specified, will prompt you before creating the drive.
1324 | </maml:para>
1325 | </maml:Description>
1326 | <dev:type><maml:name>SwitchParameter</maml:name>
1327 | <maml:uri /></dev:type>
1328 | <dev:defaultValue>False</dev:defaultValue>
1329 | </command:parameter>
1330 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Force</maml:name>
1331 | <maml:Description><maml:para>If specified, will create MDT drive even if one with same name already exists(in case one wants to create a drive of the same name with a different path)
1332 | </maml:para>
1333 | </maml:Description>
1334 | <dev:type><maml:name>SwitchParameter</maml:name>
1335 | <maml:uri /></dev:type>
1336 | <dev:defaultValue>False</dev:defaultValue>
1337 | </command:parameter>
1338 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="wi"><maml:name>WhatIf</maml:name>
1339 | <maml:Description><maml:para>If specified, will output what changes the command will make without making them.
1340 | </maml:para>
1341 | </maml:Description>
1342 | <dev:type><maml:name>SwitchParameter</maml:name>
1343 | <maml:uri /></dev:type>
1344 | <dev:defaultValue>False</dev:defaultValue>
1345 | </command:parameter>
1346 | </command:syntaxItem>
1347 | </command:syntax>
1348 | <command:parameters><command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="cf"><maml:name>Confirm</maml:name>
1349 | <maml:Description><maml:para>The confirm preference. If left alone, will just let the command run as normal. If $true is specified, will prompt you before creating the drive.
1350 | </maml:para>
1351 | </maml:Description>
1352 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
1353 | <dev:type><maml:name>SwitchParameter</maml:name>
1354 | <maml:uri /></dev:type>
1355 | <dev:defaultValue>False</dev:defaultValue>
1356 | </command:parameter>
1357 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="none"><maml:name>Force</maml:name>
1358 | <maml:Description><maml:para>If specified, will create MDT drive even if one with same name already exists(in case one wants to create a drive of the same name with a different path)
1359 | </maml:para>
1360 | </maml:Description>
1361 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
1362 | <dev:type><maml:name>SwitchParameter</maml:name>
1363 | <maml:uri /></dev:type>
1364 | <dev:defaultValue>False</dev:defaultValue>
1365 | </command:parameter>
1366 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="0" aliases="none"><maml:name>Name</maml:name>
1367 | <maml:Description><maml:para>Specifies what name you would like to give to the drive you want to create. This is the share name you'll reference later on when querying the share.
1368 | </maml:para>
1369 | </maml:Description>
1370 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1371 | <dev:type><maml:name>Object</maml:name>
1372 | <maml:uri /></dev:type>
1373 | <dev:defaultValue></dev:defaultValue>
1374 | </command:parameter>
1375 | <command:parameter required="true" variableLength="true" globbing="false" pipelineInput="False" position="1" aliases="none"><maml:name>Path</maml:name>
1376 | <maml:Description><maml:para>{{Fill Path Description}}
1377 | </maml:para>
1378 | </maml:Description>
1379 | <command:parameterValue required="true" variableLength="false">Object</command:parameterValue>
1380 | <dev:type><maml:name>Object</maml:name>
1381 | <maml:uri /></dev:type>
1382 | <dev:defaultValue></dev:defaultValue>
1383 | </command:parameter>
1384 | <command:parameter required="false" variableLength="true" globbing="false" pipelineInput="False" position="named" aliases="wi"><maml:name>WhatIf</maml:name>
1385 | <maml:Description><maml:para>If specified, will output what changes the command will make without making them.
1386 | </maml:para>
1387 | </maml:Description>
1388 | <command:parameterValue required="false" variableLength="false">SwitchParameter</command:parameterValue>
1389 | <dev:type><maml:name>SwitchParameter</maml:name>
1390 | <maml:uri /></dev:type>
1391 | <dev:defaultValue>False</dev:defaultValue>
1392 | </command:parameter>
1393 | </command:parameters>
1394 | <command:inputTypes><command:inputType><dev:type><maml:name>None</maml:name>
1395 | </dev:type>
1396 | <maml:description><maml:para>
1397 | </maml:para>
1398 | </maml:description>
1399 | </command:inputType>
1400 | </command:inputTypes>
1401 | <command:returnValues><command:returnValue><dev:type><maml:name>System.Object</maml:name>
1402 | </dev:type>
1403 | <maml:description><maml:para>
1404 | </maml:para>
1405 | </maml:description>
1406 | </command:returnValue>
1407 | </command:returnValues>
1408 | <maml:alertSet><maml:alert><maml:para>
1409 | </maml:para>
1410 | </maml:alert>
1411 | </maml:alertSet>
1412 | <command:examples><command:example><maml:title>Example 1: Create an MDT drive</maml:title>
1413 | <dev:code>PS C:\&gt; Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$"</dev:code>
1414 | <dev:remarks><maml:para>Creates an MDT Drive with a name of `MDTProduction` and a path of `"\FILESERVER\MDTProduction$"`
1415 | </maml:para>
1416 | </dev:remarks>
1417 | </command:example>
1418 | <command:example><maml:title>Example 2: Create an MDT drive, overwriting previous drives</maml:title>
1419 | <dev:code>PS C:\&gt; Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$" -Force</dev:code>
1420 | <dev:remarks><maml:para>Creates an MDT Drive with a name of `MDTProduction` and a path of `"\FILESERVER\MDTProduction$"`, overwriting any previous drives with the name `MDTProduction`.
1421 | </maml:para>
1422 | </dev:remarks>
1423 | </command:example>
1424 | <command:example><maml:title>Example 3: Shows what will happen if the command is run</maml:title>
1425 | <dev:code>PS C:\&gt; Set-MDTDrive -Name MDTProduction -Path "\\FILESERVER\MDTProduction$" -WhatIf</dev:code>
1426 | <dev:remarks><maml:para>Shows what will happen if you try to create an MDT Drive with a name of `MDTProduction` and a path of `"\FILESERVER\MDTProduction$"`
1427 | </maml:para>
1428 | </dev:remarks>
1429 | </command:example>
1430 | </command:examples>
1431 | <command:relatedLinks><maml:navigationLink><maml:linkText>Online Version:</maml:linkText>
1432 | <maml:uri>https://github.com/JohnForet/MDTApplicationTools/blob/master/docs/Set-MDTDrive.md</maml:uri>
1433 | </maml:navigationLink>
1434 | </command:relatedLinks>
1435 | </command:command>
1436 | </helpItems>
1437 | 


--------------------------------------------------------------------------------