Ste_Harve

Hi All, Got a prob with Java on Terminal Services. TS is on server 2003, java is latest version. Problem is that Java works for adminis, but when a teacher or student log in it says the java plugin needs enabling. Does anyone have any ideas on how to cure this problem? Java was installed in Install mode under console access. TIA Ste

Mines DarkendViper Got quite a few games, and feel free to add me.

We're running a Netgear controller and WG102 flashed to WGL102, only did this as it was cheaper to buy WG102 than WGL102, dont know why though!! We've got about 100 student laptops and 40 staff laptops that use it daily and dont seem to have any problems with it. I've not really configured and advanced settings on it but will do in the future. We've found it to be reliable and quick. We're adding 30 netbooks in the english department which will be shared across 2 access points but these will only be used for moodle access and internet. Ste

for %MACHINENAME% to work the computer needs to be managed in AD and the GUID properly entered. I've got around 400 machines all deployed with sysprep that will pick up the same name as they had before. The big pain was entering the GUID for them all, but well worth the effort. I'd be tempted to delete the computer account from AD and reenter it again making sure guid is right.

Well here's my result. Using CLEO as our provider, 100mb fibre telewest fibre to somewhere, think it ends up going to lancaster uni, and connected into JANET network i think. http://www.speedtest.net/result/535859313.png and if i use the london server i get http://www.speedtest.net/result/535864673.png

I think the problem could be hal related, i've got about 15 images on my WDS server and it only shows the ones that are relevant to that hal. ie dual core machines on pull in images created on a dual core machine. single core only get the single core images. think there is a way to switch off hal detection in WDS though so it will show all images.

Right well I use WDS. It takes a minute or two to boot into the deployment client and from there the whole process is automated after i've selected the image. All my machines are staged in the directory so it automatically pulls in machine names for each machine. Can do a whole room in about 30-45 mins. If anyone needs any help on using WDS drop me a PM and i'll try and sort it out. It took me a few days to get it set up to automatically name the machines, but now thats sorted it's easy. I use this for XP images, not had time to look at using it with vista yet, but it's on the todo list, as i'm wanting to move some machines over to vista, mainly some office machines.

I've had a smilar problem with a friends pc recently. Tried everything mentioned above and it still did it. I could browse the net using the ip address in the address bar but it got very tiring having to remember them!! Have you tried Malware Bytes Anti Malware? I found the problem with the PC I had was done to AVG being uninstalled and leaving some files behind. There was also a whole host of other problems on this PC so i just rebuilt it and it turned out a lot quicker than ever!!

I set up RADIUS with out wireless network and had similar problems to this. To rectify it I had to add the domain computers to my access rule in IAS. This then allows the machine to authenticate and then when a user logs on it re authenticates as a user so they can access a wider range of network resources using their credentials.

I've been using netgear WG102's for 16 laptops and so far they seem to be absoulutely fine. Maybe look at the WG302 as it has more management features and sligtly better range.

Here's my sysprep.inf file which allows me to set a machine imaging and leave it. When it's rebooted it's ready for use with the staged name and GUID in AD.

Thats right, my sysprep.inf file has the reference %AMCHINENAME% for the machine name and %MACHINEDOMAIN% for the domain to join. All I do is boot machine via PXE to WDS, set it to pull the image down, and after 10 mins it's sat at the logon box waiting to be used. If you want a copy of my sysprep.inf file i'll happily post it up here.

Well to drag this back up, I couldn't get the machines with the Pro100/VE entwork connection to pick the name out of AD but if I use another supported network card it does. I've now got all my machines staged in AD and the sysprep.inf file pulls the computername down from AD. I think it does this when you use the RIS or WDS part to setup. I can't tell you how it works but it does and it's saved me a lot of time. No more moving computer accounts between OU's, no more renaming, unless I change the motherboard!! If anyone wants any more info on this just PM me and I'll see if I can guide you in the right direction

Only thing i could possibly think of is having to boot each machine individually and copying a sysprep.inf that you've created with your settings in to the sysprep folder on each machine before it starts to run the windows setup.

