Quantcast
Channel: Microsoft Deployment Toolkit forum
Viewing all 11297 articles
Browse latest View live

Capture Failing on Physical Machines - Access Denied - rc = 5 (MDT v8450)

$
0
0

Good-day folks,

I'm having a rather interesting experience with the Microsoft Deployment Toolkit version 6.3.8450.1000.  I'm new to using MDT in general but I believe based on all the online learning I've done to prepare myself, I've done a pretty good job of coming up with a setup that should work.  In fact, I have been successful in capturing a Windows 10 Enterprise (v1803) image from a VMWare Virtual Machine without any issues (twice actually).  Unfortunately, with the same MDT settings, the capture fails on a physical machine (HP Z8 - to be specific).  This is happening with both Secure Boot (UEFI) enabled and Legacy Mode (i.e., Secure Boot disabled).

At first I thought perhaps this may have been a permissions issue on the DeploymentShare.  So I granted "EVERYONE" modify permission from the root of the drive (since the DeploymentShare inherits from the root).  I've also tried using my own account vs using the service account I created specifically for capturing - same results (i.e., capture succeeds for a VM but not for a physical machine).

What I find strange is that, if indeed this is a permissions issue, then why is it that the capture fails to create the image file but then succeeds in copying over the log files?  At this point I'm at my wit's end and I could use some help from anyone willing to help.  I've provided, below, my MDT settings and a snippet of the BDD.log file showing the error message at the end.

Any help, no matter how small, is welcomed and very much appreciated.  Thank you.

This is my Bootstrap.ini:

[Settings]
Priority=Default

[Default]
DeployRoot=\\SCCMSRV\DeploymentShare$

This is my CustomSettings.ini:

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
_SMSTSOrgName=MY COMPANY NAME
OSInstall=NO
SkipCapture=NO
SkipAdminPassword=NO
SkipProductKey=NO
SkipComputerBackup=YES
SkipBitLocker=YES
EventService=http://SCCMSRV:9800
SLShare=\\SCCMSRV\MDTLogs$
SLShareDynamicLogging=\\SCCMSRV\MDTLogs$

This is the error message I've been getting (from BDD.log):

Beginning backup of drive C:
Event 41035 sent: Beginning backup of drive C:
About to run command: "\\SCCMSRV\DeploymentShare$\Servicing\X64\dism.exe" /Capture-Image/CaptureDir:C /ImageFile:"\\SCCMSRV\DeploymentShare$\Captures\CAP0001-Test.wim" /Name:"CAP0001CDrive" /Compress:MAX /ConfigFile:"\\SCCMSRV\DeploymentShare$\Tools\X64\wimscript.ini" /ScratchDir:"C:MININT\Scratch"
Command has been started (process ID 1328)
ZTI Heartbeat: command has been running for 0 minutes (process ID 1328)
Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 1328)
 Console > Deployment Image Servicing and Management tool
 Console > Version 10.0.14393.0
 Console > Error: 5
 Console > Access is denied.
 Console > The DISM log file can be found at X:\windows\Logs\DISM\dism.log
