Mdt/wds

hi. i am running the deployment workbench on a windows 7 32 bit operating system. i need to deploy windows xp 32 bit. my deployment share is on my windows server 2012 with wds enable. on my windows 7 computer i checked the box for enabling multicast and
write the local path d:\mdt\deployment. question is : do i have to install the deployment workbench 64 bit and aik 64 bit on the windows server or not ?. thanx

Here's a forum that is all about MDT -
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt Though there are some people following this forum who have a fair bit of knowledge about MDT, the percentage of MDT knowledgeable contributors is higher over there.
. : | : . : | : . tim

Similar Messages

Problem with WMI after using MDT/WDS to deploy

Hi
I am using MDT with WDS to deploy windows server.
All is fine, besides WMI from Zenoss for monitoring, it show's me errors like
" Could not read the Windows event log (NT_STATUS_ACCESS_DENIED). Check your username/password settings and verify network
connectivity."
If i do the same installation by hand, everything works.
Do you have any idea how installation from MDT differs from by hand installation, that could have impact on WMI?

Hi Bartosz Kupiecki,
May you must have some misunderstand of WDS and MDT deploy, your issue may occur because your MDT has some unattended file or customize the install image (has setting
some special configuration which different with the your manually installed system), please remove this customize configuration then try again.
More information:
MDT 2013 – Part I: MDT Configuration; Capture a Windows Server 2012 R2 Base OS Image
http://blogs.technet.com/b/askpfeplat/archive/2014/08/04/mdt-2013-part-i-mdt-configuration-capture-a-windows-server-2012-r2-base-os-image.aspx
There have a specific forum to support the MDT question, more detail about the MDT question please post to the MDT support forum.
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
Thanks for your understanding and support.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

MDT / WDS Computers joining the network with correct computer name, but no drivers (including NIC) installed

I'm using WDS and MDT to install the computers in my network.
I recently reinstalled a server 2012R2 with the last available versions of WDS and MDT. Everything works fine except for the fact that none of my computers (different series) is installing the out of the box drivers in windows.
The network connection although is ok during setup because the computers add to the domain with the given computer name.
I'm sure I'm using the correct drivers and in my task sequence I enabled to inject all drivers.
Ideas?

Hi admin0485,
I am not very familiar with MDT, if you used the MDT to install the drivers we can ask in the specific MDT support forum, if you are using WDS to install drivers please recheck
your drivers architecture compatible with your system, we can not use the x64 driver on x86 image.
More information:
Managing and Deploying Driver Packages
http://technet.microsoft.com/en-us/library/dd348456(v=ws.10).aspx
MDT support
forum:
https://social.technet.microsoft.com/Forums/en-US/home?forum=mdt
Thanks for your understanding and support.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Will WDS MDT WDS keep everything?

If I import a custom wim into WDS, then export to MDT, then export to a ZTI ISO...if I import the ISO into WDS will it keep everything that was customized and remain ZTI?
Thanks

Hi nthnu,
"if I import the ISO into WDS will it keep everything that was customized and remain ZTI?"
What is the main question here ?
As far as I know ,the MDT is based on the WDS server.We can configured the iso image from the MDT and then import Boot WIM to WDS to deploy it through the WDS server .
Here is a link for reference :
Deploy Windows 7 The Easy Way: Using WDS, MDT and AIK - Step-By-Step Video
http://blogs.technet.com/b/danstolts/archive/2010/03/11/deploy-windows-7-the-easy-way-using-wds-mdt-and-aik-step-by-step-video.aspx
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]

Unattend errors - MDT,WDS,ADK

