hi guys i don't want to change subject here but since we are talking about HP. Where can i download software package from hp (as Dell cab drivers for osd http://en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx#Optiplex)
thanks Arif Usman On Sat, Oct 26, 2013 at 9:46 AM, Jimmy Martin <[email protected]>wrote: > This is a great resource as well…**** > > http://catalog.update.microsoft.com/v7/site/Home.aspx**** > > ** ** > > just enter the pnp id in the search blank**** > > ** ** > > Jimmy Martin | HS IS-INFRASTRUCTURE | BMHCC - > CORPORATE > > Phone: (901) 227-8209 | [email protected] > > The opioions expressed above are not necessarily > those of Baptist. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jason Wallace > *Sent:* Thursday, October 24, 2013 1:05 AM > > *To:* [email protected] > *Subject:* Re: [mssms] Deploy OS WIM from USB**** > > ** ** > > James**** > > ** ** > > There is some great advice on here about drivers and their effect on the > build process.**** > > ** ** > > One thing you might want to try is visiting a few examples of each of > these errant systems and looking at the PNP IDs to see if they match the > drivers that you are sending down.**** > > ** ** > > Sometimes you will find that the use of DoubleDriver or, better, > DriverGrabber is a good idea.**** > > ** ** > > While the *latest* driver is a good answer most of the time of course like > all good rules .....**** > > ** ** > > Be aware of variations in the hardware shipped - a device on system A may > have the same SKU as on system B but be totally different.**** > > ** ** > > On my present project we are working on a Lenovo Carbon X1 deployment. We > are finding that the little USB dongles which we use are manufactured by > ASIX who must have shipped a bunch of these under their Vendor ID before > using Lenovo - means we have to carry both drivers in BOOT and deployment. > **** > > ** ** > > We are also using their port replicators and what I believe is happening > is that the driver does some flashing on the PR. This means that we have to > have a driver version match between BOOT and driver package for deployment > - the old version and then a subsequent fix up**** > > ** ** > > Back to deploying Windows over PGP systems.**** > > > On 24 Oct 2013, at 05:19, "Avery, James" < > [email protected]> wrote:**** > > I download the large single package from HP’s website and do the import > from that.**** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jimmy Martin > *Sent:* Wednesday, October 23, 2013 9:29 PM > *To:* [email protected] > *Subject:* RE: [mssms] Deploy OS WIM from USB**** > > **** > > when u do ur driver packages, do u download the model and os specific full > driver packages from hp? U might try downloading the latest Nic driver > from hp for that model into ur model specific package > > Sent from my Windows Phone**** > ------------------------------ > > *From: *Avery, James > *Sent: *10/23/2013 8:49 PM > *To: *[email protected] > *Subject: *RE: [mssms] Deploy OS WIM from USB**** > > That’s checked and it’s working correctly. I’ve also remove the WMIC query > for my testing.**** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jimmy Martin > *Sent:* Wednesday, October 23, 2013 8:17 PM > *To:* [email protected] > *Subject:* RE: [mssms] Deploy OS WIM from USB**** > > **** > > One other thing to check… on the computer not getting the driver… open > cmd prompt, type:**** > > Wmic computersystem get model**** > > **** > > Make sure the value is EXACTLY what you are expecting…**** > > **** > > I have seen hp do something like this inside a model series…**** > > **** > > **** > > HP Compaq 8200 Elite SFF PC**** > > HP Compaq Elite 8200 SFF**** > > * > Jimmy Martin | ENGINEER-SYSTEMS II | BMHCC - CORPORATE | > (901) 227-8209 | [email protected] ***** > > *The opinions expressed above are not necessarily those of > Baptist.<[email protected]> > ***** > > **** > > **** > > Jimmy Martin | HS IS-INFRASTRUCTURE | BMHCC - CORPORATE **** > > Phone: (901) 227-8209 | [email protected] **** > > *The opinions expressed above are not necessarily those of > Baptist* <[email protected]> **** > > **** > > **** > > **** > > *From:* [email protected] > [mailto:[email protected]] *On Behalf Of *Avery, James > *Sent:* Wednesday, October 23, 2013 8:10 PM > *To:* [email protected] > *Subject:* RE: [mssms] Deploy OS WIM from USB**** > > **** > > Jason, you forgot to add the URL.**** > > **** > > I’m still having NIC issues and I’ve been playing with it trying to figure > out why the NIC driver isn’t showing up correctly.**** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Jason Sandys > *Sent:* Wednesday, October 23, 2013 2:03 PM > *To:* [email protected] > *Subject:* RE: [mssms] Deploy OS WIM from USB**** > > **** > > That won’t change anything. Apply Network Settings simply populates the > unattend.xml file and the domain join doesn’t happen until Windows Setup > happens during the Setup Windows and ConfigMgr task (using info in the > unattend.xml that the Apply Network Settings task populated).**** > > **** > > You need to simply track down the **proper** NIC driver and ensure it is > part of the package being deployed to the target system. Here’s a good post > on tracking down why a driver may or may not have been chosen by Windows.* > *** > > **** > > J**** > > **** > > **** > > *From:* [email protected] > [mailto:[email protected]] *On Behalf Of *Jimmy Martin > *Sent:* Tuesday, October 22, 2013 3:38 PM > *To:* [email protected] > *Subject:* RE: [mssms] Deploy OS WIM from USB**** > > **** > > Move your drivers above the apply network settings**** > > **** > > * > Jimmy Martin | ENGINEER-SYSTEMS II | BMHCC - CORPORATE | > (901) 227-8209 | [email protected] ***** > > *The opinions expressed above are not necessarily those of > Baptist.<[email protected]> > ***** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Avery, James > *Sent:* Tuesday, October 22, 2013 3:37 PM > *To:* [email protected] > *Subject:* RE: [mssms] Deploy OS WIM from USB**** > > **** > > I figured it out. It’s a NIC driver issue.**** > > **** > > For some reason the NIC isn’t being seen after windows is installed.**** > > **** > > Right now, I have the General drivers installing after the “Apply Network > Settings”. I’m going to test and see if it works when I move the “Apply > Network Settings” below the general drivers so the nic drivers will be > installed before joining to the domain.**** > > **** > > **** > > <image001.png>**** > > **** > > **** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Niall Brady > *Sent:* Tuesday, October 22, 2013 2:31 AM > *To:* [email protected] > *Subject:* Re: [mssms] Deploy OS WIM from USB**** > > **** > > joining domain just fine here wth Standalone media (Configuration Manager > 2012 SP1 CU3).**** > > **** > > On Tue, Oct 22, 2013 at 12:08 AM, Jimmy Martin <[email protected]> > wrote:**** > > Have done it from both > > Sent from my Windows Phone**** > ------------------------------ > > *From: *Avery, James > *Sent: *10/21/2013 4:30 PM**** > > > *To: *[email protected] > *Subject: *RE: [mssms] Deploy OS WIM from USB**** > > **** > > *Jimmy, did you test that from SCCM 2007 or 2012?***** > > * ***** > > **** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Jimmy Martin > *Sent:* Monday, October 21, 2013 4:25 PM > *To:* [email protected] > *Subject:* RE: [mssms] Deploy OS WIM from USB**** > > **** > > I use it and domain join is fine too**** > > **** > > * > Jimmy Martin | ENGINEER-SYSTEMS II | BMHCC - CORPORATE | > (901) 227-8209 | [email protected] ***** > > *The opinions expressed above are not necessarily those of > Baptist.<[email protected]> > ***** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Avery, James > *Sent:* Monday, October 21, 2013 3:56 PM > *To:* [email protected] > *Subject:* RE: [mssms] Deploy OS WIM from USB**** > > **** > > Stand Alone Media will not join the domain in SCCM 2012. We just tested > this and it works perfect, but does not join the domain.**** > > **** > > James**** > > **** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Daniel Ratliff > *Sent:* Monday, October 21, 2013 3:46 PM > *To:* '[email protected]'; '[email protected]' > *Subject:* RE: [mssms] Deploy OS WIM from USB**** > > **** > > We use standalone media and join the domain just fine. Have you tried > leaving the step in the TS? > > -Daniel Ratliff > > -----Original Message----- > *From: *Avery, James [[email protected]] > *Sent: *Monday, October 21, 2013 04:43 PM Eastern Standard Time > *To: *[email protected] > *Subject: *[mssms] Deploy OS WIM from USB**** > > Guys I wanted your opinion.**** > > **** > > Issue:**** > > I have several sites with super low bandwidth. They do not have a DP, > however, they do have connectivity to the network. I need to deploy NEW > OS’s with applications.**** > > **** > > Options:**** > > 1. Utilize the Stand Alone Media, This works great, but I have to > add the system back to the domain.**** > > 2. Try to come up with a way to utilize PreStaged Media as shown in > Chris Nackers BLOG. However, this still has to come from a DP. > > http://sccm2o12.blogspot.com/2010/12/configuration-manager-r3-prestaged.html > **** > > **** > > Any thoughts?**** > > **** > > James**** > > **** > ------------------------------ > > This e-mail is intended solely for the person or entity to which it is > addressed and may contain confidential and/or privileged information. Any > review, dissemination, copying, printing or other use of this e-mail by > persons or entities other than the addressee is prohibited. If you have > received this e-mail in error, please contact the sender immediately and > delete the material from any computer. To unsubscribe send an email to: > [email protected] Hitachi Consulting Corporation, 14643 > Dallas Parkway, Suite 800, Dallas, Texas 75254 (HCAD0411) **** > ------------------------------ > > > > 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.* > *** > > **** > > **** > > This message and any files transmitted with it may contain legally > privileged, confidential, or proprietary information. If you are not the > intended recipient of this message, you are not permitted to use, copy, or > forward it, in whole or in part without the express consent of the sender. > Please notify the sender of the error by reply email, disregard the > foregoing messages, and delete it immediately.**** > > **** > > P *Please consider the environment before printing this email...***** > > **** > > **** > > **** > > This message and any files transmitted with it may contain legally > privileged, confidential, or proprietary information. If you are not the > intended recipient of this message, you are not permitted to use, copy, or > forward it, in whole or in part without the express consent of the sender. > Please notify the sender of the error by reply email, disregard the > foregoing messages, and delete it immediately.**** > > **** > > P *Please consider the environment before printing this email...***** > > **** > > **** > > **** > > **** > > **** > > This message and any files transmitted with it may contain legally > privileged, confidential, or proprietary information. If you are not the > intended recipient of this message, you are not permitted to use, copy, or > forward it, in whole or in part without the express consent of the sender. > Please notify the sender of the error by reply email, disregard the > foregoing messages, and delete it immediately.**** > > **** > > P *Please consider the environment before printing this email...***** > > **** > > **** > > **** > > **** > > This message and any files transmitted with it may contain legally > privileged, confidential, or proprietary information. If you are not the > intended recipient of this message, you are not permitted to use, copy, or > forward it, in whole or in part without the express consent of the sender. > Please notify the sender of the error by reply email, disregard the > foregoing messages, and delete it immediately.**** > > **** > > P *Please consider the environment before printing this email...***** > > **** > > **** > > **** > > This message and any files transmitted with it may contain legally > privileged, confidential, or proprietary information. If you are not the > intended recipient of this message, you are not permitted to use, copy, or > forward it, in whole or in part without the express consent of the sender. > Please notify the sender of the error by reply email, disregard the > foregoing messages, and delete it immediately.**** > > **** > > P *Please consider the environment before printing this email...***** > > **** > > **** > > ** ** > > ** ** > > This message and any files transmitted with it may contain legally > privileged, confidential, or proprietary information. If you are not the > intended recipient of this message, you are not permitted to use, copy, or > forward it, in whole or in part without the express consent of the sender. > Please notify the sender of the error by reply email, disregard the > foregoing messages, and delete it immediately. > > > P *Please consider the environment before printing this email...* > > >
