URLs will be parsed automatically
http://www.kbpublisher.com - http://www.kbpublisher.com
[b]text[/b] - Bold text.
[u]text[/u] - Underline text.
[i]text[/i] - Italic text.
[color=green]text[/color] - Colored text.
[url]kbpublisher.com[/url] - kbpublisher.com
[url=kbpublisher.com]text[/url] - text
[email]firstname.lastname@example.org[/email] - email@example.com
[h1]text[/h1] - Caption text.
Newer versions of the Realtek LAN Driver, from around mid-2014 onwards, may fail to import into Windows Deployment Services, either WDS 2008R2 or WDS 2012.
WDS reports that the package addition failed. However, no actual error code or meaningful reason for the failure is displayed.
The root cause appears to be a problem with the WDS Jet Database and either the size of the Realtek LAN driver, or some particular information inside the driver INF. If you use the WDS Powershell utilities to try and import the driver an error code is return which indicates that a database error is being generated, with a record being "too big".
There is one full resolution for this issue and three alternatives should your situation require it. However with the release of the April 2016 Realtek driver, only the full resolution should be required.
As of April 2017, some x64 versions of the Realtek driver, even the WinPE version, do not import into WDS for Server 2008R2. There is no resolution for this apart from upgrading your Server infrastructure or the work-arounds below.
Overview of Adding a Driver to a WIM file
Imagex /mountrw "d:\wimwork\boot.wim" 1 d:\output
Dism /Image:d:\output /Add-Driver /Driver:d:\drivers /Recurse /ForceUnsigned
Imagex /unmount /commit d:\output
Note: Always ensure that the finished, built machine has the latest Realtek network driver on it, before handing it over to the user. The temporary 2013 Realtek network driver should not be left running on deployed machines.
Article ID: 441
Last updated: 13 Apr, 2017
Posted: 16 Mar, 2015 by Andrew Sharrad
Updated: 13 Apr, 2017 by Andrew Sharrad