I have a physical server (IBM HS22) with 2 NICs.  I freshly installed Windows Server 2016 with AD Directory Services, DNS, DFS, and DHCP server roles.  It's up-to-date with Windows Updates.

The two NICs are teamed using lbfoadmin as switch independent, dynamic, and no standby.

Problem

When the server reboots, many unexpected event log entries are recorded.  All the errors are related to networking problems, or lack of networking.

Examples: DNS server could not bind to IP address, ADWS cannot service directory, DFS Rootxxx failed during initialization, ntpclient cannot find peer, Intersite Messaging failed, etc.

I receive 20-40 errors on each boot.

Notes

• If I break the team and just use one NIC (it doesn't matter which one), these errors do not occur
• If the team contains only one NIC, and I disable the other NIC, the problem still exists
• Changing other team settings such as standby adapter and type doesn't help
• This problem does not appear on similar hardware using 2012 R2
• Side note:  The services seem to auto-recover because all the server roles seem to be working

I suspect the teaming layer is adding a delay to networking availability and is causing the services to fail because the network is not ready.

I really want the NICs teamed for fault-tolerance.  Any ideas on how I can fix/workaround this problem?

Hi,

I am trying to use the Volume Activation Management Tool to distribute Visual Studio licenses but VAMT is not able to see any existing installs of Visual Studio (either ones that are already licensed nor ones that are awaiting a license) it is however able to see the Windows OS installations and the Microsoft Office installations just fine. Does anyone have any suggestions on how to get this to work?

Thank You

WDS - Server 2008 r2

Trying to install windows 10 and it fails saying "Windows installation encountered an unexpected error. Verify that the installation sources are accessible and restart the installation. Refer screenshot and logs below. PLease let me know the cause of the problem.

Below is the logs from c:\windows\logs\cbs

2019-07-09 17:11:53, Info                  CBS    Starting TrustedInstaller initialization.
2019-07-09 17:11:53, Info                  CBS    Loaded Servicing Stack v6.1.7601.23505 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.23505_none_681aa442f6fed7f0\cbscore.dll
2019-07-09 17:11:54, Info                  CSI    00000001@2019/7/9:13:11:54.817 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fed60feb5d @0x7fedd7e9b6d @0x7fedd7b358f @0xff9ce97c @0xff9cd799 @0xff9cdb2f)
2019-07-09 17:11:54, Info                  CBS    Could not load SrClient DLL from path: SrClient.dll.  Continuing without system restore points.
2019-07-09 17:11:54, Info                  CSI    00000002@2019/7/9:13:11:54.927 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fed60feb5d @0x7fedd836ade @0x7fedd802984 @0x7fedd7b3665 @0xff9ce97c @0xff9cd799)
2019-07-09 17:11:54, Info                  CSI    00000003@2019/7/9:13:11:54.974 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fed60feb5d @0x7fef1b98728 @0x7fef1b98856 @0xff9ce474 @0xff9cd7de @0xff9cdb2f)
2019-07-09 17:11:55, Info                  CBS    Ending TrustedInstaller initialization.
2019-07-09 17:11:55, Info                  CBS    Starting the TrustedInstaller main loop.
2019-07-09 17:11:55, Info                  CBS    TrustedInstaller service starts successfully.
2019-07-09 17:11:55, Info                  CBS    SQM: Initializing online with Windows opt-in: False
2019-07-09 17:11:55, Info                  CBS    SQM: Cleaning up report files older than 10 days.
2019-07-09 17:11:55, Info                  CBS    SQM: Requesting upload of all unsent reports.
2019-07-09 17:11:55, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2019-07-09 17:11:55, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2019-07-09 17:11:55, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2019-07-09 17:11:55, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
2019-07-09 17:11:55, Info                  CBS    No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
2019-07-09 17:11:55, Info                  CBS    NonStart: Checking to ensure startup processing was not required.
2019-07-09 17:11:55, Info                  CSI    00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x17bfe10
2019-07-09 17:11:55, Info                  CSI    00000005 Creating NT transaction (seq 1), objectname [6]"(null)"
2019-07-09 17:11:55, Info                  CSI    00000006 Created NT transaction (seq 1) result 0x00000000, handle @0x1e0
2019-07-09 17:11:55, Info                  CSI    00000007@2019/7/9:13:11:55.052 CSI perf trace:
CSIPERF:TXCOMMIT;583
2019-07-09 17:11:55, Info                  CBS    NonStart: Success, startup processing not required as expected.
2019-07-09 17:11:55, Info                  CBS    Startup processing thread terminated normally
2019-07-09 17:11:55, Info                  CSI    00000008 CSI Store 4526496 (0x00000000004511a0) initialized
2019-07-09 17:11:55, Info                  CBS    Session: 30750295_3783326453 initialized by client RMT.
2019-07-09 17:11:55, Info                  CBS    Session: 30750295_3783326453 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-07-09 17:14:04, Info                  CBS    Session: 30750296_779178716 initialized by client RMT.
2019-07-09 17:14:04, Info                  CBS    Session: 30750296_779178716 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-07-09 17:16:12, Info                  CBS    Session: 30750296_2067072718 initialized by client RMT.
2019-07-09 17:16:12, Info                  CBS    Session: 30750296_2067072718 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-07-09 17:18:22, Info                  CBS    Session: 30750296_3358200838 initialized by client RMT.
2019-07-09 17:18:22, Info                  CBS    Session: 30750296_3358200838 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-07-09 17:20:31, Info                  CBS    Session: 30750297_353096046 initialized by client RMT.
2019-07-09 17:20:31, Info                  CBS    Session: 30750297_353096046 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-07-09 17:22:38, Info                  CBS    Session: 30750297_1628675797 initialized by client RMT.
2019-07-09 17:22:38, Info                  CBS    Session: 30750297_1628675797 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-07-09 17:32:38, Info                  CBS    Reboot mark refs incremented to: 1
2019-07-09 17:32:38, Info                  CBS    Scavenge: Starts
2019-07-09 17:32:38, Info                  CSI    00000009@2019/7/9:13:32:38.628 CSI Transaction @0x4438f0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"