I Just setup a new Server 2012 R2 running Wds , MDT and Windows ADK I am having issues loading the captured image back to the pc. I get this error: Error : Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [Specialize].
A component or setting specified in the answer file does not exist.
My current older wds server is running fine and just about everything is setup the same. I have attached my task sequence unattend file and the error log from the failed pc.
Any help would be great.
Thanks
<?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>1</PartitionID>
</InstallTo>
<InstallFrom>
<Path>.\Operating Systems\Windows 7 x64\Sources\install.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>
<ProductKey>
<Key></Key>
</ProductKey>
</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></Username>
<Domain></Domain>
<Password></Password>
</Credentials>
<JoinDomain></JoinDomain>
<JoinWorkgroup></JoinWorkgroup>
<MachineObjectOU></MachineObjectOU>
</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></ComputerName>
<ProductKey></ProductKey>
<RegisteredOrganization>Windows User</RegisteredOrganization>
<RegisteredOwner>Windows User</RegisteredOwner>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
<TimeZone>Pacific Standard Time</TimeZone>
<CopyProfile>true</CopyProfile>
</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>about:blank</Home_Page>
<DisableWelcomePage>true</DisableWelcomePage>
<DisableFirstRunWizard>true</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>
</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>0409:00000409</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>Pa$$word=</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value>Pa$$word</Value>
<PlainText>false</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>Windows User</RegisteredOrganization>
<RegisteredOwner>Windows User</RegisteredOwner>
<TimeZone></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>0409:00000409</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>
<cpi:offlineImage cpi:source="catalog://e077wds12s/deploymentshare$/operating systems/windows 7 x64/sources/install_windows 7 professional.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
</unattend>
2014-05-05 15:17:51, Info CMI CBS_Core_Finalize:Calling cbs core finalize complete
2014-05-05 15:17:51, Info CMI Callback_CMI_ConfigInstall: CBS startup processing re-run complete.
2014-05-05 15:17:51, Info [0x030023] CMI Callback_CMI_ConfigInstall: Exit.
2014-05-05 15:17:51, Info [setup.exe] UnattendSearchExplicitPath: Found unattend file at [C:\Windows\Panther\unattend.xml]; examining for applicability.
2014-05-05 15:17:51, Info [setup.exe] UnattendSearchExplicitPath: Found usable unattend file for pass [specialize] at [C:\Windows\Panther\unattend.xml].
2014-05-05 15:17:51, Info [setup.exe] UnattendSearchExplicitPath: Found unattend file at [C:\Windows\system32\sysprep\unattend.xml]; examining for applicability.
2014-05-05 15:17:51, Info [setup.exe] UnattendSearchExplicitPath: Found usable unattend file for pass [specialize] at [C:\Windows\system32\sysprep\unattend.xml].
2014-05-05 15:17:51, Info IBS Callback_Unattend_InitEngine:Using unattend file found at [C:\Windows\Panther\unattend.xml].
2014-05-05 15:17:51, Info [setup.exe] ValidateSMIPass: serialized settings stream; status 0x00000000
2014-05-05 15:17:52, Info [setup.exe] ValidateSMIPass: construct settings context; status 0x00000000
2014-05-05 15:17:52, Error [setup.exe] SMI data results dump: Source = Name: Microsoft-Windows-Setup, Language: neutral, ProcessorArchitecture: amd64, PublicKeyToken: 31bf3856ad364e35,
VersionScope: nonSxS, /settings/CopyProfile
2014-05-05 15:17:52, Error [setup.exe] SMI data results dump: Description = Setting is not defined in this component.
2014-05-05 15:17:52, Info [setup.exe] ValidateSMIPass: load SMI settings; status 0x00000001
2014-05-05 15:17:52, Error [0x060432] IBS The provided unattend file is not valid; hrResult = 0x80220001
2014-05-05 15:17:52, Error [0x060565] IBS Callback_Unattend_InitEngine:The provided unattend file [C:\Windows\Panther\unattend.xml] is not a valid unattended Setup answer file; hr = 0x1, hrSearched = 0x1, hrDeserialized = 0x0,
hrImplicitCtx = 0x0, hrValidated = 0x1, hrResult = 0x80220001
2014-05-05 15:17:52, Info IBS UnattendErrorFromResults: Hit an unattend error; dumping any info we have about the failure...
2014-05-05 15:17:52, Info IBS UnattendDumpSetting: ------Unattend setting error / warning------
2014-05-05 15:17:52, Info IBS UnattendDumpSetting: Error code = 0x80220001
2014-05-05 15:17:52, Info IBS UnattendDumpSetting: Pass = specialize
2014-05-05 15:17:52, Info IBS UnattendDumpSetting: --------------------------------------------
2014-05-05 15:17:52, Info IBS UnattendErrorFromResults: Error text = Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [specialize].
A component or setting specified in the answer file does not exist.
2014-05-05 15:17:52, Error [0x0600c2] IBS Callback_Unattend_InitEngine:An error occurred while finding/loading the unattend file; hr = 0x1, hrResult = 0x80220001[gle=0x00000490]
2014-05-05 15:17:52, Info IBSLIB PublishCriticalError: Publishing blocked message [Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [specialize].
A component or setting specified in the answer file does not exist.]
2014-05-05 15:17:52, Info This installation is blocked from completing due to compliance failures or invalid input; this is not an internal error.

<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></Username>
<Domain></Domain>
<Password></Password>
</Credentials>
<JoinDomain></JoinDomain>
<JoinWorkgroup></JoinWorkgroup>
<MachineObjectOU></MachineObjectOU>
</Identification>
</component>
Try removing this section^
You don't have anything specified, So it shouldn't affect anything, it seems that it is seeing this section,
noticing there are no defined values and erroring out.

MDT/WDS 2012 - Applying the install.wim file concurrently with the multicast download

