Tallwood_6

Will mostly be HP z400 workstations, I've managed to package everything up now just need to do some further testing and then I will post instructions for those interested. I did see the communities but thought I might get a response from the online academic support form or one of the emails I sent directly to support. If they gave me access to the knowledge base I'm sure there's some useful guides on there! Full install guide would be most handy though if you can share.

I've managed to package up the program so it installs and licences all the componets just need to test the uninstall script and package some of the plugins so they install after. PTC support have been less than useless but fortunately found a couple of guides by 3rd parties online.

Also sophos, I do think the lastest clients are a bit resource hungry but it sits there and gets on with it.

Dropping CC4 isn't going to help you much with appinventor 2 I'm afraid.

I am awaiting access to the full academic version but reading through the instructions that have been sent across you've got to spend 10 minutes at each machine faffing to get it setup and give users permission to run scripts. Love the instructions for the student edition stipulate at the top "Note: Before starting the installation process please turn off your antivirus software as it could prevent the installation of some libraries." If I have to do this with each station on the network I will be advising they find an alternative. I've emailed asking if its possible to perform an unattended install but I'm not holding my breath.

DT are looking at using PTC Creo next year following one of them going on a course and I've just been sent the install instructions and i'm slightly worried. Is anyone using this or found a method of deploying this silently?

I ending up biting the bullet and purchased the CC4 install pack for AppInventor 2 which basically gives you a package for the emulator and some policy changes to make to get it running for users looking to run it. Far from elegant though!

We have recently started using freshdesk which is pretty good and free for up to 3 agents.

App wizard can produce some pretty untidy msi packages. I am hoping that RM may have completely repackaged it and turned all the bat files into executables so the batch processing doesn't need to be turned on.

RM are selling an install pack for MIT app inventor 2 which might save some headaches, I bit the bullet and placed an order last week as I'd rather have something I know will work 100% if it's going get be widespread use.

I am similarly hacked off with it, Frog just seem to pursue there own agenda or that of a select few when it comes to development. We are stuck with on Frog 3 at the moment which is really showing its age, simply because people have invested so much time training and developing resources for it and Frogs approach to the FrogLearn roll out seems to very much be, here you its now enabled on your server best of luck setting up and training your new VLE, there are some help guides and some videos on the communities.

You will likely spend more than 5k if you want frog to do any real legwork and the yearly cost is bases on student numbers. Frog is probably one of the most popular VLE's but if your buying into at the moment you probably will be buying FrogOS or Froglearn as they now call it which is still buggy and incomplete in my view.

Have you tried updating the switch to the latest firmware and then trying?

You have a hell of a lot of config there, you need someone to either unpick it all or start afresh with some static vlans. We quite simply have the following enabled on the switch (not per vlan) ip routing ip udp-bcast-forward and our server vlan config looks like this (our WOL uses udp 40000) vlan 10 name "Servers" untagged B19,B23-B24,J5,J12-J13,J16,J19-J20,L13,L15-L16 ip address 172.16.10.1 255.255.255.0 ip forward-protocol udp 172.16.60.255 40000 ip forward-protocol udp 172.16.61.255 40000 ip forward-protocol udp 172.16.62.255 40000 ip forward-protocol udp 172.16.63.255 40000 ip forward-protocol udp 172.16.64.255 40000 ip forward-protocol udp 172.16.65.255 40000 exit

Nope the switch should route broadcast udp traffic on that port from the server on the default vlan to the broadcast address of all the stations on the other vlans. Under the running config you should now see: ip forward-protocol udp 10.5.31.255 2050 9 ip forward-protocol udp 10.5.39.255 2050 9 ip forward-protocol udp 10.5.3.255 2050 9 etc You can always use wireshark to check that this traffic is reaching the stations if need be.

You just need to add port UDP port 9 to the existing: ip forward-protocol udp 10.5.31.255 2050 ip forward-protocol udp 10.5.39.255 2050 ip forward-protocol udp 10.5.3.255 2050 ip forward-protocol udp 10.5.7.255 2050 ip forward-protocol udp 10.5.11.255 2050 ip forward-protocol udp 10.5.15.255 2050 ip forward-protocol udp 10.5.19.255 2050 ip forward-protocol udp 10.5.23.255 2050 ip forward-protocol udp 10.5.27.255 2050 ip forward-protocol udp 10.5.35.255 2050 Under your default vlan 1

Blimey a bit much to properly scan through but what have you go on what I.e are the servers on the default VLAN now not the one labeled servers vlan 500? You have what looks like the broadcast address of the range you have the servers on not the stations I.e you need ip forward-protocol udp 10.5.31.255 9 ip forward-protocol udp 10.5.39.255 9 ip forward-protocol udp 10.5.3.255 9 Etc

Post your running config

You configure this just on the core switch. You may need to double check the udp port your wol is using. I think port 7 or 9 most common but it could use another port I.e cc4 remote start uses udp 10000

Enable on the switch: ip directed-broadcast ip udp-bcast-forward And then on the VLAN the wake on lan broadcast is originating from, i.e. Server VLAN specify the broadcast address the stations are on. ip forward-protocol udp 10.0.5.255 7

Uplinks carry tagged traffic for all the vlans you wish to be available at the connected switch (although you can probably leave the default vlan untagged), the ports connected to client workstations will need to be untagged for the correct vlan. VOIP phones can usually handle tagged traffic as in some instances you will have a client PC running off the same connection.

I'm not sure what you mean by pushed out by the core switch, but 10 vlans for workstations by location seems a bit much unless your running hundreds of workstations from each location?

It depends on what each VLAN is for i.e. If some of the vlans are designed for stations in geographical locations then obviously you won't need all of these on each edge switch. That said it certainly does no harm to add them all.

We have a 32 of these Fujitsu machines which just wont playback youtube clips in internet explorer (versions 9, 10 and 11) under Win 7 64bit, every other site using flash to payback video is fine. I have tried everything from updating all the drivers cleanly removing flash and reinstalling, disabling hardware acceleration in IE, building one of the stations as a standalone, plugging it into different switches but the only way to get it to work at the moment seems to be to install another browser. Anyone with any bright ideas?

Sophos web appliance would be a good low cost option, and does pretty much everything smoothwall does, is certainly more user friendly and easy to setup but... does get bogged down when you have lots of bandwidth happy users, support can be a bit naff and in terms of actually blocking uncatagorised sites is not every effective. If you get a hardware appliance you do get a licence for a VM as well for failover if you want this setup. Lightspeed wasnt much cheaper than smoothwall web we looked back in Dec. Sophos UTM (astaro) looked pretty good but i'm not sure how it would come price wise for you.