Windows 7 / 8.1 : Dynamically load drivers in a SCCM 2012 task sequence with Nomad
Overview: Within your organisation you have many different types of computer models. You want a single build task sequence that can dynamically select the correct driver package to install with the OS.
The Answer: To achieve the dynamic selection it is necessary to implement a MDT 2013 database (supply link) in which the Task Sequence will gather the assigned PackageID based on a Model type WMI query.
With this Task Sequence variable %OSDDRIVERPACKAGE% it is possible to use a command line to run an election and locate the PackageID within the local subnet.
NomadPackageLocator.exe -Nomad_local -RemoveHTTPLocations -RequireNomad -HideErrorDialog -RestrictPackages=%OSDDRIVERPACKAGE%
Then as a follow up step the use of SMSNomad.exe prestage command will query the DP for the package and then download the Package from the winner of the election
SMSNomad.exe --s --Prestage --pp=http://%SMSDP%/SMS_PP_SMSPKG$/%OSDDRIVERPACKAGE%
More details surrounding the database creation, Single Site Store, and things to watch out for in the log to follow. Use the comment field if you wish me to expand on any particular point.
Monday, September 22, 2014
Windows 7 / 8.1 : Dynamically load drivers in a SCCM 2012 task sequence
Windows 7 / 8.1 : Dynamically load drivers in a SCCM 2012 task sequence with Nomad
Overview: Within your organisation you have many different types of computer models. You want a single build task sequence that can dynamically select the correct driver package to install with the OS.
The Answer: To achieve the dynamic selection it is necessary to implement a MDT 2013 database (supply link) in which the Task Sequence will gather the assigned PackageID based on a Model type WMI query.
With this Task Sequence variable %OSDDRIVERPACKAGE% it is possible to use a command line to run an election and locate the PackageID within the local subnet.
NomadPackageLocator.exe -Nomad_local -RemoveHTTPLocations -RequireNomad -HideErrorDialog -RestrictPackages=%OSDDRIVERPACKAGE%
Then as a follow up step the use of SMSNomad.exe prestage command will query the DP for the package and then download the Package from the winner of the election
SMSNomad.exe --s --Prestage --pp=http://%SMSDP%/SMS_PP_SMSPKG$/%OSDDRIVERPACKAGE%
More details surrounding the database creation, Single Site Store, and things to watch out for in the log to follow. Use the comment field if you wish me to expand on any particular point.
Overview: Within your organisation you have many different types of computer models. You want a single build task sequence that can dynamically select the correct driver package to install with the OS.
The Answer: To achieve the dynamic selection it is necessary to implement a MDT 2013 database (supply link) in which the Task Sequence will gather the assigned PackageID based on a Model type WMI query.
With this Task Sequence variable %OSDDRIVERPACKAGE% it is possible to use a command line to run an election and locate the PackageID within the local subnet.
NomadPackageLocator.exe -Nomad_local -RemoveHTTPLocations -RequireNomad -HideErrorDialog -RestrictPackages=%OSDDRIVERPACKAGE%
Then as a follow up step the use of SMSNomad.exe prestage command will query the DP for the package and then download the Package from the winner of the election
SMSNomad.exe --s --Prestage --pp=http://%SMSDP%/SMS_PP_SMSPKG$/%OSDDRIVERPACKAGE%
More details surrounding the database creation, Single Site Store, and things to watch out for in the log to follow. Use the comment field if you wish me to expand on any particular point.
Windows 8.1: How to capture a golden image and preserve the Metro layout.
Windows 8.1: How to capture a golden image and preserve the Metro layout.
Overview: There are several ways in which it is possible to customize the start screen/ Metro layout in Windows 8.1 (GPO, PowerShell, XML). I didn’t want to use GPO as the menu options would be enforced preventing the end user from making customizations and PowerShell would only modify the current users profile. The intention was to provide an out of box experience that was customized for each users who logs in.
The use of ‘CopyProfile’ during the image capture is able to apply a default layout for each user who logs in after being built.
The solution:
1. Customize the Metro layout, start screen etc
2. Create an XML file called Unattend.xml
3. Open Unattend.xml with notepad and copy the corresponding text below (Choose the correct OS architecture). Save to C:\Windows\System32\Sysprep
[64-bit Unattend.xml]
<?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:f:/sw_dvd9_sa_win_ent_8.1_64bit_english_-2_mlf_x19-49847/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
[32-bit Unattend.xml]
<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" 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:f:/sw_dvd9_sa_win_ent_8.1_64bit_english_-2_mlf_x19-49847/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
4. Open Admin command prompt and type:
C:\Windows\System32\Sysprep\Sysprep /generalize /oobe /shutdown
TechNet reference.
http://technet.microsoft.com/en-us/library/hh825135.aspx
Windows 8.1: How to capture a golden image and preserve the Metro layout.
Windows 8.1: How to capture a golden image and preserve the Metro layout.
Overview: There are several ways in which it is possible to customize the start screen/ Metro layout in Windows 8.1 (GPO, PowerShell, XML). I didn’t want to use GPO as the menu options would be enforced preventing the end user from making customizations and PowerShell would only modify the current users profile. The intention was to provide an out of box experience that was customized for each users who logs in.
The use of ‘CopyProfile’ during the image capture is able to apply a default layout for each user who logs in after being built.
The solution:
1. Customize the Metro layout, start screen etc
2. Create an XML file called Unattend.xml
3. Open Unattend.xml with notepad and copy the corresponding text below (Choose the correct OS architecture). Save to C:\Windows\System32\Sysprep
[64-bit Unattend.xml]
<?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:f:/sw_dvd9_sa_win_ent_8.1_64bit_english_-2_mlf_x19-49847/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
[32-bit Unattend.xml]
<?xml version="1.0" encoding="utf-8"?><unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" 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:f:/sw_dvd9_sa_win_ent_8.1_64bit_english_-2_mlf_x19-49847/sources/install.wim#Windows 8.1 Enterprise" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
4. Open Admin command prompt and type:
C:\Windows\System32\Sysprep\Sysprep /generalize /oobe /shutdown
TechNet reference.
http://technet.microsoft.com/en-us/library/hh825135.aspx
Windows 8.1: How to install .NET 3.5
Windows 8.1: How to install .NET 3.5
Overview: When you try to install .NET 3.5 through the control panel you have the choice to search Windows update servers or specify media. In either case you are unable to install .NET with an error.
The solution:
1. Copy the d:\SXS folder from the media to the C drive.
2. Open and Administrator command prompt.
3. Type:
dism.exe /online /enable-feature /featurename:NetFX3 /Source:c:\sxs /
4. .NET has been successfully installed.
Overview: When you try to install .NET 3.5 through the control panel you have the choice to search Windows update servers or specify media. In either case you are unable to install .NET with an error.
The solution:
1. Copy the d:\SXS folder from the media to the C drive.
2. Open and Administrator command prompt.
3. Type:
dism.exe /online /enable-feature /featurename:NetFX3 /Source:c:\sxs /
4. .NET has been successfully installed.
Windows 8.1: How to install .NET 3.5
Windows 8.1: How to install .NET 3.5
Overview: When you try to install .NET 3.5 through the control panel you have the choice to search Windows update servers or specify media. In either case you are unable to install .NET with an error.
The solution:
1. Copy the d:\SXS folder from the media to the C drive.
2. Open and Administrator command prompt.
3. Type:
dism.exe /online /enable-feature /featurename:NetFX3 /Source:c:\sxs /
4. .NET has been successfully installed.
Overview: When you try to install .NET 3.5 through the control panel you have the choice to search Windows update servers or specify media. In either case you are unable to install .NET with an error.
The solution:
1. Copy the d:\SXS folder from the media to the C drive.
2. Open and Administrator command prompt.
3. Type:
dism.exe /online /enable-feature /featurename:NetFX3 /Source:c:\sxs /
4. .NET has been successfully installed.
Monday, September 15, 2014
1e PXE Everywhere / PXE Lite
1e PXE Everywhere / PXE Lite
Overview:
Dell Venue 11 Pro to PXE boot using 1e PXE Everywhere results in the message below and fails to load the boot image.
Checking Media Presence
Media Present
Start PXE over IPv4
PXELiteServer.log details
Sending DHCP ACK to [D4##:##:##:##:D3:F5] at client 10.160.3.204:68 PXELiteDhcpFilter_D4##:##:##:##:D3:F5 15/09/2014 16:18:49 11412 (0x2C94)
Error: recvfrom failed (DHCP). The virtual circuit was reset by the remote side PXELiteDhcpFilter_D4##:##:##:##:D3:F5 15/09/2014 16:18:49 11412 (0x2C94)
More to follow.. Leave feedback on your successes
Resolution: In my case I was using PXE Everywhere v2.2 which will support laptops with UEFI as well as Legacy boot options. However, tablets like the Venue 11 Pro are native UEFI and this is currently not supported! I big surprise considering the demands on Enterprise IT to deploy Windows 8.1 as just another OS (JAOS we'll see if it catches on). 1e reported that in v2.3 due later this year (todays date: 22/09/2014) UEFI native will be fully supported.
Overview:
Dell Venue 11 Pro to PXE boot using 1e PXE Everywhere results in the message below and fails to load the boot image.
Checking Media Presence
Media Present
Start PXE over IPv4
PXELiteServer.log details
Sending DHCP ACK to [D4##:##:##:##:D3:F5] at client 10.160.3.204:68 PXELiteDhcpFilter_D4##:##:##:##:D3:F5 15/09/2014 16:18:49 11412 (0x2C94)
Error: recvfrom failed (DHCP). The virtual circuit was reset by the remote side PXELiteDhcpFilter_D4##:##:##:##:D3:F5 15/09/2014 16:18:49 11412 (0x2C94)
More to follow.. Leave feedback on your successes
Resolution: In my case I was using PXE Everywhere v2.2 which will support laptops with UEFI as well as Legacy boot options. However, tablets like the Venue 11 Pro are native UEFI and this is currently not supported! I big surprise considering the demands on Enterprise IT to deploy Windows 8.1 as just another OS (JAOS we'll see if it catches on). 1e reported that in v2.3 due later this year (todays date: 22/09/2014) UEFI native will be fully supported.
1e PXE Everywhere / PXE Lite
1e PXE Everywhere / PXE Lite
Overview:
Dell Venue 11 Pro to PXE boot using 1e PXE Everywhere results in the message below and fails to load the boot image.
Checking Media Presence
Media Present
Start PXE over IPv4
PXELiteServer.log details
Sending DHCP ACK to [D4##:##:##:##:D3:F5] at client 10.160.3.204:68 PXELiteDhcpFilter_D4##:##:##:##:D3:F5 15/09/2014 16:18:49 11412 (0x2C94)
Error: recvfrom failed (DHCP). The virtual circuit was reset by the remote side PXELiteDhcpFilter_D4##:##:##:##:D3:F5 15/09/2014 16:18:49 11412 (0x2C94)
More to follow.. Leave feedback on your successes
Resolution: In my case I was using PXE Everywhere v2.2 which will support laptops with UEFI as well as Legacy boot options. However, tablets like the Venue 11 Pro are native UEFI and this is currently not supported! I big surprise considering the demands on Enterprise IT to deploy Windows 8.1 as just another OS (JAOS we'll see if it catches on). 1e reported that in v2.3 due later this year (todays date: 22/09/2014) UEFI native will be fully supported.
Overview:
Dell Venue 11 Pro to PXE boot using 1e PXE Everywhere results in the message below and fails to load the boot image.
Checking Media Presence
Media Present
Start PXE over IPv4
PXELiteServer.log details
Sending DHCP ACK to [D4##:##:##:##:D3:F5] at client 10.160.3.204:68 PXELiteDhcpFilter_D4##:##:##:##:D3:F5 15/09/2014 16:18:49 11412 (0x2C94)
Error: recvfrom failed (DHCP). The virtual circuit was reset by the remote side PXELiteDhcpFilter_D4##:##:##:##:D3:F5 15/09/2014 16:18:49 11412 (0x2C94)
More to follow.. Leave feedback on your successes
Resolution: In my case I was using PXE Everywhere v2.2 which will support laptops with UEFI as well as Legacy boot options. However, tablets like the Venue 11 Pro are native UEFI and this is currently not supported! I big surprise considering the demands on Enterprise IT to deploy Windows 8.1 as just another OS (JAOS we'll see if it catches on). 1e reported that in v2.3 due later this year (todays date: 22/09/2014) UEFI native will be fully supported.
Subscribe to:
Posts (Atom)