Hi,

One of our Windows 7 images has been captured using imagex and then added to WDS. When we go to deploy it, it doesnt show up on the list. After looking at the properites of time .wim it has no hal type, is this why its not showing up?

If i do an imagex /info this is what I get

WIM Information:
----------------
Path:        d:\scse8.wim
GUID:        {1b037610-3245-4ec3-802e-624bc359071a}
Image Count: 1
Compression: XPRESS
Part Number: 1/1
Attributes:  0x8
             Relative path junction

Available Image Choices:
------------------------
<WIM>
  <TOTALBYTES>34954737009</TOTALBYTES>
  <IMAGE INDEX="1">
    <DIRCOUNT>78206</DIRCOUNT>
    <FILECOUNT>920217</FILECOUNT>
    <TOTALBYTES>80333226987</TOTALBYTES>
    <HARDLINKBYTES>3534890930</HARDLINKBYTES>
    <CREATIONTIME>
      <HIGHPART>0x01CC78B1</HIGHPART>
      <LOWPART>0x18BBC96A</LOWPART>
    </CREATIONTIME>
    <LASTMODIFICATIONTIME>
      <HIGHPART>0x01CC78B1</HIGHPART>
      <LOWPART>0x18D3A0EE</LOWPART>
    </LASTMODIFICATIONTIME>
    <WINDOWS>
      <ARCH>0</ARCH>
      <PRODUCTNAME>Microsoft® Windows® Operating System</PRODUCTNAME>
      <VERSION>
        <MAJOR>6</MAJOR>
        <MINOR>1</MINOR>
        <BUILD>7601</BUILD>
        <SPBUILD>17651</SPBUILD>
        <SPLEVEL>0</SPLEVEL>
      </VERSION>
      <SYSTEMROOT>WINDOWS</SYSTEMROOT>
    </WINDOWS>
    <NAME>scse8</NAME>
  </IMAGE>
</WIM>

Is there any way of adding the hal info to the image?

Thanks

I have a Win2008 R2 WDS server that has been up and running for quite some time. I have a Windows 7 x86 image that is hosted on that server.

I recently updated the Win7 image, syspreped, and uploaded to my WDS server as a new (v2) image. In the past this has always been quite simple, but for some reason i cannot get the new v2 image to display at the WDS client image selection screen.

The WDS server allowed me to add the new v2 image to my install image group, and says its online and working properly.

The WDS Client will only display the old v1 image and not the newly updated v2 image.

Both images were created on the SAME computer, x86, acpi multiprocessor. I am using the SAME computer to test/deploy the image.

The source of the problem seems to be from the install image missing the HAL details

If i use the WDS console and drill down to my old and new install images, right click and look at the properties this is what i get:

v1 Image: HAL Type ACPIAPIC

v2 Image: HAL Type (ITS F"N BLANK!!!!)

I get the same results looking at the <HAL>  </HAL> parmeters using ImageX /info blah.wim

SO, Why the HELL does WDS/Sysprep not recognize my HAL type of my new v2 image???? I have tried 3 different computers to generate/capture the install image and ALL are missing the HAL type.

I have previously tried this KB with no change:

"An ACPI APIC UP HAL operating system image cannot be deployed if a Windows 7 boot image or a Windows Server 2008 R2 boot image is used in the deployment process

http://support.microsoft.com/kb/980711"

me

Hi,

We're having a bunch of WDS on Windows Server 2012 spread out. We need to get statistics from these servers (one by one or centralized). We are specifically interested in how many deployments have occured at a WDS machine.

We were looking at the WDS logging but couldn't quite find the fact of how many installations had been performed.

Anyone know if this is possible?

Thanks

Erik, with many, many certs! ;-)

Hello everyone!

I'm trying to setup a standalone deployment server using MDT 2013 on a WS2012R2 OS but i'm running into some slight problems. 

The first problem is that i can't seem to figure out how to give the deploying clients internet during the deployment process in order to activate Windows and Office. I'm using a ProLiant MicroServer Gen8 from HP as the dedicated server. The first NIC is for accessing internet and the other one have the static IP for the deployment

