Monday, 18 February 2013

ConfigMgr 2012 / SCCM 2012 SP1 Step by Step Guide Part 13: Operating System Deployment - Deploying new computers

Back to main menu

Parts 8 -12 described how to create a complete OSD solution. Part 13 now describes the process of actually building the computers.

Remember that our task sequence has been deployed to "Unknown Computers". If your computer is already known to Config Mgr you must first delete it from the database. It could help if you first ran the Config Mgr report to locate a particular MAC address


Turn on computer and press F12 for network boot (or for one time boot menu)

Boot from Network Controller





When PXE point is located via DHCP you are prompted to press F12 to continue. You don't have much time here (this is a BIOS issue - not Config Mgr) so press F12 quickly



Boot image is downloaded and the computer restarts into Windows PE



Enter your PXE password


Choose your task sequence


Double click on OSDComputerName


Enter required computer name and click OK


Click Next to continue (no further input is required)


Drive is formatted



Image file is downloaded



Image file is applied to the formatted drive













Posted by at
Labels: , ,

55 comments:

  1. Unknown4 June 2013 at 19:00

    Dear Gerry
    Good night
    could you please help me in this issue
    this message happened after i entered computer name
    Failed to run Task sequence: The task sequence cannot be run because the program files for C01xxxxx cannot be located on a distribution point

    ReplyDelete
    Replies
    1. Anonymous23 January 2014 at 09:33

      Hello
      I have the same problem like ITMAN Demo (the task sequence cannot be run because this program file ....) and i don't have solution can you help me please thanks

      Delete
    2. Gerry Hampson23 January 2014 at 11:38

      This means that one of the packages that your task sequence requires is not available on your Distribution Point. There could be a number of reasons for this including:
      - you have not actually distributed the package to the DP
      - there is something wrong with your DP

      Have a look at the SMSTS.Log file and this will tell you which package(s) are giving bother.
      Also look a the DISTMGR.log file for issues with the DP.

      Delete
  2. Unknown5 June 2013 at 15:28

    Dear Gerry
    the previous issue was solved
    but in the end of task sequence deployment show this error ,Configuration Manager 2012 failed with Error code 0×00000001,however after deployment end ..OS deployed properly
    please advise

    ReplyDelete
  3. Gerry Hampson8 June 2013 at 10:36

    You should examine the smsts.log file on the client for errors

    ReplyDelete
  4. Christophe Girardy9 June 2013 at 00:28

    Dear Gerry
    I want to thank you for your guide. It's the best guide I have found till now.

    My host computer is installed with Windows 8 Pro x64.
    I'm using Hyper-V and I have installed 6 Windows 2012 servers VMs (2 AD / 1 WSUS / 1 File Server / 1 SCCM 2012 SP1).
    I have installed Windows 8 Enterprise in a VM (basic install without any modification) and captured it as described in your guide.
    I'm trying to deploy this captured image to another VM that has no OS installed.
    I followed your guide from step 1 to this step and I have 1 problem reported as : Task Sequence: xxxx has failed with the error code (0x80070057). For more information........

    I have checked that everything is ok regarding Boundary Groups as you described in Step 6 (http://www.gerryhampsonsccm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part-6.html).

    What can I do to find out what's wrong ?
    Thanks

    ReplyDelete
    Replies
    1. Adam21 December 2013 at 03:41

      I'm sure you figured this out by now, but for other readers I had this exact same problem and it turned out that I had used a x64 boot image to capture a x86 operating system image.

      Delete
  5. Gerry Hampson9 June 2013 at 11:20

    0x80070057 means "Parameter not found", which is too generic to tell you much. You should check the smsts.log file for more details.
    x:\Windows\Temp\SMSTSLOG\SMSTS.LOG

    Also
    - have you configured a boundary group and added your boundary DP to it?
    - have you configured a network access account?
    - perhaps this is a NIC issue - usually, in a VM, you don't have to worry about NIC drivers. However, press F8 before the TS fails and see if you can get an IP address.

    After you examine the log file, search on Technet Forum for similar issues

    http://social.technet.microsoft.com/Forums/en-US/category/systemcenter2012configurationmanager

    ReplyDelete
  6. Christophe Girardy9 June 2013 at 12:41

    This comment has been removed by the author.

    ReplyDelete
  7. Christophe Girardy9 June 2013 at 16:10

    Hi again,

    Thanks for your answers.

    I have configured a boundary group and the computer is appearing in my devices as "unknown".
    The network access account is also configured.
    The VM has an IP address.

    Here are all the failed sequences in the log file :
    - Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type

    - Failed to run the action: Apply Operating System. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.

    - The parameter is incorrect. (Error: 80070057; Source: Windows)
    Failed to run the last action: Apply Operating System. Execution of task sequence failed.

    - The parameter is incorrect. (Error: 80070057; Source: Windows)

    - The execution of the group (Install Operating System) has failed and the execution has been aborted. An action failed.
    Operation aborted (Error: 80004004; Source: Windows)

    I'm gonna look for this in the Technet forum but it's always quicker to ask the right guy than to look for an answer everywhere :)
    Thanks

    ReplyDelete
    Replies
    1. Gerry Hampson10 June 2013 at 19:30

      Those errors really don't tell us much Christophe. There must be more in the log.

      Delete
  8. Christophe Girardy9 June 2013 at 16:20

    One more question : should it be running out of the box when you create a default "Build and capture a reference operating system image" task ?
    Thanks

    ReplyDelete
    Replies
    1. Gerry Hampson10 June 2013 at 19:30

      I don't quite understand this question Cristophe

      Delete
    2. Christophe Girardy11 June 2013 at 22:53

      OK sorry about that.
      I meant, when you create a new task sequence to deploy a raw Windows 8 operating system, should it be running without any editing anything ?
      I have partly solved my problem : I finally understood that, when it's a raw windows 8 operating system you want to deploy, you need to add this OS into Operating System Installers then edit the task sequence and change the Apply Operating System task from "Apply Operating System from a captured image" to "Apply operating system from an original installation source"..
      This allowed me to deploy Windows 8 in a bare metal VM.
      Thanks again for your answers

      Delete
    3. Anonymous14 October 2014 at 02:47

      k

      Delete
  9. Mosqueteiro 26 January 2014 at 13:40

    I Gerry
    I want to thank you for your guide...It´s splendid
    I have an error in step process "Drive is formatted" image, when in my case don´t show the "downloading Win7first.wim". I have a error "task sequence: Deploy W7x64 SP1 has failed with the error code (0x80070002). For more information..."

    What can I do to find out what's wrong ?
    Thanks

    ReplyDelete
    Replies
    1. Gerry Hampson7 January 2014 at 10:57

      0x80070002 = The system cannot find the file specified.
      Have you configured a network access account?

      Delete
    2. Mosqueteiro 27 January 2014 at 17:28

      I Gerry,

      in fact the problem was in the account that i select in network access...I choose another account and the problem disappeared...This scenario was for a virtual machine that I created in Hyper-V and worked properly.

      however I have a problem if the machine is physically...I have a physical machine (clean operating system) it gives me the error "PXE Boot aborted. Booting to next device...PXE-M0F: Exiting PXE ROM"

      Do you know what´s wrong??

      Delete
    3. Gerry Hampson7 January 2014 at 19:55

      This usually means that no task sequence has been deployed to this device. Are you deploying to "Unknown Computers? If so this would suggest that your physical device is "known" ie there is a record in the ConfigMgr database.

      Run a report to find a specific MAC address. This will find the entry so that you can delete it.

      This is common in testing.

      Delete
    4. Mosqueteiro 28 January 2014 at 10:36

      I Gerry,

      At the beginning I created a new collection and I had the computer in this collection by using the import computer information - import single computer and enter a name and the MAC Address. In the task sequence I deployed to this collection but the error still.

      Now, I delete the computer in the devices list for use the collection "Unknow Computers" but the error still.

      This error happens with all physical computers that who has or had the agent installed. For virtual machines to be created is working well because it will use the "Unknow Computers".

      Deleting computer in database and trying to deploy is not result...
      Do I have to delete some more information somewhere else?

      Thanks Gerry

      Delete
    5. Gerry Hampson8 January 2014 at 13:51

      If you cannot use "Unknown Computers" then the physical computer must be "known" - ie there is an entry for this MAC address in the SCCM database.

      Run the report "MAC - Computers with a specific MAC address" to find this and delete it. Remember it may not have the name you think. It could be called Unknown as there may have been a previously failed attempt during testing.

      Delete
    6. Mosqueteiro 28 January 2014 at 18:02

      I Gerry,

      It is possible to have more than one computer with the same GUID???
      If this is not possible the problem may be that...Because I have 6 computers with the same GUID as one of them is that computer.

      Thank´s

      Delete
    7. Gerry Hampson9 January 2014 at 08:35

      I've seen it happen but it shouldn't. This is a mistake by your vendor. This will cause problems in OSD via PXE. The vendor should provide a utility to change the GUID - many do. Otherwise you may have to implement "Banned GUIDs" registry key.

      Have a look here

      http://social.technet.microsoft.com/Forums/en-US/c30b2692-8cd0-4fb8-9639-99306e3bdb80/troubleshooting-pxe-boots?forum=configmanagerosd

      Delete
    8. Mosqueteiro 210 January 2014 at 15:24

      I Gerry,

      The problem was with the same GUID and resolved the issue of F12. I put the GUID as Banned GUIDs in registry key and it worked.

      I have a task sequence with windows 7 and I deploying to "Unknown Computers", but in this device after the F12 it says there is not a task sequence for it...this device does not exist in the database so it's an unknown computer. It´s correct???

      Thank´s

      Delete
    9. Mosqueteiro 210 January 2014 at 16:38

      This comment has been removed by the author.

      Delete
    10. Mosqueteiro 210 January 2014 at 17:49

      I Gerry,

      I analyzed the file SMSTS.LOG and found that now the MAC and GUID that appears is that another machine. This happened after I have created the "Banned GUIDs" registry key. Do you know how I change it??

      Thank´s

      Delete
    11. Gerry Hampson11 January 2014 at 15:28

      I don't quite understand some of this. Firstly, you have taken the line from the SMSTS.LOG totally out of context. It means nothing without seeing more of the log.

      If a device does not exist in the databse then it is unknown - that is correct. Are you saying that you now have duplicate MAC addresses also? Are you using Virtual Machines?

      Delete
  10. Mosqueteiro 211 January 2014 at 16:36

    I Gerry,

    First I have several machines with the same GUID (duplicate SMBIOS GUIDs) so it was giving error on a PXE boot. To resolve this error I have created the "Banned GUIDs" registry key on the server.

    I stopped having this error on startup but I have an error when deploy the task sequence image. Analyzing the file "SMSTS.LOG" the computer name and mac address that appears is that another computer exists on the network but with the same GUID.

    Do you know how I change it??

    Thank´s

    ReplyDelete
    Replies
    1. Gerry Hampson11 January 2014 at 18:55

      When you PXE boot a computer both MAC address and GUID are used in the process. If either exists in the database then your computer is known. This is why duplicate GUIDs are a problem. Your vendor should be able to give you a utility to change the dodgy GUIDs.
      When you implement the "Banned GUIDs" reg key you are changing the process so that the MAC address only will be used for computers with the duplicate GUID. You have to add each duplicate GUID as you come across them for this to work.

      It would be so much easier for you to contact your vendor for support on this. It would be the best practice way of dealing with the problem.

      Delete
  11. Mosqueteiro 220 January 2014 at 16:08

    I Gerry,

    Thanks for the help .... the manufacturer provided me a utility to resolve the issue of duplicate.

    Thank´s for everything

    ReplyDelete
    Replies
    1. Gerry Hampson20 January 2014 at 20:26

      That's good. Thanks for letting me know. Glad to help.

      Delete
  12. Mosqueteiro 231 January 2014 at 15:12

    I Gerry,

    Recently the folder of the sql logs sccm got many logs files S: \ MSSQL10.SCCM \ MSSQL \ Log \ SQLDump4674.log and SQLDump4674.mdmp).

    How can I do to have less files in this folder?

    Thank´s for everything

    ReplyDelete
    Replies
    1. Gerry Hampson31 January 2014 at 16:06

      That's not normal. You need to get advice from a SQL DBA.

      Delete
  13. Ruben18 February 2014 at 20:52

    Hi Gerry:
    I have deployed two Boot Images (x86 and x64). I have prepared two task sequences, for each of the two Images. Then I boot a x86 computer in PXE and it's showing me the following error: This 64-biy application couldn't load because your pc..... It is showing me just the Microsoft Windows PE (x64) option.

    Why is not showing the Microsoft Windows PE(x86) option? Why is assuming just the x64?

    ReplyDelete
    Replies
    1. Gerry Hampson19 February 2014 at 11:32

      Did you actually distribute both boot images? Can you see them in Monitoring > Distribution Status > Content Status

      Delete
    2. Ruben19 February 2014 at 13:07

      That's right, I distributed both images and I can see them both in Monitoring > Distribution Status >Content Status and they are 100% compliance

      Delete
    3. Ruben19 February 2014 at 22:03

      Hi, Gerry. I found the problem. I deployed both Task Secuences to the collection Unknown Computers. But In Unknown Computers I have x86 and x64 clients. It might pick another boot image when you pxe boot if you have deployed many task seqeunces with different boot images to the same Collection.

      Delete
  14. Ram23 April 2014 at 23:32

    Hi - I followed above steps and everything worked out in task sequence except the computer did not join to domain + drivers did not install and CCM Client did not install.

    After the image 1-1 and 2-2 got installed the system downloaded configuration files and I saw restart screen to reboot the system. After restart the system logged into Win 7.

    I created virtual machine in Hyper-v and did network boot. The image got downloaded without any issue and the partition are right. Not sure why the machine did not complete all the steps in task sequence.
    What log should, I look to troubleshoot the issue.
    This is a home lab environment. So no rush....

    ReplyDelete
    Replies
    1. Gerry Hampson24 April 2014 at 12:27

      Have a look at the SMSTS.log file. This normally happens when the NIC drivers are not installed in the OS. Have a look when you log in for the first time. Is there a network connection? Look in Device Manager - are there drivers missing?

      This means that you have to apply a driver package with the NIC driver (and probably other drivers too).

      Delete
  15. Ram24 April 2014 at 16:10

    Thank you Gerry.

    When, I first logged in - it immediately started to install NIC drivers and got connected to the NET. Then, I looked at device manager - there are 4 unknown devices. You are right - the issue is missing drivers. I was under the impression that no driver package is required when testing using hyper-v virtual machine. I might be wrong.

    This is what, I am going to do during this weekend.
    1. Add NIC driver to boot image from Hyper-v integration file
    2. Create driver package from Hyper-v Integration file
    3. Import driver package in SCCM by following your lab guide - I believe lab 9
    4. Modify TS to include driver package
    5. Test the deployment and see what happens

    Will open command prompt - run cmtrace to monitor the TS progress for any errors.

    I was able to find a good link on the NET - creating WinPE with Integration Services for Hyper-v for use with sccm 2012

    http://weblogs.asp.net/owscott/archive/2009/06/28/creating-winpe-with-integration-services-for-hyper-v.aspx

    I have a long way to go with sccm 2012 r2 - lot of reading, testing and learning at home lab.

    ReplyDelete
  16. Anonymous30 April 2014 at 07:37

    If you can't use PXE, how do you go about creating a bootable CD/ISO that will run WinPE? Thank you!

    ReplyDelete
    Replies
    1. Gerry Hampson1 May 2014 at 12:24

      You can just right click task sequences and create a bootable media.

      Delete
  17. Mathan12 June 2014 at 15:11

    Gerry please look in to my probelm and i have given below the log file of SMSPXE
    Client lookup reply:
    SMSPXE 12-06-2014 19:36:17 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: device is not in the database. SMSPXE 12-06-2014 19:36:17 1392 (0x0570)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 12-06-2014 19:36:17 1392 (0x0570)
    Client boot action reply:
    SMSPXE 12-06-2014 19:36:17 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: no advertisements found SMSPXE 12-06-2014 19:36:17 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: No boot action. Rejected. SMSPXE 12-06-2014 19:36:17 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: Not serviced. SMSPXE 12-06-2014 19:36:17 1392 (0x0570)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 12-06-2014 19:36:25 1392 (0x0570)
    Client boot action reply:
    SMSPXE 12-06-2014 19:36:25 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: no advertisements found SMSPXE 12-06-2014 19:36:25 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: No boot action. Rejected. SMSPXE 12-06-2014 19:36:25 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: Not serviced. SMSPXE 12-06-2014 19:36:25 1392 (0x0570)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 12-06-2014 19:36:57 1392 (0x0570)
    Client boot action reply:
    SMSPXE 12-06-2014 19:36:57 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: no advertisements found SMSPXE 12-06-2014 19:36:57 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: No boot action. Rejected. SMSPXE 12-06-2014 19:36:57 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: Not serviced. SMSPXE 12-06-2014 19:36:57 1392 (0x0570)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 12-06-2014 19:37:05 1392 (0x0570)
    Client boot action reply:
    SMSPXE 12-06-2014 19:37:05 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: no advertisements found SMSPXE 12-06-2014 19:37:05 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: No boot action. Rejected. SMSPXE 12-06-2014 19:37:05 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: Not serviced. SMSPXE 12-06-2014 19:37:05 1392 (0x0570)
    Getting boot action for unknown machine: item key: 2046820352 SMSPXE 12-06-2014 19:37:09 1392 (0x0570)
    Client boot action reply:
    SMSPXE 12-06-2014 19:37:09 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: no advertisements found SMSPXE 12-06-2014 19:37:09 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: No boot action. Rejected. SMSPXE 12-06-2014 19:37:09 1392 (0x0570)
    C8:9C:DC:A0:B8:22, 955F247C-0B36-11E1-9343-4C5CDECE2700: Not serviced. SMSPXE 12-06-2014 19:37:09 1392 (0x0570)

    ReplyDelete
  18. Anonymous27 June 2014 at 04:00

    You Should only have to remove the computer from AD, not SCCM. If you remove the computer from SCCM and you are just doing a re-image it will not re-deploy the users application during the image process.

    It will still deploy using unknown computers for a known machine in SCCM. This is my setup and works perfectly. The only reason it may not work is if you have not removed the machine from AD

    ReplyDelete
  19. Stephen8 August 2014 at 09:28

    Hi Gerry, Great Job on all the Blogs. Makes it easier for learning, one question i have installed config mgr 2012 r2 and i need to replace ghost for imaging 1000 machines, they usually put a KMS Key in and that connects to KMS Server. Should i just put in KMS key in the image and its as easy as that or is there anything else? thanks

    ReplyDelete
    Replies
    1. Gerry Hampson8 August 2014 at 16:56

      You need a client KMS key. See here

      http://technet.microsoft.com/en-us/library/jj612867.aspx

      Delete
  20. Sion19 February 2015 at 09:55

    Hi,

    i am now sucessfully deploying the image to my target computers.
    i would like to know of a way that i can add new network drivers to this image so that i can deploy it to different model computers?

    ReplyDelete
    Replies
    1. Gerry Hampson19 February 2015 at 10:08

      This is how you deal with drivers Sion

      http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part-9.html

      Delete
  21. Anonymous23 February 2015 at 12:50

    Thanks for this guide -- it does help a lot.
    Got a question regarding reference image prepared in the virtual environment to be deployed on physical PCs. We're using VMware and I installed and configured Windows 7 SP1 x64 (with all updates and software installed). I'm planning to use it to deploy physical PCs in the office. This image also contains VMware Tools. Hence my question is: if I capture this reference image, VMware Tools will also be captured right? How do I avoid it? Does it require additional deployment task sequence to uninstall VMware Tools and install proper drivers for physical machines?
    Thanks.

    ReplyDelete
    Replies
    1. Gerry Hampson25 February 2015 at 09:16

      You don't need the VMWare Tools on the reference image. Therefore you don't need to uninstall it in the task sequence. You just need a network driver. Have a look here to see how to deal with drivers and driver packages.

      http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part-9.html

      Delete
  22. Melvin3 June 2015 at 02:03

    Dear Gerry

    I have issues with the OSD. I encountered the error message when i boot from PXE:

    E55: ProxyDHCP service did not reply to request on port 4011

    Basically my settings are configured as follows:

    1) Inputted my sccm server IP address to the IP helper list
    2) Option 66 and 67 is configured from DHCP
    3) My SCCM server and DHCP are from different server (different subnets)

    I troubleshooted with the following
    1) Remove boot images from DP, removed PXE and WDS; then re-added back PXE, WDS and re-distribute the boot images
    2) Restarted the DHCP Server (due to that i previously added Option 60 for DHCP using the string PXEClient, therefore i removed Option 60 and restarted the DHCP Server services)
    3) Increased the self-signed certificates expiry date (from year 2114 to year 2200)
    4) Checked the SMSPXE.log; noticed the errors
    RequestMPKeyInformation: Send() failed.
    Failed to get information for MP: SCCM Server. 80004005.
    PXE::MP_InitializeTransport failed; 0x80004005
    PXE::MP_LookupDevice failed; 0x80004005
    PXE Provider failed to initialize MP connection. Unspecified error (Error: 80004005; Source: Windows)
    RequestMPKeyInformation: Send() failed.
    Failed to get information for MP: SCCM Server 80004005.
    PXE::MP_InitializeTransport failed; 0x80004005
    PXE::MP_ReportStatus failed; 0x80004005
    PXE::CPolicyProvider::InitializeMPConnection failed; 0x80004005

    Unsure is it the management point issue or still lies with the DHCP settings. Really need your help!!!!

    ReplyDelete
  23. Anonymous28 June 2016 at 00:35

    Hi Gerry,


    Thank you for sharing wonderful Guides for setting up SCCM.
    I always follow them :)

    I am stuck in a scenario here :
    One primary site with 6 Distribution points
    Did test for OS Deployment, worked really well
    OS and Apps got installed.

    Now, its just the OS which is getting deployment.
    None of the Apps are getting deployed.

    Hope you can help me .

    Which logs are my best bet to look at .

    Thanks
    Rahul

    ReplyDelete
    Replies
    1. Gerry Hampson29 June 2016 at 13:12

      Have a look at the smsts.log file for errors.

      Delete
  24. Anonymous28 March 2017 at 23:19

    Gerry,

    First of I would like to say thank you for all your hard work. These guides have been lifesavers.

    Question though every time I network boot I get TFTP Timeout PXE-E32. Have you ever seen this error and what would take to resolve this issue.

    ReplyDelete
    Replies
    1. Gerry Hampson30 March 2017 at 17:03

      This is a generic error telling you that no response has been received from the WDS server. How have you configured your solution?

      Delete

Subscribe to: Post Comments (Atom)