Quantcast
Channel: PowerShell App Deployment Toolkit
Viewing all 2341 articles
Browse latest View live
↧

New Post: OffScrub13.vbs Script Hangs

April 29, 2015, 11:36 pm
↧
Search

New Post: Syntax

May 5, 2015, 1:46 pm
$
0
0
Since this is around for archival purposes still, I figured I'd mention a workaround. I had the same error.

Instead of using the built in function, I replaced it with Start-Process in the Deploy-Application.ps1 script.
Remember to also replace -Arguments with -ArgumentList as that is the available parameter for Start-Process.

Also, if any admins are still reading these, a couple comments/questions:
  1. Thank you again for a such a powerful tool!
  2. There are certain functions of the forum that I much preferred in this old one, such as layout, ease of response and MOSTLY the ability to subscribe to the RSS so I would receive daily updates in Feedly.
  3. I noticed other methods of login being used on the new PSADT site, but can you also please add MS accounts as an option? It makes sense to me because PowerShell is MS, but those other accounts I don't use (Google+, Instagram, etc.)
Thanks again!
↧
↧

New Post: Mouse and Keyboard disabled during installation

May 21, 2015, 6:10 am
$
0
0
Hello,
has someone disabled the mouse and keyboard during the installation in his script? Some installations are very important for the computer and I do not want the user simply shuts him.

salute,
ameise1234
↧

New Post: Mouse and Keyboard disabled during installation

May 21, 2015, 10:42 pm
$
0
0
Hi,
in the past i had the same Problem for BIOS Update and after a Long search i found a script and modified this for us:
If ($Battery -like "False")
{
function Lock-Screen([ScriptBlock] $Payload={Start-Sleep -Seconds 5}, $Title='Busy, go away.')
{
    try
    {
      $window = New-Object Windows.Window
      $label = New-Object Windows.Controls.Label

      $label.Content = $Title
      $label.FontSize = 50
      $label.FontFamily = 'Consolas'
      $label.Background = 'Transparent'
      $label.Foreground = 'Red'
      $label.HorizontalAlignment = 'Center'
      $label.VerticalAlignment = 'Center'

      $Window.AllowsTransparency = $True
      $Window.Opacity = .7
      $window.WindowStyle = 'None'
      $window.Content = $label
      $window.Left = $window.Top = 0
      $window.WindowState = 'Maximized'
      $window.Topmost = $true

      $null = $window.Show()
      Invoke-Command -ScriptBlock $Payload
    }
    finally { $window.Close() }
}

$job = 
{ 
  Execute-Process -FilePath "manage-bde" -Arguments "-protectors -disable C:" -WindowStyle Hidden
  sleep 10
  Execute-Process -FilePath "WINUPTP.EXE" -Arguments "/S"
}

Lock-Screen -Payload $job -Title 'ACHTUNG!!! BIOS Update läuft daher NICHT ABSCHALTEN!' 
}
ELSE
{
Show-DialogBox -Title "---> BIOS UPDATE - WICHTIG INFO - BITTE LESEN <---" -Text "ACHTUNG: Das BIOS Update konnte nicht ausgeführt werden da der PC nicht am STROMNETZ angeschlossen ist! Bitte am STROMNETZ anschließen und das BIOS Update erneut starten!!!" -Icon "Exclamation" -TimeOut 600
Exit-Script -ExitCode "1618"
}
↧

New Post: Mouse and Keyboard disabled during installation

May 21, 2015, 10:54 pm
$
0
0
did you use this script into the deployment tool script? in my script i want to install mozilla firefox, can i use your script into mine?
↧
↧

New Post: Mouse and Keyboard disabled during installation

May 21, 2015, 11:09 pm
$
0
0
Du scheinst ja aus Deutschland zu kommen :) Ich bin mit dem Skripten nicht so bewandert. Kann ich das in dieses PowerShell App Deployment Toolkit-Skript mit einsetzen?


