My Network Boot Setup - WDS and Syslinux - Inst Windows in mins + boot CDs over LAN

[FoolishTech]

Next create two new directories in your WDS share:
\\<server>\REMINST\Boot\x86\Linux
\\<server>\REMINST\Boot\x86\pxelinux.cfg

2.Modify the DEFAULT file located in \\<server>\REMINST\Boot\x86\pxelinux.cfg directory (and same in \x64) to include the menu entries for your boot images.

The following bit's of information seem to conflict, one indicates the folders are only created in x86, and the other indicates that they exist in both x86 and x64.

If the default file exists in both, how do select which menu to use?

Sorry, you do create the directories in both x86 and x64. You will want your DEFAULT file the same in both as well.

You don't actually select the initial menu defined in the DEFAULT file (x86 or x64), it is done automatic by WDS depending on what platform you boot from; example it detects if your platform is x64 and automatically gives you that menu (DEFAULT file).

This is why we have to put the same files in both x86 and x64 directories, (including your boot images) so they are accessible by all platforms. I suspect if we used the wdsutil commands for both x86 and x64 with the /architecture:x86 switch this wouldn't be necessary, but I figure at some point I might want different options for x64 *shrug*

 

[TLE]

Ok that makes sense, I tested it out at lunchtime with ERD Commander 6.5 and it worked like a dream.

However when I selected Windows Deployment Services, it just seemed to refresh the page and not do anything at all. Am going to play a little more this evening to see if I can pin it down, unless you can think of anything I may have missed.

Thanks for the help.

 

[FoolishTech]

Hmm... Make sure you didn't miss this step:

Copy pxeboot.n12 and rename it to pxeboot.0
Copy abortpxe.com and rename it to abortpxe.0

Those are copies NOT RENAMES, so the same file which is named both pxeboot.n12 and pxeboot.0 should appear in each of your x86 and x64 directories and same with abortpxe.com and abortpxe.0

Also make sure your WDS label in the DEFAULT files has the line: KERNEL pxeboot.0

 

[TLE]

I have just double checked the files now. All the files are there.

I will try this out again when I get home this evening.

 

[TLE]

I have to say that this is great, should have done it a long time ago. Means no more having to duplicate disks.

Here is what I have added so far and are working:
Windows Password Reset 7.0
ERD 6.5 Commander x64
ERD 6.5 Commander x86
ERD 6 Commander x64
ERD 6 Commander x86
ERD 5 Commander
Avast Bart CD
MHDD
Memtest86+
Easeus Partition Manager
Acronis

I couldn't get the following to work fully:
Dr. Web Cure IT
Kaspersky Rescue

 

[cyabro]

I'm just having a weird issue with our setup.

I created a clean XP Pro setup on a computer and captured the image and when I boot from any machine that clean XP Pro shows up on the list along with Win7 and Vista options, which is great.

We then got in 8 PC's, all of the exact same model, that needed to be formated and reloaded with XP Pro so they could be sold on.
So I setup XP Pro on one of them, put in all the drivers and configured everything to how I wanted them all to be, then sysprep'd and captured the image.
This new XP Pro image shows up on the WDS server under the Windows XP group, along with the clean XP Pro image I made first, however when booting from any machine the new XP Pro image doesn't show up on the list at all.
The original clean XP Pro is listed along with Win7 & vista options.

Why won't this new XP image show up on the list to be deployed?

I thought maybe I had done something wrong so deleted the image from the WDS server and captured it again but made no difference.

 

[FoolishTech]

Question: Have you tried deploying your new XP image to the SAME machine you did the new capture from? If the new XP image is visible in the install list on that same machine, then likely your other machines aren't identical maybe they are a different architecture or have a different HAL.

As stated I'm not an expert, but I'll try and do some research on this.

 

[cyabro]

Question: Have you tried deploying your new XP image to the SAME machine you did the new capture from? If the new XP image is visible in the install list on that same machine, then likely your other machines aren't identical maybe they are a different architecture or have a different HAL.

As stated I'm not an expert, but I'll try and do some research on this.

Yes I did try on the original machine and no it still didn't show up on the list.

 

[krishal]

awesome

Thanks for sharing.

 

[spetsnyc]

Guys,
Just to add up. If you have WDS running, you can also install MDT2010/2012- also for FREE. When you use MDT2010 tool kit you can do deploy images, work on image (Win7) for example, install Software. When you use MDT2010 you dont need to use Sysprep because it installs fresh copy of OS. Try it out. I deploy 1 Win7+ Office 2007+Java+Flash+QuickTime and it takes only 15 min per package. Eventhough WDS gives you an oportunity to put drivers into boot.wim but much easier is done in the MDT- different task sequences.

 

[DCGPX]

Ok - Got WDS Server up and running as DC with DNS/DCHP all Ok if I use server on its own network

Now my problem - I use my BT Router normally for DCHP on the network, Im still learning Servers so has anyone set this up with DCHP/DNS turned off and an ISP router doing DNS/DCHP etc?

