Quantcast
Channel: Setup Deployment forum
Viewing all 2818 articles
Browse latest View live
↧

Service Pack 1 is reverting back 8% on Windows 2008 R2 Enterprise

January 30, 2017, 9:46 am
$
0
0

This error is from setuapi.dev.log   How do i fix this


>>>  [Unstage Driver Updates]
>>>  Section start 2017/01/30 17:59:13.581
      cmd: C:\Windows\servicing\TrustedInstaller.exe
     sto: Driver Update Context:
     sto:      Image State        = Specialized
     sto:      Image Architecture = amd64
     sto:      Transaction        = None
     sto:      Driver Updates     = 56
     sto: Unstaging all driver updates.
     sto: {Delete Driver Package: C:\Windows\System32\DriverStore\FileRepository\tsgenericusbdriver.inf_amd64_neutral_24c807694f614911\tsgenericusbdriver.inf} 17:59:13.690
     sto:      Deleting driver package from Driver Store:
     sto:           Driver Store   = C:\Windows\System32\DriverStore (Online | 6.1.7600)
     sto:           Driver Package = C:\Windows\System32\DriverStore\FileRepository\tsgenericusbdriver.inf_amd64_neutral_24c807694f614911\tsgenericusbdriver.inf
     sto:           Flags          = 0x00000001
!!!  idb:      Cannot unregister a published driver store entry 'tsgenericusbdriver.inf_amd64_neutral_24c807694f614911', Error = 0x00000032
!!!  idb:      Failed to unregister 'tsgenericusbdriver.inf', Error = 0x00000032
!!!  idb:      Error 50: The request is not supported.
!!!  sto:      Failed to unregister driver package 'C:\Windows\System32\DriverStore\FileRepository\tsgenericusbdriver.inf_amd64_neutral_24c807694f614911\tsgenericusbdriver.inf'. Error = 0x00000032
!!!  sto:      Failed to delete driver package from Driver Store. Error = 0x00000032
     sto: {Delete Driver Package: exit(0x00000032)} 17:59:13.752
!!!  sto: Failed to unstage all driver updates. Error = 0x00000032
     sto: Re-staging all unstaged driver updates.
     sto: {Import Driver Package: C:\Windows\WinSxS\amd64_tsgenericusbdriver.inf_31bf3856ad364e35_6.1.7601.17514_none_9872c8452ac8f816\tsgenericusbdriver.inf} 17:59:13.752
     sto:      Importing driver package into Driver Store:
     sto:           Driver Store   = C:\Windows\System32\DriverStore (Online | 6.1.7600)
     sto:           Driver Package = C:\Windows\WinSxS\amd64_tsgenericusbdriver.inf_31bf3856ad364e35_6.1.7601.17514_none_9872c8452ac8f816\tsgenericusbdriver.inf
     sto:           Architecture   = amd64
     sto:           Locale Name    = neutral
     sto:           Flags          = 0x00000245
!    sto:      Driver package 'tsgenericusbdriver.inf' already exists in Driver Store:
!    sto:           Filename = C:\Windows\System32\DriverStore\FileRepository\tsgenericusbdriver.inf_amd64_neutral_24c807694f614911\tsgenericusbdriver.inf (tsgenericusbdriver.inf)
     sto:      Imported driver package into Driver Store:
     sto:           Filename = C:\Windows\System32\DriverStore\FileRepository\tsgenericusbdriver.inf_amd64_neutral_24c807694f614911\tsgenericusbdriver.inf
     sto:           Time     = 15 ms
     sto: {Import Driver Package: exit(0x00000000)} 17:59:13.783
<<<  Section end 2017/01/30 17:59:13.783
<<<  [Exit status: FAILURE(0x00000032)]

↧
Search

Antminer s4

January 15, 2017, 4:03 pm
$
0
0
Hello, how are you guys doing? Hey, i don't have any idea on how to set the antminer to antpool or minergate, please, suggest me how to do it please!
↧
↧

WDS Driver package issue

January 31, 2017, 6:14 am
$
0
0
I have recently created a win 10 image on wds and now require to installed the drivers on the image, however I now receive "The request is not supported" whenever I try to add drivers to the image using the add drivers to boot image wizard, I have had this working 100% until this week, but not it wont work, please can you advise what may have changed?
↧

UEFI PXE Boot Issues - Intel I219-V / Killer E2500 NICs

February 1, 2017, 7:35 am
$
0
0

Hi Guys

Looking for some ideas/advice on this one.

We have a Server 2016 WDS Server. No MDT/SCCM, just a clean WDS install configured as a "Standalone Server".

Most systems PXE boot in UEFI using IPv4 Network Stack Options set at a UEFI BIOS level.

The only pattern to the systems that don't find the server is they have either of the following NIC's:

Intel(R) Ethernet Connection I219-V (e1d65x64.inf)

Killer E2500 (e2xw10x64.inf)

I've checked the Windows 10 ISO (released in Jan 2017) and it doesn't have the required drivers built in.

I've tried injecting the drivers using DISM and although it reports it's succeeded the systems with these LAN ports still don't find the server on the network.

The error when trying to PXE boot is:

PXE-E16: No offer received.

As an alternative idea I created a WinPE USB with a Discovery Image loaded in (including the two drivers) - these are having issues getting connected to the server during launch:

2017-02-01 16:02:19, Info                  IBS    InstallWindows:Successfully loaded resource language [en-GB]
2017-02-01 16:02:19, Info       [0x0601c1] IBS    InstallWindows:Install Path = X:\sources
2017-02-01 16:02:19, Info       [0x0601c2] IBS    InstallWindows:Setup Phase = 2
2017-02-01 16:02:19, Info       [0x0606cc] IBS    LogBootDeviceInfo:The firmware boot device ARC path is [multi(0)disk(0)rdisk(0)partition(1)] and NT path is [\Device\Harddisk2\Partition1].
2017-02-01 16:02:19, Info       [0x0606cc] IBS    LogBootDeviceInfo:The system boot device ARC path is [ramdisk(0)] and NT path is [\Device\Ramdisk{d9b257fc-684e-4dcb-ab79-03cfa2f6b750}].
2017-02-01 16:02:19, Info       [0x0601e9] IBS    CheckWinPEVersion:Compatible WinPE Version 10.0.14393 sp 0.0
2017-02-01 16:02:19, Info       [0x0601c9] IBS    InstallWindows:Starting a new install from WinPE
2017-02-01 16:02:19, Info                  IBS    InstallWindows: Setup working directory = X:\windows\panther
2017-02-01 16:02:19, Info       [0x0601ce] IBS    Setup has started phase 2 at 2017-02-01 16:02:19
2017-02-01 16:02:19, Info       [0x0601cf] IBS    Install source is X:\sources
2017-02-01 16:02:19, Info       [0x0601d0] IBS    Build version is 10.0.14393.0 (rs1_release.160715-1616)
2017-02-01 16:02:19, Info       [0x06403f] IBSLIB CreateSetupBlackboard:Creating a new persistent blackboard. Path is [X:\windows\panther\SetupInfo] Setup phase is [2]
2017-02-01 16:02:19, Info       [0x090008] PANTHR CBlackboard::Open: X:\windows\panther\SetupInfo succeeded.
2017-02-01 16:02:19, Info       [0x064043] IBSLIB CreateSetupBlackboard:Successfully created/opened Setup black board path is [X:\windows\panther\SetupInfo]
2017-02-01 16:02:19, Info                  IBS    InstallWindows:No UI language from a previous boot was found on the blackboard. Using selected language [en-GB].
2017-02-01 16:02:19, Info                  IBS    InstallWindows:Setup architecture is [x64]
2017-02-01 16:02:19, Info       [0x0601d5] IBS    InstallWindows:Starting with Empty Queue. Setup Phase = 2
2017-02-01 16:02:19, Info                  PANTHR InitializedCriticalSection for pExecQueue->csLock;
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module ScenarioDetect in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Engine in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Internal in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module ErrorHandler in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Diagnostic in diagnostic.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Unattend in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module ParseCommandLine in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Ems  in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module PrepareInstallDrive in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module TempDrive in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module CopySetupFiles in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module BootPrep in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module BootEntries in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module CopyPrivates in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module ProductKey in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module ComputerName in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module License in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module DiskInformation in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module FixBBPaths in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module DiskConfig in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module CreatePageFile in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Imaging in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module CopyImages in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module DeployImages in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module DiskSpace in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Completion in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module MountDev in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Cmi in cmisetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module SystemRestore in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module FirstBootCleanup in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module RestartModule in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module ExternalDrivers in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module CBS in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module SkuAssembly in cmisetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module LanguagePack in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module ConfigSet in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module UnattendImgInstall in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module CFGOfflineImage in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info                         PnPIBS: Initializing the PnP IBS Module ...

2017-02-01 16:02:19, Info                         PnPIBS: Successfully initialized the PnP IBS Module.