<#
.SYNOPSIS
This script performs the installation or uninstallation of an application(s).
.DESCRIPTION
The script is provided as a template to perform an install or uninstall of an application(s).
The script either performs an "Install" deployment type or an "Uninstall" deployment type.
The install deployment type is broken down into 3 main sections/phases: Pre-Install, Install, and Post-Install.
The script dot-sources the AppDeployToolkitMain.ps1 script which contains the logic and functions required to install or uninstall an application.
.PARAMETER DeploymentType
The type of deployment to perform. Default is: Install.
.PARAMETER DeployMode
Specifies whether the installation should be run in Interactive, Silent, or NonInteractive mode. Default is: Interactive. Options: Interactive = Shows dialogs, Silent = No dialogs, NonInteractive = Very silent, i.e. no blocking apps. NonInteractive mode is automatically set if it is detected that the process is not user interactive.
.PARAMETER AllowRebootPassThru
Allows the 3010 return code (requires restart) to be passed back to the parent process (e.g. SCCM) if detected from an installation. If 3010 is passed back to SCCM, a reboot prompt will be triggered.
.PARAMETER TerminalServerMode
Changes to "user install mode" and back to "user execute mode" for installing/uninstalling applications for Remote Destkop Session Hosts/Citrix servers.
.PARAMETER DisableLogging
Disables logging to file for the script. Default is: $false.
.EXAMPLE
Deploy-Application.ps1
.EXAMPLE
Deploy-Application.ps1 -DeployMode 'Silent'
.EXAMPLE
Deploy-Application.ps1 -AllowRebootPassThru -AllowDefer
.EXAMPLE
Deploy-Application.ps1 -DeploymentType Uninstall
.NOTES
Toolkit Exit Code Ranges:
60000 - 68999: Reserved for built-in exit codes in Deploy-Application.ps1, Deploy-Application.exe, and AppDeployToolkitMain.ps1
69000 - 69999: Recommended for user customized exit codes in Deploy-Application.ps1
70000 - 79999: Recommended for user customized exit codes in AppDeployToolkitExtensions.ps1
.LINK
http://psappdeploytoolkit.codeplex.com

>

[CmdletBinding()]
Param (
[Parameter(Mandatory=$false)]
[ValidateSet('Install','Uninstall')]
[string]$DeploymentType = 'Install',
[Parameter(Mandatory=$false)]
[ValidateSet('Interactive','Silent','NonInteractive')]
[string]$DeployMode = 'Interactive',
[Parameter(Mandatory=$false)]
[switch]$AllowRebootPassThru = $false,
[Parameter(Mandatory=$false)]
[switch]$TerminalServerMode = $false,
[Parameter(Mandatory=$false)]
[switch]$DisableLogging = $false
)

Try {
## Set the script execution policy for this process
Try { Set-ExecutionPolicy -ExecutionPolicy 'ByPass' -Scope 'Process' -Force -ErrorAction 'Stop' } Catch {}

##*===============================================
##* VARIABLE DECLARATION
##*===============================================
## Variables: Application
[string]$appVendor = 'Mozilla'
[string]$appName = 'Firefox'
[string]$appVersion = '3.6.28'
[string]$appArch = ''
[string]$appLang = 'DE'
[string]$appRevision = '01'
[string]$appScriptVersion = '3.6.1'
[string]$appScriptDate = '05/21/2015'
[string]$appScriptAuthor = 'Max Mustermann'
##*===============================================

##* Do not modify section below
#region DoNotModify

## Variables: Exit Code
[int32]$mainExitCode = 0

## Variables: Script
[string]$deployAppScriptFriendlyName = 'Deploy Application'
[version]$deployAppScriptVersion = [version]'3.6.1'
[string]$deployAppScriptDate = '03/20/2015'
[hashtable]$deployAppScriptParameters = $psBoundParameters

## Variables: Environment
[string]$scriptDirectory = Split-Path -Path $MyInvocation.MyCommand.Definition -Parent

## Dot source the required App Deploy Toolkit Functions
Try {
    [string]$moduleAppDeployToolkitMain = "$scriptDirectory\AppDeployToolkit\AppDeployToolkitMain.ps1"
    If (-not (Test-Path -Path $moduleAppDeployToolkitMain -PathType Leaf)) { Throw "Module does not exist at the specified location [$moduleAppDeployToolkitMain]." }
    If ($DisableLogging) { . $moduleAppDeployToolkitMain -DisableLogging } Else { . $moduleAppDeployToolkitMain }
}
Catch {
    [int32]$mainExitCode = 60008
    Write-Error -Message "Module [$moduleAppDeployToolkitMain] failed to load: `n$($_.Exception.Message)`n `n$($_.InvocationInfo.PositionMessage)" -ErrorAction 'Continue'
    Exit $mainExitCode
}

#endregion
##* Do not modify section above
##*===============================================
##* END VARIABLE DECLARATION
##*===============================================

If ($deploymentType -ine 'Uninstall') {
    ##*===============================================
    ##* PRE-INSTALLATION
    ##*===============================================
    [string]$installPhase = 'Pre-Installation'

    ## Prompt the user to close the following applications if they are running:
    Show-InstallationWelcome -CloseApps 'iexplore,AcroRd32,cidaemon' -AllowDefer -DeferTimes 3
    # Show Progress Message (with the default message)
    Show-InstallationProgress


    ##*===============================================
    ##* INSTALLATION
    ##*===============================================
    [string]$installPhase = 'Installation'

    # Install the base MSI 
    Execute-MSI -Action Install -Path 'Firefox-3.6.28-de.msi' -Parameters '/QN' 



    ##*===============================================
    ##* POST-INSTALLATION
    ##*===============================================
    [string]$installPhase = 'Post-Installation'

    ## <Perform Post-Installation tasks here>

    ## Display a message at the end of the install
    Show-InstallationPrompt -Message 'Glückwunsch! Eine Software mehr!' -ButtonRightText 'OK' -Icon Information -NoWait
}
ElseIf ($deploymentType -ieq 'Uninstall')
{
    ##*===============================================
    ##* PRE-UNINSTALLATION
    ##*===============================================
    [string]$installPhase = 'Pre-Uninstallation'

    ## Prompt the user to close the following applications if they are running:
    Show-InstallationWelcome -CloseApps 'iexplore,AcroRd32,cidaemon' -AllowDefer -DeferTimes 3

    ## Show Progress Message (with a message to indicate the application is being uninstalled)
    Show-InstallationProgress -StatusMessage 'Uninstalling application [$installTitle]. Please Wait...'


}

##*===============================================
##* END SCRIPT BODY
##*===============================================

## Call the Exit-Script function to perform final cleanup operations
Exit-Script -ExitCode $mainExitCode
}
Catch {
[int32]$mainExitCode = 1
[string]$mainErrorMessage = "$(Resolve-Error)"
Write-Log -Message $mainErrorMessage -Severity 3 -Source $deployAppScriptFriendlyName
Show-DialogBox -Text $mainErrorMessage -Icon 'Stop'
Exit-Script -ExitCode $mainExitCode
}
↧

