clareq

It was a few years ago, but we provided dedicated accounts for them to do their coursework for the exam, then locked down the accounts during the exam. They saved the work to a mapped drive, not to 365, and used the desktop version of Office.

So it's failing once you boot into full Windows? Could it be the Windows network drivers aren't installing? You should be able to restart the machine and log on with a local account and check drivers. As the TS works with other models it's not an app issue.

There is a free third party app called TSGui. I used it extensively to set up a screen at PXE boot with drop downs that linked to OUs. I then used the variables created to put unknown machines into the correct OU and assign the appropriate software.

I've used YouTube in the past successfully. Upload as a private video, use the edit feature to blur the faces - it uses facial recognition, so you can select the faces to leave in the clear, then download the editted video and delete from YouTube.

does this help? https://powerusers.microsoft.com/t5/Building-Power-Apps/New-line-in-email-body/m-p/168363#M56457

I used that method to limit what appears when you right click the start button. It's certainly worth testing. Another route could be to find out what registry changes happen when the tick boxes are cleared, and push them by GPO. The settings are recorded somewhere, be it registry or ini file - it's just a case of finding where and using a GPO to replicate it.

Find out where the folders are and use a GPO to set them as read only and hidden.

Have you redistributed the application once you updated the file?

OK, on the SIMS server, go to computer management, shared Folders, Open Files. Find the pdf in the list, highlight, right click, Close File.

Barfie

I raised a call about this with ESS because all staff were getting an outdated pdf every time I updated SIMS. I was advised to simply rename the S:\SIMS\documentation folder. As most staff didn't notice it was a 2019 document I doubt it was being read.

I have the below to tweak permissions on sharepoint items - you might be able to adapt it:

We have a power off script run every night, so I would expect machines in use to have been powered up this morning

Not sure it is - I have machines I know are currently in use, with a modified date in AD over 2 weeks ago.

Further to this, running the script manually, rather than via SCCM, .\image\Installer.exe -i deploy --offline_mode -q -o .\image\Collection.xml --installer_version "1.40.0.24" fails .\image\Installer.exe" -i deploy --offline_mode --ui_mode basic -o .\image\Collection.xml --installer_version "1.40.0.24" works Now to test it within a deployment