2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module PnP IBS module in pnpibs.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Compliance in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Rollback in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Locale in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Source media module in winsetup.dll
2017-02-01 16:02:19, Info       [0x060359] IBS    Callback_ScenarioDetect:Setup is starting from [2] phase
2017-02-01 16:02:19, Info                  IBS    Callback_BootEnvironmentDetect:FirmwareType 2.
2017-02-01 16:02:19, Info                  IBS    Callback_BootEnvironmentDetect: Detected boot environment: EFI
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module WinPEUI in win32ui.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module WinPEProgress in spprgrss.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module WinPEUpgLoader in upgloader.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module WdsClient in wdsclient.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module WpeUntndBtstrp in winsetup.dll
2017-02-01 16:02:19, Info                  PANTHR InitializeModule: Initializing ExecQueue->csLock;
2017-02-01 16:02:19, Info       [0x0601a4] IBS    LoadWorkerModules:Successfully added worker module Cryptography in cryptosetup.dll
2017-02-01 16:02:19, Info       [0x060004] IBS    Callback_UpdateDrivePathsOnBB:No need to update the blackboard paths.
2017-02-01 16:02:19, Info                  IBS    Callback_Engine_StartupScenarioIsWinPE:Setup is running from RAM drive. Path is [X:\sources]
2017-02-01 16:02:19, Info                  IBS    LoadHWCompatData:Successfully opened HW compat file [X:\sources\hwcompat.txt]
2017-02-01 16:02:19, Info                  IBS    LoadHWCompatData:Successfully opened HW compat file [X:\sources\hwexclude.txt]
2017-02-01 16:02:19, Info                  IBS    Callback_Compliance_LoadDeviceCompatDB:Count of Device IDs is [28134], count of exclusions is [62]
2017-02-01 16:02:19, Info                  IBS    EnumOnlineDriverStoreForInjectedDriverPackages:Enumerating online driver store for injected driver packages.
2017-02-01 16:02:19, Info                  IBS    EnumOnlineDriverStoreCallback:Found non inbox driver package [X:\windows\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_6c3fe40b6c06827e\e1d65x64.inf]
2017-02-01 16:02:19, Info                  IBS    GatherDeviceIDsInDriverPackage:Driver package path is [X:\windows\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_6c3fe40b6c06827e\e1d65x64.inf]
2017-02-01 16:02:19, Info                         GetModelSectionNameEx:Using section name [Intel.NTamd64.10.0.1]
2017-02-01 16:02:19, Info                  IBS    AddDeviceIDsToInjectedDriverNodeHelper:Model section name is [Intel.NTamd64.10.0.1]
2017-02-01 16:02:19, Info                  IBS    GatherDeviceIDsInDriverPackage:Successfully gathered device ID's from [X:\windows\System32\DriverStore\FileRepository\e1d65x64.inf_amd64_6c3fe40b6c06827e\e1d65x64.inf]
2017-02-01 16:02:19, Info                  IBS    EnumOnlineDriverStoreCallback:Found non inbox driver package [X:\windows\System32\DriverStore\FileRepository\e2xw10x64.inf_amd64_ad05f098c0c2086b\e2xw10x64.inf]
2017-02-01 16:02:19, Info                  IBS    GatherDeviceIDsInDriverPackage:Driver package path is [X:\windows\System32\DriverStore\FileRepository\e2xw10x64.inf_amd64_ad05f098c0c2086b\e2xw10x64.inf]
2017-02-01 16:02:20, Info                         GetModelSectionNameEx:Using section name [Rivet.NTamd64.6.3]
2017-02-01 16:02:20, Info                  IBS    AddDeviceIDsToInjectedDriverNodeHelper:Model section name is [Rivet.NTamd64.6.3]
2017-02-01 16:02:20, Info                  IBS    GatherDeviceIDsInDriverPackage:Successfully gathered device ID's from [X:\windows\System32\DriverStore\FileRepository\e2xw10x64.inf_amd64_ad05f098c0c2086b\e2xw10x64.inf]
2017-02-01 16:02:20, Info                  IBS    EnumOnlineDriverStoreForInjectedDriverPackages:Enumerated online driver store. Return code is [0x0]
2017-02-01 16:02:20, Info       [0x070035] DIAG   CallBack_DiagnosticDataGeneration: Called with notification for Initialization
2017-02-01 16:02:20, Info       [0x07003b] DIAG   CallBack_DiagnosticDataGeneration: Starting Timer as we are starting new phase
2017-02-01 16:02:20, Info       [0x06019f] IBS    CallBack_ParseCommandLine:Publishing command line option [/wds]
2017-02-01 16:02:20, Info       [0x06019f] IBS    CallBack_ParseCommandLine:Publishing command line option [/wdsdiscover]
2017-02-01 16:02:20, Info       [0x06019f] IBS    CallBack_ParseCommandLine:Publishing command line option [/WdsServer:REDACTED.SERVER.SERVER]
2017-02-01 16:02:20, Info       [0x0b0022] WDS    StartNetworking: Trying to start networking.
2017-02-01 16:02:20, Info                  WDS    Network service dhcp not running or could not be queried: c83c1980 1 1
2017-02-01 16:02:20, Info                  WDS    Network service lmhosts not running or could not be queried: c83c2460 1 1
2017-02-01 16:02:20, Info                  WDS    Network service lanmanworkstation not running or could not be queried: c83c2460 1 1
2017-02-01 16:02:20, Info                  WDS    Network service bfe not running or could not be queried: c83c1d40 1 1
2017-02-01 16:02:20, Info                  WDS    Network service ikeext not running or could not be queried: c83c22e0 1 1
2017-02-01 16:02:20, Info                  WDS    Network service mpssvc not running or could not be queried: c83c1e00 1 1
2017-02-01 16:02:20, Info                  WDS    Installing device root\kdnic X:\windows\INF\kdnic.inf succeeded
2017-02-01 16:02:25, Info                  WDS    Installing device pci\ven_8086&dev_15b8 X:\windows\INF\oem0.inf succeeded
2017-02-01 16:02:25, Info                  WDS    No computer name specified, generating a random name.
2017-02-01 16:02:25, Info                  WDS    Renaming computer to MININT-7Q0ETB3.
2017-02-01 16:02:25, Info                  WDS    Waiting on the profiling mutex handle
2017-02-01 16:02:25, Info                  WDS    Acquired profiling mutex
2017-02-01 16:02:25, Info                  WDS    Service winmgmt disable: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Service winmgmt stop: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Service winmgmt enable: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Released profiling mutex
2017-02-01 16:02:25, Info                  WDS    Global handle for profiling mutex is non-null
2017-02-01 16:02:25, Info                  WDS    Waiting on the profiling mutex handle
2017-02-01 16:02:25, Info                  WDS    Acquired profiling mutex
2017-02-01 16:02:25, Info                  WDS    Service dhcp start: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Service lmhosts start: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Service ikeext start: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Service mpssvc start: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Service NetBIOS start: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Service LanmanWorkstation start: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Service mrxsmb10 start: 0x00000000
2017-02-01 16:02:25, Info                  WDS    Released profiling mutex
2017-02-01 16:02:25, Info                  WDS    Spent 188ms installing network components
2017-02-01 16:02:25, Info                  WDS    Spent 218ms installing network drivers
2017-02-01 16:02:25, Info                  WDS    Installed 0 network driver(s)
2017-02-01 16:02:25, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:25, Info                  WDS    Friendly name:      [Ethernet]
2017-02-01 16:02:25, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:25, Info                  WDS    Type:               6; IF_TYPE_ETHERNET_CSMACD
2017-02-01 16:02:25, Info                  WDS    Flags:              453
2017-02-01 16:02:25, Info                  WDS    MTU:                1500
2017-02-01 16:02:25, Info                  WDS    UNICAST:
2017-02-01 16:02:25, Info                  WDS          [fe80::19df:93ae:1e38:75a9%2]
2017-02-01 16:02:25, Info                  WDS    ANYCAST:
2017-02-01 16:02:25, Info                  WDS    MULTICAST:
2017-02-01 16:02:25, Info                  WDS          [ff01::1%2]
2017-02-01 16:02:25, Info                  WDS          [ff02::1%2]
2017-02-01 16:02:25, Info                  WDS          [ff02::1:ff38:75a9%2]
2017-02-01 16:02:25, Info                  WDS          [224.0.0.1]
2017-02-01 16:02:25, Info                  WDS    DNS:
2017-02-01 16:02:25, Info                  WDS          [fec0:0:0:ffff::1%1]
2017-02-01 16:02:25, Info                  WDS          [fec0:0:0:ffff::2%1]
2017-02-01 16:02:25, Info                  WDS          [fec0:0:0:ffff::3%1]
2017-02-01 16:02:25, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:25, Info                  WDS    Friendly name:      [Loopback Pseudo-Interface 1]
2017-02-01 16:02:25, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:25, Info                  WDS    Type:               24; IF_TYPE_SOFTWARE_LOOPBACK
2017-02-01 16:02:25, Info                  WDS    Flags:              384
2017-02-01 16:02:25, Info                  WDS    MTU:                4294967295
2017-02-01 16:02:25, Info                  WDS    UNICAST:
2017-02-01 16:02:25, Info                  WDS          [::1]
2017-02-01 16:02:25, Info                  WDS          [127.0.0.1]
2017-02-01 16:02:25, Info                  WDS    ANYCAST:
2017-02-01 16:02:25, Info                  WDS    MULTICAST:
2017-02-01 16:02:25, Info                  WDS    DNS:
2017-02-01 16:02:26, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:26, Info                  WDS    Friendly name:      [Ethernet]
2017-02-01 16:02:26, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:26, Info                  WDS    Type:               6; IF_TYPE_ETHERNET_CSMACD
2017-02-01 16:02:26, Info                  WDS    Flags:              453
2017-02-01 16:02:26, Info                  WDS    MTU:                1500
2017-02-01 16:02:26, Info                  WDS    UNICAST:
2017-02-01 16:02:26, Info                  WDS          [fe80::19df:93ae:1e38:75a9%2]
2017-02-01 16:02:26, Info                  WDS    ANYCAST:
2017-02-01 16:02:26, Info                  WDS    MULTICAST:
2017-02-01 16:02:26, Info                  WDS          [ff01::1%2]
2017-02-01 16:02:26, Info                  WDS          [ff02::1%2]
2017-02-01 16:02:26, Info                  WDS          [ff02::1:ff38:75a9%2]
2017-02-01 16:02:26, Info                  WDS          [224.0.0.1]
2017-02-01 16:02:26, Info                  WDS    DNS:
2017-02-01 16:02:26, Info                  WDS          [fec0:0:0:ffff::1%1]
2017-02-01 16:02:26, Info                  WDS          [fec0:0:0:ffff::2%1]
2017-02-01 16:02:26, Info                  WDS          [fec0:0:0:ffff::3%1]
2017-02-01 16:02:26, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:26, Info                  WDS    Friendly name:      [Loopback Pseudo-Interface 1]
2017-02-01 16:02:26, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:26, Info                  WDS    Type:               24; IF_TYPE_SOFTWARE_LOOPBACK
2017-02-01 16:02:26, Info                  WDS    Flags:              384
2017-02-01 16:02:26, Info                  WDS    MTU:                4294967295
2017-02-01 16:02:26, Info                  WDS    UNICAST:
2017-02-01 16:02:26, Info                  WDS          [::1]
2017-02-01 16:02:26, Info                  WDS          [127.0.0.1]
2017-02-01 16:02:26, Info                  WDS    ANYCAST:
2017-02-01 16:02:26, Info                  WDS    MULTICAST:
2017-02-01 16:02:26, Info                  WDS    DNS:
2017-02-01 16:02:27, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:27, Info                  WDS    Friendly name:      [Ethernet]
2017-02-01 16:02:27, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:27, Info                  WDS    Type:               6; IF_TYPE_ETHERNET_CSMACD
2017-02-01 16:02:27, Info                  WDS    Flags:              453
2017-02-01 16:02:27, Info                  WDS    MTU:                1500
2017-02-01 16:02:27, Info                  WDS    UNICAST:
2017-02-01 16:02:27, Info                  WDS          [fe80::19df:93ae:1e38:75a9%2]
2017-02-01 16:02:27, Info                  WDS    ANYCAST:
2017-02-01 16:02:27, Info                  WDS    MULTICAST:
2017-02-01 16:02:27, Info                  WDS          [ff01::1%2]
2017-02-01 16:02:27, Info                  WDS          [ff02::1%2]
2017-02-01 16:02:27, Info                  WDS          [ff02::1:ff38:75a9%2]
2017-02-01 16:02:27, Info                  WDS          [224.0.0.1]
2017-02-01 16:02:27, Info                  WDS    DNS:
2017-02-01 16:02:27, Info                  WDS          [fec0:0:0:ffff::1%1]
2017-02-01 16:02:27, Info                  WDS          [fec0:0:0:ffff::2%1]
2017-02-01 16:02:27, Info                  WDS          [fec0:0:0:ffff::3%1]
2017-02-01 16:02:27, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:27, Info                  WDS    Friendly name:      [Loopback Pseudo-Interface 1]
2017-02-01 16:02:27, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:27, Info                  WDS    Type:               24; IF_TYPE_SOFTWARE_LOOPBACK
2017-02-01 16:02:27, Info                  WDS    Flags:              384
2017-02-01 16:02:27, Info                  WDS    MTU:                4294967295
2017-02-01 16:02:27, Info                  WDS    UNICAST:
2017-02-01 16:02:27, Info                  WDS          [::1]
2017-02-01 16:02:27, Info                  WDS          [127.0.0.1]
2017-02-01 16:02:27, Info                  WDS    ANYCAST:
2017-02-01 16:02:27, Info                  WDS    MULTICAST:
2017-02-01 16:02:27, Info                  WDS    DNS:
2017-02-01 16:02:28, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:28, Info                  WDS    Friendly name:      [Ethernet]
2017-02-01 16:02:28, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:28, Info                  WDS    Type:               6; IF_TYPE_ETHERNET_CSMACD
2017-02-01 16:02:28, Info                  WDS    Flags:              453
2017-02-01 16:02:28, Info                  WDS    MTU:                1500
2017-02-01 16:02:28, Info                  WDS    UNICAST:
2017-02-01 16:02:28, Info                  WDS          [fe80::19df:93ae:1e38:75a9%2]
2017-02-01 16:02:28, Info                  WDS    ANYCAST:
2017-02-01 16:02:28, Info                  WDS    MULTICAST:
2017-02-01 16:02:28, Info                  WDS          [ff01::1%2]
2017-02-01 16:02:28, Info                  WDS          [ff02::1%2]
2017-02-01 16:02:28, Info                  WDS          [ff02::1:ff38:75a9%2]
2017-02-01 16:02:28, Info                  WDS          [224.0.0.1]
2017-02-01 16:02:28, Info                  WDS    DNS:
2017-02-01 16:02:28, Info                  WDS          [fec0:0:0:ffff::1%1]
2017-02-01 16:02:28, Info                  WDS          [fec0:0:0:ffff::2%1]
2017-02-01 16:02:28, Info                  WDS          [fec0:0:0:ffff::3%1]
2017-02-01 16:02:28, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:28, Info                  WDS    Friendly name:      [Loopback Pseudo-Interface 1]
2017-02-01 16:02:28, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:28, Info                  WDS    Type:               24; IF_TYPE_SOFTWARE_LOOPBACK
2017-02-01 16:02:28, Info                  WDS    Flags:              384
2017-02-01 16:02:28, Info                  WDS    MTU:                4294967295
2017-02-01 16:02:28, Info                  WDS    UNICAST:
2017-02-01 16:02:28, Info                  WDS          [::1]
2017-02-01 16:02:28, Info                  WDS          [127.0.0.1]
2017-02-01 16:02:28, Info                  WDS    ANYCAST:
2017-02-01 16:02:28, Info                  WDS    MULTICAST:
2017-02-01 16:02:28, Info                  WDS    DNS:
2017-02-01 16:02:29, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:29, Info                  WDS    Friendly name:      [Ethernet]
2017-02-01 16:02:29, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:29, Info                  WDS    Type:               6; IF_TYPE_ETHERNET_CSMACD
2017-02-01 16:02:29, Info                  WDS    Flags:              453
2017-02-01 16:02:29, Info                  WDS    MTU:                1500
2017-02-01 16:02:29, Info                  WDS    UNICAST:
2017-02-01 16:02:29, Info                  WDS          [fe80::19df:93ae:1e38:75a9%2]
2017-02-01 16:02:29, Info                  WDS    ANYCAST:
2017-02-01 16:02:29, Info                  WDS    MULTICAST:
2017-02-01 16:02:29, Info                  WDS          [ff01::1%2]
2017-02-01 16:02:29, Info                  WDS          [ff02::1%2]
2017-02-01 16:02:29, Info                  WDS          [ff02::1:ff38:75a9%2]
2017-02-01 16:02:29, Info                  WDS          [224.0.0.1]
2017-02-01 16:02:29, Info                  WDS    DNS:
2017-02-01 16:02:29, Info                  WDS          [fec0:0:0:ffff::1%1]
2017-02-01 16:02:29, Info                  WDS          [fec0:0:0:ffff::2%1]
2017-02-01 16:02:29, Info                  WDS          [fec0:0:0:ffff::3%1]
2017-02-01 16:02:29, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:29, Info                  WDS    Friendly name:      [Loopback Pseudo-Interface 1]
2017-02-01 16:02:29, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:29, Info                  WDS    Type:               24; IF_TYPE_SOFTWARE_LOOPBACK
2017-02-01 16:02:29, Info                  WDS    Flags:              384
2017-02-01 16:02:29, Info                  WDS    MTU:                4294967295
2017-02-01 16:02:29, Info                  WDS    UNICAST:
2017-02-01 16:02:29, Info                  WDS          [::1]
2017-02-01 16:02:29, Info                  WDS          [127.0.0.1]
2017-02-01 16:02:29, Info                  WDS    ANYCAST:
2017-02-01 16:02:29, Info                  WDS    MULTICAST:
2017-02-01 16:02:29, Info                  WDS    DNS:
2017-02-01 16:02:30, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:30, Info                  WDS    Friendly name:      [Ethernet]
2017-02-01 16:02:30, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:30, Info                  WDS    Type:               6; IF_TYPE_ETHERNET_CSMACD
2017-02-01 16:02:30, Info                  WDS    Flags:              453
2017-02-01 16:02:30, Info                  WDS    MTU:                1500
2017-02-01 16:02:30, Info                  WDS    UNICAST:
2017-02-01 16:02:30, Info                  WDS          [fe80::19df:93ae:1e38:75a9%2]
2017-02-01 16:02:30, Info                  WDS    ANYCAST:
2017-02-01 16:02:30, Info                  WDS    MULTICAST:
2017-02-01 16:02:30, Info                  WDS          [ff01::1%2]
2017-02-01 16:02:30, Info                  WDS          [ff02::1%2]
2017-02-01 16:02:30, Info                  WDS          [ff02::1:ff38:75a9%2]
2017-02-01 16:02:30, Info                  WDS          [224.0.0.1]
2017-02-01 16:02:30, Info                  WDS    DNS:
2017-02-01 16:02:30, Info                  WDS          [fec0:0:0:ffff::1%1]
2017-02-01 16:02:30, Info                  WDS          [fec0:0:0:ffff::2%1]
2017-02-01 16:02:30, Info                  WDS          [fec0:0:0:ffff::3%1]
2017-02-01 16:02:30, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:30, Info                  WDS    Friendly name:      [Loopback Pseudo-Interface 1]
2017-02-01 16:02:30, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:30, Info                  WDS    Type:               24; IF_TYPE_SOFTWARE_LOOPBACK
2017-02-01 16:02:30, Info                  WDS    Flags:              384
2017-02-01 16:02:30, Info                  WDS    MTU:                4294967295
2017-02-01 16:02:30, Info                  WDS    UNICAST:
2017-02-01 16:02:30, Info                  WDS          [::1]
2017-02-01 16:02:30, Info                  WDS          [127.0.0.1]
2017-02-01 16:02:30, Info                  WDS    ANYCAST:
2017-02-01 16:02:30, Info                  WDS    MULTICAST:
2017-02-01 16:02:30, Info                  WDS    DNS:
2017-02-01 16:02:31, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:31, Info                  WDS    Friendly name:      [Ethernet]
2017-02-01 16:02:31, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:31, Info                  WDS    Type:               6; IF_TYPE_ETHERNET_CSMACD
2017-02-01 16:02:31, Info                  WDS    Flags:              453
2017-02-01 16:02:31, Info                  WDS    MTU:                1500
2017-02-01 16:02:31, Info                  WDS    UNICAST:
2017-02-01 16:02:31, Info                  WDS          [fe80::19df:93ae:1e38:75a9%2]
2017-02-01 16:02:31, Info                  WDS          [192.168.3.23]
2017-02-01 16:02:31, Info                  WDS          [169.254.117.169]
2017-02-01 16:02:31, Info                  WDS    ANYCAST:
2017-02-01 16:02:31, Info                  WDS    MULTICAST:
2017-02-01 16:02:31, Info                  WDS          [ff01::1%2]
2017-02-01 16:02:31, Info                  WDS          [ff02::1%2]
2017-02-01 16:02:31, Info                  WDS          [ff02::1:ff38:75a9%2]
2017-02-01 16:02:31, Info                  WDS          [224.0.0.1]
2017-02-01 16:02:31, Info                  WDS    DNS:
2017-02-01 16:02:31, Info                  WDS          [192.168.0.4]
2017-02-01 16:02:31, Info                  WDS          [192.168.0.1]
2017-02-01 16:02:31, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:31, Info                  WDS    Friendly name:      [Loopback Pseudo-Interface 1]
2017-02-01 16:02:31, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:31, Info                  WDS    Type:               24; IF_TYPE_SOFTWARE_LOOPBACK
2017-02-01 16:02:31, Info                  WDS    Flags:              384
2017-02-01 16:02:31, Info                  WDS    MTU:                4294967295
2017-02-01 16:02:31, Info                  WDS    UNICAST:
2017-02-01 16:02:31, Info                  WDS          [::1]
2017-02-01 16:02:31, Info                  WDS          [127.0.0.1]
2017-02-01 16:02:31, Info                  WDS    ANYCAST:
2017-02-01 16:02:31, Info                  WDS    MULTICAST:
2017-02-01 16:02:31, Info                  WDS    DNS:
2017-02-01 16:02:31, Info                  WDS    QueryAdapterStatus: found operational adapter with DHCP address assigned.
2017-02-01 16:02:31, Info                  WDS    Spent 6063ms confirming network initialization; status 0x00000000
2017-02-01 16:02:32, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:32, Info                  WDS    Friendly name:      [Ethernet]
2017-02-01 16:02:32, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:32, Info                  WDS    Type:               6; IF_TYPE_ETHERNET_CSMACD
2017-02-01 16:02:32, Info                  WDS    Flags:              453
2017-02-01 16:02:32, Info                  WDS    MTU:                1500
2017-02-01 16:02:32, Info                  WDS    UNICAST:
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Info                  WDS    ANYCAST:
2017-02-01 16:02:32, Info                  WDS    MULTICAST:
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Info                  WDS    DNS:
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Info                  WDS    // Checking Adapter Status /////////////////////////////////////
2017-02-01 16:02:32, Info                  WDS    Friendly name:      [Loopback Pseudo-Interface 1]
2017-02-01 16:02:32, Info                  WDS    Operational Status: 1; IfOperStatusUp
2017-02-01 16:02:32, Info                  WDS    Type:               24; IF_TYPE_SOFTWARE_LOOPBACK
2017-02-01 16:02:32, Info                  WDS    Flags:              384
2017-02-01 16:02:32, Info                  WDS    MTU:                4294967295
2017-02-01 16:02:32, Info                  WDS    UNICAST:
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Error      [0x0b003a] WDS          <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2017-02-01 16:02:32, Info                  WDS    ANYCAST:
2017-02-01 16:02:32, Info                  WDS    MULTICAST:
2017-02-01 16:02:32, Info                  WDS    DNS:
2017-02-01 16:02:32, Info                  WDS    GetNetworkingInfo: WpeNetworkStatus returned [0x806]. Flags set: WPE_NETWORK_ADAPTER_OPERATIONAL WPE_NETWORK_DHCP_ENABLED WPE_NETWORK_ADAPTER_HAS_DHCP_ADDRESS
2017-02-01 16:02:32, Info       [0x0b0023] WDS    StartNetworking: Networking successfully started.
2017-02-01 16:02:32, Error      [0x0b002f] WDS    CallBack_WdsClient_DetectWdsMode: Failed to discover Wds Server, Error [10049].
2017-02-01 16:02:32, Error      [0x0b0006] WDS    CallBack_WdsClient_DetectWdsMode: No PXE boot information is present in registry.
2017-02-01 16:02:32, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: There was a problem initializing WDS Mode.]