Return code from command = 5
Error creating an image of drive C: rc = 5
Event 41036 sent: Error creating an image of drive C:, rc = 5
ZTIBackup COMPLETED.  Return Value = 5
ZTI ERROR - Non-zero return code by ZTIBackup, rc = 5
Event 41002 sent: ZTI ERROR - Non-zero return code by ZTIBackup, rc = 5
Command completed, return code = -2147467259
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Event 41004 sent: Litetouch deployment failed, Return Code = -2147467259 0x80004005
For more information, consult the task sequencer log ...\SMSTS.LOG.
Property RetVal is now = -2147467259
Validating connection to \\SCCMSRV\MDTLogs$
Mapping server share:\\SCCMSRV\MDTLogs$
Already connected to server SCCMSRV
OriginalPartitionIdentifier is set, find disk: SELECT * FROM Win32_LogicalDisk WHERE Size = '506333229056' and VolumeName = 'Windows' and VolumeSerialNumber = 'B07DB95D'
Search for Drive: OriginalPartitionIdentifier SELECT * FROM Win32_LogicalDisk WHERE Size = '506333229056' and VolumeName = 'Windows' and VolumeSerialNumber = 'B07DB95D'
Found Drive: C:
Property OSDTargetDriveCache is now = C:
Property OSDisk is now = C:
Copying C:\MININT\SMSOSD\OSDLOGS\LitTouch.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\LiteTouch.log
Copying C:\MININT\SMSOSD\OSDLOGS\LTIApply.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\LTIApply.log
Copying C:\MININT\SMSOSD\OSDLOGS\LTISysprep.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\LTISysprep.log
Copying C:\MININT\SMSOSD\OSDLOGS\Wizard.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\Wizard.log
Copying C:\MININT\SMSOSD\OSDLOGS\ZTIBackup.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\ZTIBackup.log
Copying C:\MININT\SMSOSD\OSDLOGS\ZTIConfigure.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\ZTIConfigure.log
Copying C:\MININT\SMSOSD\OSDLOGS\ZTIDrivers.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\ZTIDrivers.log
Copying C:\MININT\SMSOSD\OSDLOGS\ZTIGather.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\ZTIGather.log
Copying C:\MININT\SMSOSD\OSDLOGS\ztiRunCommandHidden.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\ztiRunCommandHidden.log
Copying C:\MININT\SMSOSD\OSDLOGS\ZTISetVariable.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\ZTISetVariable.log
Copying X:\windows\TEMP\SMSTSLog\SMSTS.LOG to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\SMSTS.LOG
Copying X:\windows\Debug\Netsetup.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\
Copying X:\windows\System32\wpeinit.log to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\
Copying log C:\MININT\SMSOSD\OSDLOGS\BDD.log contents to \\SCCMSRV\MDTLogs$\MININT-HLDHE78\BDD.LOG
CleanStartItems Complete
Unregistering TSCore.dll
About to run command: wscript.exe "X:\Deploy\Scripts\LTICleanp.wsf"
Run Command: X:\windows\system32\bcdedit.exe /delete {d22e7e91-9ee7-46eb-89d7-c5859e4302f0} /cleanup
BCD> The operation complete successfully.
BCDEdit returned ErrorLevel = 0
Removing BCDEdit
Removing AutoAdminLogon registry entries
Re-enabling UAC for built-in Administrator account
VSSMaxSize not specified using 5% of volume.
Logs contained 17 errors and 5 warnings.
Removing MDT commands from unattend.xml template.
Removed AutoLogon settings.
Removed FirstLogonCommands settings.
Modified unattend.xml saved to C:\windows\panther\unattend.xml
Checking mapped network drive.
testing drive Z: mapped to \\SCCMSRV\MDTLogs$
testing drive Y: mapped to \\SCCMSRV\DeploymentShare$
Disconnecting drive Y: mapped to \\SCCMSRV\DeploymentShare$
Cleaning up C:\MININT directory.
Cleaning up TOOLS, SCRIPTS, and PACKAGES directories.
Removing C:\MININT folder (final log entry)


Failed to remove apps for the current user: 0x80073cf2

$
0
0

So I installed MDT and ADK, installed a base image of Win10 Pro, installed all the apps I needed, then went to take a capture and sysprep failed. Here's the setuperr log

2017-11-28 14:19:10, Error                 SYSPRP Package Microsoft.BingNews_4.21.2212.0_x64__8wekyb3d8bbwe was installed for a user, but not provisioned for all users. This package will not function properly in the sysprep image.

2017-11-28 14:19:10, Error                 SYSPRP Failed to remove apps for the current user: 0x80073cf2.

2017-11-28 14:19:10, Error                 SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.

