Single MDT Database and two Deployment shares

I have two unique Deployment shares as I have separated my Deployment shares by OS, as such I have a Windows 7 DS, and a Windows 8.1 DS. The reason behind this is shear size for the number of models I have to support, it would bloat the image over the
15GB mark it sits today.
That all being said what I am attempting to do is utilize a single database as it all houses the proper site information (all 500+ locations), however the issue I am running into is with the fact that if I have an Application bundle in my Windows 7 DS
with dependencies, and I go add the Bundle for the machine to the database in my Windows 8 DS then it overwrites the database information completely and I lose the capability to install the app bundle in my Win7 deployment.
I do understand that if I had both OS within a single DS and had multiple TS for the OS deployment and all the bundles created by OS version and utilized the logic to only install on specific OS version I could get this to work rather easily but as stated
above I support over 40 Models of PC in my windows 7 image and cannot add to its size as it is already a hassle to distribute.
Any help or suggestions would be appreciated.

Keith,
The "Completely" meant that due to the mismatched GUIDs it was overwriting the database entry for the working Deployment share when I added the new Bundle . I have since copied the Bundles from one Deployment share to the other and that seems to
have resolved most of my issues, However I am still seeing in the Applications.xml file that it pulls the applications from the Windows 7 side for Bundles if I do not have an application in that same Bundle for the Windows 8 side. This would attempt to install
even if the app was set only for the Windows 7 side as a SupportedPlatform, as it was added to the Applications.xml file and would always error out because it was unable to find the application for that GUID.
Basically I have a Bundle for all Laptops and on the Windows 7 side I have a few apps that get installed and we are not that far into Windows 8 to needs these same apps yet which is why it was empty on the Windows 8 side.
So your suggestion is indeed the solution but also wanted to make people aware that there cannot be an empty Bundle on one of the Deployment Shares if there are Apps in that Bundle on the other Deployment share.

Similar Messages

Two Deployment Shares -- One boot.wim

No pun intended with the title :) I'm wondering is it possible to have two deployment shares and use only one boot.wim. They're on two different domains, I'm wondering if I had any options to keep this from being a boot.wim for each share,
perhaps an exit script or switching between bootstraps? Any ideas would be appreciated, thanks!
Ryan

The purpose of the bootstrap.ini file is to help WinPE find the share from where it came from. MDT *must* know where the deployment share is If nothing is in the bootstrap.ini file, it will fall back to the LocationServer.xml file (which I typically try
to avoid).
Note that if the WinPE image booted from a PXE server, then MDT can extract the MDT server IP address, so there is *no* need to populate the bootstrap.ini. So for PXE environments, I always leave the values blank in the BootStrap.ini file.
Keith Garner - keithga.wordpress.com

MDT 2013: bootstrap.ini not applying username and password for share access

