dude10028

Not sure if my experiences were the same but maybe this will help...? Find out exactly which drivers you need off the Intel driver disk. Best way to do this is create new capture boot image with no drivers, boot using this then follow link in earlier post for instructions on manually adding a driver from the inf. In my case this was using the NDIS2 driver. When you have the one that works add this specific one to your WDS drivers and be sure to add this single driver to a new driver group. Next create a new boot image from original media (i.e without any drivers) and then add drivers to this image but filter these by driver group so only the single known working Intel driver is added. This new boot image should then work fine. Well, done this on two separate WDS implementations with two different Intel Pro 1000 NIC's and it worked fine both times. Good luck

Work around (see previous post) was good for capture but not deploy as error message appears but even if drivers manually added clicking OK to error just reboots device. Was considering applying image manually with big hdd and imagex (there were only 6 x devices with this hardware) but gave adding drivers to boot image one more go and it worked. The difference was instead of using Add Driver Package with 'All packages from a folder', the 'Driver packages from inf' was used and only the specific known working driver added (to a new driver group). Boot image was then updated re-adding all available drivers and it worked. Maybe this made a difference, maybe it was just adding the driver in a certain order or maybe it was just my lucky day - who knows?

Had a similar problem with Intel DH61 series where WDS would not capture image back to WDS server (network driver had not loaded or network not initialised). To work around this used the instructions in the following Error message when you start a PXE client to connect to a WDS server on a Windows Server 2003 SP1-based computer or on a Windows Server 2008-based computer&#58 &#34WdsClient&#58 An error occurred while starting networking&#34 While there was not error in the log file we were able to manually load the driver (in this case with driver CD copied to USB was drvload f:\pro1000\winx64\ndis62\elc62x64.inf) and perform initialise - got ip etc. and was then able to continue with the capture process. Hope this helps Andy

Hi All @Jose, Rawns, AyatollahPies, RinSewand Looking at the posts I can see what you mean. Can't speak for the others but i have used edugeek to get information for some time - when i saw a post about something i have some experience with i thought i would post - no conspiracy here. Maybe the posts are actually positive because it genuinly is a good product for education networks? Sure it's not without problems. One issue we experienced was with domain users being members of local admins. This meant that they were able to access the centrastage client settings. In the end we just had to put up with this since removing users from local admins caused issues with the older curric software. Another is that there is no support for Linux clients (but being based on Windows WMI this is no great surprise). Still, even with a few issues, it's still a good product. Sure it does not provide anything that cannot be achieved (for a lot less cost) using separate systems i.e. RDP/VNC for remote control, WSUS for M$ patches, logon scripts and GPO's for software installation and updates, WMI based logon scripts for device audit etc. Anyone who has actually used GPO's for software installs knows this is not without issues too! Plus with centrastage you do get all the features in one centrally managed interface. As someone who used separate solutions for several years to support over 200 schools i can say that centrastage made my life somuch easier. PS. The fact that BETT is aproaching fast and redstor/centrastage have alcholic refreshments has no bearing on my comments at all @Rawns Hands up - i might be a little biast since i was the one that originally installed and configured centrastage in Somerset and then left before you got it rolled out to all clients. Still, it's a hellofa lot better than Tivolli which is what you'd have (eventually!) ended up with otherwise. Andy

Hi. I've used CentraStage in an education support environment and think it's top stuff. The web based remote control is good but other features put it way above the likes of LogMeIn. Ability to push installations to and run scripts on selected clients (and get return values) is excellent. Audit features are very useful too (hardware, software etc.). Thing i relied on most was the monitoring tool which could email when specific events appeared - v.good for failing drives and audit events! Andy