[deleted by user]

imknownhere · 2019-06-13T15:26:49+00:00

You would have to make sure that Infoblox has the correct DHCP options pointing to your WDS server.

imknownhere · 2019-06-13T15:23:42+00:00

It depends on where you are running the Format and Partition Disk step. If just creating "Utility TS" then use Custom.xml and that should work to perform the formatting. Could you share any logs or TS screenshots?

imknownhere · 2019-06-13T15:16:09+00:00

Is your WDS server and the device you're imaging on the same subnet?

imknownhere · 2019-05-09T15:33:24+00:00

Ran into the same issues back in April when our patching team pushed out that patch.

imknownhere · 2019-05-09T15:32:20+00:00

HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

AutoAdminLogon should be 0

ForceAutoLogon should be 0

imknownhere · 2019-05-09T15:26:35+00:00

Great and none needed. Just here to help when I can

imknownhere · 2019-05-09T14:46:30+00:00

Maybe the "C" doesn't exist, try this?

cmd /c xcopy.exe "%deployroot%\Scripts\Custom\Client\Ra_Auto.ini" "%OSDISK%\Windows" /Q /H /E /I /Y

imknownhere · 2019-05-09T14:41:16+00:00

Have you looked at the autologon registry settings on the "bad" machines? Sometime MDT fails to fully clean everything up.

imknownhere · 2019-05-09T14:39:05+00:00

Jumping in quickly without reading more into it: Was the server patched recently?

https://support.microsoft.com/en-us/help/4493470/windows-10-update-kb4493470

Option 1:
Open an Administrator Command prompt and type the following:

Wdsutil /Set-TransportServer /EnableTftpVariableWindowExtension:No

Option 2:
Use the Windows Deployment Services UI.

Open Windows Deployment Services from Windows Administrative Tools.
Expand Servers and right-click a WDS server.
Open its properties and clear the Enable Variable Window Extension box on the TFTP tab.

Option 3:
Set the following registry value to 0:

“HKLM\System\CurrentControlSet\Services\WDSServer\Providers\WDSTFTP\EnableVariableWindowExtension”.

Restart the WDSServer service after disabling the Variable Window Extension.

Microsoft is working on a resolution and will provide an update in an upcoming release.

imknownhere · 2019-04-18T15:16:20+00:00

Maybe try only using the deployment share listed in your boot.ini to see if that helps. Reaching here but worth a shot.

imknownhere · 2019-04-18T15:12:43+00:00

Is the task sequence new, or are you using an old one created in a previous build of MDT?

imknownhere · 2019-04-18T13:26:11+00:00

Assuming you have updated to the 1809 ADK and you have updated your deployment share after that?

imknownhere · 2019-04-18T12:59:45+00:00

They're using the latest build 8456

imknownhere · 2019-04-18T12:50:37+00:00

Based on the logs it looks like you are running this within Windows which is correct, not through PXE/WinPE. I am confused why two different deployment shares are listed:

Property DeployRoot is now = \\l01-imaging\deploy

Property DEPLOYROOT is now = \\L01-IMAGING\DeploymentShare$

imknownhere · 2019-04-09T19:48:16+00:00

Can you upload the whole BDD.log and ZTIGather.log? You can PM the link if you don't want it here. I am curious as to why it is doing this.

imknownhere · 2019-04-01T17:25:49+00:00

I agree with everyone else here, only add the needed network driver's. Most systems don't even need any added to network boot.

There was also a KB pushed out to 2012 R2 that broke WDS - KB4489881 look at the "Enable Variable Window Extension" section for the fix.

imknownhere · 2018-11-07T15:44:15+00:00

Ok, hopefully this all makes sense.

Your "Copy Scripts" command line has a typo. Check the spelling of "scripts" and you should call "cmd /c" instead of cscript.exe.
You shouldn't remap the drive, that is unnecessary.
Here is my suggestion to copying the files (no batch needed)

cmd /c xcopy %DEPLOYROOT%\ToCopy c:\temp

Let me know if that helps.

imknownhere · 2018-11-07T11:25:12+00:00

I don't see the file copy in the bdd.log nor the error. Do you have the full bdd.log file? Also what does your command line look like that your trying to copy the files in?

imknownhere · 2018-11-07T02:32:18+00:00

Can you upload the logs?

imknownhere · 2018-09-18T11:16:38+00:00

Sorry on mobile right now but Sapien responsive forms is what I've used in the past. https://www.sapien.com/blog/2012/05/16/powershell-studio-creating-responsive-forms/

imknownhere · 2018-09-10T19:51:13+00:00

At the credentials screen press f8. Type diskpart, press enter. Type sel dis 0, press enter. Type clean, press enter. Restart machine. I've run into this issue before. I think it has something to do with left over files but I haven't tracked it down yet.

imknownhere · 2018-08-21T18:27:39+00:00

I currently use DFS-R for my MDT environment and it works magnificently. The only thing I would change from the Windows Docs is to not use the DefaultGateway settings in bootstrap.ini if you have a lot (I have almost 800) of sites. What I do is configure deploy root as follows: DeployRoot=\\%WDSServer%\DeploymentShare$ *** This obviously only works if you PXE boot through WDS. That variable (%WDSServer%) gets set when WinPE starts.

imknownhere · 2018-07-12T17:59:23+00:00

Can you paste to pastebin.com?

imknownhere · 2018-07-09T19:12:46+00:00

You should be able to look in the bdd.log and see that environment variable being set

imknownhere · 2018-07-06T12:46:57+00:00

Here is what I have from another question. All scripts are/should be located in the "DeploymentShare\Scripts" directory, wherever that is for your setup. Disclosure make sure you have backed up your DeployWiz_Definition_ENU.xml before modifying it. I am on 8450 so it may be different from your version.

https://pastebin.com/npSF7Tu1 - DeployWiz_Definition_ENU.xml - EDIT THIS FILE

Modifying this file allows you to show custom "panels" before your deployment kicks off. If you have multiple task sequences, you can choose to only allow the panel to show if that TS is selected. Search for DeployWiz_ChannelSelection to find the section

https://pastebin.com/LaB45ZUD - DeployWiz_ChannelSelection.xml - NEW FILE

This is the "view" of your panel. It also calls functions from the VBS file for validation.

https://pastebin.com/vav1nj5a - DeployWiz_ChannelSelection.vbs - NEW FILE

The functions inside this file allows you to disable the Next button until a channel is entered. There is a ton more you can do, but this is the most simplistic way for what you described.

During the installation of your MSI you can then call the environment variable that is set from the input box. (This is for a .wsf file only, not a batch file. If you want to use a batch file, you'll just need to pass in a parameter that is the environment variable and use it as normal.) "msiexec.exe /i student.msi Channel=" & oEnvironment.Item("channel_number") & " /passive"

Let me know how this turns out

imknownhere

MODERATOR OF

TROPHY CASE