From that the only issue I can see is that it receives both a proper IPv4 address as well as an APIPA address.

Any ideas?

↧

Mounting Image using DISM

February 2, 2017, 7:34 am
$
0
0

I am trying to create a WinPE image with HyperV integration drivers built in....

I'm having issues in trying to mount my winpe image to add the drivers.

This is the command I am using:

Y:\Working\Windows 2012r2 Standard\sources>"Y:\Program Files (x86)\Windows Kits\

10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /mount-im

age /imagefile:boot.wim /index:1 /mountdir:Y:\mount

 

or

 

"Y:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /mount-image /imagefile:"Y:\Working\Windows 2012r2 Standard\sources\boot.wim" /index:1 /mountdir:Y:\mount

No matter what i do, where i put quotes, check the file exisits, permissions etc etc I always get the following error

"Error: 3

 

The system cannot find the path specified."

I'm banging my head against a wall - i don't know if its something obvious or i'm doing something totally wrong. Has anyone else come across this issue or know what the problem is with my command?

Thanks,

↧
↧

Finding .inf driver files to add to .wim files

October 12, 2011, 10:45 am
$
0
0

I'm trying to add a driver to a .wim file using ImageX and I realized that you can only add .inf files. How are you supposed to get a Dell network driver that is only provided in a .exe file to convert to .inf?

