Assume that a Microsoft System Center Configuration Manager task sequence that uses the “Install Software Updates” step installs a software update that triggers multiple restarts after the task sequence successfully runs the Install Software Updates task. In this situation, the task sequence can fail and generate the following error message:
Task Sequence environment not found
Note You can avoid this issue in System Center 2012 Configuration Manager Service Pack 2 and System Center 2012 R2 Configuration Manager Service Pack 1 by using the new Retry option in the Install Updates task sequence step. For more information, refer to the Install Software Updates documentation on the Microsoft TechNet website.
The first restart that is initiated by the software update is controlled by the task sequence. However, the second restart request is initiated by a Windows component (typically, Component-Based Servicing) and is not controlled by the task sequence. Therefore, the task sequence execution state is not saved before the restart because the second restart is not controlled by the task sequence. When the task sequence resumes after the second restart, no state is available to continue successfully.
Continue reading Task sequence fails in Configuration Manager if software updates require multiple restarts
here is what you need to do when you get the error blow in SCCM2012 console:
“Cannot edit the object, which is in use by ‘’ at Site ‘’.”
This happened as the result of the ConfigMgr console crashing while he had the object open.
To resolve this issue connect with sql management studio to the SQL server where the database is running and then execute the code below:
select * from SEDO_LockState where LockStateID <> 0
The query above will get you a list of possible locks on the dB, with the code below you can remove the lock:
DELETE from SEDO_LockState where LockID = ‘<LockID of the record identified in the previous query>’
Once the record is removed, you should be able to modify the object.
When testing the latest Build of Windows 10 I got an error installing the Configuration Manager 2012 R2 client, it fails installing the Windows Update agent with the following error in the CCMSetup.log file.
“File ‘C:WINDOWSccmsetupWindowsUpdateAgent30-x64.exe’ returned failure exit code 775. Fail the installation.”
Continue reading SCCM 2012 client fails to install Windows 10 Build 10049
SCCM 2012 is able to uninstalls the following antimalware software only:
- Symantec Endpoint Protection version 11
- Symantec Endpoint Protection Small Business Edition version 12
- McAfee VirusScan Enterprise version 8
- Trend Micro OfficeScan
- Microsoft Forefront Codename Stirling Beta 2
- Microsoft Forefront Codename Stirling Beta 3
- Microsoft Forefront Client Security v1
- Microsoft Security Essentials v1
- Microsoft Security Essentials 2010
- Microsoft Forefront Endpoint Protection 2010
- Microsoft Security Center Online v1
If you try to install the Endpoint Protection client on a computer and the uninstall of an existing antimalware solution is not supported, then the Endpoint Protection client installation will fail. In this case, you can use application management to uninstall the existing antimalware solution, install the Endpoint Protection client and then use the Manage Endpoint Protection client on client computers client setting to let Configuration Manager manage the newly installed Endpoint Protection client.
The list is available here: http://technet.microsoft.com/en-us/library/4acd0c29-e453-4863-8194-e479263291c8#BKMK_EndpointProtectionDeviceSettings