There is no system files that uses the MDI printer. So you can make this
option to be not available during deployment.
When you need to deploy this on a big network, use Custom Installation
Wizard (CIW) which is available if you install the Office Resource Kit tools.
On page 7 in CIW, expand "office tools" and make "microsoft office document
imaging" to be not available.
Finish the process to create an MST file.
Install the software using the newly created MST file.
"Sandy" wrote:
[Quoted Text] > How can we deploy Office and keep the Microsoft Office Document Image
> Writer from being enabled as the default printer? Because it installs
> itself as the default printer, it causes much confusion among users who
> are trying to print to other printers once other printers are added to
> the workstation. In an enterprise environment, we would prefer to be
> able to install the MS Image Writer only when we need it, instead of
> having it forced down our throats, causing us to have to manually
> remove it on every workstation. Please help!
>
> The posting below looks like it might have been a step in the right
> direction, but nobody ever replied to this guy and the topic has since
> been closed.
>
>
> MS Office Document Image Writer - how to remove via GP?
> Only 1 message in topic - view as tree
> From: Mark - view profile
> Date: Thurs, Dec 1 2005 8:25 am
> Email: "Mark" <M...[ at ]discussions.microsoft.com>
> Groups: microsoft.public.office.setup
> Not yet ratedRating:
> show options
> Reply | Reply to Author | Forward | Print | Individual Message | Show
> original | Report Abuse | Find messages by this author
>
>
> I have about 500 workstations, everyone that has Office 2003 installed
> gets
> the Document Image Writer installed. No one in our corporation uses
> that
> "printer" and it usually gets installed as a default. I would like to
> know if
> there's a GPO or anything to remove it permanently, if I can modify the
>
> Office install files to remove it after Office has been installed, to
> hide
> it, or to never have it be the default... ever. I do understand that
> some
> programs may need some MDI system files to run properly, that's why I
> would
> rather it NOT be the default but still available.
>
>
|