Windows 7 Sysprepped Image - Injecting Drivers issue

Hi
I have created a Windows 7 Image, sysprepped it and capture an image using MDT. I am using the "Total Control" driver management method and during the imaging phase I can see that it injects the drivers into the image but for some strange reason,
and I can't see to figure out why, it's not installing the drivers during the windows setup phase.
Please can someone help!
Thanks

How do you know for sure the drivers are not getting installed, and how do you know for sure you have the correct drivers? Please illusrate. You should be able to boot into the new OS, open DevMgmt.msc, and update each missing device with drivers MDT copyied
to the c:\Drivers folder, if these drivers don't install, then you might now have the correct drivers.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Similar Messages

Windows 7 X301 Music Device Drivers Issue

I am having issues with 3 Devices. they are all Akai items (LPD8, LPK25, MPK25).
The items work perfectly on 6 other win7 machines - install with no issues. The X301 is the only problem child. These devices use generic drivers - there are no specific drivers for them. on the machines that work the following drivers are used:
dmk.sys
ksthunk.sys
portcls.sys
usbaudio.sys
sysfxui.dll
wmalfxgfxdsp.dll
somhow this won;t work on the OS on the lenovo. 'driving' me nuts.
ideas?

one more detail on the dirvers themselves.
This items are all using the generic 'USB Audio Device' Driver - so please don't say - go to the manufacturer's site :-)
this driver seems completely unavailable on this one machine - even though all the supporting files are there. In addtion, it can't seem to get it from Windows update.
Completely Bizzarre...

Not able to install sysprepped Windows 8.1 image, an OfflineServicing error appears.