The other problem is time zones. I have the commands for the timezones put in on rules but it doesn't accept it and gives me something else. What would the command for +01:00 GMT timezones be? 

Kind regards

A padawan!

Hello, I've been using WDS on Windows Server 2012 R2 for quite a while now, and mostly in success.
However, yesterday the boot image that I use to boot x86 Windows 8 Client hardware (Lenovo TP10) suddenly gets a 
'Secure Boot
Image failed to verify with *ACCESS DENIED*'
Message each time i boot it. This does happen on 4 of these specific deviced; if I try booting to my x64 image on a Fujitsu E544, it works like a charm.

The reason why I say 'Suddenly stopped' is because it did work without problem (on all devices on which it does no longer..) untill yesterday evening. 
I did not change anything in the configuration; except that I tried using the boot image to create a 'Capture Image' - which failed because it is a modified boot image and the WDS Capture Client was not found inside it.
Directly after that; this behaviour started.

I've enabled logging in the 'Event Viewer > Application and Services --> Microsoft --> Windows --> Deployment-Services-Diagnostics-->Debug' and it gives me 133 events while booting, from which 3 are errors:

[Information]
[WDSServer/WDSTFTP] TftpSession[0x000000E5957068F0:192.168.48.8:1433] - Error: Received error from client. Code=8.

[Error1]
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tftpsession.cpp:1636] Expression: , Win32 Error=0x4d3

[Error2]
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tftpsession.cpp:1720] Expression: , Win32 Error=0x4d3

[Error3]
[WDSServer/WDSTFTP] [base\eco\wds\transport\server\tftp\tftpserver.cpp:1211] Expression: , Win32 Error=0x4d3

I am unable to find 0x4d3 anywhere as a consistend error message (well, I can find that it is being logged a lot, but never a meaning of it)

As I check the security of the file which is downloaded before the errors start (according to log)
[WDSServer/WDSTFTP] TptReadFile: File=W:\RemoteInstall\boot\x86\wdsmgfw.efi, Size=1286608

It says 'Everyone' can read and execute; and it is not different from the wdsmgfw.efi in the x64 folder (x64 bootting works)

The signatures seem to be OK (digitally signed 'till 04-30-2015) by microsoft)
and my date/time settings also seem to be correct (else the x64 won't work either)

I tried creating a new x86 Windows 8 boot.wim, and uploaded it without modifying it, and the problem still exists.

I'm really desperate for a solution, cause reïnstalling the WDS feature would be a major pain and I do need this solution to image x86 Windows 8 machines with WDS.

Thanks in advance,

Alex van den Bos

Hello!

I'm having some issues with multicasting on a large university network. Our setup is like this:

• WDS role setup on VM with Server 2012 R2
  
• Deployment shares hosted on the same VM - Using MDT 2013 to manage Deployment Shares
  
• VM is on a different VLAN from client computers. - IP Helpers to connect between the VLANs
• Multicast namespace was created successfully.
• All switches between server and client are managed, IGMPv3 compatible, and have snooping enabled3
• MDT Images are custom WIMs, with no setup files

When I run a deployment on any number of clients, I get the message saying "Attempting multicast transfer". The clients show up listed in the WDS Multicast Transmission. Then the clients drop off the server, and begin unicasting. Unicast speeds are excellent. Our 10GB images copy in about 10 mins. But we plan to do 30-40 systems at a time, and I believe that could cause some issues with so many individual sessions running...

I've noticed under our network adapter properties that Microsoft Network Adapter Multiplexor Protocol is unchecked. Not sure if that is related?

I have copied multicast information from the BDD.log file on one of the failed clients. That can be found below.

Any help/advice will be greatly appreciated! Thank you!

<![LOG[LTI applying image \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4\Windows 7 (x64) - 4.0.wim using ImageX]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Event 41023 sent: LTI applying image \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4\Windows 7 (x64) - 4.0.wim using ImageX]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Property SourcePath is now = \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Multicast transfer to directory: C:\MININT\Operating Systems\Windows 7 (x64) - Vers 4]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[<Message containing password has been suppressed>]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Command has been started (process ID 504)]LOG]!><time="14:42:33.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 504)]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 504)]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Windows Deployment Services Multicast Client [Version 6.3.9600.17237]
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Copyright (c) Microsoft Corporation. All rights reserved.
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:42:34.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Transfer Started.
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Transfer Complete [0x800705B4].
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > Operation Failed. [0x800705B4].
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > This operation returned because the timeout period expired.
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console >
]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[  Console > ]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Return code from command = -2147023436]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply"><![LOG[Multicast transfer could not be completed, rc = -2147023436, falling back to using \\BRYANTWDS-SERV1\CopyToDrives$\Operating Systems\Windows 7 (x64) - Vers 4\Windows 7 (x64) - 4.0.wim]LOG]!><time="14:43:04.000+000" date="02-04-2015" component="LTIApply" context="" type="1" thread="" file="LTIApply">

