Hi,

Was trying to open the mdt share folder  from a  backup (manual copy backup) . 

How to apply  all the shared and security  permission in this case 

Thanks 

Hi,

Is there a way to update bios using mdt ?

Thanks 

Hi All,

I'm trying to deploy the AutoDesk DWG TrueView 2018 software via MDT as part of a task sequence. The instructions from AutoDesk's website state that the following command needs to be run to perform a silent install -Setup.exe /qb /i /language en-us.

The issue I'm having is that the software successfully installs. However, MDT doesn't recognize this and just displays a message advising that the software is being installed.

I've checked the log files and I can see that the heartbeat is command has been continually running since the initial installation was commenced (see below for an example).

<![LOG[        Run Command: \server\DeploymentShare$\Tools\X64\bddrun.exe Setup.exe /qb /i /language en-us]LOG]!><time="15:52:44.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI installing application ]LOG]!><time="15:52:44.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41031 sent: ZTI installing application ]LOG]!><time="15:52:45.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[About to run command: \\server\DeploymentShare$\Tools\X64\bddrun.exe Setup.exe /qb /i /language en-us]LOG]!><time="15:52:45.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Command has been started (process ID 7444)]LOG]!><time="15:52:45.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI Heartbeat: command has been running for 0 minutes (process ID 7444)]LOG]!><time="15:52:46.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 0 minutes (process ID 7444)]LOG]!><time="15:52:46.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI Heartbeat: command has been running for 5 minutes (process ID 7444)]LOG]!><time="15:57:00.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 5 minutes (process ID 7444)]LOG]!><time="15:57:00.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[ZTI Heartbeat: command has been running for 10 minutes (process ID 7444)]LOG]!><time="16:02:00.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">
<![LOG[Event 41003 sent: ZTI Heartbeat: command has been running for 10 minutes (process ID 7444)]LOG]!><time="16:02:00.000+000" date="08-09-2018" component="ZTIApplications" context="" type="1" thread="" file="ZTIApplications">

What I've found when reviewing the log file for the installation of the software is that it installs the 2008 SP1 C++ redistributables along with a specific version of DirectX prior to installation the actual software. I've tried installing these prerequisites manually but I encounter the same issue in MDT.

Any help would be appreciated.

Hi,

Hoping someone can help out...

