Thursday, December 04, 2008
Deployment Forum HomeDeployment Forum ArticlesDeployment Forum Download LibraryDeployment Forum Member BlogsDeployment Forum Community Forums
Community   »   Forums  
Member Login
StandardLiveID


Register
Forgot Password ?

Guests can view and read messages in the community forums, but you must register and log in to Deployment Forum before you can post messages. Click Register at the top of this page. Before posting messages, please read the forum guidelines at the bottom of this page.

Forums > Related Technologies > Windows Deployment Services
Subject: Not PXE booting Win2008 (Access Violation)
Prev Next
You are not authorized to post a reply.

AuthorMessages
JayUser is Offline

Posts:17

Send Message
03/05/2008 11:51 PM  

Hey Guys,

I am having the worst luck with WDS - First server got an error that not even Microsoft could solve! Now we have created a new server running Windows 2008. When we try to pxe boot to it we get:

PXE-T04: Access violation

Is anyone using Windows 2008, and if so can you please try running from command on another computer

tftp -i  serverip GET /boot/x86/pxeboot.com

And tell me if you get this
Error on server : Access violation.

 

We have got it on our domain and also tested on a home domain.

 

JayUser is Offline

Posts:17

Send Message
03/11/2008 5:22 PM  
It turns out the slashes were around the wrong way.. which was a problem for us because out dhcp server would only allow forward slashes in config.. In windows 2008 you can add /boot/ to the tftp registry settings.
csuhdsUser is Offline

Posts:2

Send Message
08/04/2008 6:01 PM  

Could you please elaborate on that response a bit? We're running a Linux DHCP server, and we're running into the same issue. I can sit at a Windows XP box and enter tftp -i serverip get boot\x64\pxeboot.com, and it works fine. However, when I run tftp -m binary serverip get boot/x64/pxeboot.com on a Linux machine, I get an Access violation. I have added /boot/* to HKLM/SYSTEM/CurrentControlSet/Services/WDSServer/Providers/EDSTFTP/ReadFilter, but I'm still getting the error. Our PXE clients get the PXE-T04 and PXE-E36 errors.

Thanks for any advice..
TuxUser is Offline

Posts:10

Send Message
09/04/2008 2:04 PM  

HI There,

I am not sure why you wish to do these things by hand? Setting WIN2008 and WDS is so easy compared to old theways.

I do Research and developement for my company, we mass deploy about 100 000 images a year, currently we hate RIS, becuase everything is manual.

I have documented these exact steps to setup WDS on a single box.

Load OS - Install Drivers - Activate Windows - Add role AD - Click start - run - type DCPROMO. Follolw the wizard, make you test box something like MYDOMAIN.local, when prompted to add DNS agree.

Reboot login as Domain Administrator to the domain. Add role DHCP - configure the scope you wish to use.

Open DNS console is the admin menu, configure a reverse zone. reboot on good faith. Login again, test you forward and reverse DNS.

If all works, add role Windows Deployment Services. When done luanch WDS console, right click your server and configure. If you run WDS on the server as your DHCP, then make you check the two Boxes on the DHCP tab. "Option 60 " and Listen on Port 67. If not do not check them. Do not add any images immediatly, you can but it is not nessecary. But you can reboot as a token of good faith.

Once rebooted it just works, I have loaded 78 test configurations todate, and this works seemlessly everytime. I have more indepth docs which if you want I can share with you.

You are not authorized to post a reply.
Forums > Related Technologies > Windows Deployment Services > Not PXE booting Win2008 (Access Violation)



ActiveForums 3.7
Forum Policies
Minimize

These forums are a user-supported community for IT professionals to exchange deployment tips, solutions, and techniques. For the benefit of all Deployment Forum members, please observe the following guidelines when posting to these forums:

  • We reserve the right to remove any message. Our moderators will remove all messages that are not respectful or productive. Profanity, racism, prejudice, and flaming are not tolerated.
  • Do not advertise products or services. Our moderators will remove all advertisements or service announcements. Product and service recommendations from active Deployment Forum members are encouraged, however.
  • Make sure your question isn't already answered. Before posting questions, search the forums. After ensuring that your questions are unique, post them to the most appropriate forum. This will help reduce noise in the forums.
  • Help make the most of each thread. Do not post unrelated messages to a thread. Also, if you've resolved a question outside of these forums, please share the solution with other members by posting it back to the thread.
  • Do not share confidential information. Confidential information includes product keys and addresses. Our moderators will edit any message containing confidential information, so double-check messages and their attachments before posting them.
  • Post messages using only the English language. For the benefit of all Deployment Forum members, please post your messages using the English language.

We hope that you enjoy using this community. Please submit your comments and feedback on the Comments and Feedback page or post them to the Comments, Feedback forum.
Privacy Statement  |  Terms Of Use
© 2007 Jerry Honeycutt