Re: Setup /m off11
From: Scruffy1 (Scruffy1_at_discussions.microsoft.com)
Date: 08/26/04
- Next message: Kevin: "Re: Advanced client in NT domain"
- Previous message: Kevin: "Help....scanwrapper.log errors"
- In reply to: Frank Buzin: "Re: Setup /m off11"
- Next in thread: Scruffy1: "Re: Setup /m off11"
- Reply: Scruffy1: "Re: Setup /m off11"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 26 Aug 2004 08:55:04 -0700
I'm experiencing a similar issue with a different MSI. I've checked my test
station and it meets all the requirements. When I run the job manually, the
MIF is created; when I run it through SMS, it's not. I've tried /mMIFNAME
and /m MIFNAME because I remember there being an issue with spaces in the
past. Any ideas?
"Frank Buzin" wrote:
> I think I found it after much googling. 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/default.asp?url=/library/en-us/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
>
>
> "Frank Buzin" <frankbuzin@mailhot.moc> wrote in message
> news:e8TDcaQgEHA.2928@TK2MSFTNGP10.phx.gbl...
> > I recently scripted a custom install of office 2003 w/ SP1 chained and it
> is
> > installing fine for almost all clients. Yah! We do have a few failures (so
> > far all installer related errors), and I wanted to get more info for our
> SMS
> > guys to use in reporting. Looking at the Office 11.sms file that I know
> our
> > SMS people used, they as using the /m switch to produce a mif file. I'm
> > testing my setup with this switch and I don't see it creating anything. I
> am
> > specifying /m off11 (no .mif ext). I have tried it in various positions on
> > the command line as someone posted that it need to be before the
> > TRANSFORMS=... Is this switch valid (I get no errors using it and the log
> > files indicate it is parsing it) and if so where is the MIF that it
> creates!
> > Right now I'm returning the exit code I get back from setup. So all they
> are
> > getting is install/not install. Would love to use this /m switch and have
> it
> > do something. My command line looks something like this (paths removed):
> >
> > setup.exe /qb- /wait /lpiwaeo+ "Microsoft Office 2003 Setup(*).txt"
> > /settings mysetup.ini /m off11 TRANSFORMS=mytransform.mst /NOREBOOT
> > NOCANCEL=1
> >
> > Works fine to get it installed, but I don't see the /m switch doing
> > anything/
> >
> > Thanks,
> > Frank
> >
> >
>
>
>
- Next message: Kevin: "Re: Advanced client in NT domain"
- Previous message: Kevin: "Help....scanwrapper.log errors"
- In reply to: Frank Buzin: "Re: Setup /m off11"
- Next in thread: Scruffy1: "Re: Setup /m off11"
- Reply: Scruffy1: "Re: Setup /m off11"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