2017-11-28 14:19:10, Error      [0x0f0082] SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll; dwRet = 0x3cf2
2017-11-28 14:19:10, Error                 SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2017-11-28 14:19:10, Error                 SYSPRP RunPlatformActions:Failed while validating SysprepSession actions; dwRet = 0x3cf2
2017-11-28 14:19:10, Error      [0x0f0070] SYSPRP RunExternalDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2017-11-28 14:19:10, Error      [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2

It seems to be an issue that has happened before, for a while now. I've read some of the fixes that do not seem to work, without breaking something else, but why should I have to jump through hoops when it was a Microsoft installed problem? This is just really poor customer service. One of your Noobs created a Appx package incorrectly and then you pushed it out to the world. Why don't you fix it Microsoft? BTW, your software scanned my network without my permission, saw my Toshiba printers, then also installed Toshiba updates that are also misconfigured, and install the same way a Bing News.

SLSShareDynamicLogging and SLSShare not working

$
0
0

Hi all,
I have set up a new environment for my MDT and I have added the two string directly on "Rules tab" 

SLSShareDynamicLogging=\\YourOwnComputerName\DeploymentShare$\Logs
SLSShare=\\YourOwnComputerName\DeploymentShare$\Logs

Right now I'm using the latest MDT Version 8450 and Window ADK for window 10 1809 version.
I have share the DeploymentShare$ to everyone and create the Logs Folder on my E:\Drive as I set up my Deployment share on E:\.
I have also off the firewall on both client machine and my MDT server and used a test machine to verify I can access the share folder at 
\\YourOwnComputerName\DeploymentShare$\Logs. 
but I'm unable to generate any log file during deployment. can anyone tell me is the latest version support these 2 strings? 
can you guide me where to check next? or is there any require setting needed?

thanks.

Unable to update deployment share after copying to new server

$
0
0

I copied the deployment share from an old server, installed MDT and ADK, opened the deployment share, edited the customsettings and bootstrap files with the new server information and then tried to update the deployment share.

The update fails with an error stating it can't find the specified WIM file at the specified path.  The message doesn't include what file name and path it's looking for.

How can I fix this?

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

=== Processing LiteTouchPE (x64) boot image ===

Building requested boot image profile.

System.Management.Automation.CmdletInvocationException: Unable to open the specified WIM file. ---> System.Exception: Unable to open the specified WIM file. ---> System.ComponentModel.Win32Exception: The system cannot find the path specified
   --- End of inner exception stack trace ---
   at Microsoft.BDD.Core.BDDWimFile..ctor(String wimPath, Boolean forUpdate)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.UpdateBootImage(String template, String platform, String dpPath, Boolean createISO, String isoName)
   at Microsoft.BDD.PSSnapIn.UpdateDeploymentPoint.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
   --- End of inner exception stack trace ---
   at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
   at Microsoft.BDD.Wizards.UpdateProgress.WizardProcessing()
   at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()

Windows 10 deployment fails randomly on one type of PC/hardware - installation can not continue

$
0
0

I am deploying Windows 10 1803 based image which contains some additional SW. We have several types of computers - mostly Dell, some Panasonic laptops and some HP workstations (HP 7300MT). On these HP machines the deploy fails randomly with message "The Computer Restarted unexpectedly or encountered an unexpected error.  Windows installation cannot proceed.  To install Windows, click OK to restart the computer and then restart the installation". The second or third installation on the same PC usually works. I do not know why this is happening just on these HP machines.

There is not drivers injections during the MDT setup. Previouly Windows 10 version 1709 worked well on these machines.

Where can I find the reason of the failure?

Latest lines from Panther\setupact.log:

018-09-02 18:49:04, Info                  SYSPRP SPPNP: Status: Starting...
2018-09-02 18:49:04, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
2018-09-02 18:49:04, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
2018-09-02 18:49:05, Info                  SYSPRP SPPNP: Status: Starting...
2018-09-02 18:49:05, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
2018-09-02 18:49:05, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
2018-09-02 18:49:06, Info                  SYSPRP SPPNP: Status: Starting...
2018-09-02 18:49:06, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
2018-09-02 18:49:06, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
2018-09-02 18:49:07, Info                  SYSPRP SPPNP: Status: Starting...
2018-09-02 18:49:07, Info                  SYSPRP SPPNP: Status: Total = 0, Complete = 0, Progress = 0% (0%)
2018-09-02 18:49:07, Info                  SYSPRP SPPNP: Status worker: Waiting for device installation to start...
2018-09-02 18:49:07, Info                  SYSPRP SPPNP: System services have been started.
2018-09-02 18:49:07, Info                  SYSPRP SPPNP: Waiting for pending device installs.

Monitor

$
0
0
Monitoring has been working fine.  Suddenly it does not update in the workbench.  Http access test show its working and the  sdf file is growing and date stamp is changing.  I see 5 machines in the monitor q.  4 complete and one failed.  If I right click and hit delete on anything in the q it does not delete.  No new builds are adding to the monitor q but build fine - how can I purge the sdf or reinstall the monitoring.  Has anyone seen this before?  Thanks

Running Powershell Task Sequence in MDT 2013 getting below error

$
0
0

I am getting this error when I try to run the Task sequence to Enable SNMP on Windows 10 LSTB Enterprise Image.   I did put the script in Deployment Script folder with the name ZTISNMP.ps1.  I don't know where am I missing ?  any help be appreciated.

Thank You

Nilay


mdt 2012 reboots while installing office 2019

$
0
0

mdt reboots while offce 2019 c2r  task is running it advances to the next step in task sequence and office isn't installed.

if I install 2016 msi it doenst happen why?


Unable to Deloy Window 7 (32bits)

$
0
0
I'm using sing MDT 2013 6.3.8443.1000 with Windows Kits ADK v.1803, I am able capture and deploy successful from both Window 7 (64bits) and Window 10 (64bits) on the model Lenovo T470 (20JM). For Window 7 (32Bits) I am able to capture through MDT but I encounter a problem when I try to deploy Window 7 (32Bits) through WinPE. on the installation it will stuck on Running action: Format and partition Disk (BIOS)/ Preparing partition 2... for around few minutes and it will go this this error page showing FAILURE (7706): ERROR! Drive C: was not Found! Lite touch deployment failed, Return Error Code = 2147467259 0x80004005. I had Download Win PE3.1 through Lenovo and have the Driver injected on Windows PE as well as the 2 hotfix KB2990941 and KB3087873 patched.
I didn't know what I am doing wrong. I have even download the NVME SSD driver and manually install into the window 7 images before capture.
Anyone got any solution or what am I doing wrong.

SCCM 1810 / W10 ADK 1809 > What version of MDT

$
0
0

Where can I find what versions of MDT are supported by SCCM as well as W10 ADK?

I currently have MDT 2012(6.1.2373.0) installed and will be upgrading to SCCM 1810 / W10ADK 1809 and am wondering if MDT needs to be upgraded as well and if so to what version?

Please advise........

Jason


Jason

MDT - Windows 10 imaging and initial default browsers

$
0
0

Hello!

I have been creating images for several years now and still have not found a suitable solution to changing the default browser for all new users from Edge to Internet Explorer.  Up until Windows 10 1803 this hasn't seemed to cause a pressing need to get this changed.  From what I have noticed, the Edge browser starting with 1803 causes issues with our state testing app.  There are several background services that start up and prevent the testing app to run.

I have tried to accomplish this 3 different ways.  I have applied a group policy that uses the xml file I exported from a computer I set all the defaults on.  I have used the same xml file and applied it in an MDT task sequence using the ZTIDefaultAssociations.wsf that copies the OEMDefaultAssociations.xml file to the system32 folder as well as writes the path in registry.  Both of these options have successfully changed the default browser to IE, but if you change the default to something else it is reverted back to IE every time you restart. 

I have also tried using dism to load these defaults.

I need to get the default changed from Edge to Internet Explorer for every new user that logs into the computer, but allows the user to pick their own browser and have it stick.

MDT 2013 update 2 error: Litetouch deployment failed, Return Code = -2147467259 0x80004005

$
0
0

Upgraded my Test system from MDT 2013 update 1 to update 2.  Also updated to the newest ADK. Updated deployment shares and recreated boot disks. When I try an deploy windows 7 X64 task sequence (using LiteTouchPE_x86.iso) i'm getting this error:

BDD.log:

Event 41003 sent: ZTI Heartbeat: command has been running for 1 minutes (process ID 880)    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
  Console > Error: 0x800f080d    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
  Console > DISM failed. No operation was performed.     LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
  Console > For more information, review the log file.    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
  Console > The DISM log file can be found at X:\windows\Logs\DISM\dism.log    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
Return code from command = -2146498547    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
FAILURE ( 5627 ): -2146498547  0x800F080D: Run DISM.exe    LTIApply    1/6/2016 12:27:06 PM    0 (0x0000)
Event 41002 sent: FAILURE ( 5627 ): -2146498547  0x800F080D: Run DISM.exe    LTIApply    1/6/2016 12:27:07 PM    0 (0x0000)
Command completed, return code = -2147467259    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)
Litetouch deployment failed, Return Code = -2147467259  0x80004005    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)
Event 41014 sent: Litetouch deployment failed, Return Code = -2147467259  0x80004005    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)
For more information, consult the task sequencer log ...\SMSTS.LOG.    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)
Property RetVal is now = -2147467259    LiteTouch    1/6/2016 12:27:07 PM    0 (0x0000)

