Change pointer to IP address of PXE server WDS

Question

I have a page with a couple CSS files. I want to call a new CSS file (not present on page load) when a button is clicked. I want the other CSS files to remain unchanged though.

This works - but, it seems to replace ALL the css files and ONLY pulls styles from the new one I call. How can I keep the existing styles in place and only override what I'm targeting in this new file?

$(function () {
    $('button').click(function () {
        $('link').attr('href', 'foo.css');
    });
});

Solution

Ultimately your PXE clients need to be told where to find WDS1 as WDS2 is still responding to their requests.

The PXE client will acquire an address from a DHCP server and then locate the PXE server, both of which are performed using UDP broadcasts. If the two servers are separated by a router (or on different segments) then the broadcasts won't be reaching WDS1, so I am assuming that your two WDS servers are on different network segments.

That I know of, there are two possibilities for configuring which server the clients use for deployment: using DHCP options and using IP helper addresses.

• DHCP options 66 and 67 can be configured to direct the client to the correct server.
• IP helper addresses are used to forward UDP broadcasts onto an address on a different network segment.

See the following article from the Microsoft KB which explains the difference between the two in quite some detail: http://support.microsoft.com/kb/926172

This one should also help you on your way: Managing Network Boot Programs (Microsoft TechNet)

Which option is better for you could probably be answered with a bit more detail about the network infrastructure that lies under your two organisations and their WDS servers, for example what address ranges are being used, routing mechanisms in place, how many DHCP servers and where they are placed, operating system versions, etc.

Comments

[David H.]

This question was answered many times on SO: stackoverflow.com/questions/5680657/adding-css-file-with-jqu‌​ery

[Robert]

Your code doesn't work because it's not doing what you think it should do. You're REPLACING rather than adding. The duplicate solution I (and others) have provided answers your DESIRED results.

[Split71]

Check the 66 and 67 options on the address for the WDS2 server and find out where and if it's getting it's bootstrap file from. If you can't find it there it may be set to broadcast as a PXE service in your routing.

[MDMarra]

@Split71 As outlined in john's answer, 66 and 67 don't have to be defined if you use a helper address.

[john]

@MDMArra Apologies, I edited my answer to be more detailed. I didn't mention IP helper before Split71 commented.

[Kenny Bones]

Just a thought, isn't it possible to just copy the contents of the entire Image folder to the other domain?

[john]

Yes it probably is a viable alternative, but that wasn't requested, and the OP might be wishing to consolidate for ease of maintenance.

[Kenny Bones]

Just for the record, I only set option 66 and 67 in the DHCP. Option 66 was set to the IP address of the new server. And 67 was set to \boot\x86\wdsnbp.com. This worked immediatly. But because of the increased network traffic, I had to copy the deployment share to the local server instead.