After finding truly great ways for managing drivers dynamically within MDT, I think I have stumbled upon one of the more efficient ways that offers granularity and simplifies management all at the same time.

In "CustomSettings.ini" use the following value

;Driver Settings (Based on the OSVersion, Image Architecture, Make, and Model of the device)

DriverGroup001=CreateBaseImage\%OSCurrentVersion_MajorMinor%\%ImageProcessor%

DriverGroup001=Deploy\%OSCurrentVersion_MajorMinor%\%ImageProcessor%\%Make%\%Model%

'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
'Get OSCurrentVersion_MajorMinor
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
If Not IsNull(oEnvironment.Item("ImageBuild")) And Not (oEnvironment.Item("ImageBuild") = "") Then
    OSCurrentVersion = oEnvironment.Item("ImageBuild")
Else
    OSCurrentVersion = oEnvironment.Item("OSCurrentVersion")
End If
    
If Not IsNull(OSCurrentVersion) And Not (OSCurrentVersion = "") Then
    OSCurrentVersion = Split(OSCurrentVersion, ".")(0) + "." + Split(OSCurrentVersion, ".")(1)
    oEnvironment.Item("OSCurrentVersion_MajorMinor") = OSCurrentVersion
End If
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''

Place the above block of code into your respective "UserExit" scripts. It will generate a variable that contains the first two parts of the operating system version/kernel (6.1, 10.0, etc)

This is great because the value is set to use the built-in task sequence variable of "ImageBuild" that will contain the version of the windows image you are deploying and should that be blank, it will use the version from the current OS. Also, the built in variable of "ImageProcessor" will always come out as X86 or X64. Now your drivers will pull based on the OS Version, OS Architecture, Make, and Model of the device your are deploying. Provided that your Out-Of-Box Driver folders are created according to this pattern, all you would have to do is maintain the Out-Of-Box Driver folder structure and thus eliminate having to worry about changing driver paths within Task Sequences, etc!

Your resulting path can be found in the logs, but the path will expand to look like the following...

"Deploy\6.1\X86\Hewlett-Packard\HP ProBook 640 G1" when deploying (Windows 7 x86)

"Deploy\6.1\X64\Hewlett-Packard\HP ProBook 640 G1" when deploying (Windows 7 x64)

"Deploy\6.3\X64\Hewlett-Packard\HP ProBook 640 G1" when deploying (Windows 8.1 x64)

"Deploy\10.0\X64\Hewlett-Packard\HP ProBook 640 G1" when deploying (Windows 10 x64)

(That is only if Microsoft does not redesign how those builtin variables are named or formatted!)

Tested and working great using Microsoft Deployment Toolkit 2013 Update 1 and with Windows 10! We also deploy Windows 7 here, it is working there as well!

I hope this helps somebody! Have a blessed day folks!

Hi , I keep having next error but I can't figure out what's wrong ...

=== Making sure the deployment share has the latest x86 tools ===

=== Processing LiteTouchPE (x86) boot image ===

Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
WIM file mounted.
Set Windows PE system root.
Set Windows PE scratch space.

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

Processing 1 of 1 - Adding package WinPE-HTA-Package~31bf3856ad364e35~x86~~10.0.10240.16384
An error occurred - WinPE-HTA-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

Exit code = 5

DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-hta.cab, rc = 5.
Added component winpe-hta

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

Processing 1 of 1 - Adding package WinPE-Scripting-Package~31bf3856ad364e35~x86~~10.0.10240.16384
An error occurred - WinPE-Scripting-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

Exit code = 5

DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-scripting.cab, rc = 5.
Added component winpe-scripting

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

Processing 1 of 1 - Adding package WinPE-WMI-Package~31bf3856ad364e35~x86~~10.0.10240.16384
An error occurred - WinPE-WMI-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

Exit code = 5

DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-wmi.cab, rc = 5.
Added component winpe-wmi

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384

Image Version: 10.0.10240.16384

Processing 1 of 1 - Adding package WinPE-SecureStartup-Package~31bf3856ad364e35~x86~~10.0.10240.16384
An error occurred - WinPE-SecureStartup-Package Error: 0x80070005

Error: 5

Access is denied.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

Exit code = 5

DISM /Add-Package failed for component C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\winpe-securestartup.cab, rc = 5.
Added component winpe-securestartup

I cannot deploy a captured image using wdt deployment share using lti method.