I customized my bootstrap.ini file to skip the welcome screen, set keyboard locale, and enter a service account username and password for share access. The welcome screen skip and keyboard locale work beautifully but it's not applying the share username/password/domain
at all.
bootstrap.ini:
[Settings]
Priority=Default
[Default]
DeployRoot=\\mydeploymentserver\DeploymentShare$
UserID=myuserid
UserDomain=mydomain.com
UserPassword=mypassword
KeyboardLocale=en-US
SkipBDDWelcome=YES
I verified that the unattend.xml file on the MININT volume during deployment had all of this information populated correctly:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ImageInstall>
<OSImage>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<InstallFrom>
<Path>\\mydeploymentserver\deploymentshare$\Operating Systems\Windows 7 x64 with District Software - 06222014\Windows 7 x64 with District Software - 06222014.wim</Path>
<MetaData>
<Key>/IMAGE/INDEX</Key>
<Value>1</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<Display>
<ColorDepth>16</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<UserData>
<AcceptEula>true</AcceptEula>
</UserData>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="generalize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Identification>
<Credentials>
<Username>myusername</Username>
<Domain>mydomain.com</Domain>
<Password>mypassword</Password>
</Credentials>
<JoinDomain>mydomain.com</JoinDomain>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ComputerName>eos-vm-02</ComputerName>
<RegisteredOrganization>Regional School District 19</RegisteredOrganization>
<RegisteredOwner>Information Technology</RegisteredOwner>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
<TimeZone>Eastern Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Home_Page>http://www.eosmith.org</Home_Page>
<DisableWelcomePage>true</DisableWelcomePage>
<DisableFirstRunWizard>false</DisableFirstRunWizard>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>EnableAdmin</Description>
<Order>1</Order>
<Path>cmd /c net user Administrator /active:yes</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>UnfilterAdministratorToken</Description>
<Order>2</Order>
<Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>disable user account page</Description>
<Order>3</Order>
<Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-TapiSetup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TapiConfigured>0</TapiConfigured>
<TapiUnattendLocation>
<AreaCode>""</AreaCode>
<CountryOrRegion>1</CountryOrRegion>
<LongDistanceAccess>9</LongDistanceAccess>
<OutsideAccess>9</OutsideAccess>
<PulseOrToneDialing>1</PulseOrToneDialing>
<DisableCallWaiting>""</DisableCallWaiting>
<InternationalCarrierCode>""</InternationalCarrierCode>
<LongDistanceCarrierCode>""</LongDistanceCarrierCode>
<Name>Default</Name>
</TapiUnattendLocation>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DisableSR>1</DisableSR>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<UserAccounts>
<AdministratorPassword>
<Value>administratorpassword</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value>administratorpassword</Value>
<PlainText>true</PlainText>
</Password>
<LogonCount>999</LogonCount>
</AutoLogon>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<RegisteredOrganization>Regional School District 19</RegisteredOrganization>
<RegisteredOwner>Information Technology</RegisteredOwner>
<TimeZone>Eastern Standard Time</TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:keyValue="1" wcm:action="add">
<Path>\Drivers</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
</unattend>
... and the bdd.log file appeared not to read the username and password at all:
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = C: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property LogPath is now = D:\MININT\SMSOSD\OSDLOGS]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property Debug is now = FALSE]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Cleaned up a dirty deployment.]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives (False)]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[ZTIUtility!GetAllFixedDrives = C: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[No task sequence is in progress.]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDisk : \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS TargetDisk: \\MININT-U1TGFAD\root\cimv2:Win32_DiskDrive.DeviceID="\\\\.\\PHYSICALDRIVE0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[GetPartitions: 2]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS Target Partition: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="C:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Target Partition not big enough: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #0"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Possible OS Target Partition: \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[New ZTIDiskPartition : \\MININT-U1TGFAD\root\cimv2:Win32_DiskPartition.DeviceID="Disk #0, Partition #1" \\MININT-U1TGFAD\root\cimv2:Win32_LogicalDisk.DeviceID="D:"]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found Drive: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Found FirstPossibleSystemDrive: D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property SMSTSLocalDataDrive is now = D:]LOG]!><time="05:03:38.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Unable to connect to BCDStore.]LOG]!><time="05:03:43.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Not running within WinPE or WinRE.]LOG]!><time="05:03:43.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeploymentMethod is now = UNC]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeploymentMethod = UNC]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployRoot is now = X:\Deploy]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Using a local or mapped drive, no connection is required.]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployRoot = X:\Deploy]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeployDrive is now = X:]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[DeployDrive = X:]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property PHASE is now = PREINSTALL]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property DeploymentType is now = NEWCOMPUTER]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Phase = PREINSTALL]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[About to run command: wscript.exe "X:\Deploy\Scripts\ZTIGather.wsf" /inifile:Bootstrap.ini]LOG]!><time="05:03:44.000+000" date="06-23-2014" component="LiteTouch" context="" type="1" thread="" file="LiteTouch">
<![LOG[Property inifile is now = Bootstrap.ini]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------------------------- Object Initialization -------------------------]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------------------------- Initialization -------------------------]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Synchronizing the environments.]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DeployRoot is now = X:\Deploy]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DeployDrive is now = X:]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished synchronizing the environments.]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting OS info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OSCurrentVersion is now = 6.3.9600]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OSCurrentBuild is now = 9600]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OSVersion is now = WinPE]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsServerOS is now = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsServerCoreOS is now = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting OS info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting HAL information]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property definition is now = BDD_Welcome_ENU.xml]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Microsoft Deployment Toolkit version: 6.2.5019.0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property HALName is now = acpiapic]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting HAL information]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting network info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Checking network adapter: [00000001] Intel(R) PRO/1000 MT Network Connection]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[MAC address = 00:50:56:85:38:B4]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[IP Address = 172.16.4.182]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[IP Address = fe80::c98:9fef:4305:51f0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Default Gateway = 172.16.4.1]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IPAddress001 is now = 172.16.4.182]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IPAddress002 is now = fe80::c98:9fef:4305:51f0]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property MacAddress001 is now = 00:50:56:85:38:B4]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DefaultGateway001 is now = 172.16.4.1]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting network info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting DP info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Unable to determine ConfigMgr distribution point]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting DP info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting WDS server info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Not Wizard = False]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property WizardComplete is now = N]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="Wizard" context="" type="1" thread="" file="Wizard">
<![LOG[Property WDSServer is now = mydeploymentserver.mydomain.com]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting WDS server info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property HostName is now = MININT-U1TGFAD]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting asset info]LOG]!><time="05:03:45.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[FindFile: The file x86\Microsoft.BDD.Utility.dll could not be found in any standard locations.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 1]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[RUN: regsvr32.exe /s ""]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[FindFile(...\Microsoft.BDD.Utility.dll) Result : 0]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[RUN: regsvr32.exe /s "X:\Deploy\Tools\x64\Microsoft.BDD.Utility.dll"]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property AssetTag is now = No Asset Tag]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SerialNumber is now = VMware-42 05 2b f7 cd 5b 63 fd-83 8a 77 84 7c ed 79 05]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Make is now = VMware, Inc.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Model is now = VMware Virtual Platform]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Product is now = 440BX Desktop Reference Platform]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property UUID is now = F72B0542-5BCD-FD63-838A-77847CED7905]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Memory is now = 2047]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Architecture is now = X64]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property ProcessorSpeed is now = 2800]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property CapableArchitecture is now = AMD64 X64 X86]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsLaptop is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsDesktop is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsServer is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsUEFI is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsOnBattery is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsX86 is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsX64 is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsSLAT is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting asset info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting OS SKU info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Unable to determine Windows SKU while in Windows PE.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Determining the Disk and Partition Number from the Logical Drive X:\WINDOWS]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property OriginalArchitecture is now = ]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Getting virtualization info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsHypervisorRunning is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsVT is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsNX is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property Supports64Bit is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property SupportsHyperVRole is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsVM is now = True]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property VMPlatform is now = VMware]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished getting virtualization info]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Connection succeeded to MicrosoftVolumeEncryption]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[There are no encrypted drives]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property IsBDE is now = False]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Processing the PREINSTALL phase.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Determining the INI file to use.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Finished determining the INI file to use.]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Using from [Settings]: Rule Priority = DEFAULT]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------ Processing the [DEFAULT] section ------]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Property DEPLOYROOT is now = \\mydeploymentserver\DeploymentShare$]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[Using from [DEFAULT]: DEPLOYROOT = \\mydeploymentserver\DeploymentShare$]LOG]!><time="05:03:47.000+000" date="06-23-2014" component="ZTIGather" context="" type="1" thread="" file="ZTIGather">
<![LOG[------ Done processing X:\Deploy\Scripts\Bootstrap.ini ------]LOG]!>