↧

SQL 2016 not showing Mapped Raw Drive

February 3, 2017, 7:15 am
$
0
0

Hello,

I have SQL 2008 Management studio and when open i can see the mapped raw drive but on SQL Management studio of 2016 it does not show.

Can someone guide me on this one.


↧

MDT / WDS Multicast

February 3, 2017, 9:45 am
$
0
0

I've been trying to get multicast deployment working in our environment. I notice when I begin the MDT task sequence, the client attempts multicast transfer but always kicks back to unicast. When I run the task sequence on a VM on the same Hyper V host as the MDT server, multicast transfer works just as it should.

We use a Cisco Meraki MX100 for routing on this portion of our network. According to Meraki documentation, "MX Security Appliances will forward IGMP traffic for a single broadcast domain. It does not forward multicast traffic upstream, between VLANs, or over a VPN." So it looks like multicasting across VLANs is a no-go. But I can't get multicast even to work when both the MDT/WDS server and host are on the same VLAN. The ONLY time multicast works is when the host is a VM on the same Hypervisor host.

For reference, I have configured our MDT/WDS server according to the steps defined here: https://keithga.wordpress.com/2014/04/23/multicasting-with-mdt/

Does anyone have any insight on why this might be, or just how the IGMP multicast process works as far as MDT is concerned?