Hi,
First time posting in here. I'm a bit stuck on a project that I'm currently working on and was hoping someone here with some more WDS experience might be able to spot something I'm missing. I'm currently using server 2008r2 to facilitate an unattended deployment of some client Windows 7 desktops. The annoying part is that the site I'm deploying to is a support office with no IT staff there - just me doing this remotely.

I've managed to get the networking and DHCP (on a separate linux system) running great. The computers are picking up the boot file and installing windows fine (drivers, partitioning, etc). Client_unattend.xml is installing the software as commanded. Where I'm hitting my snag is that the computer is then trying to boot to the local admin account instead of joining the domain. This confused me because I used the exact same (barring a few minor tweaks for time zone and languages) image_unattend.xml file in my test setup at my main office and it worked fine. Below is the XML file in use. Is there something here that jumps out at anyone? Any hints would be very very welcomed, and thanks to anyone who can have a look.

P.s. My next step is to talk the staff through getting the /panther/setup log files off the computers C: drive.
Users,tokens, domains and passwords have been changed to protect the innocent.

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="specialize">
        <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="<PUBLIC TOKEN>" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <Identification>
                <JoinDomain>DOMAIN.net.au</JoinDomain>
                <UnsecureJoin>false</UnsecureJoin>
                <DebugJoin>true</DebugJoin>
                <MachineObjectOU>OU= OUR SITE,OU= SITE COMPUTERS,DC=COMPANY,DC=net,DC=au</MachineObjectOU>
                <DebugJoinOnlyOnThisError>0</DebugJoinOnlyOnThisError>
                <Credentials>
                    <Domain>OURDOMAIN.net.au</Domain>
                    <Password>PASSWORD</Password>
                    <Username>USER</Username>
                </Credentials>
            </Identification>
        </component>
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="PUBLIC TOKEN" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <ComputerName>%MACHINENAME%</ComputerName>
            <TimeZone>Singapore Standard Time</TimeZone>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="PUBLIC TOKEN" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <OOBE>
                <NetworkLocation>Work</NetworkLocation>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                <HideEULAPage>true</HideEULAPage>
                <ProtectYourPC>3</ProtectYourPC>
            </OOBE>
            <UserAccounts>
                <LocalAccounts>
                    <LocalAccount wcm:action="add">
                        <Password>
                            <Value>PASSWORD</Value>
                            <PlainText>false</PlainText>
                        </Password>
                        <Description>Vagrant User</Description>
                        <DisplayName>vagrant</DisplayName>
                        <Group>Administrators</Group>
                        <Name>vagrant</Name>
                    </LocalAccount>
                </LocalAccounts>
            </UserAccounts>
            <TimeZone>Singapore Standard Time</TimeZone>
        </component>
    </settings>
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-DNS-Client" processorArchitecture="amd64" publicKeyToken="PUBLIC TOKEN" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <DNSSuffixSearchOrder>
                <DomainName wcm:action="add" wcm:keyValue="DOMAIN">1</DomainName>
            </DNSSuffixSearchOrder>
            <DNSDomain>DOMAIN.net.au</DNSDomain>
            <UseDomainNameDevolution>true</UseDomainNameDevolution>
        </component>
    </settings>
    <cpi:offlineImage cpi:source="wim://DOMAIN/software/msi%20and%20mst%20stuff/win7%20wim%20files/sources/install.wim#Windows 7 PROFESSIONAL" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>

