Jump to content


Greg Ramsey (MVP)

Established Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by Greg Ramsey (MVP)

  1. This is all you should have in that sysprep.inf file, and apply it using the "apply operating system" phase - let ConfigMgr handle the rest of the config in that .inf. [unattended] UpdateInstalledDrivers=Yes
  2. You do not need to run that rundll32 command - there must be some other problem. Did you add the information I mentioned for sysprep.inf?
  3. Is this your first attempt using OSD, or are you deploying others successfuly? For the record, Deploying XP is harder than vista and win7 . Looking at your first image in this post, I see you have GUIDS, as well as R numbers. That driver package source directory should not look like that. If you're in a test environment, I recommend you (from the admin console, delete all drivers, and all driver packages, and start over, then walk through the steps I referenced from delltechcenter - if we can get back to that basic, we should be able to help you better. Use the .CAB download for XP on the 6410 on delltechcenter, and follow that process to import them - don't add anything to the driver package source. oh yea, side note - I would still include this entry in sysprep.inf: UpdateInstalledDrivers=Yes . . . . for me, better safe than sorry.
  4. What model system did you use to capture the .wim file? If that original capture contained any of the same drivers that are on the target hardware, you need to have an entry in sysprep. UpdateInstalledDrivers=Yes This goes into the Unattend section of sysprep.inf. See here for more information. http://support.microsoft.com/kb/302577 You can dynamically apply this during your task sequence, in the "Apply Operating System" step.
  5. btw - for all things Dell and ConfigMgr, check out http://www.dell.com/configmgr
  6. Hi, Have you seen our docs on www.delltechcenter.com?? Specifically, take a look here: http://www.delltechcenter.com/page/Dell+Business+Client+Operating+System+Deployment Hit the "Download the CAB Files" link to download drivers for the E6410. Also from that page, you'll see that we have an XP WalkThrough as well as a "Vista WalkThrough" (this Vista Example is very similar to win7). Dealing with Mass storage on XP is a bit of a pain, but if you follow the walk through, you should be able to handle it. hope that helps, Greg
  7. can you post some log files? mpsetup mpfdm, mp* ??
  8. there is only a 32 bit client - runs fine on x64 - just do a client push, or install as normal - there are a couple differences. 1 - setup installation directory will be %windir%\ccmsetup instead of the normal %windir%\system32\ccmsetup 2 - installation directory will be in %windir%\syswow64\ccm Greg
  9. I would guess a driver issue. What model(s) have you tried to deploy to? are any succeeding? have you tried to VM??
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.