|
|
|
|
||||||
| ms.sqlserver.setup Questions about SQL Server. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hello,
How can I pass .ini file to the setup without mentionning the explicit directory name. I use this command and it does not recognize the .ini file: "E:\SQL Exp\setup.exe" /qb /settings setup.ini But I I mention this command it can find it: "E:\SQL Exp\setup.exe" /qb /settings E:\SQL Exp\setup.ini" -- Mike |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Are you try to avoid having to put the ini folder on the same directory for
each computer? You have to express an entire unc path for the ini in this command. What I would do is set up a network share that all computers you are installing SQL on can access. Maybe E:\SQL Exp\setup.exe" /qb /settings \\Server1\SQLExp\setup.ini" If you arent trying to avoid this what problem are you trying to solve? thanks, -- /* Warren Brunk - MCITP - SQL 2005, MCDBA www.techintsolutions.com */ "Mike9900" <Mike9900@discussions.microsoft.com> wrote in message news:68089DC6-EA14-4463-AEF7-5FC712EC94A5@microsoft.com... > Hello, > > How can I pass .ini file to the setup without mentionning the explicit > directory name. I use this command and it does not recognize the .ini > file: > > "E:\SQL Exp\setup.exe" /qb /settings setup.ini > > But I I mention this command it can find it: > > "E:\SQL Exp\setup.exe" /qb /settings E:\SQL Exp\setup.ini" > -- > Mike |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Hello,
I am using DemoShield and want to pass an .ini file to the setup.exe. For example, the user clicks install SQL Server button, and it executes SQL Server and passes .ini. -- Mike "Warren Brunk" wrote: > Are you try to avoid having to put the ini folder on the same directory for > each computer? > > You have to express an entire unc path for the ini in this command. What I > would do is set up a network share that all computers you are installing SQL > on can access. > Maybe E:\SQL Exp\setup.exe" /qb /settings \\Server1\SQLExp\setup.ini" > > If you arent trying to avoid this what problem are you trying to solve? > > thanks, > > -- > /* > Warren Brunk - MCITP - SQL 2005, MCDBA > www.techintsolutions.com > */ > > > "Mike9900" <Mike9900@discussions.microsoft.com> wrote in message > news:68089DC6-EA14-4463-AEF7-5FC712EC94A5@microsoft.com... > > Hello, > > > > How can I pass .ini file to the setup without mentionning the explicit > > directory name. I use this command and it does not recognize the .ini > > file: > > > > "E:\SQL Exp\setup.exe" /qb /settings setup.ini > > > > But I I mention this command it can find it: > > > > "E:\SQL Exp\setup.exe" /qb /settings E:\SQL Exp\setup.ini" > > -- > > Mike > > > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
Then using a UNC path sounds like a good solution? Or can you create the
ini file with that package say in the root of the installation folder then move onto the execution of the installation. -- /* Warren Brunk - MCITP - SQL 2005, MCDBA www.techintsolutions.com */ "Mike9900" <Mike9900@discussions.microsoft.com> wrote in message news:4F840635-4D3D-4D69-849A-B5A69ABEBC77@microsoft.com... > Hello, > > I am using DemoShield and want to pass an .ini file to the setup.exe. For > example, the user clicks install SQL Server button, and it executes SQL > Server and passes .ini. > -- > Mike > > > "Warren Brunk" wrote: > >> Are you try to avoid having to put the ini folder on the same directory >> for >> each computer? >> >> You have to express an entire unc path for the ini in this command. What >> I >> would do is set up a network share that all computers you are installing >> SQL >> on can access. >> Maybe E:\SQL Exp\setup.exe" /qb /settings \\Server1\SQLExp\setup.ini" >> >> If you arent trying to avoid this what problem are you trying to solve? >> >> thanks, >> >> -- >> /* >> Warren Brunk - MCITP - SQL 2005, MCDBA >> www.techintsolutions.com >> */ >> >> >> "Mike9900" <Mike9900@discussions.microsoft.com> wrote in message >> news:68089DC6-EA14-4463-AEF7-5FC712EC94A5@microsoft.com... >> > Hello, >> > >> > How can I pass .ini file to the setup without mentionning the explicit >> > directory name. I use this command and it does not recognize the .ini >> > file: >> > >> > "E:\SQL Exp\setup.exe" /qb /settings setup.ini >> > >> > But I I mention this command it can find it: >> > >> > "E:\SQL Exp\setup.exe" /qb /settings E:\SQL Exp\setup.ini" >> > -- >> > Mike >> >> >> |
|
![]() |
| Outils de la discussion | |
|
|