Basics - Server 2008 R2 - SP1, WDS, MDT 2013
Well all, I've done this at least 20 times today and the deployment share info is still wrong...
Someone else built and messed with this thing so i'm trying to fix it. We have 2 MDT servers and 1 WDS that is on the Production MDT. I've turned the test MDT off.
It was working fine, until I updated the deployment share ... after adding some drivers for the surface pro 3 for the pxe boot
Very Simple bootstrap.ini
[Settings]
Priority=Default
[Default]
DeployRoot=\\MMPDEPLOY02\DeploymentShare$
UserID=xxx
UserDomain=xxx
UserPassword=xxx
KeyboardLocale=en-US
SkipBDDWelcome=YES
It continues to show up on the client as ||mdt901w8|deploymentshare$ (test server) (pipes for \ since it makes it a link and i'm new)
I've deleted all the .wim and associated files from all locations from the deployment share\boot folder and from the wds remote install\boot\x64\images folder where they are instead of the remote install\boot\images folder that everyone refers to.
I really can't figure this one out... I know it's something simple I'm over looking but I can't see it..
Any ideas..

MDT 2013 and RES Automation Manager

Hi,
In one of the first step of MDT I'm using a simple script that asks for the country code (e.g. NL), which I would like to store in an environment variable, which I can later on read into RES Automation Manager. But it seems that after MDT is finished and
Windows starts up, the environment variable is gone. Are there any other ways to accomplish this? I'm using it to install language specific applications from RES AM, after MDT is finished. The Windows language settings itself I set with the
CustomSettings.ini, that is based on the same simple script
[Settings]
Priority=ByCountry, CountryAbbr,Model,Default
Properties=CountryAbbr, CountryOU,CustomProperty
[ByCountry]
UserExit=ZTIGetCountry.vbs
CountryAbbr=#GetCountryCode()#
[NL]
CountryOU=NL
CountryOrRegion=31
InputLocale=0409:00020409
KeyboardLocale=nl-US
UserLocale=nl-NL
UILanguage=nl-NL
TimeZoneName=W. Europe Standard Time
ZTIGetCountryCode.vbs
Function UserExit(sType, sWhen, sDetail, bSkip)
oLogging.CreateEntry "entered UserExit ", LogTypeInfo
UserExit = Success
End Function
Function GetCountryCode()
Set objShell = CreateObject("WScript.Shell")
Set objEnv = objShell.Environment("SYSTEM")
GetCountryCode = InputBox("Fill in Country Code (NL DE DA FR PT); If default, use None")
objEnv("MDT_Language") = GetCountryCode
Set objShell = Nothing
Set objEnv = Nothing
End Function
Any idea what I can do else??
Thanks,
Mario

Hi, this looks quite similar to my blog post I did some time ago:
MDT 2012 LTI Deployment, Regional and Locale settings based on #chars of Hostname
The trick in your specific case is to either, not reboot your machine, or to set the installation of RES Automation Manager right after the reboot.
Basically MDT clean's up it's act after it is finished. This also means the environment variables which are stored in a .dat file in the C:\MININT folder are removed after MDT has finished.
So either you need to find a way to perform your RES AM job, during the MDT task sequence, or set or dump the environment variables to a file are temporarily variable which RES AM can use.
Here are some articles that will help you get further:
MDT and RES Automation Manager – Let’s come together (in Sweet Harmony)
Creating custom variables in MDT 2013
Finding All References to MDT Variables in a Deployment Share: VariableDocumentor
v1.0
Dumping Task Sequence Variables
Cheers!
If this post is helpful please click "Mark for answer", thanks! Kind regards

MDT Deployment share and SQL Share on different servers

Hello Technet,
I would like help to figure out how to deal with my MDT Deployment share being on a different server than my SQL Share. I am trying to use the MDT Database in MDT 2013 and SQL Server Express 2014. My deployment share is located on a Linux File Server share,
and my MDT Server and SQL Express Server are located on the same Windows Server 2012 VM.My Bootstrap.ini therefore looks like this:
[Settings]
Priority=Default
[Default]
SkipBDDWelcome=YES
DeployRoot=\\192.168.1.10\DeploymentShare$
UserID=user
UserPassword=password
my Customsettings looks like this:
[Settings]
Priority=CSettings, CPackages, CApps, CAdmins, CRoles, Locations, LSettings, LPackages, LApps, LAdmins, LRoles, MMSettings, MMPackages, MMApps, MMAdmins, MMRoles, RSettings, RPackages, RApps, RAdmins, TaskSequenceID,Default
[Default]
CaptureOS=YES
[CSettings]
SQLServer=SQLServer
Instance=SQLEXPRESS
Database=MDT
Netlib=DBNMPNTW
SQLShare=Logs
Table=ComputerSettings
Parameters=UUID, AssetTag, SerialNumber, MacAddress
ParameterCondition=OR
Therefore, the problem is that during winPE Bootup, WinPE connects to the deploymentshare using the provided credentials just fine, and tries to process customsettings. However, I can map a network drive to the SQL Share as seen in the logs by the following
errors:
1.ERROR-Unable to map a network drive to \\SQLServer\Logs
2. ZTI Error opening SQL Connection:[DBNETLIB][ConnectionOpen(Connect()).]SQL Server does not exist or access is denied.
3.Unable to establish database connection using [CAPPS] properties.
In WinPE, as soon as I hot F8, and use net use \\SQLServer\Logs, the deployment works fine and the properties are read from the database during each section process..
Why is MDT Unable to map the \\SQLServer\Logs , and it requires the manual use of net use? Must I move the deployment share to the same server as my SQL Server Server? Thanks so much.

Should work, Don't know why it's failing.
Can you post your full bdd.log file to a public site like OneDrive and share the link?
There are some inconsistencies with your written summary above.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Upgradation of Primary (RAC) two node database and single node standby DB

We have our primary setup in Oracle RAC in 10g R2 (10.2.0.1.0) in HP UX 11i 64bit (PA RISC). It is a two node RAC.
And we have a single node standby database (DR).
Both the primary and standby database are existing in 10.2.0.1.0
We need to upgrade the primary and standby database from 10.2.0.1.0 to 10.2.0.4.0
Am planning to go through the DBUA method for upgrading the database.
I like to know is there any special cases for upgrading both the primary and standby database.
since as i mentioned i will upgrade the database through dbua method, and if i upgrade my standby database as same as primary,
will it forcefully open the database, because while we upgrade the database through dbua it will open the database at the end of installation.
Is it possible to upgrade the standby database with DBUA method even when my standby database is in Mount state.
I will be helpfull if anyone has done this earlier, are there any know issues and is there any good document which i can refer.
with regards
A.Aravind

hi,
thanks for your reply, and i was following the document.
I like to know that is it mandatory to create a new Oracle Home for upgrading from 10.2.0.1.0 to 10.2.0.4.0
or i can proceed the installation of software in the same oracle home.
I will list out my action plan, please correct me if am wrong,
In Primary RAC,
a) Shutdown the database
b) Shutdown the asm instance
c) Stop the nodeapps services
d) Stop the cluster ready services.
e) Stop the enterprise manager
f) Stop the isqlplus
In Standby single node database,
1)Cancel the managed Recovery process
2) shutdown the database
3) Shutdown the asm instance.
PATCHING Process
g) Apply the oracle clusterware patch 10.2.0.4.0 in the same old existing ORA_CRS_HOME
h) Apply the oracle database software patch 10.2.0.4.0 in the same old existing ORACLE_HOME
Note: In my case both the ORACLE_HOME and ASM_HOME are in the same location.
i) Execute dbua to update the database in the primary database.
j) Apply the 10.2.0.4.0 patch in standby database ORACLE_HOME where as ORACLE_HOME and ASM_HOME are in the same location
k) Copy the recently generated archive logs from primary to standby manually and apply in standby database.
l) Mount the database in standby
m) Start the Managed recovery process.
with regards
A.Aravind

