I usually only use the manufacturer's drivers.  I don't even allow WSUS to
pull the drivers from Microsoft.  If I want/need drivers updated I much
prefer to do them manually until I am sure they will not blow up.  That
said once the hardware is about 5 to 10 years old I use the Microsoft
drivers.  Some times it is just too hard to find the drivers on the
manufacturer's site for those.  I have had at a previous job kept hardware
in production for 10 to 15 years or until it finally gave up the ghost and
I could not get replacement parts.  I used to have a locked room filled
with old machines.  Management refused to purchase unless they were forced
to due to either hardware or software issues.

Jon

On Wed, Mar 14, 2012 at 7:13 PM, <[email protected]> wrote:

> Any input it appreciated.
>
> I swear by using manufacturer drivers for hardware instead of those
> supplied by Windows Update.
>
> Has anybody had a reason to use Windows Update drivers instead of
> manufacturer supplied drivers with the exception of cases where the
> manufacturer specifically says to use the drivers supplied from Windows
> Update?
>
> Sent from my iPhone
>
> On Mar 14, 2012, at 5:57 PM, David Lum <[email protected]> wrote:
>
> I did have to install Konica software which automatically queries your LAN
> and installs appropriate drivers and then I ran “add printer”, entered a
> Konica printer IP and when the server queried it fired up the Konica
> utility which found all the Konica printers and installed them. I also had
> to to create a new SMTP connector for Konica scan-to-e-mail, and then I had
> to modify the existing SMTP (which had been migrated over) that was
> flattening the new one.****
>
> ** **
>
> Dave****
>
> ** **
>
> *From:* Don Kuhlman [mailto:[email protected]]
> *Sent:* Wednesday, March 14, 2012 7:58 AM
> *To:* NT System Admin Issues
> *Subject:* Re: My SBS swing brag****
>
> ** **
>
> Thanks Dave.  Sounds like the printer migration process is pretty straight
> forward with the main requirements being you need a 32 bit client with all
> the target print drivers, and you have to initially manually add the new
> printers to the 64 bit server.****
>
> ** **
>
> Did the new server require 64 bit or 32 bit driver downloads from external
> sources, or other work?****
>
> ** **
>
> Regards,****
>
> ** **
>
> Don K****
>
> ** **
> ------------------------------
>
> *From:* David Lum <[email protected]>
> *To:* NT System Admin Issues <[email protected]>
> *Sent:* Wednesday, March 14, 2012 8:48 AM
> *Subject:* RE: My SBS swing brag****
>
> ** **
>
> Printers are a manual re-add at the server. Client PC’s are a mix of
> 64-bit Win7 and 32-bit XP but after loading the 32-bit drivers on the
> server (from an XP box) the client PC’s didn’t notice the change and I
> didn’t have to touch ‘em. In a very real sense I didn’t have to touch any
> of the PC’s for this swing upgrade.****
>
>  ****
>
> For overall time and 17 users it **might** have been same/same to create
> a new SBS domain from scratch and disjoin/rejoin the PC’s and create “new”
> user accounts and PST all that crap over (I think I have 30-ish hours into
> the swing soup to nuts, including testing), but that would require me
> knowing all the users’ password and logging in as them and RDP-ing to each
> one.****
>
>  ****
>
> Dave****
>
>  ****
>
> *From:* Don Kuhlman [mailto:[email protected]]
> *Sent:* Tuesday, March 13, 2012 2:30 PM
> *To:* NT System Admin Issues
> *Subject:* Re: My SBS swing brag****
>
>  ****
>
> I gotta ask how if the kit included the print migrations procedures from
> 32 bit to 64 bit - you mentioned that went well, so it begs the question :)
> ****
>
>  ****
>
>  ****
> ------------------------------
>
> *From:* Jonathan Link <[email protected]>
> *To:* NT System Admin Issues <[email protected]>
> *Sent:* Tuesday, March 13, 2012 11:44 AM
> *Subject:* Re: My SBS swing brag****
>
>  ****
>
> Not by much.  I used the SBSMigration swing kit to swing to new hardware a
> while back.  I could've done everything in it manually, certainly.  The
> ~$200 for me was well worth it to put all the pieces of information
> together in one spot.  Saying I used this tool for this reason and then how
> you used it is an entirely reasonable topic to blog about.****
>
>  ****
>
> Yes, all the information out there is freely available.  Is it worth
> spending some money to 1) put it all in one place and 2) highlight some
> common points of trouble[1].****
>
>  ****
>
> [1] I had one of those common points of trouble.  It was nice having
> something in hand instead of googling for it hoping someone else had tread
> the path I was walking...****
>
> On Tue, Mar 13, 2012 at 11:42 AM, David Lum <[email protected]> wrote:***
> *
>
> Sure, but it would look a lot like this:****
>
>  ****
>
> Step 1: Buy a kit from SBSMigration.com****
>
> Step 2: The end****
>
>  ****
>
> That _*might*_ be oversimplifying it J****
>
>  ****
>
> Dave****
>
>  ****
>
> *From:* James Rankin [mailto:[email protected]]
> *Sent:* Tuesday, March 13, 2012 7:30 AM****
>
>
> *To:* NT System Admin Issues****
>
> *Subject:* Re: My SBS swing brag****
>
>  ****
>
> In keeping with the current fashion, you should definitely write a blog
> post on your migration****
>
> On 13 March 2012 14:01, David Lum <[email protected]> wrote:****
>
> So, I successfully swung a small (17 employee law fim) client from SBS2003
> to SBS2011 this weekend, went off with exactly one caveat: iPhone users had
> to delete, reboot, then recreate the Exchange accounts on their phones.
> That was it! Needless to say the client is very happy, and most employee’s
> hardly noticed a thing (other than I was onsite all day yesterday, which
> had never happened before ;-).****
>
>  ****
>
> Convert everyone from Exchange 2003->Exchange 2010: Check
> Convert domain controller to SBS2011 (aka2008R2): Check
> Convert LexisNexis application from SQL2005 – SQL2008R2: Check
> <Upgrade from PracticeAdvantage 10 to PA 11: Check!>****
>
> Move printers from 2003 32-bit server to SBS2011 64-bit server: check
> (this went easier than expected)
> Recreate shared folders and perms: check
> Copy all data to new server (did you know there’s a utility for 2008 R2 to
> restore from .BKF files?): Check
> Reconfig home directories from share-per-user to single share/ABE/SBS2011
> default locations: Check****
>
>  ****
>
> Worthy to note that SBS2011 really encourages you (er, me) to not treat
> SBS like just a small domain with Exchange. Pretty slick OS too.****
>
>  ****
>
> I could NOT have done it without the SBSSwing kit, there are so many
> little things that Jeff’s team has figured out. I don’t have any current
> certs, but I passed that test! W00t!****
>
> *David Lum* ****
>
> Systems Engineer // NWEATM
> Office 503.548.5229 //* *Cell (voice/text) 503.267.9764****
>
>  ****
>
>  ****
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~****
>
>
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin****
>
>
>
> ****
>
>
> --
> "On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into
> the machine wrong figures, will the right answers come out?' I am not able
> rightly to apprehend the kind of confusion of ideas that could provoke such
> a question."
>
> ****** IMPORTANT INFORMATION/DISCLAIMER *****
>
> This document should be read only by those persons to whom it is
> addressed. If you have received this message it was obviously addressed to
> you and therefore you can read it, even it we didn't mean to send it to
> you. However, if the contents of this email make no sense whatsoever then
> you probably were not the intended recipient, or, alternatively, you are a
> mindless cretin; either way, you should immediately kill yourself and
> destroy your computer (not necessarily in that order). Once you have taken
> this action, please contact us.. no, sorry, you can't use your computer,
> because you just destroyed it, and possibly also committed suicide
> afterwards, but I am starting to digress...... *****
>
> *The originator of this email is not liable for the transmission of the
> information contained in this communication. Or are they? Either way it's a
> pretty dull legal query and frankly one I'm not going to dwell on. But
> should you have nothing better to do, please feel free to ruminate on it,
> and please pass on any concrete conclusions should you find them. However,
> if you pass them on via email, be sure to include a disclaimer regarding
> liability for transmission.*****
>
> *In the event that the originator did not send this email to you, then
> please return it to us and attach a scanned-in picture of your mother's
> brother's wife wearing nothing but a kangaroo suit, and we will immediately
> refund you exactly half of what you paid for the can of Whiskas you bought
> when you went to Pets At Home yesterday. *****
>
> *We take no responsibility for non-receipt of this email because we are
> running Exchange 5.5 and everyone knows how glitchy that can be. In the
> event that you do get this message then please note that we take no
> responsibility for that either. Nor will we accept any liability, tacit or
> implied, for any damage you may or may not incur as a result of receiving,
> or not, as the case may be, from time to time, notwithstanding all
> liabilities implied or otherwise, ummm, hell, where was I...umm, no matter
> what happens, it is NOT, and NEVER WILL BE, OUR FAULT! *****
>
> *The comments and opinions expressed herein are my own and NOT those of
> my employer, who, if he knew I was sending emails and surfing the seamier
> side of the Internet, would cut off my manhood and feed it to me for
> afternoon tea. *****
>
>  ****
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~****
>
>
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin****
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin****
>
>  ****
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin****
>
>  ****
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin****
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin****
>
> ** **
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin****
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to