Hi all,

I wanted to know, what would be the best way to setup my WDS so that I can incorporate both windows 7 & 8.1 x64 boot and capture images.

The reason I ask this, is because I added the Windows 8.1 boot image, created a capture image and then after sysprep'ing a machine with windows 8.1 64 bit, I tried to capture it but ended up with the 0xc000000f error which has knocked out all of my capture images.

I've only just attempted the dism mount & dismount method to see if it has fixed it, but I would appreciate if anyone knows an error free method so that I can have both windows 7 & 8.1 capture images to work together.

Thanks,

Hasan

Hello- I am a help desk manager but am trying to learn the ropes on more advanced topics.

Currently, for our users to go to our self service reset portal, they need to enter http://<ip address>:<port number> in IE.

I'd like to be able to tell them they can type 'help' in the url bar and get redirected towards this portal.

I can probably figure out the group policy to make sure the term 'help' isn't searched for using bing/google, etc. but is treated as a machine name.

The issue I am asking about it setting up an alias that will point to an IP w/ port. I've looked around online and this isn't easily done- I believe you have to set up a reverse proxy. I have access to a server and can install the IIS role. I was just wondering if anyone has done this already, or knows of a tutorial online that can guide me?

Thanks-

I want to deploy an image using wds on server 2012. I will be using an answer file for unattended installation with little touch as possible. My answer file works great but I can't get the auto-logon to work and the FirstLogonCommand to run. I added Components\7 oobeSystem\amd64_ Microsoft-Windows- Shell-Setup _neutral\FirstLogonCommands to my answer file using Windows Image Manager and added these values:

    CommandLine = powershell -command Install-WindowsFeature DNS –IncludeManagementTools -IncludeAllSubFeature -Restart

    Description =Install dns server

    Order = 1

Then I did auto logon located at Components\7 oobeSystem\amd64_ Microsoft-Windows- Shell-Setup _neutral\Autologon and added these values:

    Domain = contoso

    Enabled = true

    LogonCount = 1

    Typed the password

    Username = Administrator

These two components alone don't work. It installs server 2012 OK and bypasses all the screens I want to bypass it even joins the domain contoso successfully. I have to manually logon and then when I logon no scripts or anything is ran. When server manager opens dns role is not installed and not even located under tools.

Things I tried:

Open cmd as admin and typed "powershell -command Install-WindowsFeature DNS –IncludeManagementTools -IncludeAllSubFeature -Restart." this worked and installed roles successfully

If I missed anything to help you troubleshoot just ask.

Hi. Im having a problem where I get the error 'An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment'when booting from a standard WDS boot.wim image taken from a Windows 7 DVD.

I am using Server 2008 R2 and am adding the drivers to the boot using WDS, but also have the problem if the drivers are injected beforehand using DISM.

When the error occurs I can shift + F10 and IPCONFIG and see it HAS picked up an internal IP from DHCP. Seems maybe it is timing out before it gets the IP?

As per some fixes I have read I enabled RSTP on my switches but that didnt help.

I have included the end of setupact.log to see if any of you have any ideas.Seems to be failing but as I say, the network IS initialized as I can see the internal IP assigned by DHCP when running IPCONFIG.

I dont suppose theres any way of increasing the timeout?

Thanks.

