Lethcan Aernis

When you say "move" it is actaully delete the old machine opbject and create a new machine object (with same name) but in a different OU? If the account adding the machine account got permission to write to the OU it can do so, but it fails if the same name exist already in another OU if same domain. So if you can have the machine account deleted in the begning of your task sequence I think you be just fine to "move" the machine account. Sorry no help on the VBS script etc just giving another option.

Can you please in a (evelated) cmd line try to run this from the same folder that got ccmsetup.exe (normally c:\windows\ccmsetup): ccmsetup.exe /skipprereq:windowsupdateagent30-x64.exe Found it here http://ccmexec.com/2015/04/sccm-2012-client-fails-to-install-windows-10-build-10049/and it seems to apply to you even if the build isn't the same the issue seems extermly similiar. and it is the update agent that gives you the error <![LOG[File 'C:\Windows\ccmsetup\WindowsUpdateAgent30-x64.exe' returned failure exit code 775. Fail the installation.]LOG]!><time="16:09:25.242+00" date="03-07-2016" component="ccmsetup" context="" type="3" thread="4076" file="manifest.cpp:2239">

Do you have that on all hardware models? how do you install drivers for the hardware? wihtout looking in the logs it looks to me that in WinPE you got the network driver and all working, it restart and it is time to join the domain and reach packages and it fails. If it fails to joun the domain, please login locally and look at this file why it fails: C:\Windows\debug\NetSetup.LOG but all you mention to me sounds like network issue, maybe wrong or no driver loaded to the NIC.

Full path I vote for also and sinc eyou got space between Office and 2013 I would use quotations "" For /q why not /qn instead and also add a /log %temp%\mylog.log so you see that it works as wanted. Wait to uninstall? not sure that is needed since it wont go to next task sequence before the previous is finished. If both are click to run you normally don't have to uninstall previous office unless you got different architecture, I just run install and it upgrade 2013 to 2016

Hello, Just wondering if anyone has manage to image the Dell XPS 13 9350? Got SCCM 2012 R2 SP1 CU2 and when using my current TS wtih Dell XPS 13 9350 it came to the first reboot (partitioning, apply wim, check drivers, install client etc...) and then fail... acording to this link that is normal for this model if you set disk opertion to AHCI which I had: https://www.reddit.com/r/SCCM/comments/40t2iv/dell_xps_9350_9550_sccm_imaging_guide/ I switched to RAID ON as suggested in the link, and added the Intel RAID driver to my WInPE. I can boot on WinPE, partition the disk but when apply WIM in SATA RAID ON mode it fails, smsts.log says the following: Expand a string: WinPE TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) Executing command line: OSDApplyOS.exe /image:P010034A,%OSDImageIndex% "/config:P010005F,%OSDConfigFileName%" /runfromnet:True TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) Command line for extension .exe is "%1" %* ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Set command line: "OSDApplyOS.exe" /image:P010034A,1 "/config:P010005F,Unattend.xml" /runfromnet:True ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Found run from net option: 1 ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Not a data image ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) ApplyOSRetry: ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) TSLaunchMode: PXE ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) OSDUseAlreadyDeployedImage: FALSE ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) 'C:\' not a removable drive ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Searching for next available volume: ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Volume S:\ size is 350MB and less than 750MB ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Volume C:\ is a valid target. ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Found volume C:\ ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Windows target partition is 0-2, driver letter is C:\ ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) !sSystemPart.empty(), HRESULT=80004005 (e:\qfe\nts\sms\framework\tscore\diskvolume.cpp,132) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) System partition not set ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Unable to locate a bootable volume. Attempting to make C:\ bootable. ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) bBootDiskDefined == true, HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\applyos\installcommon.cpp,690) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Unable to find the system disk ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) MakeVolumeBootable( pszVolume ), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\applyos\installcommon.cpp,772) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Failed to make volume C:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system. Unspecified error (Error: 80004005; Source: Windows) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) ConfigureBootVolume(targetVolume), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\applyos\applyos.cpp,499) ApplyOperatingSystem 3/7/2016 5:01:42 PM 1980 (0x07BC) Process completed with exit code 2147500037 TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) !--------------------------------------------------------------------------------------------! TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) Failed to run the action: Apply Win10x64Ent 1511 + Office 2016 WIM. Unspecified error (Error: 80004005; Source: Windows) TSManager 3/7/2016 5:01:42 PM 1520 (0x05F0) Same TS works on vitually all other Dell models and google around it shows quicly that this model is an issue but most seems to have problem to just see the disk, and I do that... if I F8 in WinPe I can in diskpart see the disk.. and the partitioning parts work.. it is apply the WIM that fails. Thankful for help thanks

BTW do you deploy/advertise to a specific collection with a machine object in it or directly to unkown machines?

Depends how far you arrive in the OSD process. if your WinPE load and you ahve enabled F8 mode you can press F8, and then go to different locations and search for it: if not reached format the hard disk it is most likely here: x:\windows\temp\smstslog\smsts.log if it come further it is often disk drive: _SMSTaskSequence\Logs\Smstslog\smsts.log If it finish to image it goes to c:\windows\ccm\logs this all on the actual client you try to image (so do not look at server for this log like you did for smspxe.log) hope that helps?

Is everything solved here? I'm using the Microsoft Scrubs script and packaged, let it run and it uninstalls all Office products, then restart and then install O365.

wow! thank you so much, that was the issue, if I put X:\WINDOWS\system32\mshta.exe D:\_SMSTaskSequence\Packages\P0100382\test.hta my HTA shows up! of course I wont keep that path must use a varaible but 95% of the battle is done. So I still don't understand why the VBS file doesn't need a path but the HTA needs but doesn't matter. I love this forum it has helped me so much before by reading and now by these post, will try to hang around and try to give back something also and help others.

Thanks a lot, that would make sense that it doesn't work any maybe mshta.exe give exit code if ran but not finding a HTA file... I might test to hard code the path to run: X:\WINDOWS\system32\mshta.exe D:\_SMSTaskSequence\Packages\P0100382\test.hta just to see if it works.. if it does, then yeah spot on that was the issue. I didn't had to do it for pause_ts.vbs so therefor thought it wasn't needed here either but it could be a dangerous assumption. getting late here, will try it tomorrow and post back thanks!

the package ID is:P0100382 that includes the HTA, VBS and ServiceUI.exe and I refind it here: D:\_SMSTaskSequence\Packages\P0100382 so I assume it runs from that folder, or could that be the problem... I saw some put all in a .cmd file and use relative path (tilde)%dp0 etc..

It is in the package so same folder as ServiceUI.exe Replicated. So I got this in same folder ServiceUI.exe (64-bit) test.hta pause_ts.vbs Running the ServiceUI.exe with pause_ts.vbs works great, running another with ServiceUI.exe calling test.hta gives success code but it goes in the same second and nothing displayed. Added HTA support in 64-bit WinPE, if F8 and run the HTA file it goes as I want.. I maybe have to try to do misstake by misstake just to see if that also gives error code 0, or try to make the pause_ts.vbs call the HTA since I know that one works.. but sounds like a real "fullösning"

ran it again and in WinPe press F8 and then start taskmgr.exe it goes so quick but I could not see the HTA process flash by, but for PAsue vbs I see vbscript.exe (or what it is called)

Thanks Anyweb, Running it during WinPE, actually the first thing running in the whole TS, so F12, it PXE boot and bam! I can F8 and run tasklist but I'm afraid the HTA is no longer running since my smsts.log says exit with code 0 The HTA I used I "took" from this site: https://t3chn1ck.wordpress.com/tag/hta/

Forgot to add that I have added HTA support to my WinPE (version 10).