Example MDT rules config

A Thank you to Amine Lallali for providing me with this config file below

Copy the below to rules.ini

[Settings]

Priority=Default

Properties=MyCustomProperty

[Default]

OSInstall=Y

SkipCapture=YES

SkipAdminPassword=YES

SkipProductKey=YES

SkipComputerBackup=YES

SkipBitLocker=YES

EventService=http://SRVTST19:9800

AdminPassword=Whtc12345

SkipDomainMembership=YES

;<DOMAIN JOIN INFORMATION>

;NetworkLocation=Work

SkipDomainMembership=YES

JoinDomain=ict.local

DomainAdmin=wds

DomainAdminDomain=ict.local

DomainAdminPassword=Whtc12345

SkipTaskSequence=NO

TaskSequenceID=1

DriverSelectionProfile=Nothing

DriverInjectionMode=ALL

DriverGroup001=Windows 10 x64\%Model%

FinishAction=REBOOT

SkipDeploymentType=YES

DeploymentType=NEWCOMPUTER

SkipUserData=YES

SkipLocaleSelection=YES

KeyboardLocale=0809:00000809

UserLocale=en-US

UILanguage=en-US

SkipTimeZone=YES

TimeZoneName=GMT Standard Time

_SMSTSOrgName=Running %TaskSequenceID% on %OSDComputername%

SkipAppsOnUpgrade=YES

SkipCapture=YES

DoCapture=NO

SkipApplications=NO

SkipSummary=YES

Home_page=http://www.google.com

SkipFinalSummary=Yes

Comments

Add and Remove Drivers to an offline Windows Image or WinPE

Add and Remove Drivers to an offline Windows Image Link https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/add-and-remove-drivers-to-an-offline-windows-image You can use DISM to install or remove driver (.inf) files in an offline Windows or WinPE image. You can either add or remove the drivers directly by using the command prompt, or apply an unattended answer file to a mounted .wim, .ffu, .vhd, or .vhdx file. When you use DISM to install a device driver to an offline image, the device driver is added to the driver store in the offline image. When the image is booted, Plug and Play (PnP) runs and associates the drivers in the store to the corresponding devices on the computer. Note To add drivers to a Windows 10 image offline, you must use a technician computer running Windows 10, Windows Server 2016, or Windows Preinstallation Environment (WinPE) for Windows 10. Driver signature verification may fail when you add a driver to a Windows 10 im...

Create a Windows 10 x64 Enterprise USB Installer

Download Window 10 Enterprise 1809 with the Media Creation Tool The October 2018 release of Windows 10 has just dropped and is now availabe to download using the Media Creation Tool . Using the GUI you can download the consumer ISO which contains the Home, Professional and Education SKUs of Windows 10. If you want to download the Enterprise version of Windows 10, but don’t have access to Microsoft VLSC or Action Pack subscriptions, it is possible to download it using the Media Creation Tool if you know the right command line switches. To download Windows 10 Enterprise 1809 using the Media Creation Tool, log in with a local administrator account (for some reason it isn’t good enough to run the tool using Run as administrator, you actually do have to be logged in as an administrator) and download the tool. Open a CMD prompt and change directory to the directory you saved the Media Creation Tool in, and enter the following command: MediaCreationTool1809.exe /Eul...

How to Fix Sysprep was not able to validate your Windows installation

How to Fix Sysprep was not able to validate your Windows installation For example, if you have already downloaded apps on a Windows 8.1 or 10 machine where you want to run the sysprep command, the sysprepact log file (setupact.log) which is created under C:\Windows\System32\sysprep\Panther folder displays the following error(s): " [0x0f0036] SYSPRP spopk.dll:: Sysprep will not run on an upgraded OS. You can only run Sysprep on a custom (clean) install version of Windows. [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'Sysprep_Clean_Validate_Opk' from C:\Windows\System32\spopk.dll; dwRet = 0x139f SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Cleanup.xml; dwRet = 0x139f SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x139f [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halti...

KagedTech

Search This Blog