none
Remote install of dot net 3.5 on windows 7 hangs RRS feed

  • Question

  • I get no error message for this, left it running for 3 hours and then restarted the remote install.

    The last few entries in dd_dotnetfx35install are:

    [08/12/09,16:33:36] vs70uimgr: CUIMgr::LoadPages(): Finished adding Global Property: CustomCoreProp_AutoLoginAvailable
    [08/12/09,16:33:36] vs70uimgr: CUIMgr::Start(): Finished loading Pages
    [08/12/09,16:33:36] vs70uimgr: CUIMgr::Start(): Creating Main Thread Events
    [08/12/09,16:33:36] vs70uimgr: Entering DisplayStartup() method. - not custom implemented
    [08/12/09,16:33:36] Setup.exe: ISetupManager::ResetBaselineActions() : SMP_SUITEBASELINE
    [08/12/09,16:33:36] Setup.exe: ISetupManager::GetBaslineComponents()
    [08/12/09,16:33:36] Setup.exe: ISetupManager::ResetBaselineActions() : SMP_SUITEBASELINE
    [08/12/09,16:33:36] Setup.exe: ISetupManager::GetBaslineComponents()
    [08/12/09,16:33:36] Setup.exe: ISetupManager::ResetBaselineActions() : SMP_SCENARIOBASELINE
    [08/12/09,16:33:36] vs70uimgr: Entering ThreadUI() method.
    [08/12/09,16:33:37] vs70uimgr: CUIMGr::SetWindowTitle(): Getting Property Value for: VS Custom;ProdDesc
    [08/12/09,16:33:37] vs70uimgr: CUIMGr::SetWindowTitle(): Finished getting Property Value for: VS Custom;ProdDesc
    [08/12/09,16:33:37] VS Scenario: IVSSetupScenarioImpl::GetBaslineComponents()
    [08/12/09,16:33:37] vs70uimgr: Entering SelectScenario() method. - not custom implemented
    [08/12/09,16:33:37] Setup.exe: ISetupManager::RunIntro() : CheckBaselines
    [08/12/09,16:33:37] Setup.exe: MoveLoadProgress()
    [08/12/09,16:33:37] Setup.exe: ISetupManager::RunIntro() : StartUIManager
    [08/12/09,16:33:37] Setup.exe: MoveLoadProgress()
    [08/12/09,16:33:37] Setup.exe: StartUIManager()
    [08/12/09,16:33:37] vs70uimgr: Entering RunScenario() method.
    [08/12/09,16:33:37] vs70uimgr: CUIMgr::RunScenario(): Starting the active scenario
    [08/12/09,16:33:37] Setup.exe: GetGlobalCustomProperty - Property: {AA62DF98-3F2C-11D3-887B-00C04F8ECDD6} - PropertyName: Maintenance Mode - Value: 0
    [08/12/09,16:33:37] Setup.exe: GetGlobalCustomProperty - Property: {340F7930-0E41-11D3-ACE2-00C04F8EEBA1} - PropertyName: Output Unattend File - Value:
    [08/12/09,16:33:37] VS Scenario: Validating system requirements
    [08/12/09,16:33:37] Setup_Blocked: CSupportedPlatformCheck
    [08/12/09,16:33:37] Setup.exe: GetGlobalCustomProperty - Property: {092114C2-997D-4D68-8F3A-8BC2584FD23B} - PropertyName: Quiet Mode Setup - Value:

    Would appreciate any pointers as to what the problem may be :)


    Wednesday, August 12, 2009 3:48 PM

Answers

  • When you use the 3.5 installation package on Windows 7, it will popup a dialog telling you to use "Turn Windows features on or off" instead. This is by design and we cannot change it.

    it would be better though if the installstate could be remotely set to enabled.  Is this possible?

    Yes. You can run the ocsetup command on the remote Windows 7 PC to enable the "Microsoft .NET Framework 3.5.1" feature.

    The package name for this feature is NetFx3 (case sensitive).

    So the command line will be:

    ocsetup NetFx3

    And that will install the feature. You can manually try it first on Windows 7 in a admin command prompt, then figure out how to run it remotely via WMI.

    Hope this helps.

    Jie
    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg@microsoft.com
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    If you have any feedback, please tell us.

    The CodeFx Project
    My Blog (in Simplified Chinese)
    Friday, August 14, 2009 9:39 AM
    Moderator

All replies

  • Hi,

    Windows 7 has .NET Framework 3.5.1 in place by default, is there any reason to install it again?

    Could you please provide more background information of what do you want to achieve?

    Thanks!

    Jie
    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg@microsoft.com
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    If you have any feedback, please tell us.

    The CodeFx Project
    My Blog (in Simplified Chinese)
    Thursday, August 13, 2009 10:23 AM
    Moderator
  • Hi,

    We have an application that is doing remote installs of a windows service, one of the prerequisites of the service is the installation of dot net 3.5.

    When the user selects a computer to install the service on the application checks the current framework version on the remote computer and if it is not 3.5 it then attempts a remote install of 3.5 using the /q (quiet) option.

    One of the test scenarios is for windows 7 with dot net 3.5.1 disabled under windows features.  In this case it reports a dot net version of 3.0, the application then attempts to run the 3.5 install but it seems windows 7 has popped a message box (which cannot be seen) which advises checking windows features.  The install then hangs.  The message box can be seen when running the install directly on the remote machine in quiet mode.

    I have found a workaround for this in that the installstate can be queried through wmi and an error is thrown if 3.5.1 is disabled, it would be better though if the installstate could be remotely set to enabled.  Is this possible?
    Thursday, August 13, 2009 3:20 PM
  • When you use the 3.5 installation package on Windows 7, it will popup a dialog telling you to use "Turn Windows features on or off" instead. This is by design and we cannot change it.

    it would be better though if the installstate could be remotely set to enabled.  Is this possible?

    Yes. You can run the ocsetup command on the remote Windows 7 PC to enable the "Microsoft .NET Framework 3.5.1" feature.

    The package name for this feature is NetFx3 (case sensitive).

    So the command line will be:

    ocsetup NetFx3

    And that will install the feature. You can manually try it first on Windows 7 in a admin command prompt, then figure out how to run it remotely via WMI.

    Hope this helps.

    Jie
    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg@microsoft.com
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    If you have any feedback, please tell us.

    The CodeFx Project
    My Blog (in Simplified Chinese)
    Friday, August 14, 2009 9:39 AM
    Moderator
  • Jie,

    Thanks for the help, all works fine now on Windows 7 :)
    Friday, August 14, 2009 3:00 PM
  • Great to know it works.

    Have a nice day!

    Best regards,
    Jie
    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg@microsoft.com


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    If you have any feedback, please tell us.

    The CodeFx Project
    My Blog (in Simplified Chinese)
    Friday, August 14, 2009 4:11 PM
    Moderator