Hello
I have Windows 8.1 Enterprise image failing at the end of the PE phase from a
WDS Server. I´ve searching through every related post but nothing solves the issue. My scenario is similar to this one (http://social.technet.microsoft.com/Forums/en-US/7ce4c49d-e8a4-460a-ae17-240daaf5f50e/deploying-a-win7-image-via-wds-fails-with-offlineservicing-error?forum=w7itproinstall),
but with Windows 8.1 Enterprise instead.
Basically, I have sysprepped Windows 8.1 and capture the image successfully without any problem. Then, I´ve uploaded the image to my WDS without any unattend xml file, but when trying to install it I get the following error message after completing the "Expanding
Windows Files" phase:
“Windows could not apply unattend settings during pass [offlineServicing]”
I´ve used the official image release, plus the only one partition disk is formatted before the installation. Every configuration seems to be set correctly. I wonder if there is any particular issue related to Windows 8.1.
I´ve already done this procedure with many other OS images and I´ve never got this error message.
Furthermore, I also tried to perform the installation with an empty unattend answer file attached to the deployed image, but the error still appears.
I wonder if the Win8.1 image needs a proper configuration of the unattend answer file, specially on the
Pass 2 of OfflineServicing. Unfortunately I don´t know how to configure it. I would like to keep the credentials and partition configuration be set manually.
Thank you for any help you can give me.

Hello, thanks for the replay but I didn't found any relevant log file on the client machine.
Unattend mode is unchecked, and I haven't used DISM at all when creating the image. I haven't also opened nor updated any metroApp (although if this were the case, it would raise an issue on sysprep phase).
X:\Windows\panther directory does not exists; (C: volume is not available at installation phase)
X:\Windows\diagerr.xml doesn't have any relevant information (it defines some AtrributeType tags with a number in a xml format but it has no content on any tag.)
X:\windows\tracing\ folder is empty;
X:\windows\Logs & \Logs\CBS folders are empty;
I've checked all the volume and I couldn't find any relevant log which shows an error on the instalation.
In addition, I tried to look into WDS server, but the Enable Log property that the article refers for Windows Server 2012 (WDS is installed in a Windows Server 2012), is not shown at the
EventViewer - Deployment-Services-Diagnostics section. Plus, I search the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Tracing\WDSMGMT
entry in order to enable it, but it does not exist.
WDS worked and is working without any issue regardless this Windows 8.1 image. I don't think it has a somthing to do with its configuration.
Looking forward to hearing from you.

MDT 2010 - USB 3.0 issue after OS Install and Inject Drivers steps

Hello,
I'm using MDT 2010 and I'm booting and image PCs from a USB drive. On some newer systems (eg: Latitude El530) I have issues when I use the USB 3 ports (if media is connected to USB 2 port, everuthing is fine). The systes recognizes the USB stick and I can
start the Task Sequence just fine. I pass the Install OS step and Inject Drivers step, but after the first reboot, I get the prompt to insert the media to continue the deployment. This happens only if the stick is connected to the USB 3.0 ports. If I
check Device Manager, I see the USB device withouth driver. The drivers are already on the USB stick...I puled them from FileRepository from an updated system with all the drivers. Is anyone else having similar issues? I see other people have USB 3 issues,
but mostlly to start the deployment from it, or at partitioning...I don't have that issue. My issue starts after the OS is installed.
Any sugestion is appreciated...Thank you...
aburica

You should be able to do this. nVidia Optimus video drivers have the same issue. How we solved this
We create selection profiles for each make and model
We inject every single driver in profile for each make and model
The Optimus driver then gets installed because it is local to the machine already.
Why it didn't work before is the child device never gets detected during the PNP enum that happens when you have 'Install only matching drivers from the selection profile' so never ends up in the local driver store.
P.S. We ONLY have the drivers that install imported into each make model folder.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”
How to ask a question that is fixable.

Customize Windows 8 start screen for sysprepped image deployment.

I am attempting to customize the start screen of a windows 8 Pro image for deployment. I have been searching and reading different threads well as technet articles but I have not found anything that works or is not completely documented.
I have tried the three methods outlined in the technet about customizing the start screen with no luck. http://technet.microsoft.com/en-us/library/jj134269.aspx
The CopyProfile option does not work. Even after enabling the administrator account in audit mode the start screen tiles are not saved after sysprepping.
Copying the AppFolderLayout.bin file or appsFolder.itemdata-ms to the default user profile does not work. The file is overwritten during the oobe process. I have added these files after sysprepping the image. They are overwritten in the default user
profile during oobe before the new user is created.
Using the StartTiles section of unattend would be the best option that will require fewer manual steps but only seems to be able to add new tiles. I cannot remove tiles or change order with StartTiles.
My unattend.xml file is here: https://dl.dropboxusercontent.com/u/10327232/unattend.xml
If anyone has a method that works for them please let me know. Especially if this can be automated using unattend.xml

Copying the AppFolderLayout.bin file or appsFolder.itemdata-ms to the default user profile does not work.
I think Niall's procedure sounds a bit more complicated than that. ; )
http://www.windows-noob.com/forums/index.php?/topic/8101-using-system-center-2012-configuration-manager-part-13-deploying-windows-8-x64-with-custom-start-screen/
Also, regarding removal specifically, did you see Antony Mann's reference to the PowerShell DISM module?
http://social.technet.microsoft.com/Forums/en-US/w8itproinstall/thread/cbe566f9-fe40-4344-9e7d-1dbf72178429#a59888a6-5196-47b9-91c0-9ddba6a26384
Other good references available then via
(Bing search for
RemoveAppxProvisionedPackage
HTH
Robert Aldwinckle

MDT - Injecting Drivers

Morning,
I've managed to figure out how to inject drivers using the %make and %model% variables. After booting into the image the drivers are not installing automatically; I have to manually install them myself by going into device manager and updating.
Is there a way to automate this at all?
Many Thanks

All i've done so far is installed windows 7 from the disk and capture an image without syprepping it using MDT. I was then hoping what I could do is to use this image to install a basic copy of Windows 7 and inject the necessary drivers. I'm guessing doing
it this way does not go through the Windows 7 setup stage until I sysprep it?
Hope that makes sense
Regards

Weird Drivers Issue

Having issues with our SCCM 2012 setup with injecting drivers into an OSD.
I have created a x86 Windows 7 image for our organization and downloaded the drivers for the Lenovo L412 laptop that I'm trying to deploy it out to and added them into SCCM. I've then deployed the image and gotten this error in the logs:
<![LOG[Failed to resolve content for driver "Intel(R) 5 Series/3400 Series Chipset Family Virtualization Engine Controller - 3B53". Code 0x800700b7]LOG]!><time="10:11:16.096-660" date="11-27-2012" component="OSDDriverClient" context="" type="3"
thread="884" file="driverinstaller.cpp:615">
<![LOG[Failed to find a suitable device driver for device 'PCI to PCI Bridge'.]LOG]!><time="10:11:16.096-660" date="11-27-2012" component="OSDDriverClient" context="" type="2" thread="884" file="driverinstaller.cpp:799">
<![LOG[Failed to resolve content for driver "Intel(R) QuickPath Architecture Generic Non-Core Registers - 2C50". Code 0x800700b7]LOG]!><time="10:11:16.361-660" date="11-27-2012" component="OSDDriverClient" context="" type="3" thread="884" file="driverinstaller.cpp:615">
Now the weird issue is that I then tested out these drivers and deployed them to a clean x86 Windows 7 image using SCCM and all the drivers went through fine.
I would also like to point out that the image is not corrupt as I've deployed the same image to our desktops and it installs its drivers for them fine.
I've tried using both "Apply Device Drivers" and "Apply Device Package" sequences but neither worked.
So if my drivers and image isn't the problem what is?

getting closer..
In part 2 of your logs, I see these lines:
Executing command line: "X:\WINDOWS\Pkgmgr\dism.exe" /image:"C:" /windir:"WINDOWS" /apply-unattend:"C:\_SMSTaskSequence\PkgMgrTemp\drivers.xml" /logpath:"C:\_SMSTaskSequence\PkgMgrTemp\dism.log"
Process completed with exit code 2147500037
uExitCode == 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,549)
Dism failed with return code -2147467259
AddPnPDriverToStore( pszSource, sTargetSystemDrive, sTargetSystemRoot, wProcessorArchitecture), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osddriverclient\sysprepdriverinstaller.cpp,659)
Failed to add driver to driver store. Code 0x80004005
Several random comments/questions...
1- confirm your target OS is in c:\windows - confirm this while you're in winpe - sometimes, while you're applying OS, the target drive letter will be different than c: while in winpe
2- Are you using 'auto apply drivers' or 'apply driver package'?
3-Ensure 'continue on error' is disabled for this step in your task sequence - it would be good to fail at this point. From the log, you can see that you want to take a look at C:\_SMSTaskSequence\PkgMgrTemp\dism.log as soon as the failure occurs. There's
a good chance that dism.log file will have the info we need - note that for every driver it attempts to install, this .log file will be written/overwritten, so try to grab it when failure occurs.
4-Are you installing win7 x86?
if none of the things above get you closer to resolution, I suggest trying again with the Original install.wim file, and grab the logs at the same point (while still in winPE to see what's different.
Greg
Greg Ramsey Microsoft MVP - ConfigMgr Dell, Inc. www.twitter.com/ramseyg

Windows 7 sysprep errors after security updates to be IA compliant

After installing security updates to remain IA compliant I am unable to run sysprep on my Windows 7 VM's and our hardware images.
It is NOT rearm.
Log:
2012-06-20 09:56:25, Error                 SYSPRP SPPNP: Error 0x2 setting SDDL on driver file C:\Windows\system32\igfxsrvc.exe!
2012-06-20 09:56:25, Error                 SYSPRP SPPNP: Error 0x2 setting SDDL on driver file C:\Windows\system32\igfxtray.exe!
2012-06-20 09:56:25, Error                 SYSPRP SPPNP: Error 0x2 setting SDDL on driver file C:\Windows\system32\DRIVERS\Accelern.sys!
2012-06-20 09:56:25, Error                 SYSPRP SPPNP: Error 0x3 setting SDDL on driver file C:\Program Files\STMicroelectronics\AccelerometerP11\stdcfltn\stdcfltn.cab!
2013-06-20 11:51:04, Error                        [sysprep.exe] UnattendFindAnswerFile: Explicitly provided unattend file [C:\windows\system32\sysprep\unattend.xml]
does not exist.
2014-03-27 13:48:30, Error                 SYSPRP WindowsSideShow: Failed to get task folder (0x80070003)
2014-03-27 13:48:30, Error      [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\System32\AuxiliaryDisplayClassInstaller.dll,WindowsSideShow_Sysprep_Generalize', returned error code 31
2014-03-27 13:48:30, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 31
2014-03-27 13:48:30, Error      [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0x8007001f
2014-03-27 13:55:57, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 31
2014-03-27 13:55:57, Error      [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f
2014-03-27 15:16:24, Error      [0x0f0073] SYSPRP RunExternalDlls:Not running DLLs; either the machine is in an invalid state or we couldn't update the recorded state, dwRet = 31
2014-03-27 15:16:24, Error      [0x0f00ae] SYSPRP WinMain:Hit failure while processing sysprep cleanup external providers; hr = 0x8007001f

It is not that. Based on other posts I have found that if I delete this key HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Generalize, value {b3257dc1-2617-6667-6a6f-2fe2739a2b89} sysprep works fine. Does anyone know the risks
of deleting this key?

Help Windows 7 deployment image

Hi,
I have recently created a custom Windows 7 reference image, I have changed the background, installed programs and configured. I then uploaded to my deployment server (Using server 2012, WDS and MDT 2012) and then deployed to a test machine. However
when I came to log into the test machine the desktop background had changed back to the Windows 7 default and although the programs were installed, it appeared that none of them had ever been opened and I had to re-configure them all. Is there anyway where
I can capture an image and deploy exactly as it is when I have fully configured it?
Apologies if this has already been asked

The best practice for standard imaging best practices is to make all OS tweaks and enhancements from the local Administrator account. Then once you are ready to sysprep the image and prepare for capture, you will need to utilize the CopyProfile=TRUE option
in your Unatten.xml answer file.
Below is a sample of the Unattend.xml answer file with the CopyProfile feature enabled which allows the profile settings captured to be seen across all other profiles that log in for the first time, post-deployment:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<CopyProfile>true</CopyProfile>
</component>
</settings>
<cpi:offlineImage cpi:source="wim:h:/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
Please remember to click “Mark as Answer” on the post that helps address your issue. This can be beneficial to other community members reading the thread.

Setting up a sysprepped image with user account customisations

I'm trying to create a sysprepped image of a Windows installation for cloning (basically, as a VM template I can clone to create throwaway test environments quickly). I'm using a new build of Windows 8.1, going into audit mode and configuring my environment,
then using sysprep to generalise the image for cloning (sysprep /generalize /oobe /shutdown /unattend:C:\MyUnattendFile.xml).
I have customised the default account by setting things up the way I want in audit mode (under the administrator account that audit mode defaults to). My unattend.xml file has CopyProfile set to true (in the specialize phase, the only one I can set it in
IIRC). I also have my local account configured for creation in the OOBE phase in the unattend.xml file.
When I boot a copy of the sysprepped image, it starts up fine, exactly as I'd expect. But when it gets to the OOBE phase, it goes into the "Setting up a few things" sequence, and when I get the login screen and log in, I see a clean account (default
start page and taskbar, Windows theme is the default, etc). It's as if the default profile I set up hasn't been applied.
I can't tell what I am doing wrong - I saw a note somewhere (via google) that I need to set CopyProfile in the unattend file I boot from, not the one I sysprep with, but that can't be right as in this case I'm not incorporating the image into a setup process
- it's just a VM disk image that I boot normally.
I'm new to all this, and I'm a developer rather than a deployment specialist, so the discussion around images, PE boot disks, custom install disks, etc, is very confusing to me. If I'm doing something wrong, I'd appreciate any explanation someone can give
as to how to achieve what I want relatively simply.
Many thanks in advance,
Paul

I checked the log file, and I see "CopyProfileDirectory from C:\Users\Administrator succeeded. CopyProfile succeeded."
So it looks like the default profile was set up properly.
The desktop background is set correctly on the account, it's just the start page and taskbar, so the blog entry you mentioned seems like it's relevant. The problem is, there's no solution given in there :-(
From what I can see, the issue appears to be that when I initially log onto the user account created in the unattended startup, it runs the "first login" process - "Hi... We're setting things up for you... Installing your apps". So I
guess the key question is how I stop it from running that process, which is messing up the customisations I already made.
From the articles you mention, it seems like there isn't a particularly straightforward way to script the start page/taskbar changes I want. I didn't see anything that suggested I could make the changes once, then back up some data from the registry and/or
some user config files, and then set up a postinstall script to restore them (that probably still wouldn't work, as the "Hi... We're setting things up" process would probably still overwrite them :-(
If it's not possible to do things this way, maybe I'm going to have to go down the route of making a custom install disk. Is there a simple tutorial that assumes no deployment experience, and walks through the process of creating a custom install disk that
includes:
Setting the product key, the default language/locale etc (a fully unattended install)
Selecting to overwrite the whole disk, no dialog about disk partitions, etc
Create a local user account
Install various items of software (7-zip, conemu, virtualbox guest additions, chrome, probably a few others)
Pre-configure the local account with a custom start page, taskbar items, program settings like Internet Explorer home page and search providers and conemu defaults, desktop background
Set up a few other configurations (such as enabling WinRM) that can be done from an automated postinstall Powershell script.
I'm assuming this must be possible somehow, as I can't imagine corporate deployments will use the default start page. It's just how to do this as a home user. I just have a single PC, plus I can set up any VirtualBox VMs I need on it, so approaches
that talk about setting up a lab of machines and deployment servers and shares are probably out of my reach :-(
Thanks,
Paul

MDT Deployment for Windows 8 (Sysprep failes with generalization setting)

Here's my issue...
I'm trying to capture and redeploy Windows 8. In of itself, the capturing and deploying works well. Except for one thing, I can't default the desktop nor can I default the Start Tiles for the start tiles. Upon a visit with Microsoft and
confirmation of a few colleagues, I tried the tutorial listed here, http://msdn.microsoft.com/en-us/library/jj134269, using method 1 the copyprofile.
I have this set up for the unattended on the MDT deployment, but my problem is the issue that I'm running into which is the failure in sysprep running the /generalize tag. Whether I use OOBE or Audit results in the same thing. I have built a
couple of fresh images as well and sysprep keeps failing. I've attached the error log below. So far research has come up with nada, so I can't even getting started on troubleshooting the error.
Here's the error log below.
2012-10-03 14:36:09, Error                 SYSPRP Package Microsoft.VCLibs.110.00_11.0.50727.1_x86__8wekyb3d8bbwe was installed for a user, but not provisioned for all users.
This package will not function properly in the sysprep image.
2012-10-03 14:36:09, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.
2012-10-03 14:36:09, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
2012-10-03 14:36:09, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralize' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2012-10-03 14:36:09, Error                 SYSPRP ActionPlatform::ExecuteAction: Error in executing action; dwRet = 0x3cf2
2012-10-03 14:36:09, Error                 SYSPRP ActionPlatform::ExecuteActionList: Error in execute actions; dwRet = 0x3cf2
2012-10-03 14:36:09, Error                 SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2012-10-03 14:36:09, Error                 SYSPRP RunPlatformActions:Failed while executing SysprepSession actions; dwRet = 0x3cf2
2012-10-03 14:36:09, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2012-10-03 14:36:09, Error      [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize internal providers; hr = 0x80073cf2

Did you ever figure out how to make this work?
I have the same problem with my Win8 64 image -- as soon as I installed the 11 Microsoft Metro app updates from "Store", I can no longer sysprep my image without getting the same "fatal error" (with the exact same log -- except for a different "Package"
listed):
2012-10-10 15:58:47, Error SYSPRP Package Microsoft.WinJS.1.0_1.0.9200.20512_neutral__8wekyb3d8bbwe
was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.
2012-10-10 15:58:47, Error SYSPRP Failed to remove apps for the
current user: 0x80073cf2.
2012-10-10 15:58:47, Error SYSPRP Exit code of RemoveAllApps thread
was 0x3cf2.
2012-10-10 15:58:47, Error [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing
'SysprepGeneralize' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2012-10-10 15:58:47, Error SYSPRP ActionPlatform::ExecuteAction:
Error in executing action; dwRet = 0x3cf2
2012-10-10 15:58:47, Error SYSPRP ActionPlatform::ExecuteActionList:
Error in execute actions; dwRet = 0x3cf2
2012-10-10 15:58:47, Error SYSPRP SysprepSession::Execute: Error
in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2012-10-10 15:58:47, Error SYSPRP RunPlatformActions:Failed while
executing SysprepSession actions; dwRet = 0x3cf2
2012-10-10 15:58:47, Error [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry
sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2012-10-10 15:58:47, Error [0x0f00a8] SYSPRP WinMain:Hit failure while processing sysprep generalize
internal providers; hr = 0x80073cf2
The app updates are *coming from Microsoft* -- so why would I need to provision them (according to that article?)
This seems like a bug...
(The workaround, of course, is to just not update Metro apps on my main image, but that seems rather silly to not be
allowed to do that...)

Since the capture media is no longer working for capturing Windows 8.1 images,

Since Copy Profile doesn't work when you use the sccm capture media to capture a Windows 8.1 image
This is how I been capturing my Windows 8.1 image.
1. Manually sealing the image. Logged in as Administrator, I run, C:\Windows\System32\sysprep\sysprep.exe /generalize /oobe /shutdown /unattend:"C:\Windows\System32\sysprep\sysprep64-81-std.xml" this points to my answer file which contains copy
profile=true. Once Windows is shutdown, I boot directly to PXE, using a TS of the method found in the link below.
2. I then use this method to capture the image directly to a wim file. http://blog.coretech.dk/mip/capture-none-syspreped-image-using-sccm-running-imagex-from-a-ts/
I'd like to hear how others are capturing there Windows 8.1 images, because I am always looking for a better method.

Adding more info:
Deployment Image Servicing and Management (DISM) Command-Line
http://msdn.microsoft.com/en-us/library/jj980032(v=winembedded.81).aspx
Sysprep (Generalize) a Windows installation
http://technet.microsoft.com/en-us/library/hh824938.aspx
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Installing Windows 7 Professional 64 bit drivers för Canon MF8330 Cdn printer/fax/scanner

Hi!
After Windows update in april 2014 I cant any longer use the scanning funktion via network from Canon MF8330 Cdn multifunktion printer/fax/scanner machine! It worked fine Before the april Windows update installation.
I have reinstalled with Canons driver kit 2005b för Windows 7 64 bit. All works fine until the scanner installation ends, then system report that it cannot install the scanner and I have to try installing again. I have done that now several times but it
helps not. I Think it has something to do with that the Canon scanner drivers isn´t 64 bit files, or the problem is that windows update has replaces saome dll file to a never version that not work with Canon drivers.
I have seen that there is a service pack 1 from Canon för Windows 8 and 8,1, can I use that service pack to get a never dll file for scanner or work this only for windows 8 version.
Have someone a solution to this! I have contacted the Canon support already and they say that its a Microsoft problem!
Very thanful for help in this case!
Greetings
Sixten

Hi!
I am installing the drivers from Canons site. It is the newest version 2005b for Windows 7 64 bit to MF8330Cdn Canon multifunction printer/fax/scanner. Installation goes well for the printer and fax but not for scanner drivers. The error message is Could
not install the scanner. In device manager is there then a unknown device under Image devices. In Device Manager I try to update drivers, but it does not help either, error message is access denied. I am logged on the system with administrator account, therfore
it is strange that I get the error message access denied.
I tried earlier to do system restore back to previous time, but it did not work, error was that the system could not do the system restore because of access rights.
is there anything else I could do.
Here is the MF36SCN.inf file for scanner installation from Canon, if it can help You to go further with the problem. Is there something strange in the inf file that does not work in Windows 7 64 bit Windows, something shows that ther is also same 32 bits
parts in the inf file.
Greetings
Sixten
; MF36SCN.INF -- Windows Setup File for the MF8300 Series (Windows XP,Vista(64-bit))
; Copyright CANON INC. 2009 All Rights Reserved
; InfID: {BA7E017E-FA42-4831-A084-AA9E671325EE}
; Last Modified: 11-Jun-2009
[Version]
Signature="$Windows NT$"
Class=Image
ClassGUID={6bdd1fc6-810f-11d0-bec7-08002be2092f}
; The above GUID is the class GUID for all scanners and MUST NOT change
Provider=%Msft%
CatalogFile.NTamd64=MF36SCN.CAT
DriverVer=06/17/2009, 11.3.0.0
[DestinationDirs]
DefaultDestDir=11
CNCDsFiles=10,"twain_32\"%CNCRFN%
CNCMediaFiles=10,media
ColorFiles.NT=11,spool\drivers\Color
[ControlFlags]
;ExcludeFromSelect=*
[Manufacturer]
%Mfg%=Models,NTamd64.5.1,NTamd64.6.0
[Models.NTamd64.5.1]
%LPTENUM\CNC.DeviceDesc%=CNCInstall_XP,USB\VID_04A9&PID_2708&MI_00
%LPTENUM\CNC.DeviceDesc%=CNCInstallNet_XP,CANON_MFNP&%CNCRFN%
[Models.NTamd64.6.0]
%LPTENUM\CNC.DeviceDesc%=CNCInstall_VISTA,USB\VID_04A9&PID_2708&MI_00
%LPTENUM\CNC.DeviceDesc%=CNCInstallNet_VISTA,CANON_MFNP&%CNCRFN%
;........................................ WinXP(64-bit) section
[CNCInstall_XP.NTamd64]
Include=sti.inf
Needs=STI.USBSection
SubClass=StillImage
DeviceType=1
DeviceSubType=0x1
DeviceData=CNCDeviceData
AddReg=CNCAddreg,CNCAddreg.USB,CNCUSDAddreg_XP
CopyFiles=WiaFiles,CNCDsFiles,ColorFiles.NT,MPScanLLD,CNCMediaFiles
ICMProfiles="sRGB Color Space Profile.icm"
; used for push button event
Capabilities=0x11
Events=PushButton.Events
DriverVer=06/17/2009, 11.3.0.0
FriendlyName=%CNC.FriendlyName%
[CNCInstall_XP.NTamd64.Services]
Include=sti.inf
Needs=STI.USBSection.Services
[CNCInstall_XP.NTamd64.CoInstallers]
CopyFiles = ScanCoInstaller_CopyFiles_x64
AddReg    = ScanCoInstaller_AddReg_x64
[ScanCoInstaller_CopyFiles_x64]
CNCLSO36b.dll
[ScanCoInstaller_AddReg_x64]
HKR,,CoInstallers32,0x00010000,"CNCLSO36b.dll,Coinstaller_EntryPoint"
;........................................ WinVista(64-bit) section
[CNCInstall_VISTA.NTamd64]
Include=sti.inf
Needs=STI.USBSection
SubClass=StillImage
DeviceType=1
DeviceSubType=0x1
DeviceData=CNCDeviceData_VISTA
AddReg=CNCAddreg,CNCAddreg.USB,CNCUSDAddreg_XP,CNCUSDAddreg_VISTA
CopyFiles=Wia2Files,CNCDsFiles,ColorFiles.NT,MPScanLLD,CNCMediaFiles
ICMProfiles="sRGB Color Space Profile.icm"
; used for push button event
Capabilities=0x11
Events=PushButton.Events
DriverVer=06/17/2009, 11.3.0.0
FriendlyName=%CNC.FriendlyName%
[CNCInstall_VISTA.NTamd64.Services]
Include=sti.inf
Needs=STI.USBSection.Services
[CNCInstall_VISTA.NTamd64.CoInstallers]
CopyFiles = ScanCoInstaller_CopyFiles_x64
AddReg    = ScanCoInstaller_AddReg_x64
[ScanCoInstaller_CopyFiles_x64]
CNCLSO36b.dll
[ScanCoInstaller_AddReg_x64]
HKR,,CoInstallers32,0x00010000,"CNCLSO36b.dll,Coinstaller_EntryPoint"
;........................................ WinXP(64-bit) section(Network)
[CNCInstallNet_XP.NTamd64]
Include=sti.inf
Needs=STI.SerialSection
SubClass=StillImage
DeviceType=1
DeviceSubType=0x1
DeviceData=CNCDeviceData
AddReg=CNCAddreg,CNCUSDAddreg_XP
CopyFiles=WiaFiles,CNCDsFiles,ColorFiles.NT,MPScanLLD,CNCMediaFiles
ICMProfiles="sRGB Color Space Profile.icm"
; used for push button event
Capabilities=0x11
Events=PushButton.Events
DriverVer=06/17/2009, 11.3.0.0
FriendlyName=%CNC.FriendlyName%
[CNCInstallNet_XP.NTamd64.Services]
Include=sti.inf
Needs=STI.SerialSection.Services
[CNCInstallNet_XP.NTamd64.CoInstallers]
CopyFiles = ScanCoInstaller_CopyFiles_x64
AddReg    = ScanCoInstaller_AddReg_x64
[ScanCoInstaller_CopyFiles_x64]
CNCLSO36b.dll
[ScanCoInstaller_AddReg_x64]
HKR,,CoInstallers32,0x00010000,"CNCLSO36b.dll,Coinstaller_EntryPoint"
;........................................ WinVista(64-bit) section(Network)
[CNCInstallNet_VISTA.NTamd64]
Include=sti.inf
Needs=STI.SerialSection
SubClass=StillImage
DeviceType=1
DeviceSubType=0x1
DeviceData=CNCDeviceData_VISTA
AddReg=CNCAddreg,CNCUSDAddreg_XP,CNCUSDAddreg_VISTA
CopyFiles=Wia2Files,CNCDsFiles,ColorFiles.NT,MPScanLLD,CNCMediaFiles
ICMProfiles="sRGB Color Space Profile.icm"
; used for push button event
Capabilities=0x11
Events=PushButton.Events
DriverVer=06/17/2009, 11.3.0.0
FriendlyName=%CNC.FriendlyName%
[CNCInstallNet_VISTA.NTamd64.Services]
Include=sti.inf
Needs=STI.SerialSection.Services
[CNCInstallNet_VISTA.NTamd64.CoInstallers]
CopyFiles = ScanCoInstaller_CopyFiles_x64
AddReg    = ScanCoInstaller_AddReg_x64
[ScanCoInstaller_CopyFiles_x64]
CNCLSO36b.dll
[ScanCoInstaller_AddReg_x64]
HKR,,CoInstallers32,0x00010000,"CNCLSO36b.dll,Coinstaller_EntryPoint"
;.......................................... Common Section
[PushButton.Events]
PushButtonPushed1=%PushButtonPushed1%,{66F2A894-EC9B-430c-9D52-E8719D200DAC},%ButtonApp%
PushButtonPushed2=%PushButtonPushed2%,{506AC8D1-E030-4f05-8F8A-4476153E2D6C},%ButtonApp%
PushButtonPushed3=%PushButtonPushed3%,{9813E8A6-3652-4768-9AD1-C89E9B5CA956},%ButtonApp%
PushButtonPushed4=%PushButtonPushed4%,{03B58D10-0245-4859-A489-D695C7729FB3},%ButtonApp%
[ColorFiles.NT]
CNZ005.ICC
CNFR08.ICC
[CNCDeviceData]
TwainDS=%CNC.TwainDS%
SpecialInfo=%CNC.SPInfo%
DeviceKey=%CNCRFN%
InstallDirectory="\TWAIN_32\%CNCRFN%\"
KeyNamePath=%KEYNAME%
DefaultKeyNamePath=%DEFAULTKEYNAME%
[CNCDeviceData_VISTA]
TwainDS=%CNC.TwainDS%
SpecialInfo=%CNC.SPInfo%
DeviceKey=%CNCRFN%
InstallDirectory="\TWAIN_32\%CNCRFN%\"
KeyNamePath=%KEYNAME%
DefaultKeyNamePath=%DEFAULTKEYNAME%
UI Class ID={DF89C549-D67D-4fb0-A575-547073BFAB11}
;The above GUID reused from sample MUST change for each Model.
[CNCAddreg]
HKLM,"%SGDKEY%","DeviceName",,%CNC.MDL%
HKLM,"%SGDKEY%","SeriesName",,%CNC.SRS%
HKLM,"%SGDKEY%","Manufacturer",,"Canon Inc."
HKLM,"%SGDKEY%","ProductFamily",,"TWAIN Scanners"
HKLM,"%SGDKEY%","ProductName",,%CNC.MDL%
HKLM,"%SGDKEY%","InstallDirectory",,"%10%\TWAIN_32\%CNCRFN%\"
HKLM,"%SGDKEY%","DeviceDriver",,"SCANINTF.DLL"
HKLM,"%SGDKEY%","ProductId",,"MF8300          "
HKLM,"%SGDKEY%","DataSourcePath",,"%10%\TWAIN_32\%CNCRFN%\cisds.ds"
HKLM,"%SGDKEY%","TextEnhance",0x00010001,0
HKLM,"%SGDKEY%","HiDefinitionMode",0x00010001,0
HKLM,"%SGDKEY%","AutoPreview",0x00010001,0
HKLM,"%SGDKEY%","AutoClose",0x00010001,0
HKLM,"%SGDKEY%","SavePreview",0x00010001,1
HKLM,"%SGDKEY%","DriverDate",,"06 2009"
HKLM,"%SGDKEY%","DriverVersion",,"11.3.0.0.mf09"
HKLM,"%SGDKEY%","ColorGear",,%CNC.ColorGear%
HKLM,"%SGDKEY%","ColorMatch Platen",,"CNFR08.ICC"
HKLM,"%SGDKEY%","SGIPPDEF",,"CNCFR08.DAT"
HKLM,"%SGDKEY%","Descreen",0x00010001,0
HKLM,"%SGDKEY%","Unsharp",0x00010001,3
HKLM,"%SGDKEY%","MultiLimitThreshold",0x00010001,180
HKLM,"%SGDKEY%","MultiJackUp",0x00010001,9
HKLM,"%SGDKEY%","MultiTrimJackUp",0x00010001,20
HKLM,"%SGDKEY%","CardPhotoDistThr",0x00010001,30
HKLM,"%SGDKEY%","PhotoTrimThr",0x00010001,210
HKLM,"%SGDKEY%","PhotoRThr",0x00010001,210
HKLM,"%SGDKEY%","PhotoGThr",0x00010001,210
HKLM,"%SGDKEY%","PhotoBThr",0x00010001,210
HKLM,"%SGDKEY%","CardTrimThr",0x00010001,30
HKLM,"%SGDKEY%","CardRThr",0x00010001,30
HKLM,"%SGDKEY%","CardGThr",0x00010001,30
HKLM,"%SGDKEY%","CardBThr",0x00010001,30
HKLM,"%SGDKEY%","ParWhiteBlackEth",0x00010001,5
HKLM,"%SGDKEY%","ParWhiteBlackEthDG",0x00010001,5
HKLM,"%SGDKEY%","ParWhiteBlackSth",0x00010001,35
HKLM,"%SGDKEY%","ParWhiteBlackVth",0x00010001,10
HKLM,"%SGDKEY%","ParLabelingHth",0x00010001,30
HKLM,"%SGDKEY%","ParLabelingLeft",0x00010001,1
HKLM,"%SGDKEY%","ParLabelingTop",0x00010001,1
HKLM,"%SGDKEY%","ParLabelingRight",0x00010001,1
HKLM,"%SGDKEY%","ParLabelingBottom",0x00010001,1
HKLM,"%SGDKEY%","DT_Left",,"10"
HKLM,"%SGDKEY%","DT_Top",,"0"
HKLM,"%SGDKEY%","DT_Width" ,,"1.5"
HKLM,"%SGDKEY%","DT_Length",,"4.5"
HKLM,"%SGDKEY%","DT_Border_1",,"2.5"
HKLM,"%SGDKEY%","DT_Border_2",,"3.5"
HKLM,"%SGDKEY%","DT_BkTh",,"18"
HKLM,"%SGDKEY%","DT_MinWhThr",,"15"
HKLM,"%SGDKEY%","DT_MaxWhThr",,"45"
HKLM,"%SGDKEY%","ButtonNum",0x00010001,1
HKLM,"%STIKEY%","MF8300",0x00010001,1
[CNCAddreg.USB]
HKLM,"%SGDKEY%","AvailableDriver",0x00010001,1
[CNCUSDAddreg_XP]
HKLM,"%WIASGDKEY%","ColorMatch",0x00010001,1
HKLM,"%WIASGDKEY%","ColorGear",,"%CNC.ColorGear%"
HKLM,"%WIASGDKEY%","TextEnhance",0x00010001,0
HKLM,"%WIASGDKEY%","Descreen",0x00010001,0
HKLM,"%WIASGDKEY%","UnsharpMask",0x00010001,0
HKLM,"%WIASGDKEY%","HiDefinitionMode",0x00010001,0
HKLM,"%WIASGDKEY%","ProductId",,"MF8300          "
HKLM,"%WIASGDKEY%","ButtonNum",0x00010001,1
HKLM,"%WIASGDKEY%","DspGamma",0x00010001,1
HKLM,"%WIASTIKEY%","MF8300",0x00010001,1
HKR,,USDClass,,"{4BA01336-9934-455e-8FB8-4A47A638DF0E}"
HKCR,CLSID\{4BA01336-9934-455e-8FB8-4A47A638DF0E},,,"Canon USD"
HKCR,CLSID\{4BA01336-9934-455e-8FB8-4A47A638DF0E}\InProcServer32,,,%11%\CNCC8300.DLL
HKCR,CLSID\{4BA01336-9934-455e-8FB8-4A47A638DF0E}\InProcServer32,ThreadingModel,,"Both"
; The above GUID is specific to MF8300 and MUST change for a different model.
[CNCUSDAddreg_VISTA]
HKCR,CLSID\{DF89C549-D67D-4fb0-A575-547073BFAB11},,,"WIA Driver UI Extension"
HKCR,CLSID\{DF89C549-D67D-4fb0-A575-547073BFAB11}\shellex\ImageProcessingFilter\{CA0D4D3E-98ED-4787-AF02-4AF2A1303ACC}
; The above GUID is specific to MF8300 and MUST change for a different model.
HKCR,CLSID\{CA0D4D3E-98ED-4787-AF02-4AF2A1303ACC},,,"Canon Image Processing Filter"
HKCR,CLSID\{CA0D4D3E-98ED-4787-AF02-4AF2A1303ACC}\InProcServer32,,,%11%\CNCE8300.dll
HKCR,CLSID\{CA0D4D3E-98ED-4787-AF02-4AF2A1303ACC}\InProcServer32,ThreadingModel,,"Both"
; The above GUID is specific to MF8300 and MUST change for a different model.
[WiaFiles]
CNCC8300.DLL
CNCI8300.DLL
CNCL8300.DLL
[Wia2Files]
CNCC8300.DLL
CNCI8300.DLL
CNCL8300.DLL
CNCE8300.DLL
[CNCDsFiles]
CISDS.DS
SGUI.DLL
SGUI_RES.DLL
WIARES.DLL
IOP.DLL
ITLIB32.DLL
SCANINTF.DLL
TPM.DLL
CNCFR08.DAT
MC2.TXT
JDA_CIMG.DLL
NBS4MB.DLL
NBSCOR4M.DLL
RMSLANTC.DLL
RSTCOL.DLL
[MPScanLLD]
CNCMFP36.INI,,,0x20
CNCLSI36b.DLL,,,0x20
CNCLSD36b.DLL,,,0x20
CNCLSC36b.DLL,,,0x20
CNCLST36b.DLL,,,0x20
CNCLSU36b.DLL,,,0x20
[CNCMediaFiles]
CSSAMP1.MID
;-------------------------------Source Index
[SourceDisksFiles]
CNZ005.ICC=1
ITLIB32.DLL=1
JDA_CIMG.DLL=1
NBS4MB.DLL=1
NBSCOR4M.DLL=1
RMSLANTC.DLL=1
RSTCOL.DLL=1
CISDS.DS=1
SGUI.DLL=1
IOP.DLL=1
SCANINTF.DLL=1
TPM.DLL=1
SGUI_RES.DLL=1
WIARES.DLL=1
CSSAMP1.MID=1
CNCFR08.DAT=1
CNFR08.ICC=1
MC2.TXT=1
CNCC8300.DLL=1
CNCI8300.DLL=1
CNCL8300.DLL=1
CNCE8300.DLL=1
CNCMFP36.INI=1
CNCLSI36b.DLL=1
CNCLSD36b.DLL=1
CNCLSC36b.DLL=1
CNCLST36b.DLL=1
CNCLSU36b.DLL=1
CNCLSO36b.DLL =1
[SourceDisksNames]
1=%D1%,scan.cab,
;-------------------------------String Aliases
[Strings]
Msft="Canon"
Mfg="Canon"
SGDKEY="Software\Wow6432Node\Canon\SateraMFP1\ScanGear\11.3\Devices\MF8300"
STIKEY="Software\Wow6432Node\Canon\SateraMFP1\ScanGear\STI"
DEFAULTKEYNAME="Software\Wow6432Node\Canon\SateraMFP1\Toolbox Ver4.9\Devices\"
KEYNAME="\Software\Canon\MFToolbox\"
WIASGDKEY="Software\Canon\SateraMFP1\WIA\3.0\Devices\MF8300"
WIASTIKEY="Software\Canon\SateraMFP1\WIA\STI"
D1="Canon MF8300 Series Setup Disk"
LPTENUM\CNC.DeviceDesc="Canon MF8300 Series"
ButtonApp        = "MF Toolbox Ver4.9"
CNCRFN           = "MF8300"
CNC.MDL          = "Canon MF8300"
CNC.SRS          = "Canon MF8300 Series"
CNC.DeviceDesc   = "Canon MF8300"
CNC.SPInfo       = "Canon MF8300 Scanner"
CNC.TwainDS      = "Canon MF8300 Series"
CNC.ColorGear    = "FR08"
PushButtonPushed1= "Scan-1"
PushButtonPushed2= "Scan-2"
PushButtonPushed3= "Scan-3"
PushButtonPushed4= "Scan-4"
CNC.FriendlyName     = "WIA Canon MF8300 Series"
greeting
Sixten

Problem in unattended installation of Windows 10 OS image from its ISO

Hi There,
I am trying to install unattended Windows 10 OS image from its ISO by unattended.xml. While doing it windows boot screen get stuck at windows setup screen where it ask input for Language, TIme format and Keyboard input method. For same
process if I use windows 8.1 ISO for installation it works fine. From technet I come to know that Windows 10 has NT DISM version as 6.4 and 8.1 has 6.3. But I am not getting how I can make these change in my automation..
We are creating a FLP file which includes (unattended.xml and few other files)and then specify that file to Vmware workstation Windows 10 image floppy drive and Windows 10 iso to DVD drive and then booting the VM.
Same process works for Windows 8.1 OS unattended installation but it is getting failed for Windows 10.
Please help.
Regards,
Nortonboy

Hi Alex,
I am using ISO :- 9841.0.140912-1613.FBL_RELEASE_CLIENTPRO-CORE_OEMRET_X64FRE_EN-US.ISO
Answer file :- autounattend.xml.
Yeah same answer file works for Win 8.1 but when I am useing above ISO which is same what you mentioned but still it stuck.
I am using below content in autounattend.xml
##################################3
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<SetupUILanguage>
<UILanguage>en-us</UILanguage>
</SetupUILanguage>
<InputLocale>en-us</InputLocale>
<SystemLocale>en-us</SystemLocale>
<UILanguage>en-us</UILanguage>
<UserLocale>en-us</UserLocale>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SkipAutoActivation>true</SkipAutoActivation>
</component
<component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<UserData>
<AcceptEula>true</AcceptEula>
<ProductKey>
<WillShowUI>OnError</WillShowUI>
<Key></Key>
</ProductKey>
</UserData>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<DiskConfiguration>
<WillShowUI>OnError</WillShowUI>
<DisableEncryptedDiskProvisioning>true</DisableEncryptedDiskProvisioning>
<Disk>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
<CreatePartitions>
<CreatePartition>
<Extend>true</Extend>
<Order>1</Order>
<Type>Primary</Type>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition>
<Active>true</Active>
<Format>NTFS</Format>
<Label>Windows</Label>
<Order>1</Order>
<PartitionID>1</PartitionID>
</ModifyPartition>
</ModifyPartitions>
</Disk>
</DiskConfiguration>
<ImageInstall>
<OSImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
<WillShowUI>OnError</WillShowUI>
<InstallToAvailablePartition>false</InstallToAvailablePartition>
</OSImage>
</ImageInstall>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Security-SPP-UX" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<component name="Microsoft-Windows-LUA-Settings" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<EnableLUA>false</EnableLUA>
</component>
<component name="Security-Malware-Windows-Defender" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<DisableAntiSpyware>true</DisableAntiSpyware>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<DisableSR>1</DisableSR>
</component>
<component name="Microsoft-Windows-SQMAPI" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<CEIPEnabled>0</CEIPEnabled>
</component>
<component name="Networking-MPSSVC-Svc" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
<PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
<PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
<DomainProfile_DisableNotifications>true</DomainProfile_DisableNotifications>
<PrivateProfile_DisableNotifications>true</PrivateProfile_DisableNotifications>
<PublicProfile_DisableNotifications>true</PublicProfile_DisableNotifications>
</component>
<component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<UserAccounts>
<AdministratorPassword>
<Value>password</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>symantec</Value>
<PlainText>true</PlainText>
</Password>
<Description>Automation Account</Description>
<DisplayName>Automation Account</DisplayName>
<Group>Administrators;Power Users</Group>
<Name>Automation</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
<ProtectYourPC>3</ProtectYourPC>
<NetworkLocation>Other</NetworkLocation>
</OOBE>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<VerticalResolution>768</VerticalResolution>
</Display>
<TimeZone>Pacific Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="amd64">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
</unattend>
Do you guys have any inputs on this issue
Nortonboy

Inject Drivers Task Sequence Step vs Using DriverSelectionProfile in Database

I'm using a Database and 'Make and Model' in MDT 2012. I wonder if I specify a DriverSelectionProfile in the Database, what happens when the Task Sequence reaches the Preinstall > Inject Drivers step? Does it process the selection there and ignore the
Database settings? Or should I disable this step in the Task Sequence?
Orange County District Attorney

If you are having driver folders that are named after the computer models a single line is enough. MDT will replace the variable with the real model name. If you only deploy Windows 7 SP1 x64 you can set in the CustomSettings.ini file.
[Default]
DriverGroup001=Windows 7 x64\%Model%
If you deploy multiple operating systems (Windows Server 2012 R2, Windows 8.1 and Windows 7) it's easier to set it in the task sequence instead.
/ Johan
Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Windows 7 Sysprepped Image - Injecting Drivers issue

Similar Messages

Maybe you are looking for