I have to bump this. I can't believe no one has had a similar issue. I don't use a printer at home and so I really need a way to install Office Document Image Writer.

Sorry for the late response, I've been swamped for the past 3-4 weeks.



You know, this is something I've never tested and I probably should. I'll get to checking this week and get back to you once I have, it's been added to my official to-do list so I won't forget but there's a chance I might not get to it until like Friday.

Thank you for replying. And take your time, I'm glad just to see someone is helping.

When you captured MS office, did you do a global capture? If not, that is probably the issue...



also, when I capture applications that install 'virtual' printer drivers, I always add "net stop spooler" to the PreActivate event, and "net start spooler" to the Post activate event, as this has solved issues in the past.



Cheers,

Phil

Crappy news, but I appreciate the answers. Thanks again!

quote:
Originally posted by: Spriggan

Phil is right you're going to have to global capture, which with an install like office probably isn't a good thing, to get this. You don't have to restart the print spool if the layer is set to auto activate.

Globally capturing it should not be a problem, but you will have to put in allot of work to tidy up the package.



If the layer is going to be activated on demand / per user, then starting and stopping the print spooler is normally required. Also if it is being deployed whilst a user is logged on, it is also required...

just my experience



Cheers

Phil

To help cut down on clutter from a global capture I recomend doing it on a clean system that just has SVS installed and nothing else running.

I'm seeing that the printer gets installed during the single program capture of office 2007 setup but...it's installed to the base and not the layer. Does anyone know of a way to grab the files/reg keys that define the printer and put it in the layer ? And if so, or even if you find a way to capture the printer in the layer during the office install, isn't it going to create a conflict with existing enumerated ports? I'd imagine an existing system already uses ne00 but that's what MODI gets setup as during the inital capture since it's the first printer on a clean XP setup...

When capturing ANYTHING that has to do with drivers / services with SVS ALWAYS use the global capture method. I have seen alot of problems with services / drivers not being picked up correctly when not using the global capture method.



I know this means that you have extra effort in cleaning up the resulting package, but by my own exp. this is the only reliable method of getting an accruate capture.



Regarding the conflicting printer driver, this is something that you might have to engineer in the package (i.e. not use NE01 entries in the registry, but perhaps something larger like NE09 etc.)



If I remember rightly, with the new release of SVS, layer visabilty can be reduced, so that the base does not see the layer, therefore conflicts should be avoided...



Cheers

Phil