GeeDee

Run your FTPd on another port? You can usually FTP via a HTTP proxy too - although IEs FTP client sucks for this (well, ok, it just sucks).

iirc (and tbh, i'd rather not be corrected on this - could be pricy! ) that's not the way it works for education. That is correct for some of the MS Volume licensing schemes, but under the education licensing system you don't need to re-license a box that's already licensed with the same product. i.e. A box with an OEM XP Pro license, you should be fine to run XP Pro on as is and in addition; IF you volume license other machines in your school you can also use the volume install media on your OEM licensed boxes (as in the doc I linked to a couple of posts ago). Where the waters are muddied a bit (and what the software licensing houses don't always make very clear) is that the education Windows license prices are actually for upgrades only, so you would need another license (OEM or retail) in order to be able to 'upgrade' to XP under education pricing per box. So if you had machines with Win98 OEM stickers, or XP Home OEM stickers, you could buy education XP Pro licenses on the ~£32 pricing, use the volume media and as a bonus, use the volume media on your XP Pro OEM licensed boxes too. What you couldn't do is build your own machines, or buy machines with no OS license, buy the ~£32 education XP Pro license and run XP Pro. You need something to upgrade from (although Win95 does qualify - keep those old licenses ) That's always been my understanding anyhow. Plus, our old admin network which was a Hampshire CC managed jobbie were all OEM licensed but installed with volume media and no volume licenses were ever purchased. I always thought it rather odd that any VL scheme would require re-buying licenses you'd already paid for via the OEM anyway. :/

No worries. If you want to image OEM pre-activated machines under an OEM license or want to know more; this page might be useful to you.

1: You can't use VLK media unless you are a Microsoft volume licensing customer BUT you can use VLK media on OEM licensed boxes, providing you are a volume license customer. I.E. You don't have to re-buy a volume license for an OEM licensed box to use the volume media, providing you have volume licenses for other (presumabely none OEM /retail licensed boxes). 2: The Dell (and most other OEM) recovery / Windows install CDs use what's called OEM pre-activation. The Dell XP CD will check for a flag in the machines BIOS and if it finds it, won't ask for activation. Same applies for the XP disks of other OEMs who take part in pre-activation. If you use the Dell CD in a none-Dell PC, it wont find the flag it's looking for aks will ask for activation. 3: You can't activate using the OEM COA sticker numbers over the internet. Microsoft switched that off some time ago. You CAN activate the sticker number via a phone activation, just not online. Apparently too many people were stealing COA sticker numbers and using them on other machines or something (the COA numbers were never getting used for most OEM boxes, as they are all pre-activated either using pre-activation or as part of the factory install). Hope that helps.

- More offensive content - Ric_ To answer your question, i'm sure it's possible to write a quick script to do the necessary mass imports for qmail. Have a Google, read the documentation and have a play. That said it's hardly ideal to have to maintain a totally separate user infrastructure for mail when (I assume) you already have Active Directory running as your primary authentication mechanism. Educational licensing for Exchange is really very cheap and mdaemon from alt-n is a very powerful e-mail server that will integrate with AD (for an alternative to exchange). There are also plenty of ways to integrate most of the major *nix mailserver apps with AD via LDAP (or plain old NTLM I guess :/); but it will be a bit of a steep learning curve. Enjoy.

Post removed due to offensive content - Ric_

No, not on XP Home. IIS with XP Pro is also only designed for testing purposes - not live sites. I assume you realise that *nix / Apache isn't going to be all that much help to you for hosting ASP too?

gallery2 should be the only choice really. It's brilliant software. Not only does it integrate with a lot of CMSs 'out of the box' (and has a world of docs for integrating with it something yourself) but it's the best gallery i've seen that "just works". Can literally throw a zip file of 3000 images at if if you want and it'll extract, create thumbnails, create midsize version, add to a gallery. You can then edit, comment, rename, rotate (although it'll auto rotate if the camera supplied the appropiate exif data) and you can set as granular permissions as you want on the gallery, albums (,photos, comments). There's also various plugins that integrate into a Windows shell for quick n easy publishing without even needing to open a web browser if you want.

Sure, and that's the primary reason for deploying vlans in this kind of environment usually - but you really don't need many. Running Windows clients, you could happily shove ~350 - 400 machines in a single vlan, even with 100meg uplinks & clients using el cheapo switches. And you don't need to mix subnet masks (nor should you) just to provide a 'simple' way to select a logical group of machines. The machines can run on a /24 (or whatever), but when you tell your proxy to deny on a /26, only those logical machines will be affected. It's just an easy way to select part of a network. It's actually pretty easy to get your head round, at least at this sort of level. All you need to remember is that a /24 is your typical "home network" block of 255 addresses, using a subnet mask of 255.255.255.0. So 10.10.1.0/24 would be a single network of 10.10.1.0 through 10.10.1.255, using a subnet mask of 255.255.255.0. You then just work from there, so a 10.10.1.0/23 would be 10.10.1.0 through 10.10.2.255 (and 10.10.1.0/25 would be 10.10.1.0 through 10.10.1.127). So, if your network runs on a big network of 10.10.1.0/24, but you tell your proxy to please ban 10.10.1.0/25 - that would be 10.10.1.0 through 10.10.1.127. Likewise, banning 10.10.1.128/25 is the other half of the network. You can of course go deeper, a /30 is a network of 4 machines.

You can assign each room it's own network as part of a larger single subnet without arsing around with a small world of vlans. vlan'ing everything off just creates so much unnecessary load on the switches that have to do all this extra routing. Why not just assign each room a /24 of part of a /16 network (or a /26 as part of a /23 or whatever). You can then do your room blocking by network to get just the same result without all the overhead. Glad you managed to solve it though.

Considering how easy it is to spoof a mac address (they even give you a nice field in the GUI with most driver sets these days) that's hardly going to bring you any security benefit. If ensuring ports aren't swapped is a priority for you, just enable port security.

It might be easier to just read the manual for ffmpeg (or install windows media encoder if wmv is your thing) rather than run code from a site that looks like that.

....The point of this being what exactly? What are you imagining happening in this scenario?

For the purposes of 'making it work'; you probably haven't tagged the vlan on the uplink. Aside from that though, why on earth so many vlans? Seperating by room seems a little more than overkill! You can happily run several hundred machines on a single network even over 100meg uplinks. The only thing you're going to cut down on over all those vlans is broadcast traffic - which really won't be an issue (at least not in the average environment) until you hit ~400 odd machines. Seems like extra overhead on your switches & technician time for no good reason really.

What exactly are you trying to achieve? Unless you have a 'special' setup, you want to configure all the ports for your new vlan as untagged; except for the uplink port(s) which will need to be tagged. The switch at the other end of the uplink will then need the vlan creating & tagging as well as untagged on any other ports with machines in the new vlan on. Then same on any other switches elsewhere. That will create you a 'new' network, across multiple switches - but unless you have either another router or you configure ipforwarding (or whatever HP might call it - assuming your switches are layer3) to forward layer3 traffic you won't be able to talk to anything except your new network. Are you sure you actually want a new VLAN? What's the purpose of it here?