kennysarmy

Found some information here which might help: https://community.spiceworks.com/topic/2143950-remove-all-start-menu-items-win-10-pro-group-policy

A slight bit of free time so thought I'd investigate again why our redirected start menus for staff and students show folders which are not in the redirected path! ie. All these that begin "Microsoft.." as shown below. The desktop is redirecting to the same folder <\\server\desktops\_test10Pupils64Edu\StartMenu\programs> and there are no such folders being created on the desktop :/

All looks OK?

No, they are behaving as they should and using group policy to auto-move.

Yes, some that are appearing are in the right group, others are in unassigned. I can't see any differences with clients exhibiting both behaviours - they both run the relevant Group Policy Object and the settings are being taken.

>>>When you ran the 'clean-up' wizard, did it delete any computers that haven't reported in, or are they still in the console? Exactly that - and it looks like if I ran it again today it might delete a few more! I would say I've only got around 70 out of 1000 devices now checking in correctly. Frustrating.

What's really odd is a room we've re-imaged recently with 30 computers in it: 24 are now in unassigned. (Last contact back in mid November!) 6 are in the correct container and have today's date as last contact They were all re-imaged exactly the same.

Could be time for an uninstall and reinstall if I can't get to the bottom of it. Quite a few errors in Event Viewer

Restarted the WSUS Server yesterday

Finally got round to checking WSUS this term and after running the cleanup wizard I find that only 1/5th of my PC's have been checking in in the last 30 days. 36 of 1000 are showing as unassigned I'm using group policy to put the PC's in the correct folders in WSUS - one group is only showing 3 computers when it should be showing around 360! I have checked a couple of clients and everything seems in order. They can download the file from : http://server.domain.local:8530/selfupdate/iuident.cab gpresult /h gpo.htm - shows the GPO settings applying successfully. I can ping the wsus.domain.local The registry key : HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\WindowsUpdate\AU\UseWUServer is set to 1. Powershell script : $(New-Object -ComObject "Microsoft.Update.ServiceManager").Services | Select-Object Name, IsDefaultAUService - returns TRUE for Windows Server Update Service Previously when I've had WSUS issues it was the odd client. This seems to be more of an issue with WSUS itself. Are there any tricks to giving the WSUS a kick up it's butt.

@PaulZoom Can I ask what the licence restrictions might be of using Zoom in a school environment? Should staff be using it with their personal logons?

Failed! Was not to do with it shutting down - just removed the policy that does that and attempted to upgrade a PC on the domain. I suspect now it might be to do with our local administrator name being changed by group policy, have renamed the local account back to "Administrator" and I'm trying again !!

That worked. I suspect the policy that caused the issue yesterday was one from our PowerMan settings which shutsdown PC's if no one is logged on for 10 minutes, I think once the script has done it's bit and the PC sits updating with no one logged on the policy kicked in and shutdown the PC Bit more testing to do.

It should be that easy right To rule things out I've taken the test PC off the domain, logged in locally and am trying again. It's currently doing the upgrade...

I'm wondering if during the image process it has to reboot and then it can't get back in touch with the deployment share :/

My upgrade task sequence was not happy Logged on to PC as domain admin, mapped a drive to the deployment share and ran the litetouch.vbs - choose the upgrade task sequence, seemed to be successful but then PC rolls back and gives above error

Went through the whole process again and it's fine - must have got something in a twist

Trying to follow the guide here to update our MDT deployed version of Windows 10: https://askme4tech.com/how-perform-place-upgrade-windows-10-mdt On MDT the base WIM file that's deployed out (1903) is "en-GB" I've downloaded the English International version of Windows 10 from VLSC and imported in to MDT and it's saying the version is "en-US". Can I still use this for my upgrade? If not, how do I convert or get hold of the "en-GB" version? Cheers.

Does anyone know if it's possible to run WMI filters in powershell against the PC's in AD to check the results of the filter?

Might go with this: SELECT * FROM Win32_OperatingSystem WHERE BuildNumber >= "15063" AND ProductType = "1"

Sometimes you can't see the wood for the trees - thanks

I currently have the following WMI filters in place in Group Policy Management. For Windows 10 devices still running 1607 LTSB (wish we are slowly reducing numbers of) SELECT * FROM Win32_OperatingSystem WHERE BuildNumber = "14393" AND ProductType = "1" For Windows 10 devices running 1903 EDU select * from Win32_OperatingSystem WHERE Version like "10.0.18362%" AND ProductType="1" AND OSArchitecture = "64-bit" I use the WMI filters to give different desktops to the two versions, in 1607 we have lots of legacy software shortcuts on the desktop, different WSUS settings and different lockdown policies applied. I now want to run some tests on a later version of Windows 10, but it will be close enough to 1903 EDU that it can run all the same GPO's. Can anyone help me edit the WMI code so that it works if the version is 10.0.18362 and later? Thanks.

Do you not have to choose for the reports to save to the DMS? Did n't think they went their automatically?

Does anyone know if when calculating your Microsoft FTE you include cover teachers who are not permanently on staff role?

Might look in to that, but why is that preferable to just running the Update Assistant? I'm guessing because you don't have to go to the latest version?