LeonC

https://www.theleys.net/vacancies/it-support-analyst/

https://www.theleys.net/vacancies/it-support-analyst/

IT Support Technician - The Leys

https://www.theleys.net/vacancies/it-support-technician/

https://www.theleys.net/vacancies/senior-it-support-technician/ We are seeking a Senior IT Support Technician to provide first and second line support for IT and audio-visual technology to The Leys community. You will assist the IT Operational Manager in the deployment and maintenance of equipment and services, and provide first line support for all the School’s managed computing, printing facilities and audio-visual equipment via the School’s Servicedesk. We are looking for somebody with excellent technical and interpersonal skills and at least 4 years experience of providing IT support at 1st and 2nd line level. The Leys is an inclusive and inspiring co-educational boarding and day school offering an incredible learning environment and pupil experience in Cambridge. Putting pupils at the heart of everything we do, our shared values create a strong, caring, and cohesive community. The successful candidate will be joining a dedicated, successful, and welcoming team of teaching and business professionals, committed to working together to combine their skills, experience, and insights to deliver an excellent education to our pupils. This school is committed to safeguarding and promoting the welfare of children and young people and expects all staff and volunteers to share this commitment. Before appointment to any role in the school, checks including an Enhanced DBS Check and workplace references will be undertaken in accordance with current statutory guidance. Evidence of eligibility to work in the UK is required. A six-month probationary period will also apply. The Foundation is committed to fostering an inclusive culture that promotes and values diversity and celebrates the diverse voice of our community. Senior IT Support Technician Role Profile Application Form For further details call 01223 508955 or email [email protected] Applications with a covering letter should be submitted to HR, The Leys School, Cambridge CB2 7AD or [email protected] by 09.00 on Friday 19 May 2023. This role has the opportunity for regular contact with pupils and therefore is exempt from the Rehabilitation of Offenders Act 1974. By applying for this role, you are consenting to The Leys School storing your personal data. Please read our ‘Privacy Notice for Job Applicants’ for further details.

Just an update to this post. I made a little script that registers all versions of the Microsoft.UI.Xaml instead of a static version. This avoids any maintenance following Microsoft Updates. The first part needs to run with administrator privileges to be able to access the WindowsApps folder, but the second part needs to be run as the user to register the applications within their session. I achieve this using the Ivanti Workspace Dynamic Permissions feature. If you don't have this, you could split this into two scripts. The first script could be run with admin or system privileges at machine start up. The second script could then be run in the user context when they login. #Get list of installed versions of Microsoft.UI.Xaml Get-ChildItem "C:\Program Files\WindowsApps" | Where-Object {$_.name -like "Microsoft.UI.Xaml*"} | Select Name | Export-CSV -Path C:\Support\MicrosoftApps.csv -NoTypeInformation #Register each installed version of Microsoft.UI.Xaml $items = Import-CSV C:\Support\MicrosoftApps.csvforeach ($item in $items){ $foldername = $item.Name Write-Host $item.Name Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\$foldername\AppxManifest.xml"}

I use Mandatory profiles with RES Workspace. I get the issue mentioned here on both a customized and non customized Windows 1809 image. I run the following Powershell command at logon and it has resolved the issue for me for all of the modern apps I have tried. Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.1_2.11906.6001.0_x64__8wekyb3d8bbwe\AppxManifest.xml" Add-AppxPackage -DisableDevelopmentMode -Register "C:\Program Files\WindowsApps\Microsoft.UI.Xaml.2.1_2.11906.6001.0_x86__8wekyb3d8bbwe\AppxManifest.xml" Perhaps this will help someone else.

I managed to get the start menu working on 1703 by making sure the "Authenticated Users", and "All App Packages" groups had full permissions over the mandatory profile hive.

No problems, glad it worked for you! Are you experiencing the same issue of user profile folders not being successfully deleted when users log out?

I have found a solution to the problem of search not working in build 10240 (RTM) and Cortana not working in 10586 (November 1511 build) when using mandatory profiles on Windows 10. The issue is due to a required permission in the registry hive on the Mandatory profile not being present when you follow the Microsoft instructions to create a Mandatory profile with Sysprep. I got around this by opening the Mandatory profile's NTUSER.DAT hive in reg edit. I then added "Authenticated Users" and most importantly "All App Packages" with full permissions from the root level of the hive. This permission seems to be required to configure the search and Cortana apps when a user log on. Obviously, you still need to change the NTUSER.DAT to NTUSER.MAN before deploying it. Now that I have this working, I am having problems when users log off. The profile isn't removed properly, the TileDataLayer folder (which contains the modern start menu database) is still in use by the Tile Data Model Server Service. The next time the user logs in, a new profile .001 or .domain is created. The new profile uses the TileDataLayer folder from the first profile. When the user logs off, the .001 or .domain profile is deleted successfully. This behavior continues until you restart the machine, at which point a new TileDataLayer folder is created in the .001 or .domain profile which is not deleted when the user logs out. I can resolve this issue by stopping the Tile Data Model Service manually at log off, but this is a really ugly fix and it fills the event log with errors. Has anyone else had this issue?