Sheridan

We've put Applocker to work on our Windows 10 PCs, with rules set to allow Administrators to install anything. However if we try to install an MSI that is on a network share it is always blocked. The annoying thing is that Applocker shows an event saying the MSI was prevented from running and the administrator gets the message 'The system administrator has set policies to prevent this installation' despite the full network path of the MSI being whitelisted, and no other blocking rules are in the Windows Installer Applocker rules. So where is it getting the rule from, or does Applocker not work properly with 10 yet?

We've had a few failed logins that result in the circle, CTRL+ALT+DEL and Sign Out then works - or at least takes them back to the login prompt.

I've noticed a slightly annoying issue with W10 (Edu) with the sleep function. When you wake up a PC that has gone to sleep, the display shows our AUP message, and the OK button only responds to a mouse click, rather than just hitting Enter as in Win7 Anyone else found this? Its a small niggle but I can it causing problems for us - when students don't realise they have to use the mouse only

We're testing out Xirrus at the moment and want to use our currently working Radius NPS Server for authentication. Currently we have the old wireless controller in NPS as a Radius client, with Xirrus am I correct in thinking each AP needs to be added into this list as there is no central management for this, as its all cloud based?

This 100% for me - I'm getting a little tired of both Apple and MS rushing OS's out and then ramming a series of updates down our throats. Big updates as well not just patches. How about they spend some time preparing an OS in advance for a change! They're as bad as other for doing this, Apple's updates are now comical - has anyone read the 40+ pages before they 'Agree' to the latest IOS update If I bought a PC for home use with 7 on it, or even 8 then it is effectively my right to continue to use it, if I choose not to update then its my tough luck!

I guess thats the point of LTSB! But I think Win10 was rushed out in all forms, so none of them were fully ready for general use.

Thats the thing, I'm happy to plan and deploy a new OS, with new features and ways of doing things but this isn't ready for mass deployment in many ways. Of course some will say thats just me being against progress, far from it - I was expecting to start deploying 10 last year but a list of issues held us back. LTSB has addressed a lot of these issues but added the niggling element of doubt - it hasn't been updated since July 2015 so has the original bugs from the day 1 release!

'Upgrade' - based on the last few these are enormous files and make it easier to reimage.

We're stuck between a rock and hard place. LTSB is the only version that actually works without all the crap, but apparently we're not 'supposed' to use it. The version that was supposed to be ideal for us, Education, is a bloaty mess that will need reimaging twice a year. Talk about 1 step forward and 10 steps back. In my mind , 'Windows as a service' does not mean reimaging our pc stock twice a year.

LTSB with Classic start Menu will be our next OS deployment here. Judging by the comments on here, why didn't MS produce an Education that was actually designed for education? And I mean all education (Unis/colleges included!) as we (and a lot of businesses) want the same thing, a simple deployable OS without bloat or toys that most people wouldn't even use at home!

Exactly. And as edge is a buggy unfinished product then I would rather have IE and Chrome as the browsers.

For me, the removal of all the rubbish that clogs up the other versions has pushed me towards LTSB. Even the education version comes with Xbox garbage etc, why!?

"netsh winhttp show proxy" shows the correct settings - its supposed to hit the proxy which will allow update through unauthenticated. It hits the proxy, and then the firewall as the firewall is effectively the default gateway. Therefore its acting like a home pc in the sense it ignores the proxy settings.

This is bugging me now. Tried various VMs/hardware and can capture any version of 10 absolutely fine. But as soon as we try to deploy it (back to the same hardware or VM) it stops at 42% and then crashes out. We've got no chance of even a test deployment of 10 at this rate, its like an ongoing battle to fix the problems!

Nothing there. I think it might be because we're testing with a copy of LTSB downloaded from VLSC - so its the old 'broken' version of Windows from July 2015, whereas the the Edu/Pro versions are the Nov 2015 versions. I think we'll have to try Edu or Pro and see what happens. We can't update LTSB as its just not working behind a proxy.

Yes - thats exactly where I got the list from! Its not a case of anything being blocked by the proxy, more like its not trying to use the proxy, and our firewall is blocking (correctly!) this http/https access going directly out.

Hmm, we've tried that exact method. Our proxy is set to unauthenticated for all update sites and it still seems to hit the firewall after an initial connection to the proxy!

Still cannot get this to work. I can see the machine hitting the proxy and then it bombards the firewall (i.e default gateway) for a load of MS sites. So as far as I can tell WU on Windows 10 uses the proxy first then ignores it for subsequent downloads?

I can't get it work like I want. I can login to the RDS site, but any app I try and start prompts for authentication and nothing entered in here will work, no matter how I enter it Works fine internally though, which isn't much use! If nothing else its proved Citrix is worth the money!

Sorry yes, its my Friday keyboard! We've got the drivers in the boot image and the capture and install images. I've just checked and the ADK is already the latets version (I updated that last year and must have forgotten I'd done it!) It seems to be an issue with the fact the image is from a VM on virtualbox.

We created the Install (boot) and Capture images from the Windows 10 boot.wim. I haven't updated the ADK yet as we're not doing anything with the images apart from capturing them and deploying them (for the time being anyway)

Boot image is latest Windows 10 LTSB from the VLSC site. Drivers are injected into the boot image as far as we can tell - i.e the drivers we use are what was on the original image. The only thing is that the original image was created as a VM.

We're running WDS on 2012 to deploy Win7 which has worked fine for a while. We've created a base image of 10 and captured it to the WDS server. The only thing is no matter what we try and deploy it to (physical or virtual pc) it crashes out with an error at the 'Installing devices' stage. The setuperr.log contains this: [0x0b003e] WDS QueryAdapterStatus: no adapters found. Followed by a lot of these: [0x0b003a] WDS [gle=0x0000276d] But thats it, no real as to what the problem is. I'm not sure what adapter its missing as the drivers for the network cards are injected into the image?

Yes we're using IE11/Edge and its asking for authentication. Haven't tried the remote app part yet as we're just testing this.

Its odd then, as I have a 'proper' certificate installed across the way, from the TMG firewall to the all of the RDS Server components. It works fine internally, user logs in and launchs apps with no further authentication. If we can't work around it we'll have to stick with Citrix, staff wouldn't be happy with this carry on!