if you use teamviewer i'm happy to connect and see what the problem is, seeing as you have such good taste in guides and all :-)
On Thu, Feb 5, 2015 at 8:38 PM, David McSpadden <[email protected]> wrote: > Build and capture. > > Part 7 > > If printed page 32 otherwise select build and capture and wait. > > > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Marable, Mike > *Sent:* Thursday, February 05, 2015 2:35 PM > > *To:* '[email protected]' > *Subject:* [mssms] RE: vmware build > > > > Okay, start simple. Try disabling the driver install step in the task > sequence. Windows 7 should have the drivers it needs without using any 3 > rd party drivers. > > > > What kind of task sequence are you using? Is it an MDT integrated > sequence or a basic “build and capture”? > > > > Which step are you on with the docs from Windows-Noob? > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *David McSpadden > *Sent:* Thursday, February 5, 2015 1:30 PM > *To:* '[email protected]' > *Subject:* [mssms] RE: vmware build > > > > I can build one in vcenter. > > I want to build one in SCCM 2012 r2 cu3 like he is showing in the doc. > > But I am screwing up the build or something. > > 0x80004005 > > Generic build error. > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Marable, Mike > *Sent:* Thursday, February 05, 2015 1:22 PM > *To:* '[email protected]' > *Subject:* [mssms] RE: vmware build > > > > What version of VMWare are you using? > > > > If you have the option of Windows 7 for the guest OS then you should be > good. The key hardware is the NIC, which if you select Win7 as the guest > OS VMWare will use a standard Intel NIC (a default driver included with > Windows). > > > > You can get by without the VMWare Tools. It will work. You won’t have > the integration services but it’ll work. There’s no harm in adding an > install of the tools. But it all depends on what you’re looking to > accomplish. If you’re using VMs for basic build testing then (in my > opinion) don’t worry about integrating the VMWare Tools. On the other > hand, if you’re building production VMs perhaps in ESX then I would add the > tools and install it as an application. > > > > What drivers are you currently trying to install when it blows up? > > > > > > > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *David McSpadden > *Sent:* Thursday, February 5, 2015 12:13 PM > *To:* [email protected] > *Subject:* [mssms] vmware build > > > > Trying to go through Windows-noob instructions and I have a vmware instead > of hyper-v workstation (For a windows732bit) build. Do I need to dump the > vmware tools to a source for the device drivers? > > It looks like in the smsts log that I am blowing up when it is trying to > install device drivers. > > > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > > > Please consider the environment before printing this email. > > > > ********************************************************** > Electronic Mail is not secure, may not be read every day, and should not > be used for urgent or sensitive issues > > > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > > > Please consider the environment before printing this email. > > > > ********************************************************** > Electronic Mail is not secure, may not be read every day, and should not > be used for urgent or sensitive issues > > > > This e-mail and any files transmitted with it are property of Indiana > Members Credit Union, are confidential, and are intended solely for the use > of the individual or entity to whom this e-mail is addressed. If you are > not one of the named recipient(s) or otherwise have reason to believe that > you have received this message in error, please notify the sender and > delete this message immediately from your computer. Any other use, > retention, dissemination, forwarding, printing, or copying of this email is > strictly prohibited. > > Please consider the environment before printing this email. > >
