Office 2003 Setup /m switch

F

Frank Buzin

I think I found it. To use the /m switch with the setup wrapper (that in
turn passes it to msiexec where it is used), you must have ISMIF32.DLL
located somewhere in the path. See msiexec command line options:

http://msdn.microsoft.com/library/d...msi/setup/command_line_options.asp?frame=true

It is very possible that my test PC at work doesn't have the adv client on
it yet (I was testing from my CD installation, not an SMS push) or it has
issues.

Anyway these appear to be the requirements for using the /M switch:

1) ISMIF32.DLL present (normally there from an SMS client install, but
comes with some dev products like Visual Studio 6.0)

2) No extension (i.e. .MIF) should be supplied

3) Should not include path (mif will always be placed in %systemroot%)

4) Name specified must be 8 characters or less


I know I met 2-4, but I bet ISMIF32.DLL not being in the path is the
problem.

Thanks,
Frank
 
F

Frank Buzin

I think I found it. To use the /m switch with the setup wrapper (that in
turn passes it to msiexec where it is used), you must have ISMIF32.DLL
located somewhere in the path. See msiexec command line options:

http://msdn.microsoft.com/library/d...msi/setup/command_line_options.asp?frame=true

It is very possible that my test PC at work doesn't have the adv client on
it yet (I was testing from my CD installation, not an SMS push) or it has
issues.

Anyway these appear to be the requirements for using the /M switch:

1) ISMIF32.DLL present (normally there from an SMS client install, but
comes with some dev products like Visual Studio 6.0)

2) No extension (i.e. .MIF) should be supplied

3) Should not include path (mif will always be placed in %systemroot%)

4) Name specified must be 8 characters or less


I know I met 2-4, but I bet ISMIF32.DLL not being in the path is the
problem.

Thanks,
Frank
 
F

Frank Buzin

I think I found it. To use the /m switch with the setup wrapper (that in
turn passes it to msiexec where it is used), you must have ISMIF32.DLL
located somewhere in the path. See msiexec command line options:

http://msdn.microsoft.com/library/d...msi/setup/command_line_options.asp?frame=true

It is very possible that my test PC at work doesn't have the adv client on
it yet (I was testing from my CD installation, not an SMS push) or it has
issues.

Anyway these appear to be the requirements for using the /M switch:

1) ISMIF32.DLL present (normally there from an SMS client install, but
comes with some dev products like Visual Studio 6.0)

2) No extension (i.e. .MIF) should be supplied

3) Should not include path (mif will always be placed in %systemroot%)

4) Name specified must be 8 characters or less


I know I met 2-4, but I bet ISMIF32.DLL not being in the path is the
problem.

Thanks,
Frank
 
F

Frank Buzin

I think I found it. To use the /m switch with the setup wrapper (that in
turn passes it to msiexec where it is used), you must have ISMIF32.DLL
located somewhere in the path. See msiexec command line options:

http://msdn.microsoft.com/library/d...msi/setup/command_line_options.asp?frame=true

It is very possible that my test PC at work doesn't have the adv client on
it yet (I was testing from my CD installation, not an SMS push) or it has
issues.

Anyway these appear to be the requirements for using the /M switch:

1) ISMIF32.DLL present (normally there from an SMS client install, but
comes with some dev products like Visual Studio 6.0)

2) No extension (i.e. .MIF) should be supplied

3) Should not include path (mif will always be placed in %systemroot%)

4) Name specified must be 8 characters or less


I know I met 2-4, but I bet ISMIF32.DLL not being in the path is the
problem.

Thanks,
Frank
 
F

Frank Buzin

I think I found it. To use the /m switch with the setup wrapper (that in
turn passes it to msiexec where it is used), you must have ISMIF32.DLL
located somewhere in the path. See msiexec command line options:

http://msdn.microsoft.com/library/d...msi/setup/command_line_options.asp?frame=true

It is very possible that my test PC at work doesn't have the adv client on
it yet (I was testing from my CD installation, not an SMS push) or it has
issues.

Anyway these appear to be the requirements for using the /M switch:

1) ISMIF32.DLL present (normally there from an SMS client install, but
comes with some dev products like Visual Studio 6.0)

2) No extension (i.e. .MIF) should be supplied

3) Should not include path (mif will always be placed in %systemroot%)

4) Name specified must be 8 characters or less


I know I met 2-4, but I bet ISMIF32.DLL not being in the path is the
problem.

Thanks,
Frank
 
F

Frank Buzin

I think I found it. To use the /m switch with the setup wrapper (that in
turn passes it to msiexec where it is used), you must have ISMIF32.DLL
located somewhere in the path. See msiexec command line options:

http://msdn.microsoft.com/library/d...msi/setup/command_line_options.asp?frame=true

It is very possible that my test PC at work doesn't have the adv client on
it yet (I was testing from my CD installation, not an SMS push) or it has
issues.

Anyway these appear to be the requirements for using the /M switch:

1) ISMIF32.DLL present (normally there from an SMS client install, but
comes with some dev products like Visual Studio 6.0)

2) No extension (i.e. .MIF) should be supplied

3) Should not include path (mif will always be placed in %systemroot%)

4) Name specified must be 8 characters or less


I know I met 2-4, but I bet ISMIF32.DLL not being in the path is the
problem.

Thanks,
Frank
 
F

Frank Buzin

I think I found it. To use the /m switch with the setup wrapper (that in
turn passes it to msiexec where it is used), you must have ISMIF32.DLL
located somewhere in the path. See msiexec command line options:

http://msdn.microsoft.com/library/d...msi/setup/command_line_options.asp?frame=true

It is very possible that my test PC at work doesn't have the adv client on
it yet (I was testing from my CD installation, not an SMS push) or it has
issues.

Anyway these appear to be the requirements for using the /M switch:

1) ISMIF32.DLL present (normally there from an SMS client install, but
comes with some dev products like Visual Studio 6.0)

2) No extension (i.e. .MIF) should be supplied

3) Should not include path (mif will always be placed in %systemroot%)

4) Name specified must be 8 characters or less


I know I met 2-4, but I bet ISMIF32.DLL not being in the path is the
problem.

Thanks,
Frank
 
F

Frank Buzin

I think I found it. To use the /m switch with the setup wrapper (that in
turn passes it to msiexec where it is used), you must have ISMIF32.DLL
located somewhere in the path. See msiexec command line options:

http://msdn.microsoft.com/library/d...msi/setup/command_line_options.asp?frame=true

It is very possible that my test PC at work doesn't have the adv client on
it yet (I was testing from my CD installation, not an SMS push) or it has
issues.

Anyway these appear to be the requirements for using the /M switch:

1) ISMIF32.DLL present (normally there from an SMS client install, but
comes with some dev products like Visual Studio 6.0)

2) No extension (i.e. .MIF) should be supplied

3) Should not include path (mif will always be placed in %systemroot%)

4) Name specified must be 8 characters or less


I know I met 2-4, but I bet ISMIF32.DLL not being in the path is the
problem.

Thanks,
Frank
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Upgrading to Office 2003 0
Error 0x80070002 failed to open product's delivery key 9
using silent setup with Microsoft Custom Installation Wizard 10
Error 1719 when trying to add Office Pro 2003 components.(bit long) 0
Office 2007 and XP Web Components 0
office 2003 setup error 1911 0
office 2007 enterprise setup help 1
Office 2003 Setup Questions 0

Top