Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio
All postings are provided AS IS
with no warranties, and confer no rights. Additionally, views expressed
herein are my own and not those of my employer, Microsoft.
I tried to install Visual Studio 2005 using the unattended installation instructions that you previously posted, and in some cases I see that the computer reboots without any notification to the user, and I have to either log the computer back on or configure automatic logon to allow unattended setup to finish installing VS 2005. When I searched through the log files I found that one of the prerequisite components required a reboot.
How can I configure unattended installation so that it will suppress reboots until the end so I can avoid this scenario?
Visual Studio 2005 unattended installation suppresses all UI, and it does not have built-in support for suppressing reboots until the end. In previous versions of Visual Studio (VS .NET 2002 and 2003), the recommended solution for this scenario was to create a script that pre-installs each of the prerequisite components and then installs VS using the /unattendfile switch and an unattended INI file. Doing this allows you to manage any possible reboots during prerequisite setup package installation on a more granular level.
However, VS 2005 setup shipped with a bug in the unattended INI file creation process that causes prerequisite components to be included for installation in the INI file even if they have already been installed on the system. I previously talked about a workaround for this type of issue on Windows Vista in this blog post. A couple of recent emails from customers alerted me to the fact that this issue happens on all operating systems and not just on Windows Vista.
In order to create a script that that will allow you to suppress reboots during unattended installation of VS 2005, you will need to do the following:
1. Create and modify an unattended INI file to work around the bug described above:
2. Create a script to install the prerequisites and then run VS 2005 in unattended mode:
Knowledge base article KB913445 also describes this scenario and provides a slightly different workaround. That knowledge base article only describes how to fix x86 installation scenarios, so I would suggest following the steps in this blog post instead of the ones in the knowledge base article.
<update date="3/26/2006"> Added a link to a knowledge base article which was recently published about this scenario </update>
Recently, a fellow employee contacted me with a question about unattended installation of Visual Studio
This guide is intended to serve as a collection of links to articles, tools, tips and tricks that explain
PingBack from http://aisweb.artinsoft.net/aisblogs/jose_aguilar_blog/archive/2006/09/05/1159.aspx
I tried the steps in the blog but am not able to successgully install vs using the unattend file
i can see setup process started in the task manager but after few min the process ends
"c:\visual studio 2005\vs\setip\setup.exe" /unattendfile c:\vs_2005.ini
is the mcd am using ... pls tell e wer am making mistake
Hi Vs unattended installation - Can you please list the exact steps that you've tried and the exact errors that you're currently seeing? Also, can you please zip and upload your VS setup log files to a file server (such as http://skydrive.live.com) and reply here with a link I can use to download the logs and take a look? You can find a list of VS 2005 setup log files in the blog post at blogs.msdn.com/.../447012.aspx.
<VS install source>\setup\setup.exe /unattendfile vs_2005.ini
This can be a problem if you are deploying this via SCCM unless you specify the UNC path for the location where the ini file is stored or else SCCM isn't smart enough to assume that the ini file is located in the same directory as the setup.exe
Therefore the command line should be like <VS install source>\setup\setup.exe /unattendfile \\path to ini\vs_2005.ini which can represent an issue down the road for deployment