My wife and I have two different accounts with apple, and want to share a database.

Let me start by saying that we both just moved from under a rock and started using Apple and Itunes.
I have a 4S she has a 4. We both created an account before using Itunes. I set up itunes on our home pc (XP) without thinking about her wanting/needing to share the pc for syncing and loading music to our phones. I dont want to plug her in until I am sure we wont mess anything up.
Is there a way we can use one pc and two different devices with two different accounts without a divorce. The majority of cds were hers, so i'm already on her bad list
Please help
Len Adams

You're welcome.
Happy Holidays to you and your family.
Please note the items listed under Legend in the right sidebar of this page.

Dell Laptops E7440 & E7240 - Issues with connecting to MDT 2012 deployment share

Hi,
Good afternoon.Need help on this please
-Test laptops Iam using are 2 * E7440 and 1*E7240. One laptop of model E7440 has our image installed and other two (1*E7440 & 1*E7240) are shipped from Dell with default Win 7 64 bit OS.
-Test desktops Iam using are Dell Optiplex 3020 & Dell 3010 . Both models have our own images of Win 7 64 Bit.
-Laptops and desktops are on same network .
-For OS deployments we have MDT 2012.
-While there are no issues with desktops, all the laptops mentioned above don’t connect to MDT deployments share . The detailed error message I get when I run a litetouch ISO is ‘A connection to the deployment share could not be made. Connection OJ.Possible
cause:invalid credentials. Retry : Try again to connect to the deployment share.’
-Have injected all possible network & storage drivers mentioned by Dell & Intel into MDT boot image but the problem still persists. Still WinPE doesn’t detect network adapter wherein IPaddresses are not picked in WinPE mode.
-Have been testing each and every driver by manually loading them into Winpe mode to see if they pick up the IP addresses and I finally found one driver by name ‘e1d63x64.inf ‘ which I downloaded directly from Intel website. This one is picking IP Address
in WinPE mode when loaded manually. Also have tested the connectivity to MDT server in WinPE mode with net use command and it was successful.
Have injected this driver into MDT Laptop deployment share, regenerated the ISO and tried again however Iam still unable to connect to the deployment share with litetouch ISO.
The above driver is very much part of set of network drivers on Dell website too.But it doesn’t work.
-Have also tried combination of network & storage drivers from Dell website (along with the above one mentioned ) injecting them into the MDT laptop boot image but no luck.
-Every time I make changes to drivers in boot image,I update deployment share & recreate boot image .
-This very litetouch iso connects to MDT deployments share for Dell desktop models 3010 & 3020 but have issues with laptop models E7440 & E7240. This means any connectivity or access issues can be ruled out. Also no problem with our image cause
this happens even with brand new shipped laptops with your inbuild win 7 OS.
-Have tried all options suggested on internet,tested all the drivers suggested but no luck.
-For example I tried latest E7440 netwrok & storage drivers ,Dell Win PE drivers,drivers from Intel website,etc individually as well as in combinations but the issue persists.
-If you google many express similar issues with these laptop models.
Though I used the drivers suggested by various bloggers,nothing worked for me.
Any help on this is appreciated.Thanks in advance.

