I am trying to have Bitlocker encrypt the drive when offline. If I turn on the TPM and the activate it manually, MDT is able to offline encrypt the drive. If I do not do it manually and let CCTK enable bios password, turn on the TPM and activate it, Bitlocker
fails with "Failed to find a TPM instance in the provider class". I know that CCTK is working because if I stop the imaging and check the BIOS all 3 tasks have been completed. Also, Bitlocker will work with the standard method of encryption,
but it just takes too long. Any ideas?
↧
MDT fails with "Failed to find a TPM instance in the provider class" when using CCTK on Dell Laptops
↧
All imported drivers missing from toolkit?
I honestly have no idea what happened. All the drivers are gone in the toolkit, however looking at the DeploymentShare there are 20+gb's of driver files.
I have restarted the server many times, closed and reopened the share, completely re-add the drivers to a couple computer folders. Yet it still doesn't work... I even am checking for updated from microsoft, if it will even help..
I am running blind trying to fix this, as this is our only deployment server.
Any help would be greatly appreciated!
(screenshots coming after my account is verified)
↧
↧
Having issues imaging Dell Latitude E7470 (Windows 7)
Hi Everyone,
So I wanted to start of with the point that my Task Sequence actually finishes and my issues are with the missing drivers.
We got these systems as a somewhat of a surprise instead of our normal E7450 as those got disconnected. This seemed simple enough. I downloaded the CAB drivers from the dells websites and imported it into MDT then copied a task sequence from 7450 and changed the drivers which get injected (I since tried making a task sequence from scratch but result remains the same). The first issue I saw was BSOD telling me that usb drivers are corrupt. For those who see this issue you need to download the drivers from here and replace the cab drivers with them:
8/9 Series: https://communities.intel.com/external-link.jspa?url=https%3A%2F%2Fdownloadcenter.intel.com%2Fdownload%2F22824%2FUSB-3-0-Driver-Intel-USB-3-0-eXtensible-Host-Controller-Driver-for-Intel-8-9-Series-and-C220-C610-Chipset-Family
7 Series: https://communities.intel.com/external-link.jspa?url=https%3A%2F%2Fdownloadcenter.intel.com%2Fdownload%2F21129%2FUSB-3-0-Driver-Intel-USB-3-0-eXtensible-Host-Controller-Driver-for-Intel-7-Series-C216-Chipset-Family
So if this is your issue this should resolve that :)
However, the part that I am stuck on is the video card driver and the BcmNFCBus_257/CVUSBDRVBus_513 drivers. The most frustrating part of this whole thing is that if I download the drivers from the website (\Video_Driver_0RC06_WN32_20.19.15.4390_A01 for video and Security_Driver_3N9T0_WN64_4.2.9.52_A04 for the other two) they seem to install with no issues. However when I extract the drivers using 7-Zip and upload it to the MDT they don't seem to install. I even tried to unzip the cab drivers and import the drivers while excluding the Video drivers and USB then uploading them manually with no luck.
I guess I should also mention that when I make any type of change and re-generate my deployment share, Update the lite touch in WDS Image and restart the server as that seems to be something that's easy to miss.
Has anyone seen this issue yet or perhaps can point me to the cab drivers you used that actually work as even when i was unzipping the cab x86 drivers folder had all files corrupt in it according to 7zip (but since I excluded those folders from the import that does not affect me).
↧
Multiple entries of "Windows Boot manager" in UEFI on Surface Pro 3
Hi
We are deploying a custom captured image on Surface Pro 3 using a using MDT 2013.
Every time i deploy a image there is a new "Windows Boot Manager" entry created and same is visible when you try to boot from a device.
The below post talks about the same issue but option given is to use bcdedit
http://www.windows-noob.com/forums/index.php?/topic/7817-multiple-windows-boot-manager-entries-under-uefi-section/
The below post says that Dell would be fixing it in future BIOS releases.
http://social.technet.microsoft.com/Forums/en-US/192596f1-1c68-4c4b-8b0f-21b279a79403/eufi-options-multiple-windows-boot-manager-entries?forum=mdt
Is it a bug with the surface pro 3 UEFI or am i doing something wrong?
We are using the same image to deploy ON Lenovo Thinkpad 10 but i dont see this issue.
BCDEdit /deletevalue might be an option but want to know if it is a known bug or something wrong with the way i am doing.
UK
↧
MDT 2013 Update 2 reinstalling systems - problem with Windows Boot Manager
Hi there,
We have a problem with "Windows Boot Manager" on reinstalling systems since MDT 2013 Update 2.
Initially we configured our MDT 2013 (Build 6.2.5019.0) for Light Touch Installation: A supporter simply had to prioritize PxE boot for installation or reinstallation of a System (Deployment Type = NEWCOMPUTER). MDT/EFI mechanisms did the rest since the "Windows Boot Manager" prioritized itself for the restart after image was applied.
But since MDT Update 2 the installed system runs PxE Boot a 2nd time at this point when there was a previous installation on the system. Therefore the installation stops with the message "Dirty environment. (...) would you like to start a new one[installation]?" When ignoring with "No" the task sequence continues, the system restarts and boots finally with "Windows Boot Manager" as it should. Same, when simply turn it off and on again. There are no other error messages and the installation completes successfully.
I already scanned logs and scripts, compared old and new ones and tried several Workarounds. Some findings:
- There is no "MININT"-Folder on the previous installation or the image which messes with the task sequence.
- Cleaning the disk before PxE boot or deleting the "Windows Boot Manager" entry in BIOS both prevent the problem, but this is not good enough.
- Compared logs showed that the Parameter "bCreateBootPartition" in ZTIDiskpart.wsf always was TRUE before Update 2. Since Update 2 it now is FALSE most of the time. I found no way to force bCreateBootPartition to TRUE only to FALSE with "DoNotCreateExtraPartition=YES" in CustomSetting.ini which does not help my cause.
At this point I am totally clueless what causes this need for a second restart since Update 2, and how to recreate the previous behavior. Perhaps someone experienced similar problems?
↧
↧
"cosmetical" error from old MDT
Hi,
eventually, I connected to one of computers (it is in autologon mode). After restart Wizard error appeared...
Probably the pc was deployed from MDT2012. MDT2012 server not exist on LAN from year 2012.
How to eliminate this popup? There is no MAP Drive with Red cross on which I can click delete in Explorer...
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis
↧
FAILURE ( 7706 ): ERROR! Drive D: was not found!
I was wondering if anybody run into this issue and could point me in the right direction.
I have been using MDT for over 4 years and last week was the first time that I have ever seen this "FAILURE ( 7706 ): ERROR! Drive D: was not found!" message. I'm running a MDT 2013 deployment server with AIK 8.1 and this error occured while imaging
a Surface Pro 3.
We successfully imaged about +10 Surface's with this MDT build however they all had 128GB SSD's and and 4GB of RAM this one that failed has a 256GB SSD and 8GB of RAM and the issue was replicated on another Surface with the exact same specs.
So far I have;
1) Tried another Surface Pro 3 of the same SKU and it had the exact same issue.
2) Successfully imaged this Surface with Windows 10 and with the Windows 8.1 Pro Surface Pro 3 recover image from Microsoft using USB media.
3) Updated my deployment share to MDT 2013 Update 1 and AIK 10 and tried both the original MDT 2013 standard deployment Task Sequence and the updated MDT 2013 standard deployment Task Sequence both modified for Surface Pro 3 (Driver Firmware, patches etc...)
4) Updated the Surface Pro 3 driver set with the very latest drivers but I noticed that even the latest drivers still uses the Intel ahci 8 driver from 2013 that the worked fine on the other 128GB SSD 4GB RAM Surface Pro 3 SKU's that we imaged before.
When looking at the BDD.log I can see that SSD drive is successfully cleared of any existing partition but it fails to create any partitions and after it fails in WinPE if you manually run Diskpart no drives seems to be available even though driver for the storage controller should still be loaded.
I have done a lot of research and I have found similar issues but none of the solution suggested has solved this issue and I'm running out of things to try.
Here are some of the Logs Files, let me know if any others are required;
https://onedrive.live.com/redir?resid=3fd6cdd8cde1b711!114&authkey=!APd0_2xdY_3izhQ&ithint=file%2cLOG
https://onedrive.live.com/redir?resid=3fd6cdd8cde1b711!115&authkey=!AIQSsEoJ0LBvCZE&ithint=file%2clog
https://onedrive.live.com/redir?resid=3fd6cdd8cde1b711!116&authkey=!AD6FuNbGaKVTpW4&ithint=file%2clog
Thanks in advanced.
↧
Error when importing Operating System into MDT 2013 Update 1
Hi Guys,
I am getting an error when importing an operating system into my deployment share.
Performing the operation “import” on target “Operating system”.
Creating new item named REFW81X64CDrive in Windows 8.1×64 REFW81X64.wim at DS002:\Operating Systems.
Creating new item named REFW81X64CDrive in Windows 8.1×64 REFW81X64.wim at DS002:\Operating Systems.
Item already exists: ‘E:\MDT\DEPLOYMENT\Operating Systems\REFW81X64CDrive in Windows 8.1×64.wim’ specified.
Import processing finished.
It says item already exists ” specified. Can you please tell me what is happening??
I have done abit of research and some people are saying to remove the tag of the operating system from the Operatingsystems.xml in the control folder in your deployment share. I have tried this buyt it still is failing.
Some please help!
↧
MDT 2013 - using WSUS with Windows 10 reference image
I have used a process to connect to our internal WSUS server and install latest patches before capturing the reference image on Windows 7 successfully for a long period of time. Now I am trying with Windows 10 and it doesn't seem to behave the same way so I'm looking for someone to tell me what I'm doing wrong. Here is my process:
- MDT 2013 selecting Windows 10 1607
- I have a Pause in my selection task so I can import our internal WSUS server certificate.
- During this pause I also install KB 3189866 manually to fix the WSUS issue 1607 was experiencing
- I have a selection task created to perform Windows Updates and in the customsettings.ini file I have specified our internal WSUS server as the WSUS server it should connect to
- when I resume the Windows Update task starts and it connects to the WSUS server and installs all appropriate updates
- when done I have verified there are no more updates the reference machine needs from the WSUS console and I also can see all the updates that were installed in the update history section on the reference machine
- The process continues on and I capture the WIM file
However, on the reference image I am now no longer able to see anything in the update history section and when I use the new reference image and connect the machine to WSUS it wants to download and install the exact same updates as if they hadn't been installed before. Can someone explain why this is different than Windows 7 and what the heck I'm doing wrong?
↧
↧
MDT Server keeps dropping network connection...
Hi Guys and Girls,
MDT Server keeps losing network connection randomly...although I am starting to think now it is happening while capturing the image.
Does anyone have any suggestions?
Alex Olver
↧
Network Limitations with MDT Server?
Hello, is there networking limitations with MDT with imaging multiple machines at the same time?
I sometimes have to disable and enable to network adapter to get it working again and just wondering if this is due to to much traffic? if so how can I get around this issue? Multicast?
Alex Olver
↧
"Wizard Error: You must be running with Administrator rights. The deployment cannot Proceed." after reboot of Windows 10 Upgrade
I am preparing to upgrade all machines in my environment from Windows 7 Enterprise to Windows 10 Enterprise using MDT 2013 Update 1 Build 8298. I am using the standard upgrade sequence template in MDT and running litetouch.vbs from a domain account with local administrative permissions on the box. The script does its thing and then goes to the Black screen saying Windows 10 is upgrading sit back and relax and the prograss circle with the %. Once the computer reboots and I log back in to Windows (now windows 10) as that same domain user with local administrative privileges I get the following error come up "Wizard Error: You must be running with Administrator rights. The deployment cannot Proceed."
I have tried disabling the Install Applications task as I am not using it at this point. I have also tried adding specific credentials for the tattoo task however to no avail. Each time I still get the error message. I have double check that my user is still part of the local administrator group on the machine, which he is so I'm unclear of what exactly is going wrong.
As you can see I don't have anything crazy setup in my task sequence:
Here is what I have setup in my customsettings.ini:
[Settings]
Priority=Default
[Default]
_SMSTSORGNAME=<CompanyName>
OSInstall=Y
SkipWizard=YES
SkipCapture=YES
SkipAdminPassword=YES
SkipApplications=YES
SkipProductKey=YES
SkipComputerBackup=YES
SkipBitLocker=YES
SkipBDDWelcome=YES
SkipTaskSequence=YES
TaskSequenceID=WIN10-X64-UPG
SkipSummary=YES
SkipFinalSummary=YES
And in Bootstrap.ini:
[Settings]
Priority=Default
[Default]
DeployRoot=\\<Server>\DeploymentShare$
UserID=MDT_BA
USerDomain=<MyDomain>
UserPassword=<MDT_BAPassword>
**Removed some identifying information
I'm trying to make this pretty much automated for the end user to just run LiteTouch.vbs and MDT do the rest however I must be missing something simple. Please help!
↧
Install State Unknown for all Applications installed during UDI Task Sequence
When the UDI Task Sequence finishes, a final "Deployment Complete" window is shown with three tabs (Welcome, Deployment Summary and Applications Installed) and a Start Windows button at the bottom. When I click on the "Applications Installed" tab, all applications have a yellow warning indicating "Install State Unknown" even though every application installs successfully without any errors in the logs. Also there is no SuccessOrFailureCode shown when expanding each application. These same applications install fine via normal deployments (post imaging) and using standard Task Sequences (Install Application step).
↧
↧
Drivers Not Installing on Lenovo Model
I had asked in a previous post regarding a nic driver not installing in a Lenovo mini desktop. However, I have found that after the os is deployed and reboot occurs several things aren't working. I'm using a KVM switch when deploying. The mouse and keyboard show power but do not function. The network is not connecting. I can not get any logs from the machine because of this and for some reason, even though I have the logs being forwarded to the MDT capture folder, they aren't there either.
I'm attempting to image a Lenovo model 10-FM mini desktop, M900. Lenovo has an admin pack for all drivers needed. I imported the drivers into MDT, updated the boot image and replace it in WDS. The mini PXE boots without a problem. After the os is deployed and after the first reboot, when all devices and system setting are complete, the deployment fails with the unable to connect to the share error showing.
Anyone who can offer assistance I would truly appreciate it. I have approximately 180 of these I need to deploy for my school district.
Thanks in advance.
/Bob
↧
MDT 2013 Update 2 Not deploying Windows 8.1 after it upgraded from MDT 2012
Hi All,
We were using one Windows 8.1 build created using MDT 2012 without any issue. After that we upgrade MDT to 2013 Update 2 and ADK 10, then upgraded deployment share. Later on, our build failing after mini setup. It is not executing any step in STATE-RESTORE phase. We end up with an error in BDD log:
Litetouch deployment failed, Return Code = -2147467259 0x80004005
Regards,
Sugu
↧
Windows 10 In-Place Upgrade - Installation Progress Window does not appear after OS Upgrade
Using MDT 2013 Update 2 In Place Upgrade task sequence to upgrade machines to Windows 10. The installation progress window that is usually persistent throughout the deployment process for all other types of task sequences does not appear after the actual OS upgrades. All the tasks still occur as usual and can be followed along in bdd.log but the progress window is no where to be seen
Have any of you been able to see the progress window during a W10 in place upgrade at this point? I've read on another forum about this issue but overall there is not much information on it. It is likely an MDT bug.
This occurs on every machine tested, VMs included, Windows 7 upgrade and Windows 8.1 upgrade. The log files do not seem to yield anything of value but let me know if there is a specific one I should post.
Thanks
↧
Removing Windows 10 built in Apps
Hello,
I created and captured a Windows 10 Reference Build. During my build process I removed some of the Windows 10 built in Apps using a PS command. I made some changes to the profile. When I bring down the image I am seeing the profile changes are there but the built in Apps are back! I was unable to find a place in the unattended file to remove these apps. So does that mean I need to remove these apps each time I build new computer or do I need to do it a different way?<o:p></o:p>
Thanks
↧
↧
MDT 2013 Capture Errors
Domain Admin credentials provided to all tasks in task sequence and Domain Admin group has Full Control on Images volume where DeploymentShare$ is located.
↧
Windows 10 - language pack wizard is not shown
Hi,
I'm trying to make a Windows 10 Enterprise anniversary reference image using MDT 2013 Update 2. I downloaded the Windows 10 EN ISO with the Multi Language Pack. The Windows 10 ISO is 1607 and the Language pack ISO ends with X20-08995. Both ÎSO are 64bit. I obtained them from the volume license site.
The problem is that the language pack wizard is not shown. In the customsettings.ini I use
SkipPackageDisplay=NO
I want to deploy languages EN-US and DE-DE. I also specified both package guid in the customsettings.ini with
Languagepacks001= [GUID]
Languagepacks002 = [GUID]
However in the wizard "user locale" I can chose the language to install English or German.
Another option I was trying to download the German language directly in the reference image which I captured. However when I deploy that captured image the injected language is gone.
I read here in a forum that it is important the language pack matches the exact Windows build. I think in my case it is.
Why do not MDT display the language pack wizard?
Thanks,
Edy
Edy from Switzerland
↧
Escaping WinPE after image capture
Hi,
I am running a deployment that enters/exits WinPE a few times. It runs a new OS install, returns into Windows, runs Windows Update and other scripts, then creates a .wim on the server. After the .wim creation, I need it to "escape" the WinPE environment and run some of the scripts under Windows after recovering from Sysprep. I can't seem to "escape" back into my normal Windows environment by any other means than letting the deployment end.
↧