abaxter2

Hi all, Just a heads up really as I am still seeing issues with WSUS and windows 10 1607 updates - seems to be a bug and seems after a few reboots the clients do install windows 10 updates - Office updates etc are all good apart from if a windows 10 update is included with the other updates The latest windows 10 1607 update (KB3176934) seems to be the worst I have seen so far for failing to install! - https://social.technet.microsoft.com/Forums/scriptcenter/en-US/31718a20-64dd-43f7-87d7-c86f03f74a4d/14393-windows-update-crash-every-minute?forum=win10itprogeneral Getting beyond a joke now! Microsoft sort it out grrr.

Hi Pete, Microsoft have just released KB3176934 ( https://support.microsoft.com/en-us/help/12387/windows-10-update-history ) and listed in the improvements is: "Improved reliability of Network Controller, DNS server, gateways, Storage Spaces Direct, Group Managed Service Accounts, remote procedure calls (RPC), PowerShell, Internet Explorer 11, printer pairing and interoperability, the Windows kernel, Media Core, Windows Store, Connected Standby, Cluster Health service, the Hypervisor debugger and platform, and Active Directory." Only problem tho is that it is not installing nicely via WSUS :-( https://social.technet.microsoft.com/Forums/scriptcenter/en-US/31718a20-64dd-43f7-87d7-c86f03f74a4d/14393-windows-update-crash-every-minute?forum=win10itprogeneral

Yeah I hope the fix the issue soon as I know from my insider build that yet another cumulative update is about to be released! that would be the third one since they released build 1607! anyway at least it is not to hard to add the cumulative updates as packages - I am just adding them the same was as I add the .Net Framework 3.5 - OS|DC: MDT 2013 U1: How to Install .Net Framework 3.5 on Windows 10

Will try adding the latest update as a package and see what happens - I do think there is a bug

That is what I am seeing also

I will double check when on site tomorrow. I should of said that the task is a deploy of a custom image and not a capture of a image but that shouldn't make a difference

Hi mullet_man, Thank you for the reply and link but I already have the update mentioned in the link installed in my custom image and all was working as good as gold until the latest update released today what has caused the problem for me so it seems that with every major update will cause this problem until the bug is fixed but you are right adding any major update as a package will get round the issue and is quicker then recreating the custom image for the time being. Thanks again

Hi All, My images included all updates until today and until today I have been deploying Win 10 build 1607 fine with no problems but just to give a heads up after microsoft released their patch Tuesdays updates including: KB3176495 - I have found that a MDT task will hang at the windows update task sequence - I am not alone - https://social.technet.microsoft.com/Forums/en-US/35309dd8-f87a-41e1-8a20-33ffbb2648e2/windows-update-step-hanging-windows-10-1607?forum=mdt So there is a bug with either WSUS or MDT so for the time being I am not including the windows update with my MDT tasks - I have found that once the device is built windows update via WSUS / GPO seems to be working and as there are no students in at current I am happy to carry on this way and will keep an eye open for a fix.

Hi, The account being used must either be a domain admins account or local administrator account The powershell must be run as administrator Once in powershell run the following: Export-StartLayout -Path C:\Layout.xml Note there are no " and that you can name the file anything you like - it does not need to be layout just needs to have .xml at the end. I have found that if you try and add a folder to the path it does not always work but just using the root (C:\) has always worked for me. One the powershell has run you will find the file in the root of the C drive. I am sure you have already seen this but here are a couple of links: https://technet.microsoft.com/en-us/itpro/windows/manage/customize-windows-10-start-screens-by-using-group-policy https://technet.microsoft.com/library/mt188237.aspx Hope it helps

I did not go down the route of upgrading to Windows 10 via WSUS as I wanted to create my base image and roll out via MDT over a school holiday and my understanding is that is for when you are already running Windows 10 and to upgrade your windows 10 to the latest build (I could be wrong tho!) So If this is something you are going to do I would recommend checking these out: https://blogs.technet.microsoft.com/wsus/2015/12/03/important-update-for-wsus-4-0-kb-3095113/ Most important: https://blogs.technet.microsoft.com/wsus/2016/05/05/the-long-term-fix-for-kb3148812-issues/ After installing this update you must complete the manual steps (found under 'More infomation) https://support.microsoft.com/en-gb/kb/3159706 Also regarding the activation as long as you have already added your KMS keys for Windows 10 to your KMS server you should be fine.

The Windows 10 start layout GPO is inconsistent to say the least but after a lot of playing around this what I have working: 1. I do not redirect the AppData (Roaming) via folder redirection 2.All my users have roaming profiles and folder redirection. 3.I created a test user for staff / students / admin staff in their own OU and then copied the GPO that applies the folder redirection and Start Layout for each user type - renamed and edited the start menu folder redirection to my network share where I wanted the shortcuts stored - I have one share for staff / one share for students / one for admin staff and one for 32 bit version of Office 2016 (I run the 64 bit version of Office across my site apart from the computers that have Sage installed as Sage will not work with the 64 bit version of Office) within these GPO's under folder redirection -Start Menu - properties - settings untick 'Grant the user exclusive right' and Also apply to windows 2000 but leave a tick in move the contents of the Start Menu to the new location (for now) 4. Sign in with the test accounts so that the content of the start menu gets copied over to the new location and then go back to the GPO and untick 'Move the contents of the Start Menu to the new location' 5. Go to the network share that holds the start menu shortcuts and remove any that you do not want the user to have access too and of course add any that are need that are not already there. 6. Create a test accounts that can run powershell and make sure the GPO with the new start menu redirection are applied to those users. 7. Create the start layouts that I want my users to have and export the xml file. 8. Push the newly created .xml files out to all computers via GPO 9. Edit my test GPOs that have the new Start menu redirection and apply the the start layout to point to the new .xml file. 10. Sign in with the test accounts that have the test gpo of start menu redirection and the start layout .xml - At the point I can see all is working and as I have pushed the .xml out to all computers I can test this on any device. 11. Now I know this was working for my test accounts I edited my GPO that applies basic settings to all computers and edited - Computer Configuration - Policies - Administrative Templates - System - User Profiles and enabled 'Delete cached copies of roaming profiles' and of course warned my users that the network would run slow 12. Edited the GPO settings that apply to my users to match the ones that that I created for my test accounts - just edited the Start menu redirection (unticking all boxes under settings) and pointed the start layout to the newly created .xml file 13. Because i had move from Windows 8.1 in user GPOs under 'Start Menu and Taskbar' I had enabled 'Remove All Programs list from the start menu' but now I set this to 'Not configured' so that if the start layout fails my user can still get access to the programs via 'All apps' but only have access to shortcuts that are stored in the redirected folder. 14. Set 'Delete cached copies of roaming profiles' to not configured in my GPO that applies basic settings to all computers. So far after do this I am finding the start menu to be working. I have also found / working on proving that Impero causes problems with start layout on laptops because it queries Win32_Product class when a device starts (https://support.microsoft.com/en-gb/kb/974524) and as we know in Windows 10 the shortcut are stored in database. It strange that it only affects the laptop but the only reason I can think of is because my desktop devices are turned on via power management before they are used it gives the device time to sort the database where the laptops are turned on when and off when needed but what I am seeing is any laptop that does not have Impero installed are getting the correct start layout and any with Impero are not. I'm not saying for sure that it is Impero - just sharing my findings as I have found with the above Start menu redirection and the new .xml all users who sign in to any desktops get the correct start menu but still have a few issues on the laptops. You may also want to have a look at this great thread about using Classic Shell: http://www.edugeek.net/forums/windows-10/163286-windows-10-start-menu-working-solution.html

I know I am late to this thread but thought I would just share that I have found that access points that are connected to spanning tree enabled switches have problems with the UNC hardening feature but access points connected to dummy switches (unmanaged) do not have any problems - So I disabled spanning tree on my managed switches and have had no problems with the UNC hardening feature and do not need to add any registry keys or configure the UNC hardening GPO - I have also enabled 'Disable detection of slow network connections' and enabled 'Always wait for the network at computer startup and logon' and also on my GPO that applies to my Wi-Fi I also enabled 'configure Group Policy slow link detection' set to: 0. With these setting in place I have found that my GPO's apply to lan and wireless clients without a problem.

I would also say this is a driver issue. I moved to Window 10 from Windows 8.1 - Wake on lan worked fine in Windows 8.1 but on Windows 10 with same drivers would not wake - went to device manager and update driver software - then checked power management - restarted the device and found wake on lan worked - then added the new driver to deployment share so that any new builds would work with wake on lan