I everyone, I've got a master with Windows 1803 and we wan't to update it with Windows 1903. Because of old informix database, the master can't be fully rebuild without installing manualy some software so is it possible to update the master in 1903 by an deploy update and capture sequence?
I try different things but no success so I need help, even to know if it's possible to do it?
Thanks
I upgraded to 2004 and set up a new TS to deploy the image.
My TS is exactly the same as my 1809 was. In the State Restore phase, I have
Gather local,
Apply Network Settings,
Post-Apply
Recover from Domain
Tatoo
As soon as I get to Recover from Domain, the pc reboots. Just once, and then comes up to a logon with
Administrator (and a username and password field below it
and another Administrator at the bottom (which is the correct one to use). The problem is, after the reboot
it doesn't goes on to the desktop to finish the TS unless I sign on as admin.
This has me stumped and I'm prevented to move on to 2004 until I can figure this reason out.
Any ideas would help.
Everything was going okay, now all of sudden all my captures fail because it says "Another copy of this application is already r unning". I've tried multiple computer and VMs and the results are all the same. What's going on?
Hi
I have a deployment Task Sequence for a freshly created Windows Server 2016 Server image that i just captured. I captured the WIM file directly from a Dell T430 Poweredge which had drivers and windows updates installed using a standard Sysprep and Capture task sequence. I created a standard Client Task Sequence based on the WIM file to deploy.
While deploying i get Failure (5624) 1392 Run DISM Error
In DISM.log
2020-07-23 12:48:00, Error DISM DISM WIM Provider: PID=716 G:\Windows\WinSxS\ManifestCache\c51851603bc3818b_blobs.bin (HRESULT=0x80070570) - CWimManager::WimProviderMsgLogCallbackin SMSTS.log
<![LOG[Could not find CCM install folder. Don't use ccmerrors.dll]LOG]!><time="12:48:01.124+480" date="07-23-2020" component="TSManager" context="" type="0" thread="1984" file="String.cpp:1364">I presume that my WIM file is corrupted . anyway to recover or start from scratch ?
I have a parent server which I have built with WDS PXE boot, and MDT 2013 (Win 10ver2004 config). All installations, configurations, etc. are processed and handled through MDT.
I am NOT running SCCM in this environment.
I create a multicast transmission from MDT Deployment Workbench using Update Deployment Share action. The Multicast Transmission is housed within, and called from, the WDS server's Multicast Transmissions section.
This process works flawlessly on my parent server.
I have built a number of Distribution Points (DP) throughout numerous States across the U.S., which all operate as children using DFS-R. Each Child DP has a WDS for localized PXE booting and imaging. This entire process works flawlessly at every step, at every location.
No child has an MDT server, as the parent server shares out all necessary files and folders for localized builds. We like it this way, to keep everything setup for centralized management at the parent level.
The issue I am running into, is that although multicast works perfectly at the parent server, none of the DPs seem to be creating a usable multicast transmission for their clients to use. Log files show the following:
From there, Unicast completes perfectly fine.
How do I go about creating Multicasts at each DP (Child Server)? I've gotta be missing something here.
Hi,
I am getting Error code 0X8007007B while activating the office 2010
Commands used from Administrator`s Command prompt :- cscript "C:\Program Files\Microsoft Office\Office14\ospp.vbs" /act
Shailendra Dev
Using: Microsoft MDT version 8456, with KB 4564442 applied following install of Windows 10 2004 ADK
Good morning,
I have been using a reliable Build and Capture task sequence for some time, and all versions of Windows 10 up to 1909 have been built and captured successfully, without errors, with the task sequence. This includes a 1909 build and capture after updating
the ADK and then KB4564442 applied with deployment share updates and new ISO generated for booting.
However, whenever I am attempting a build and capture with Windows 10 2004, the task sequence gets to execute sysprep, and this fails.
C:\windows\system32\sysprep\panther\setupact.log points towards MicrosoftWindows.Client.CBS as being the culprit, extract from the log file is below:
2020-07-28 09:45:24, Info SYSPRP Entering SysprepGeneralizeValidate (Appx) - validating whether all apps are also provisioned.
2020-07-28 09:45:24, Error SYSPRP Package MicrosoftWindows.Client.CBS_120.2202.130.0_x64__cw5n1h2txyewy was installed for a user, but not provisioned for all users.
This package will not function properly in the sysprep image.
2020-07-28 09:45:24, Error SYSPRP Failed to remove apps for the current user: 0x80073cf2.
2020-07-28 09:45:24, Error SYSPRP Exit code of RemoveAllApps thread was 0x3cf2.
2020-07-28 09:45:24, Error SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'SysprepGeneralizeValidate' from C:\Windows\System32\AppxSysprep.dll;
dwRet = 0x3cf2
2020-07-28 09:45:24, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x3cf2
2020-07-28 09:45:24, Error SYSPRP RunPlatformActions:Failed while validating Sysprep session actions; dwRet = 0x3cf2
2020-07-28 09:45:24, Error [0x0f0070] SYSPRP RunDlls:An error occurred while running registry sysprep DLLs, halting sysprep execution. dwRet = 0x3cf2
2020-07-28 09:45:24, Error [0x0f00d8] SYSPRP WinMain:Hit failure while pre-validate sysprep generalize internal providers; hr = 0x80073cf2
Performing a check on getting the information for the Windows Package shows that it is installed, but pending removal, but also that it'a a system level application.
Clearly that's something newly added in 2004, as checking for this in Windows 10 1909 shows nothing, and no errors during sysprep.
Can anyone please suggest how this can be resolved?
We recently upgraded our MDT Database from 2008 to 2016 and the new server uses TLS 1.2 only. When attempting to connect to the DB using TCP/IP on a specific port we receive this error in the BDD Logs while retrieving the location settings in bootstrap.ini.
[DBNETLIB][ConnectionOpen SECDoClientHandshake()]SSL Security error
Also, using a custom HTA front end, when trying to retrieve data from the DB we get the same message.
sconn="Provider=SQLOLEDB;OLE DB Services=0;Data Source=SomeServerName\SomeInstance,SomePort;Initial Catalog=SomeDatabase;Network Library=DBMSSOCN;Integrated Security=SSPI"
Searching the web I found that the older SQLOLEDB provider is not capable of supporting TLS 1.2
Does anyone know what is required to make MDT communicate to the DB using TLS 1.2 only?
I have successfully capture image and deployed windows 10 2004 throgh MDT. User can login and user for few hours without any issue. It is going to freeze after 3 hours.
Is anyone facing same issue in windows 10 2004 image deployment?
Greetings.
I would like some advice as to why certain devices are not installing when deploying via MDT. It seems to be mainly software components/extensions that are not installaing during deployment, despite having the driver/software imported and being in the correct section of the oob drivers folder. I have oob driver folders setup to use model names in order to select drivers and it works for everything except the above.
However when selecting to update the driver via device manager, and pointing it to the same driver folder in the deployment share, it will install the device no problem. Is there any way I can add a task to force another driver installation session at some point later in the sequence? Or am I barking up the wrong tree trying to install those components via mdt even though they are a class that it supports?
Any advice appreciated!
Thanks
One of my VM's that I just upgraded to 2004 boots correctly from the resume icon. It continues on to the Capture to create a WIM.
Another VM I upgraded in the same manner boots up to the desktop, I launch the Resume, it reboots, boots up to the grey screen where it should start a Capture, but ends up at a CMD dos box. I'm not sure why this isn't creating a WIM like my other VM did.
Anyone know what happens when a VM boots to a CMD?
I work for a school with 7 sites.
I am building images in MDT, and would like to have them be the same across the board with the exceptions of adding them to different OUs and also installing software based on the schools VLAN. I know it's possible to accomplish this, but I am unsure how?
Help?
Hello,
I'm using MDT lite touch to deploy Windows 2016 onto a Dell server with a raid controller (PERC 740)
Booting the server with a USB to start the process, rather than using PXE
I'm creating the virtual disk on the PERC using the tool, PERCCLI64. This is integrated in the task sequence; such that it will create the virtual disk only if it finds unconfigured disks.
Since the virtual disk is created after bootup, the disk IDs are respectively: 0 for the USB, and 1 for the virtual disk
After creating the virtual disk, and before "Format and Partition" step, I update the TS variable OSDDiskIndex to point to the virtual disk, so that the "Format and Partition" step will install onto the virtual disk.
However, the issue I am seeing is that the task sequence is failing when it has to perform the first reboot ("Restart Computer" under "Post Install"). Looking at smsts.log, I see numerous references to "Failed to save environment
to (80070057)"
I tried creating the virtual disk outside of the task sequence, and then power cycling to start the MDT install. In this situation, the install completes fine. The virtual disk will have an disk ID of 0 in this situation, so I don't need to modify OSDDiskIndex
BDD.log and smsts.log are in the link below
https://1drv.ms/u/s!AvmUZmjHK8m5gedWM5Tgy4XJa3twpw?e=IXi2l7
Any insights would me much appreciated.
MDT 8456, ADK 1903 (with update)
This all seemed to be working well for a while. I created/upgraded some VM's to 2004 and added encryption in MDT during imaging.
With 2004, I have a few different images, but they all behave the same:
If I drop that image on a Dell, it encrypts during deployment and writes a key to AD.
If I drop that same image on a Panasonic, same TS, it does not encrypt. I get a message about "Group Policy settings require that a recovery password be specified before encrypting the drive. This drive (C:) has been encrypted with Bitlocker and now
just needs to be activated."
-----
When you click Activate, another popup comes up saying Element not found.
How could AD allow 'some' models to encrypt and not others, especially when a week ago I tested my 2004 on a Panasonic and it worked just fine?
Its a major roadblock for me...
By the way, 1803 and 1809 encrypts both Dells and Panasonics.
I also see 1 error at the end of imaging: Message containing password has been suppressed.
Great, but I can never activate Bitlocker at all on these.
I currently have a layout mod file for 1803/1809 which allows 6 tiles across.
Using that same Layoutmidification for 2004, it is only 3 tiles wide.
Do I have to make a new Layout file for 2004? And if so, how would I have 1809 use one file while
2004 would use another named the same thing?
Has anyone found a way to silently install GoogleEarthProV1.3.35.exe silently?
I fooled around with some switches and once it did run but then it also launched during deploy.
I can't find an MSI anywhere, so this being an exe I've tried all I know. One other time it worked but
wasn't adding a shortcut to ALLUSERS desktop as an icon.
I'm hoping to find a correct command to install that exe with an icon for ALLUSERS.
Any assistance would be greatly appreciated.
Hello,
We are having a strange issue with MDT driver installation. Drivers inject when the task sequence starts however, when the PC boots up, none of the drivers that are imported into MDT are installed. If I look in \DeploymentLogs\Bdd.log it seems that MDt is finding drivers, one log entry at the bottom.
Drivers installation is configured in the rules as below:
DriverSelectionProfile=Nothing
DriverGroup001=Windows 10\%make%\%model%
This server is managed by someone else but there ae two that seem out of the ordinary to me. One is, it isn’t joined to our domain and the other is that bootstrap.ini does not have UserID, UserDomain or UserPassword configured, we have to type the user name, password and domain on each deployment. I can’t see this interfering with driver installation but wanted to include these two details just in case.
If there are any other details I can provide, please let me know.
Thanks I advance.
<![LOG[Found a driver for Device: {678d7426-acb1-4273-9553-cae8a02e8cbd} from \\Server1\DeploymentShare$\Out-of-box Drivers\MEDIA\AtihdWT6_10.0.1.09_97C6C170DE484B7E32532D4F4E06BAC8582D295C323B0C4DF1A0A3BD375EEEEB\AtihdWT6.inf]LOG]!><time="07:19:10.000+000" date="03-12-2020" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
<![LOG[Validating connection to \\Server1\DeploymentShare$\Out-of-box Drivers\MEDIA\AtihdWT6_10.0.1.09_97C6C170DE484B7E32532D4F4E06BAC8582D295C323B0C4DF1A0A3BD375EEEEB]LOG]!><time="07:19:10.000+000" date="03-12-2020" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
<![LOG[Mapping server share: \\Server1\DeploymentShare$]LOG]!><time="07:19:10.000+000" date="03-12-2020" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
<![LOG[Already connected to server Server1 as that is where this script is running from.]LOG]!><time="07:19:10.000+000" date="03-12-2020" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
<![LOG[Copying drivers from "\\Server1\DeploymentShare$\Out-of-box Drivers\MEDIA\AtihdWT6_10.0.1.09_97C6C170DE484B7E32532D4F4E06BAC8582D295C323B0C4DF1A0A3BD375EEEEB" to "E:\Drivers\MEDIA\AtihdWT6_10.0.1.09_97C6C170DE484B7E32532D4F4E06BAC8582D295C323B0C4DF1A0A3BD375EEEEB"]LOG]!><time="07:19:10.000+000" date="03-12-2020" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
<![LOG[About to run command: cmd.exe /c xcopy /seihycd "\\Server1\DeploymentShare$\Out-of-box Drivers\MEDIA\AtihdWT6_10.0.1.09_97C6C170DE484B7E32532D4F4E06BAC8582D295C323B0C4DF1A0A3BD375EEEEB" "E:\Drivers\MEDIA\AtihdWT6_10.0.1.09_97C6C170DE484B7E32532D4F4E06BAC8582D295C323B0C4DF1A0A3BD375EEEEB" 1> NUL 2>NUL]LOG]!><time="07:19:10.000+000" date="03-12-2020" component="ZTIDrivers" context="" type="1" thread="" file="ZTIDrivers">
Hello,
Is the LocationServer.xml settings still supported in MDT (6.3.8456.1000)?
I was following a tutorial that stated this was possible:
<?xml version="1.0" encoding="utf-8" ?><servers><QueryDefault></QueryDefault><server><serverid>1</serverid><friendlyname>
Contoso HQ, Seattle, USA</friendlyname><Server1>\\STLDS01\Deployment$</Server1><Server2>\\STLDS02\Deployment$</Server2><Server3>\\STLDS03\Deployment$</Server3><Server weight=”1”>\\STLDS01\Deployment$</Server><Server weight=”2”>\\STLDS02\Deployment$</Server><Server weight=”4”>\\STLDS03\Deployment$</Server></server><server><serverid>2</serverid><friendlyname>
Contoso NYC, New York, USA</friendlyname><UNCPath>\\NYCDS01\Deployment$</UNCPath></server></servers>So MDT likes the path in the UNCPath tag for serverid 2, but it doesn't like anything in the serverid 1 section at all. In fact if I remove the serverid 2 section MDT complains that the UNCPath is unrecognised. Anyone else got this working?
Kind regards,
Ricky