nhottinger

Been looking for some recommendations but can't find any. Can MBAM be installed directly on the SCCM server or do they need to be separated on different hardware?

Thank you for the information. I have set this up for a few test pc's before we roll it out to the org.

Currently running CM1806 and looking into Endpoint Protection as a replacement for our current AV. I have the role installed and tested it to 1 pc and it all seems great, but I don't know where to go from here? Is there some kind of setup guide I can follow with best practices included? I have a lot of questions before I even begin really testing this? What OS's is this compatible with? Will it work on Server OS's (2008, 2012, 2016)? Just looking for some guidance on what my next steps should be.

We just upgraded SCCM to 1806 including the hotfix. Everything seemed to be ok. I updated the ADK as well so I could install the new version of Windows 10. I'm currently having trouble with that as well, but that's a different post. Any idea why my windows 7 images fail at the driver package now that I upgraded SCCM? Nothing else has changed. Logs don't show anything of use that I can find. ** Update ** For all my windows 7 driver packages, I had to check "Install driver package via running DISM with recurse option". Wish that was in some kind of documentation I had read ahead of time.

We just downloaded Win 10 1809 and started to attempt to roll it out (testing) but every time the task sequence fails with unknown errors (0x80004005) at the Apply Operating System Step. I did some searching and it sounded like the version of SCCM we were on was not compatible so yesterday I upgraded to Config Mgr 1806 and also the 1806 hotfix. Thought that would resolve the issue but it doesn't. I copied the original task sequence for 1803 that was working and replaced the OS thinking that would be the easiest way to do it. Any ideas what might we wrong with the 1809 version? *Edit, my Network Admin downloaded the ARM version which will not work on our pc's. Now that 1809 is paused, I'm not going to worry about it anymore. Until the next version...

Solved: This has to do with Windows 10 and Imprivata. 1.) Run Regedit on the Windows 10 Endpoint. 2.) Navigate to [HKLM]\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers 3.) Rename “Wrapper for Automatic Redeployment Credential Provider” with the following GUID {11660363-49E2-4F87-AB2E-FD210019AE88} by adding an "_" at the front so the string should look like this: _{11660363-49E2-4F87-AB2E-FD210019AE88}

We have an issue where some of our users are accidentally reloading windows without realizing it. Yeah, if they would read the words on the screen they would realize, but lets be real, our users don't do that. Here is the scenario. We are using Imprivata for SSO and strong auth in our healthcare facility. At the Imiprivata login box, the user is able to press "Esc" and bypass the Imprivata login box. When doing that, they are then able to click on "Other user" in the lower left hand corner of Win 10. If they select Other user, they are prompted with the attached image which will literally wipe their computer if they have admin privs. Some users do for specific reasons, most do not. We have had a few cases of this already. Is there a way to remove this option or get rid of the "Other user" sign in option?

Garth, we've used this for years and I don't ever recall having any problems. It's just nice to be able to use the built-in reports to search for files and versions to report back to management. Thanks itrider, I'll give your suggestion a shot and see how it works for me.

I'm attempting to run a software inventory report to find a specific file and version on our devices. The problem is when I run the report, I get no results. I've verified in the default client settings that software inventory is setup. What could I be missing? Hardware Inventory is also enabled as I read that plays a part in Software inventory also.

For some reason, all I had to do was take out the "Run this step as the following account" and it's all imaging correctly now.

