none
Installing a compiler and SDK on compute nodes

    Question

  • We are adding Visual Studio C++ Express 2008 to our compute nodes as well the the Windows 7 SDK so we can use the x64 compiler.
    The SDK comes with multiple .msi files - (too numerous to list here) they provide an .exe which uses all the .msi's to install the components we need.

    Looking for a simple way to install the SDK to the compute nodes. Any suggestions?

    We have found a way to install VS C++ Express using a command line with an msi file.

    We would prefer not to re-image the compute nodes, and also prefer not to have to log in remotely to each compute node to install the SDK.

    Thanks in Advance!

    Thursday, February 18, 2010 5:32 PM

Answers

  • My previous comment about the SDK not supporting unattend was incorrect, sorry. There were older versions of the SDK that didn't unattend install correctly, but this new Win7 one works just fine.

    I used your command line and the SDK installed just fine.

    You are giving it enough time to complete before killing it right? The SDK takes a long time to install (like a half hour)
    Friday, February 19, 2010 9:45 PM
    Moderator

All replies

  • You should be able install our SDK on your compute nodes without any user interaction using a command line such as the following:

    clusrun msiexec.exe /i [yourpath\]sdk_x64.msi /passive

    Regards,

    Patrick

    Thursday, February 18, 2010 6:11 PM
  • From the DVD, a list of the Setup folders is shown below.
    From which of the directories listed should we choose msi files from?


    07/15/2009  03:10 PM    <DIR>          .
    07/15/2009  03:09 PM    <DIR>          ..
    07/14/2009  09:34 PM            23,071 SDKSetup.cab
    07/14/2009  09:34 PM         1,623,872 SDKSetup.exe
    07/15/2009  03:09 PM    <DIR>          WinSDKApplicationVerifier
    07/15/2009  03:09 PM    <DIR>          WinSDKApplicationVerifier_amd64
    07/15/2009  03:09 PM    <DIR>          WinSDKApplicationVerifier_ia64
    07/15/2009  03:09 PM    <DIR>          WinSDKBuild_amd64
    07/15/2009  03:09 PM    <DIR>          WinSDKDebuggingTools
    07/15/2009  03:09 PM    <DIR>          WinSDKDebuggingTools_amd64
    07/15/2009  03:09 PM    <DIR>          WinSDKDebuggingTools_ia64
    07/15/2009  03:09 PM    <DIR>          WinSDKDocNetFx_amd64
    07/15/2009  03:10 PM    <DIR>          WinSDKDocWin32_amd64
    07/15/2009  03:10 PM    <DIR>          WinSDKIntellisenseRefAssys_amd64
    07/15/2009  03:10 PM    <DIR>          WinSDKInterop_amd64
    07/15/2009  03:10 PM    <DIR>          WinSDKNetFxTools_amd64
    07/15/2009  03:10 PM    <DIR>          WinSDKRedist_amd64
    07/15/2009  03:10 PM    <DIR>          WinSDKSamples_amd64
    07/15/2009  03:10 PM    <DIR>          WinSDKTools_amd64
    07/15/2009  03:10 PM    <DIR>          WinSDKWin32Tools_amd64
    07/15/2009  03:09 PM    <DIR>          WinSDK_amd64
    07/15/2009  12:58 AM            59,224 custsat_amd64.dll
    07/15/2009  04:52 AM           105,304 custsat_ia64.dll
    07/14/2009  09:34 PM            39,752 custsat_x86.dll
    07/15/2009  03:09 PM    <DIR>          vc_stdamd64
    07/15/2009  03:09 PM    <DIR>          vc_stdia64
    07/15/2009  03:09 PM    <DIR>          vc_stdx86
    07/15/2009  03:09 PM    <DIR>          winsdk_intellidocs
                   5 File(s)      1,858,955 bytes
                  23 Dir(s)               0 bytes free

    We've looked at the log file created by running the setup - it's almost 3000 lines long, with multiple msi's being referenced.
    Are we supposed to parse all this and come up with our own install using mutiple msi files?

    There must be a better way...

    Thursday, February 18, 2010 6:49 PM
  • Sorry about that, I answered your question thinking you were asking how to install the HPC SDK on your compute nodes.

    As for the Windows 7 SDK, on your CD in the folder above the one you listed, is there a setup.exe file?

    If so, you should be able to run that with a "-q" argument to perform a quiet installation. The full usage can be seen by running "setup.exe /?".

    Let me know how you go.

    Regards,

    Patrick

    Thursday, February 18, 2010 7:28 PM
  • Thanks Patrick,

    Unfortunately, I can't seem to get this to work.
    Here is one of the commands I have tried:

    d:\Setup.exe -source:"d:\Setup" -params:WinSDK:ADDLOCAL=ALL -q -l:c:\temp\sdkinstall.log

    This seems to copy the files over and then just stops - I can see the SDKSetup.exe running in the taskmanager but no further progress is made.
    Any suggestions?

    Friday, February 19, 2010 2:09 AM
  • Not all products support unattended installs. You've run in to one of them unfortunately!

    Try running setup.exe /? and see if a dialog comes up showing the other command line switches, there may be one related to 'eula' or 'license' that you can use to indicate you've read & accept the license terms.

    If you have a small cluster, logging in to each and installing is one solution. If you have a large cluster you could consider installing the SDK, plus any other apps you want, on one node and then using the WAIK (windows advanced installation kit) to make an image from that machine. You could then use that custom image to redeploy all your nodes.
    Friday, February 19, 2010 3:39 AM
    Moderator
  • I'm not quite sure what you mean when you say it just copies the files over. The SDKSetup.exe process should run for quite a while as it installs the (quite-large) package.

    Also, it should be sufficient to just use "d:\setup.exe -q" instead of specifying the source and other params.

    I suggest testing out your command line without the -q and see if it displays any error dialogs.

    Regards,

    Patrick
    Friday, February 19, 2010 3:42 AM
  • What is a goal of adding SDK to all of compute nodes? isnt better to add all necessary libs as a static?
    sorry if i don't understand you properly.

    Friday, February 19, 2010 5:55 AM
  • My previous comment about the SDK not supporting unattend was incorrect, sorry. There were older versions of the SDK that didn't unattend install correctly, but this new Win7 one works just fine.

    I used your command line and the SDK installed just fine.

    You are giving it enough time to complete before killing it right? The SDK takes a long time to install (like a half hour)
    Friday, February 19, 2010 9:45 PM
    Moderator
  • Thanks for the replies.
    Currently if I to run the following:

    \\somemachine\t$\SDKDVD\Setup\SDKSetup -source:"\\somemachine\t$\SDKDVD\Setup" -params:WinSDK:ADDLOCAL=ALL -q -l:c:\temp\sdkinstall.log

    The last line that appears in the log file is...
    9:52:15 AM Monday, February 22, 2010: [SDKSetup:Info] File succesfully downloaded - source:file://somemachine/t$/SDKDVD/Setup/WinSDKDebuggingTools_amd64/dbg_amd64_6.11.1.404.msi target:file:///C:/Users/myuserid/AppData/Local/Temp/SDKSetup/WinSDKDebuggingTools/WinSDKDebuggingTools_amd64/dbg_amd64_6.11.1.404.msi size:15953408

    No further progress is made, waited 40 minutes just to make sure. If I look in the Users Temp directory the SDKSetup contains all of the folders and msi files.
    Could this be a problem running from a UNC?
    I first thought maybe I was having issues as I installed and un-installed the SDK several times trying different things. So the system was not pristine that this was tested on. The computer tested this morning was one not used previously.
    At this point I am installing the individual msi files that we need. This seems to work just fine.
    Thanks again for the suggestions.

    Monday, February 22, 2010 4:04 PM
  • I'm sorry to hear you're still having trouble.

    Have you tried running "\\somemachine\t$\SDKDVD\setup.exe -q" without any other arguments at all? (i.e. not sdksetup.exe) Does that work any better for you?

    Regards,

    Patrick
    Monday, February 22, 2010 7:33 PM
  • Hi - No, I don't beleive I tried that exact command.
    We are all set with what we need now, so I do not have time to work on this further or test out different commands.

    Monday, February 22, 2010 8:16 PM