Hi,
I have several E6420, O3010 and since a week also some E7440 and E7240 on site.
I never had issues using the current Dell PE package for MDT.
At the moment my PE contains only the drivers from the Dell PE 3.0 package (WinPE3.0-Drivers-A13-D67JC)
and all my systems mentioned abobe have no issues connecting to the deployment share.
(btw: I have also some older E6400, E6410 and O390 I do no longer support, they
are supported by the pack Dell-WinPE-Drivers-A05.CAB according
to the Dell site, but I just started a deplymenst on a E6410 and is is also workign with just the latest PE pack)
I'd
suggest you start over with your deplyoment share using at least MDT2012 Update 1.
Create a folder "PE" under "Out-of-Box Drivers" and extract latest Dell PE pack and import he drivers there
Create a selection profile e.g. "PE Drivers" and include just the "PE" folder created above
When configuring the Windows PE settings of your deployment share select "PE
Drivers" selection profile for the driver injection in the "Drivers and Patches" to keep the PE image free of not needed drives.

MDT - iaStorA.sys error when starting up, Status: 0xc0000098, multiple errors updating deployment share

I recently had rearranged our imaging by creating selection profiles for each computer model and then creating a task sequence for each model so that it looks for a model and only injects the drivers for that model. Everything had been working great
and then we got a new batch of Dell Latitude E6440's in. I checked over the machine and just wanted to make sure nothing changed so i grabbed a couple drivers off of it and uploaded them into mdt under that model. I went to update the deployment
share and started to get a whole host of Error: 2, no driver packages were found on the specified path. Verify the driver .INF file are in the specific location and try the command again. It points to the dism log and exit code is =2 then it says DISM
/Add-Driver failed, rc = 2 and lists all the drivers that had failed. It was a whole bunch for both the x86 and x64. Although i didnt add all these drivers. I only messed with the wifi and nic driver and it was only two files. I ran
through imaging and there were no issues it rebooted windows is about to start and it goes to the black screen with the iaStorA.sys message. I checked everything, i looked over all the chipset drivers i knew i imported and those were still there. I
downloaded the WINPE stuff from dell and found the driver and made sure to import everything in that folder and it skipped it as it said it was still there. I wanted to make sure it wasnt the whole mdt server so i imaged a different computer model all
together and that worked. So i deleted every driver out for this model made sure to delete it if it was in other places. I am now in the process of only including very specific drivers ie just the nic and display and audio and see if it will get
passed first bootup. But what would make it go from working every time for about 3 weeks now to all of a sudden not injecting drivers through updating the deployment share and causing a problem for just this image. I am including the dism log and
it is lengthy. The drivers are all sitting all sorted out in their respected folders on the desktop of the share. This has never been an issue before. here is the log
=== Making sure the deployment share has the latest x86 tools ===
=== Processing LiteTouchPE (x86) boot image ===
Building requested boot image profile.
Determining if any changes have been made in the boot image configuration.
No existing boot image profile found for platform x86 so a new image will be created.
Calculating hashes for requested content.
Changes have been made, boot image will be updated.
Windows PE WIM C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\en-us\winpe.wim will be used.
WIM file mounted.
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\iaAHCI_8.9.8.1005_157DE4AE7437DC1A46C7E0E4B3294E513CB47D80\iaAHCI.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc iaAHCI.inf 8.9.8.1005 (2)
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (14)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
Image Version: 6.3.9600.16384
There was a problem opening the INF file. D:\Windows7\Out-of-box Drivers\hdc\ibexahci_7.0.0.1013_CDE6EABDFCC22A23476F9CB4EA115D63FF4A6DBE\ibexahci.inf Error: 0x80070002.
Error: 2
No driver packages were found on the specified path.
Verify that the driver .INF files are in the specified location and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Exit code = 2
DISM /Add-Driver failed, rc = 2.
Injected driver Intel hdc ibexahci.inf 7.0.0.1013 (15)
Injected driver Intel hdc ibexid2.inf 9.1.1.1013 (6)
Deployment Image Servicing and Management tool
Version: 6.3.9600.17029
There were about 2,000 plus more lines of the same stuff.
For future purposes where should the driver be when import them into mdt and do i need to then keep them? I am still learning all this stuff after taking over the roll in October of 2014. Any help would be greatly appreciated.

