Trouble booting to WDS server to deploy or capture image

Hello, we have an existing WDS server running Server 2008 R2 with SP1. I am having trouble getting a Surface Pro 3 to boot to the WDS (even after creating updated deploy and capture boot images). I can get the Surface to PXE boot, and I am
able to choose the Deploy or Capture boot image, but then I get the message that an error occurred obtaining an IP address from the DHCP server. During the PXE boot, the device does obtain an IP address in the correct range. I tried adding the
Surface ethernet adapter drivers to the boot wims but since they are not signed I get errors that they cannot be added. Any suggestions?

Added drivers to boot images using DISM with the /ForceUnsigned override.

Similar Messages

Windows Deployment Services - Capturing Image

To Microsoft Technet,
I am currently a student and I have setup a fully functioning Windows Server. This Windows Server has AD, DHCP, WDS and MDT installed on to it. This server was setup so that we can re-deploy Windows to any of our computer labs and it will just be a fresh
install. My problem is that the students also need to upload (capture) an image of the OS to the server every now and then as part of the coursework. When uploading an image they are presented with this option:
Obviously when you click connect it asks for a username and password so that it can write to the folder. The students are not allowed to know the username and password because if they do then they break the server. They do this because they log on and mess
around with it. I am currently asking if there is a solution so they can connect to the server and it will automatically log them on as the admin.
These are solutions however I feel they would be inappropiate:
- Give them a username that has read / write access but block the logon.
- Allow "Everyone" to read / write thus no logon screen.
However I feel that both are a security risk as students can just join the folder from the network and delete other students work.
Instead I would like the windows server to automatically allow the connection by implementing the logon details. Is there a possible way to do this?
Thanks,
Thomas.
The image is off the internet (I did not make it).

Hi thomasjcf21,
Another possible is you can create shared folders for each student and give each student account full control permission, after they finish the OOBE they can upload their
image to WDS server.
The related third party article:
Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part I
http://blog.augustoalvarez.com.ar/2010/04/20/deploying-windows-7-using-windows-deployment-services-wds-step-by-step-part-i/
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

WDS Server 2012 R2 "The specified image file is either invalid or corrupted"

Hi,
I'm trying to setup a WDS in a 2012 R2 environment but I cannot add install image for x64 architecture.
I've managed to add boot images from both x86 and x64 architecture and install image for Windows 8.1 x86.
For everything else I receive the error message "The specified image file is either invalid or corrupted". The images used for setting up the install are 100% functional (I manualy installed the OS from them).
I tried to unconfigure, reconfigure, reinstall role, install on another machine, everything without success.
Thanks!

Hi Costache Cristi,
What account you are using when you meet this issue, please use the
domain administrator permission account to import image or please try give your image source everyone full control permission then monitor again, it seems is the permission issue.
More information:
Windows Deployment Services 101
https://technet.microsoft.com/en-us/magazine/2008.08.desktopfiles.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]

Deploying a Captured Image

I would like to broadcast a image to all machines on the network even those with SCCM clients. I have some machines that are on the domain that need to be imaged from time to time and I also have some new machines that need to be imaged. I
also need to prompt the user that starts the image process to enter the computers name. I know the computer name can be prompted by using the unknown group and prompting for the OSD but how would I do this for a machine name that is already listed
in SCCM? Would the machine fall under the unknown category once the image process starts?

Here's couple of ways to do it:
http://www.windows-noob.com/forums/index.php?/topic/5542-how-can-i-easily-prompt-for-a-computer-name-in-configuration-manager-2012/
http://t3chn1ck.wordpress.com/2009/04/24/script-to-prompt-for-system-name-in-sccm-osd/

WDS capture image on a Windows 2012 R2 server fails with a winload error