New Post: Mouse and Keyboard disabled during installation

May 27, 2015, 12:21 am
$
0
0
Hello, yes i am german but i wrote in english that´s would be help other guys.

you can use this script inside the PSAPPDEP, i put it into the section for the Installation, take a look at here. it you must define when you would like to use it and how Long you would like block the devices.

Hope this helps more. :)

function Lock-Screen([ScriptBlock] $Payload={__Start-Sleep -Seconds 5__}, $Title='Busy, go away.')
#*===============================================
#* INSTALLATION 
$installPhase = "Installation"
#*===============================================

If ($Battery -like "False")
{
function Lock-Screen([ScriptBlock] $Payload={Start-Sleep -Seconds 5}, $Title='Busy, go away.')
{
    try
    {
      $window = New-Object Windows.Window
      $label = New-Object Windows.Controls.Label

      $label.Content = $Title
      $label.FontSize = 50
      $label.FontFamily = 'Consolas'
      $label.Background = 'Transparent'
      $label.Foreground = 'Red'
      $label.HorizontalAlignment = 'Center'
      $label.VerticalAlignment = 'Center'

      $Window.AllowsTransparency = $True
      $Window.Opacity = .7
      $window.WindowStyle = 'None'
      $window.Content = $label
      $window.Left = $window.Top = 0
      $window.WindowState = 'Maximized'
      $window.Topmost = $true

      $null = $window.Show()
      Invoke-Command -ScriptBlock $Payload
    }
    finally { $window.Close() }
}

$job = 
{ 
  Execute-Process -FilePath "manage-bde" -Arguments "-protectors -disable C:" -WindowStyle Hidden
  sleep 10
  #Execute-Process -FilePath "E6440A07.exe" -Arguments "/s /f /p=bdr529"
  sleep 10
}

Lock-Screen -Payload $job -Title 'ACHTUNG!!! BIOS Update läuft daher NICHT ABSCHALTEN!' 
}
ELSE
{
Show-DialogBox -Title "---> BIOS UPDATE - WICHTIG INFO - BITTE LESEN <---" -Text "ACHTUNG: Das BIOS Update konnte nicht ausgeführt werden da der PC nicht am STROMNETZ angeschlossen ist! Bitte am STROMNETZ anschließen und das BIOS Update erneut starten!!!" -Icon "Exclamation" -TimeOut 600
Exit-Script -ExitCode "1618"
}

#*===============================================
#* POST-INSTALLATION
↧

New Post: Using a wildcard with Remove-MSIApplications

