lonewolff

1. What is your current salary range? NJC scale PO1 - full time 2. How many people do you have in your department? me and an IT technician who is also outdoor activities coordinator 3. How many PC's/Servers do you support? 350pc's & 8 servers 4. What other systems do you support (eg IP camera's, VLE, Sims, telephone system, etc)? MIS, CCTV, Intranet/website/VLE, email, Photocopiers, AV stuff 5. Do you support any other organisations (eg primary schools, private businesses, etc) IT wise as part of your working week? no

This makes it sound like you have proxying working but your website is pushing out links with the FQDN in the URL - there is no need to do this - if you want to like to page2.htm in the root of the folder just link to /page2.htm not http://www.jkhs-pd.local/page2.htm then it will work no matter what the domain is which is used to access the site.

What I would do in this situation would be to set the server with the search stuff on to respond with the search page to any url's you wish to point there then just put these on your dns server. e.g. if I wanted to redirect http://www.google.com to our own search engine I would go onto the web server with the search app on it, and set it up to respond with our search page to any requests to the domain http://www.google.com then go into DNS and set http://www.google.com up as a record pointing to that server

Apache can do lots of stuff like that, but it is not clear exactly what you want to do. Do you mean have someone access http://www.external.co.uk which points to your gateway system and for apache to then access another webserver webserver.local and then send those pages to the client? - Apache can do that, we use it for that here Or do you mean when someone access http://www.external.co.uk it redirects them to webserver.local and then it just serves up the pages? - apache can also do this and it is quite handy for forcing people to use SSL. In both situations you will want to use mod_rewrite and for the first situation you will want to use mod_proxy as well.

This is correct, the ap's just need to connect to your network somewhere. Not one of our access points actually plugs directly into any of our wireless switches.

We have eportal set up running behind IIS on the eportal server, then apache2 installed on our gateway server (the only server we have with a public ip) which forvces everyone from outside of the schools local network to connect over SSL then just acts as a proxy to the IIS eportal server. This works very well.

they support load balancing as well as handoff of wireless devices between ap's if you have roaming users (wireless IP phones, PDAs etc)

we have one of these switches running 8 access points for areas of the school where there are no desktop computers form registration and it works really well. We plan on expanding the wireless network with more of these 'stacked' to cover the whole school, they support 16ap's each and you can stack as many as you want all getting their config from the master switch

the migration from sims to cmis is normally done as part of the commissioning processes and I must say is the worst part of using the facility system. best to run the two side by side for a while to make sure everything is up and running properly. Migrating timetables is the worst part so its best to use sims for your current year and start setting up cmis for the coming year, including writing the timetable using scheduler.