Hello,
I have been fighting with this problem for days now. I have to install
30 Win8.1 Pro PC's with WDS. The WDS service is running on a Win2012 R2
server. I added the Win 8.1 Pro boot and install images and created a capture image.
Now when I boot the reference computer I get a Boot Manager message saying that winload.exe is missing or corrupt. The original boot wim works
correctly.I removed and added the WDS role a couple of times, I tried the procedure with a 32 bit Win7 boot image, and that worked, But when I added the capture image created from the original Win8.1 boot.wim, that spoiled both capture images. I tried
the same thing with a Win2012 R2 Standard server after removing and adding the WDS role again, but the capture image generated the same error as above. .I see that since about mid-April many people has the same problem.Different solutions are suggested, but
none of them worked for me. One of them is to mount and unmount the capture image, that didn't help for me.
Any help is appreciated.
Thanks
Gabor

Do I understand correctly that if you deploy original wim file to your testPC1 it works all right, but if you deploy an image that you captured on buildPC to testPC1 then you get the winload.exe error ?
Are you formatting (deleting all the partitions) on testPC1 during the
deployment of captured image ? Can you check and confirm if the HDD seting for AHCI or IDE (yes, its still around) is the same option on both stations?

Windows 7 Professional PC hangs at "Loading files" when trying to boot with custom capture image on Windows Deployment Services.

I have created a custom capture image in WDS. Now when I try to boot my reference PC into this image the PC hangs at "Loading files". The reference PC is running Windows 7 and I am using Windows Server 2012 Standard on my server.
I have followed the instructions on how to create the custom capture image on the server to a fault. I PXE boot the PC and it shows the capture images after I hit F12. The problem is that it starts to boot and then hangs about 2/3 way through the progress
bar.
Any help would be appreciated.

Hi Derrick Logan,
We need know the detail phases your client hang, if it is irregular status, please collect the WDS log then post it. You can refer the following similar thread solution first.
How to enable logging in Windows Deployment Services (WDS) in Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, and in Windows Server 2012
http://support.microsoft.com/kb/936625/en-us
Windows is loading files... Hangs on WDS
https://social.technet.microsoft.com/Forums/windowsserver/en-US/baacadc4-830d-43e1-ace8-3292e886958e/windows-is-loading-files-hangs-on-wds?forum=winserversetup
WDS hangs at "Windows is loading files..." on a LAM jhl91 laptop
https://social.technet.microsoft.com/Forums/windowsserver/en-US/3ebb6e0b-9f05-4fee-b3c0-129c34bb879d/wds-hangs-at-windows-is-loading-files-on-a-lam-jhl91-laptop?forum=winserversetup
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Deploying captured image of reference computer - WDS & MDT

Hi, yesterday I set up MDT 2012 Update 1 on Windows 7 computer and WDS on Windows Server 2008 R2. I completed the following tasks:
Create New Deployment Share
Import Operating System (Windows 7) into Deployment Share
Import network drivers for HP Compaq Pro 6300 Small Form Factor into Deployment Share
Create Sysprep and Capture Task Sequence for capturing image of reference computer
Update Deployment Share
Prepare reference computer for imaging - install OS, drivers, apps, patches . . .
Run Sysprep and Capture Task Sequence from reference computer
Import captured image of reference computer into Deployment Share
Create Standard Client Task Sequence for deploying captured image to bare-metal computer
Use Lite_Touch wim file as WDS boot image
Run PXE boot on bare-metal computer
Enter necessary information - computer name, domain name, time zone and so on
I took more than 2 hours to complete deployment of captured image to bare-metal computer. Everything worked well but after this process finished I noticed that computer name was not the one I entered in TS nor computer was joined to the domain. Time zone
was not set. It seems that computer name, workgroup membership, time zone can not be altered in TS - they remain the same as they were on sysprepped computer.

My doubts and yours Keith were right, sysprep was not performed well at all via Sysprep and Capture Task Sequence so I did
sysprep /generalize /oobe /shutdown on reference machine and then booted it into WinPE with ImageX tool (if I am right in newest ADK dism is main tool for capturing online images instead of ImageX which is deprecated). I captured
image of Windows 7 OS partition and copied it to MDT technician computer, imported it as operating system in MDT deployment share and selected it as .wim image to deploy to new bare metal machine via Standard Client Task Sequence. During deployment entered
values for computer name, time zone were applied successfully and computer was joined to a domain. After restart message was shown with info that built in local administator account was disabled with switch user option where I could choose local account that
existed on sysprepped machine or domain account.
Conclusion: Sysprep step in Sysprep and Capture TS in MDT does not work at all. I will try this on newest version of MDT (MDT 2013) since I am testing now on MDT 2012 Update 1 version. If sysprep does not work again MDT is useless for capturing images thus
I have to use sysprep manually and then dism for capturing sysprepped image.
Thank you very much for your time and patience.

