Lee_West

Hi Folks, I've been banging my head against a brick wall with this for days now. It may seem odd, but the way I work with images and MDT is to have a single captured image that I tinker with, I capture that with DISM ++ and then reboot that image and sysprep and capture that with MDT. The reasoning behind is that I always have a non-sysprepped image to work from. I've managed to create a task sequence to do the capture only in MDT, but what I'm trying to do is roll all three steps into one. Start a capture, reboot into PE to capture, reboot back into Windows, start sysprep and reboot into PE to capture that with "- Sysprepped" on the end. How do I get the task sequence to reboot into Windows? When I put a Restart Computer task in, it just reboots back into PE and then fails the task. What am I missing?

Hi Folks, We were having a similar issue. We've got all options set to delete profiles at logoff, but nothing worked. The solution was to make one of the groups they are part of Domain Guests. Guest profiles get wiped at logoff and we've barely had an issue since. For example, all our students are part of a student group for which ever campus they are on, etc xxx.students. That was the group we added to Domain Guests. Works really well for us in terms of deleteing profiles at log off and we've had no issues with the APPX things.

I have to say this software is amazing and has made our lives so much easier. The only time we're experiencing an issue is with accounts using the spell checker. I only have the student's explanation, so I'm making a bit of an assumption, but when they right click on a word to alter the spelling Write Pad will "crash". The top menu bar is still fully functional, but the main document becomes inaccessible. If you type anything on the keyboard, save and re-open, what you typed is there. It feels like either the right click menu hasn't loaded or has crashed after a word has been changed. We've also had a couple that have just closed down at random. As in the program has just closed. Again, only seems to be with the spellchecker. We're running off a network drive, but had no other issues so far. We've been telling students to use the spell check button and haven't had any issues with that.

That's parts 3-5 of what I use, so yes in theory, it should do. The problem I had was the 40 folder deep nesting of Application Data. The structure ended up being something like C:\Windows.old\username\AppData\Local\Applicat... Data\Application Data\Application Data\Application Data\ for about 40 levels. It maxed out the 260chr limit, even with NTFS long names enabled in GPO.

That'll be the next thing. If we hit any major issues or if we want to scale the image down. Pushing nearly 60gb at the moment.

@ass17 Two posts up . You can't use disk cleanup remotely, as you need to click 'Yes' when removing old Windows installations. I've not been able to find a way to do that with out actually being either at or TS'd to the PC

This was a mandatory profile on the network. Roamers didn;t have the issue, but we're swapping them to using UE-V at the moment, as we use Deep Freeze, so everything gets lost at reboot. Problem is we have tonnes of software to reinstall, a chunk of which works, but the installers might not as it's old Win98 stuff.

@Chuckster I use PDQ to deploy it, but it uses a a sysinternals tool called Junction to scan windows.old for junction points then outputs them to a text file. I then found a Powershell script that looks at that text file and deletes the junction. That bypasses the 260chr error. I then use takeown, Icacls and RD to delete it. #Run in CMD c:\tools\junction64.exe -accepteula -s -q C:\windows.old > %temp%\junc.txt -force #Save below as a PS Script foreach ($line in [system.IO.File]::ReadLines("$env:temp\junc.txt")) { if ($line -match "^\\") { $file = $line -replace "(: JUNCTION)|(: SYMBOLIC LINK)","" & c:\tools\junction64.exe -d "$file" } } #Run the next three parts in CMD takeown /F C:\windows.old /R /D Y echo y| cacls C:\windows.old /T /Grant Everyone:F rd /s /q C:\windows.old What had happened was a junction had been created in Application Data that made about 40 levels of the same folders underneath, so steps 3-5 on their own would fail every time.

Hi all, That was exactly the issue we had. No amount of profiles changes would solve it, so we abandoned a network one and just use the default one on the PC. We've not had any reports of errors so far. Just for the record, our image has been a series of upgrades. We went from fully patched Win 7 to 1709, then to 1803. Just starting with 1809 today. Looking at deploying it via WSUS if I can, especially now I've figured out how to remove the Windows.old folder remotely. Seemed to have a massive junction point in application data, so it ran over 260chrs, so takeown kept crashing out. Right pain. Stumbled across this while looking for a way to remove Mixed Reality Portal. Thanks for the heads up