I followed this guide to perform the windows 10 in place upgrade from windows 7:
https://technet.microsoft.com/en-us/library/mt426642%28v=vs.85%29.aspx
The task sequence seems to run fine until it finishes downloading the items in the "Upgrade Windows" step. The items finish downloading and the task sequence stalls at "Upgrade Windows" until the error message 0x00000001 appears. The task sequence then enters the "Recover from Setup Failure" step but never recovers.
Help is appreciated.
Thanks
I have now built two brand new clean Windows 10 x64 Enterprise reference computers on a virt. When I go to capture to the Configuration Manager 2012 R2 updated with the latest cu, I get error code 0x00004005. I get this on the first run through right after building from the Windows 10 - build 10586 that I downloaded last week before MS pulled it.
The SMTSLog.txt located here: C:\users\username\AppData\Local\Temp shows this:
Executing command line: "C:\Windows\system32\sysprep\sysprep.exe" /quiet /generalize /oobe /quitPrepareOS11/23/2015 12:12:07 PM4184 (0x1058)
Process completed with exit code 0PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Sysprep state set to IMAGE_STATE_COMPLETEPrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
The OS has not been generalized using sysprep.exe, or sysprep did not complete.PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
bSysPreped, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,514)PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Sysprep did not complete successfullyPrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
RunSysprep(sCmdLine, bActivate, m_bDebug), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\prepareos.cpp,1375)PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Unable to sysprep the machine, hr=80004005PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
pCmd->Sysprep(bActivate, bMsd), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\prepareos\main.cpp,270)PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Sysprep'ing the machine failed, hr=80004005
PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
De-Initialization successfulPrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Exiting with error code 16389PrepareOS11/23/2015 12:12:08 PM4184 (0x1058)
Process completed with exit code 16389TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
!--------------------------------------------------------------------------------------------!TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Could not find CCM install folder. Don't use ccmerrors.dllTSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Failed to run the action: Prepare Operating System.
Unknown error (Error: 00004005; Source: Unknown)
TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Do not send status message in full media case
TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Set a global environment variable _SMSTSLastActionRetCode=16389TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Set a global environment variable _SMSTSLastActionSucceeded=falseTSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Clear local default environmentTSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Let the parent group (Capture the Reference Machine) decides whether to continue executionTSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
The execution of the group (Capture the Reference Machine) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)TSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
Could not find CCM install folder. Don't use ccmerrors.dllTSManager11/23/2015 12:12:08 PM4088 (0x0FF8)
David Grand
=====
(two hours later) - I just spun up a hardware based Reference Computer. Same problem. See below:
Hello,
I know I can add the following registry key to our existing WDS server (see below) to present an "F11 menu";
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\WDSServer\Providers\WDSPXE\Providers\BINLSVC]
"AllowServerSelection"=dword:00000001
...that if pressed, will broadcast for any other WDS servers on the same subnet and present them as menu options to PXE boot from, but what if the other WDS (SCCM DP) is on a different subnet? Our DNS/DHCP infrastructure is not MS, we use Cicso DNS and DHCP and our servers have static IP's (if this matters), we currently use IP helpers to find PXE which we set per location. The goal is to leave our existing WDS infrastructure in-place to serve up our mature Windows 7 image (not created using SCCM or MDT) while still being able to use our SCCM infrastructure for bare metal Windows 10 deployments. I know SCCM can "upgrade" an OS but we're looking at wipe-and-load (party due to McAfee encryption but either way, not upgrading!)...
Thanks for the help,
Jack
I am trying to deploy an OS from SW Center and getting the error "The Software cannot be found on any servers at this time." The DP is fully up to date with all content and the boundary is set correctly. Looking at the execmgr.log on the client, I see this:
Validating chain of dependent programs for package CAS000C5 optional program *execmgr 1/31/2014 8:16:31 PM 2492 (0x09BC)
Validating package CAS000C5 program * in the chain. The content request ID is {00000000-0000-0000-0000-000000000000} execmgr 1/31/2014 8:16:31 PM 2492 (0x09BC)
Creating an optional execution request for package CAS000C5 program * execmgr 1/31/2014 8:16:31 PM 2492 (0x09BC)
Content is not available on the DP for this program. The program cannot be run now. execmgr 1/31/2014 8:16:56 PM 2492 (0x09BC)
OnOptionalExecutionRequests failed for program * execmgr 1/31/2014 8:16:56 PM 2492 (0x09BC)
The problem with this is the package ID does not exist on the server in any way. It is nowehere to be found in any reports and not in the content distribution area.
What is going on?
Bryan
Hello,
I have captured an image of Windows 10 Education (using imagex) with an embedded unattend.xml file which successfully works when restored / deployed using imagex. This particular image is being sent to the manufacturer to be the OEM image supplied with
the machine. However I'd like to add this WIM into our SCCM to allow us to reimage devices when need be without having to manually restore it using imagex.
When I attempt to restore the image using SCCM, firstly it doesn't skip the product key page as it does when restored using imagex and it doesn't create the username it is meant to create from the unattend.xml file which again works fine with imagex. How can
I get SCCM to simply deploy the WIM without it making any changes or messing with the OOBE experience which has been configured through the embedded unattend.xml located in the c:\windows\panther directory?
Thanks!
Hi,
OSD Task sequence fails at the very end of the build and following are the smts.log which it generates. Any idea what is going wrong? We can log in to PC's but some of the apps and credentials are missing. Seems like PC's is not done correctly. Please see following smts logs.
Failed to set log directory. Some execution history may be lost.
The system cannot find the file specified. (Error: 80070002; Source: Windows)OSDSetupHook11/19/2015 1:26:48 PM1020 (0x03FC)
Executing task sequenceOSDSetupHook11/19/2015 1:26:49 PM1020 (0x03FC)
Task Sequence environment not found.OSDSetupHook11/19/2015 1:26:49 PM1020 (0x03FC)
Attempting to get active request.OSDSetupHook11/19/2015 1:26:49 PM1020 (0x03FC)
Failed to create instance if Software Execution Request Managerr. 0x80070005OSDSetupHook11/19/2015 1:26:51 PM1020 (0x03FC)
Waiting for ccmexec process to start.OSDSetupHook11/19/2015 1:26:51 PM1020 (0x03FC)
Failed to create instance if Software Execution Request Managerr. 0x80070005OSDSetupHook11/19/2015 1:26:57 PM1020 (0x03FC)
Waiting for ccmexec process to start.OSDSetupHook11/19/2015 1:26:57 PM1020 (0x03FC)
Failed to create instance if Software Execution Request Managerr. 0x80070005OSDSetupHook11/19/2015 1:27:04 PM1020 (0x03FC)
Waiting for ccmexec process to start.OSDSetupHook11/19/2015 1:27:04 PM1020 (0x03FC)
Failed to create instance if Software Execution Request Managerr. 0x80070005OSDSetupHook11/19/2015 1:27:09 PM1020 (0x03FC)
Waiting for ccmexec process to start.OSDSetupHook11/19/2015 1:27:09 PM1020 (0x03FC)
GetActiveRequest failed with error code 0x87d01012
OSDSetupHook11/19/2015 1:27:15 PM1020 (0x03FC)
GetActiveRequest failed. 0x87D01012.OSDSetupHook11/19/2015 1:27:15 PM1020 (0x03FC)
ReleaseActiveRequest failed. 0x87d01012.OSDSetupHook11/19/2015 1:27:15 PM1020 (0x03FC)
Deleting SMS_MaintenanceTaskRequests istance: SMS_MaintenanceTaskRequests.TaskID="{E3E29A5E-9483-406F-9C3A-19AEAE6981E9}".OSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
Removed 1 instance of SMS_MaintenanceTaskRequests for tasksequence.OSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
Uninstalling Setup HookOSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
Removing setup hook from registry.OSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
Successfully removed C:\WINDOWS\system32\OSDGINA.DLLOSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
Successfully removed C:\WINDOWS\system32\OSDSETUPHOOK.EXEOSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
Successfully removed C:\WINDOWS\system32\_SMSOSDSetupOSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgramOSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
GetTsRegValue() is unsuccessful. 0x80070002.
OSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
End program: OSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
Successfully finalized logs to SMS client log directory from C:\WINDOWS\CCM\LogsOSDSetupHook11/19/2015 1:27:16 PM1020 (0x03FC)
I updated from R2 to R2 SP1 last week and one of the new SP1 features is the deployment verification of High Risk Deployments like OSD task sequences. When users try to deploy a task sequence, they go to choose the collection and see the new High Risk Verification prompt. The user can hit OK and choose a collection as normal. The next screen on the deployment wizard asks if this is an available or required deployment. When choosing available everything works as normal but choosing required and hitting next should pop up another verification depending on the contents of the collection. The user can verify that they want to continue with the deployment wizard.
However, I’ve found that if the user's security role does not have access scoped to it for the All Systems collection and the All Users and Groups collection, choosing required and hitting next in the deployment wizard does nothing; no verification popup, no advance to the next screen. Since we delegate access to our users based on collections querying their department specific OU, and they do not have access to the All Systems or All User and Groups collection, none of them are able to run required OS deployments.
I opened a case with Microsoft today but am curious if anyone else has any workaround or has seen this issue as well.
We have a dozen driver packages in our OSD. Everything was working fine. Then I added drivers for a new model. I added it to its own group and created a new package. This seems to have broken 4 laptop builds. The drivers for these 4 laptops do not get applied. All the desktop builds still work fine.
Can adding a new driver(s) corrupt or break existing drivers?
So I then Imported the drivers for one of the failed laptops. I added it to a new category and created a new driver package. I odified the task sequence to use this new package. It runs the new driver package (I says so during the OS build. I labeled it) but the drives do not get installed once complete.
What on earth can cause this?
mqh7
Getting this error after installing Windows 10 ADK
Failed to save the current environment block. This is usually caused by a problem with the program. Please check the Microsoft Knowledge Base to determine if this is a known issue or contact Microsoft Support Services for further assistance.
The parameter is incorrect. (Error: 80070057; Source: Windows)
Is this related to missing hard drive driver in PE?
Hello All................Is it possible to do a Light Touch Installation (LTI) of Hyper-V Hosts? Is it practical? Does it have any benefits?
If possible can following be done through it:
1. Installing OS, Prerequisites, Hyper-V and addition into existing cluster?
2. Can we have Hosts join Hyper-V Cluster based on its Hardware Profile, OS, Network and Storage?
3. Can we have a Task Sequence to configure Hosts Properties, Networking and Storage?
4. Can we have nodes added into VMM through Task Sequence?
5. Can we create LUNs, Encrypted and Unencrypted Volumes for Hosts?
6. Can we create Virtual Switches, Networks and Sites through Task Sequence?
Have setup new TS for Windows 10 Enterprise under R2 SP1 CU1. I apply the Software Updates step after installing apps so that it picks up all the updates including Office 2013. On laptops I am enabling Bitlocker. I'm finding the SU step finds about 57 patches, downloads then starts applying and then stops at particular office updates - nothing showing in SMSTS.log other than "Waiting for RefreshUpdates complete notification from Updates Deployment Agent". Strangely a desktop (non bitlocker) works just fine i.e. applies all the patches without fail. So I've had to move the apply SU step higher up so it only applies O/S updates and that is ok. I tried taking specific update it was failing out of the SU group but it hangs at a different Office update, but as I say never a problem with the desktop - same build just no bitlocker. I also tried moving the bitlocker step below the software updates to no avail. The TS never times out - i.e. still sitting there over night hanging at the SU step
Ian Burnell, London (UK)
Our OSD Task sequence has many pc's model's which re-image using a single OSD Task sequence. We are just adding a new hardware Model to our OSD Task sequence, added its drivers and drivers packages to Task sequence and now trying to re-image it with windows 7 for the first time.
To image, I boot from a disk, then plug in a password at the task sequence welcome, it retrieves avaliable policy, I then select the appropriate task sequence (in this case Windows 7x64 Role Based)... All that is good.
It then goes to Format and Partition the HDD
I then receive:
Task Sequence: Windows 7 x64 Role Based has failed with the error code (0x800700A1)
Following is the smts log.....
I added only Network driver to winpe.... nothing else and added the cab file as driver package to OSD task sequence.
https://onedrive.live.com/redir?resid=92D0BDECFE5C858D!1146&authkey=!AAPO8AEU3CBAN6E&ithint=file%2clog
Hi all. So we run our Build & Capture task sequence every month to include the latest patches in our standard image. This has worked great in SCCM 2012 for the last few months. However, this month the TS has been failing at one of the "Install Software Updates" steps. We have 2 other install software updates steps earlier in the TS which work fine, but this 3rd pass has been failing lately.
The error I can see in the SMSTS.log is:
Refreshing Updates InstallSWUpdate 11/25/2015 1:28:53 PM 2344 (0x0928) Successfully initiated RefreshUpdates operation InstallSWUpdate 11/25/2015 1:28:57 PM 2344 (0x0928) Waiting for RefreshUpdates complete notification from Updates Deployment Agent InstallSWUpdate 11/25/2015 1:28:58 PM 2344 (0x0928) Process completed with exit code 2278557265 TSManager 11/25/2015 1:42:39 PM 1932 (0x078C) !--------------------------------------------------------------------------------------------! TSManager 11/25/2015 1:42:39 PM 1932 (0x078C) Failed to run the action: Install Software Updates2. Post install scan failed (Error: 87D00651; Source: CCM) TSManager 11/25/2015 1:42:39 PM 1932 (0x078C)
I have not been able to locate any other posts or articles about this issue. Any ideas? Thanks in advance.
i am facing a terrible issue migrating xp machines to windows 7. i have done making my USMT script to match our needs and added all the settings to TS. TS does simple jobs like reading network and computer config, scanning user data and preparing xp machine to reboot in winpe. i was getting error code of win32 for boot staging. this stopped me to do the migration. so i googled and found the KB2910552 which seems MS offers this to solve the issue. but none of both isses solved. first issue about boot staging and incompatibility of bootsect.exe remains. also every XP machine (even after installing the Client version of KB 2910552) getting NTLDR error after boot staging failure and i lose the OS completely. even i tried replacing bootsect.exe from adk 8.0 and this doesn't helop at all. lastly i tried using winPE 3.1 that i created using WAIK 3.1 and i could pass the Staging step. but right after that i'm getting another initialization issue when machines boots up using WINPE 3.0 or WINPE 3.1 . it's actually failing on initializationg hardware devices. I even tried updating whole system including servers,clients and admin console and again no chances to pass this ! there are some questions that i need to get an answer please:
1- is this really so hard to have SCCM working with windows xp or i am a noob on this really !!!!
2- why KB 2910552 does not help at all !! is there any points at all !!
3- do i need to install KB 2910552 even after updating Servers and clients with SP1 and CU2 ?
4- what should i do now !! is this Driver related ? or i am missing some thing else !
Are there any well documented cases where WAN Accelerators have caused [unusual] issues when SCCM traffic is 'optimized'; specifically when distributing data or attempting to access shares as part of OSD, Build & Captures or Capture Only scenarios etc.?
HISTORY
I created an SCCM Build & Capture (non-MDT) Task Sequence and the capture consistently fails because of invalid credentials:
I've done the following (multiple times) to verify it wasn't a silly pebkac /id 10-t issue:
As a last resort I created a share on the Distribution Point that was local to the VM in question, mirroring the permissions setup on the share on the Primary Server where I was originally trying to save the .WIM. This seems to work flawlessly as its successful 10 out of 10 times. When saving to the PS, it was very hit-or-miss sometimes working as many as 3 times in a row then failing as many as 15 times before the next successful connection.
But this issue isn't limited to OSD's or builds and captures. Frequently when distributing data it the package fails to reach one or more DP's.
The next steps IMHO are packet captures from both ends and involving our architecture and engineering teams but knowing this is not a one off pain point for SCCM admins is helpful.
Hi,
One of our customer wants to create and deploy windows 10 image using SCCM 2012 SP1 infrastructure. I understand for support for windows 10 current SCCM environment need to be upgraded with SCCM 2012 SP2. Since it will take a time is there a possibility to create windows 10 golden image using current SCCM 2012 SP1 infrastructure and what are the issues will encounter if we create the image
Regards,
Madhan
This must be a problem for other users, hence me posting.
After moving to R2 SP1 (SP2 in other words) and upgrading to ADK 10, and recreating boot media, I need to get Windows 10 (NDIS65) network drivers for all our devices.
For legacy devices (and i'm only talking about 4 years old) OEMs are not interested in writing new drivers for old kit, so potentially this upgrade has rendered a LOT of kit unusable from an SCCM OSD perspective.
Does anyone have any tips and tricks to get non Win 10 drivers working in the boot media?
I am struggling in particular with Broadcom drivers - which is especially annoying as they claim to be W10 compatible. Even when manually installing the inf in WinPE successfully and running a NETCFG -WINPE it doesn't appear to be working.
Dear Experts,
I was doing a refresh scenario basically creating a Task Sequence so that I could replace Windows 7 OS with Windows 10 with all user data migrated to new OS, I am facing two issues
a> The Task sequence is not starting from within Windows 7 though I have deployed it to Configuration Manager client.
b> The Task sequence is starting from PXE boot, but after completion I cant see user data migrated over to Windows 10.
My goal is to run the TS from within Windows 7 so that it could collect all user data and copy them to SMP, after Deployment all user data migrates to windows 10.
Kindly provide a helping hand.
Hi there experts
Today i noticed some strange Information in the ConfigMgr Console. I've got a Build and Capture Task-Sequence, which creates a Reference Image for Windows 10 Enterprise x64.
When i Import the generated WIM File into ConfigMgr the following OS Version is shown in the Operating System Images Node.
From my Point of view the Version should be something like "10.0..." and not "6.2..." which would be Windows 8???
Deployment works without any problems, just noticed this. Anyone around seen the same issue?
Environment: ConfigMgr 2012 R2 SP1 CU1
Best regards, Simon