Michael

1607, then manually install the November 2016 fix or later addresses the issue with WSUS. Including this as part of your base image makes your life easier!

I don't have any of these problems to be honest. There were issues with earlier versions of Redstone 1, but anything after November 2016 has been solid.

I know with Server 2016 (when hosting WSUS), you need to 'Specify intranet Microsoft update service location' and populate all three fields (even if they're the same), otherwise Windows 10 devices fail to download updates from WSUS.

I only have a 64Bit version which is an MSI. As I say, otherwise I just install the driver manually where required, rather than on every machine.

What parts of it are particularly bad? I've heard of some users experiencing blank icons (no labels), but whether or not that was Impero related was unclear.

There you go, I stand correct. 4 versions in and slowly Microsoft are making small changes.

As previously discussed on Edugeek, later down the line, they may decide to release Apps specific for the Education version, but this is yet to materialise.

Only driver version 5.9 has both Serial and USB drivers enabled. Anything later doesn't. The only solution is to install the driver manually, to the best of my knowledge and select Serial.

If you implement WSUS, you don't have to roll out every patch or upgrade to Windows 10. I don't have a single machine running Redstone 2 yet, still all Redstone 1. Likelihood is I'll have a look at Redstone 3 which has improved OneDrive functionality later this year. Machines wouldn't be upgraded either, they'd be re-imaged as new, as the 'upgrade' path for Windows 10 is ill thought out and very messy.

They are exactly the same

How many internal DNS servers do you have?

Depending on what it's for, you could go down that route. A large/dedicated SQL Server (physical), then the actual applications running on a second server or virtual.

Hypothetically, if you had iPads with a 3G/4G SIM connecting to a cloud MIS, this is the ideal scenario as it will safely work off the network.

I believe you can license for just what you're using - so for example if virtualising, you'd limit the number of cores and memory to suit in Hyper-V. If it was physical, then it'd be a bit of a waste having a Xeon with 20 cores, yet you only used 4 for example.

Yes I believe it does.

No problems here (Birmingham).

Thanks Al - it looks great, but definitely room for some improvement (especially for large AD structures). Considering all users will be part of one or more groups, it would make sense to be able to target groups for messaging.

Several questions - - If it talks to AD for its database, can you message specific users and/or Security Groups? - If a user isn't signed in, will the message appear when they next sign in? - Will the window always appear on top of others? - Can the end user kill the process used by the Alerting software (if they have access to Task Manager)? - What port(s) does it use? - Can I create favourite lists for regular messaging, instead of having to add all the same users/groups each time? Thanks!

But the last paragraph mentions 'enterprise scenarios'?

You'd think Enterprise/Education should do all the above anyway, clearly not!?

Link2ICT could do this, however it would be based on the current lifecycle of the existing certificate (ending end of June 2017). This is their decision. To be honest, it's all a bit political, but so long as you make a decision on how to proceed (suppressing the certificate warning), then it doesn't matter.

Well the alternative (if requiring external API access), is the data is submitted insecurely. Definitely not a good idea. Paying for an SSL cert is perfectly normal for every company, school or charity globally. As to whether Advanced Learning should provide an SSL certificate at their cost is a different discussion altogether. They do of course do this for Progresso, but they're buying one certificate for all customers.

Yeah I use that too on Windows 10 devices. Seems to work OK overall.

But having to do that for every user is just ridiculous. It's not a fix in my opinion. The problem is Link2ICT won't buy the AnyConnect software.

Opening RDP to the public is a very bad idea, as it means anyone could then 'attempt' to sign into your server. One option is to look at setting up a VM and configuring it for VPN. It's something I've looked at before, but haven't had the time to do it properly. Link2ICT will then route all VPN requests to your VM for example, instead of requiring the Cisco VPN client, which clearly doesn't work on Windows 10. VPN of some form is always going to be better/more secure than RDP (in the context of accessing services remotely).