WDS deployment

Hi
I have to propose a Wi-Fi zone for a university.There are around 8 floors and I plan to go with 1200 series
A simple solution which would come to your mind is 1231g (IOS) installed in WDS mode.Documents shows that
Client1==AP1==WDS==AP2==client2
will work fine. AP1 and AP2 are in range with WDS master on which I will terminate internet connectivity with ethernet handoff.
Great! Now the design specific problem I am facing that there is nowhere written or shown that
Client1==AP1==AP2==AP3==WDS==AP4==AP5==client2\
would work.AP1 and AP2 are not in direct wireless range with WDS. So is AP5.
So will this work.
The idea is to deploy 2 APs per floor and both the floors' APs should work in WDS so that I would not have to lay ethernet for each AP.
Pardon me for being silly.....
Also I have seen that there is around 50% signal degradation (3-4dB) loss per floor.Will above setup work?
Pardon me for being silly.....:)
Any ideas? comments?
Thanks in advance.
JD

There are many threads for this, have a look : https://social.technet.microsoft.com/Search/en-US/Technet?query=invalid%20credentials%3A%20the%20network%20path%20was%20not%20found&beta=0&ac=5
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Similar Messages

  • WDS Deployment Error; Network Path Was Not Found

    Hello,
    For a couple of years we have had a Windows Deployment server on Server 2008 called "WinDeploy".  Recently, we created a new server on Server 2012 and I created a new WDS called "WDHQ".  I did not want to have to create new
    task sequences and redo all of my out of box drivers, so we just copied the old "DeploymentShare" to the new file share on WDHQ.
    However, now when I try to PXE boot and enter in my credentials, it says "Invalid credentials: the network path was not found".  If I cancel, it points to a old network path that is no long there. WinDeploy.  I deleted the boot files,
    updated the deployment share, and updated the boot files.  I found a bootstrap file that still referenced WinDeploy and changed it to WDHQ.  Still the same problem.
    Any help or other possible solutions would be greatly appreciated.  
    Thanks! 

    There are many threads for this, have a look : https://social.technet.microsoft.com/Search/en-US/Technet?query=invalid%20credentials%3A%20the%20network%20path%20was%20not%20found&beta=0&ac=5
    Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
    the thread.

  • How to create PBR functionality using WDS deployment

    Dear sir/madam,
    We are a Dutch OEM currently working on deployment and DIS. I have a question about deployment I’m hoping you can help us with.
    We were tought to deploy images via USB using the following script:
    dism /Apply-Image /ImageFile:%1 /Index:1 /ApplyDir:W:\
    md T:\Recovery\WindowsRE
    attrib -h -a -s W:\windows\system32\recovery\winre.wim
    copy W:\windows\system32\recovery\winre.wim T:\Recovery\WindowsRE\winre.wim
    W:\Windows\System32\bcdboot W:\Windows /s S:
    W:\Windows\System32\reagentc /setreimage /path T:\Recovery\WindowsRE /target W:\Windows
    Mkdir R:\RecoveryImage
    Copy %2 R:\RecoveryImage\
    W:\Windows\System32\reagentc /setosimage /path R:\RecoveryImage /target W:\Windows /index 1
    This works perfectly for single systems. However, since we’re planning on building a lot of units we want to automate installation over network. We’re building a solution to deploy custom images on tablets, laptops and desktops based on
    WDS. We currently have a working MS Server 2012 WDS server and several working custom images. The question we have is regarding the system recovery functions (PBR). I’ve managed to automate login to WDS, language choice and disk partitioning using WDSunattend
    (see below). WinRE and Recovery Image partitions are created. We can manually select the image we want to deploy and it will successfully install to the Windows partition.
    <?xml version="1.0" ?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
    <settings pass="windowsPE">
    <component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
    <WindowsDeploymentServices>
    <Login>
    <WillShowUI>OnError</WillShowUI>
    <Credentials>
    <Username>Administrator</Username>
    <Domain>WDS.assemblage.com</Domain>
    <Password>xxx</Password>
    </Credentials>
    </Login>
    <ImageSelection>
    <WillShowUI>OnError</WillShowUI>
    <InstallTo>
    <DiskID>0</DiskID>
    <PartitionID>4</PartitionID>
    </InstallTo>
    </ImageSelection>
    </WindowsDeploymentServices>          
    <DiskConfiguration>
    <Disk>
    <DiskID>0</DiskID>
    <WillWipeDisk>false</WillWipeDisk>
    <CreatePartitions>
    <CreatePartition>
    <Order>1</Order>
    <Size>540</Size>
    <Type>Primary</Type>
    </CreatePartition>
    <CreatePartition>
    <Order>2</Order>
    <Size>260</Size>
    <Type>EFI</Type>
    </CreatePartition>
    <CreatePartition>
    <Order>3</Order>
    <Size>128</Size>
    <Type>MSR</Type>
    </CreatePartition>
    <CreatePartition>
     <Order>4</Order>
    <Size>20000</Size>
    <Type>Primary</Type>
    </CreatePartition>
    <CreatePartition>
    <Order>5</Order>
    <Extend>true</Extend>
    <Type>Primary</Type>
    </CreatePartition>
    </CreatePartitions>
    <ModifyPartitions>
    <ModifyPartition>
    <Order>1</Order>
    <Format>NTFS</Format>
    <Label>WinRE</Label>
    <PartitionID>1</PartitionID>
    <TypeID>de94bba4-06d1-4d40-a16a-bfd50179d6ac</TypeID>
    </ModifyPartition>
    <ModifyPartition>
    <Order>2</Order>
    <PartitionID>2</PartitionID>
    <Label>System</Label>
    <Format>FAT32</Format>
    </ModifyPartition>
    <ModifyPartition>
    <Order>3</Order>
    <PartitionID>3</PartitionID>
    </ModifyPartition>
    <ModifyPartition>
    <Order>4</Order>
    <PartitionID>4</PartitionID>
    <Letter>C</Letter>
    <Label>Windows</Label>
     <Format>NTFS</Format>
    </ModifyPartition>
    <ModifyPartition>
    <Order>5</Order>
    <PartitionID>5</PartitionID>
    <Label>Recovery</Label>
    <Format>NTFS</Format>
    <TypeID>de94bba4-06d1-4d40-a16a-bfd50179d6ac</TypeID>
    </ModifyPartition>
    </ModifyPartitions>
    </Disk>
    </DiskConfiguration>
    </component>
    <component name="Microsoft-Windows-International-Core-WinPE" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
    <SetupUILanguage>
    <WillShowUI>OnError</WillShowUI>
    <UILanguage>en-GB</UILanguage>
    </SetupUILanguage>
    <UILanguage>en-GB</UILanguage>
    </component>
    </settings>
    </unattend>
    Here’s the problem: I can’t find any information on creating PBR functionality using unattend anywhere. Is this possible? If it is, can you help us find a solution?
    Since I can’t find any info on creating PBR using unattend I’m assuming that we have to add PBR functionality using scripts after Windows setup is completed. How do we get this done using WDS?
    With kind regards,
    Frank Wessels.

    Hi,
    We could use deploymenr scripts to configure the recovery partitions:
    Samples: Applying Windows, System, and Recovery Partitions by using a Deployment Script
    More information regarding Capture and Apply Windows, System, and Recovery Partitions, please check:
    http://technet.microsoft.com/en-us/library/hh825041.aspx
    Hope this may help
    Best regards
    Michael Shao
    TechNet Community Support

  • WDS deployment booting not working properly! filename incorrent?

    Hi!
    I recently set up a new Server 2012 and installed WDS using this guide http://technet.microsoft.com/en-us/library/jj648426.aspx
    I did a Active directory integrated installation and accepting any computer to boot from the wds files.
    But the boot fails with error code PXE-E23 so i tried downloading the file manually from the WDS using a tftp client. everything works out fine.
    The file is located in boot\x86\wdsnbp.com
    But when i try to boot on the network it says "NBP filename is boot\x86\wdsnbp.comÿ" why is that ÿ there? it doesnt show up in the dhcp configuraion(we use a thirdparty dhcp called infoblox and it worked fine with our old wds.) and the configuration
    in the dhcp is correct. 
    How do i troubleshoot PXE-E23?
    Why is that "ÿ" there? just a bug something to worry about?

    Lots of other people are having this issue- can you elaborate on "it was the client computer"?
    Were you able to change something on the client to fix this? If so- what?

  • 2012 Deployment using WDS

    I was wondering does anyone use WDS to deploy 2012/2012R2 to HP Proliant servers (G7s,G8s,G9s)?
    If so, can you tell me your experience?  Easy to setup and use as compared to Intelligent Provisioning on the G8s and G9s?
    Thanks!

    Hi
    For the WDS deploy process always is same, such as all the first step may be is add dirvers to boot image,When we use WDS to deploy image often need to use multiple drivers,
    you can install the HP SoftPaq Download Manager utility to download drivers.
    More information:
    Windows Deployment Scenarios and Tools
    http://technet.microsoft.com/en-us/library/dn744294.aspx
    I’m glad to be of help to you!
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • So how to specify different answer file for different install images in WDS snap-in?

    hello
    in WDS snap-in, in properties on server name, on client tab, we can define an answer file for unattended windows installation on WDS clients.
    my question is, maybe we have added multiple images in WDS snap-in (win xp image, win 7 , win 2008,...)
    now this one answer file applies to all of them ?
    so how to specify different answer file for different install images in WDS snap-in?
    thanks in advanced 

    Under the "Client" tab of WDS, you should only use an answer-file with settings relevant for the installation. This would be credentials for the WDS deployment share, international settings used during the setup and possibly also destination drive
    details (if you want the installation to take care of partitioning the disk etc). The settings relevant for unattend-files used under "Client" would only be of those in phase 1 (WinPE).
    However, if you would like to have specific unattend file for every installation, e.g. Win7, Server 2008, Win 8 etc, you can browse to the image under "Install Images" under the image Groups. There you can select properties for every image and
    have a personal unattend-file.
    hi Joel
    very cool. thanks a lot, that really helped me.
    best regards

  • WDS - No boot image

    Good afternoon,
    Hoping that one of you gurus will be able to help save my sanity here. :)
    Background: We used RIS for quite a while, but after the SP2 update it failed so we decommisioned it. Now, WDS is on a Server 2008 R2 box and joined to the in the domain. While not an actual DHCP server, it is authorized in AD as a DHCP server. The DHCP
    server is on a different server (running Solaris) on the same subnet. I have created images and have been able to do captures and remote installations.
    Issue: The WDS server and the PXE clients work perfectly if they are both connected to a workgroup/soho type switch (5 port Linksys/DLink/etc). However if they are both plugged into the wall (the 'real' network) they do not work at all...the PXE client just
    spins waiting for an address before returning that it couldn't locate a boot image. This is true even if I put both the WDS server and the PXE client on the same subnet.
    I have ran packet captures on both working and non-working scenarios. In the non-working scenario with both machines on the same subnet the server's NIC can see the network traffic, but does not respond to it. When they are both on the workgroup switch it
    does respond to it. I have checked the routers for this subnet and there is an ip address helper configured to match the IP of the WDS server. However, if they are both on the same subnet then they are in the same broadcast domain and really that shouldn't
    matter...but it is there and configured because eventually the WDS server will move to a different subnet than the PXE clients.
    So I am curious, does anyone have any ideas as to why WDS would work flawlessly on a little workgroup switch, but not on the corporate network even when on the same subnet, in the same room, on the same wallplate, running to the same switch?
    I appreciate any and all advice, tips, tricks, insights that anyone could provide. :)
    -Joe

    Hi Joe,
    Can I ask if you've configured the DHCP options required on your Solaris DHCP Server?
    A snippet from the WDS deployment guide
    http://technet.microsoft.com/en-us/library/cc766320(WS.10).aspx
    "Add DHCP options 66 and 67. Option 66 should be set to the Windows Deployment Services server, and option 67 should be set to boot\x86\wdsnbp.com."

  • WDS Unattendant oobe - need help

    Hello.
    My problem is in unattended installation. I use Image Manager to perform unattended installation. My XML file is verified but something is wrong with oobe section. I'm trying to configure installation so that the following options are not be promted but
    configured in XML:
    1. User adding.
    2. Timezone choice.
    3. Locale and language choice.
    I link a screenshot of my XML file in Image Manager.
    This file works for other sections but when Windows starts for the first time, it asks all this options. I don't want it.
    Please help.

    Hi Dissonance,
    As Tripredacus said, there are two answers for WDS deployment:
    WDSClientUnattend for WinPE phase
    AutoUnattend for specialize and OOBE things  
    So, you can follow the link above to create related answer files for your own sake.
    If this issue still persists, we can check the installation log file to more information. But first, we should confirm the information above.
    If you have any feedback on our support, please click
    here
    Alex Zhao
    TechNet Community Support

  • WDS on server 2008 std breaking .WIM files

    Hi,
    SUMMARY - 'Importing images into WDS seems to break them'
    I'm a bit green so i appologise if I'm being stupid. I'm installing and configuring WDS and MDT deployment within a mixed MS 2003 domain environment. We need to be able to deploy 32 bit images and the server will be used for servicing images as well
    as deploying and so (I think) I need to use Server 2008 standard as creating catalogue files on x64 systems for x86 images doesn't work.
    So - the system is:
    Server 2008 standard x86 edition; WDS Deployment Services Role; MDT 2012 Update 1; ADK 8, config manager tools for trace32.exe.
    I have imported win7 boot and install images directly from the original DVD .iso files, both x86 and x64. Both capture and setup images work ok. I've added network drivers to these successfully. I can deploy vanilla win7 x86 and x64 using WDS - this works
    fine.
    So my issue is: I've deployed vanilla windows 7 to a desktop, installed applications, updated config as nessecary etc. Booted using the appropriate capture image and captured a .wim file. I've copied this to my WDS server and imported it as an install
    image. When I try and deploy the image it fails just after the 'expanding windows files' stage. After looking in log files the error seems to be 'selected image file does not have a resource section'.
    I've gone back to the WDS server, exported these image files and tried to mount them using DISM - I get the same error: "1812 The specified image file did not contain a resource section"
    Mounting fails.
    Now I've tried mounting the .wim files using dism BEFORE I import them into WDS and they mount without any issues. As soon as I import them and export them again they will not mount any more.
    Please help, I don't know what else to try! :)
    Some things I've thought but can't find answers to: Can you use 2008 standard to deploy Windows 7 at all? (server is earlier version of windows)
    Is the apparent importing into WDS issue a red herring? Could it be that these images are broken from capture? Is there a way to test this without deploying the image using a USB stick instead of WDS?
    I've tried uninstalling the ADK and installing WAIK instead. Exactly the same result. Here are some choice extracts from dism.log:
    2015-03-02 17:33:18, Info                  CBS    Failed to find a matching version for servicing stack: C:\Users\softset\AppData\Local\Temp\MDTUpdate.2544\Mount\Windows\WinSxS\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.2.9200.16384_none_060a6d2998b13f25\
    [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2015-03-02 17:33:18, Info                  CBS    Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2015-03-02 17:33:18, Info                  CBS    Failed to get proc address for CMP_GetServerSideDeviceInstallFlags [HRESULT = 0x8007007f - ERROR_PROC_NOT_FOUND]
    2015-03-02 17:33:18, Info                  CBS    Failed to load CfgMgr32 DLL. [HRESULT = 0x8007007f - ERROR_PROC_NOT_FOUND]
    2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 Failed to mount the image. - CWimImageInfo::Mount(hr:0x80070714)
    2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:999 - CWimManager::InternalOpMount(hr:0x80070714)
    2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:2247 - CWimManager::InternalCmdMount(hr:0x80070714)
    2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 Error executing command - CWimManager::InternalExecuteCmd(hr:0x80070714)
    2015-03-03 15:29:27, Error                 DISM   DISM WIM Provider: PID=2852 d:\w7rtm\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimmanager.cpp:516 - CWimManager::ExecuteCmdLine(hr:0x80070714)
    2015-03-03 15:29:27, Error                 DISM   DISM.EXE: WimManager processed the command line but failed. HRESULT=80070714

    Hello JPNhingy,
    How to do you capture the .wim file?
    About the question: Can you use 2008 standard to deploy Windows 7 at all? The answer is: Yes, you can use the Windows Server 2008 to deploy Windows 7.
    You could create a capturer image in WDS, for more information, please take a look at the following article.
    http://social.technet.microsoft.com/wiki/contents/articles/11680.creating-a-capture-image-in-wds.aspx
    Additionally, you could use the sysprep to generalize the install image.
    https://technet.microsoft.com/en-us/windows/preparing-an-image-using-sysprep-and-imagex.aspx
    Best regards,
    Fangzhou CHEN
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • WDS licensing on client side (OEM Desktops)

    Hello all,
    Have implementing a wds server and the thing is licensing a OEM desktop which has windows 7 pro
    We have like 300 Desktops, all are Dell make with preloaded OEM windows 7 pro operating system & i have recovery disk
    I have created image in WDS and succesfully deployed the image to client but after installation of os on a client
    IT shows windows is not activated.
    HOW to auto reactivate windows licenses on OEM systems
    sharath

    Hi Sharath,
    Did you mean that want to use OEM license for WDS deployment? Or anything I misunderstand?
    On current situation, please refer to following threads and check if can help you.
    Windows
    Deployment server with OEM windows 7 license
    Useing
    Windows Deployment Service to install and activate your Dell OEM copy of windows 7
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • WDS with unattended.xml, client starts without using unattended.xml

    Hi all,
    i've a server W2K12 with WDS (properly installed). I created the file unattended.xml, put it in the folder of my WDS deployment and in the WDS server.
    The ouput of the my unattended.xml is:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="windowsPE">
            <component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
    xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance">
                <SetupUILanguage>
                    <UILanguage></UILanguage>
                </SetupUILanguage>
                <InputLocale>en-us</InputLocale>
                <SystemLocale>en-us</SystemLocale>
                <UILanguage>en-us</UILanguage>
                <UILanguageFallback>en-us</UILanguageFallback>
            </component>
            <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm"http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance">
                <ImageInstall>
                    <OSImage>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>1</PartitionID>
                        </InstallTo>
                        <InstallFrom>
                            <MetaData wcm:action="add">
                                <Key>/Image/Name</Key>
                                <Value>Windows Server 2012 SERVERSTANDARD</Value>
                            </MetaData>
                        </InstallFrom>
                    </OSImage>
                </ImageInstall>
                <UserData>
                    <AcceptEula>true</AcceptEula>
                </UserData>
                <DiskConfiguration>
                    <Disk wcm:action="add">
                        <CreatePartitions>
                            <CreatePartition wcm:action="add">
                                <Order>1</Order>
                                <Size>10000</Size>
                                <Type>Primary</Type>
                            </CreatePartition>
                        </CreatePartitions>
                        <ModifyPartitions>
                            <ModifyPartition wcm:action="add">
                                <Active>true</Active>
                                <Extend>true</Extend>
                                <Format>NTFS</Format>
                                <Label></Label>
                                <Letter>C</Letter>
                                <Order>1</Order>
                                <PartitionID>1</PartitionID>
                            </ModifyPartition>
                        </ModifyPartitions>
                        <DiskID>0</DiskID>
                        <WillWipeDisk>true</WillWipeDisk>
                    </Disk>
                </DiskConfiguration>
                <WindowsDeploymentServices>
                    <Login>
                        <Credentials>
                            <Domain>lol.local</Domain>
                            <Password>AAAA2015</Password>
                            <Username>Administrator</Username>
                        </Credentials>
                    </Login>
                    <ImageSelection>
                        <InstallTo>
                            <DiskID>0</DiskID>
                            <PartitionID>1</PartitionID>
                        </InstallTo>
                    </ImageSelection>
                </WindowsDeploymentServices>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance">
                <UserAccounts>
                    <AdministratorPassword>
                        <Value>QQBuAGQAcgBlAGEANwA5AGMAdgBBAGQAbQBpAG4AaQBzAHQAcgBhAHQAbwByAFAAYQBzAHMAdwBvAHIAZAA=</Value>
                        <PlainText>false</PlainText>
                    </AdministratorPassword>
                    <LocalAccounts>
                        <LocalAccount wcm:action="add">
                            <Password>
                                <Value>QQBuAGQAcgBlAGEANwA5AGMAdgBQAGEAcwBzAHcAbwByAGQA</Value>
                                <PlainText>false</PlainText>
                            </Password>
                            <DisplayName>Administrator</DisplayName>
                            <Group>Administrators</Group>
                            <Name>Admin</Name>
                        </LocalAccount>
                    </LocalAccounts>
                    <DomainAccounts>
                        <DomainAccountList wcm:action="add">
                            <Domain>lol.local</Domain>
                        </DomainAccountList>
                    </DomainAccounts>
                </UserAccounts>
                <AutoLogon>
                    <Password>
                        <Value>QQBuAGQAcgBlAGEANwA5AGMAdgBQAGEAcwBzAHcAbwByAGQA</Value>
                        <PlainText>false</PlainText>
                    </Password>
                    <Username>Administrator</Username>
                    <Enabled>true</Enabled>
                </AutoLogon>
                <FirstLogonCommands>
                    <SynchronousCommand wcm:action="add">
                        <CommandLine> cmd.exe /c a:set-power-config.bat</CommandLine>
                        <Description>Turn off all power saving and timeouts</Description>
                        <Order>2</Order>
                        <RequiresUserInput>true</RequiresUserInput>
                    </SynchronousCommand>
                </FirstLogonCommands>
            </component>
            <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>en-us</InputLocale>
                <UILanguage>en-us</UILanguage>
                <UILanguageFallback>en-us</UILanguageFallback>
                <UserLocale>en-us</UserLocale>
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-ServerManager-SvrMgrNc" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
    xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance">
                <DoNotOpenServerManagerAtLogon>true</DoNotOpenServerManagerAtLogon>
            </component>
            <component name="Microsoft-Windows-IE-ESC" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance">
                <IEHardenAdmin>false</IEHardenAdmin>
                <IEHardenUser>false</IEHardenUser>
            </component>
            <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
    xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance">
                <SearchScopes>
                    <Scope wcm:action="add">
                        <ScopeDefault>true</ScopeDefault>
                        <ScopeUrl>http://www.google.com/search?q={searchTerms}</ScopeUrl>
                        <ScopeKey>Google</ScopeKey>
                        <ScopeDisplayName>Google</ScopeDisplayName>
                    </Scope>
                </SearchScopes>
                <DisableAccelerators>true</DisableAccelerators>
                <DisableFirstRunWizard>true</DisableFirstRunWizard>
                <Home_Page>about:blank</Home_Page>
            </component>
            <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
    xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance">
                <fDenyTSConnections>false</fDenyTSConnections>
            </component>
            <component name="Networking-MPSSVC-Svc" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance">
                <FirewallGroups>
                    <FirewallGroup wcm:action="add" wcm:keyValue="Remote Desktop">
                        <Active>true</Active>
                        <Group>RemoteDesktop</Group>
                        <Profile>all</Profile>
                    </FirewallGroup>
                </FirewallGroups>
            </component>
            <component name="Microsoft-Windows-TerminalServices-RDP-WinStationExtensions" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
    xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi=">http://www.w3.org/2001/XMLSchema-instance">
                <UserAuthentication>0</UserAuthentication>
            </component>
            <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance">
                <Identification>
                    <Credentials>
                        <Domain>lol.local</Domain>
                        <Password>AAAA2015</Password>
                        <Username>admin</Username>
                    </Credentials>
                </Identification>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <ComputerName>W2K12Test</ComputerName>
            </component>
        </settings>
        <settings pass="offlineServicing">
            <component name="Microsoft-Windows-LUA-Settings" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <EnableLUA>false</EnableLUA>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim:c:/images/install.wim#Windows Server 2012 R2 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
    When the client starts instead of going in automatic screen appears windows where I am asked to choose which operating system to install.
    What is wrong?
    Please, DON'T GIVE ME LINKS, BUT THE SOLUTIONS on how to fix it
    Thank you in advance.

    There seems to be some confusion here. What you have posted is a customized unattend.xml file used in WDS deployments, however most MDT deployments won't use these highly customized unattend.xml files, instead using it's own unattend.xml template files.
    FOr example when choosing the SKU type, WDS will allow you to select the type from the unattend.xml file <InstallTo> element above.
    In MDT, however, the SKU Index is chosen and applied manually through a dism.exe /apply image.
    And although your unattend.xml file is interesting, I can't tell what the problem is just by looking at it.
    If you are still having problems, best thing is to start looking through panther logs to see where the OS got confused looking for the image source.
    Check out my help file:
    How to debug problems in Windows Setup (Panther)
    Keith Garner - Principal Consultant [owner] -
    http://DeploymentLive.com

  • Question deploying and imaging Windows 7

    So I have my 2 answer files fully automatic. Added drivers with WDS.
    The problem is now Windows Updates and Applications. What should I use? SCCM or MDT or WDS msi packages? What is the easiest way. 

    Hi,
    To use which tool that depends on your requirements of the deploy environment. I suggest we first take a check with the following article:
    Choose the Right Microsoft Deployment Tool
    More information regarding SCCM, MDT and WDS, please check :
    SCCM: System Center 2012 Configuration Manager,
    MDT: Microsoft Deployment Toolkit, WDS:
    Deploying Windows 7 with Windows Deployment Services
    Best regards
    Michael Shao
    TechNet Community Support

  • Error with syspreped windows 7 image related to capisp.dll execution...

    Hi Folks,
    some time ago I crafted an windows 7 image with sysprep generalization for WDS deployment. In real there are 2 images: one dumped w/o sysprep and the another w/ (dumping with ImageX Tool from WAIK for W7/W2K8R2). The syspreped one I delivered to our WDS
    Server. In the past I made several changes based on the non-syspreped image (incl. WUs) and afterward I've generated a new syspreped version from it. ...and now, since the last revision und sysprep run the last syspreped version (stored at the WDS) is no longer
    installable onto any target machine... Ervery time I tried to deploy this version from the WDS at the target machine an error popup occurs and says that this image cannot be installed at this target machine type (see *** - the german message). Examinig the
    SETUPACT.LOG / SETUPERR.LOG files the following problem has been stated:
    2010-06-21 14:22:54, Info       [0x0f0081] SYSPRP LaunchDll:Successfully executed 'C:\Windows\System32\sppnp.dll,Sysprep_Specialize_Pnp' without error
    2010-06-21 14:22:54, Info       [0x0f008b] SYSPRP RunRegistryDlls:Found entrypoint in registry at SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrep\Specialize\{2172c981-2c23-e969-b30d-046ffeeb096e}; will try to launch 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize'
    2010-06-21 14:22:54, Info       [0x0f0080] SYSPRP LaunchDll:Found 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize'; executing it
    2010-06-21 14:22:54, Info                         capisp.dll::CheckIFCryptoSysPrepSpecialized: returning 0
    2010-06-21 14:22:55, Info                         capisp.dll::CryptoSysPrep_Specialize: assigned CAPI machine guid "44d42aa2-dee4-4023-bea5-d2f166bbb42c"
    2010-06-21 14:22:55, Info                         capisp.dll::DisableAdministratorIfApplicable disabled the admin account.
    2010-06-21 14:22:55, Info                         capisp.dll::CryptoSysPrep_Specialize: returning 5
    2010-06-21 14:22:55, Error      [0x0f0082] SYSPRP LaunchDll:Failure occurred while executing 'C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize', returned error code 5[gle=0x000003e5]
    2010-06-21 14:22:55, Info                  IBS    Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers
    2010-06-21 14:22:55, Info                  IBS    Callback_Specialize: Specialize return: [5]
    2010-06-21 14:22:55, Error      [0x060435] IBS    Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x5
    2010-06-21 14:22:55, Info       [0x0640ae] IBSLIB PublishMessage: Publishing message [***Windows kann nicht für die Ausführung auf der Hardware dieses Computers konfiguriert werden.]
    The mentioned error is the only one.
    ANY help is very appreciated!
    From Colonel Gizmo

    Hi,
    Regarding the returned error code, error code 0x5 is a “Access denied” error. It seems that the sysprep disables the administrator account, it can’t
    process the capisp.dll and pass CryptoSysPrep_Specialize. To resolve this kind of issue, I would like to suggest:
    1.       
    Ensure that you deploy image running as Administrator account.
    2.       
    Mount the image and check if the capisp.dll file exists and try taking ownership of it.
    3.       
    Open Registry Editor and navigate to the following path:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\Sysprep\Specialize
    Check if there is an entry with the Data:
    C:\Windows\system32\capisp.dll,CryptoSysPrep_Specialize , make sure it is spelled correctly and check the permissions on the above key.
    4.       
    Then deploy again.
    Best Regards
    Dale
    Please remember to click “Mark as Answer” on the post that helps you.

  • Using MDT to re-join computers to a domain after a re-image

    Since 2010 we have been using WDS to build, capture and deploy our image across our organisation (A High School) which has worked well enough. While WDS can do all this the build and capture is a little clunky and relies on you to manually installing all
    programmes and then mounting the WIM file and inject the drivers so I have moved us onto MDT for the build and capture before importing the finished WIM file into WDS for deployment.
    This has worked much better as MDT makes it much quicker to get an image up and going (programme silent installs, testing is much quicker etc) and drive management is as simple as telling MDT to put ALL the drivers you want into the image but I have been
    reading that you should link MDT and WDS together.
    I followed the instruction and imported the LiteTouchPE wim file into WDS and we are able to PXE boot right into MDT and either make a new image or capture the one we are working on but I am trying to automate the deployment so it is more like what we have
    when just using WDS for deployment. Because I want to retain the ability to use MDT to make a new image I cannot customise the customesettings.ini file too much and instead I am relying on MDT task sequences for must of the customisations.
    Currently all our systems are pre-staged into WDS (I think it is actually Active Directory at the end of the day but you use wdsutil to pre-stage them) so when we boot into PXE WDS deploys and configures the machines using WDSClientUnattend and ImageUnattend
    XML file so that once the deployment is finished it is sitting at the logon screen waiting for the user to login already joined to the domain and our wireless network.
    I am having trouble trying to achieve this same result using our WDS + MDT combo with the main sticking point being trying to re-join the computer back to the domain (we re-image machines constantly so re-join back to the domain is a must). I wrote/found
    a PowerShell script that does the domain join but because an account already exists (all our machines are pre-staged under their service tag and GUID) it throws an error about their already being an account with that name (the computer still appear to join
    the domain and I can logon using my domain account). Because of this error MDT borks the deployment and doesn't finish up and complains about deployment being in progress etc.
    Is using WDS to boot the LiteTouchPE and then deploying through MDT the best way or are we better off going back to using MDT to do the build and capture and then using WDS and it's pre-staging to do the deploy? I really like that with MDT I can have a little
    more control over driver deployment (recently had a problem where we got a new laptop and injecting the new drivers into the WIM broke the entire image for all our machines except the new one) and software at the time of the re-image (I cannot install the
    Lenovo hotkey software in a virtual machine because it does a hardware check and fails to install so either the entire image needs to be made on a Lenovo or the software doesn't get installed).
    I am currently making a Windows 8.1.1 x64 Enterprise SOE/MOE/whatever you would like to call it using MDT 2013 with WDS running on Windows Server 2012 R2 x64.

    Hello,
    It is better to use so-called "thin" images. These contain only the operating system (in a facility and captures vm). Subsequently pilots and soft will be deployed by the bais of MTD. 
    For drivers I recommend you to use selection profiles. Moreover it is necessary to put a condition in step "Inject Drivers". Condition Type: Variable called MODEL, variable value Latitude E6430 (change the value to the desired model). It is necessary
    to add more step Inject Drivers that type of position. 
    Application level, you import the different applications in MDT allowing you to select only the desired wizard when applications. If you want to automate this step you will need to indicate statically in the task sequence to install applications, this will
    require the creation of several task sequence.
    Best Regards
    Well I am well aware the Microsoft recommends a thin image it is simply not practical in a School environment where Students change in and our of subjects and where the combination of subject specific software is nearly infinite the overhead is too great
    (maybe if we used something like SCCM where we could deploy applications based on OU or group membership).
    All your other points aside my problem/issue/question which appears to have been lost is, how do I rejoin a computer to the domain using MDT?  We re-image laptops constantly and using WDS they rejoin with no problems but using MDT an error is thrown because
    the account already exists.  In WDS we have all our machines pre-staged so is there an MDT equivalent that will let me re-image a laptop and have it re-join the domain under the same account without throwing and error.

  • KB2918614 Breaks MDT2012 Update 1 Task Sequence "Install Application" Items on Windows 7 deployments

    Consider the following scenario:
    You have a WDS deployment environment for your enterprise running on Windows Server 2008 R2.
    You use MDT 2012 Update 01 to create a Windows 7 Task Sequence for workstation deployment. 
    The task sequence has an "Install Application" task to install Symantec Endpoint Protection 12.1 RU4 MP1b.
    You either refresh your reference build to incorporate KB2918614 or you publish the update via WSUS and use the Install Updates task in the task sequence prior to the "Install Application" task to install the hotfix. 
    In this scenario, the "Install Application" task starts but never completes. The Symantec installation executable is never called and does not show up in Task Manager. All subsequent "Install Application" tasks exhibit the same behavior.
    No error messages are generated. Eventually the Task Sequence itself times out and moves on to the next task. 
    If you remove update KB2918614 from your reference build or unapprove it from your WSUS server, all "Install Application" tasks in the task sequence execute correctly. 
    Has anyone else experienced a similar issues with deployments? My hunch is that the problem is not specific to the application being installed, and it may also be a problem for environments using SCCM to install Windows 7. I have not had a chance to explore
    this more, so I kept my scenario to the facts that I have directly observed.
    Thanks,
    Rick Reuling
    Walker IT Group, LLC

    Quite the few incorrect assumptions, but thank you for your input. I disagree with your methodology and irrelevant conclusions.
    Problem is quite clearly seen under easily reproducible conditions, which according to your description was not correctly proscribed. No one ever said the patch did not install correctly.
    Whether the root cause is that mainstream third party applications are utilizing Microsoft solution accelerator proscribed methods that a privately reported vulnerability implicated as harmful; and thus the aforementioned patch changed the
    expected behaviour to the detriment of mainstream certified applications in an unattended environment is at fault is up for discussion. Jamal's experience implicates the overall method in not only MDT but also SCCM so there stands a reasonable chance
    that the problem exhibits on a further scale beyond the MDT environment.
    However, as has been documented on a real world basis in the context of actual running environments (in which many do indeed still run Windows 7, much to all our chagrin and your self-declared shock) the issue still exists, and we must decline
    your proposed solution as being appropriate to the described scenario. Your response clearly does not duplicate nor even attempt to recreate the problem space, If you had read clearly you would have seen we had already inserted a reboot in between the Windows
    Update step in the TS and the "Install Application" step. Of course there are many other potential variables, hence why one should be quite careful about declaring an explicit problem or an explicit solution. 
    I believe Mike Niehaus clearly indicated the next step, and Jamal has confirmed the immediate workaround. I will encourage my clients to raise the issue through their EA channel.
    Regards,
    Rick

Maybe you are looking for