error 5640 says The network path was not found.

The path is real and accessible ----------------  net use K: \'\wds-rpm\reminst\

I have a copy of the log file.

What could be the issue here?????????????????

#server 2012r2 #mdt 2012 #adk 8.0 #win 8.1   

###########################################################################

<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="08:08:34.213+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="instruction.cxx:2957"><![LOG[Expand a string: WinPEandFullOS]LOG]!><time="08:08:34.213+000" date="03-12-2015" component="TSManager" context="" type="0" thread="1588" file="executionenv.cxx:782"><![LOG[Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"]LOG]!><time="08:08:34.213+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="commandline.cpp:805"><![LOG[Process completed with exit code 5640]LOG]!><time="08:09:49.687+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="commandline.cpp:1102"><![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="08:09:49.687+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="instruction.cxx:3010"><![LOG[Failed to run the action: Install Operating System.
Unknown error (Error: 00001608; Source: Unknown)]LOG]!><time="08:09:49.701+000" date="03-12-2015" component="TSManager" context="" type="3" thread="1588" file="instruction.cxx:3101"><![LOG[Sending status message . . .]LOG]!><time="08:09:49.701+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="utility.cxx:292"><![LOG[Executing in non SMS standalone mode. Ignoring send a task execution status message request]LOG]!><time="08:09:49.701+000" date="03-12-2015" component="TSManager" context="" type="1" thread="1588" file="utility.cxx:302"><![LOG[Set a global environment variable _SMSTSLastActionRetCode=5640]LOG]!><time="08:09:49.701+000" date="03-12-2015" component="TSManager" context="" type="0" thread="1588" file="executionenv.cxx:668">

###########################################################################

Hi

My environment is like Windows server 2012 R2, MDT 2010 update1 trying to deploy Windows10. While trying to update the deployment share, it is giving an error like 'Dism host service process has stopped working'. I have spent a lot of time doing trouble shooting but no luck.

Has any one got the same issue and found any solution?

Please let me know if any further details is required.

Regards,

Subhas Roy

Hello Deployment folks,

im currently running into problems which i seemingly cannot resolve on my own anymore. Im recreating our media deployment from MDT 2010 in MDT 2013 from scratch. I've not designed the old (and messy) deployment and started learning about 2,5 months ago.

We are running a complete rework of the wizard written from me which is working just fine. Basically at the end of the wizard (after some required inputs) the computer querys the SQL server for his configuration again and the installation starts. So far so good, but after injecting the drivers to the machine (no matter what i change or which solutions from the internet i try) the deployment fails with the following lines in smsts.log:

Executing command line: cscript.exe "%SCRIPTROOT%\ZTIDrivers.wsf"	TSManager	12.11.2015 18:09:48	1568 (0x0620)
Process completed with exit code 13	TSManager	12.11.2015 18:10:18	1568 (0x0620)
!--------------------------------------------------------------------------------------------!	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Failed to run the action: Inject Drivers.
The data is invalid. (Error: 0000000D; Source: Windows)	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Sending status message . . .	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Set a global environment variable _SMSTSLastActionRetCode=13	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Set a global environment variable _SMSTSLastActionSucceeded=false	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Clear local default environment	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Let the parent group (Preinstall) decides whether to continue execution	TSManager	12.11.2015 18:10:18	1568 (0x0620)
The execution of the group (Preinstall) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Failed to run the last action: Inject Drivers. Execution of task sequence failed.
The data is invalid. (Error: 0000000D; Source: Windows)	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Sending status message . . .	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Executing in non SMS standalone mode. Ignoring send a task execution status message request	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmanager\tsmanager.cpp,767)	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Task Sequence Engine failed! Code: enExecutionFail	TSManager	12.11.2015 18:10:18	1568 (0x0620)
****************************************************************************	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Task sequence execution failed with error code 80004005	TSManager	12.11.2015 18:10:18	1568 (0x0620)
Cleaning Up. Removing Authenticator	TSManager	12.11.2015 18:10:18	1568 (0x0620)

Information:

Even if i tell the Deployment to not inject ANY drivers at all, the deployment will still fail.

I am using the same drivers which worked fine in MDT 2010 with the old media. I am currently not able to change them out.

I am deploying Windows 7 Professional 64 Bit (~4500 PCs)

What i have tried:

Re-adding all drivers to the Deployment Share; regenerate Media.

Comparing OS.xml with the TS.xml GUID.