Hi KheenanHalvorson,
According to the log ,it seems that there is something missing in the driver package .
According to your description ,I assumed that you have configured the whole process correctly.
To deploy the drivers in this way the driver package should include two files an INF and SYS file .We may need to replace the driver package with another one including the INF file .
Here is a link for reference:
How to manage Out-of-Box Drivers with the use of Model Specific Driver Groups in Microsoft Deployment Toolkit 2012 Update 1
http://blogs.technet.com/b/askcore/archive/2013/05/09/how-to-manage-out-of-box-drivers-with-the-use-of-model-specific-driver-groups-in-microsoft-deployment-toolkit-2012-update-1.aspx
"One thing to note about Driver injections is that the driver must have an INF and SYS file in order for us to install the driver this way. If a driver installs via an EXE and there is no way to extract that driver to reveal the actual INF
and SYS file, then you would be forced to add that driver EXE package as an application and install it as an application. "
Best regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]

MDT 2013 - A Connection to the deployment share could not be made - DHCP Lease was not obtained

First, let me give you some context:
Framework: MDT 2013 with MS SDK 7.1
Task Sequence: Standard Client TS with sysprep and capture.
Target workstation (build workstation): VM Guest on ESX 5.5 host, 8 vCPU, 8GB RAM, LSI Logic SAS Controller, E1000 NIC, SSD DAS
Behavior: The VM loads and installs the OS fine in PE, VM boots into OS successfully and resumes the TS, after the first system reboot, the error message occurs and it reads:
A connection to the deployment share (\\*********\DeploymentShare$) could not be made. DHCP Lease was not obtained for any Networking device! Possible Cause: Check physical connection. Retry:...... Cancel:.....
While observing this error, I didn't notice the NIC hadn't completely initialized and obtained an IP yet (network adapter icon in systray), additionally hitting retry after the NIC was initialized resumed the TS.
This behavior reoccurs with several subsequent reboots until a few more applications (Citrix Receiver, VMware Tools) with services are installed which seem to then slow the system boot-up time and then allows the TS to start after the NIC has initialized.
From several posts I've read on this forum, this particular behavior was alleviated by a "wait for IP lease" mechanism built into the TS engine which was introduced in MDT 2010 SP1, I wasn't able to find any other confirmation whether
this mechanism is still in effect with MDT 2013. Another point worth mentioning from several other posts I was able to find is that this behavior appears to manifested itself on target workstations with SSDs, which would somewhat explain the faster
TS load time vs waiting for an IP lease. I've also tried to replicate this behavior in a non-SSD and low-performance VM environment and I wasn't able to replicate it.
My question: Does anyone else have experienced this behavior with MDT 2013 and if so, how did you resolve it? Or is this a bug?

