Another point is management of driver revisions across the life-cycle of the
image, if the printer drivers are being installed by the Print Server as is
normal route then there's no kick back to the image managers when the print
guys replace a driver.

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Daniel Ratliff
Sent: 17 March 2014 18:09
To: [email protected]
Subject: [mssms] RE: Installing printer drivers in your image? Good or bad?

 

This will be used on all machines in the given environment, I was really
just looking for justification for deploying via ConfigMgr as opposed to
updating in the image and having to manage there. 

 

Daniel Ratliff

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Mark Mears
Sent: Monday, March 17, 2014 1:46 PM
To: [email protected] <mailto:[email protected]> 
Subject: [mssms] RE: Installing printer drivers in your image? Good or bad?

 

Part of the criteria I use for including something in the reference image is
whether it will be installed on 100% of the machines being made from that
image.  If the answer is no, then it goes no further.  No doesn't require an
explanation, yes will need to be justified further and does not imply
automatic inclusion.

 


Thanks, 


 

Mark Mears

[email protected] <mailto:[email protected]%0d> 

Phone: (757) 945-2651

 

 <http://www.cireson.com/> 


 <http://twitter.com/teamcireson>   Check out our System Center App Store:
www.cireson.com/app-store

"Self Service Portal Unleashed!" Webinar |  <https://vimeo.com/87792187>
Watch it here.

 


  _____  

 

 

From: [email protected] <mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Daniel Ratliff
Sent: Monday, March 17, 2014 11:53 AM
To: [email protected] <mailto:[email protected]> 
Subject: [mssms] Installing printer drivers in your image? Good or bad?

 

I am researching this topic and looking for opinions on whether this is a
good idea or not. I always understood that printer drivers are just like
device drivers, you don't want them in your image for risk of compatibility.
Am I mistaken? The same logic applies as to why you don't build an image on
physical hardware, always a VM?

 

Daniel Ratliff 

 


The information transmitted is intended only for the person or entity to
which it is addressed
and may contain CONFIDENTIAL material. If you receive this
material/information in error,
please contact the sender and delete or destroy the material/information.

 

 


The information transmitted is intended only for the person or entity to
which it is addressed
and may contain CONFIDENTIAL material. If you receive this
material/information in error,
please contact the sender and delete or destroy the material/information.

 



<<image001.png>>

<<image002.jpg>>

Reply via email to