I want to put the WDS server onto normal network so no matter where I plug a PC in ( I have access point dotted around) I can PXE boot and it picks up the server.

I havent done anything yet other than set server up, next steps are tomorrow.

I assume it cant be as simple as turning off DNS/DCHP on server, giving it a static address on same network as router and add to same network.

I'll google and play but if anyone has pointers I'd appreciate a heads up.

Thanks

 

[Martyn]

Ok - Got WDS Server up and running as DC with DNS/DCHP all Ok if I use server on its own network

Now my problem - I use my BT Router normally for DCHP on the network, Im still learning Servers so has anyone set this up with DCHP/DNS turned off and an ISP router doing DNS/DCHP etc?

I want to put the WDS server onto normal network so no matter where I plug a PC in ( I have access point dotted around) I can PXE boot and it picks up the server.

I havent done anything yet other than set server up, next steps are tomorrow.

I assume it cant be as simple as turning off DNS/DCHP on server, giving it a static address on same network as router and add to same network.

I'll google and play but if anyone has pointers I'd appreciate a heads up.

Thanks

I've started to set this up and am using a static ip sbs 2011 controlling the dns and dhcp. Turned dhcp off on the router.

 

[DCGPX]

I've started to set this up and am using a static ip sbs 2011 controlling the dns and dhcp. Turned dhcp off on the router.

Thought to do that but not sure effect that will have on other PCs.

Sides I'd be interested in trying to do it with router first.

I never got round to separating Business from home network so I'd have to rethink wife/sons PC/Xbox/Wii/WHS setup accessing through a DC.

I'll draw a network map and see what it all looks like - Now might be the time to separate the two

Not sure if I have to have access through server for net, forwarding all internet requests to router - Google here I come!!

As I said servers a new arena.

Never been an issue with infections on home mixed network as I only ever connect a clients PC at end of repairs, so far not caused issues.

 

[Martyn]

The other computers will just pick up an ip address and dns address out of the server scope.

 

[DCGPX]

The other computers will just pick up an ip address and dns address out of the server scope.

Yeah just figured that out, just need to set DCHP scope to same sub as existing with DNS to BTs DNS so dont have to refigure every device.

I'll have a play tomorrow and switch router DCHP off to see what happens. I'll set each to static IP and just use allocated IPs for new connections.

I really want to get this working so I can look at WDS/WSUS/MDT setup.

Should ease things massively in long run - And I learn a damn site mor on basic server setup.

 

[spetsnyc]

Hey DCGPX,
If you want to setup WDS/WSUS/MDT:

1. You can install and configure MDT first.
2. Install and config WDS ( you will be using images from MDT). When you boot a computer into PXE and WDS picks up, it will chain to MDT. MDT will finish the job. Try to get MDT working with installing OS first only. After you can config software intallation. I was able to deploy WIn7 and WinXp on at least 100 Desktops/Laptops.

3.WSUS is done thru the Group Policy. I set up 2 WSUS (upstream and downstream). THey work fine. On clients PCs you will see when WSUS takes effect.

 

[Slaters Kustum Machines]

My Untangle box is handling my DNS and DHCP, but my WDS box is SBS 2011 Essentials and not running as a Domain Controller.

 

[DCGPX]

Hey DCGPX,
If you want to setup WDS/WSUS/MDT:

1. You can install and configure MDT first.
2. Install and config WDS ( you will be using images from MDT). When you boot a computer into PXE and WDS picks up, it will chain to MDT. MDT will finish the job. Try to get MDT working with installing OS first only. After you can config software intallation. I was able to deploy WIn7 and WinXp on at least 100 Desktops/Laptops.

3.WSUS is done thru the Group Policy. I set up 2 WSUS (upstream and downstream). THey work fine. On clients PCs you will see when WSUS takes effect.

Already got WDS working on its own using FoolishTechs guide, once I get the DCHP router issue figured I'll be looking at MDT/WSUS.

WSUS more for info/learning as my broadband speed doesnt warrant it, normal updates just as fast.

All this on hold though as wife was emergency admitted to hospital with liver complications last night, so not a priority, getting the kids sorted each day and seeing her are!

I'll try and spend some time at night to look at it if not too knackered!

Massive respect yet again to mums! How the hell do they do it!!

 

[spetsnyc]

Already got WDS working on its own using FoolishTechs guide, once I get the DCHP router issue figured I'll be looking at MDT/WSUS.

WSUS more for info/learning as my broadband speed doesnt warrant it, normal updates just as fast.

All this on hold though as wife was emergency admitted to hospital with liver complications last night, so not a priority, getting the kids sorted each day and seeing her are!

I'll try and spend some time at night to look at it if not too knackered!

Massive respect yet again to mums! How the hell do they do it!!

Sorry to hear about that man. Speedy Recovery to your wife.

 

[DCGPX]

Thanks, I'm sure she will.