2011-04-11 17:26:31, Info       [0x0b0022] WDS    StartNetworking: Trying to start networking.
2011-04-11 17:26:31, Info                  WDS    Network service dhcp not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service lmhosts not running or could not be queried: 264e18 1 1
2011-04-11 17:26:31, Info                  WDS    Network service lanmanworkstation not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service bfe not running or could not be queried: 264e18 1 1
2011-04-11 17:26:31, Info                  WDS    Network service ikeext not running or could not be queried: 264d00 1 1
2011-04-11 17:26:31, Info                  WDS    Network service mpssvc not running or could not be queried: 264e18 1 1
2011-04-11 17:27:24, Info                  WDS    Installing device pci\ven_14e4&dev_1691&subsys_04aa1028 X:\WINDOWS\INF\oem37.inf succeeded
2011-04-11 17:27:25, Info                  WDS    No computer name specified, generating a random name.
2011-04-11 17:27:25, Info                  WDS    Renaming computer to MININT-VN2P876.
2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
2011-04-11 17:27:25, Info                  WDS    Service winmgmt disable: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Service winmgmt stop: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Service winmgmt enable: 0x00000000
2011-04-11 17:27:25, Info                  WDS    Released profiling mutex
2011-04-11 17:27:25, Info                  WDS    Acquired profiling mutex
2011-04-11 17:27:25, Info                  WDS    Install MS_MSCLIENT: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_NETBIOS: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_SMB: 0x0004a020
2011-04-11 17:27:25, Info                  WDS    Install MS_TCPIP6: 0x0004a020
2011-04-11 17:27:26, Info                  WDS    Install MS_TCPIP: 0x0004a020
2011-04-11 17:27:26, Info                  WDS    Service dhcp start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service lmhosts start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service ikeext start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Service mpssvc start: 0x00000000
2011-04-11 17:27:26, Info                  WDS    Released profiling mutex
2011-04-11 17:27:26, Info                  WDS    Spent 967ms installing network components
2011-04-11 17:27:28, Info                  WDS    Spent 2247ms installing network drivers
2011-04-11 17:27:38, Info                  WDS    QueryAdapterStatus: no operational adapters found.
2011-04-11 17:27:38, Info                  WDS    Spent 10140ms confirming network initialization; status 0x80004005
2011-04-11 17:27:38, Info                  WDS    WaitForNetworkToInitialize failed; ignoring error
2011-04-11 17:27:38, Info                  WDS    GetNetworkingInfo: WpeNetworkStatus returned [0x0]. Flags set:   
2011-04-11 17:27:38, Error      [0x0b003f] WDS    StartNetworking: Failed to start networking. Error code [0x800704C6].[gle=0x000000cb]
2011-04-11 17:27:38, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [WdsClient: An error occurred while obtaining an IP address from the DHCP server. Please check to ensure that there is an operational DHCP server on this network segment.]

Hello,

I want to inject the update in the ISO image can anyone help me on the same.

As per the methods in below link tried but in vain.

 https://support2.microsoft.com/kb/2966870

Appreciate any suggestions.

I have a lab environment setup specifically for imaging laptops via WDS.   I have a stand alone Windows 2012 server connected directly to an 8-Port Cisco SG-220 8 Port switch.    Nothing else is connected to this server and it is not being used for anything else.  The server is running DHCP and WDS.    I can boot laptops via PXE and connect to the WDS server to deploy the images through standard WDS imaging.  However, I have not been able to get Multicasting to work.  I have never used Multicasting before and have read through the documentation but must be missing something.  This is what I've done:

1. In the WDS server I right click on my deployment image and select 'create multicast image' then go through the prompts to create an auto-cast image.  

2. The Multicast image is created and shown as 'waiting' on the WDS server.

3. The Cisco router is brand new out of the box, the only configuration I did was to enable IGMP snooping.  I did not make any other changes to the setup of the switch.

4. I boot a target machine via PXE using the same Boot Image that I always use.  It loads to the screen where I can select the image I want to deploy but it never shows the multicast image as an option.  I only see the regular image I had previously been using.

I'm not sure what else I'm missing in order to get the target machine to connect and image using the multicast image.  

Here are a few screen shots of what I have setup:

Here is the multicast image created on the server

Here is the Cisco Router configuration:

Here is the NIC card configuration on the server:

This is the target laptop booted via PXE but it never shows the multicast image as an option.

/>

Hey guys and gals:

I am trying to setup a L2TP VPN server (Win2k12 R2) for a small business and for the life of me I can not figure out whats wrong, I can Auth. and connect but can not access any network resources. I did a netstat -r command and it shows that there are two different masks 255.255.255.255 and 255.255.255.0 (server, provided by router), but when I connect via VPN it's using 255.255.255.255 and I think thats the problem, how do I go about fixing this?  Any help will do.