I have this issue intermittently as well. For us, it coincided with the deployment of IP phones, which meant PoE switches all around. However, the problem persisted even after we turned off PoE to the ethernet ports from which we normally PXE
boot.
As this issue has been intermittent, I've backburnered it. When it does happen, I just wait for the lease to arrive then rerun the wizard.
Thanks for the feedback, that's true the TS can be resumed manually once the lease has occured but it defeats the purpose of an automated TS if I have to keep an eye on it and intervene if I need to.
The network guys here recommended putting wireshark or network monitor on it and figuring out just what the heck is going on. Basically, what Keith Garner said. They also disabled PortFast awhile back to see if that made any difference, and it did
not.

Windows 7 Image Deployment Failed in HP model D530 using MDT 2012 and ADK 8.0

Hi,
I need your help to sort out the following issue.
I have installed MDT 2012 +ADK 8.0 and created Windows 7 32 bit OS from CD in the deployment share and tried deploying the raw OS from Deployment Share in to a reference machine (HP D530) ,the deployment failed also couldn't able to capture
Image from the machine,even the sysprep failed. This is the error
Your PC needs to restart.
Please hold down the power button.
Error Code:0x0000005D
Parameters:
0x030F0209
0x746E6547
0X49656E69
0X6C65746E
So tried the same in another HP machine ,the deployment was success and also was able to capture the refrence machine.
Need your help to find why this error occurred in this specific HP model D530 alone. Is it the reason that ADK was not supported in that specific model.
D530 is the maximum available HW model in client environment so your help will be much appreciated.
Thanks in Advance!!

