Search This Blog

Loading...

Thursday, June 25, 2015

Task Sequence: has failed with the error code (0x80220005)

You might see this error when you try to deploy Windows from SCCM.

Task Sequence: has failed with the error code (0x80220005)

image

The step running when failing is Apply Windows Settings:

image

SMSTS.log will further more show this information:

Failed to open the Task Sequencing Environment. Code 0x80220005. Please ensure you are running this executable inside a properly configured OS Deployment task sequence.

image

In this example the problem is that I am trying to use a computer name longer than 15 characters, so if you see this error check your computer name (also tailoring spaces!).

image

Monday, June 15, 2015

Skipping task sequence because it is not active yet

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):

image

SCCM will auto select Schedule when this deployment will become available and setting the date and time to now (your current time):

image

But when you for example PXE boot a computer expecting the Task Sequence to be available it might not be so, and in smsts.log you will find the message Skipping Task Sequence because it is not active yet:

image

Changing the schedule to yesterday or just one hour back will make the Task Sequence available:

image

Tuesday, June 9, 2015

Move SCCM database to another drive

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 Smile

And make sure you have system administrator permission.

First start an administrative command prompt and stop all SCCM services.

You can use the command preinst.exe /STOPSITE from your SCCM installation.

Mine is located in the following path:

"C:\Program Files\Microsoft Configuration Manager\bin\X64\00000409\preinst.exe" (the last folder is dependent upon the language of the product, 00000409 is for the English version).

image

image

Next start SQL Management Studio.

image

If you select properties on the current SCCM database you will be able to find the current file location:

image

Select Files to find the current Path:

image

Now Detach the database:

image

Select Drop Connections and hit OK.

image

The database will disappear from the Databases folder.

Copy or move the SCCM database files to the new location:

image

Attach the database again:

image

Click Add:

image

Select the MDF file you copied (in the new location) and click OK:

image

Click OK again:

image

Select the database you just attached and click New Query:

image

Run the command:

ALTER DATABASE <ConfigMgr DB> SET TRUSTWORTHY ON

image

Change owner to sa:

EXEC sp_changedbowner 'sa'

image

Ensure that Isolation Level is set to read committed snapshot by running the command:

DBCC USEROPTIONS

image

If it is set to anything else than read committed snapshot then run the following commands, if isolation level is read committed snapshot then ignore next step.

ALTER DATABASE <ConfigMgr DB> SET ALLOW_SNAPSHOT_ISOLATION ON

ALTER DATABASE <ConfigMgr DB> SET READ_COMMITTED_SNAPSHOT ON

image

Note: You might have to switch the SQL DB to Single User mode before running the two commands. Once done, change it back to Multi User mode.

Finally start SCCM Services using Service Manager or restart the server.

After moving the System Center 2012 Configuration Manager SQL Site Database to another drive, creating a new Software Update package or a new application fails

Thursday, May 21, 2015

Task Sequence installs Windows to wrong drive

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:\

image

image

You will be able to use different methods around this problem, but the fastest and easiest way will often be to use the Task Sequence variable OSDPreserveDriveLetter.

Set the variable to FALSE as shown here:

image

Insert the variable immediately before  Apply Operating System

And the result after using OSDPreserveDriveLetter = False:

image

This is actually a problem with more to it than you might think, so read this post if you want to know more and also other possible solutions.

How to Ensure that Windows Installs on C: During a System Center 2012 Configuration Manager OSD Task Sequence