STMS.log:

Expand a string: WinPEandFullOS    TSManager    1/6/2016 12:07:36 PM    696 (0x02B8)
Executing command line: cscript.exe "%SCRIPTROOT%\LTIApply.wsf"    TSManager    1/6/2016 12:07:36 PM    696 (0x02B8)
Process completed with exit code 5627    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
!--------------------------------------------------------------------------------------------!    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Could not find CCM install folder. Don't use ccmerrors.dll    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Failed to run the action: Install Operating System.
Unknown error (Error: 000015FB; Source: Unknown)    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Set a global environment variable _SMSTSLastActionRetCode=5627    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Set a global environment variable _SMSTSLastActionSucceeded=false    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Clear local default environment    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Let the parent group (Install) decides whether to continue execution    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
The execution of the group (Install) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Could not find CCM install folder. Don't use ccmerrors.dll    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Failed to run the last action: Install Operating System. Execution of task sequence failed.
Unknown error (Error: 000015FB; Source: Unknown)    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Executing in non SMS standalone mode. Ignoring send a task execution status message request    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Task Sequence Engine failed! Code: enExecutionFail    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
****************************************************************************    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Task sequence execution failed with error code 80004005    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Cleaning Up.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Removing Authenticator    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Cleaning up task sequence folder    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Unable to delete file C:\_SMSTaskSequence\TSEnv.dat (0x80070005). Continuing.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Failed to delete directory 'C:\_SMSTaskSequence'    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
SetNamedSecurityInfo() failed.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
SetObjectOwner() failed. 0x80070005.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
RemoveFile() failed for C:\_SMSTaskSequence\TSEnv.dat. 0x80070005.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
RemoveDirectoryW failed (0x80070091) for C:\_SMSTaskSequence    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Deleting volume ID file C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Deleting volume ID file V:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca ...    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Successfully unregistered Task Sequencing Environment COM Interface.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Executing command line: "X:\Deploy\Tools\X86\TsProgressUI.exe" /Unregister    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
==========[ TsProgressUI started in process 1452 ]==========    TsProgressUI    1/6/2016 12:27:07 PM    1568 (0x0620)
Unregistering COM classes    TsProgressUI    1/6/2016 12:27:07 PM    1568 (0x0620)
Shutdown complete.    TsProgressUI    1/6/2016 12:27:07 PM    1568 (0x0620)
Process completed with exit code 0    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Successfully unregistered TS Progress UI.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
RegQueryValueExW is unsuccessful for Software\Microsoft\SMS\Task Sequence, SMSTSEndProgram    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
GetTsRegValue() is unsuccessful. 0x80070002.    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
End program:     TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Error Task Sequence Manager failed to execute task sequence. Code 0x80004005    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)
Sending error status message    TSManager    1/6/2016 12:27:07 PM    696 (0x02B8)

