5 ms·

You can script the OS and application install with WDS, SCCM, and AD. Just because you can't or won't do it doesn't mean it can't be done.

mappu 13y ago
Can you script all those common installers that are (a) not an msi, (b) don't have a /SILENT switch or other unattended installation, (c) require license input, or any combination thereof? I guess you could use AutoHotkey to simulate mouse clicks, or attempt to repackage the software yourself. But when comparing the ability to script installations in general, linux has a major, major advantage.
- cbhl 13y ago
  Repacking all the software yourself so that you can automate the installation of packages is hardly what I'd consider a solution. In practice, people use drive images of Windows, or Ninite, or pay the neighbourhood PFK $12/hr to "automate" it.
  - delian66 13y ago
    What is neighbourhood PFK ?
    - estebank 13y ago
      Pimple Faced Kid
beagle3 13y ago
That's almost funny. I was too lazy to do things properly (kickstart script, etc.) so I have a bash script with about 10 "apt-get install" lines that set up everything I want on Ubuntu or debian, and a few more "echo" lines that configure 90% of my other preferences. 50 line scripts that contain very little other than the names of the programs I want or the configuration I want. Let's say I just got a new computer with Windows 7/8, not part of a domain or anything - just a new laptop. Care to list the steps needed to get into your favorite state (list YOUR favorite 10 apps you need to install)
- leo_mck 13y ago
  I just use the same old .exe that I generate from ninite.com. It takes just one click and I have all my favorite apps running. I just need to install VS2013 and are good to go. It can't be more simple than this.
  - beagle3 13y ago
    Just looked at ninite again (after having not done so in years) and was pleasantly surprised - although it's still very pale compared to Debian's 20k strong packages. But it's definitely a good start. (It can be simpler than this - it is, on modern Linux)
    - deleted 13y ago
      [deleted]
- rblatz 13y ago
  I would use chocolatey nuget http://chocolatey.org http://chocolatey.org. That's how I set up my last machine. Didn't think to a make it a .bat file, but I will next time I build a new machine.
- csense 13y ago
  > Care to list the steps needed to get into your favorite state Well, first you have to figure out how the screen capture API for Windows. Then you have to take screenshots of each screen of the installer program of each application you have to run. Write image recognition code to figure out the location of each button on each tab of each installer screen. Then delve further into the Windows API's to write code to inject mouse movements or keystrokes to make the installations happen. Oh, and if you're using this with a newer version of Windows that uses a different font, or slightly different styling for buttons, or has different UAC dialogs, you're totally hosed. Ditto if any of the installers releases a new version, you may have to make changes. This example demonstrates a command line interface's obvious, inherent, even self-evident superiority to any GUI. Why anyone puts up with the GUI at all is beyond me. It took me ten years to figure out how to get anything done in the GUI when Windows 95 was released; before that, I used the command line pretty much exclusively for moving/copying files and the like.

mappu 13y ago

Can you script all those common installers that are (a) not an msi, (b) don't have a /SILENT switch or other unattended installation, (c) require license input, or any combination thereof? I guess you could use AutoHotkey to simulate mouse clicks, or attempt to repackage the software yourself. But when comparing the ability to script installations in general, linux has a major, major advantage.

cbhl 13y ago
Repacking all the software yourself so that you can automate the installation of packages is hardly what I'd consider a solution. In practice, people use drive images of Windows, or Ninite, or pay the neighbourhood PFK $12/hr to "automate" it.
- delian66 13y ago
  What is neighbourhood PFK ?
  - estebank 13y ago
    Pimple Faced Kid

beagle3 13y ago

That's almost funny. I was too lazy to do things properly (kickstart script, etc.) so I have a bash script with about 10 "apt-get install" lines that set up everything I want on Ubuntu or debian, and a few more "echo" lines that configure 90% of my other preferences. 50 line scripts that contain very little other than the names of the programs I want or the configuration I want. Let's say I just got a new computer with Windows 7/8, not part of a domain or anything - just a new laptop. Care to list the steps needed to get into your favorite state (list YOUR favorite 10 apps you need to install)

leo_mck 13y ago
I just use the same old .exe that I generate from ninite.com. It takes just one click and I have all my favorite apps running. I just need to install VS2013 and are good to go. It can't be more simple than this.
- beagle3 13y ago
  Just looked at ninite again (after having not done so in years) and was pleasantly surprised - although it's still very pale compared to Debian's 20k strong packages. But it's definitely a good start. (It can be simpler than this - it is, on modern Linux)
  - deleted 13y ago
    [deleted]
rblatz 13y ago
I would use chocolatey nuget http://chocolatey.org http://chocolatey.org. That's how I set up my last machine. Didn't think to a make it a .bat file, but I will next time I build a new machine.
csense 13y ago
> Care to list the steps needed to get into your favorite state Well, first you have to figure out how the screen capture API for Windows. Then you have to take screenshots of each screen of the installer program of each application you have to run. Write image recognition code to figure out the location of each button on each tab of each installer screen. Then delve further into the Windows API's to write code to inject mouse movements or keystrokes to make the installations happen. Oh, and if you're using this with a newer version of Windows that uses a different font, or slightly different styling for buttons, or has different UAC dialogs, you're totally hosed. Ditto if any of the installers releases a new version, you may have to make changes. This example demonstrates a command line interface's obvious, inherent, even self-evident superiority to any GUI. Why anyone puts up with the GUI at all is beyond me. It took me ten years to figure out how to get anything done in the GUI when Windows 95 was released; before that, I used the command line pretty much exclusively for moving/copying files and the like.