Hello,
How can I fix an issue with an updating causing the filteradministratontoken in the registry to change from a 0 to a 1 value. It should remain a 0 until the end of the imaging. Since it changes to a 1 due to an update the TS does not resume and I have to manually go into the registry and change the value back to 0 for the TS to resume. This change happens during my windows update (post application install) task.
Hello
Im using MDT 2013 and have been happily deploy windows 10 machines using a standard task sequence.
However we have just been sent in a new Dell XPS 13 (we have used these before and have imaged fine) and each time i image the machine i restart and get the INACCESSIBLE BOOT DEVICE.
I can re-install using a windows 10 usb key fine, but each windows 10 image i select in the MDT task sequence produces this error.
I thought it may have been driver error so i have tried also to disable the part where it installs the device drivers.
Any ideas?
Thanks
I have a Fujitsu P728 laptop that I created a image for a few month ago (Win10-1709).
This unit/Image does not have encryption enabled on it at all.
Recently I got a the same model Fujitsu P728, and noticed out-of-the box, the drive has encryption enabled and is on Win10-1803.
I checked and Bitlocker is waiting for activation on the unit.
manager-bde -status shows 100% encrypted.
For testing..
I tried to move this HDD into another shell (Same "newer" P728 model), but it would not boot to Windows. I got a Bitlocker error
I have a few question hopefully I can get answers on...
1) is this normal to get a Bitlocker error when moving a encrypted drive that does not have Bitlocker truly enabled with a PIN to another shell?
1b) Can I bypass this by Clearing the TPM in the BIOS?
Now the tricky ones..
I was able to take my master image that I created with the "Older" P728 that never had any encryption going on, and deploy this to the newer P728's. They immediately start encrypting on first boot (Nothing in my unattend.xml has encryption settings).
2) What is enabling this encryption when the "Image" and "Master Machine" never had encryption enabled?
3) I was able to swap the drives between machines once they had my "Master Image" on them.
So this appears as though encryption really is not working at this point?
Is this a TPM setting within windows which is allowing the drives to be swapped? Possibly a conflict with TPM and Bitlocker provisioning?
Any help would be appreciated! Thanks
Hi guys,
Issue that I do not understand.
On my test MDT server, when I install W10 to computer, I can select 4 languages during the WinPe Wizard, during the "locale and time" wizard. It is possible, and after OS deployment, my language selected is applied to computer.
On the production server, I wanted to make same steps, but the UI Language settings is blank or forced to english only.
Why?
The OS Wim file I install on computer ever had the 4 languages I need, but the only difference between prod & test server is that the production server has no packages added in the MDT deployment share/packages folder instead of my test server where
I previously added LP for W10 1709 and 1607.
Do you think that explained my issue?
Also Wierd thing is on the test server, when I generate boot wim, I've got error about LP injection, so I mean these old LPs are not published in the boot wim, that's why on production server I never added them.
I need to install computer in different languages, so I found that selecting the LP with the "Locale and time" wizard was a better Idea than create an TS for each OS deployment...
Thank you
Hi All,
I created the new TS. modified the TS by going to OSinfo tab - edit Unattend.xml file.
I just added OOBE and changed the below settings.
HideEULAPage- false
HideOnlineAccountScreens - false. I need work or school account screen (if net connected) or local user account screen should be display.
I did not removed anything. Autologon etc., keep it the same.
when I deploy the image. it is prompting for me accept the EULA screen and after that directly logging into local admin account.
it is not prompting for me enter my username and password box.
if I remove Autologon from unattend - TS not completing and it is creating MININT fodders in C:\drive.
I want OOBE enable in my image machine where user has to enter his work or school account or create his local admin account.
local admin account should be disable. and login with user entered login details.
but now, my image machine directly logging into local admin account after EULA screen. it is not applying HideOnlineAccountScreens.
Please help me on this. Thank you.
Bonjour,
La migration vers windows 10 n'étant prévu que pour l'année prochaine apres test de compatibilité
de nos logiciels métiers, je suis encore obligé de déployer Windows 7. Or sur les nouveaux pc équipés de processeurs intel de 7ieme et 8ieme génération, le déploiement échoue. Ce qui n'était pas le cas avec les anciens processeurs. Même une installation classique (installation sur clé usb) échoue, car le clavier et souris usb ne sont pas gérés.
Quelles sont les solutions que vous voyez, car je suis en panne d'inspiration. j'ai tenté l'injection des drivers dans l'image, aussi bien sur MDT que sur l'installation par clé usb. Mais rien n'y fait.
Une installation de Windows 10 par clé, fonctionne .
Merci de vos réponses.
A+ JJ
Hello all!
I really need your help as this is making me going crazy...
So i have installed MDT latest version with AIK latest version all to deploy windows 10 1709 kms iso.
I setup MDT with sql database as i have multiple locations to manage; the setup went fine without problems or errors. So now i have put only windows 10 OS, created the pxe boot drivers disk from Dell pxe v10 download, created roles, locations, models, task sequences and uploaded the needed drivers.
On the SQL server the database is up and running and all tables/views seem to be there.
Now when a new pc boots it fires up the pxe boot and the task sequence and all seems ok until the step where the custom settings are loaded and the different SQL sections are loaded.... it all goes fine until loading the LPACKAGES section. Until here it goes fast for each section but from here it is slow and generates errors on the logs.
I cant understand why this happens.... please HELP!
Hi my friends, I'm experiencing a little issue.
I want to deploy custom images with OOBE. In other terms, when a client boot his computer for the first time, I want Welcome window display, and ask for account name, etc.
But now, when I boot client computer, it auto-signs in to an administrator session and finish MDT deployment. Please help me understand.
Let's me explain how i proceed. First, I installed with an iso file my Windows, and when I get welcome windows, I enter in audit mode to add some programs etc. Then I launched my \\ServerMDT\DeploymentShare$\Scripts\LiteTouch.vbs to start Sysprep.
It reboots, and I am able to boot PXE and start capturing. Works like a charm. Now I upload my captured image in another DeploymentShare using a Standard Client Task Sequence to deploy my captured image. I updated my new DeploymentShare, etc.
The deployment looks to work great. But when it reboots, it signs in without asking for password or else, and finalize deployment. My programs are here, it is OK. But I haven't my OOBE.
What I misunderstood ? Help me guys...
My configuration: Stand alone laptop. No WSUS server. No network connections. No System Center Configuration Manager.
Objective: Create offline deployment media that can be used to create a virtual machine that can be used to create a reference machine and capture an image.
Status: I have a deployment share created. I can create the offline deployment media (bootable ISO). I can create the vmware virtual machine. When I get to the Windows Deployment Wizard and select "Capture an image of this reference computer.", I am prompted for User Credentials. I enter my login name and password for my laptop and I get "Invalid credentials. The network name cannot be found.".
What am i missing?
My customsettings.ini
;------------------------------------------------------------------------------------------
;Customsettings.ini - This file has been generated with MDT Profile Generator
;------------------------------------------------------------------------------------------
[Settings]
Priority=DeploymentShareDefault
Properties=MyCustomProperty
[DeploymentShareDefault]
_SMSTSORGNAME=*********************
AdminPassword=***************
;TaskSequenceID=W10_2018_09
TaskSequenceID=Test1
ProductKey=******************
;SkipFinalSummary=NO
;SkipSummary=YES
;FinishAction=LOGOFF
;Hiding the Shell prevents the Windows task bar from being displayed at the bottom of the window while the installation is going on.
;HideShell=YES
;DoCapture=YES
;------------------------------------------------------------------------------------------
;NETWORK SELECTION
;------------------------------------------------------------------------------------------
;OSDAdapterCount=1
;OSDAdapter0EnableDHCP=TRUE
;------------------------------------------------------------------------------------------
;BACKUP SELECTION - CAPTURE AND COMPUTER BACKUP PART
;------------------------------------------------------------------------------------------
:JSP 3-28-19 DeploymentType=NEWCOMPUTER
DeploymentType=REFRESH
:JSP 3-28-2019 DoCapture=NO
DoCapture=YES
ComputerBackupLocation=NONE
;------------------------------------------------------------------------------------------
;BACKUP SELECTION - RESTORE USER DATA PART
;------------------------------------------------------------------------------------------
;------------------------------------------------------------------------------------------
;BACKUP SELECTION - RESTORE USER DATA PART
;------------------------------------------------------------------------------------------
UserDataLocation=NONE
;------------------------------------------------------------------------------------------
;DOMAIN/WORKGROUP SELECTION
;------------------------------------------------------------------------------------------
;JoinWorkGroup=WorkGroup
;------------------------------------------------------------------------------------------
;LOCALE AND TIME SELECTION
;------------------------------------------------------------------------------------------
;LanguagePacks1=
;UILanguage=en-US
;TimeZoneName=Coordinated Universal Time
;KeyboardLocale=00000409
;UserLocale=en-US
;------------------------------------------------------------------------------------------
;APPLICATION SELECTION
;------------------------------------------------------------------------------------------
;No applications selected
;------------------------------------------------------------------------------------------
;WIZARD SELECTION
;------------------------------------------------------------------------------------------
;SkipBDDWelcome=YES
SkipWizard=YES
SkipTaskSequence=YES
SkipProductKey=YES
;SkipComputerBackup=YES
;SkipDomainMembership=YES
;SkipUserData=YES
;SkipAdminPassword=YES
;SkipApplications=YES
;SkipCapture=NO
;SkipBitLocker=YES
;SkipLocaleSelection=YES
;SkipTimeZone=YES
;SkipPackageDisplay=YES
;SkipComputerName=YES
;------------------------------------------------------------------------------------------
;OTHER PART
;------------------------------------------------------------------------------------------
;ApplyGPOPack=NO
[Default]
EventService=******************
Hi everyone,
I was able to capture a custom WIM file from my VMWorkstation. When I try to use the image, I can get to the point when the task sequence attempts to install the WIM then fails with the following error:
I am not sure if the issue is with the wim file or it is a task sequence trouble
SC
I was given a pc today and I dropped an image on it. Everything to me looked fine as the C: was a whopping 984G.
What I later found out was that the pc also has a 512G solid state drive and that is where they want the OS to be (C:).
Every pc that runs through MDT gets one whole drive and the OS resides there, C:. I have no idea how to have MDT drop my image onto the smaller drive and leave the large one as storage (D: maybe?).
I'm thinking it must be in the partition section of MDT, yet then I'd have to have that step apply only to the Precision 7530 model.
How do I go about either configuring the BIOS so that C: and the OS is the 512G drive and the other is a storage drive? Would I also have to hard-code that drive as a letter?
I've never had this situation before and they're in a hurry for it, as usual.
I will add that I'm a logical thinker but I'm no scripter. I still need my one-drive pc's to remain as they are, just for two-drive pc's I need to format and deploy to the SSD and I guess format and letter-assign the larger storage drive as well.
I have a task sequence that queries the computer model and then runs a BIOS update if the model matches.
If the BIOS is already up to date, the BIOS update application doesn't update the BIOS and the deployment continues. Everything is OK, but then we get a yellow summery screen at the end saying the BIOS update task had an error code.
Is there a way to filter the BIOS update task so that it only runs when the model matches AND the BIOS version is below a certain value?
hey everyone i am trying to make a custom windows 10 enterprise installer with added updates and software but when i try to update the image so it can be created i am getting the following error and i am not sure how to fix it
Error detected running command: 'C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\BCDBoot\bcdedit.exe -store "offline installer\Content\Boot\bcd" /create "{896944bd-2396-4eaf-af59-db5647327b16}" -d "Litetouch Boot [MEDIA001] (x64)" -application OSLOADER' Exit code is: 1
Error text is: The boot configuration data store could not be opened. The system cannot find the file specified.
BcdEdit returned an error.Good Morning,
Yesterday I was working in MDT to add a App package. It wasn't working so I deleted it and updated the Deployment Share. When I try to PXE boot now, I am getting this error:
Nothing else changed except for me deleting the app package I was trying to install. Everything was working fine until I updated the deployment share. Any ideas on what went wrong here?
SC
Hi Everyone I am new to MDT/imaging. It has been a struggle learning this.
Can someone explain to me under 'State Capture > Refresh only > Apply Windows PE.
I know what Windows PE.
Why would I use it, as this is in regard to a reference image, I am seeing this in a reference image, that device will not be joined to the domain, have no internet access.
We are using MDT 2013, SCCM 2012 R2, we create the OS.wim and then import into SCCM.
Thanks
Linda
I have been experiencing the behavior described in the following article for quite a long time:
https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-mdt-2013-update-1-and-hideshell/
My machines will image relatively quickly, and MDT monitoring will show the task sequence as "completed". However, the machines will sit at the "It's talking a bit longer than usual....." message for a long time, then the task sequence finished message will appear.
I'm looking to resolve this, and stop the machines from sitting at that message. I found the above article, but I'm hesitant to implement the registry tweaks provided because I'm unsure of what they'll effect. Particularly the DelayedDesktopSwitchTimout set to 0.
Has anyone else experienced this/fixed this?
(I am running MDT 8450 with updated ADK.)
Thank you!
Hi
In my environment we have an MDT server that is rather outdated
The current setup is running MDT 6.38443.1000 with Win10 ADK version 10.1.10586.0 (Win10 v1511 i think but the image we deploy is v1607)
Anyways, I am going through this documentation here:
https://deploymentresearch.com/Research/Post/660/A-Geeks-Guide-for-upgrading-to-MDT-8450
Question is regarding the ADK upgrade. On the website it mentioned that if I am not already running Win 10 ADK v1709 i should just uninstall whatever i have and install it. Should i actually do that or do i have to manually upgrade the ADK by route of 1607> 1703 > 1709
Just asking because i was reading some posts regarding the MDT upgrade and how you shouldn't jump between versions. Was wondering is that is applied to the ADK as well
Thanks for your time
I thought you had to update the deployment share whenever you edited anything in the customsettings.ini or bootstrap.ini.
However, I just tried making changes in those files and the changes worked without updating the share.
So, what else other than changing boot images, requires updating the deployment share?