Dear all

1 Physical host: W2k12R2, 1 Hyper-V virtual switch.

1 Hyper-V VM with W2k12R2 DC with DNS, DHCP, WDS.

1 Empty Hyper-V VM Generation 2 UEFI booting from network.

Problem: Error "PXE-E16: No offer received" on the empty Hyper-V VM when trying to Uefi boot from WDS in AD integrated mode.

I verified that it works when WDS is set-up to standalone mode. See also: https://social.technet.microsoft.com/Forums/windowsserver/en-US/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/wds-efi-bios-wont-pxe-boot-into-efi-mode

PS: Switch to standalone mode: On the WDS server: wdsutil /verbose /uninitialize-server /server:<servername>; wdsutil /verbose /progress /initialize-server /server:<servername> /reminst:C:\RmInst

Cause (found by Netmon IP traffic monitoring):

The Client asks for the TFTP Server on UDP port 4011.

The TFTP Server takes more than 8 seconds to reply on port 4011.
This seems to be due to NbtNs (Netbios name search) broadcast queries searching for 1C Domain Controllers.

Solution: ???????

Any help is much appreciated.

Dominique, Zürich, Switzerland.

Hi all

Recently set up a 2012R2 server in our domain as a WDS server. After syspreping Win7 x64 with an unattend file and capturing images the machines just don't want to join the domain, after windows install it gets to the "Applying system settings" and hangs for 15 minutes (while i assume it tried to join the domain) then eventually restarts but with no domain join, everything else in the unattend file works fine bar the domain join. I've tried with secure join and unsecure join but none work. Using no unattend file the domain join works fine.

I've searched every forum and tried various methods to get this working but still no joy.

Can anyone suggest anything?

Thanks

I am installing a new Server 2012 (Essentials) and am at the point of deciding whether to start with a clean install or to migrate our existing domain.  Our network is less than 10 workstations, so while migration might be quicker, I'm not sure its the right thing.  Here's why:

We have a Windows 2003 SBS that was itself migrated from a previous server version. Within Active Directories Domains and Trusts, our domain is listed as XXX.local with a full domain name of "Company", where XXX is a 3-letter acronym for Company. This has caused lots of confusion when adding new workstations because, on most other networks that I see, the listing is the same as the actual domain name.

I know that Server 2012 will require a domain named "name.CompanyDomain.com" (or the like), but am not sure how it will handle migrating this odd setup.  (I don't want to end up with XXX.CompanyDomain.com with a name of "Company".)

Thanks!

I have a Windows 2012 server in a lab environment connected directly to a Cisco SG200 8 Port Gigabit switch configured for Multicasting.    I have an image that is about 8GB in size that I using to test with.   When I image just a single target machine in unicast it takes about 5 minutes to complete.   I then create a multicast of that same image in the WDS console and try imaging the same  single machine via Multicast but it take 20 minutes to complete.   I also tried this with 7 target machines but the same speed was still just as slow.

The Cisco switch has IGMP snooping enabled and I also tried enabling Multicast Storm Control but still no difference.

Any suggestions as to why the Multicast is SO slow?

Thanks

My KMS server is running on Windows Server 2012 R2 and activated by Server 2012 KMS Key. 
I would like to use the KMS server to activate many Windows 2008 R2 server, however, Error message "0xC004F050 The software licensing service reported that the product key is invalid" is appear when adding Windows Server 2008R2 KMS Key. The Windows Server 2008 R2 KMS key is confirmed and validated by Microsoft Telephone service.

Command used:

slmgr /ipk<Windows Server 2008 R2 KMS Key>

Anyone can help? thanks.  

Hi,

My scenario.

I need to deploy 10 Winserver 2012R2 through WDS , and I need all of these 10 machines to have a different SID after installation.

at what stage I should run SYSPREP.exe so that all these 10 newly installed machines have differe SID.

Thanks,

Zasid