↧
Search

After running sysprep vm reboots with other admin password

December 14, 2016, 1:31 pm
$
0
0

Hello all

After running sysprep on a cloned vm (vmware) it reboots with other admin password, so I cant log on as administrator.

Windows 2008 R2 SP1 updated

Thanks,

De Lucca

↧
↧

Planning to add Windows 10 (1607) image to WDS (Windows Server 2008 R2)

February 6, 2017, 9:46 am
$
0
0

Hey friends

I'm planning to add Windows 10 (1607) image to WDS. I also have a plan to capture 5 Images Department wise.

But when microsoft releases new versions in future( for Eg: Windows creator update, and further another version of Windows 10) I'm having only 1607 based capture images in our WDS for new deployments. Also once i deploy it (1607) i need to install next versions from WSUS.

In order to skip the new update installation from WSUS is there any 3rd party tools or microsoft tools to perform the below Scenario. 

I'm having an idea as below:-

Adding a common Windows 10 (1607) Image which will be used for deployment.

Then I create groups (eg: Development, Finance, HR, Customer support etc.) and add applications to those particular groups which the teams are using ( Eg:- adding Visual Studio in Development, Tally in finance group Likewise). 

Once a Pxe boot is triggered it first need to go through normal Windows installation steps and before starting installation it should ask for which group apps should it install. Once the installation is complete the machine should be installed with Windows 1607 Image and the selected group apps.