OS seems to install, but that's it.

Surface Deployment Accelerators

$
0
0

Hi All

I am using the latest version of the Surface Deployment Accelerators (v 2.8.136.0) to rollout Windows 10 Enterprise 1803 July 2018 Edition

I have downloaded the ISO image to use as the source OS files for this edition from the MS Volume Licensing Service Centre and also from our MSDN Subscriptions (Business Editions)

When running the SDA wizard, when it prompts me to select the location of the Windows Source Files, I browse and select the Drive where the ISO image is mounted and select the root of the share but a red cross pops up saying "could not find a compatible ISO file in this location"

I know the ISO file is correctly mounted and is there. It happens with Windows 10 1709 edition ISO file as well

Interestingly, it works just fine with Windows 10 1703 Editions when I mount the ISO file downloaded from the VLSC site

Anyone else had this issue and if so what was your resolution step?

We have for now used the Windows 10 1703 Edition ISO and intend to patch up to 1803 edition manually but that is going to be laborious for 60 to 70 Surface devices

Any pointers are much appreciated

Thanks in advance



CopyProfile

$
0
0

Hello,

please excuse my English.
I know, CopyProfile was discussed so many times. But unfortunately I am not sure about it yet.

I am using MDT (without SCCM) to deploy Windows  (1809). There is no sysprep, just a standard client task sequence. My objective is to change registry keys e. g. for all new users. There are two ways: editing the default user (via loading the hive) or using CopyProfile, right?

