dsgoody

Related, but not in answer to your question - do you have your C drives restricted in Group Policy? We are trying to get the client working but nobody is able to view their files. http://www.edugeek.net/forums/windows-10/174424-accessing-onedrive-c-drive-restricted-gp.html

No good for non-Office apps unfortunately.

It seems after plenty of problems in the Summer with Start Menu's we are now working all ok; the fix was to cache the local profiles. I'm currently looking into using delprof2 to routinely clean up the local profiles. Next problem; we restrict access to the C drive via GPO (as you do). Unfortunately, this seems to stop the users accessing their O365 OneDrives stored under C:\Users\%USERNAME%\OneDrive - School Name. Any ideas? Is it possible to make an exception in Group Policy for this folder? Dave.

I can't agree more; and I've been really hesitant in even thinking about it. My original plan was think about it once the September rush is out the way, possibly looking for an October or April deployment. It's really what's the lesser of the two evils....? We can use SCCM to push the upgrade no problem. Suppose we will have to get some testing done in-between now and then.

After extensive Googling and testing; I believe the problem lies with the way Windows 10 1511 handles the local profile component when using roaming profiles with 'Delete cached copies of roaming profiles' enabled in GPO. After some Googling; this looks be be resolved, or at least improved, in 1607. So after months of preparing for 1511 it looks like our hand might be forced towards upgrading the whole site before September. Anybody else having the same experience?

How it should look: How it sometimes looks:

They are secured; but as is the way there are always the odd one or two bits and pieces (network apps for example) that Students have full access to - and I wouldn't want them getting to these. They are all hidden $ shares; but it only takes one of them to work out the network path. It's disabled through AppLocker; it's more File Explorer that they will use. Staff get roaming; Students get mandatory - both pickup the default layout. Get-AppXProvisionedPackage -Online | Where-Object {$_.packagename -like "*Zune*"} | Remove-AppxProvisionedPackage -Online Get-AppXProvisionedPackage -Online | Where-Object {$_.packagename -like "*XboxApp*"} | Remove-AppxProvisionedPackage -Online Get-AppXProvisionedPackage -Online | Where-Object {$_.packagename -like "*MicrosoftOfficeHub*"} | Remove-AppxProvisionedPackage -Online This is run through a PowerShell script when the machines are built via SCCM.

Is that a .v5 profile or has it increased to .v6 as was rumored?

Hi all, We have deployed Windows 10 Education 1511 site wide; and are working to nail down the Group Policies ready for September. We are currently seeing the following issues: Using Cortana seems to bypass UNC path restrictions in File Explorer; The Start Menu seems really unstable, with the File Explorer and Settings link disappearing at random and users loosing their tiles. We injected a default Start Menu layout into the default user profile on the machines using PowerShell Import-StartLayout. Other than that everything seems to be working for the minute. Removal of the Xbox, Music, Video and Get Office apps; Default App Associations; Lock Screen & Default User Image Replacement all work. Even the Mandatory profile seems to be working (so far). Cheers, Dave.

Anybody? We are down to our last one

Apologies for the simple question, but this has always puzzled me. Our structured cabling across the school uses 2 types of modules, one is the Euro module (on the right) and the other (one the left) I'm not sure. http://s5.postimg.org/tjw0ssrhz/IMAG0511.jpg http://s5.postimg.org/6h5htmq0n/IMAG0512.jpg We need to buy some more as they occasionally break; but have no idea what I should be looking for as I can only find Euro modules.

I don't mean a separate network - just some separate collections in SCCM. I managed to integrate the Intel USB drivers from the INF Update package on the Intel website but that didn't resolve the issue for us.

Our workaround in the end was to create a collection specifically for deploying to the Dell 380's and then deploy the task sequence to that collection and make it required therefor no task sequence selection is required and the machine just starts imaging. This does mean you have to remove your password as well. Not an issue for us as we only drop machines into our deployment collections when they need re-imaging. Dave.

No, we are still working on it at the minute. I've been looking around the web high and low - but nobody else seems to have the issue. Glad it's not just us.

Unfortunately not, the only settings for the USB controller turns it on, off or disables USB boot support. It's really odd as older machines work fine and newer machines work fine - it's just this one type of machine that has an issue.