Ha... Our lead Desktop guy was just finishing a rebuild of our ThinkPad X230 packages under v3... I wonder if he'll want to jump on v4 and do it over again already.
On Thu, Jul 11, 2013 at 7:39 AM, Stewart, Michael <[email protected]>wrote: > Looks like v4 was released today J**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Benjamin Monrad > > *Sent:* Wednesday, July 10, 2013 2:27 PM > *To:* [email protected] > *Subject:* Re: [mssms] SCCM OSD Driver Managers**** > > ** ** > > We started with ENGL last year at a time when we were migrating from CM07 > to CM12, and wanted to revamp our approach to driver organization anyway.* > *** > > ENGL took away a lot of the pain of getting up and running with about 20 > models all at the same time, but was not perfect. Our main Desktop engineer > working on OSD estimates ENGL got us 80% of the way there out of the box, > and left 20% of oddball items to figure out between Lenovo annoyances and > ENGL behavior. Part of the issue was ENGL didn't seem to have many Lenovo > customers at the time so we were making a lot of first time requests for > them to catalog drivers for our models (plus we were trying to test a > couple not-typically-enterprise Ultrabook models at the same time).**** > > We will probably renew our license in order to try out the new version due > out soon which is expected to take care of a lot of the "remaining 20%", > and they say they have a stronger Lenovo customer base now.**** > > ** ** > > On Wed, Jul 10, 2013 at 2:19 PM, Charles Moore <[email protected]> > wrote:**** > > Manual here, it’s really not that bad, once you configure it, you > shouldn’t have to touch it again unless something doesn’t work in the > future.**** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Underwood, Bob > *Sent:* Wednesday, July 10, 2013 1:27 PM > *To:* [email protected]**** > > > *Subject:* RE: [mssms] SCCM OSD Driver Managers**** > > **** > > I’m in roughly the same boat for models, and the overall picture is > getting worse lately… have had to recently add support for a 32-bit version > of Windows 7, and we’re ramping up with Windows 8 as well.**** > > **** > > With that said, I’m still doing it all manually. One of the biggest pain > points is hardware-specific applications and troublesome drivers like > Bluetooth… which all have to be packaged. One of the driver automation > vendors was promising complete automation of those kinds of things as well, > but when I dug deeper I found that it didn’t really do much in that regard. > **** > > **** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Daniel Ratliff > *Sent:* Monday, July 08, 2013 5:53 PM > *To:* '[email protected]'; '[email protected]' > *Subject:* RE: [mssms] SCCM OSD Driver Managers**** > > **** > > Nope all manual. We have upwards of 35 models and about 20 driver packages. > > -----Original Message----- > *From: *Stewart, Michael [[email protected]] > *Sent: *Monday, July 08, 2013 06:49 PM Eastern Standard Time > *To: *[email protected] > *Subject: *[mssms] SCCM OSD Driver Managers**** > > Quick question for everyone. Anybody use Driver Management Software like > ENGL etc. to manage the driver packages for OSD? Or all manually?**** > > **** > > Mike**** > > **** > ------------------------------ > > - CONFIDENTIAL- > > This email and any files transmitted with it are confidential, and may > also be legally privileged. If you are not the intended recipient, you may > not review, use, copy, or distribute this message. If you receive this > email in error, please notify the sender immediately by reply email and > then delete this email. > > > 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.* > *** > > **** > > [CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email > is proprietary to Medtronic and is intended for use only by the individual > or entity to which it is addressed, and may contain information that is > private, privileged, confidential or exempt from disclosure under > applicable law. If you are not the intended recipient or it appears that > this mail has been forwarded to you without proper authority, you are > notified that any use or dissemination of this information in any manner is > strictly prohibited. In such cases, please delete this mail from your > records. To view this notice in other languages you can either select the > following link or manually copy and paste the link into the address bar of > a web browser: http://emaildisclaimer.medtronic.com**** > > **** > > ** ** > ------------------------------ > > > CONFIDENTIALITY NOTICE: This email message and any attachments hereto are > intended only for use by the addressee(s) named herein and may contain > information which is legally privileged, confidential and/or exempt from > disclosure under applicable law. If you are not the intended recipient, or > an authorized representative of the intended recipient, of this email > message, you are hereby notified that any review, dissemination, > distribution, copying, or use (including any reliance thereon) of this > email message, and/or any attachment hereto, is strictly prohibited. > > Although this transmission and any attachments are believed to be free of > any virus or other defect that might affect any computer system into which > it is received and opened, it is the responsibility of the recipient to > ensure that it is free from virus or other defect and no responsibility is > accepted by the sending company, its subsidiaries and affiliates, as > applicable, for any loss or damage arising in any way from its use. > > If you have received this email message in error, please immediately > notify the sender by return email and permanently delete from your system, > the original and any copies of this email and any attachments hereto and > any printout hereof. Unauthorized interception of this email is a violation > of federal criminal law.**** > > ** ** > > ** ** > > ** ** > >