Installing OS without any driver injections.

Swapped hardware to another test machine.

Some more stuff i can't remember right now.

Im very thankful for any further tips!

Thank you

Hey Guy,

I created MDT offline media to upgrade W7 to W10 on machines that are not on the network and or sccm. The only change I made to the "Standard Client Upgrade Task Sequence" is to install the latest version of McAfee and to reboot after the fact. The current version of McAfee on our systems causes W10 upgrade to fail.

If I launch the litetouch.vbs script from a USB Stick everything seems to work fine. The only issue I had was after the machine was rebooted the TS never resumed. I was able to fix this by adding a shortcut to litetouch.wsf into the startup folder.

The reason for my post: Ideally I want the users to be able to download the offline media locally and run it. The first issue I had was that the litetouch script triggering a UNC deployment method. I modified the script as follows to force it to "Media" method:

       DeployDir = ofso.getparentfoldername(ofso.getparentfoldername(WScript.ScriptFullName))

        bFoundMedia = True
        oEnvironment.Item("DeployRoot") = DeployDir
        oEnvironment.Item("ResourceRoot") = DeployDir
        oEnvironment.Item("DeploymentMethod") = "MEDIA"

This works until the TS reboots. It doesn't resume and it actually deletes the shortcut I made in startup before it reboots. If I run the litetouch manually it gives me the "there's already a TS running message".

Is there a way to get Offline Media to run on the local harddrive?

Thanks for you help!

We have a couple computers -- different brands -- that will boot into Windows but won't complete the State Restore phase: Windows updates, install applications, and custom tasks. Here is a screenshot from the end of the BDD.log:

We use Radia for software distribution.  I need to kick-off a Radia "connect" so it will install software before ending my task sequence.

The way it works, a command line is run to have it call back to the server.  It launches a few different processes, but RADPINIT.exe is the only one that is open for the duration of the package installs, and closes when complete, with a caveat.

This RADPINIT process closes and reopens at the end each package, so my attempts to make MDT wait until RADPINIT closes have not worked.

I got some help from jrv in the Scripting Guy forums, but that forum isn't very kind to scripting novices.  I was essentially kicked out and told to go learn PowerShell better. :)

This is the script he helped me with:

$CMD =  'c:\Program Files (x86)\Novadigm\radntfyc.exe'
$arg1 =  'LOCALHOST'
$arg2 =  'Radskman.exe'
$arg3 =  'cat=prompt,ulogon=n,hreboot=y,context=m,mname=radia,dname=SOFTWARE,ip=radia.domain.com,port=3464,uid=$MACHINE,startdir=SYSTEM,ind=y,cop=y,log=software_connect.log'
$Retries = 5& $CMD $arg1 $arg2 $arg3

Sleep 5
$Retries = 5
while(1){
     if(Get-process Radpinit)
     {sleep 5}
     else{exit}
}

This script has a couple of flaws and if anyone can help me make some modifications I would appreciate it.

What this script does:

1. Starts a While loop.  

2. If Get-Process finds Radpinit it sleeps for 5, then checks again, and again, etc.

3. If it isn't running, it launches my CMD, sleeps 5, then exits.

The first problem is that it launches my CMD AFTER running the while loop (Function before CMD / non-liner script processing).

The 2nd problem is that it doesn't have any method of dealing with the brief period when RADPINIT may be between packages.

What I need it to do:

Essentially, I need to put the While loop, inside a Retry loop of some kind.  But I can't figure it out.  Every example that seems similar doesn't work the way I expect when I try to adapt it to this script.

Run my CMD first, then sleep for 5. (Or just let the proposed retry loop take care of this)

Start the while loop.  If Get-Process finds RADPINIT, sleep 5 and start over.  It it DOESN'T find RADPINIT running,  sleep 5 and try again 3 times.  If found on one of those 3 retries, restart the retry counter.

So, for ex:

1. Script Start

2. Run Radia CMD

3. Sleep 5

4. Start While Loop, Get-Process = RADPINIT running, sleep 5.

5. Restart While Loop, Get-Process = RADPINIT running, sleep 5.

6. Restart While Loop, Get-Process = RADPINIT = NOT running, sleep 5.

7. Retry 1 in While Loop, Get-Process = RADPINIT running, sleep 5.

8. Restart While Loop, Get-Process = RADPINIT = running, sleep 5.

9. Restart While Loop, Get-Process = RADPINIT = NOT running, sleep 5.