I have never seen that error before (see identical post). I did a quick internet search and found the following:
http://optimizewindows8.wordpress.com/2013/03/26/how-to-fix-error-code-0x0000005d/
Either:
1) Upgrade your machines with modern processors that support the ADK.
or
2) Downgrade to the WAIK
http://www.microsoft.com/en-us/download/details.aspx?id=5753 and stick with Windows 7.
Keith Garner - keithga.wordpress.com

MDT 2010 - Validation Error: The deployment share is read-only, so no changes can be made

I keep getting the above listed error when trying to update the rules on one of my deployment shares. I've even gone so far as to remove the read-only flag on everything in the share, it doesn't help.
As a workaround, I've been editing the CustomSettings.ini directly, but I'd really like this to work. Any ideas?
As an aside, the 'Alert me when someone responds to this post' never seems to work here. And yes, I've checked my spam folder as well...

Ok, it seems to be related to the MDT WizardEditor, but I'm not sure how. I logged on to the server and was able to update the deployment share several times. I closed the MMC, opened the WizardEditor, opened the Deploy.xml thing inside the WizardEditor, closed WizardEditor, reopened MMC - READ ONLY.
Very weird.

WLS 8.1 two domains with EJB and webapp deployed has JVM conflicts?

Test configuration environment:
Windows 2003 server installed with weblogic 8.1 server and oracle 9i.
This weblogic server have two domains, one is for EJB deployment, the other is a webapp that implements accessing to oracle through EJB.
The issue is when we tested a method provided by the EJB that uses double to calculate some total value, the result was correct. But when we tested it using webapp that was deployed on the same server of EJB, it's result was negative or zero.
I think the reason is that the JVM which both EJB and webapp used for calculation was the same and may made some conflicts when they run at the same time.
Any suggestion would be greatly appreciated.
Thank you in advance!
Shuaibing
Message was edited by:
linuxapple

This morning I deployed that webapp to the Domain that deployed the EJB, The results of calculating in webapp's jsp was correct.
Any one be kind enough to tell me what the calling JVM differences between single domain(deployed by EJB and webapp) and two domains (deployed EJB and webapp separately)?

"Same Database" references and post-deploy scripts

Say that I have two database projects - project A and project B. Project A references project B as a same database reference.
When deploying project A (with Include Composite Objects enabled), all of project B's objects are included, as expected. However, project B's post-deployment script is not run.
Is this by design, or a bug?

Hi Jamie,
In our scenario, we are using post-deployment scripts with MERGE statements as a way to manage population of initial data in certain tables. For example, if you imagine a fictitious Gender table:
CREATE TABLE Gender (
Id INT IDENTITY PRIMARY KEY NOT NULL,
Code VARCHAR(2) NOT NULL,
Description NVARCHAR(16) NOT NULL,
CONSTRAINT [UK_Gender_Code] UNIQUE (Code)
we would have a corresponding entry in the post-deployment script such as:
MERGE INTO Gender AS Target
USING (VALUES
('M', 'Male'),
('F', 'Female')
) AS Source (Code, Description)
ON Target.Code = Source.Code
WHEN MATCHED THEN
UPDATE SET
Target.Description = Source.Description
WHEN NOT MATCHED BY TARGET THEN
INSERT (Code, Description)
VALUES (Code, Description)
WHEN NOT MATCHED BY SOURCE THEN
DELETE;
For tables that (for better or for worse) are expected to always contain certain values, this works very well to ensure that those tables are populated with the correct entries both when databases are initially deployed and when they are updated, and also
works well to handle updating this data for new or modified entries.
But, for same-database references, the post-deploy script never runs, and you end up with empty tables. It's possible to work around this (deploy database B to target, then deploy database A, excluding composite objects), but it doesn't really fit
nicely into the press-F5-to-deploy that SSDT's Visual Studio experience has.

MDT Deployment Share on USB

Hi everyone..
can I use an external HDD to host my MDT deployment share.. Basically, I don't have enough drive space in my laptop to host the deployment share & the WIM's/Apps...
thanks in advance..

USB 3.0 drives are more than fast enough (over 1GB)
USB 2.0 drives are not as fast, but should be OK.
When combined with WDS Multicasting, I would feel confident using a 3 year old laptop to service a single install.wim over a hundred clients using USB 2.0.
However, if you are servicing more than 10 clients over unicast, you will start to get IO bound. Do your performance testing.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Single MDT Database and two Deployment shares

Similar Messages

Maybe you are looking for