EamonSch

Hi, we recently got some Fujitsu A555 laptops and i seem to be having an issue imaging them on WDS. I installed windows, added drivers and software on one of them, and everything works correctly. I then ran sysprep using /generalize /oobe /shutdown and our unattend file. I then capture the image and add it to WDS, and for this test FOG too, and when i bring this image down onto another Fujitsu a555 using WDS everything works correctly apart from wireless. The adapter is on, but complains the "Wireless hardware is not bound to transport driver" and it cannot see any of our SSID's. Reinstalling the driver doesnt fix it either. This exact same image and unattend file is uploaded to FOG and the wireless does work after imaging using it. So the issue is pointing at something WDS does differently to FOG. I use PersistAllDeviceInstalls, and i know the unattend file is running on WDS as i can add/remove settings, in the unattend file, which do reflect the changes. We have 11 other WDS images and they all behave correctly, this has been the only one so far with this issue. Any Ideas? I seem to be going round in circles on Google trying to fix this. Many Thanks, Eamon

Many Thanks, i thought that part only set permissions, i didn't realise it hides the drives too.

Hi, is it possible within HAP to hide certain drives for certain users or groups? I would like to give access to both teachers and students but currently the staff resource drive appears for the students which causes errors when the students try to open it, it would be cleaner if it didn't appear from them. Many Thanks, Eamon

Hi gbaman, many thanks for your response. Firefox starts up perfectly however after prompting to login to our proxy (smoothwall) it displays NTLM authentication errors when we try to visit websites. I tested a stand-alone version of wheezy from the raspberry pi website and it works correctly and doesn't encounter this error. Any idea's? Many thanks for your help so far.

Further to this, we started again from scratch and linked the PiNet server and clients directly to our existing network and the pi clients now boot correctly. Everything seems to work fine now apart from the browsers, Epiphany seems to force close when we try to visit a website and chromium, although brings up our Smoothwall login screen and lets us login, get stuck in a redirect loop. Has anyone seen this before? Many Thanks

Hi, the current situation is we have our live network with dhcp and a pxe boot server (fog). If we setup PiNet directly onto our existing network our dhcp assigns it an ip and automatically sets the dhcp rule pointing clients, who wish to pxe boot, to our existing pxe boot server and not the PiNet server. Our first idea was to setup PiNet onto a separate vlan, secondary NIC attached to our network for internet access, primary nic for pi side. I installed dhcp for the primary NIC and configured it to hand out ip's to the PiNet clients, which worked correctly, however although we had internet access on the PiNet server this didn't follow through to the clients. No doubt due to separate subnets which is why we tried squid. I guess the simple question is how do we setup PiNet to our existing network so it doesn't conflict with our current pxe boot server? Many Thanks.