2019-07-09 17:32:38, Info                  CBS    Scavenge: Begin CSI Store
2019-07-09 17:32:38, Info                  CSI    0000000a Performing 1 operations; 1 are not lock/unlock and follow:
  Scavenge (8): flags: 00000017
2019-07-09 17:32:38, Info                  CSI    0000000b Store coherency cookie matches last scavenge cookie, skipping scavenge.
2019-07-09 17:32:38, Info                  CSI    0000000c ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=7
2019-07-09 17:32:38, Info                  CSI    0000000d Creating NT transaction (seq 2), objectname [6]"(null)"
2019-07-09 17:32:38, Info                  CSI    0000000e Created NT transaction (seq 2) result 0x00000000, handle @0x220
2019-07-09 17:32:38, Info                  CSI    0000000f@2019/7/9:13:32:38.925 CSI perf trace:
CSIPERF:TXCOMMIT;55105
2019-07-09 17:32:38, Info                  CBS    Scavenge: Completed, dis
2019-07-09 17:32:38, Info                  CSI    00000010@2019/7/9:13:32:38.925 CSI Transaction @0x4438f0 destroyed
2019-07-09 17:32:38, Info                  CBS    Reboot mark refs: 0
2019-07-09 17:32:38, Info                  CBS    Idle processing thread terminated normally
2019-07-09 17:32:38, Info                  CBS    Ending the TrustedInstaller main loop.
2019-07-09 17:32:38, Info                  CBS    Starting TrustedInstaller finalization.
2019-07-09 17:32:39, Info                  CBS    Ending TrustedInstaller finalization.

rubeen

Hi,

I just installed WDS on Windows server 2008 R2. I have the DHCP server and WDS on the same system. I have configured WDS and added the x64 boot and install images. I am trying to network boot an x64 efi based client. The client successfully obtains a DHCP address. Now, in the network trace, I observe that the first file to be downloaded is always the wdsmgfw.efi file.

1. Initially, I added the Windows 2008 SP2 boot image. The boot\x64\ folder did not have the wdsmgfw.efi file and TFTP request would fail.

2. I added the Windows 2008 R2 boot image. This created the wdsmgfw.efi file in the boot\x64\ folder. Now the TFTP download succeeds. Then I end up with a black screen.