Later on when Microsoft releases a new Version of Windows 10 I just need to replace the os with the old os version(1607). On further deployment it will deploy the latest version of Windows and the apps from the group, Thus skipping the Version upgradation after the initial deployment. 

Any idea :) 

A Windows Lover :)

↧

Increase PageFile using commandline without reboot

October 27, 2016, 10:15 pm
$
0
0

Hi,

I need to increase the pagefile size on a system using a command line on the fly. There are 2 options using which I can set it:

1. wmic pagefileset where name="C:\pagefile.sys" set InitialSize=1450,MaximumSize=1450

OR
2. REG ADD "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management" /v PagingFiles /t REG_MULTI_SZ /d "D:\pagefile.sys <value> <value>" /f

Both the above mentioned methods work and show the changes in the registry. However, it does not change the actual size of the pagefile on the disk until a restart. Nor does it show the updated value when checking using "Get-CimInstance Win32_PageFileUsage | fl *" command.

Ideally, an increase in the page file size from the GUI does not need a reboot, when click on "Set" option.

Is there a way to refresh the pagefile size after it has been increased in the registry, without rebooting the system? Or is there a way to set the page file size at startup which can be automated.

Any help will be highly appreciated!

↧

Update Media Content issue

June 10, 2018, 7:21 pm
$
0
0

I attempted to update media content to create an ISO file with Microsoft Deployment toolkit version 8450.  I copied the whole process with error towards the end below.  Wanted to see have anybody else encoutered any similar issues in the past and if so, would appreciate recommendations and feedback.

Starting MDT Media Update

Opened the media deployment share.

Folders to be copied to the media deployment share: 6

Copied: DS001:\Applications

Copied: DS001:\Operating Systems

Copied: DS001:\Out-of-Box Drivers

Copied: DS001:\Packages

Copied: DS001:\Task Sequences

Copied: DS001:\Selection Profiles

Copied: DS001:\Applications with Replace option

Copied: DS001:\Operating Systems with Replace option

Copied: DS001:\Out-of-Box Drivers with Replace option

Copied: DS001:\Packages with Replace option

Copied: DS001:\Task Sequences with Replace option

Copied: DS001:\Selection Profiles with Replace option

Copied standard folders.

Boot images updated.

System.Management.Automation.CmdletInvocationException: Access to the path is denied. ---> System.UnauthorizedAccessException: Access to the path is denied.

