Upgraded ADK and MDT to the preview builds for Windows 10 support...
Now I get to the login in WinPE to connect to deployment share and get a message regarding Network Share not found.
Any ideas where to start?
Dave
↧
MDT 2013 Update 1 Preview + Windows 10
↧
Sysprep fails while preparing Windows 10
Hi! I have installed windows 10 pro from the WDS server (sources of OS was were taken from the disc by Hewlett-Packett Inc.), then updated to 15.11 version. And when I start capturing task, sysprep is failed, says, that Sysprep will not run on an upgraded
OS. Why? Window 10 on the disc isn't upgraded OS (cuz I don't know, how HP have made this disc).
↧
↧
MDT Wizard Windows Sizing issues with UEFI
On any system that I set up to use UEFI once I boot into Windows PE using the LiteTouchPE_x64 file that MDT creates all the menu sizes are messed up. Most of the time you cannot even see anything in the wizard windows, you have to resize each window
as you go, and all the buttons and formatting is still all messed up. How can I correct this issue so you can use LTI in UEFI?
↧
MDT/OSD Deployment Page Not showing up corrrectly -MDT 2013 Update2
About 95% of the time, the final MDT/OSD Deployment Complete page is only showing up after logging in as an admin.
It usually shows up after last reboot. Here is the complete error:
The task sequence execution engine failed executing the action (Scan Installed Apps) in the group (OSD Results and Branding) with the error code 1
Action output: [ smsswd.exe ]
PackageID = ''
BaseVar = '', ContinueOnError=''
ProgramName = 'cmd /c "cscript //nologo C:\WINDOWS\UDI\OSD_InstalledAppsLookUp.vbs > C:\WINDOWS\UDI\OSD_InstalledAppsLookUp.log"'
SwdAction = '0001'
Set command line: Run command line
Working dir 'not set'
Executing command line: Run command line
Process completed with exit code 1
Command line returned 1. The operating system reported error 1: Incorrect function.
_____________________________________________________________
Second error:
The task sequence execution engine failed executing the action (Parse Base Variable) in the group (OSD Results and Branding) with the error code 200Action output: [ smsswd.exe ]
PackageID = ''
BaseVar = '', ContinueOnError=''
ProgramName = 'cscript.exe //nologo "C:\_SMSTaskSequence\WDPackage\Scripts\OSD_BaseVariables.vbs"'
SwdAction = '0001'
Command line for extension .exe is "%1" %*
Set command line: Run command line
Working dir 'not set'
Executing command line: Run command line
Process completed with exit code 200
--------------------------------
Initializing Objects
--------------------------------
--------------------------------
Extracting TS Base Variable
--------------------------------
Reading OSD variable: [_SMSTSTaskSequence]
Loading XML from variable string content...
Using XPATH to query for [BaseVariableName]
Failed to read XPATH query value, or value is empty.
--------------------------------
Exiting with [200]
--------------------------------
Command line returned 200. The operating system reported error 200: The code segment cannot be greater than or equal to 64K.
The only thing I see out there is this: http://www.myitforum.com/forums/MDT-2012-UDI-OSD-Results-Window-Installed-Applications-Unknown-m235557.aspx
But there has to be a better way to make sure this works correctly all of the time.
Using SCCM 2012 R2 SP2 CU2
Thanks.
↧
MDT upgrade from 2012 to 2013, update 2. LTI - No mouse or keyboard
I have upgraded MDT from 2012 to 2013, update 2. I've upgraded the Deployment Share, I've run 'Update Deployment Share', which has regenerated the boot image, but otherwise have made no other changes. When I try to image a machine I get to the LTI screens, but have no way to interact with them - no mouse, no keyboard. The drivers are all the same as before.
I use a UFD for booting to image with LTI. There's one thing I don't understand - do the PE drivers actually reside on the UFD or not - I don't see any sign that they're on the stick. Understanding how this works might help me figure this out.
Thanks
↧
↧
MDT 2013 U1 - Batch File Installs
I have an install of MDT2013 Update 1 with Quiet Install Commands of batch files (install.bat, etc). In 2013 Update 1, for some reason the ZTIApplications file changed the way it handled batch files as the install command. I was able to track down the solution for this here
https://social.technet.microsoft.com/Forums/en-US/8b471021-4a84-4366-9467-acf6d03cba38/mdt-2013-update-1-batch-files-are-searched-in-cwindowssystem32-not-in-application-directory?forum=mdt
However, now i have embarked on moving my install files off of my MDT server onto another server on my network. I have copied the files from the MDT server to a new server and then edited the Working directory of the applications in MDT. When i run a task with these applications, the install of those applications fails with error code 1. I thought it may be an issue with the "old" applicaiton in MDT, so i created a new Application from scratch and pointed it at the install files elsewhere on the network and used the quiet install command of my batch file. The install still fails.
In order to troubleshoot, i have done the following.
1. changed the quiet intsall command from a batch file to an executable with switches. This worked fine, however i need to use the batch file since i am doing other things beside installing the application (ie installling multiple applications, transfering files).
2. Put the entire path in the Quiet install command. THis did not work
3. Used the MDT 2013 ZTIApplications file instead of my edited version. This did not work .
Any help would be appreciated.
↧
MDT 2013 (6.2.5019.0) Windows 7 Build
Hi All,
I already have a suspect for this issue (the server hosting the deployment share), but just want to check with other MDT users to see if I'm missing something and barking up the wrong tree.
We have a Windows 7 build for capturing our reference image, and this has started saying <Message containing password has been suppressed> in the completion summary, sometimes once, sometimes more, and sometimes none.
Our last change (last year, and several captures before) was to start using ZTIWindowsUpdate.wsf to patch the image (which had already worked a number of times), so I turned off those entries in the task sequence and found I was still getting the same error.
The build doesn't have credentials set in customsettings.ini or bootstrap.ini, so I added some in to customsettings.ini and built two PCs about 30 mins apart from the same server with the same build and this time on one PC got "The network path was not found" twice instead, the other PC had no errors.
I tried it again and then got the following where the WIM failed to be captured this time. I've done it since and it worked.
The server was up, and this worked since (though still giving us the <Message containing...> error).
I've had a look at the logs, and each time (with no credentials) I think it seems to sometimes struggle to authenticate, and then just work and continue.
<![LOG[Mapping server share: \\buildserver\REFDEPLOY$]LOG]!><time="19:19:01.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch"><![LOG[Unable to connect to share: The network path was not found.
( 0x80070035 ) , trying to connect without username. ]LOG]!><time="19:19:22.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[<Message containing password has been suppressed>]LOG]!><time="19:19:24.000+000" date="03-04-2016" component="LiteTouch" context="" type="3" thread="" file="LiteTouch">
<![LOG[Unable to connect to \\buildserver\REFDEPLOY$. Sleeping for 5 seconds.]LOG]!><time="19:19:24.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\buildserver\REFDEPLOY$]LOG]!><time="19:19:29.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
earlier in the log -
<![LOG[Mapping server share: \\buildserver\REFDEPLOY$]LOG]!><time="10:47:06.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\buildserver\REFDEPLOY$]LOG]!><time="10:47:06.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\buildserver\REFDEPLOY$]LOG]!><time="10:51:59.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\buildserver\REFDEPLOY$]LOG]!><time="10:52:00.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\buildserver\REFDEPLOY$]LOG]!><time="18:59:16.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\buildserver\REFDEPLOY$]LOG]!><time="18:59:16.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\buildserver\REFDEPLOY$]LOG]!><time="19:15:24.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\buildserver\REFDEPLOY$]LOG]!><time="19:15:25.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
And after
<![LOG[Mapping server share: \\buildserver\REFDEPLOY$]LOG]!><time="19:45:10.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\buildserver\REFDEPLOY$]LOG]!><time="19:45:10.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\buildserver\REFDEPLOY$]LOG]!><time="19:46:45.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\buildserver\REFDEPLOY$]LOG]!><time="19:46:45.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapping server share: \\buildserver\REFDEPLOY$]LOG]!><time="20:35:07.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Mapped Network UNC Path Z: = \\buildserver\REFDEPLOY$]LOG]!><time="20:35:08.000+000" date="03-04-2016" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
These builds are done in hyper-v, and I've set up another test VM on another hyper-v server and we still get the <Message containing...> error.
Does anyone have any ideas what could be causing this? Am I missing a clue?
Thanks
↧
Error code -214767259 0x80004005 ...
How many of you have had this problem?
Your reference computer boots from the Litetouch image, installs windows 7 and when it comes to putting the wim back to the DeploymentShare you get the above error to which you click finish and a prompt appears.
From this prompt have you noticed that you cannot access the deploymentshare? if not next time typedir \\servername\DeploymentShare$ you will most likely get a Access Denied message.
This is the entire reason the upload fails. It cant access the share.
If you type net use * \\servername\DeploymentShare$ /user:DOMAIN\Username password and then try and do the dir command above, you will notice it works.
I am now trying the public sharing. Under network and sharing centre in windows 7, click on change advanced sharing settings. Under public turn on ALL sharing for public. Will let you know if it works
Regards James Loker-Steele http://www.lokersteele.co.uk/
↧
Using MDT 2012 to recapture a physical machine.
We have about 200 servers to image, using MDT 2012. While Dell does not offer CABs for servers, we built one from scratch on a physical machine and captured it normally. Now, they found they want to modify the image some. Its my understanding that you
cannot recapture a physical machine once its been captured through MDT, and you must rebuild it all over from scratch again. Is this true? Or can you do that 3 times because of the rearm scenario? I recall back in PXE that you had to modify the unattend
to set the rearm to 0 to recapture. I'm not using physical machines, but VMs, except for this server image since there is no CAB. Otherwise its my understanding that recapturing a physical machine in MDT is not allowed.
Any suggestion about recapturing a server (physical machine) that's already been captured in MDT?
Thanks
Any suggestion about recapturing a server (physical machine) that's already been captured in MDT?
Thanks
↧
↧
MDT - The following networking device did not have a driver installed
Using MDT 6 and WDS
x2 different dell laptops E5440 and E7250 using the same nic card - Intel I218-LM
Booting into litetouchpe_x86 wim
get error
The following networking device did not have a driver installed
PCI\VEN_8086&DEV_155A&Subsys_0DE2039&REV_04 - E5440
PCI\VEN_8086&DEV_15A2&Subsys_062D1028&REV_03 - E7250
Downloaded the drivers from the intel site and loaded im certain the correct drivers I m loading both x86 and x64 as when i look at the inf files it shows
PCI\VEN_8086&DEV_155A and PCI\VEN_8086&DEV_15A2 however the subsys number does not match does this matter?
so in MDT i load the drivers into the WinPE folder then updated the share which completes successfully then updated the image in WDS but i still get the error.
Tried using the Dell drivers as well same problem
What am i doing wrong ?
Any help would be great.
Quick update still having the same problem but i went into winpe and opened the .inf from MDT and I do see PCI\VEN_8086&DEV_15A2&SUBSYS_062D1028 in there dont see REV03 not sure if this makes the difference? so the drivers do match in WINPE folder and still getting the same error.
↧
MDT 2013 U2 UDI Wizard preview not working
Hello. Has anyone else noticed that clicking the UDI Wizard preview does not do anything ?
I have tried on several systems with the same result, nothing happens.
I monitored the activity with process monitor, but the processes it fires seems to exit normally.
eshe
↧
Info on the MDT 2013 update 2 documentation
Hi
Where istheMDT2013 update 2documentation?
Thanks
Bye
Balubeto
↧
DeploymentScripts\Wizard.hta (Win10) Not Running
Hello,
I am using MDT to deploy a Windows 10 image to a test device. After the imaging process the machine logs into the Administrator account where usually the Deployment Wizard should launch and complete the MDT deployment, following a successful message or errors. However, after the device auto logs into the Administrator account to complete MDT, I am presented with a blank Wizard.hta screen. I followed the path to where the Wizard.hta is launching from and the folder is empty.
Folder = C:\Users\ADMINI~1\AppData\Local\Temp\DeploymentScripts\Wizard.hta
I also located the log file and found this: (Wizard.log)
<![LOG[Property LogPath is now = C:\MININT\SMSOSD\OSDLOGS]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Property Debug is now = FALSE]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file> CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:39:25.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard"><![LOG[Microsoft Deployment Toolkit version: 6.3.8330.1000]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[Not Wizard = False]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="1" thread="" file="Wizard"><![LOG[FAILURE ( 20001 ): Definition file not defined. Please call with /Defintion:<file> CommandLine:"\\myimages\mymdt\Scripts\Wizard.hta"]LOG]!><time="15:40:01.000+000" date="03-14-2016" component="Wizard" context="" type="3" thread="" file="Wizard">
Would anyone know why the Wizard.hta is not properly launching and why MDT is not completing on Windows 10?
Thank-you,
AP
↧
↧
Failed deployment
Hello Everyone,
I am by no means an expert on MDT, but I've been requested to take over the MDT build and deployment of a previous contractor regarding a 2012 R2 host. I'm at my wits end as to where to proceed.
Background. The previous contractor(after a lot of undocumented troubleshooting) was able to finally able create a bootable USB using lite-touch to automate the installation of a 2012 r2 host server. We now need to make changes and updates to the image but unfortunately the contract is no longer around and he didn't document what he did to successfully deploy the image.
In a nutshell it is my understanding that the image was first syspreped from a physical server, the wim imported to mdt using a deploymentshare and a specific task sequence. I have left the task sequence exactly as is, using the exact same unattend, media creation and have even simply tried copying the new wim to the usb key to try and install the new image. All have failed in the sense that lite touch does not complete by prompting the user that the installation was successful. There are _SMSTasksequence folders on the c drive and the only way I can clean it up and receive the successfully installation notice is to reboot into the usb on restart. Very strange.
Apologizes for the crude explanation.
↧
MMC snap-in failing when editing the TaskSequence of any deployment. Win7 Win8, after updating from MDT 2012 to MDT 2013 update 2
FX:{ffb8695a-66b4-4929-abb6-15cb8bd2ae3d}
at Microsoft.BDD.Workbench.TaskSequenceEditor.GetActionControl(XmlNode propertyNode)
at Microsoft.BDD.Workbench.TaskSequenceEditor.PopulateTree(TreeNode col, XmlNode node)
at Microsoft.BDD.Workbench.TaskSequenceEditor.PopulateTree(TreeNode col, XmlNode node)
at Microsoft.BDD.Workbench.TaskSequenceEditor.RefreshTree(XmlNode selectedNode)
at Microsoft.BDD.Workbench.TaskSequenceEditor.RefreshData(ResultNode userNode)
at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessNotification(Notification notif)
at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification()
at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)
at Microsoft.BDD.Workbench.TaskSequenceEditor.GetActionControl(XmlNode propertyNode)
at Microsoft.BDD.Workbench.TaskSequenceEditor.PopulateTree(TreeNode col, XmlNode node)
at Microsoft.BDD.Workbench.TaskSequenceEditor.PopulateTree(TreeNode col, XmlNode node)
at Microsoft.BDD.Workbench.TaskSequenceEditor.RefreshTree(XmlNode selectedNode)
at Microsoft.BDD.Workbench.TaskSequenceEditor.RefreshData(ResultNode userNode)
at Microsoft.ManagementConsole.SnapInBase.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.NamespaceSnapInBase.ProcessNotification(Notification notif)
at Microsoft.ManagementConsole.Internal.SnapInClient.Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessNotification(Notification notification)
at Microsoft.ManagementConsole.Executive.SnapInNotificationOperation.ProcessNotification()
at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback)
↧
Windows 10, Change HTML to Internet Explorer, File Assoziation
Hi all
what's the best way to Change file Extension for user?
today we have Tasksequence (for pdf = Adobe Reader and html = Internet Explorer) Edge can't ActiveX
Dism.exe /Online /Import-DefaultAppAssociations:%Deployroot%\MagConfig\FileAss.xml
<LayoutModificationTemplate Version="1" xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification">
<DefaultLayoutOverride>
<StartLayoutCollection>
<defaultlayout:StartLayout GroupCellWidth="6" xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout">
<start:Group Name="Alles auf einem Blick" xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout">
<start:Tile Size="4x2" Column="0" Row="0" AppUserModelID="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
<start:Tile Size="2x2" Column="4" Row="2" AppUserModelID="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App" />
…..
but now me must set all Extensions and from time to time new builds we have many problems
Chris
↧
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
↧
↧
Deployment fails BDD.log disk not found
During deployment PXE Boot to MDT Deployment Share then task sequence fails. Looking at the log it stated disk not found. I have checked to make sure drivers for storage were imported and they were. We have set up selection profiles for drivers but I don't
believe it gets to that point before failing. Any assistance would be appreciated.
↧
MDT Deploy Wizard problems with auto DPI Scaling in WinPE 10.0.10586
Since upgrading our MDT environment to the most current release for Windows 10, Windows PE now automatically sets the DPI based on the native resolution of the screen that it is running. Our current model laptops run with a 1920x1080 resolution, Windows PE sees this and sets the DPI to 144 (150%).
All the fonts are now HUGE but the windows and other elements of the MDT Wizards are tiny. This makes it near impossible for our deployment technicians to navigate through the deployment wizards.
I started looking at the .hta, .css, and .xml files and I notice that the fonts are sized in points, but all the other elements are sized by pixels. This seems to be where the display problems are being caused (other than the fact that the DPI is being dynamically set by Windows PE 10)
Is there a fix for this??? We need one. Soon.
↧
MDT not injecting all drivers
MDT2013.. litetouch deployment.. been using the exact procedure for years with no issues.. uploaded new Windows 10 Image and all drivers for Surface Book.. the system will image (not using WDS for surfaces) and 3 drivers wont install. The
BDD log states no 3rd party drivers found for those devices (I matched the Hardware ID from device mgr to confirm its the actually device(s) having the issue). I triple checked and made sure the driver(s) are there and enabled. After imaging, I
go into device manager and manually point to the driver and it installs properly. It is skipping 2 HD sound drivers and 1 unknown. We dont use Windows Update or WSUS during deployment yet.. however, when I manually point to the driver or do a full
windows update, everything installs. I removed all drivers, and readded and updated ISO.. still wont install them.. any ideas as to whats going on?
↧