When I change keys in HKEY_CURRENT_USER (instead of the default profile) the changes do not appear in any new account, but I set CopyProfile true in the unattended.xml.

The changes are being applied while deployment. In this time I am logged in as Administrator.

I thought especially for things like this CopyProfile is used and thought for, isn't it?

Thank you and have a nice Christmas

Problems creating tasks for software to automatically install

$
0
0

I have created a Litetouch image and deployed it with MDT and the computer gets imaged very easily and with no problems.

But! when I create the software installs within the DeploymentWorkbench, it will not install the software in the Task Sequences.

I am new to using MDT and am trying to get better at using it, any assistance will be greatly appreciated! 

Thanks! 


Super LOOOOOOOOOOOONG load time

$
0
0

Recently I set up the database for MDT on a separate (existing) MS SQL server that I manage.  The data upload was fine, but I am getting two problems since getting the server attached: 1) When deploying, the computers aren't being named from the database; and 2) the scripts that occur between authentication and the menu takes 20ish minutes!  I'm not totally sure where to start troubleshooting the second problem, but I think the first has to do with how the CS.ini file is setup to handle the naming of the computers.

Of course, I could be totally wrong (probably), and it could be the unattend.xml file that needs work.  Either way, any help in resolving these problems would be greatly appreciated.


Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

IE 11 closed by itself every day.

$
0
0

IE closed Unexpectedly every day. tried below:

1. update Java to lastest version

2. Clear IE cache, Reset IE, Uninstall/Reinstall IE

3. update Anti-virus, Run Virus full Scan

4. SFC /Scannow

5. disable crash recovery in IE advanced setting

all above is not working.

could you please advise if other solution can be try.

thanks


Looking for assistance with GPO to prevent peer-to-peer MS Updates.

$
0
0

I know very little about GPO. We have a Server Unit which should maintain this.

During MDT imaging, I can turn off peer-to-peer and also disable driver updates during MS Updates.
We also have an OU which is the ONLY OU to allow MS Updates. All of the others prevent Updates.

However, while in an OU which prevents MS Update, clients still get updates via peer-to-peer. These are computers
that were deployed prior to me fixing this through MDT.

What I'm hoping to find is a GPO template setting to prevent peer-to-peer updates, regardless of the OU.
So far, our Server Unit is preventing updates from MS itself. They are not addressing the peer-to-peer issue.

Unless I tell them specifically where to make a change...and what to change, nothing will get changed.

Has anyone modified the peer-to-peer option to prevent updates from happening from pc to pc?
Thanks!

Service Pack for ProLiant

$
0
0

Has anyone managed to install HP Service Pack for ProLiant with SCCM or MDT any version since 2018.06?

I am using smartupdate /s / softwareonly and getting exit code 1. 

Don't think this install can create log files. Thank you.

Update Deployment Share Options

$
0
0

Hi all,

       So I found a great post here https://social.technet.microsoft.com/Forums/en-US/a4e12993-34ca-485b-af80-d9b25dc5fe23/update-deployment-sharewhen-is-it-necessary-to-do-it?forum=mdt 

talking about when you would/should update a deployment share.  Now I'm curious about the two options? 

       1. Optimize the boot image updating process. 

       2. Completely regenerate boot images.

My question is when/what circumstances would you use each option?

Extra question...  In a deployment share\Applications\Java folder I have an existing MSI I call upon called JREUpdate.msi.   If I overwrite that with a newer version (same name) would I need to update the deployment share?

Thank you.   

Viewing all 11297 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>