Resolver

I'd set up a WDS test server and test workstations a few months ago and had everything working nicely, including unattend.xml and sysprep.inf configuration files. Last week, I set up a new server and grabbed some computers in need of a standard image. But now I can't get it working!! If I capture an image, I can redeploy it to the same box and reboot successfully to test the image, but If I deploy it to a different computer, as soon as it boots, I get a bluescreen. I think the problem is that I'm not using a standard hardware platform. In my initial testing, I used two identical computers. This time I built the image on an HP, then deployed it to a Dell, which failed. Then I grabbed two Dells, but they were different models. Finally, I found two Dim 170L's but when it failed on that too, I noticed the one 170L's motherboard had been replaced with an Asus instead of the standard Dell one. So, my long winded question is, how much wiggle room is there in deploying images across different models of computer hardware?

clean & classy.

I've been searching Joomla, and doing some googling, but can't quite find what I'm looking for. I'd like to find an open source knowledge base that would allow us to set content/categories to be viewed only by internal users (by using AD authentication would be ideal), or viewable to both internal users and outside customers via a webportal. Thanks for any suggestions.

Bluetooth, I come across this problem constantly, luckily there's an easy fix. 1. On the server, make sure that the LPR service is running. control panel -> add/remove programs -> add/remove windows components -> Other Network File and Print Services -> Print Services for Unix Then, in Administrative Tools -> Services -> make sure that TCP/IP Print Server is set to Automatic start 2. On the Laptop, add the LPR service. control panel -> Programs and Features -> Turn windows features on and off -> Print and Document Services -> LPR Port Monitor 3. On the Laptop, download the needed x64 driver, and go to Add a printer -> Add a local printer -> Create a new port -> LPR Port -> Top field is the name/IP of the x86 print server -> Bottom field is the name of the shared printer (for example.... type \\server\ into the run box to see what is publicly shared off the server. The name of the printer as you see it there, is the name you want to enter in the second box) -> finish the rest of the printer install normally. Whats going to happen is when the user prints, the job will be processed on the x64 machine using the local driver, but the output of that will go to the shared printer on the server. The server doesn't have to do any processing, and it just forwards the data back out to the printer. I've done this many times, and had to make a few adjustments here and there, but haven't had a case yet where I couldn't make it work. Let me know if you have any problems with it.