Hi Folks.
I have a working MDT 2012 setup on Server 2012. Multicasting is all good and my images are deploying smoothly.
Looking though the "What's New" for WDS 2012 it mentions that "You can apply the install.wim file while it is being downloaded"
Does anybody have any idea on how to get this working with MDT? I can't find any info about this new feature anywhere.
PS. Should add that my Windows PE is built from the Windows ADK via MDT and I'm pushing out Win 7.
Cheers
Chris

This is the article I believe you are referring to:
http://technet.microsoft.com/en-us/library/hh974416.aspx
Unfortunately, no data is given (that I can find) about how to enable the functionality.
David Coulter | http://DCtheGeek.blogspot.com |
@DCtheGeek

MDT/WDS PXE Deployment - DHCP Options for both x64 and x86

Alright, I've found out the option 66 & 67 information, as what to set for each. The problem I'm trying to figure out is what to use for the boot file for option 67. So far all the info I've found says this:
Configure DHCP option 67 with the right boot image file.
For 32-bits systems \boot\x86\wdsnbp.com
For 64-bits systems \boot\x64\wdsnbp.com
I want to be able to use this for both 32 and 64 bit Windows clients, but cannot find anywhere that specifies how I would be able to do both.

DHCP Options (specifically 067) can have a significant impact on which NBP your client can access. If you specify \Boot\x86\Wdsnbp.com you are forcing the client to the 32bit NBP.
If you specify \Boot\x64\Wdsnbp.com you are forcing the client to the 64bit NBP.
Niether option is an ideal solution, especially if you have a varied environment.
I would take a look at the following article and see if it sheds some light on your question:
PXE booting with WDS – DHCP Scope vs IP Helpers

MDT/WDS Keep installing OS on the wrong disk, can't figure out why ?

Everything in Task Sequence and Unnatend.xml is set to install to
Disk0 parition 1 (as default is)
New Dell PC out of the box comes with two Disks (1 HDD and 1 SSD)
SSD is Disk0 (Checked the motherboard and BIOS to see what disk are what) - 1st Boot priority
HDD is Disk1.
After booting from PXE/WDS and watchng Light Touch Installation progress I
SEE it says Preparing Disk0 under the progress bar.
After first reboot it boots to Disk0 as as it should and then it says no boot loader found.
If i go to boot options and Boot from Disk1 it boots to Windows and conttinues with deployment.
If I disconnect Disk1 from motherboard it all installs perfectly.
Why is this happening ?

Add the raid drivers first, not convinced it will help but give it a go (You should add them anyway).
If not, I believe Mark Thomas' solution should help you out.
https://social.technet.microsoft.com/Forums/en-US/45d51409-7853-4d95-9db3-400a047f03e3/osd-and-sata-drive-enumeration-trouble?forum=configmanagerosd
Thanks,

Unable to WDS install Win 8.1 VM on Hyper-V 2012 R2

Hi.
We've recently gone from Server 2008 R2 (Data Center) to Windows 2012 R2 (Data Center) and we're now trying to install Windows 8.1 clients on our Hyper-V solution.
When using the virtual machine creation wizard I create two test machines.
One machine is a gen1 and one machine is gen2 both are set to install via network (MDT 2013) and both a given a 40GB disk and 4GB of ram. Both installations fail.
"Windows setup could not configure windows to run on this computer's hardware".
According to everything I've found on the web this could happen if you try and install Windows 7 - something to do with 4K disks I think. This shouldn't happen on Windows 8.x.
I've seen a few posts where they explain the IDE controller being unable to handle 4K disks so that might explain something but in my case I also have a gen2 machine where disk is attached to a SCSI controller.
As I understand it a server 2012 R2 with Hyper-V should be able to have a Windows 8.1 installed on a VHDX file on a SCSI controller.
Can anyone help out here?
Thank you!

