Hi All,
I am looking for a way to automate Task Sequence entry by running script so that we don't have to add\remove entries in Task Sequence manually.
Is there anybody who can help me to suggest some blog or solution?
Thanks,
Sourav
Born to Learn
Hi All,
I am looking for a way to automate Task Sequence entry by running script so that we don't have to add\remove entries in Task Sequence manually.
Is there anybody who can help me to suggest some blog or solution?
Thanks,
Sourav
Born to Learn
I'm facing an issue with MDT while trying to deploy a Windows 10 Pro 1709 image to physical machines.
The image capture phase fails because the drive is encrypted (or encrypting).
I'm not interested to encryption and I tried to disable in several way:
- SkipBitLocker=NO
- BDEInstallSuppress=YES
- BDEInstall=NO
- BDEInstall=False
- Disabling task sequence step "Enable BitLocker (Offline)"
- Disabling task sequence step "Enable BitLocker"
and many combinations of these settings.
Despite the settings BDE wizard page is not shown and drive get encrypted.
Any help appreciated.
Hi.
I have current added two Run command line task sequences.
One for Activating Windows 7 online with existing key that was on the reference image:
cscript c:\windows\system32\slmgr.vbs /ato
One for activating MS Office 13:
cscript "C:\Program Files (x86)\Microsoft Office\Office15\ospp.vbs" /act
The Activate Win7 task sequence seems to fail sometimes, and I suspect that its because it moves on to the next task too fast. It works if I enter the command manually afterwards. Is there a better way to do this? Or can I simply ask it to wait 30-60 sec before moving onto the next task?
MDT 8450, ADK 10.1.17134.1
Works fine on the 32-bit image.
These are not being added to the 64-bit boot image, because "the specified package is not applicable to this image."
The x64 boot image is useless to us at present, as you can get into WinPE, but you get this message, then it reboots:
The lack of these components is my best guess for the cause of this, since it's the only clear discrepancy between the two boot images.
You can see the boot image creation log here, just the results of updating the deployment share and completely regenerating the boot images.
The dism log is here.
I thought perhaps just to reinstall the ADK, and I've already run a repair on it to no avail, but this is occurring across more than one of my deployment servers.
I don't have much to say. Below is a collection settings in my environment. MDT Fails to enable BitLocker, but I can enable it manually through the Windows interface after deployment.
Server 2012 R2
MDT Version 8450
Deployed OS
Windows 10 LTSB
MDT Deployment Share [Rules]
SkipBitLocker=YES BDEDriveLetter=S: BDEDriveSize= 2000 BDEInstall=ProtectKeyWithTpm BDEInstallSuppress=NO BDERecoveryKey=TRUE BDERecoveryPassword=TRUE BDERequired=YES OSDBitLockerMode=TPM OSDBitLockerCreateRecoveryPassword=AD OSDBitLockerWaitForEncryption=TRUE
Task Sequence
https://imgur.com/mayBB6V
Group Policy
https://imgur.com/TMit4o8
Error Output
https://imgur.com/4MXn9iS
ZTIBDE.log
https://pastebin.com/21jwsj7w
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.
Like the title says, I am new to MDT. I have created a VERY basic image with MDT just simply to understand the general process. I am now trying to start the process of making a customized image to be used for deployment.
Here is an overview of the situation. We build customs computers to run proprietary software that are then sold to customers. Currently I am making an image for IoT machines that are either using a motherboard with H81A chipset 4th gen processors(i3,i5,i7) or H110A chipset 7th gen (i3,i5,i7).
I am wanting to create a single image that will be used on all variants. The problem I am running into is getting the full set of drivers available for both motherboards. Windows will find the basic drivers it needs and things will get up and running but this is not ideal. I would like to have all the proper drivers added into the final image. I will not be doing an OOBE for these computers. The image will be applied and the computer should boot and be ready to go without the need for any additional installation of drivers or hardware. (Or at least only a very minimal amount)
So the question is, what is the best way of going about accomplishing this? From what I understand of OOB drivers, they only add when the image is applied to the correct hardware, which is not what I am looking for.
I appreciate and welcome all help. Thank you.
Jonathan
Hi,
In my society, i had to start from the beginning Deployment MDT/WDS after the loose of our NAS.
So i create everything like before but i have a problem.
When I boot on PXE, i can do F12 ... but the screen to choose my task sequence never appear.
I tested to launch Litetouch.vbs on another computer and i see my Task Sequences correctly.
Do you have any idea about this ?
Thanks and have a good day
Regards
Hi,
I am preparing multiple keys for offline deployment (for remote sites).
I have a little "inconvenience" after first boot.
To continue the deployment I have to press OK in the window displaying "reinsert the key".
Then it installs couple of apps and i get SUCCESS for the deployment. I remember in the past I didn't have this message.
Also, the key is detected because there is a window for Actions on the key, but probably with the delay.
May be it is pc model related (USB detection stuff).
Any advice... Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
Good morning all,
I have been managing an MDT server for several years now. Within my task sequence, I set the DriverGroup001 variable (to "Windows 10\%Make%\%Model%") so MDT automatically handles driver installs. I use the Set Task Sequence Variable for this. For drivers, I download and import the CAB file from the Dell Enterprise CAB site. I have my Drivers folder organized. Windows 10 is the parent folder. Then, I have folders with the make name. And within those folders, I have the model folders. My task sequence has worked great for several models. I've installed Windows 10 on the OptiPlex 7050, OptiPlex 5250 AIO, Precision 7720, Latitude E6230, and Latitude 3379 to name a few models. Now, we have the OptiPlex 7060 and MDT imports the drivers as expected. However, once the computer restarts and goes into Windows, I get the message, "Cannot connect to deployment share". I turned on the shell for troubleshooting. I look at the Device Manager and see that MDT missed a lot of drivers, the network driver being amongst them. I can manually install the drivers. I can browse the C:\ drive and Windows finds the drivers. So, they are on the computer. After I install the drivers, I can click Retry on the error message that pops up and my deployment completes successfully. My initial thought is that there needs to be some delay because MDT is moving too fast through the process and not allowing the drivers to get installed. I remember reading a post about MDT and faster hardware, but I have not found it again. I do not mind editing the VBS script files and adding a pause. But, I am not quite sure if that would help or where I would add the pause. I also wanted to post and see if anyone else came across similar issues with the newer hardware. I'm scratching my head wondering why everything works on other models, but not our newest one. I appreciate anyone's input. Thank you!
Hello All,
I am trying to deploy the new Windows 10 1803 image, however I am having a little trouble. I have MDT 8450 build (latest) & Windows 1803 ADK. Basically when I go to Deploy, everything seems to get work except domain join. It will finish deployment but not join my to my domain. It also seems to get stuck for awhile on the "Getting Ready" screen a lot longer than 1709 did. 1709 was working perfectly. Any advice or is anybody else having this issue?
Windows Server 2012 R2
MDT 6.3.8450.1000
ADK 10.1.16299.15
Software has been fully removed and reinstalled in correct order.
I am currently having an issue with deploying and image using MDT. I have used MDT previously with no issues however recently we needed to do an image (custom .wim file) for Win 10 ver 1709.
I had some issued with this and it looked like we needed to update MDT to latest version.
Having done this both my older image (in one deployment share) and the new Win 10 image (Test Deployment Share) do not seem to work both as a USB key or as PXE Boot (preferred).
The Issue:
The main issue is that I can pxe boot in to the splash screen and get the Microsoft Deployment Tool kit text in top right. I get a cursor and then after about 1 min the system reboots.
When using F8 I run the command “cscript.exe x:\deploy\scripts\litetouch.wsf /Debug:true /DebugCapture”
The final few lines on this are:
Validating connection to \\servername\TestDeploymentShare$
Mapping server share: \\servername\TestDeploymentShare$
x:\deploy\scripts\litetouch.wsf(2779, 5) (null): The system cannot find the file specified
Previously when the share was working the first thing that would happen would be a prompt to enter credentials to connect to the deployment share.
Your help would be appreciated.
Hi everyone,
I added a pane in MDT to ask the final user to put it as Administrators.
It's working fine, but when I start the LiteTouch for capture, this pane appears too.
Is it possible to remove my pane if I start a capture task?
Regards.
Having some problems trying to deploy Office 365 ProPlus using MDT (8443) on Server 2016. The batch file and config.xml I have setup work ok if I run them on a computer manually, but when I put it into MDT to run, it errors out during deployment. I'm basically having it run the command below.
\\server\deploymentshare$\applications\Microsoft Office\setup.exe /configure \\server\deploymentshare$\applications\Microsoft Office\config.xml
Below is a copy of the config.xml.
<Configuration>MDT 8450 and ADK 1803
I am trying to build Windows 10 Enterprise using latest 1803 media (I see the media has been revised so I am using Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-4_MLF_X21-87129.ISO and i was previously using Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-3_MLF_X21-82160.ISO).
After importing the media I get 10 different editions,.
Whether I choose Pro or Enterprise (not tried the N versions) I always receive Pro.
So in other words, i am not able to build Windows 10 Enterprise.
Has anyone else seen this?
swetha
Hello all,
Problem
I am seeing an strange issue with specific dell E7450 and E7440 model laptops but for some laptop deployment goes smoothly.
Deployment is working perfectly fine with many other dell model desktops,laptops and servers
Brief about the MDT setup
MDT 8450 with ADK Windows 10 1803 and WDS are running in Windows server 2016 server.
latest drivers included in the MDT and boot image
Laptop is installed with latest BIOS (A19)
BIOS load default is done, and SECURE BOOT enabled/disabled both i have tried.
DHCP is configured with policy to differentiate the BIOS/UEFI.
Can someone help me if i am missing something here.
Hi All,
I am running the Powershell script which is the default script of MDT to import Operating System. This script is giving me error. in the following line.
import-mdtoperatingsystem -path $DS_ID":\Operating Systems" -SourcePath $OS_SRC_DIR -DestinationFolder $OS_DS_DIR -Verbose
"import-mdtoperatingsystem : Index (zero based) must be greater than or equal to zero and less than the size of the argument list."
We are setting
Set–ExecutionPolicy Bypass
Any help to solve this issue will be appreciated.
Thanks,
Sourav
Born to Learn
I keep getting the above listed error when trying to update the rules on one of my deployment shares. I've even gone so far as to remove the read-only flag on everything in the share, it doesn't help.
As a workaround, I've been editing the CustomSettings.ini directly, but I'd really like this to work. Any ideas?
As an aside, the 'Alert me when someone responds to this post' never seems to work here. And yes, I've checked my spam folder as well...
Hello,
I am trying to install Server 2012 using MDT.
I have added a package-group with some security-updates (cab-files) for server 2012 and created an "offine installation command" to install these patches.
Configuration like this:
When these updates are added to this package-group, the deployment fails with this error:
When I delete the security-updates (cab-files) from this package-group, the installation will succeed.
How can I fix a solution with the intergration of the security-patches?
Thx
Edit :
When I download all updates separate as .msu, same problem.
What is going wrong when adding the .cab/msu-file (grapped from c:\windows\softwaredistrubition\download)
Another question : with which software-package can I easily download the latest .msu-files from the Microsoft-site to import into MDT ? I found some software , but that is not compatible for downloading server2012-updates.
Thx