Administrator account is disable when deploying windows 7 x64 captured image

I’m using MDT 2012 update 1. I create one deployment share with two task sequence.
The task sequences are: one for windows 7 x86 and the other one is windows 7 x64.
Both are working fine until I try to sysprep and capture with all the windows updates.
Sysprep and capture windows 7 x86 with all windows update work fine. I’m able to deploy the captured image without an error.
My problem is with the windows 7 x64 captured image. I’m able to sysprep and capture the windows7 x64 with all the windows update. Once the capture is completed, I change the .win file in my windows 7 x64 task sequence to point to the new .win file (capture
image with all the windows update). When I deploy windows 7 x64 on a pc, the OS get install but boot up to the sign on screen. The Task sequence does not complete. No error message. Cannot log in as local or domain administrator, account is disable.
Why does it work with my windows 7 x86 image and not with my windows 7 x64 image?
With my windows 7 x86 image the task sequence completed successfully with no error and it logon automatically in windows but not with my windows 7 x64 image.
Both task sequences are the same.
Let me know if any info for this please.
thanks

They should both work, perhaps you missed a step when creating the x64 image.
1. Verify that the Windows 7 x64 image was created cleanly, with no errors. Sysprep ran with no errors.
2. Verify that you created the windows 7 deployment task sequence cleanly. I would do a windiff of the TS.xml and unattend.xml file from both folders in the deployment share.
3. Try running without a domain. Some domain's have a GP set to disable the local administrator account.
Keith Garner - keithga.wordpress.com

WDS Capture Image Failing to Load

Using the instructions posted here:http://social.technet.microsoft.com/wiki/contents/articles/11680.creating-a-capture-image-in-wds.aspx I created a capture image and then injected network drivers into the boot image. When trying to load the capture image
I get the error:
Status: 0x000000f Info: The boot selection failed because a required device is inaccessible.
Does anyone know what might cause this or how to resolve this issue?

Hi,
First test to add/remove any mass storage drivers when capture the image.
Also the error could relate to BCD corrupt. Check BCD entry to see if it is correct. You could try following 3 commands:
a. bcdedit /set {default} device partition=c:
b. bcdedit /set {default} osdevice partition=c:
c. bcdedit /set {bootmgr} device partition=c:
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

Problem deploying captured image

I'm testing our new SCCM 2012 and specifically OSD and deploying a captured image. The image is captured on a separate MDT config.
What I'm seeing with this image deployment is that about 90% of the times it ends with a 80070002 TS error. Examining the smsts.log shows the following:
Successfully completed the action (Setup Windows and ConfigMgr) with the exit win32 code 0
So this step seems to go fine and and then the State Restore step starts and the computer reboots to the full OS.
The group (State Restore) has been successfully started
But then I don't know what happens, non of the following steps are run, for example there's application install and so forth. It seems to parse through the remaining steps but doesn't run them and then ends with Gather Logs and stateStore on Failure.
I just can't see from smsts.log what the problem would be, what other logs should I look in to find out what's going on?

Seen that many times when doing deployments, but not on capture mentioned. In that case the error is a known bug. Workaround is to add 2 Task Sequence Variables. Unfortunately R2 is needed for that.
-SMSTSDownloadRetryCount = 5
-SMSTSDownloadRetryDelay = 15
Just have a look at my blogpost for more information on this:
http://henkhoogendoorn.blogspot.nl/2014/07/osd-ts-fails-during-package-download.html
My blogs: Henk's blog and
Virtuall | Follow Me on:
Twitter | View My Profile on:
LinkedIn

Boot an ESX 5.1 VM to my SCCM 2012 (WDS) server?

