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

New Post: -ShowInstallationRestartPrompt -NoCountdown not visiable Version 3.5

January 26, 2015, 3:42 pm
$
0
0
With -Countdownseconds 600 -CountdownNoHideSeconds 60 works correctly.
With -NoCountdown no restart prompt ever shows. No error in the logs
↧
Search

Created Unassigned: Logname parameter not working in Execute-MSI function [150]

January 26, 2015, 7:06 pm
$
0
0
Hi,

This command is not working

```
Execute-MSI -Action Install -Path "ActivePerl-5.14.3.1404-MSWin32-296513.msi" -Parameters "REBOOT=ReallySuppress DISABLEADVTSHORTCUTS=1 ALLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1"

```

The error message will be "Execute-MSI : Impossible de trouver un paramètre correspondant au nom « LogName ».
Au caractère Ligne:1 : 153
+ ... LLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1.log"
+ ~~~~~~~~
+ CategoryInfo : InvalidArgument : (:) [Execute-MSI], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Execute-MSI"

Impossible to find a parameter corresponding to logname.

If I remove the logname parameter then the installation is running fine.

```
Sound the latest modification: [string]$private:LogName is the problem.
```

Thanks,

François
↧
↧

Commented Unassigned: Logname parameter not working in Execute-MSI function [150]

January 26, 2015, 7:21 pm
$
0
0
Hi,

This command is not working

```
Execute-MSI -Action Install -Path "ActivePerl-5.14.3.1404-MSWin32-296513.msi" -Parameters "REBOOT=ReallySuppress DISABLEADVTSHORTCUTS=1 ALLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1"

```

The error message will be "Execute-MSI : Impossible de trouver un paramètre correspondant au nom « LogName ».
Au caractère Ligne:1 : 153
+ ... LLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1.log"
+ ~~~~~~~~
+ CategoryInfo : InvalidArgument : (:) [Execute-MSI], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Execute-MSI"

Impossible to find a parameter corresponding to logname.

If I remove the logname parameter then the installation is running fine.

```
Sound the latest modification: [string]$private:LogName is the problem.
```

Thanks,

François
Comments: Hi, Just try to see what I mean: ``` Function Execute-vctest { [CmdletBinding()] Param ( [Parameter(Mandatory=$false)] [ValidateNotNullorEmpty()] [string]$private:LogName ) } execute-vctest -logname "test" ```
↧

New Post: Regarding the SCCM limitation with Applications and "allow user to interact with program installation"

January 26, 2015, 10:35 pm
$
0
0
ServicesUI.exe displays the interface in the console session, not in the RDP session. The Interface is there, but you can't see or interact with it.
↧

New Post: getting error code 1 on a majority of machines on one deployment

January 27, 2015, 1:16 am
$
0
0
Hi!

I'm also having this issue. Can you please provide me your solution? :)
↧
↧

New Post: Multiple Parameters in the Execute-Process function?

January 27, 2015, 3:40 am
$
0
0
Hi LoganDS,

the answer was given by the dev guys. You have to use a special syntax:

Click here
↧

Commented Unassigned: Logname parameter not working in Execute-MSI function [150]

January 27, 2015, 4:26 am
$
0
0
Hi,

This command is not working

```
Execute-MSI -Action Install -Path "ActivePerl-5.14.3.1404-MSWin32-296513.msi" -Parameters "REBOOT=ReallySuppress DISABLEADVTSHORTCUTS=1 ALLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1"

```

The error message will be "Execute-MSI : Impossible de trouver un paramètre correspondant au nom « LogName ».
Au caractère Ligne:1 : 153
+ ... LLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1.log"
+ ~~~~~~~~
+ CategoryInfo : InvalidArgument : (:) [Execute-MSI], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Execute-MSI"

Impossible to find a parameter corresponding to logname.

If I remove the logname parameter then the installation is running fine.

```
Sound the latest modification: [string]$private:LogName is the problem.
```

Thanks,