According to the web setup.exe /quiet /norestart should be valid parameters for the components.
What I mean by Applicaton Install is that there's a part of a Deployment Share where you can choose to install applications. A Task which will run at a appropriate time, e.g. Office is installed into our base image at that time. I tried including the Integration
Components before the Office install creating a base image with Office 2013 and the IC.
I also tried to use the base image a create a task for VMs only where no driver what so ever gets installed - it simply installs the base image created and activates Windows and nothing more. That doesn't work either.
The problem in a nutshell is this:
I want to install via MDT/WDS. I don't care if it's a regular machine or a virtual one. Both should work.
I've created several base images (Win7_x86, Win7_x64, Win8_x64 etc.) with Office included and everything has worked fine except when I try and install Windows 8 as a VM.
I must say that I've tweaked around and tried a few things while trying to find the problem so I probably have to test some things again to make sure what I say goes but we've installed both Win7 & Win8 on regular machines without problems but I can't
seem to install a Windows 8 machine via MDT/WDS for some reason as a VM - only on regular PCs.
As tested above installing via ISO works fine and creating a new image didn't help either.
The way I capture an OS is by simply write DoCapture=YES in my Deployment Share Rules section and boot into that Deployment Share (then I get a menu where I can choose to capture the machine and it simply installs the imported Windows ISO via a Standard
Client Task Sequence (where it also installs Office - there's an Application Install section part of the Standard Client Task Sequence).
So really really short; the image I try to install works fine on a regular PC but won't install on Hyper-V.

How do i install windows on mavericks using MDT?

I have no problems installing 7 thru dvd or usb, but cannot get it to install using MDT

Well, what happens when you try? Are all the Mac drivers installed? Where does it fail? What specifi steps are you taking to accomplish this?
I suggest you stick with searching Google and the TechNet forums, as while we're all Mac users here, not everyone uses Windows, let alone MDT. And certainly nobody here would know anything about your MDT, WDS or SCCM environment.

SQL for MDT

i have three servers . DC + MDT/WDS + SQL
i installed SQLExpress with SQL Management Studio 2012
when i tried to create my databse from MDT/WDS server i get an error : 40
provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server”on server
on SQL Manager TCP/IP and Named Pipes are enables.
ports TCP and UDP are opend
DNS resolution works fine
i can ping . but i don't know why i get this message .
thanks
This topic first appeared in the Spiceworks Community

i have three servers . DC + MDT/WDS + SQL
i installed SQLExpress with SQL Management Studio 2012
when i tried to create my databse from MDT/WDS server i get an error : 40
provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server”on server
on SQL Manager TCP/IP and Named Pipes are enables.
ports TCP and UDP are opend
DNS resolution works fine
i can ping . but i don't know why i get this message .
thanks
This topic first appeared in the Spiceworks Community

MDT user login Log?

My google foo is failing me at the moment.
Can someone point me in the right direction so as to find out where MDT logs what user authenticated against the WDS/MDT server to initiate a deployment?
I've been digging around the MDT/WDS servers logs to no avail, I'm thinking I'm looking in the wrong place...

MDT will only generate deployment logs like, TFTP download started, failed, completed etc.
You wont get authentication logs.
Arnav Sharma | http://arnavsharma.net/ Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Wiping a disk with MDT task sequence?

I'm thinking that I could use MDT/WDS to do a secure disk wipe for old computers. Has anyone implemented something like this with MDT?

Take a look at the "Client Replace" Task sequence template supplied with MDT
This Task Sequence is designed to de-commission a client computer, first saving the data to a external network share.
The task sequence also calls the ZTIWipeDisk.wsf script to peform a multi-pass wipe of all partitions.
Then again, if you have machines with sensitive information on them, you should be using disk encryption like Bitlocker to ensure that the data is protected. Simply install a new OS without suspending the old BitLocker protection.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

MDT 2010

When I PXE boot on new Lenovo T440, W540 and X240 I get the following error"PXE - E51: No DHCP pr proxyDHCP offers were received" but I was able to pxe boo the older Lenovo laptop
like T410, T420 and T430. Is anyone out there is having the same issue as me? If so, were you able to fix this issue? Please help.
Thanks,
Nai
Nai

Are you still able to boot the older Laptop? Check to see if both DHCP and WDS (Windows Deployment Services) are running. And or if you are PXE-booting on a separate subnet than
that your MDT/WDS server, make sure you have IP-helper configured properly.
Check out this post: http://www.bootix.com/support/problems_solutions/pxe_e51_no_dhcp_or_proxydhcp_offers_were_received.html
Marius A. Skovli | MCP/MCTS/MCITP | Twitter: @mariusskovli

Netboot a Apple PC on a Windows DHCP server.

I need to set up our Windows DHCP servers to support netboot across subnets for our Apple machines. I am unable to find a clear list of what scope options and what data they need online. Can someone provide me this information?
Thanks!
Shawn

Hi,
Although Microsoft does not recommend this method, you can use the following DHCP options to direct PXE clients to an appropriate NBP to download:
• Option 60 = client identifier. You should set this to the string PXEClient. Note that this only
applies if DHCP is on the same server as Windows Deployment Services.
• Option 66 = boot server host name
• Option 67 = boot file name
Managing Network Boot Programs
http://technet.microsoft.com/en-us/library/cc732351%28v=ws.10%29.aspx
The similar thread:
WDS,PXE & DHCP
http://social.technet.microsoft.com/Forums/en-US/cb02c4ac-0ab6-401d-96d3-bd0d61e6eee3/wdspxe-dhcp?forum=configmgrosd
MDT/WDS PXE Deployment - DHCP Options for both x64 and x86
http://social.technet.microsoft.com/Forums/en-US/6f7a1af4-0dd8-4af6-8d2a-1e9ee16a8f37/mdtwds-pxe-deployment-dhcp-options-for-both-x64-and-x86?forum=mdt
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Mdt/wds

Similar Messages

Maybe you are looking for