10. Retry 1 in While Loop, Get-Process = RADPINIT NOT running, sleep 5.

11. Retry 2 in While Loop, Get-Process = RADPINIT NOT running, sleep 5.

12. Retry 3 in While Loop, Get-Process = RADPINIT NOT running, EXIT.

Any assistance appreciated!

-Matt

There's no place like 127.0.0.1

Trying to boot a new lenovo x1 carbon pc but I get this error:

1. When I read this on google it said I need to update my PE?

2. How can I see what version of PE I have?

3.Will I lose all my drivers if I update my PE?

I updated my MDT to 2013 update 1 and WAIK 10 to be able to deploy windows 10.My workaround for this error is to disable secure boot, and change UEFI mode to Legacy only then I can pxe boot.

4.Do you know any other solution?

My other questions are:

5. Do you know what ROW I can't write in customsettings.ini to create a local account that is not admin and assign it lets say a name and a password? Can the password be random and saved somewhere like ad or a text document? Sometimes people don't have a network when they receive our their new pcs and this could be a solution, to logon to a local account and the remote it.

6. Can I choose to hide a task sequence that will deploy windows 10 but still choose it somehow? I want to test deploy windows 10 without other users being able to choose that task sequence?

7. Is it also possibly to change the pxe language to Swedish keyboard instead of English?

Thank you guys and girl!

Hi everybody,

I'm trying to setup new MDT environment (MDT 2013 Update 1) but I'm having some trouble in the process.

What I did and should be OK :

• Create a new blank server (Windows Server 2012 R2)
• Transfer backups I made from my server where there is MDT 2013 (deployment shares) to my new server where is installed MDT 2013 Update 1
• Edit Boostrap.ini files and other elements of configuration on the new server (such as UNC paths...)
• Create a Lite Touch Windows PE WIM file matching with the deployment share we use to make the deployments
• Deploy the Lite Touch Windows PE WIM file into my WDS server

My problem :

I try to make a deployment with a VM. I'm able to select the boot image I put into WDS but afterwards it's stuck on Windows logo.

Thank you in advance for your help ;)

I have this odd problem that local administrator account in windows 8.1 get disabled after first reboot during deployment.

i never had this problem before until i updates my windows 8 ref. image.

I thought something must have happend to the image that is doing it, but even if I used my previous wim images from backups, I still have the same problem.

I even resotred the whole deployment share to the date prior to the date this issue happend , and still have this problem.

at this point the problem should be related to mdt itself not the image.

mu thoughts is that it could be unattend.xml is not working the way it is supposed to but dont know how to truble shoot that.

any Idea?

thanks

\

Unable to find the SMs task sequence. The deployment will not proceed 

I have verified that there are no MININT folders or _SMSTaskSequence folder on C: drive prior to starting deployment and yet the deployment fails unless I clear out the drive completeley by using clean disk command. The reason it cannot find the Task Sequence is it sets IP to DHCP and does not process "Apply Network Settings". I have modified LiteTouch.wsf as well as added "Apply Network Settings" in Task Sequence just like what Johan's blog suggested (http://deploymentresearch.com/Research/Post/367/Fix-for-MDT-2013-offline-media-deployment-bug-Static-IP-addressing)

Here is the few lines from BDD.Log:

I tried adding diskpart.exe clean disk Task Sequence step in Pre-Install phase but it still doesn't work. I have to boot to Litetouch CD and during WinPE boot process press F8 to go to command prompt and clean the disk and then it deploys successfully with correct Static IP.

Thanks,

Deepak

I have an application that installs by running a silent installer bat file on a remote share.  The installation launches, but MDT moves on to the next thing before the installation completes.

What can be done to ensure that MDT waits for the installation to complete and the installer for the application to close before going to the next step in the task sequence?

I have injected a heap of new patches into 'OS Packages' and want to now run a job on some servers to install these new updates without needing to rebuild the server.

I have a new 'Custom' Task Sequence and added a new 'Install Updates Offline' job and pointed it to the Selection Profile that was updated above.

On the server I want to update I'm running \\MDTServer\Deploy$\Scripts\LiteTouch.wsf, select the new Custom TS to run which completes successfully straight away without actually installing any new updates.

Whats the best way to install the new patches over top of any existing install without doing a complete rebuild?