Hi folks,
I just got my SCCM 2012 server installed, configured a distribution point, published new boot.wim to distribution point.
I am trying to test booting up a 'bare metal' ESXi 5.1 VM to my SCCM 2012 (WDS) server, but fails with attached error.
Configuration Manager is looking for policy.
Anyone have a suggestion?
Thanks, romatlo

Thank you so much for responding! I must admit that this is my first install. :)
I could not find that option, so I deleted/recreated my task sequence, then found it as part of Deploy option.
I deployed the task sequence to unknown computers but I still get that message and will not boot up correctly.
I've pasted last part of my SMSPXE.log in case you see something definitive.
I did not have my WDS server role installed when enabling PXE on my DP, maybe that messed me up.
Thanks again, I may snapshot my VM here and start over on install if there is not a clue.
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6346">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: device is in the database.]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: No boot action. Aborted.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: Not serviced.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">

WDS Server Service won't start - 'An error occurred trying to start the Windows Deployment Services Server.'

I'm having issues installing starting the WDS server service on Win 2008 R2, this is happening on multiple (all 2008 R2) systems on this domain so I'm beginning to think it's either AD or network related, in event viewer I get the following error.
'An error occurred trying to start the Windows Deployment Services Server.'
Error Information: 0x0906
EventID : 257
single domain, single forest, 2008 R2 functional level, both system are virtual plugged into same vswitch on a flat network.
any ideas what might be the issue? I've never had an issue getting this working on many occasions before today and I've come to many a dead end looking at other articles thus far...
With WDS tracing enabled I get the following error information:
[4304] 09:22:11: ===>Starting logging of module [WDSServer]
[4304] 09:22:11: [UDPPorts] Policy: 1, Dynamic Port Range: 64001-65000.
[4304] 09:22:11: [RPC] Using Tcp Port 5040 for Rpc Calls.
[4304] 09:22:11: [RPC] Client Impersonation Logging=Disabled
[4304] 09:22:11: [RPC] Host Name: sccm.domain.local
[4304] 09:22:11: [RPC] NTLM/Kerberos Spn: ldap/sccm.domain.local
[4304] 09:22:11: [RPC] Initialized
[3756] 09:22:11: [RPC] Server Started.
[4304] 09:22:11: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Registered
[4304] 09:22:11: [BINLSVC] Provider Initialized.
[4304] 09:22:11: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Registered
[4304] 09:22:11: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Registered
[4304] 09:22:11: [51][WDSDDPS] [d:\w7rtm\base\ntsetup\opktools\wds\ddp\server\ddpprovider.cpp:196] Expression: , Win32 Error=0x906
[4304] 09:22:11: [WDSDDPS][RPC][Ep={FA0A27E1-C2BA-4B3B-94B2-025E82FFAA6D}] Closed
[4304] 09:22:11: [WDSDDPS][RPC][Ep={011D24AC-CB3A-4739-A339-5D2E1B5306CE}] Closed
[4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovider.cpp:144] Expression: , Win32 Error=0x906
[4304] 09:22:11: [WDSDDPS] Initialization Failed (rc=2310)
[4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsprovhdl.cpp:172] Expression: , Win32 Error=0x906
[4304] 09:22:11: [WDSDDPS] Deleted.
[4304] 09:22:11: [d:\w7rtm\base\ntsetup\opktools\wds\wdssrv\server\src\wdsservice.cpp:178] Expression: , Win32 Error=0x906
[4304] 09:22:11: [Udp] Listen Shutdown.
[3756] 09:22:11: [RPC] Server terminated (rc=0)
[4304] 09:22:11: [RPC] Listen Stopped.
[4304] 09:22:11: [BINLSVC] Shutting down
[4304] 09:22:11: [BINLSVC][RPC][Ep={5F4FB9F0-C0E3-41C1-AA00-9A7C690AC3A3}] Closed
[4304] 09:22:11: [BINLSVC] Deleted.

It seems I've found out the solution myself, the issue seems to be caused when DHCP and WDS are on the same server, The installation must identify this during the first installation of WDS but not on subsequent installations, the method to
get it working again is:
1.
Install WDS Role (using defaults)
2.
Make the following registry change:
HKLM\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSPXE\UseDhcpPorts = 0
3.
Run the following command line to initialize Windows Deployment Services:
wdsutil /initialize-server /reminst:D:\RemoteInstall
4.
Run the following command to enable the DHCP port registry setting
wdsutil /Set-Server /UseDHCPPorts:No /DHCPOption60:Yes