François
Comments: Add an alias for that variable like so: ``` [Parameter(Mandatory=$false)] [ValidateNotNullorEmpty()] [Alias('LogName')] [string]$private:LogName ```
↧

Commented Unassigned: Logname parameter not working in Execute-MSI function [150]

January 27, 2015, 5:24 am
$
0
0
Hi,

This command is not working

```
Execute-MSI -Action Install -Path "ActivePerl-5.14.3.1404-MSWin32-296513.msi" -Parameters "REBOOT=ReallySuppress DISABLEADVTSHORTCUTS=1 ALLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1"

```

The error message will be "Execute-MSI : Impossible de trouver un paramètre correspondant au nom « LogName ».
Au caractère Ligne:1 : 153
+ ... LLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1.log"
+ ~~~~~~~~
+ CategoryInfo : InvalidArgument : (:) [Execute-MSI], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Execute-MSI"

Impossible to find a parameter corresponding to logname.

If I remove the logname parameter then the installation is running fine.

```
Sound the latest modification: [string]$private:LogName is the problem.
```

Thanks,

François
Comments: Sounds good. Will you change your code accordingly?
↧
Search

New Post: Prompting user to close application(s) [Deploy Application Invoker]

January 27, 2015, 7:16 am
$
0
0
Thanks CHiland for your response..

Here is my code..

Show-InstallationWelcome -CloseApps "communicator,outlook,lync" -CloseAppsCountdown 300 -PersistPrompt

Thanks
↧
↧

Commented Unassigned: Logname parameter not working in Execute-MSI function [150]

January 27, 2015, 7:54 am
$
0
0
Hi,

This command is not working

```
Execute-MSI -Action Install -Path "ActivePerl-5.14.3.1404-MSWin32-296513.msi" -Parameters "REBOOT=ReallySuppress DISABLEADVTSHORTCUTS=1 ALLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1"

```

The error message will be "Execute-MSI : Impossible de trouver un paramètre correspondant au nom « LogName ».
Au caractère Ligne:1 : 153
+ ... LLUSERS=1 /Qn" -LogName "Vcredist2005_Frv1.log"
+ ~~~~~~~~
+ CategoryInfo : InvalidArgument : (:) [Execute-MSI], ParameterBindingException
+ FullyQualifiedErrorId : NamedParameterNotFound,Execute-MSI"

Impossible to find a parameter corresponding to logname.

If I remove the logname parameter then the installation is running fine.

```
Sound the latest modification: [string]$private:LogName is the problem.
```

Thanks,

François
Comments: Execute-MSI -private:LogName="hello" would work, too. But the Alias is still prettier. Personally I would have changed it to -MSILogName ... For people not familiar with the code, $LogName is the same variable name used for the log file for the main script. That is why $LogName had to be made private for the Execute-MSI function.
↧

New Post: Close Applications - Automatically Save Documents/Prompt to save

January 28, 2015, 5:37 am
$
0
0
Hi,

Can anyone please advise on the above?

Regards,
Craig
↧

New Post: CloseApp to generic

January 28, 2015, 6:02 am
$
0
0
Hi, I really like this script but have a small issue.
I want to uninstall Office 2003 and install 2010 so I use this code to close apps :
Show-InstallationWelcome -CloseApps 'excel,winword,msaccess,mspub,powerpnt,infopath' -PersistPrompt -BlockExecution -CloseAppsCountDown 1800

My problem comes from CDBunerXP. It start a process called NmsaccessU with the user "system". The closeApps windows ask my users to kill this task even with all office applications closed. Is there a way to ignore this process or to check an exact process name ?

Thanks

Bruno
↧

New Post: Close Applications - Automatically Save Documents/Prompt to save

January 28, 2015, 6:46 am
$
0
0
Hi Craig,

I'm with you on this one.
It would be great to have a user friendlier approach for processes with a user interface.
I find the -CloseApps naming misleading as it is killing processes using Stop-Process,