I'm trying to enable .Net 3.5 Framework during OSD and it fails every time. If I run the exact same command once the imaging TS has completed it works just fine. SMSTS.log shows it failed with error code 80004005 which is not very helpful. I have it running as one of the very last steps. Here is the command I'm using: dism.exe /online /enable-feature /featurename:NetFX3 /All /Source:"\\bvfyfs01\install$\sccm packages\netframework\sxs". I have the "Start in:" set to c:\windows\system32. Any idea what I'm missing here? Failed to run the action: Enable .Net Framework 3.5. Unspecified error (Error: 80004005; Source: Windows) TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) Set authenticator in transport TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) Set a global environment variable _SMSTSLastActionRetCode=-2147467259 TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) Clear local default environment TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) Let the parent group (Other Applications) decides whether to continue execution TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) Let the parent group (Install Applications) decide whether to continue execution TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) The execution of the group (Install Applications) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows) TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) Failed to run the last action: Enable .Net Framework 3.5. Execution of task sequence failed. Unspecified error (Error: 80004005; Source: Windows) TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) Set authenticator in transport TSManager 4/27/2018 3:31:23 PM 2904 (0x0B58) Task Sequence Engine failed! Code: enExecutionFail TSManager 4/27/2018 3:46:23 PM 2904 (0x0B58) **************************************************************************** TSManager 4/27/2018 3:46:23 PM 2904 (0x0B58) Task sequence execution failed with error code 80004005 TSManager 4/27/2018 3:46:23 PM 2904 (0x0B58) Cleaning Up. TSManager 4/27/2018 3:46:23 PM 2904 (0x0B58) Removing Authenticator TSManager 4/27/2018 3:46:23 PM 2904 (0x0B58) Cleaning up task sequence folder TSManager 4/27/2018 3:46:23 PM 2904 (0x0B58) Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing. TSManager 4/27/2018 3:46:25 PM 2904 (0x0B58) Failed to delete directory 'C:\_SMSTaskSequence' TSManager 4/27/2018 3:46:25 PM 2904 (0x0B58) SetNamedSecurityInfo() failed. TSManager 4/27/2018 3:46:25 PM 2904 (0x0B58) SetObjectOwner() failed. 0x80070005. TSManager 4/27/2018 3:46:25 PM 2904 (0x0B58) RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005. TSManager 4/27/2018 3:46:25 PM 2904 (0x0B58) RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence TSManager 4/27/2018 3:46:25 PM 2904 (0x0B58) Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ... TSManager 4/27/2018 3:46:25 PM 2904 (0x0B58) Successfully unregistered Task Sequencing Environment COM Interface. TSManager 4/27/2018 3:46:25 PM 2904 (0x0B58) Executing command line: "C:\WINDOWS\CCM\TsProgressUI.exe" /Unregister TSManager 4/27/2018 3:46:25 PM 2904 (0x0B58)

Correct, the file I need to search is in the same location on every pc (c:\Temp\file.txt). What I'm trying to get out of this, is what the file contains. This file shows us what version number of our image we have on the pc (v 3.2, v 3.3, etc). I need a list of pc names and what version of the desktop image it has, based on the .txt file.

Thanks Peter. I got it setup but it's not working at the moment. Specifically, I need to search for the .txt file in a specific location, and need the output to be the hostname of the device, and a the data from this file. It is a very small file, 1 short line. Is this possible?

Any help getting that setup? Not very familiar with compliance rules.

I know I can create a collection to search for a specific file, but is there any way to search the data inside a .txt file?

Our SCCM environment is OLD (2012 RTM 5.00.7711.0000) and we need to update. Everything is running fine but we want to start testing Windows 10 for corporate use and need to upgrade first. What is the best / quickest path to get to SCCM 1610. I've been searching around and found this site - https://www.systemcenterdudes.com/sccm-2012-version-numbers/but I'm not sure which steps, if any, I can skip. Any help is appreciated.

Yes, WSUS is installed on our SCCM server.

I've attached the .log file. I see lots of errors but they don't mean much to me. WindowsUpdate.log

Yes, the configmgr client is installed and we use WSUS to deploy updates via SCCM.

Yes I know we are WAY behind and need to upgrade, but I do have a question that we can hopefully get around while we work through our upgrade process. We are currently running Config Manager 2012 RCM v 5.00.7711.0000 and upgraded a Windows 7 pc to Windows 10. After doing so, I am getting many, what look look like temp, folders under the root of C:\. It looks to be adding about 20 folders each minute, and in the folder is another folder named Sandbox. I am able to delete them but they just come back. Any idea what this is and can I get around this?

Thanks Peter33. It seems to be working as expected. I appreciate your help!

Thanks for the walk through. I'll set this up and test.

Unfortunately I'm not familiar with how to set this up. Could you provide some assistance with that as well?

if we run "net start trustedinstaller" and it fails to start, that is our giveaway that the registry is corrupt. I'd like to run that command on each device somehow.

We have an issue in our environment where the registry on many of our pc's has become corrupt due to a bad version of Trend Micro Encryption. Because of this we can not install software or update IE once the registry is corrupt. We have worked with Trend but the only fix for this is to re-image the device. We have come to terms with this, but would like a way to find out which pc's in our environment have a corrupt registry so we can proactively "fix" them before it's a huge fire. To check the registry, we simply go to a command prompt and type: net start trustedinstaller. If it starts (or is already started) successfully the registry is fine. If it fails, the registry is corrupt. Is there any way to run a report against all our pc's with SCCM 2012 to show the bad pc's?