May 27, 2015, 8:40 am
$
0
0
I am installing Java 7 Update 80 x86 and need to specifically remove all previous versions of Java 7 that are x64. Is there any way to do something like Remove-MSIApplications "Java 7 Update * (64-bit)" as opposed to:

Remove-MSIApplications "Java 7 Update 21 (64-bit)"
Remove-MSIApplications "Java 7 Update 25 (64-bit)"
Remove-MSIApplications "Java 7 Update 40 (64-bit)"
Remove-MSIApplications "Java 7 Update 45 (64-bit)"
Remove-MSIApplications "Java 7 Update 51 (64-bit)"
Remove-MSIApplications "Java 7 Update 55 (64-bit)"
Remove-MSIApplications "Java 7 Update 60 (64-bit)"
Remove-MSIApplications "Java 7 Update 67 (64-bit)"
Remove-MSIApplications "Java 7 Update 71 (64-bit)"
Remove-MSIApplications "Java 7 Update 75 (64-bit)"

Thanks,

Mike
↧
Search

New Post: Using a wildcard with Remove-MSIApplications

May 28, 2015, 1:17 am
$
0
0
Hi

The site has moved to http://psappdeploytoolkit.com/, so you should post your questions there. Anyway the answer is to use -WildCard switch:

Remove-MSIApplications "Java 7 Update * (64-bit)" -WildCard.

It's available from version 3.6.1 onwards.
  • Jyri
↧
↧

New Post: Mouse and Keyboard disabled during installation

June 3, 2015, 4:08 am
$
0
0
ok, i'm not good with vbs. can you help me with my problem?
How would your script look, if it is to lock the mouse and keyboard for a normal installation? You can see my script above. I've no problems with my bios :) thank you very much for help
↧

New Post: Bex event at the end of the deployment

June 26, 2015, 6:20 am
$
0
0
hi guys,

i am getting the following problem at the end of the script , the application installed sucessfully but powershell crashed. any ideas?


Problem signature:
Problem Event Name: BEX
Application Name: powershell.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc414
Fault Module Name: StackHash_19ab
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 0061002d
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1028
Additional Information 1: 19ab
Additional Information 2: 19ab9926d2aa8f69a72710de3aba1701
Additional Information 3: 3d02
Additional Information 4: 3d026baba0de3076790aa3b225d9b519

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
↧

New Post: Pop-Up for MSI error codes during UI Installation

June 26, 2015, 6:50 am
$
0
0
Hi Team,

Could you Please help to get Pop-Up message boxes for MSI error codes during normal installation?

I tried to modify the AppDeployToolkitConfig.xml by adding the below content, but installation is not happened.
"<!--InstallationUI_ExitCode>9999</InstallationUI_ExitCode>
<!-- ERROR_ASSET_KEY_NOT_FOUND 9999 - PACKAGENAME cannot be installed on this non-SDS machine. -->"

Please do needful. Thanks in advance

Regards,
Bala
↧

New Post: Force users to not be able to open browsers

August 10, 2015, 7:23 am
$
0
0
Is there anyway in psappdeploy I can force a user not be able to open a browser during the whole install?

I have it closing the browser but a small number of users just open it back up.
↧
↧

New Post: Force Close Flash before install

August 10, 2015, 7:55 am
$
0
0
Is there a way to force close flashutil32_18_0_0_209_activeX process before installing flash. I tried for the application close in psappdeploy putting with my normal 'iexplore,firefox,flash*'

I was hoping to put a flash with a * after it to close all flash process's

Is there a way to do that?
↧

New Post: Force users to not be able to open browsers

August 10, 2015, 2:52 pm
$
0
0
Hi, the project has moved to a new website, please post your questions here in future: http://psappdeploytoolkit.com/

Yes, you can use the -BlockExecution parameter with -CloseApps "iexplore.exe" for example to prevent the user from launching Internet Explorer during the install. Refer to the documentation for more details.
↧
Search

New Post: Run Script as Different User

August 21, 2015, 10:53 am
$
0
0
I have some code I need to use to add a machine to a collection during an MSI install. I am already using the PADT to install the MSI. I also have it in ConfigMgr as an application deployment. The code needs to run as a service account that has access in ConfigMgr 2012. Is there an existing way in PADT of running that code without exposing the password?

I simplified the code for my testing.

https://social.technet.microsoft.com/forums/systemcenter/en-US/d569076f-001a-48b5-bb8a-2eb3a40b86d6/programatically-add-computers-to-a-collection-in-sccm