I'm currently running MDT 2013 Update 1 on a Windows 2012 R2 with WDS. I imported the OS files, drivers for Surface and created Task Sequence. I boot Surface Pro 3 into PXE and select my task and all works fine, it even loads the OS but when it tries to capture the image as the second phase it always fails with "Expected image state is Image_State_Generalize_Reseal_to_OOBE, actual image state is Image_State_Complete, sysprep did not succeed. Failure 6192, Litetouch deployment failed, return code = -2147467259 0x80004005"

I try capturing the image using a Sysprep and capture, connected to Deployment share and ran LiteTouch.vbs and wizard comes up and it starts to run thru the task but it fails in the same error. Driving me nuts and not sure why it's happening. I need to complete this image ASAP and I'm wondering if I'm hitting a MDT 2013 bug.

thanks in advance. 

I'm currently seeing an issue when deploying machines using USB.

Initially the USB drive letter is set to M: in WinPE and the machine builds accordingly. At the first reboot into the O/S however the drive letter for the USB key is set to E: but the deployment is not running because MDT thinks it still should be M:

Property DeployRoot is now = E:\Deploy

Property ResourceRoot is now = E:\Deploy

Property DeploymentMethod is now = MEDIA

DeploymentMethod = MEDIA

DeployRoot = M:\Deploy

Property DeployDive is now = M:

DeployDrive = M:

If I use subst to set E: to M: and run litetouch manually then the build completes.

Any Ideas?

I took a good working image and syspreped it and below you will see the error message I got.  Checking for logs, I only seen one log (smsts.log) and it had one entry that didnt look right:

We do not find an available volume to store the local data path.  I have the task sequence to partician the drives so not sure why it doesnt have an "available volume" for it.

I'm using Microsoft Deployment Toolkit 2013 Update 1 to deploy an offline Windows 7 image. I do not have SCCM to use. I have set up my task sequence and it works just like I need it to, but don't like at which point the applications get installed. Currently now you have to log into the computer with an administrator account in order for the task sequence to install the applications. Is there a way to install applications using the task sequence before a user logs in? I believe in SCCM though you can install applications before the logon screen. It's around the part "Setup is preparing for first use". Is there a way to mimic that?

Thanks.

Hi,

Im using MDT 2013 Update 1.

Offline build with USB.

DeployRoot is not updating when executing Litetouch.wsf after the OS has been applied and setup.

Litetouch.wsf lines 267 - 283 detects the new deploy root (when the Media.tag is found on a drive) but its not updating the variable.

Im using oEnvironment.Item("DeployRoot") but its not changing the variable.

Please help

Andrew

This is related to an unanswered post HERE

How can I get rid of OneDrive in Windows 10 during a deployment of Windows 10 in MDT 2013 U1?

I tried the known script found in different forums.

@echo off
cls

set x86="%SYSTEMROOT%\System32\OneDriveSetup.exe"
set x64="%SYSTEMROOT%\SysWOW64\OneDriveSetup.exe"

echo Closing OneDrive process.
echo.
taskkill /f /im OneDrive.exe > NUL 2>&1
ping 127.0.0.1 -n 5 > NUL 2>&1

echo Uninstalling OneDrive...
echo.
if exist %x64% (
%x64% /uninstall
) else (
%x86% /uninstall
)
ping 127.0.0.1 -n 5 > NUL 2>&1

echo Removing OneDrive leftovers...
echo.
rd "%USERPROFILE%\OneDrive" /Q /S > NUL 2>&1
rd "C:\OneDriveTemp" /Q /S > NUL 2>&1
rd "%LOCALAPPDATA%\Microsoft\OneDrive" /Q /S > NUL 2>&1
rd "%PROGRAMDATA%\Microsoft OneDrive" /Q /S > NUL 2>&1

echo Removing OneDrive from the Explorer Side Panel...
echo.
REG DELETE "HKEY_CLASSES_ROOT\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" /f > NUL 2>&1
REG DELETE "HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{018D5C66-4533-4307-9B53-224DE2ED1FE6}" /f > NUL 2>&1

I tried to use it in the task sequence, running "cmd /c %SCRIPTROOT%\removeonedrive.cmd" after moving script to DeploymentShare\Scripts.

Also tried to use the script as an application. I added a task to the group "PostInstall" to install this single application.

At the end the deployment fails with a warning and OneDrive is still there. I can not see where in the logs is the reason for that. Disable the script or the application to remove OneDrive helps...

Sincerly

Marc