I made the"bootmgfw.efi" the default boot program for x64 systems. Even then, the TFTP request is always for "wdsmgfw.efi". What is the wdsmgfw.efi file for? Is this being requested by the client? I got a feeling that if the bootmgfw.efi file is downloaded, I will be able to install and boot properly.

Do I need to set any option? Any help will be appreciated.

Thanks!

KB4503267 is meant to fix problems with TFTP downloads with Variable Window = true, but over here it iscausing those problems, for downloads with Variable Window = false.

This is on Server 2016.

We are using in-house designed ARM CPU devices booting from the network. They are built up around a Digi ConnectCore 7U module running an image built on Digi's own Net+OS. The boot loader is a minimal Net+OS build that just downloads a larger image to RAM and starts it, by rebooting to that RAM image.

We have been using these devices with different TFTP servers for more than 10 years, and they have always worked fine.

Now they suddenly start booting flaky (guesstimate: about 1 boot attempt in 3 to 5 fails) and I have dozens of these in event log:

Applications and Services Logs \ Microsoft \ Windows \ Deployment-Services-Diagnostics \ Admin

Event ID = 4101

The Following Client failed TFTP Download: 

Client IP: 10.11.19.150
Filename: image.bin
ErrorCode: 644
File Size: 1002330
Client Port: 18000
Server Port: 59082
Variable Window: false

Before the update was installed I had on average less than one of these events per month, now I have dozens per day.

Dear Ladies and Gentlemen,

we have been using setupcomplete.cmd in the "sources\$OEM$\$$\setup\scripts" folder of the Installation DVD to add unattended content to a Vista/W2K8 installation after setup completed. We now would like to move to WDS as quickly as possible without rewriting all our scripts. Is it somehow possible to use setupcomplete.cmd with a Vista/W2K8 installation from WDS ? If yes, into which folder do I have to copy the cmd on the WDS server so it gets used by Vista setup ?

Thanks a lot for your help !

Alex

Hi,

I am doing unattended deployment with Windows Deployment Service. I want to put the setupcomplete.cmd in the $OEM/$$/Setup/Script/, so I can install my programs after the windows installation.

Is this the way I should create the $OEM$ folder ?

\RemoteInstall\Images\Windows 7\install-(5)\$OEM$\$$\Setup\Scripts

Hello,

The WDS server is a freshly installed Win 2019 server.

I am trying to import install images with PowerShell.

$ImagePath = 'D:\Sources\2019\install.wim'
$ImageName = (Get-WindowsImage -ImagePath $ImagePath -Index 4).ImageName
Import-WdsInstallImage -ImageGroup 'Win2019' -ImageName $ImageName -Path $ImagePath -Multicast

However I get the following error:

Import-WdsInstallImage : An install image could not be found in the image file.
At line:3 char:1+ Import-WdsInstallImage -ImageGroup 'Win2019' -ImageName $ImageName -P ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (MSFT_WdsInstallImage:root/cimv2/MSFT_WdsInstallImage) [Import-WdsInstallImage], CimException+ FullyQualifiedErrorId : 0xC111010E,Import-WdsInstallImage

The image file is NOT read-only.

And with the console it works fine.

I also installed the latest system rollup, but the behavior is the same.

Does anybody see what's wrong with my code?

Hi!

Basically first thing in the morning 8-9am and again around 12pm-1pm one of our sites cannot pxe boot. It just sits there for hours or days, with no response. If the tech changes the  BIOS time either 1hr ahead or behind, then it works. All other times during the day, pxe is working as expected and no BIOS time change is required.

Both the Pxe server and the BIOS are on Central Time

Any idea?

Hello

I have a Windows Deployment Server hosting a couple of images.  I have prestaged my Surface Tablets so that that they auto-load the correct image completely unattended.

I have another image with some utilities on it that I would like to manually deploy on any given Tablet on any given day.  

Is there a way to "interrupt" the automated installation of the prestaged image and present me with the image menu I would see on a non-prestaged device?  

Thanks
Jason

Hi All,

I have a standalone (not AD connected) WDS 2012 that functions perfectly to a point. I can capture images, deploy them, add drivers, show multiple boot & install images.

