Mindcore Techblog

You might see this error when you try to deploy Windows from SCCM. Task Sequence: has failed with the error code (0x80220005) The step running when failing is Apply Windows Settings: SMSTS.log will further more show this information: Failed to open the Task Sequencing Environment. Code 0x80220005. Please ensure you

After upgrading System Center Configuration manager 2012 R2 to SP1 (or 2012 SP2), you might see this problem. When deploying a OSD Task Sequence and not selecting when the deployment will be available (meaning now): SCCM will auto select Schedule when this deployment will become available and setting the date

Lets try to move our SCCM database to another drive. Always make sure you have a good backup and a rollback plan if something goes wrong And make sure you have system administrator permission. First start an administrative command prompt and stop all SCCM services. You can use the command

When deploying install.wim (from DVD) using System Center Configuration Manager 2012, you will see that the installation is done on drive D: instead of the expected drive C:. Even though the Task Sequence reported that the installation was done on C: You will be able to use different methods around

Microsoft release Rollup update for System Center Configuration manager and they will normally also include a client update. But if you do nothing and just use a standard task sequence your client version will be the one released together with SCCM 2012 R2. As shown her (all versions are 5.00.7958.1000):

Cumulative Update 5 for System Center Configuration Manager 2012 R2 has been released https://support.microsoft.com/en-gb/kb/3054451 Note that ConfigMgr 2012 R2 SP1 is expected next week, so you might just wait for that one instead of installing CU5. So once again it’s time to take a closer look at how to determine

When you install the Configuration manager client you will see Software Center in your start menu. In some situations you might not want this to happen. The installation of the menu items can be excluded if you use the installation property, as shown here in a Task Sequence. /ExcludeFeatures:ClientUI After

Whenever you encounter and error in your Task Sequence you will see a Task Sequence Error popup. This message will be shown for 15 minutes by default. You might first be back after the 15 minutes has passed, and then the machines could be at the login screen. You actually