at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

at System.IO.File.InternalMove(String sourceFileName, String destFileName, Boolean checkHost)

at Microsoft.BDD.Core.DirectoryUtility.CopyFile(DEInfo sourceFile, DEInfo destFile, String destFullName)

at Microsoft.BDD.Core.DirectoryUtility.BeginCopyFile(String theSourceFile, String theDestFile)

at Microsoft.BDD.PSSnapIn.PEManager.CopyBootFiles(String dest, String architecture)

at Microsoft.BDD.PSSnapIn.GenerateMDTMedia.ProcessRecord()

at System.Management.Automation.CommandProcessor.ProcessRecord()

--- End of inner exception stack trace ---

at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)

at Microsoft.BDD.Wizards.GenerateMediaProgress.WizardProcessing()

at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()


↧

WDS installs default boot image and not my custom imaged in the installgroup1

June 18, 2018, 10:14 am
$
0
0

WDS installs default boot image and not my custom imaged in the installgroup1

I am deploying windows 10 to my endpoints, I have custom images that I have captured into installgroup1.

when I boot a endpoint and select from these custom images, everything looks to work correctly. image installs and the machine boots up and it the default boot image not my image?

HELP

↧
↧

Error deployment

June 17, 2018, 11:52 pm
$
0
0

Hello,

Someone who can help me?

In a test environment I have prepared a whole deployment and successfully executed it. After this was successful on the practice client, I removed everything.

Now that I execute the real deployment on the server, he gives the following error with the execution. Very strange because I have checked everywhere to the deployment share to adjust it correctly. But in vain, everything is well set. Someone who can help me?

Error: A connection to the deployment share (\\Test\DeploymentShare$) could not be made. Can not reach DeployRoot. Possible cause: Network routing error or Network Configuration error. 






↧

DHCP in roles and features fails to install

June 8, 2018, 4:36 pm
$
0
0

Installation of one or more roles, role services, or feature failed. The reference assembly could not be found error: 0x80073701.

DHCP Server

Remote Server Administrative Tools

Role Administrative Tools

DHCP Server Tools

Brand new server 2016 Standard installed yesterday, no anti-virus or Firewall in place yet. Patched and updated. 

Thanks 

↧
Search

WDS - captured images won't add

February 5, 2018, 11:31 am
$
0
0

I have captured a Windows 10 sysprep'ed image using two different methods:

1. pxe boot with a capture image on the WDS server: using this method, I'm able to save the image locally to a usb drive, but the option to connect to the wds server never works.  The logon screen will never connect.

2. boot to WinPE and capture the image with DISM to a usb drive.

For both methods, when I attempt to add the image to the server under "Install images", I get an error that says "The Data is Invalid".

I'm having trouble finding where the problem may be.  Any direction for troubleshooting this would be greatly appreciated!

↧

wds pxe boot - tftp download loop - 4 times F12

April 1, 2014, 7:49 am
$
0
0 

Hi
I just set up a new wds server 2012

When trying to pxe boot a client, it loops like this:

Downloaded WDSNBP from...
WDSNBP started using DHCP referral.
Contacting server...
Architecture...
Contacting server...

TFTP download: boot\x86\wdsnbp.com
Downloaded WDSNBP from ...

Architecture...
Contacting Server...

TFTP download: boot\x86\wdsnbp.com

Then it goes on 4 times in a row:

"TFTP Download: Boot\x86\wdsnbp.com"
With Option "Require the user to press the F12 key..." enabled,
I have to press F12 4 times, which is 3 times too many.
After the x-th download of wdsnbp.com the client continues the boot process
normally and the rest works fine.

Any help is greatly appreciated.

Michael








↧
↧

WDS and PCI\VEN error

June 21, 2018, 9:22 am
$
0
0

Hello,

I'm running into an error I've never had before.

The following networking device did not have a driver installed. PCI\VEN_8086&DEV_15BB&SUBSYS_085A1029&REV_10

I built an image off of a Dell OptiPlex 7060, and am trying to deploy it to the rest of the 7060s. 

A month ago I did the same exact process with OptiPlex 7050s, and ran into no errors.

Looking for any advice,

Thanks

↧

PkgMgr.exe is Deprecated

April 27, 2017, 7:52 am
$
0
0

Installing a Media Player 11 It showing Error 

Note: PkgMgr.exe has been deprecated. Please update your scripts to DISM.exe to install, uninstall, configure, and update features and packages for windows.

see http://go.microsoft.com/fwlink/?LinkID=195329 for more information operation failed with 0x80070307



I also tried this

(Open an Administrator command prompt window by,

  1. Press Windows logo + X keys on the keyboard and select Command Prompt (Admin) option.
  2. Click on Yes and continue. Provide administrator password if prompted.
  3. Check if it says Administrator: Command Prompt at the top of the command prompt window.

 

Step 2: Type the following commands in the CMD Prompt:

 

            dism /online /cleanup-image /restorehealth

            sfc /scannow

 

Step 3: Close the command window and check if the issue is resolved.)

After that tried to install WMP11 but it show same error 

Please help me out


↧

WDS on Win2012R2 - unattended file with Win 10 1709 - error in answer file using %machinename%

January 9, 2018, 12:37 am
$
0
0

I've been running WDS for a year or so now, using the same kind of answer file for the different Win10, created using Windows SIM

With Win10 1709 I'm now getting errors when deploying images. and found that it's the %MACHINENAME% value in

specialize -> amd64_Microsoft-Windows-Shell-Setup_neutral --> ComputerName

that causes the problem.

I couldn't find if it has been removed/replaced or what.

getting the following errors in setuperr.log on client

Error [0x0b003a] WDS <GetNameInfo failed, status 0x8007276d>[gle=0x0000276d]

apologies if this is the wrong forum


↧
Viewing all 2818 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>