We are running MDT 2013 update 2 (6.3.833.1000) v6.3.8330.1000), can we simply run the installer and just upgrade to MDT 8450, Windows ADK 10 v1809?
Do I have to uninstall anything?
Thanks
↧
MDT 8450, Windows ADK 10 v1809 upgrade
↧
UEFI No Bootable Devices Found
MDT 6.3.8443 on 2008 R2
trying to deploy image to Dell Latitude 5590
BIOS boot options are "Legacy for External Devices ONLY", or UEFI
Image was created from ISO. Drivers for Latitude 5590 added to Out of Box Drivers
Selection Profile Created for Latitude 5590
Task created in Windows 10 Task Sequence to inject drivers for 5590
When booting device, I press <F12> Note says Legacy boot mode does not support OS boot on internal storage devices such as HDD, SDD, NVMe, or eMMC. It is intended for use with external storage devices only, such as SD Card, USB, and Network PXE.
I select Change Boot Mode Settings and choose Legacy External Device Boot Mode, Secure Boot Off
Intel Boot Manager starts, I press <F12> to PXE boot and get to my Boot WIM options menu. We run both WDS and MDT. I select MDT Server. GUI is displayed. I select my Windows 10 Task Sequence. Task Sequence runs, I can see it go through the tasks, inject the drivers for the 5590 and install the OS but when I reboot I get the "No Bootable Devices Found" error.
I restart and select Change Boot Mode Settings. switch back to UEFI; Secure Boot: ON
Reboot and get same "No Bootable Devices Found"
I checked the Task Sequence and verified that the Format and Partition (UEFI) task is present.
The image works as expected on devices with the BIOS set to Legacy Mode.
Any help is GREATLY appreciated as we're getting a wave of new laptops with this same type of BIOS.
Thanx
SteveInOregon
"Never never doubt what nobody is sure about" -Willy Wonka
↧
↧
Invalid Credentials Connecting to Network Shares
Hi
I have MDT2010 installed and configured (and appropriate shares on server)
I am trying to do a LiteTouch deployment of Windows 7 from within Windows
I can open/access the deployment share from the computer and run the script.
Everything runs fine untill it asks for credentials to connect to network shares.
It keeps giving me "*Invalid Credentials: (800704C3)"
The credentials I am typing in are typed in correct and work outside MDT. I have confirmed the share and NTFS permissions on the Deployment Share folder.
Any Ideas?
↧
Choose on deployment if computer should join domain or workgroup
Hi!
I'm having issues with something I thought should be very smart. The possiblity to choose in the start of a specific deployment if the computer should join our domain or just stay in a workgroup.
If I blank out every domain settings in [W10X64-1803] it will join the workgroup Ive specified, but if not, it will somewhere in postinstall join the domain with name as configured. I want it to stay in the workgroup.
I would also love a tip on how to set specific tasks in the TS for if the computer is in the domain or in the workgroup.
Anyone who has a solution for this?
Under you can see my two CustomSettings.ini files.
CustomSetting:
[Settings]
Priority=DefaultGateway, ByLaptopType, ByDesktopType, Model, SetAlias, Default
Properties=MyCustomProperty, ModelAlias, MakeAlias, MacAlias, SMBIOSBIOSVersion, ComputerLocationName, ComputerTypeName
[DefaultGateway]
10.247.10.1=NORWAY
[NORWAY]
ComputerLocationName=no
[ByLaptopType]
Subsection=Laptop-%IsLaptop%
[Laptop-True]
ComputerTypeName=lt
[ByDesktopType]
Subsection=Desktop-%IsDesktop%
[Desktop-True]
ComputerTypeName=ws
[HP Elite x2 1012 G1 Tablet]
ComputerTypeName=tablet
[Surface Pro 4]
ComputerTypeName=surface
[SetAlias]
UserExit=AliasUserExit.vbs
MakeAlias=#SetMakeAlias()#
ModelAlias=#SetModelAlias()#
SMBIOSBIOSVersion=#SetSMBIOSBIOSVersion()#
MacAlias=#SetMacAlias()#
[MAKE]
DriverSelectionProfile=Nothing
DriverGroup001=%Model%
[Default]
OSDComputername=%ComputerLocationName%-%ComputerTypeName%-
_SMSTSORGNAME=DOMAIN - %TaskSequenceID% on %OSDComputername%
BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1
OSInstall=Y
SkipBDDWelcome=YES
KeyboardLocale=nb-NO
UserLocale=nb-NO
UILanguage=nb-NO
AdminPassword=P@ssw0rd
SkipAppsOnUpgrade=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipBitLocker=YES
SkipSummary=YES
SkipCapture=YES
SkipApplications=YES
DoCapture=NO
ComputerBackupLocation=\\MDTSERVER\MDTProduction$\captures
SkipFinalSummary=YES
TimeZone=110
TimeZoneName=W. Europe Standard Time
WSUSServer=http://MDTSERVER.DOMAIN.com:8530
Home_page=http://www.DOMAIN.no
EventService=http://MDTSERVER:9800
CustomSettingWG.ini:
[Settings]
Priority=DefaultGateway, ByLaptopType, ByDesktopType, TaskSequenceID, Model, Default
Properties=MyCustomProperty, ComputerLocationName, ComputerTypeName
[Default]
SkipDomainMembership=YES
JoinDomain=DOMAIN.com
DomainAdmin=%ComputerLocationName%-MDT_join
DomainAdminPassword=P@ssw0rd
DomainAdminDomain=DOMAIN.com
MachineObjectOU=ou=MDT,ou=%ComputerLocationName%,ou=Corp,dc=DOMAIN,dc=com
[W10X64-1803O]
SkipDomainMembership=YES
JoinDomain=DOMAIN.com
DomainAdmin=%ComputerLocationName%-MDT_join
DomainAdminPassword=P@ssw0rd
DomainAdminDomain=DOMAIN.com
MachineObjectOU=ou=MDT,ou=%ComputerLocationName%,ou=Corp,dc=DOMAIN,dc=com
[W10X64-1803]
SkipDomainMembership=NO
JoinDomain=DOMAIN.com
DomainAdmin=%ComputerLocationName%-MDT_join
DomainAdminPassword=P@ssw0rd
DomainAdminDomain=DOMAIN.com
MachineObjectOU=ou=MDT,ou=%ComputerLocationName%,ou=Corp,dc=DOMAIN,dc=com
JoinWorkGroup=WORKGROUPNAME
Some screendumpts:
↧
MDT Failure: Litetouch deployment failed. Return Code: -2147467259 0x80004005
I was able to image on Friday (9/29/18) without any issues, but when I tried yesterday and today, I get a task sequence error.
I was able to pull a SMSTS log, but not a BBD log.
Server info: Windows Server 2012 R2, MDT 8450. We are deploying Windows 10 Enterprise x64 v1703.
Logs and picture of the error: https://goo.gl/73YWGA
Please help!
↧
↧
MDT 8450, Windows 10 ADK 1809 - unattend_unknown.xml error
When creating a new standard client TS for 1809 in MDT, I get an error message.
Could not find file "C:\Program Files\Microsoft Deployment Toolkit\Templates\unattend_unknown.xml".
Beginning task sequence import
Creating item named test at DS006:\Task Sequences\RTM to Gold.
System.Management.Automation.CmdletInvocationException: Could not find file 'C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_Unknown.xml'. ---> System.IO.FileNotFoundException: Could not find file 'C:\Program Files\Microsoft Deployment Toolkit\Templates\Unattend_Unknown.xml'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
at Microsoft.BDD.PSSnapIn.ImportTaskSequence.CopyAnswerFiles(String destination)
at Microsoft.BDD.PSSnapIn.ImportTaskSequence.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.TaskSequenceProgress.WizardProcessing()
at Microsoft.BDD.Wizards.WizardProgress.InitiateWizardProcessing()
I uninstalled and reinstalled the ADK and updated the deployment share. MDT was not touched as there is no newer version.
Anyone else getting the same error?
↧
Storage Replica Feature missing in MDT Task Sequence "Add Roles and Features"
I'm not able to find Storage replica feature in "Add Roles and Features" task in MDT task sequence for Windows Server 2016.
Is there a way to add it to list?
↧
UEFI PXE-booting not working
Hi fellas,
Background: Legacy PXE booting works fine, but Latitude 7490s and Optiplex 7060s no longer permit legacy PXE, as you may already know. So I configured one of my two image servers as instructedhere.
Subsequently the options configured in my DHCP scope look like so:
And that worked for the Louisiana server. UEFI PXE booting worked more or less sufficiently.
The Texas server however, with identically configured options, fails every time. Legacy works fine, but UEFI straightforwardly refuses to function.
DHCP and WDS are contained on the same server, and the server only gets PXE clients on its own vlan.
This is MDT standalone so I don't have any PXE logs I can consult as with SCCM. Is there anyway to turn logging on for WDS? Any ideas?
Thanks.
↧
Windows 10 v1809 Reference Capture with MDT
Hey guys,
So I downloaded the Windows 10 Enterprise v1809 ISO, updated my ADK to 1809 with the WinPE Add-On, and created a 1809 Reference Capture TS.
My first issue was that I couldn't see any TS with the WIM file associated but I fixed it by modifying the OperatingSystem.xml to reflect the correct Platform (x64). But when I began troubleshooting some errors I noticed a forgot to update the deployment share and generate a new boot ISO to test via a Hyper V instance per the instructions from this post: https://deploymentresearch.com/Research/Post/654/Building-a-Windows-10-v1709-reference-image-using-MDT
So after doing that the ISO won't boot, giving me a 0xc000007b error for the winload.efi file. Anyone know how to resolve this issue?
↧
↧
Add computer to a AD security group during Task Sequence
Hello,
I'm trying to join a pc to an AD security group during a MDT 2012 Task Sequence with a VBS script. I'm running the script during the TS as another user. I'm getting error 0x80004005. I've run the script in Windows as another user the script just works.
I've tried several things, but I can't let it work.
I hope someone can help me
Thank you
Edward de Ruiter
↧
1803 & Activating Bitlocker as local account.
Since going to 1803 we can no longer kick off Bitlocker encryption as the local admin.
(Your ADDS schema isn't configured to run Bitlocker Drive Encryption. Contact your local system admin).
That means a few extra steps and moving a pc within AD twice more during our builds.
I thought I had seen something about modifying the WIM's to get this to work, but until I know exactly
why and all that's involved, I'd rather post here to find solutions.
My AD group has no work-around for this. We 'can' sign on as a user, after moving them to an
elevated OU as well as moving the pc within AD a couple of times....just hoping for a solid fix across
the board. Any input would be helpful.
Thanks
↧
Disable Legal Notice in MDT Windows 10 Deploy?
Is there a way to disable/bypass then re-enable the domain GPO security screen during MDT deployment of Windows 10 so that
the task can continue uninterrupted? I have it working for Windows 7 and it's a great feature.
Thanks!
What I eventually hope to do is have the Administrator boot right to the desktop without stopping
at the security banner or having to enter the password. I've got the p/w in the unattend as usual but
it stops at the notice and makes me click OK then choose Local Account and sign in as Admin.
Not completely efficient.
↧
Installing Drivers Issue with MDT 8450, Windows 10 v1803, and OptiPlex 7060 Intel i7 8th Gen Processor
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!
↧
↧
MDT 2013 - ramdisk error
We are having a recent issue with imaging any HP computer (our Lenovos work without a problem) where as soon as you try to boot the machine from a bootable usb device; we receive a black screen with the following error:
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
Status: 0xc0000017
Info: There isn't enough memory available to create a ramdisk device.
We are using MDT 2013 update 2 and ADK 10.1.14393.0 on a Windows Server 2012 R2.
We've been able to image without any problems until now and nothing has changed recently - other than the occasional windows update.
A few of the HP computers we are trying to image are HP 6200 Pro SFF and HP ProDesk 600 G2 SFF with 4-8 GB of Ram installed.
I have tried repairing MDT/ADK install on the server and completely regenerated the boot images as well.
Any advice or help would be greatly appreciated!
↧
MDT support for Windows Server 2019
Hi,
I use MDT 6.3.8450.1000 the latest version I can find. Just for testing I added Server 2019 1809. I was testing to capture a image. I kicked of an TS after boot, and the OS was istalled but I was ending up MDT "Task Sequence" again inside the MDT.
So I have not find anything about a new MDT for Server 2019 1809 support?
/SaiTech
↧
Prompt for Hostname & Join Domain
Hi Guys,
We have a third party vendor who deploy our OS image (Windows 10) which was created using MDT via offline media. The imaged machines are then shipped to our office. I'm trying to now find a way to achieve the following:
- Log into the imaged machine and be prompted to set the hostname
- Machine joins the domain
So basically, the imaged machine will be sent to our office. At this point we would like to power it on and log into the machine with the local administrator account and complete the remaining tasks. Perhaps I could simply have a Powershell script execute on the first logon?
Any ideas would be appreciated.
↧
Creating a multi-OS USB pendrive in MDT
Hi Community,
For a customer we need to create a rather unique boot device for offline installation and we're having unexplainable errors.
Goal:
To provide bootable USB pendrive with pre-configured Windows 10 x64 uefi and Windows 7 x86 bios operating systems.
Environment:
Server 2016 build: 14393.2368
MDT build: 6.3.8450.1000
W10 X64 build: 16299.192 (1709) UEFI
W7 SP1 x86 BIOS
Situation:
We've set the settings.xml file to split the .wim image files to fit on a fat32 drive, and if we build a USB pendrive for either one OS this goes as designed.
The issue:
If we create the multi-OS USB pendrive, MDT stops at different places;
- Cannot find the x86 image
- File already exist (with no further explanation)
- Cannot find the x64 image
We looked at the working directories for MDT and saw that the %appdata%\temp directory is used sometimes and causes the 'file already exist' error, but we cannot explain why MDT is splitting the wim image in the same directory as the deploymentshare\Operating Systems folder (and sometimes removing the original wim file.
What are we missing or did we stumble across a bug in MDT?
We are in the position to support both solutions (if possible on one device)
Thanks in advance!
↧
↧
Open .dbx files after reformatted computer
I recently reformatted my computer, and saved my Outlook Express Inbox, Sent, and addresses . The only way I could find to save them was in .dbx files, which I cannot seem to find a way to open!! In looking on line, I find programs ...to buy...that will open them, but surely there must be a "better" (cheaper, more accessable) way ? I keep thinking that if that is the common way to save these, I must be missing the common way to open them. Please tell me how to proceed . Thanks very much
↧
Join Domain Issue - Joins domain, but pc goes into loop
Hi Folks,
I have replicated this issue trying to deploy a number of different versions of Windows 10.
I have created, modified and captured my Win 10 image (current 1803).
I create my task sequence to deploy the OS.
I have task sequence and a slightly customised settings.
If I just build it and don't add it to the domain, it builds fine and I can manually add the PC to the domain afterwards.
If I use the customisationsettings.ini and add the "joindomain" details it will build the pc, add the PC to the domain but I do not specify a specific location it will build and drop into the "computers" OU without issue.
If I specify an OU however it builds, it appears on the OU that I want, but the PC spins in to a reboot cycle with no error except for "Why did my PC restart".
I have a number of different OU's including a one with pretty much no GPO applied (my guess its something GPO related) but I cant get it to work.
Any suggestions or has anyone seen similar?
Thanks.
↧
DFS Replication cause MDT to go in read only mode
Hi all
I would like to ask others if they are using DFS Replication of their deployment share to move to several sites, and if you find your deployment share wont update because something sets it to read-only mode?
what exactly set this to read-only? What are you doing to get around the problem?
Regards
ronnie.jorgensen systems engineer
My blog
↧