Thanks for that quackers. I know a few years ago using ghost in multicast was slow for me and that was down to the switch configuration. I'll have to have a look and see whether it's going to be worth taking a day to upgrade it and see what happens.

And will that actually give multicast on a 2003 server or is that still only a 2008 feature? As I use WDS a lot for imaging, i'm debating whether to upgrade my imaging server to 2008, server is also a DC, DNS, DHCP. Any thoughts on it? We already have a 2008 DC up and running but server doesn't have hardware capacity to support imaging properly!!

I used to use ghost entirely until last summer when I decided to move over to WDS. The initial setup configuration was the hardest part. Having to rebuild all the images, and image them. Now the imaging process is almost fully automated, only bit i need to do is pxe boot machine, login into wds, select image and format hdd and then walk away. Takes all of 2 mins. All our machines are staged in active directory and the moment the imaging is finished thats it, the machine is usuable. I also find WDS quicker than ghost, WDS takes about an hour to do a room of about 30 machines and thats from switching first one on to last one being ready to use.

I've noticed that machines with SP3 on are a lot more unstable in internet explorer with it crashing at least once first time you open it up. Only seems to happen on certain sites. Main one being Welcome to The Lancashire Grid for Learning Website could this be related to this flash problem?

We're running 100mb/s to desktops with a few select machines running at 1gb/s. These machiens are used by me. All our servers have teamed nics putting out either 2x1gb/s or 4x1gb/s into the 5406zl switch. This is then link to all the department switches and other buildings. All buildings are linked using fibre, and ports are trunked to 2gb/s and 1 3gb/s for biggest building. Our IT suite, 4 procurve 2650's are all linked to the 5406zl using 2gb/s trunks each. All switches are linked in at either 1gb/s or 2gb/s trunks. All internal links are using cat5e while fibre conenctions are using OM2 fibre.

I've used ric's script this morning and customised it, BAINES is the name of his domain so you need to change that to yours, and ensure that staff is correct, ie ric uses staff, we use teachers. You also need to change the source location on the 4th line. Have to say to ric and all who made the script that it works brillantly, and i've been looking for something similar instead of having to do it manually!!

When i use to use Ghost i could get any number of multicast clients on the go. This was from a P4 1.6 machien with 512mb ram!! and a couple of 10k scsi drives not in raid. If i did any imaging during the school day it often caused our print server to not talk to the network till the imaging had finished. I've since moved over to WDS and over the summer and 184 machines imaginging in one go!! Was bit of a task to get it all going. This was from a dual xeon server with 4gb ram and teamed gb nics. 100mb to desktop. 15k sas drives in raid 5. Quickest machine took about 15 mins to download image and slowest was about 60 mins. network infrastructure is all procurve managed switches. I'm going to try the multicast feature of wds on server 2008 soon to see of thats any better.

I drove down the motorway to preston this morning and the motorway was full of glaswegians all with flags and scarfs out the windows. I'm suppose to be going manchester later and i'm going near city stadium so god knows how long it'll be to get round anywhere!!! go on rangers is all i'm going to say!

Hi all, First hope this is in the right area. My prob i've got at the moment is that i use WDS to deploy images and some of our older machines that are being merged into the network from a different network have 3com 3c905cx-txm nics in them. Now under vista pe these don't work so i added the drivers to the vista pe image and it worked. I did the same for the capture and deploy images but it's not getting an IP or loading the driver under the capture and deploy images. Can anyone help with this problem? Cheers, Ste

gshaw - in the 5406zl i've got two 24 port cat 5 10/100/1000 modules and a 24port gbic module populated with 8 1000base-sx fibre modules. Works really well and is nice and rapid. plexer - I've just ordered 3 so will let you know on monday. I noticed that they we're shallower but will have to see if they still fit in the cabs i've got!! Will also report on how they run.

Thanks for the info people, i was comparing specs and the 2610 series does seem better on paper. Think i'll order a couple and stick them in. Our core switch is a 5406zl which so far has performed brillantly!! Best few K we spent to link everything together.