Muhammad Mashwani

//Muhammad Mashwani
Muhammad Mashwani

Forum Replies Created

Viewing 11 posts - 106 through 116 (of 116 total)
  • Author
    Posts
  • Muhammad Mashwani
    Keymaster
    Post count: 118

    Please be sure to make posts in the appropriate forum. This is the “Deployment Scripts” forum and is strictly for sharing your completed scripts with the community as explained in the forum description: “Repository for example and user contributed deployment scripts.” Requests for help should go into the “General” forum thread.

  • Muhammad Mashwani
    Keymaster
    Post count: 118

    Can you share your full command for executing this function?

  • Muhammad Mashwani
    Keymaster
    Post count: 118

    Can you point out where the guide contradicts the above information you posted?

  • Muhammad Mashwani
    Keymaster
    Post count: 118

    I would say just copy the Get-RunningProcesses function from the beta to the current version of the toolkit you are using as that will resolve your issue.

  • Muhammad Mashwani
    Keymaster
    Post count: 118

    Yup, you’re correct. This is a bug with the current release that I have already implemented a fix for in the latest 3.6.3 beta on GitHub: https://github.com/PSAppDeployToolkit/PSAppDeployToolkit/tree/master/Toolkit/AppDeployToolkit

    This is the relevant item from the 3.6.3 changelog that addresses this issue:
    Fixed issue with Get-RunningProcesses on Windows 7 where the custom object did not return ProcessDescription property unless -PassThru option was used

    Check out the issues list on GitHub to see what the latest reported issues are and which one have been resolved already in the latest beta as they will be tagged with “resolved”. Just as a note, some people are reporting that the latest beta is not detecting logged in users on Win 7 x64, so use with caution at the moment as I am still investigating this issue.

  • Muhammad Mashwani
    Keymaster
    Post count: 118

    Glad to hear the problem is solved. For future reference, please open the log file in CMTrace and copy/paste the text of the log file from there as the above raw log file is very difficult to read. Also, please post log files and code in code blocks by using the “crayon” button you see when you start typing a new message. Lastly, please use the correct forum for your post. This forum is meant for completed scripts people wish to share with the community: “Repository for user submitted functions to extend the toolkit.” The General forum would be more appropriate for this post.

    Thanks!

  • Muhammad Mashwani
    Keymaster
    Post count: 118

    No, I think I understand what you’re trying to do.

    Take one of the examples I mentioned above: the Toolkit_TempPath element in the XML file.
    This element has a defautt value of: $envSystemDrive\Users\Public

    $envSystemDrive is a variable defined in AppDeployToolkitMain.ps1. So you can use the same method we did for this variable to pass $appName to the XML file.

    It does mean that you will have to modify this line in AppDeployToolkitMain.ps1

    [string]$configClosePromptMessage = $xmlUIMessages.ClosePrompt_Message

    to

    [string]$configClosePromptMessage = $ExecutionContext.InvokeCommand.ExpandString($xmlUIMessages.ClosePrompt_Message)
  • Muhammad Mashwani
    Keymaster
    Post count: 118

    Look in the XML file at the following elements: Toolkit_TempPath, Toolkit_LogPath. They both reference variables defined in the toolkit itself.

    If you look at the toolkit, you see that we read and expand the values of these elements using this method:
    $ExecutionContext.InvokeCommand.ExpandString($xmlToolkitOptions.Toolkit_TempPath)

    Do the same for your variable.

  • Muhammad Mashwani
    Keymaster
    Post count: 118

    Make sure you’re using the latest version of the Offscrub scripts . They get updated all the time to fix bugs and there is not indication that there has been an update to the script unless you download it and look at the script version number.

    Also, I never had success with deploying the Offscrub scripts to my environment. We had a lot of problems with the scripts causing hung installs. We eventually targeted, for removal, the specific versions of Office we knew had been pushed into our environment and that worked out pretty well.

    Also, check out some of the command line options for the Offscrub scripts. I remember there were commandline options available that were less aggressive with the removal algorithms and thus less likely to cause possible issues.

  • Muhammad Mashwani
    Keymaster
    Post count: 118
    in reply to: Wix or this ? #128

    WiX is for authoring MSI installs. This is a wrapper toolkit for deploying MSI installs in an enterprise environment. I think they both serve different purposes.

  • Muhammad Mashwani
    Keymaster
    Post count: 118

    Having a “Deploy-Application.exe.config” file is the fix. We include this manifest file with every release now so as to avoid this problem. Keeping an external manifest file is the preference over an internal manifest as it’s easily configurable in the future based on user’s needs.

Viewing 11 posts - 106 through 116 (of 116 total)