Boot into WDS from external PXE

Hi there,
in our Company (huge datacenter) we use ONE PXE-Bootmenu for ALL Servers (not managed by me) to boot into different deployment-systems (predominant Linux-Based deployments). Now we want to implement WDS (on Server 2012 R2) to boot into Windows-Deployment-Services.
Now I asked the Team which is managing the DHCP and PXE to add a new Option to the PXE-Bootmenu so we can boot into WDS. On that machine there is ONLY WDS-Service running.
What do they need to setup? Which file must be linked from the PXE-Menu? Which path? Do I have to make any additional settings on WDS?
When I search the web, I can only find infos how I can setup SYSLINUX on a Microsoft WDS, but not how to boot into WDS from an external PXE.
Please can someone help?
Regards
Miranda

I wasn't referring to the setup, but the menu. The menu and config files are the same regardless of what the host OS is. I posted it as a reference to how it is possible to boot WDS from PXELinux, but the specific example is where the WDS is on the same
server.
Chainloading is definately what is needed, but even that iPXE link is chainloading via HTTP (hence my Apache/IIS remark)... I do not know how you can PXE boot a WDS via HTTP.
Windows Server also has a WDSUTIL command that sends out a "browse" option with the PXE Boot request. The result ends up being you can press F11 or F9 instead of F12 and the client machine will search the network for PXE servers. This is how I
currently manage having multiple PXE servers. My default option is to press F12 to do a Legacy PXE boot to the main server, or use F11 if I want to boot to the Linux or UEFI server. See here for that example:
http://www.stephan-schwarz.net/?p=58
If Linux has a similar option, it could be used so you can choose a different PXE server. Otherwise, still have to research how to chainload to an external server, without using HTTP unless someone knows how to PXE boot WDS via HTTP.
EDIT: pxechn.c32 looks promising to add a menu option to chainload to another server:
http://www.syslinux.org/wiki/index.php/Pxechn.c32

PXE not working from WDS Server 2012

Hello,
when i try to deploy a VM using WDS/MDT the startup for contacting the WDS-server is very slow :
The WDS-server is a Server2012R2 (not preview)-server.
I have reinstalled WDS already but nothing will help.
Anybody with a solution?
Thx

Hi,
Did the installation just stuck there?
Do you have any phycial machines with the same problem?
Acctually, there is some problem when deploy VMware using WDS:
Check this article:
Issues using Enteo Netinstall or Microsoft Windows Deployment Services (WDS) to PXE boot virtual machines (1009104)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1009104
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Java Server Proxy---Deployment error?

I am trying the scenario from this blog
/people/rashmi.ramalingam2/blog/2005/06/25/an-illustration-of-java-server-proxy
I am getting deployment error
May 30, 2006 1:39:34 PM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager) [Thread[Deploy Thread,5,main]] ERROR:
[003]Deployment aborted
Settings
SDM host : sapep
SDM port : 50018
URL to deploy : file:/C:/DOCUME1/ADMINI1/LOCALS~1/Temp/temp57679JPS_EAR.ear
Deployment exception : Server sapep did not accept login request as apiadmin on port 50018 - CmdXmlFactory could not find Top Element within String: "null".
Inner exception was :
Server sapep did not accept login request as apiadmin on port 50018 - CmdXmlFactory could not find Top Element within String: "null".
Help me
Thanks

Hi Saru,
It seems u dont have the correct sdm password or someone has changed the sdm password.It has not accepted the credentials u have given during deployment.
Check with all Sap enterprise portal settings in the prefernces/NWDS
The host name,alias,port
If not done with
Try to change the sdm password using this Password trouble in SDM
restart server again after changes
even try
- Stop nd restart the sdm from yor NWDS and deploy once again
Thanks,
Swathi
Do offer pts:-)

Trouble booting to WDS server to deploy or capture image

Similar Messages

Maybe you are looking for