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.

Yes, along with changing the keyboard and mouse it's one of the first things I've tried. The machines that are having the issues are running the latest A07 BIOS. We also have some with the older A06 BIOS, still with the same issue.

Hello, We use SCCM 2012 SP1 to image all of our machines (Dell OptiPlex 755's, 760's, 380's, 390's and 3010's). We have previously used SCCM 2007 SP3 and 2012 RTM with no issues at all but it seems the change to WinPE 4 in SP1 is upsetting our Dell OptiPlex 380's (all the other machines work fine). The WIM image loads via PXE perfectly, but once it's loaded the keyboard and mouse refuse to work. Historically, we have only integrated Network and Storage drivers into our WinPE images however to try and get around this problem I decided to integrate all of the Intel USB drives too - but no luck. I've tried booting from a Windows 8 CD and that seems to work fine - so either I've got some driver related issue going on or it's unique to SCCM. Any ideas on things to try? Anybody had this issue? Dave.

I have renamed some more printers to take the numbers out, and they all seem to work now. It seems to be numbers that it doesn't like. Out of interest, how do you deploy the printers to the workstations? Here we have a central print server looking at all the printers via TCP/IP ports, and then deployed via GPO using the Print Management method. The bad news, we tried Photoshop CS6 and the problem still exists.

Ditto to that - we have just had to upgrade all of our machines to 4GB to run Notebook 11 correctly.

Well, we have CS6 available to us so hopefully in the near future we will start doing some testing with it to see if the issue has been fixed. For now however we are continuing to see if we can see any other pattern, not just the names. It really is so intermittent for us. I just hope Adobe come back with something soon.

Sorry about the slow reply, had a few weeks well deserved holiday To be perfectly honest, I'm not sure. The printer was called Photography A11 Colour previously, it's now called Photography Epson. We found calling it Photography B-510DN didn't work either. It turns out during my absence that this issue is happening on our HP printers too, so we now have to find a more permanent workaround. We use the PCL6 HP UPD driver (v5.5.0), and we have tried the Postscript version but no luck. I have raised a call with Adobe but so far, they don't want to know.

Managed to fix this in the end. It was something to do with the driver not liking the name I gave the printer. I know that's a bit far fetched but that what our testing showed.

Unfortunately, Epson don't offer anything like this. It's just a single, straight driver they offer. They do have a slightly older version listed on there website but we used to use this and it was just as bad. The printer is a 'business class' inkjet used for printing Photographs.

Oh the joy of the Adobe Creative Suite software, if it's not throwing up one problem it's something else We have an Epson B-510DN networked via a 2008 R2 Print Server and then the printer joined to our Photography workstations via GPO (10 machines). Whenever the students try to print to the printer via Photoshop the get the following error and then it won't let us print at all. If I go into Printers and Devices the printer works fine, I can print a test page off and I can even print from Word. The only workaround we have found is to set another printer to default and then set it back again, Photoshop seems to like this. All of the workstations are Windows 7 64-bit and the Students are using the 64-bit CS5.1 version of Photoshop. We have the latest printer driver installed (v6.72) on the print server and we let the drivers own setup utility configure the driver encase there was any 'model specific' configuration that needed doing, although we have tried setting the driver up manually using the traditional manual driver and port selection too. Anybody got any clever ideas or encountered this issue before? Thanks, Dave.

Sorry to dig up an old thread, but a quick question to those who have done the upgrade. Did you uninstall SMART Notebook 10.8 first (msiexec /x) and then install 11, or just run the 11 MSI (msiexec /i) to upgrade the machine? Thanks, Dave.