My issue is that I can't get my OOBE unattend file to apply with a fresh x64 Win7 Pro wim file (not installed and sysprep'd fresh from the DVD); however the WDS unattend file does apply and sets up my partition preferences, image location and credentials to access it. I know there are two files that setup different sections of automation and that they are applyed in two different parts of WDS (server properties and install image properties). I have all of this set correctly and have set the OOBE against the install image.

I can't for the life of me work out why my OOBE won't apply, I get prompted for language, locale, computername, account etc.

I have searched but the only answers I have found all point to needing to use domain admin credentials in the WDS unattend file, I am using a 'local to the WDS box' admin account instead (NOT the builtin 'Administrator' account). Interestingly if I try to use the builtin 'Administrator' account it fails with a login error even though the credentials are correct.

My unattend files were created in WISM using x64 media on a WinXP box. I have even run up a Win7 WAIK box to test WISM from that just incase. I know x86 WISM can modify both and x64 WISM only does x64 but doesn't hurt to check (and rule out another suspect).

Checked the log files in C:\Windows\Panther

In my setupact.log I can see my entries from the unattend file and they aren't listed as erroring; the file is massive and the only error I can find is:

[0x0606cc] IBS    There were no credentials specified for accessing UNC path '\\{myserverIP}\RemInst'

Even though it connects to the same UNC path for drivers and to get the actual image and xml files. Is there somewhere else in this file I need to look? Any key items to search for? I have scrolled through it all and nothing jumps out to me.

The setuperr.log has one line:

2014-08-18 15:53:33, Error      [0x0b0010] WDS    CallBack_WdsClient_CopyPrivatesDone: Failed to process client unattend variables. Error code [0x8007000D].[gle=0x00000057]

Contents of OOBE_Win7_x64_Pro_DualBoot.xml company specific items changed to {}:

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <servicing></servicing>
    <settings pass="specialize">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="{link removed, unverified account}" xmlns:xsi="{link removed, unverified account}
            <Display>
                <ColorDepth>32</ColorDepth>
                <HorizontalResolution>1280</HorizontalResolution>
                <VerticalResolution>1024</VerticalResolution>
            </Display>
            <DisableAutoDaylightTimeSet>true</DisableAutoDaylightTimeSet>
            <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
            <RegisteredOwner>{us}</RegisteredOwner>
            <RegisteredOrganization>{me}</RegisteredOrganization>
            <ShowWindowsLive>false</ShowWindowsLive>
            <TimeZone>E. Australia Standard Time</TimeZone>
            <ComputerName>{tried * & %MACHINENAME%}</ComputerName>
            <ProductKey>{thekey}</ProductKey>
        </component>
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="{link removed, unverified account}{link removed, unverified account}
            <InputLocale>0c09:00000409</InputLocale>
            <SystemLocale>en-AU</SystemLocale>
            <UILanguage>en-AU</UILanguage>
            <UILanguageFallback>en-US</UILanguageFallback>
            <UserLocale>en-AU</UserLocale>
        </component>
        <component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="{link removed, unverified account}
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Order>1</Order>
                    <Path>net user administrator /active:yes</Path>
                    <Description>Enables the built-in admin account</Description>
                </RunSynchronousCommand>
            </RunSynchronous>
        </component>
        <component name="Microsoft-Windows-RemoteAssistance-Exe" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="{link removed, unverified account}
            <fAllowToGetHelp>false</fAllowToGetHelp>
            <fAllowFullControl>false</fAllowFullControl>
        </component>
        <component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="{link removed, unverified account}
            <DisableSR>1</DisableSR>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="{link removed, unverified account}
            <InputLocale>0c09:00000409</InputLocale>
            <SystemLocale>en-AU</SystemLocale>
            <UILanguage>en-AU</UILanguage>
            <UserLocale>en-AU</UserLocale>
            <UILanguageFallback>en-US</UILanguageFallback>
        </component>
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="{link removed, unverified account}
            <OOBE>
                <ProtectYourPC>1</ProtectYourPC>
                <NetworkLocation>Work</NetworkLocation>
                <HideEULAPage>true</HideEULAPage>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>
            <AutoLogon>
                <Password>
                    <Value>{thepass}</Value>
                    <PlainText>false</PlainText>
                </Password>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>{thename}</Username>
            </AutoLogon>
            <Display>
                <ColorDepth>32</ColorDepth>
                <HorizontalResolution>1280</HorizontalResolution>
                <VerticalResolution>1024</VerticalResolution>
            </Display>
            <RegisteredOrganization>{us}</RegisteredOrganization>
            <RegisteredOwner>{me}</RegisteredOwner>
            <TimeZone>E. Australia Standard Time</TimeZone>
            <ShowWindowsLive>false</ShowWindowsLive>
            <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
            <DisableAutoDaylightTimeSet>true</DisableAutoDaylightTimeSet>
            <UserAccounts>
                <AdministratorPassword>
                    <Value>{thepass}</Value>
                    <PlainText>false</PlainText>
                </AdministratorPassword>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>{thepass}</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Description>Local Admin account</Description>
                        <Group>Administrators</Group>
                        <DisplayName>{thename}</DisplayName>
                        <Name>{thename}</Name>
                    </LocalAccount>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>{thepass}</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Description>Autologin generic account for presentaton usage</Description>
                        <Group>Users</Group>
                        <Name>{thename}</Name>
                        <DisplayName>{thename}</DisplayName>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="catalog://{myserver}/reminst/boot/x64/images/install_win7_x64_pro_base_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Apologies for the post length, I just wanted to make sure I presented all of the info.

