.Net 4.6.1 installation never finishes when using package resource

This topic contains 2 replies, has 3 voices, and was last updated by Profile photo of Dan Dan 6 months, 1 week ago.

  • Author
    Posts
  • #39313
    Profile photo of Amjad Nawaz
    Amjad Nawaz
    Participant

    I am working on to install prerequisites for web server on base OS but i am stuck while installing .Net 4.6.1.
    Below is the part of the configuration , it starts well but never ends:
    on windows server 2012 R2 with WMF 5.0

         
    Package installNet4.6.1
            {
                Ensure = "Present"  # You can also set Ensure to "Absent"
                Path  = "C:\DSC\WMF 5.0\NDP461-KB3102436-x86-x64-AllOS-ENU.exe"
                Name = "NDP461-KB3102436-x86-x64-AllOS-ENU"
                ProductId = "94A631D5-B30A-3DD8-B65C-1117C09DA73E"
            }
    

    Another question i have is related to ProductId used in the package resource.
    I download the .net .exe (NDP461-KB3102436-x86-x64-AllOS-ENU.exe) .
    ORCA too cant extract the productId of .exe file so i extracted the exe and got the ProductId from "\NDP461-KB3102436-x86-x64-AllOS-ENU\NetFx46\netfx_Full_x64.msi"

    Is that correct place to get the ProductId and will it install complete .net 4.6.1

    below is what i see in ISE while installtion never ends :
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Validate-StandardArguments, Path was C:\DSC\WMF 5.0\NDP461-KB3102436-x86-x64-AllOS-ENU.exe
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] The path extension was .exe
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Parsing 94A631D5-B30A-3DD8-B65C-1117C09DA73E as an identifyingNumber
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Parsed 94A631D5-B30A-3DD8-B65C-1117C09DA73E as {94A631D5-B30A-3DD8-B65C-1117C09DA73E}
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Ensure is Present
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] product installation cannot be determined
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] product as boolean is False
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] The package NDP461-KB3102436-x86-x64-AllOS-ENU is not installed
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Validate-StandardArguments, Path was C:\DSC\WMF 5.0\NDP461-KB3102436-x86-x64-AllOS-ENU.exe
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] The path extension was .exe
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Parsing 94A631D5-B30A-3DD8-B65C-1117C09DA73E as an identifyingNumber
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Parsed 94A631D5-B30A-3DD8-B65C-1117C09DA73E as {94A631D5-B30A-3DD8-B65C-1117C09DA73E}
    VERBOSE: [DEVOPSVM2]: [[Package]installNet4.6.1] The binary is an EXE
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Package configuration starting
    VERBOSE: [DEVOPSVM2]: [[Package]installNet4.6.1] Starting C:\DSC\WMF 5.0\NDP461-KB3102436-x86-x64-AllOS-ENU.exe with
    VERBOSE: [DEVOPSVM2]: [[Package]installNet4.6.1] Starting process C:\DSC\WMF 5.0\NDP461-KB3102436-x86-x64-AllOS-ENU.exe with arguments
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] The binary is an EXE
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Starting C:\DSC\WMF 5.0\NDP461-KB3102436-x86-x64-AllOS-ENU.exe with
    VERBOSE: [DEVOPSVM3]: [[Package]installNet4.6.1] Starting process C:\DSC\WMF 5.0\NDP461-KB3102436-x86-x64-AllOS-ENU.exe with arguments

    am i missing something is there a better way to achieve this ?

  • #39436
    Profile photo of Eddie Douse
    Eddie Douse
    Participant

    I tend to get PackageID from a reference machine if I struggle using Orca.

    I'm pretty sure you're also going to need to supply arguments to silently install an EXE without user interaction (remember that DSC is running as local system so it must be silent )

    Try setup.exe /? from your machine to see what arguments are available.

    There is also the option is using the package resource on the extracted MSI which would be far easier (not something I've tried with .Net as I work primarily on systems using Update Services so just install the feature and update)

    Now, with all of that being said. As PowerShell and DSC are .Net related – I honestly don't know what will happen when using them to deploy a new .Net version.

  • #40046
    Profile photo of Dan
    Dan
    Participant

    You'll need to use /Q to get it to run in non-interactive mode. I also suggest using /log in case you encounter a failure.
    For example: Arguments="/q /log c:\temp\netfx\install.txt"

    Here's a link to all of the command-line options:
    https://msdn.microsoft.com/library/ee942965(v=VS.100).aspx#command_line_options

You must be logged in to reply to this topic.