$CollectionName = "<collectionname>"
$ComputerName = $Env:COMPUTERNAME
$SmsAuthority = Get-WmiObject -Namespace "Root\CCM" -Class "SMS_Authority"
[String]$SMSSiteCode = $SmsAuthority.Name.Remove(0, 4)
$SMSManagementServer = "<servername>"
$SmsResourceID = $(Get-WmiObject -ComputerName $SMSManagementServer -Namespace "Root\Sms\Site_$SmsSiteCode" -Query "Select * From SMS_R_System Where Name='$($ComputerName)'").ResourceID
$SmsNewRule = $([wmiclass]$("\$($SmsManagementServer)\root\sms\site_$($SmsSiteCode):SMS_CollectionRuleDirect")).CreateInstance()
$SmsCollection = Get-WmiObject -ComputerName $SMSManagementServer -Namespace "Root\Sms\Site_$SmsSiteCode" -Query "Select * From SMS_Collection Where Name='$($CollectionName)'"
$SmsCollection.Get()
$SmsNewRule.ResourceClassName = "SMS_R_System"
$SmsNewRule.ResourceID = $SmsResourceID
$SmsNewRule.RuleName = $ComputerName
[System.Management.ManagementBaseObject[]]$SmsRules = $SmsCollection.CollectionRules
$SmsRules += $SmsNewRule
$SmsCollection.CollectionRules = $SmsRules
$SmsCollection.Put()

Thanks,

Mike
↧

New Post: Run Script as Different User

August 22, 2015, 12:55 am
$
0
0
Well I finally figured it out and I thought I would share my proof of concept code. I am being forced to replace SCEP and install CheckPoint. I need to be able to add the computer to a collection so that SCEP no longer manages the computer. If I didn't do this it would keep reinstalling. This code will add the computer to the collection once I uninstall SCEP and install Checkpoint (against my better judgement). I simplified the code as much as I could for testing. This was not as straight forward with powershell as I expected it to be. I have an editor that will convert this script to an exe so I can call it in the Deploy-Application.PS1.

$ComputerName = $Env:COMPUTERNAME
$CollectionName = 'Test Collection'
$NameSpace = 'root\ccm'
$ServerName = '<servername>'
$username = '<domain>\<serviceAccount>'
$password = '<password>'
$cred=new-object system.management.automation.PSCredential $user,$password
$SMSSiteCode = 'PRI'
$SMSManagementServer = '<servername>'

$SmsResourceID = $(Get-WmiObject -ComputerName $SMSManagementServer -Namespace "Root\Sms\Site_$SmsSiteCode" -Credential $cred -Query "Select * From SMS_R_System Where Name='$($ComputerName)'").ResourceID
$SmsNewRule = $([wmiclass]$("\$($SmsManagementServer)\root\sms\site_$($SmsSiteCode):SMS_CollectionRuleDirect")).CreateInstance()

$SmsCollection = Get-WmiObject -ComputerName $SMSManagementServer -Namespace "Root\Sms\Site_$SmsSiteCode" -Credential $cred -Query "Select * From SMS_Collection Where Name='$($CollectionName)'"
$SmsCollection.Get()

$SmsNewRule.ResourceClassName = "SMS_R_System"
$SmsNewRule.ResourceID = $SmsResourceID
$SmsNewRule.RuleName = $ComputerName

[System.Management.ManagementBaseObject[]]$SmsRules = $SmsCollection.CollectionRules
$SmsRules += $SmsNewRule
$SmsCollection.CollectionRules = $SmsRules
$SmsCollection.Put()
$SmsCollection.RequestRefresh
↧
↧

New Post: Getting Logon Lookup errors in SERVICEUIx86 while deploying IE11 using Psappdeploy and SCCM

August 25, 2015, 9:18 am
$
0
0
Hi , we are using psappdeploy to deploy IE11 via SCCM, but notice that everytime the package starts to install there is a command prompt window that shows up:

Image

the install is succesfull however and the box disappears after install is completed. But have no idea why this is showing up
↧

New Post: Getting Logon Lookup errors in SERVICEUIx86 while deploying IE11 using Psappdeploy and SCCM

August 25, 2015, 11:51 am
$
0
0
Hi, you are using an older version of the toolkit that has been deprecated. Please download the latest version from psappdeploytoolkit.com. Also please use the forums on the new site.
↧

New Post: Uninsatll an msi with parameter or options.

December 16, 2015, 9:42 am
$
0
0
Hello,
Could you please help me with uninstalling an MSI with options. I believe the “Execute-MSI -Action Uninstall” does not support additional options.

This is an example command line : msiexec /qb! /x MyProgram.msi AUTO_DELETE=3

Thank you, MikeWallace
↧
Viewing all 2341 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>