So now that this is an official part of Horizon, how do we get help? Do we have to open a support ticket? I updated my MDT deployment with the new version and now it fails at the optimize step every time and I can't determine why.

GSS ticket is the way forward. That being said, it looks like the team that published OSOT renamed the executable to _2111, change that back to (2111) and everything should work fine.

Hello Everyone, I have multiple applications that appear to be failing after running OSOT.

Here is the example Event Viewer entry from one of them:

Application: EncompassInstaller.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArgumentNullException at System.IO.Path.Combine(System.String, System.String) at EncompassInstaller.ConfigSettings..cctor() Exception Info: System.TypeInitializationException at EncompassInstaller.Program.writeLogRegistryKey(Boolean) at EncompassInstaller.Program.Main(System.String[])

If I revert to previous snap before doing OSOT I can install that application just fine. I'm pretty conservative on OSOT settings but for a life of me cannot figure out what breaks it and what the fix could be.

We are running Windows 10 20H2.

Did anybody encounter anything similar?

Lukasz - I retract my last statement about Defender. Was unable to reproduce. Went thru all my steps again and found out what I did to fix installing Encompass.

Two Reg keys were identified as resolving the issue that were different than a fresh Win10 20H2 machine.

The two keys were
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{89820200-ECBD-11cf-8B85-00AA005B4340}]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components\{89820200-ECBD-11cf-8B85-00AA005B4383}]

I copied these back from a fresh machine and rebooted and I was able to install Encompass without issue.

Wow that is great news. We have started going the route of installing all components manually instead of using smartinstall. Then we ran into an issue with eFolder but were able to resolve it by adding blank Encompass Key in HKEY_CURRENT_CONFIG\Software and granting AUthenticated users modify rights to it.

Thank David you very much for sharing your findings

I have just tested it and you are 100% correct that it is resolved by reimporting those two keys. Very nice find, how did you find it if you don't mind sharing?

I found the resolution - at some point, I dont THINK it was OSOT but it may have been - something removed the Windows Defender program completely and some part of Encompass install required it. The files missing were located in c:\programdata\microsoft\windows defender\platform and c:\windows\system32\drivers\wd\ - restoring these missing files and reactivating the related services (with a reboot in between) resolved the issue and encompass installed as expected.

My assumption is that some function its using to pull down install files for VC++ requires defender to scan the files on download and so was failing on that part.

And the MS Security Center needed to be reinstalled via powershell

You should re-think how you manage your master image(s).
Kicking out new (and always clean) images is easy if you have the process down. I neverhave an issue with teh (vmware tech zone) method below

-=- So many issues come from trying to roll back customizations to install and update software, so why bother...?

Do this -

Load a New Win 10 from ISO, pick your level 20H2/21H1 etc,

Enter Audit mode half way through Win 10 install (Ctrl Alt Shift I believe)
- Audit mode ensures ALL changes and installs are in teh DEFAULT profie
- Win 10 really makes exiting the Def profile near impossible after Audit Mode is exited.
- Install VMware tools
- Install software
- Run windows updates
- Office 365 (Choose how you install this)
- Install VM agents, AppVol, FSLogix, DEM, Horizon etc (inproper order)
- Shutdown while in Audit mode and make it a template.
---- DO NOT CLICK FINALIZE IN AUDIT MODE IN THIS IMAGE -=EVER=-
---- If you accidentally finalize this Master image, start over...

Clone to new machine
- Power on clone, run through OSOT
- OSOT Optomize
- I have a customized template I use to not screw with edge or OneDrive, etc
- Reboot
- OSOT GENERALIZE
- This step officially exits Audit mode and NO software should be installed after this.
- You can install things, but keep in mind software changes may not make it into the default profile after
the Audit mode is exited.
- ReName machine
- Join Domai (if you do)
- Set admin password, set FSLogix groups if needed
- OSOT Finalize
- I do NOT create local GPO with OSOT (My preference)

I use this method to spin up instant clones that are fully updated every few weeks for thousands of users, image is always working and updated. testing pool for a week, and Deploy to the masses.
MDT can help with some of this.
It may seem like more "Work" but it is not. This is a safe and easy way to maintain an updated (and clean) image.

Convert Template to VM,
Update, install (Leave in Audit mode)
shutdown,
Clonen to new VM, Customize, generalize finalize, snapshot and deploy
rinse and repeat.

That is a good point. At this point we do not have time to really redo our image but definitely something to think about. We do however have couple of applications that would require to be on a domain to get installed so not sure how we could achieve that with Master Image (prior template) to accommodate this without exiting audit and adding it to the domain

Im having this same issue when trying to install Encompass - did you find a solution besides not using OSOT as it would be a lot of work to start over if I had to revert to pre OSOT

A few security solution discover there is malicious content within, any advise?

Can you provide a bit more detail please?

Is this malicious content within the OSOT tool itself or within a Windows you are creating? What was discovered and what tools were used in the discovery?

I am still working on my MDT based OSOT deployment. It's mostly working well, but I noticed recently that my images are prompting for Windows updates. I thought I'd disabled that in the OSOT settings in the task sequence. When I checked, that setting was unchecked.

I checked it, hit apply and ok. When I open up the settings again, the update box is unchecked again. All other settings appear to stick fine.

Is this a bug in the template for MDT?

After some additional testing the disable updates check box will only stay enabled if Disable notifications is also enabled. I do not want to disable notifications though.

I just noticed that someone opened a bug for this already, #165. Thanks.

There are multiple Windows Update steps in the tasks sequence (4 from memory). Make sure you disable all of them if you don't want updates applied during image build.

I do want updates during the build. I want them disabled for the end user after the image is deployed. This is a noted bug, #165. In the task sequence under Optimize, The Disable Windows Update check box won't stay on. The user who posted the bug states how to edit the xml file to fix it. That is working for me now.

Ah ok now I understand. You mean when you select that option in the Optimize step.

There does look like there is a bug there. For me this always selects to disable Windows Updates (this should be the default), regardless of what I set the radio button to.

It does now default after I made the recommended change to the ts.xml file for the deployment task.