Showing posts with label osd. Show all posts
Showing posts with label osd. Show all posts
Tuesday, August 16, 2016
Windows 10 OSD Task Sequence Failed with the Error Code 0x80070002
Windows 10 OSD Task Sequence Failed with the Error Code 0x80070002
When you do a Windows 10 deployement it failrd whit the error below ?
Error
ERROR: Task Sequence Failed with the Error Code 0x80070002. For more information, contact your system administrator or helpdesk operator.
Troubleshooting
Task Sequence Failed with the Error Code 0x80070002 – we see this error usually during the operating system deployment using SCCM 2012 R2. When you deploy the windows 10 task sequence to a collection and when you boot the computer from the network, during the step “Applying Operating System” you encounter the Error Code 0x80070002. In this situation what one might think would be to check SMTS.log file. I would recommend that but there is something else that you need to check first. Error code 0x80070002 in SCCM 2012 can be interpreted as a network error wherein during the OSD the necessary files are not accessible by the computer where the operating system is being deployed.
Resolution
To fix the issue Error Code 0x80070002, we have to define the network access account. The Network Access account is used only for accessing the content and not for running the task sequence. This account should have the minimum appropriate permissions on operating system deployment content it needs to access. This account is important because the computer receiving the operating system does not have a security context it can use to access content on the network.
To configure the Network Access Account, open the CM2012 R2 console, click on Administration, expand Overview, expand Site Configuration, click Sites, on the top ribbon click Configure Site Components, click Software Distribution.
Click on the tab Network Access Account, choose Specify the account that accesses network locations (by default the option is set to Use the computer account of Configuration Manager client). Click on the orange icon and add the user account that enough permissions to access the content which is required while deploying Windows 10 Operating System.
Available link for download
Monday, August 8, 2016
Configuration Manager 2012 R2 Increase the size of the smsts log during OSD Windows 10
Configuration Manager 2012 R2 Increase the size of the smsts log during OSD Windows 10
Increase size of the smsts.log
I propose a solution allowing you to increase the size of the log smsts.log during your deploy Windows 10
The solution is to start a boot image using the utility dism, and create a smsts.ini file in the "Windows" of the mounted image.
The smsts.ini file must be this:
[Logging]
LOGLEVEL = 0 LOGLEVEL = 0
LOGMAXSIZE = 5242880 LogMaxSize = 5242880
LOGMAXHISTORY = 3 LOGMAXHISTORY = 3
The active LOGLEVEL logs in Verbose mode, the LogMaxSize setting the size of the log, and LOGMAXHISTORY indicates the number of logs to keep.
Once your modified boot image, updatez your DPs and voila !!
Available link for download
Subscribe to:
Posts (Atom)