KagedTech

A Thank you to Amine Lallali for providing me with this config file below Copy the below to bootstrap.ini [Settings] Priority=Default [Default] DeployRoot=\\SRVTST19\DeploymentShare$ UserDomain=ICT.LOCAL UserID=wds UserPassword=Whtc12345 SkipBDDWelcome=YES

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 _SMST

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, halting sysprep execution.

Get Serial number from pc from the command prompt     wmic bios get serialnumber Avaya CMS 429 error fix Make sure to unhide "hidden" files Delete the following folder c:\users\Userid\appdata\roaming\avaya\cms supervisor r16\cache c:\users\Userid\appdata\roaming\avaya\cms supervisor r18\cache Backup Drive Mappings from the registery HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Map Network Drive MRU Cisco VPN Client hangs at “Opening cert store” 1) Open Microsoft Management Console (type mmc in Run or search). 2) Add Snap-in "Certificates" (File -> Add/Remove Snap-in... -> [find and add "Certificates] -> OK) 3) Go to folder Personal/Certificates 4) Remove any unwanted certificates (for me it was certificates added by Fiddler to enable SSL traffic debugging) Sticky Notes Backup File C:\Users\username\AppData\Roaming\Microsoft\Sticky Notes\

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 image offli

Download Windows ADK and  WinPE (Windows PE) Link from https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/download-winpe--windows-pe Before you can use WinPE, you'll have to create a bootable WinPE USB flash drive, CD, DVD, or virtual hard drive. The files you need to create WinPE media are included in the Winpe Add-on to the Windows Assessment and Deployment Kit. To create WinPE media, you'll have to install the ADK with the Deployment tools option, and then install the WindowsPE addon kit. Download and Install the Windows ADK For the ADK for Windows 10, version 1809 To start working with WinPE, download and install both the Windows Assessment and Deployment Kit (ADK) and the WinPE Add-ons. Download The Windows ADK for Windows 10, Version 1809 Here https://go.microsoft.com/fwlink/?linkid=2026036 During installation, select Deployment Tools. Download The Windows PE Add-on for the ADK Here https://go.microsoft.com/fwlink/?linkid=2022233

Create bootable WinPE media (Information from https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/winpe-create-usb-bootable-drive ) The Windows Assessment and Deployment Kit (ADK) includes the CopyPE and MakeWinPEMedia command line utilities. When run from the Deployment and Imaging Tools Environment, CopyPE creates a working set of WinPE files, that MakeWinPEMedia can use to create bootable WinPE media. MakeWinPEMedia can create bootable WinPE USB drives, virtual hard disks, or ISOs that allow you to boot a VHD or burn to a DVD or CD. CopyPE and MakeWinPEMedia are installed when you choose the Deployment tools and Windows Preinstallation Environment options when installing the ADK. If you're using the ADK for Windows 10, version 1809, Windows PE is a separate add-on that you download and install after you install the ADK. You can download the WinPE add-on from the Download Center. Step 1: Create working files No matter what type of media you're go

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 /Eula Accept

rem == CreatePartitions-BIOS.txt == rem == These commands are used with DiskPart to rem    create three partitions rem    for a BIOS/MBR-based computer. rem    Adjust the partition sizes to fill the drive rem    as necessary. == select disk 0 clean rem == 1. System partition ====================== create partition primary size=100 format quick fs=ntfs label="System" assign letter="S" active rem == 2. Windows partition ===================== rem ==    a. Create the Windows partition ======= create partition primary rem ==    b. Create space for the recovery tools rem       ** Update this size to match the size of rem          the recovery tools (winre.wim) rem          plus some free space. shrink minimum=500 rem ==    c. Prepare the Windows partition ====== format quick fs=ntfs label="Windows" assign letter="W" rem == 3. Recovery tools partition ============== create partition primary format quick fs=ntfs label="Reco

rem == CreatePartitions-UEFI.txt == rem == These commands are used with DiskPart to rem    create four partitions rem    for a UEFI/GPT-based PC. rem    Adjust the partition sizes to fill the drive rem    as necessary. == select disk 0 clean convert gpt rem == 1. System partition ========================= create partition efi size=100 rem    ** NOTE: For Advanced Format 4Kn drives, rem               change this value to size = 260 ** format quick fs=fat32 label="System" assign letter="S" rem == 2. Microsoft Reserved (MSR) partition ======= create partition msr size=16 rem == 3. Windows partition ======================== rem ==    a. Create the Windows partition ========== create partition primary rem ==    b. Create space for the recovery tools === rem       ** Update this size to match the size of rem          the recovery tools (winre.wim) rem          plus some free space. shrink minimum=500 rem ==    c. Prepare the Windows partition ====

rem == mapshare.cmd == rem == This command will map a shared network folder rem    or NAS drive to be used in capturing and deploying rem    the system image. rem    Winpe won't work with smb1 shares rem    Share needs a username and password rem    from what I've seen so far. net use y: \\ServerName\FolderName /user:image image

rem == capture.cmd == rem == These commands capture a specified Windows rem    image file to the specified share, and save it to a rem    .wim image file Dism /Capture-Image /ImageFile:"y:\w10.wim" /CaptureDir:C:\ /Name:w10x64

rem == ApplyImage.bat == rem == These commands deploy a specified Windows rem    image file to the Windows partition, and configure rem    the system partition. rem    Usage:   ApplyImage WimFileName rem    Example: ApplyImage E:\Images\ThinImage.wim == rem == Set high-performance power scheme to speed deployment == call powercfg /s 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c rem == Apply the image to the Windows partition == dism /Apply-Image /ImageFile:%1 /Index:1 /ApplyDir:W:\ rem == Copy boot files to the System partition == W:\Windows\System32\bcdboot W:\Windows /s S: :rem == Copy the Windows RE image to the :rem    Windows RE Tools partition == md R:\Recovery\WindowsRE xcopy /h W:\Windows\System32\Recovery\Winre.wim R:\Recovery\WindowsRE\ :rem == Register the location of the recovery tools == W:\Windows\System32\Reagentc /Setreimage /Path R:\Recovery\WindowsRE /Target W:\Windows :rem == Verify the configuration status of the images. == W:\Windows\System32\Reag