Instead you could "gently" ask Excel to exit by sending a close message to its main window:
Get-Process excel -ErrorAction SilentlyContinue | ? { $_.CloseMainWindow() | Out-Null }

Hopefully it can be added to the toolkit in the future.

Regards,
Marco
↧
↧

New Post: Close Applications - Automatically Save Documents/Prompt to save

January 28, 2015, 7:02 am
$
0
0
MarcoHH wrote:
Hi Craig,

I'm with you on this one.
It would be great to have a user friendlier approach for processes with a user interface.
I find the -CloseApps naming misleading as it is killing processes using Stop-Process,

Instead you could "gently" ask Excel to exit by sending a close message to its main window:
Get-Process excel -ErrorAction SilentlyContinue | ? { $_.CloseMainWindow() | Out-Null }

Hopefully it can be added to the toolkit in the future.

Regards,
Marco
Hi Marco,

Have you implemented the above command-line in your environment/deployment?

Regards,
Craig
↧

New Post: Regarding the SCCM limitation with Applications and "allow user to interact with program installation"

January 28, 2015, 7:08 am
$
0
0
A small update on my front - regarding the Interactive Service Detection service. Sorry for the delay, but I've been swamped with work.

I switched over to x64 based version of ServiceUI and all my UI problems are gone since. I still have the install.bat though, but I guess I should just change the install command to <ServiceUIx64.exe Deploy-Application.exe> in the DT but as of now that is still on the todo list.

Our client farm consists exclusively of x64 based versions of Windows (mixed 7 and 8.1), so I'm not concerned with a OS architecture detection part of the batch. I'm sure though that would solve it for a mixed platform environment. "Run installation and unins .... as 32-bit process on 64-bit clients" has been ticked all along btw..

Edit: read through the thread a bit and realize that jlapchuks solution is only concerning x86 clients. So conclusion on my part: as long as you're not dealing with x86 clients in your environment, there's no need for psexec and a batch wrapper - at least not my experience.
↧
Search

New Post: Prompting user to close application(s) [Deploy Application Invoker]

January 28, 2015, 7:32 am
$
0
0
Communicator.exe service is used by lync 2010 version . lync.exe Service is used by 2013 version.
↧

New Post: Prompting user to close application(s) [Deploy Application Invoker]

January 28, 2015, 9:12 am
$
0
0
Can you copy and paste the contents of the entire Deploy-Application.ps1?
↧
↧

New Post: Regarding the SCCM limitation with Applications and "allow user to interact with program installation"

January 28, 2015, 10:06 am
$
0
0
Correct, my solution is only intended for mixed environments and only for deployments using the Application model. If all your machines are 64-bit, or you're using the Package model for deployments, then there's no need for ServiceUI and the batch files.
↧

New Post: Trying to detect "Shutdown.exe /r /t 1000"

January 28, 2015, 11:23 am
$
0
0
Trying to detect "Shutdown.exe /r /t 1000"

I came close with ideas from this http://blog.stevex.net/making-a-windows-forms-app-respond-to-system-shutdown/

which translated to PS I get:
[int]$WM_QUERYENDSESSION = 0x11
$m = [System.Windows.Forms.Message]
$msg=$m.GetProperty("msg") #returns $null
Even found something here but it wasn't usable (http://psappdeploytoolkit.codeplex.com)/discussions/538137

Do I really need to go through [System.Windows.Forms] just to get the MSG property to read/detect WM_QUERYENDSESSION?

PS: I'm no C# wiz, I just get by in PowerShell.
↧

New Post: Providing execute-msi or execute-process with variables as parameters even if some are missing

January 28, 2015, 12:07 pm
$
0
0
The separate file already exists as AppDeployToolkitConfig.xml.
The default MSI settings are listed under <MSI_Options>

Otherwise, you'll have to set and use $YourOwnVariables in Deploy-Application.ps1

FYI: Facultatif => Default.

Et ton Englais est bon en masse.
↧
Viewing all 2341 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>