I need to upgrade the Windows 10 ADK on my imaging server from 1703 to 1709. I have read thru a bunch of threads here and realize the boot images must be "regenerated" and "replace the old ones", but I can find no specific instructions how to do this. Can you point me to such a resource that shows examples of how this is done?
I appreciate your input.
Lunchbag Mike
At the moment i make images from a VM and import these department images into MDT2013. When importing in MDT2013 check the move choice and the images are moved to the operating systems folder.
I would like to install MDT2013 on a new server and then put the images on a NAS, so the images will not be in the operating system on the MDT server anymore but seperate from the installation server on a NAS. I make a share on the NAS where MDT can get the images to deploy.
How can i point out to MDT2013 that the images are not in the operating systems folder but on the NAS?
Can this be done in the rules.ini for alle deployment images / tasks? or must this be done in the TS for each deployment..
I am trying to disable the Intel(R) Display Audio device on Dell computers. The script I have that works is:
Get-PnPDevice -FriendlyName 'Intel(R) Display Audio' | Disable-PnPDevice -confirm:$false
This disables the Intel Display device...when I run it manually. Within my TS, I get a successful completion with a yellow warning:
At\\MDTServer\Deploy\Scripts\IntelAudioDisable.ps1:1 char:56
+...ndlyName 'Intel(R) Display Audio' |Disable-PnPDevice -confirm:$false
+ --------------------------------------------
NotSpecified (Win32_PnPEntity...2087&SUBSY...):ROOT\cimn2\Win32_PnPEntity) [Disable-PnPDevice], CimException
If I open PS on the desktop and type in the above command, it runs w/o error and changes the status of the device.
It does, however, also change the status if I run the PS in my Task, but throws the above error as well.
Thanks in advance
Hello,
I have a problem to name laptops automatically. In VMs and with desktop PCs there is no problem. I want to name laptops "NB-SERIALNUMBER", as I said, it is working with VMs and desktops.
I do not understand, why it is not working with laptops. There I get the default "MININT-XXX".
Do you have an idea how I can get this working?
Thank you very much!
This are my rules in the customsettings.ini:
[Settings]
Priority=ByLaptopType, ByVMType, ByDesktopType, Default
Properties=ComputerType, SerialNumber, MyCustomProperty
[ByVMType]
SubSection=VM-%IsVM%
[ByLaptopType]
Sub Section=Laptop-%IsLaptop%
[ByDesktopType]
SubSection=Desktop-%IsDesktop%
[Desktop-True]
OSDComputername=#Left("PC-%SerialNumber%",15)#
[Laptop-True]
OSDComputername=#Left("NB-%SerialNumber%",15)#
[VM-True]
OSDComputername=#Left("VM-%SerialNumber%",15)#
[Default]
OSInstall=Y
SkipCapture=YES
SkipBDDWelcome=YES
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipDomainMembership=YES
JoinWorkgroup=WORKGROUP
SkipComputerName=NO
SkipUserData=YES
UserDataLocation=NONE
SkipLocaleSelection=YES
UserLocale=de-DE
UILanguage=de-DE
KeyboardLocale=0407:00000407
KeyboardLocalePE=0407:00000407
SkipTimeZone=YES
OSDTimeZone=110
TimeZoneName=W. Europe Standard Time
SkipBitLocker=NOHi I've configured my MDT with SQl and in my CS.ini I have
SkipComputerName=NO
OSDComputerName=%MySite%-#right("%SerialNumber%",11)#
As I deploy for the first time I'm able to change the computer name (the name is already there but the option is not greyout)
If I want to redeploy that same computer a week, a month later...In the wizard panel on the computer name box, the name is already written (that's ok) but this time the option is greyout, so unable to change the name.
If I go and delete that reference in the SQL database, and restart the MDT wizard I then able to change the computer name.
Is there a way to let me change the computer name even if it's already in the SQL database?
It was not like that before, and I'm unable to find what I've done wrong?
Thanks
Using MDT release 8450
I have established a custom task sequence variable that is an listitem lets call it "mylist" as in oEnvironment.ListItem("mylist") and it has a couple of values.
When I dump TS vars out of the task sequence, I can see values assigned like
mylist001=value1
mylist002=value2
In a custom VBScript if I do a oEnvironment.Exists("mylist"), it returns false. Should it?
Is there a different oEnvironment.Exists for ListItem?
I want to proceed in my script differently based on whether the "mylist" task sequence variable "mylist" listitem exists
Is it safe to just evaluate mylist001 to see if THAT exists instead? Should oEnvironment.Exists return True if the listitem exists?
Since updating to ADK 1803 I have updated my MDT boot images. Every time I boot a VM or physical machine with the new boot images I get the error "Not enough memory resources are available to process this command". This is only seen if you press F8 to display the command prompt from within WinPE. It's the very next line when it loads the command prompt and it's before the line where you can start issuing commands. If you continue to the Deployment wizard the deployment starts and completes the entire deployment. You probably wouldn't even notice it's there if you never look for it. I almost want to ignore it since it doesn't seem to have any noticeable effect, but it would be nice to know why it's happening.
When I updated my boot images I complete regenerated them without error. I have since done that again which did not help. I'm also seeing this on a different deployment share with different boot images.
Looking at the wpeinit.log post deployment shows no failures. I've looked at the "What's new in ADK 1803" doc and saw no major changes to WinPE or any features. I put these features in my boot images:
DISM Cmdlets
Microsoft Data Access Components (MDAC/ADO) support
.NET Framework
Windows PowerShell
Storage Management Cmdlets
I have a Windows 10 (1709) image setup on a USB from MDT 6.3.8450. Works fantastic on all new and recent machines. However, on SOME older machines, when we boot off the USB, the Windows Deployment Toolkit greyish screen pops up, sits for a few seconds, then reboots. Keeps rebooting over and over.
I did some digging and finally found this old thread - https://social.technet.microsoft.com/Forums/en-US/b8b4fd55-1564-4f5e-9c09-3b97121725df/computer-restart-at-splash-screen-when-deploying-image?forum=mdt
So I did an F8 as soon as I got to that screen and I was able to get to a dos prompt. I checked for logs, but not finding anything. So I ran the litetouch.wsf in debug mode as per the above thread. Last few lines of output below, nothing really meaningful above it.
No task sequence is in progress.
Unable to connect to BCDstore.
Not running within WinPE or WinRE.
......
SMS Task Sequencer already found on X:\Deploy\Tools\X64
Copying D:\Deploy\Control\\TS.XML to X:\Deploy\Tools\X64
And the copy fails because the path is messed up - it's missing the task sequence, which I'm not getting a chance to select. So not sure if my troubleshooting is even any good. Does litetouch.wsf/vbs run AFTER selecting a task sequence (I would
think so.) If so, I'm guessing there's something else going on.
Below is my customsettings. Again, this works fine on all new machines, so. . .?
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
OSInstall=Y
SkipCapture=YES
SkipAdminPassword=YES
SkipProductKey=YES
TimeZoneName=Eastern Standard Time
SkipDomainMembership=YES
SkipTimeZone=YES
SkipBitLocker=YES
SkipUserData=YES
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
SkipSummary=YES
SkipBDDWelcome=YES
SkipComputerBackup=YES
Hello,
now I have another question again.
When I search on the internet there are many articles about the autologon after deployment.
Until now. I was using a script which disabled the built-in administrator and created a new account without a password and without autologon.
But now I want to migrate many computers of an external organization/domain from Windows 7 to 10 with a clean installation, but user data should be migrated too. So USMT is a good way to go, isn't it? All the computers should have an emergency administrator account (local one) with the same password. But when I simply set up the password while/before deployment (customsettings or unattended) the autologon is still a problem, right?
Anyway: of course we are talking about a domain, so it is not necessary to migrate the user profiles itself, only data in the user folders would be good. Is there a better way than I am thinking about?
Sorry for my English, I hope I was able to express my issue sufficiently.
Thank you very much and have a nice day!
Hi All,
I use MDT 8450 and so far I'm happy with it. But there are two things which are a little bit annoying. Makes life harder. :)
I have two issues and hope there is an explanation for it. It is with a Windows 10 tablet with a SSD drive.
1) deploy wim
I use PXE to deploy wim and after the login MDT doesn't continue. I read in the internet, it's an issue with a token. The fix is to set the token from 1 to 0 in this reg key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\FilterAdministratorToken. Reboot and MDT continues. It's the fix in my situation. But I'm wondering why MDT won't continue on its own?
2) capture
When I run a capture task with PXE, i see "Apply WINPE" and then it reboots. However it doesn't boot into WinPE. Windows 10 boots normally. What I have to do is to sysprep again and shutdown. Start PXE and then the MDT capture task continues where it left off and creates the WIM.
Why won't it boot directly without my intervention?
I currently only work with a Windows 10 tablet on a project. I see issue 1 only with the tablet. However issue 2 happens with the tablet an VMs from VMware. Sometimes issue 2 works fine with a VM, but not always.
Thank you!Edy from Switzerland
My Customsettings.ini
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
ScanStateArgs=/v:5 /o /c /uel:120
LoadStateArgs=/v:5 /c /lac
OSInstall=Y
SkipCapture=NO
SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerBackup=NO
SkipBitLocker=NO
EventService=http://wsttdeploy:9800
My USMT parameters
Where *servername* was servername.
scanstate \\*servername*\migdata /i:migapp.xml /i:migdocs.xml /o /v:13 /c /uel:120
Part of log.
where *username* was the username.
2015-05-07 11:07:09, Info [0x0802c6] Processing GATHER for migration unit: <*username*>\MigDocUser (CMXEAgent)I'm trying to set a couple of properties via the ByServerOS/ByDesktop/ByVM variable but if i test the DS and its CS.ini it initially reports my Vmware, Server 2016 OS as a Server OS (even though buildnumber is reported as unknown and set to other.) When setting a subsection for "ByServerOS" with Subsection=Server-%IsServerOS%, it doesnt appear to read in the variables. any suggestions? Also curios where its comparing the IsLaptop/IsDesktop/IsServer/IsVM list as mine all show as false.
In short, i'm tryiing to use different properties if its a 2016 server or Windows 10 workstation, in a Vmware environment.
Any input would be appreciated
Simple example below.
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
Hi,
I want to run a specifik hidden OSD task seq from command prompt or powershell script. Our SCCM is integrated with MDT but I can't figure it out how to start the task seq from a script.
Can someone help me or point me in the right direction?
Thanks in advance!
Regards
Jean-Pierre
So I have the MDT task sequence set to enable Bitlocker and put the recovery key into Active Directory for easy access by the Domain Admins. When I tested it, everything seemed fine. When I went to image a production machine, I found that the
machine kept prompting the user for the recovery key. I then went about trying to add a GPUpdate /force command into the task sequence thinking that it might just be a policy issue. When I went to test this on one of our spare machines, I ended
up getting a failure message at the end stating the task sequence had failed. I have added a link to all of the log files from this attempt in order to allow you all to see what is going on. I am not sure if I should just add in a reboot command
to the system in order for it to make sure it gets all of the right GPO's applied to the system. Any help on this issue would be appreciated.
I downloaded my MSDN iso of v1809 a few hours ago and also noticed the new ADK is available.
Is MDT 8450 able to work with Windows 10 v1809/ADK v1809?
Thanks,
B
Hi,
We use MDT for deployment. We use Roles to determine the majority of settings, including task sequence, with only individual computers having the computer name element filled in.
I was wondering if there's any way to setup make / model with some other requirement. For example, a VM reports this with wmic computer system get
Manufacturer: Microsoft Corporation
Model: Virtual Machine
So if I had a make / model configured for that with a specific role (in this case Servers, which has the task sequence ID), EVERY VM would use that. How can I have a make / model VM for Windows Client and another for Windows Server.
Thanks
Hello,
I got the Windows 10 1809 iso from the volume license center, put it up into MDT. Applied it to the install operating system step of an existing task sequence. When I boot up the WinPE boot image, from the list of task sequences the one with 1809 disappears, hidden from view. I change the install OS step to some lower OS and it reappears in the list to select.
I then saw the new ADK and WinPE addon versions, upgraded to those, recreated the boot images, and same issue. Whenever I create a task sequence pointing to the 1809 source files the task sequence becomes invisible from WinPE. Haven't experienced this issue with any previous Windows 10 versions, wonder what is going on...
Might also be worth pointing out that MDT detects the new 1809 media as 'Unknown' Platform as well, instead of x64. That appears to the be the only thing it failed to grab though.I have a problem when I try to run a wsf that should add the computer description into AD
If I run it as my account (and load the profile) the description is added into the Active Directory perfectly
But if I run it with a different user who have the same rights as me in the AD, I got this error...
What could be the problem?