Any help would be much appreciated ;)

Hi all

Windows server 2008R2 in my unattend file, there is ComputerName

and i would like computer name to be random but with letters, like:

ComputerName-XX434XX

Can i do it ? 

will this work ?

<ComputerName>ComputerName-*</ComputerName>

or i need to do :

            <RegisteredOrganization>CompterName</RegisteredOrganization>

            <RegisteredOwner>CompterName</RegisteredOwner>

            <ComputerName>*</ComputerName>

        </component>

Thanks

I have tried capturing a few images after running sysprep, and they are getting stuck at 50% completion, never moving past after hours of waiting.  "Capturing Windows image metadata...".  If I look on the WDS server I see that the file hasn't been modified since it was actually capturing and moving the progress bar.

Has anyone ever experienced this, or have any ideas of how to troubleshoot?

Thank you!

I have been running Windows Server 2008, that provides my Windows 10 Pro Clients with mapped network drives. After a recent Windows 10 Update, it appears that new Windows PC's no longer have the mapped network drives, after logging onto the domain.

Is this a known problem with Windows 10 Pro and Windows 2008 Server?

Is there anything that I can do to continue to have mapped network drives after my new Windows PC's log into the domain server?

Does anyone have step by step process moving IIS 8.5 INETPUB directory to Another Drive? Running Windows Server 2012 R2.

Thanks.

As asked from here I ask my question on the PowerShell forum.

Hello,

The WDS server is a freshly installed Win 2019 server.

I am trying to import install images with PowerShell.

$ImagePath = 'D:\Sources\2019\install.wim'
$ImageName = (Get-WindowsImage -ImagePath $ImagePath -Index 4).ImageName
Import-WdsInstallImage -ImageGroup 'Win2019' -ImageName $ImageName -Path $ImagePath -Multicast

However I get the following error:

Import-WdsInstallImage : An install image could not be found in the image file.
At line:3 char:1+ Import-WdsInstallImage -ImageGroup 'Win2019' -ImageName $ImageName -P ...+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+ CategoryInfo          : NotSpecified: (MSFT_WdsInstallImage:root/cimv2/MSFT_WdsInstallImage) [Import-WdsInstallImage], CimException+ FullyQualifiedErrorId : 0xC111010E,Import-WdsInstallImage

The image file is NOT read-only.

And with the console it works fine.

I also installed the latest system rollup, but the behavior is the same.

I first started to display image names with Get-WindowsImage and copy/paste the name to the Import-WdsInstallImage and got the same error. That's why I was getting directly the name from the Get-WindowsImage cmdlet. But no luck, still the same error...

And while the Import-WdsInstallImage returns an error, the Import-WdsBootImage and theGet-WindowsImage cmdlets are works fine.