We’re using Microsoft Deployment Toolkit 2013 Update 1 ((Version: 6.3.8298.1000) to install Windows 10 Pro 1803

I’m trying to deploy to a Dell Precision 5520 (with latest BIOS update). I don’t have another model to test with at the moment.

If I write the LiteTouchPE_x64.iso to USB disk (MBR) and set the laptop to Legacy BIOS mode then the deployment works fine. Windows 10 is installed,  all drivers are injected and installed. The Operating System deploys successfully.

If I write the same file to usb disk (GPT) and set the Dell machine back to UEFI (with secure boot on or off) then the following happens:

- The MDT menu/splash screen which presents the list of Task Sequences is almost unreadable. It appears in a small box and even when expanded it still doesn't display properly. I can just about read/select the required Task Sequence and click continue at this point. The deployment continues and completes as expected after that.

We want to be able to deploy in GPT/UEFI mode, with secure boot enabled, as we need to use TPM/Bitlocker...so continuing with just Legacy BIOS mode isn’t an option.

Does anyone know how to fix this display issue? Is this maybe fixed in a later version of MDT?

If I need to provide any more info then please let me know.

Thanks!

This is done through a virtual machine and from the threads that i have read; I will need to check on  Setupact.log to see why it failed.

Unfortunately when i click OK on this, the following error occurs and loops back to the top

Is there a way for me to go into the virtual harddisk and pull out the log to check ? The sysprep which i am using is a Dell Sysprep and not the sysprep available in system32.

Hi fellas,

I was using Lee Stevens' blog, found here, to harness a particular capability of the UDI that MDT doesn't have natively:  to produce a dropdown menu of available domains, along with a list of OUs that change depending on which domain is selected.

I found that, while the computer does name itself correctly, the domain cannot be joined successfully, and on further investigation discovered the reason to be that the credentials specified in the Domain Join Credentials portion of the UDI were not being passed into the domain join attempt, as the screenshot of netsetup.log shows below:

Subsequent attempts to join to the domain manually work fine, and show the account used in netsetup.log.

Troubleshooting further, I added the domain credentials and password directly into customsettings.ini, and the machine successfully joined to the domain after the next reimage.  I had hoped to avoid that in production, preferring the way it works natively (authentication credentials are passed to the domain-join credentials in MDT's ComputerName page).  I didn't want to add credentials in cleartext anywhere in MDT if I could avoid it.

Troubleshooting yet further, I removed the credentials from customsettings and tried pre-filling them in the UDI wizard designer.

On the next attempt, I manually entered my password in the wizard, and the machine failed to join the domain.  Itdid, however, try to use the username specified during the domain join - it looks like it just left out the password when it tried.

I realize UDI is designed to work in conjunction with SCCM and so I'm going off in the weeds here, but I was wondering if anyone else might've tried this.  The holy grail would be to automatically use authentication credentials for the domain join as specified in the UDI.  Thanks.

Hi fellas,

I was using Lee Stevens' blog, found here, to harness a particular capability of the UDI that MDT doesn't have natively:  to produce a dropdown menu of available domains, along with a list of OUs that change depending on which domain is selected.

I found that, while the computer does name itself correctly, the domain cannot be joined successfully, and on further investigation discovered the reason to be that the credentials specified in the Domain Join Credentials portion of the UDI were not being passed into the domain join attempt, as the screenshot of netsetup.log shows below:

Subsequent attempts to join to the domain manually work fine, and show the account used in netsetup.log.

Troubleshooting further, I added the domain credentials and password directly into customsettings.ini, and the machine successfully joined to the domain after the next reimage.  I had hoped to avoid that in production, preferring the way it works natively (authentication credentials are passed to the domain-join credentials in MDT's ComputerName page).  I didn't want to add credentials in cleartext anywhere in MDT if I could avoid it.

Troubleshooting yet further, I removed the credentials from customsettings and tried pre-filling them in the UDI wizard designer.

On the next attempt, I manually entered my password in the wizard, and the machine failed to join the domain.  Itdid, however, try to use the username specified during the domain join - it looks like it just left out the password when it tried.

I realize UDI is designed to work in conjunction with SCCM and so I'm going off in the weeds here, but I was wondering if anyone else might've tried this.  The holy grail would be to automatically use authentication credentials for the domain join as specified in the UDI.  Thanks.

I found lots of old suggestions on getting Firefox to backup but the part that bugged me the most was that it went against Microsoft's suggestion of not modifying the original xml files. For good reason too, because they could be replaced and you would lose your customizations. I also found that the suggestions didn't work because of changes in the newer versions of Firefox. Below I will post the code that works with new versions of Firefox, hopefully it will help others.

Now if anyone knows how to get Chrome to work, I'd appreciate that. I'm working on it, but no need to reinvent the wheel if someone has working code already.

This is just the firefox section, it will not work if you only save this code without the required xml and migration tags.

Note: As best as I could tell the lastest version of Firefox writes to HKLM\Software\Mozilla\Mozilla Firefox\*.*\Main and not to bin where the previous code was looking.

<!-- Mozilla Firefox --><component context="UserAndSystem" type="Application"><displayName>Firefox</displayName><environment name="GlobalEnv"/><environment name="GlobalEnvX64"/><paths><path type="File">%CSIDL_APPDATA%\Mozilla\Firefox\</path></paths><role role="Settings"><detection><conditions><condition>MigXmlHelper.DoesObjectExist("Registry","%HklmWowSoftware%\Mozilla\Mozilla Firefox *.*\bin [PathToExe]")</condition><condition>MigXmlHelper.DoesObjectExist("Registry","%HklmWowSoftware%\Mozilla\Mozilla Firefox\*.*\Main [PathToExe]")</condition></conditions></detection><rules context="User"><destinationCleanup><objectSet><pattern type="File">%CSIDL_LOCAL_APPDATA%\Mozilla\Firefox\Profiles\*\Cache\* [*]</pattern></objectSet></destinationCleanup><include><objectSet><pattern type="File">%CSIDL_APPDATA%\Mozilla\Firefox\* [*]</pattern><pattern type="File">%CSIDL_LOCAL_APPDATA%\Mozilla\Firefox\Profiles\* [*]</pattern></objectSet></include><exclude><objectSet><pattern type="File">%CSIDL_APPDATA%\Mozilla\Firefox\Crash Reports\* [*]</pattern><pattern type="File">%CSIDL_APPDATA%\Mozilla\Firefox\Profiles\*\ [pluginreg.dat]</pattern><pattern type="File">%CSIDL_LOCAL_APPDATA%\Mozilla\Firefox\Profiles\*\Cache\* [*]</pattern></objectSet></exclude><merge script="MigXmlHelper.SourcePriority()"><objectSet><pattern type="File">%CSIDL_APPDATA%\Mozilla\Firefox\* [*]</pattern><pattern type="File">%CSIDL_LOCAL_APPDATA%\Mozilla\Firefox\Profiles\* [*]</pattern></objectSet></merge></rules></role></component>

If this post is helpful please vote it as Helpful or click Mark for answer.

I have a MDT server that I would like to set to backup user profiles with USMT, I would like to test USMT manually first but I see a lot of folders and I am not sure which ones are relevant: https://i.imgur.com/gm4GJLS.png

Folders

My rule files contain the following:

SLSHARE=\\REMCORPMIG02\Logs$\%ComputerName%

UDShare=\\REMCORPMIG02\MigData$
BackupShare=\\REMCORPMIG02\MigData$

UDDIR=%ComputerName%
BackupDir=%ComputerName%

ScanStateArgs=/ue:*\* /ui:Corp\* /uel:30
USMTMigFiles001=MigApp.xml
USMTMigFiles002=MigUser.xml
USMTMigFiles003=MigDocs.xml

Hello,

I'm looking for some advice in regards to my customers migration from Windows 7 to 10 (new computers, no in-place upgrades), the client uses roaming profiles, I understand that you cannot use USMT with this, the client would like to switch to local profiles once on Windows 10, what would be the best approach for this? I don't think you can use the same roaming profile between operating systems can you? 

From my understanding, the best approach would be:

1. On Windows 7 device - copy user(s) files (desktop, documents, music, pictures etc)
2. Build Windows 10 device via MDT
3. Remove roaming profile from Active Directory users and computers
4. User logs onto Windows 10 with a new local profile
5. Copy user files to Windows 10 device

Is this correct? Can USMT be used in anyway here?

Thanks,

Alex.

Hello All,

   Was wondering if someone has come across the following issue.
I've run out of ideas so hoping a fresh set of eyes or suggestion can shed some light.

After the OS [Windows10Pro_1803] is deployed via MDT the timezone is defaulting to Pacific Time.

Strangely enough if I set the zone to E. Australia Standard Time that seems to work.

I just can't get it to set to AUS Eastern Standard Time which is for [Canberra,Melbourne,Sydney].

The country location is correct as it's set to Australia but I just can't seem to get the TimeZone right ;-(.

I'm defining the TimeZone in the [CustomSettings.ini] as below

SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipDomainMembership=NO
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=NO
SkipBitLocker=YES
SkipSummary=YES 
SkipFinalSummary=NO
UserDataLocation=AUTO
TimeZoneName=AUS Eastern Standard Time  
UILanguage=en-AU
UserLocale=en-AU
KeyboardLocale=en-AU

According to the [DeployWinz_LanguageUI.xml] file the language is valid.

Thanks for taking the time to read my post.

regards,

Darsenator007

Hello,

when using USMT on a replace scenario, is it possible to have some kind of drop down menu to list the profiles to capture via the wizard?

My client has asked if it's possible to capture only specific users per device as they typically use shared computers but now are looking to use dedicated laptops.

Upgrading Windows 7 Enterprise x64 to Windows 10 Enterprise x64. The upgrade task sequence appears to work fine with no errors, but the Post-Processing group does not run. Looking at the smsts.log file, it is because "Registry value HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Windows\Win10UpgradeStatusCode does not exist".

What puts that registry value there, and why would it NOT put it there? The upgrade itself seemed to go well.

My current setup is...

Deploying 1703 (with some Win7E). I have MDT 6.3.8443 and ADK 10.1.15063.0 and I'm looking to move to
Win10 1803. My hope is to make a Task Sequence that I can run my VM's through to upgrade them as is from
1703 to 1803. Which versions of MDT and ADK do I need for a while in order for this to work...and manage to keep
my Win7E Deployments working as well? Also, I'm not entirely sure how to verify the exact version of ADK I have installed.
Thanks!

Hi Guys,

Hope someone might know the fix for this. 

I have a Deployment build that works well. Yet I have a tasked powershell script to copy files from the deployment share to the local host after OS build, that runs just after installing applications. 

The issue I have is that after the OS is installed and the server reboot the powershell script cannot access to Deployment share due to invalid credentials. 

I can create a script that will assign credentials but I would rather use the user credentials so I don't have any plan text passwords. (Event though the account is set to Guest.)

Is there a way to run the powershell script using the deployment credentials. 

Thanks for you time in Advance.

Craig 

Craig

Hello,

I was wondering if there's a way to LiteTouch.vbs via  file, having the credentials and domain pop-up post prior to the device rebooting and going into WinPE when doing a PC refresh. 

I am using this as my batch file: 
start \\MyServer\MyLocation\Deployments\Current\Scripts\litetouch /user:username password

When I run this file (I am RDP'ed to the PC that I run the batch file from) it does start the bootstrap and starts off at where you name the PC, then pick the tasksequence and then it kicks off the initial refresh by rebooting the PC. WinPE then comes up and prompts me for credentials to continue with the image/refresh. Once I input working credentials, the rest of the LiteTouch process continues.

What I would like is that prompt screen to input creds to come up with I am on the device that I ran the batch file from prior to rebooting so I do not have to enter them at the PC.

I have seen this done in the past at my previous employeer but I was not a part of the WDS / MDT (actually they used SCCM) team and never took the time to look at the .bat file they had setup for us to use. Everything that I have  with WDS and MDT at this company in the past year has been self-taught so I do apologize if this is a simple task.  

Hi All,

Ive successfully captured an image and upon testing deployment of it, everything works fine except encrypting the drive with BitLocker. The error message at the end of the deployment in the summary is "Error 6720: Encrypt the drive." I have installed the 1803 ADK and am running MDT 8450.

I read that creating a brand new TS and copying over necessary steps (such as applications, scripts etc) would be beneficial so have done that and it hasnt made a difference.

I never had this issue with deploying our custom 1709 image so can only assume that theres either new variables i need to declare in the CustomSettings or somewhere else, or settings have since been deprecated and are now causing issues???

Current settings ive got in my CustomSettings.ini file relating to bitlocker are as follows:

BDEInstallSuppress=NO
OSDBitLockerCreateRecoveryPassword=AD 
OSDBitLockerMode=TPM 
OSDBitLockerWaitForEncryption=NO

Has anyone seen this yet or can help?

Thanks.

Anyone see an error unmounting an image in DISM while commiting?
All I get is Error: 1920

This has happened a few times this weekend. After this, I cannot delete the test\offline folder due to permissions, but I can write to it (mount) and always have been able to unmount before.

The log states:

[7040] ImageUnmarshallHandle: Reconstituting wim at E:\MDTBuild\Captures\1703 ControlStation1.wim.
[7040] ImageUnmarshallHandle: Reconstituting wim at E:\MDTBuild\Captures\1703 ControlStation1.wim.
[7040] ImageUnmarshallHandle: Reconstituting wim at E:\MDTBuild\Captures\1703 ControlStation1.wim.
[7040] ImageUnmarshallHandle: Reconstituting wim at E:\MDTBuild\Captures\1703 ControlStation1.wim.
[7040] [0x80070780] WIMUnmountImageHandle:(1614): The file cannot be accessed by the system.
[7040] [0x80070780] WIMUnmountImage:(2031): The file cannot be accessed by the system.
2018-08-13 10:44:57, Error                 DISM   DISM WIM Provider: PID=7040 TID=6264 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimimage.cpp:96 - CWimImage::Unmount(hr:0x80070780)
2018-08-13 10:44:57, Error                 DISM   DISM Imaging Provider: PID=7040 TID=6264 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:1083 - CGenericImagingManager::InternalCmdUnmount(hr:0x80070780)
2018-08-13 10:44:57, Error                 DISM   DISM Imaging Provider: PID=7040 TID=6264 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:535 - CGenericImagingManager::ExecuteCmdLine(hr:0x80070780)
2018-08-13 10:44:57, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2018-08-13 10:44:57, Info                  DISM   DISM.EXE:
2018-08-13 10:44:57, Info                  DISM   DISM.EXE:

Update: I ran the get-mountedwiminfo and see the status: Invalid.
So I ran dism /cleanup-wim and then ran the mountedwiminfo again and it is still invalid.
If I knew for sure that the WIM got updated, I'd just move on and try to delete the test\offline folder later.

Hi all, I've been using MDT for 2 years now and have successfully created, built, and deployed hundreds of Windows 7, Windows 8.1, Windows 10 v1511, and Win10v1607 images.  I have recently upgraded my MDT environment to version 8443 as well as Windows ADK for v1703.

Ever since i made these changes/upgrades and built a new Win10v1703 image using VMWare Workstation and modifying the reference image in Audit mode three things are happening during the deployment:

1.) The deployment gets stuck on the "Getting Ready" screen for at least an hour or doesn't even get passed this screen at all.

2.) If it does get past the "Getting Ready" screen, the answer file (unattend.xml) does not apply.

3.) The deployment takes 2.5 hours to complete (double the time) or will then get stuck on the "Just A Moment" screen forever.

Is anyone experiencing this same issue and/or do you know what could be causing this issue?

Thanks,

Steve