RE: [MDT-OSD] Windows 10 1703 breaking auto log on when updates are being applied

[David Landry]

Hi Sean – this is why you do not have a problem with reboots with Windows 10 
1703:

AdminPassword=***

Remove that and I bet you have problems. I have never had to have it in the 
CS.ini file until now.


I try to keep my CustomeSetting.ini file as lean as I can. My thinking is the 
more you put into it, the more chances something is going to change which would 
require upkeep.

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
_SMSTSOrgName=”CompanyName”
SLShare=\\Server name\MDT\Logs\%Model%\%SERIALNUMBER% (this captures the logs 
of every build)
SLShareDynamicLogging=\\Server name\MDT\Logs\%Model%\%SERIALNUMBER% (this 
captures the logs of every build)

OSInstall=Y
SkipCapture=Yes
SkipUserData=YES
SkipBitLocker=NO
TpmOwnerPassword=password
SkipAdminPassword=YES
AdminPassword=Password
SkipProductKey=YES
WSUSServer=http://Server name

OSDComputerName=Sitecode-%SerialNumber%
JoinDomain= FQDN here
DomainOUs1=OU=Laptops,OU=,OU=,DC=domain,DC= 
domain,DC=com
DomainOUs2=OU=Desktops,OU=,OU=,DC= domain,DC= 
domain,DC=com
DomainOUs3=OU=Laptops,OU=,OU=,DC= domain,DC= 
domain,DC=com
DomainOUs4=OU=Desktops,OU=,,OU=,DC= domain,DC= 
domain,DC=com
TimeZone=Timezone #
TimeZoneName=Time zone name

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Sean Chapman
Sent: Wednesday, September 13, 2017 12:48 PM
To: mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] Windows 10 1703 breaking auto log on when updates are 
being applied

I have no idea how to find what version of ADK/MDT im using but the date on the 
folder is 06/14/2016

Anyway… I have no problems with 1703 and autologon.  Here is my CS

[Settings]
Priority=Default
Properties=MyCustomProperty

[Default]
_SMSTSORGNAME=Coilcraft
UserDataLocation=NONE
DoCapture=YES
OSInstall=Y
AdminPassword=***
TimeZoneName=Central Standard Time
JoinWorkgroup=WORKGROUP
HideShell=NO
FinishAction=RESTART
DoNotCreateExtraPartition=YES
;WSUSServer=http://wsus01-vm:8530
ApplyGPOPack=NO

SkipAdminPassword=YES
SkipProductKey=YES
SkipComputerName=NO
SkipDomainMembership=YES
SkipComputerBackup=NO
SkipUserData=YES
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=YES
SkipBitLocker=YES
SkipSummary=YES
SkipRoles=YES
SkipCapture=NO
SkipFinalSummary=YES

;JoinDomain=***
;DomainAdmin=***
;DomainAdminDomain=***
;DomainAdminPassword=***
MachineObjectOU=OU=MDT,DC=***,DC=com
SLSShare=\\WDS01-VM\W10dev$\Logs\
SLShareDynamicLogging=\\WDS01-VM\W10dev$\Logs\%OSDComputerName%

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Britney Gibbs
Sent: Wednesday, September 13, 2017 11:16 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: Re: [MDT-OSD] Windows 10 1703 breaking auto log on when updates are 
being applied

We are using Win10 Version 1703 on ADK/MDT Version 8443 on Server 2012 R2. Our 
CustomSettings.ini file is the original one that came with it other than a few 
modifications, but mostly pretty simple. We've tried the AdminPassword=Password 
and the SkipAdminPassword=YES. but I'm thinking that it never worked. Hard to 
tell.

Thank you,

Britney R. Gibbs

On Wed, Sep 13, 2017 at 11:51 AM, Jimmy Martin 
<jimmy.mar...@bmhcc.org<mailto:jimmy.mar...@bmhcc.org>> wrote:
Out of curiosity, what ver is your site? and are you using an old 
customsettings or is it a new one?


Jimmy Martin
(901) 227-8209<tel:(901)%20227-8209>
From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Britney Gibbs
Sent: Wednesday, September 13, 2017 10:41 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: Re: [MDT-OSD] Windows 10 1703 breaking auto log on when updates are 
being applied

I'm having this same issue. Even though they said that the last Cumulative 
Security Update fixed it. Bad part about it for me is that if it doesn't 
AutoLogon, it won't finish the Task Sequence unless I go to C: and run the 
LiteTouch file there, then restart the PC, but it's not consistent. What 
happens if you move the "Apply Updates" portion to the State Restore part of 
the Task Sequence (if that's possible)?

Thank you,

Britney R. Gibbs

On Tue, Sep 12, 2017 at 4:47 PM, David Landry 
<david.lan...@lairdtech.com<mailto:david.lan...@lairdtech.com>> wrote:
Hi All,

Anyone seen this?

Windows 10 1703 64bit is no longer auto logging back in once it boots up to the 
desktop and starts installing apps. Where I really see this is when Windows 
updates runs. It can take up to 8 passes and it has always auto logged back in 
after each pass. We have no issues with Windows 7 or Windows 10 1607.

I have a work around by adding AdminPassword= to the CustomSettings.ini file. I 
am hoping someone else has found the root cause with a fix?

Thanks in advance

[MDT-OSD] Windows 10 1703 breaking auto log on when updates are being applied

[David Landry]

Hi All,

Anyone seen this?

Windows 10 1703 64bit is no longer auto logging back in once it boots up to the 
desktop and starts installing apps. Where I really see this is when Windows 
updates runs. It can take up to 8 passes and it has always auto logged back in 
after each pass. We have no issues with Windows 7 or Windows 10 1607.

I have a work around by adding AdminPassword= to the CustomSettings.ini file. I 
am hoping someone else has found the root cause with a fix?

Thanks in advance..

Dave Landry

[MDT-OSD] RE: Multiple Domains MDT

[David Landry]

I assume you will need a domain admin level account that goes across all 
domains.

I do this in the CustomSettings.ini:

OSDComputerName=-%SerialNumber%
JoinDomain= 
DomainOUs1=OU=Laptops,OU=,OU=North America,DC=,DC=,DC=com
DomainOUs2=OU=Desktops,OU=,OU=North America,DC=,DC=,DC=com
DomainOUs3=OU=Laptops,OU=,OU=North America,DC=,DC=,DC=com
DomainOUs4=OU=Desktops,OU=,OU=North America,DC=,DC=,DC=com
TimeZone=040
TimeZoneName=Eastern Standard Time

This above gives you a drop down list in the wizard to select the OU you want 
to put the computer in.
-
I found this regarding a list of domains but have not tried it:

https://social.technet.microsoft.com/Forums/en-US/7dded5fe-c697-4cf7-b6ae-51397fa66793/option-to-choose-from-multiple-domains-not-ous-in-domainmembership-using-mdt?forum=mdt

There may be some tweaking needed on the top suggestion or it may not work for 
you at all. But it something you can try. I am also setting the computer name, 
and time zone. Obviously these settings would change depending on where the 
local MDT server resides.

Good luck.


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Marable, Mike
Sent: Wednesday, August 30, 2017 12:03 PM
To: mdtosd@lists.myitforum.com
Subject: [MDT-OSD] RE: Multiple Domains MDT

I’ve never done this, but I think that you could do this if you change these 
variables:

JoinDomain=sub1.domain.com
DomainAdmin=Administrator
DomainAdminDomain=sub1.domain.com
DomainAdminPassword=P@ssw0rd

If they are built onsite then you could use something like the gateway address 
to automatically select the proper values in the CS.ini.

If they are being built in a central location that won’t work of course.  In 
that case you could probably use something like UI++ to put up a prompt at the 
beginning of the task sequence for the build tech to select the destination 
domain.

Or if there was something in the computer name that you could key off of you 
could automate it that way (i.e. SUB1PC001, SUB2PC001, etc.).

In theory it should work.

Mike


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Sean Chapman
Sent: Wednesday, August 30, 2017 11:13 AM
To: mdtosd@lists.myitforum.com
Subject: [MDT-OSD] RE: Multiple Domains MDT

☹

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Sean Chapman
Sent: Thursday, August 24, 2017 3:09 PM
To: mdtosd@lists.myitforum.com
Subject: [MDT-OSD] Multiple Domains MDT

So I need to add the option to join different sub-domains and Im having trouble 
coming up with a good solution.  We have different plants with domain.com, 
sub1.domain.com, sub2.domain.com etc and we build all the PCs here at 
domain.com and ship them out.

I have seen plenty about DomainOUlist.xml but there is only 1 OU in each Domain 
I want these going into and it seems that the xml is only for selecting 
multiple OUs.  I even tried it with multiple domains but it just put in the 
first one listed.

I tried to put in multiple entries in the CS.ini but it just chose the first 
one.

I can create multiple TS’s I suppose.

I saw Johan mention use webservices but I don’t have that set up and it seems 
too advanced for me to get going as MDT is not my full time job, its just 1 
task of way too many I have.

Thanks in advance








The information contained in this communication and all accompanying documents 
from Coilcraft may be confidential and/or legally privileged, and is intended 
only for the use of the recipient(s) named above. If you are not the intended 
recipient you are hereby notified that any review, disclosure, copying, 
distribution or the taking of any action in reliance on the contents of this 
transmitted information is strictly prohibited. If you have received this 
communication in error, please return it to the sender immediately and destroy 
the original message or accompanying materials and any copy thereof. If you 
have any questions concerning this message, please contact the sender.

**
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues

RE: [MDT-OSD] RE: Missing Dell Drivers

[David Landry]

DCU also updates the BIOS. I have been told, but I have not confirmed, that a 
change in the BIOS will cause you to put in the key.

One of the guys on our security team told me this. I have not have the time to 
verify on a test machine. Our company have not “officially” started using 
bitlocker.


Best Regards,

Dave Landry
Site Support Administrator
Laird Technologies
1 Perimeter Road – Suite 700
Manchester, NH 03103
+1 603-935-7857
[Description: LairdLogo]


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Katherine M. Moss
Sent: Tuesday, August 1, 2017 12:35 PM
To: mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: Missing Dell Drivers

That’s what I was trying to understand; why Bitlocker was even mentioned.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Keith Garner
Sent: Tuesday, August 01, 2017 12:11 PM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: RE: [MDT-OSD] RE: Missing Dell Drivers

Wait… what?

What makes DCU incompatible with Bitlocker?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Katherine M. Moss
Sent: Tuesday, August 1, 2017 7:45 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: RE: [MDT-OSD] RE: Missing Dell Drivers

Good to know the caution about Bitlocker. I have a laptop with DCU on it … was 
thinking of putting Bitlocker back on; appears I can’t do that.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry
Sent: Tuesday, August 01, 2017 9:48 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: RE: [MDT-OSD] RE: Missing Dell Drivers

Hi All,

Thanks to all for sharing their solutions to the problem with Dells drivers. 
They all should work just fine.

I didn’t mention this, but the problem I am facing is not just at my site … but 
I also need to find a solution that will fit some 50+ MDT servers on a global 
scale. Drivers has always been a thorn in my side as it seems Dell does in fact 
change hardware on their business class systems on occasion. Then I have to go 
out and download the latest CAB files to get the missing driver(s).

When I spoke to their Tier 3 support, he recommended running Dell Command 
Update as an application which will automatically scan the system, identify the 
model and the hardware in it, then go out and grab the latest CAB file and 
install the missing drivers. Because DCU has this capability, I am thinking of 
only supporting LAN and storage drivers in MDT and then use DCU to finish the 
driver installs. The biggest problem with that is, I need to uninstall it after 
it completes during the MDT process. Leaving DCU on a system, specifically a 
laptop will be problematic when we start bitlocking laptops.

I have only been testing in North America for about a week, so if this works in 
Asia and Europe it will be one solution to fit all. If this doesn’t pan out, 
then I can fall back to the great ideas you guys  have found. FYI: I asked Dell 
if the DCU will download CAB files from that region or come back to the US for 
the drivers. The answer was that DCU is the same application globally. It has 
logic built in to determine the closest source to retrieve the CAB files.

If anyone wants / needs information of how to get DCU to work in MDT just let 
me know.

Thanks for sharing guys.

Best Regards,

Dave Landry



From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stephen Owen
Sent: Friday, July 28, 2017 9:51 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: Re: [MDT-OSD] RE: Missing Dell Drivers

+1 to Arif's recommendation.

I don't import the entire CAB anymore for Dell laptops.  Instead, I unzip it 
and import chipset, audio, storage and LAN, then image and see what else is 
missing.  I only import the missing drivers after that.

I'm not sure what's happening with their CAB files but I've seen this issue as 
well.

On Fri, Jul 28, 2017 at 9:24 AM, Usman, Arif 
<arif.us...@merrillcorp.com<mailto:arif.us...@merrillcorp.com>> wrote:
If you extract cab drivers from dell, remove CV folder under Security folder, 
and import drivers to MDT.
Install controlVault as application driver (Dell_CV_SW_Update_x64_7250.exe /S 
/v/qn)..

Thanks


From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Sean Chapman
Sent: Friday, July 28, 2017 7:40 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>; 
'mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>'
Subjec

RE: [External] RE: [MDT-OSD] RE: Missing Dell Drivers

[David Landry]

Sorry Todd … didn’t see your email. Yes that is what I was told.


Best Regards,

Dave Landry
Site Support Administrator
Laird Technologies
1 Perimeter Road – Suite 700
Manchester, NH 03103
+1 603-935-7857
[Description: LairdLogo]


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Miller, Todd
Sent: Tuesday, August 1, 2017 5:49 PM
To: mdtosd@lists.myitforum.com
Subject: RE: [External] RE: [MDT-OSD] RE: Missing Dell Drivers

My guess is that DCU might update the BIOS of a computer without putting 
Bitlocker into standby first and that would put the Bitlocker into recovery 
mode.  Just a guess.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Keith Garner
Sent: Tuesday, August 01, 2017 11:11 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: [External] RE: [MDT-OSD] RE: Missing Dell Drivers

Wait… what?

What makes DCU incompatible with Bitlocker?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Katherine M. Moss
Sent: Tuesday, August 1, 2017 7:45 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: RE: [MDT-OSD] RE: Missing Dell Drivers

Good to know the caution about Bitlocker. I have a laptop with DCU on it … was 
thinking of putting Bitlocker back on; appears I can’t do that.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry
Sent: Tuesday, August 01, 2017 9:48 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: RE: [MDT-OSD] RE: Missing Dell Drivers

Hi All,

Thanks to all for sharing their solutions to the problem with Dells drivers. 
They all should work just fine.

I didn’t mention this, but the problem I am facing is not just at my site … but 
I also need to find a solution that will fit some 50+ MDT servers on a global 
scale. Drivers has always been a thorn in my side as it seems Dell does in fact 
change hardware on their business class systems on occasion. Then I have to go 
out and download the latest CAB files to get the missing driver(s).

When I spoke to their Tier 3 support, he recommended running Dell Command 
Update as an application which will automatically scan the system, identify the 
model and the hardware in it, then go out and grab the latest CAB file and 
install the missing drivers. Because DCU has this capability, I am thinking of 
only supporting LAN and storage drivers in MDT and then use DCU to finish the 
driver installs. The biggest problem with that is, I need to uninstall it after 
it completes during the MDT process. Leaving DCU on a system, specifically a 
laptop will be problematic when we start bitlocking laptops.

I have only been testing in North America for about a week, so if this works in 
Asia and Europe it will be one solution to fit all. If this doesn’t pan out, 
then I can fall back to the great ideas you guys  have found. FYI: I asked Dell 
if the DCU will download CAB files from that region or come back to the US for 
the drivers. The answer was that DCU is the same application globally. It has 
logic built in to determine the closest source to retrieve the CAB files.

If anyone wants / needs information of how to get DCU to work in MDT just let 
me know.

Thanks for sharing guys.

Best Regards,

Dave Landry



From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stephen Owen
Sent: Friday, July 28, 2017 9:51 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: Re: [MDT-OSD] RE: Missing Dell Drivers

+1 to Arif's recommendation.

I don't import the entire CAB anymore for Dell laptops.  Instead, I unzip it 
and import chipset, audio, storage and LAN, then image and see what else is 
missing.  I only import the missing drivers after that.

I'm not sure what's happening with their CAB files but I've seen this issue as 
well.

On Fri, Jul 28, 2017 at 9:24 AM, Usman, Arif 
<arif.us...@merrillcorp.com<mailto:arif.us...@merrillcorp.com>> wrote:
If you extract cab drivers from dell, remove CV folder under Security folder, 
and import drivers to MDT.
Install controlVault as application driver (Dell_CV_SW_Update_x64_7250.exe /S 
/v/qn)..

Thanks


From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Sean Chapman
Sent: Friday, July 28, 2017 7:40 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>; 
'mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>'
Subject: [MDT-OSD] RE: Missing Dell Drivers

I have 7480s that deploy fine with MDT.  I do not use the control vault dr

RE: [External] RE: [MDT-OSD] RE: Missing Dell Drivers

[David Landry]

Hi All,

Yes DCU does update the BIOS also.

http://en.community.dell.com/techcenter/enterprise-client/w/wiki/7534.dell-command-update


Best Regards,

Dave Landry
Site Support Administrator
Laird Technologies
1 Perimeter Road – Suite 700
Manchester, NH 03103
+1 603-935-7857
[Description: LairdLogo]


From: David Landry
Sent: Wednesday, August 2, 2017 8:21 AM
To: mdtosd@lists.myitforum.com
Subject: RE: [External] RE: [MDT-OSD] RE: Missing Dell Drivers

Sorry Todd … didn’t see your email. Yes that is what I was told.


Best Regards,

Dave Landry
Site Support Administrator
Laird Technologies
1 Perimeter Road – Suite 700
Manchester, NH 03103
+1 603-935-7857
[Description: LairdLogo]


From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Miller, Todd
Sent: Tuesday, August 1, 2017 5:49 PM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: RE: [External] RE: [MDT-OSD] RE: Missing Dell Drivers

My guess is that DCU might update the BIOS of a computer without putting 
Bitlocker into standby first and that would put the Bitlocker into recovery 
mode.  Just a guess.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Keith Garner
Sent: Tuesday, August 01, 2017 11:11 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: [External] RE: [MDT-OSD] RE: Missing Dell Drivers

Wait… what?

What makes DCU incompatible with Bitlocker?

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Katherine M. Moss
Sent: Tuesday, August 1, 2017 7:45 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: RE: [MDT-OSD] RE: Missing Dell Drivers

Good to know the caution about Bitlocker. I have a laptop with DCU on it … was 
thinking of putting Bitlocker back on; appears I can’t do that.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry
Sent: Tuesday, August 01, 2017 9:48 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: RE: [MDT-OSD] RE: Missing Dell Drivers

Hi All,

Thanks to all for sharing their solutions to the problem with Dells drivers. 
They all should work just fine.

I didn’t mention this, but the problem I am facing is not just at my site … but 
I also need to find a solution that will fit some 50+ MDT servers on a global 
scale. Drivers has always been a thorn in my side as it seems Dell does in fact 
change hardware on their business class systems on occasion. Then I have to go 
out and download the latest CAB files to get the missing driver(s).

When I spoke to their Tier 3 support, he recommended running Dell Command 
Update as an application which will automatically scan the system, identify the 
model and the hardware in it, then go out and grab the latest CAB file and 
install the missing drivers. Because DCU has this capability, I am thinking of 
only supporting LAN and storage drivers in MDT and then use DCU to finish the 
driver installs. The biggest problem with that is, I need to uninstall it after 
it completes during the MDT process. Leaving DCU on a system, specifically a 
laptop will be problematic when we start bitlocking laptops.

I have only been testing in North America for about a week, so if this works in 
Asia and Europe it will be one solution to fit all. If this doesn’t pan out, 
then I can fall back to the great ideas you guys  have found. FYI: I asked Dell 
if the DCU will download CAB files from that region or come back to the US for 
the drivers. The answer was that DCU is the same application globally. It has 
logic built in to determine the closest source to retrieve the CAB files.

If anyone wants / needs information of how to get DCU to work in MDT just let 
me know.

Thanks for sharing guys.

Best Regards,

Dave Landry



From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Stephen Owen
Sent: Friday, July 28, 2017 9:51 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: Re: [MDT-OSD] RE: Missing Dell Drivers

+1 to Arif's recommendation.

I don't import the entire CAB anymore for Dell laptops.  Instead, I unzip it 
and import chipset, audio, storage and LAN, then image and see what else is 
missing.  I only import the missing drivers after that.

I'm not sure what's happening with their CAB files but I've seen this issue as 
well.

On Fri, Jul 28, 2017 at 9:24 AM, Usman, Arif 
<arif.us...@merrillcorp.com<mailto:arif.us...@merrillcorp.com>> wrote:
If you extract cab drivers from dell, remove CV folder under Security folder, 
and import drivers to MDT.
Install controlVault as application dri

[MDT-OSD] Missing Dell Drivers

[David Landry]

Hi All,

Just curious what everyone / anyone has done with the Dell driver problem they 
have with the new Latitude XX80 series laptops. I imported their CAB files into 
MDT and got error. Didn't know how bad so I imaged a 7280 or 5480 and lots of 
stuff came up missing. I called Dell and they informed me that they are having 
problems with drivers not importing into MDT and then everything after that 
fails to import. Control Vault drivers was the worst. But each model is 
different.

They recommended using Dell Command Update. So I got that into MDT and it runs 
first.. but I am still missing touchpad drivers for the 5480, and who knows 
what else I haven't discovered yet.

They actually pulled all their Windows 7 and Windows 10 drivers off their 
website a few weeks ago. I thought a server went down ... but it wasn't the 
server.

Has anyone else seen the driver issues at Dell? What is everyone else doing to 
resolve this?

Best Regards,

Dave Landry

[MDT-OSD] RE: Best methods to replicate MDT content

[David Landry]

Thank you to all that has responded.

If anyone else has anything to add or if some uses a method that has not been 
discussed, please feel free to add to the discussion.

Lots of good information and food for thought.

BR,

Dave L.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Wilson, J Kevin
Sent: Tuesday, November 15, 2016 1:17 PM
To: mdtosd@lists.myitforum.com
Subject: [MDT-OSD] RE: Best methods to replicate MDT content

I have used DFS-R for replication of WDS boot images. Used one-way replication, 
and replication only pushes the differential. DFS-R also makes the equivalent 
of a "combined" WIM (e.g. multi-WIM) for you - single instance storage - data 
is unified in one .RWM file. It offers MS supported replication and lots of 
consoles and logs to monitor things.

Not sure about options for unique downstream files.

Kevin Wilson

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of ODONNELL Aaron M
Sent: Monday, November 14, 2016 4:27 PM
To: 'mdtosd@lists.myitforum.com' 
<mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>>
Subject: [MDT-OSD] RE: Best methods to replicate MDT content



*** Exercise caution. This is an EXTERNAL email. DO NOT open attachments or 
click links from unknown senders or unexpected email. ***
DFS sounds like it would probably be the best solution for something that 
scale.. We have a primary MDT distribution point and 5 remote Linked Deployment 
Shares, and I recently started using powershell with scheduled tasks to 
automate things. The downside is there's no log to see if something failed but 
that hasn't been an issue (yet).

Here is the powershell script I use to start a linked deployment share copy to 
one of those sites. I just copied it from the output from the "View script" 
button in the status window after manually updating a linked deployment share. 
The "DS905" is based on part of our server naming convention. I think it starts 
at DS001 if you just use MDT's powershell output verbatim, but I changed it so 
each powershell script (I have one script per configured linked deployment 
share) would have a unique DS identifier so the multiple scripts could run at 
once.

Import-Module "C:\Program Files\Microsoft Deployment 
Toolkit\bin\MicrosoftDeploymentToolkit.psd1"
New-PSDrive -Name "DS905" -PSProvider MDTProvider -Root "D:\MDT Deployment 
Shares\Production"
Update-MDTLinkedDS -path "DS905:\Linked Deployment Shares\LINKED005" -Verbose





Thanks,

Aaron O'Donnell

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry
Sent: Monday, November 14, 2016 1:00 PM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: [MDT-OSD] Best methods to replicate MDT content

Hi All,

I need to automate replication across 3 different regional MDT servers located 
in three different regions of the world and then down to 47+/- local MDT 
servers at various sites scattered among the three regions. The flow of data 
needs to be one way, all downstream. Nothing can go upstream. Nor do I want to 
delete files on downstream MDT servers that may be specific to that particular 
site.

I am partial to DFS but am getting substantial pushback from a manager in 
another department in IT.

Before I set up a test environment to prove DFS is the best method, I am 
curious as to what everyone else uses with their pros and cons. Replicating 
through Linked Deployment shares is not cutting it at this point  I need to 
automate it.

Thanks in advance.

Best Regards,

Dave

[MDT-OSD] Best methods to replicate MDT content

[David Landry]

Hi All,

I need to automate replication across 3 different regional MDT servers located 
in three different regions of the world and then down to 47+/- local MDT 
servers at various sites scattered among the three regions. The flow of data 
needs to be one way, all downstream. Nothing can go upstream. Nor do I want to 
delete files on downstream MDT servers that may be specific to that particular 
site.

I am partial to DFS but am getting substantial pushback from a manager in 
another department in IT.

Before I set up a test environment to prove DFS is the best method, I am 
curious as to what everyone else uses with their pros and cons. Replicating 
through Linked Deployment shares is not cutting it at this point  I need to 
automate it.

Thanks in advance.

Best Regards,

Dave

RE: [MDT-OSD] UEFI Booting USB

[David Landry]

What I did was:

BIOS Settings:
Changed to UEFI and RAID ON – Secure Boot is off and Enable Legacy Options ROMs 
is checked.

USB Stick:
Must be formatted FAT32.
Only copy these Windows 10 64bit files and folders to the USB stick:
Bootmdr
Bootmgr.efi
Boot folder
Efi folder
Create a “Sources” folder – leave it empty for now.

Copy the LiteTouch_64.wim to the “sources” folder and rename it Boot.wim

I have heard you need a USB 3.0 port and stick, but have not confirmed this.

Plug it into your machine
Press F12 to get a boot menu
Select the UEFI USB Stick.


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Joshua Delaughter
Sent: Tuesday, May 31, 2016 4:57 PM
To: mdtosd@lists.myitforum.com
Subject: Re: [MDT-OSD] UEFI Booting USB

I do the BIOS update steps once Windows is installed, in the install 
applications area, and they seem to work fine

Sent from my iPhone

On May 31, 2016, at 2:05 PM, Miller, Todd 
> wrote:
The Dell BIOS utilities have 64bit versions - CCTK and the newer PowerShell 
stuff.  I guess you mean the BIOS firmware update which is 32bit only.  No 
getting around It – it just sucks.

I switched over to using 64bit WinPE boot disks and I now no longer apply BIOS 
updates as part of computer deployment.  Desktop staff have to work on that 
manually now.  The only time is it really trouble is on models where the OSD 
will fail unless the firmware is updated.  That is a catch-22.

Six years ago, there was apparently some work being done at Dell to make 64bit 
compatible BIOS flash utilities, but I don’t think anything ever came of it… 
http://en.community.dell.com/techcenter/systems-management/f/4469/t/19414825




From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marcum, John
Sent: Tuesday, May 31, 2016 8:03 AM
To: mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] UEFI Booting USB

So how are people getting around the limitation that the Dell bios utility only 
runs on x86 PE?

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Niall Brady
Sent: Thursday, May 26, 2016 2:19 PM
To: mdtosd@lists.myitforum.com
Subject: Re: [MDT-OSD] UEFI Booting USB

UEFI requires that the boot image architecture matches the architecture of the 
device, so are any of these tablets x86 instead of x64

On Thu, May 26, 2016 at 9:00 PM, D R 
> wrote:
and you set the BIOS so that the USB is the first boot device?

Leave the USB stick in the device and see if the tablet 'sees' the USB stick. 
If the BIOS reports it as bootable device set it as the first bootable. It 
should boot.

I had the same issue with my laptop. As soon as I left the USB Stick in my 
laptop and had the BIOS 'see' it as a bootable device I configured the BIOS so 
that it was the first bootable device.

Daniel

On Thu, May 26, 2016 at 1:48 PM, Wood, Sandy 
> wrote:
I’ve been routinely booting to USB and deploying systems with Media that has 
this file structure


Now, we’ve got some new HP tablets that I’m trying to boot UEFI. The tablets 
recognize the USB stick but won’t boot to the USB. Do I need to include a 
LiteTouchMedia.iso to my USB to get it to boot?

Sandy Wood
Network Engineer
Orange County District Attorney
(714) 347-8775




CONFIDENTIALITY NOTICE: This communication with its contents may contain 
confidential and/or legally privileged information. It is solely for the use of 
the intended recipient(s). Unauthorized interception, review, use or disclosure 
is prohibited and may violate applicable laws including the Electronic 
Communications Privacy Act. If you are not the intended recipient, please 
contact the sender and destroy all copies of the communication.



--
Daniel Rodriguez
drod...@gmail.com




Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.


Notice: This UI Health Care e-mail (including attachments) is covered by the 
Electronic Communications Privacy Act, 18 U.S.C. 2510-2521 and is intended only 
for the use of the individual or entity to which it is addressed, and may 
contain information that is privileged, confidential, and exempt from 
disclosure under applicable law. If you are not the intended recipient, any 
dissemination, distribution or copying of this communication is strictly 
prohibited. If you have received this communication in 

RE: [MDT-OSD] Customsettings.ini vs task sequence variables

[David Landry]

Sorry it took so long to get back to you.

If you want to have the machines auto assign to the computers OU, just leave 
the 2 DomainOU lines out.





From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Wilcox, Kyle
Sent: Tuesday, May 24, 2016 2:12 PM
To: mdtosd@lists.myitforum.com
Subject: Re: [MDT-OSD] Customsettings.ini vs task sequence variables

Ok, I know I am getting of on a tangent here, but I see different OUs below. 
Our AD guy has requested that computers join the default computers container.  
When I put MachineObjectOU=CN=Computers,DC=DomainName,DC=local I get an error 
stating that it cannot start with CN.  How can I get computers to just go to 
the default computers container?

-Kyle

On Tue, May 24, 2016 at 11:09 AM, David Landry 
<david.lan...@lairdtech.com<mailto:david.lan...@lairdtech.com>> wrote:
You can add these settings to your CS.ini file:

OSDComputerName=-%SerialNumber%
JoinDomain= 
DomainOUs1=OU=Laptops,OU=,OU=North 
America,DC=,DC=,DC=com
DomainOUs2=OU=Desktops,OU=,OU=North 
America,DC=,DC=,DC=com
TimeZone=035
TimeZoneName=Eastern Standard Time
Home_page= http://<whatever<http://%3cwhatever> you want>


List of time zones: http://unattended.sourceforge.net/timezones.php

These settings will auto configure your Deployment Wizard.

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Marable, Mike
Sent: Tuesday, May 24, 2016 6:29 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: Re: [MDT-OSD] Customsettings.ini vs task sequence variables

If I remember correctly, once a variable has been set you cannot change it.  
So, if you have conflicting values (I believe) that the first one set is the 
winner.

Were are you instructing MDT to join the computer to the domain?  Is it through 
the GUI with the wizard, or elsewhere?

What exactly do you have in the BootStrap.ini?  There should only be a minimum 
of values set in that file, basically only what is needed to get the process 
started.  Once the MDT wizard CustomSettings.ini takes over.  Between the two, 
BootStrap is very minimal while CustomSettings does the heavy lifting.

Mike

From: <listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>> 
on behalf of "Wilcox, Kyle" 
<wilc...@wws.k12.in.us<mailto:wilc...@wws.k12.in.us>>
Reply-To: "mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>" 
<mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>>
Date: Monday, May 23, 2016 at 11:52 PM
To: "mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>" 
<mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>>
Subject: RE: [MDT-OSD] Customsettings.ini vs task sequence variables


How can I determine whether a custom setting or a ts variable will have 
precedence?

Also, do any settings from bootstrap.ini carryover to either of these two?

I am using a local account in bootstrap.ini to access the deployment share and 
the variable of workgroup is set.

However I am trying to have the computer join the domain and I see in the log 
file that the join domain setting keeps getting changed back to workgroup. I am 
wondering if this could be coming from the bootstrap.ini?

-Kyle
On May 22, 2016 9:55 AM, "Phil Schwan" 
<psch...@projectleadership.net<mailto:psch...@projectleadership.net>> wrote:
The CS.ini file provides a set of extra rules for the Gather (ZTIGather.wsf) 
function to process.  This can include things like connecting to databases or 
providing logic around creating/combining new values.  ZTIGather ultimately 
ends up creating or modifying a number of Task Sequence variables that the TS 
can use throughout execution.  If you look at the ZTIGather.log file (or the 
section of smsts.log where it executes), you’ll see the variables being set in 
the TS environment.

-Phil
_
Phil Schwan | Technical Architect, Enterprise Windows Services
Microsoft VTSP (b-phs...@microsoft.com<mailto:b-phs...@microsoft.com>)
Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 
48075
Lync: 312.756.1626  Mobile: 419.262.5133
www.projectleadership.net<http://www.projectleadership.net/> 
[inkedin_logo-19x20] <http://www.linkedin.com/in/philschwan> 
[witter-Logo1-20x20] <https://twitter.com/philschwan>  [ordpress-logo3] 
<http://lab-geek.com/>
[escription: Description: Description: Arrow email]Lead with Strategy. Leverage 
Technology. Deliver Results.



From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Wilcox, Kyle
Sent: Sunday, May 22,

RE: [MDT-OSD] Customsettings.ini vs task sequence variables

[David Landry]

You can add these settings to your CS.ini file:

OSDComputerName=-%SerialNumber%
JoinDomain= 
DomainOUs1=OU=Laptops,OU=,OU=North 
America,DC=,DC=,DC=com
DomainOUs2=OU=Desktops,OU=,OU=North 
America,DC=,DC=,DC=com
TimeZone=035
TimeZoneName=Eastern Standard Time
Home_page= http://


List of time zones: http://unattended.sourceforge.net/timezones.php

These settings will auto configure your Deployment Wizard.

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Marable, Mike
Sent: Tuesday, May 24, 2016 6:29 AM
To: mdtosd@lists.myitforum.com
Subject: Re: [MDT-OSD] Customsettings.ini vs task sequence variables

If I remember correctly, once a variable has been set you cannot change it.  
So, if you have conflicting values (I believe) that the first one set is the 
winner.

Were are you instructing MDT to join the computer to the domain?  Is it through 
the GUI with the wizard, or elsewhere?

What exactly do you have in the BootStrap.ini?  There should only be a minimum 
of values set in that file, basically only what is needed to get the process 
started.  Once the MDT wizard CustomSettings.ini takes over.  Between the two, 
BootStrap is very minimal while CustomSettings does the heavy lifting.

Mike

From: > 
on behalf of "Wilcox, Kyle" 
>
Reply-To: "mdtosd@lists.myitforum.com" 
>
Date: Monday, May 23, 2016 at 11:52 PM
To: "mdtosd@lists.myitforum.com" 
>
Subject: RE: [MDT-OSD] Customsettings.ini vs task sequence variables


How can I determine whether a custom setting or a ts variable will have 
precedence?

Also, do any settings from bootstrap.ini carryover to either of these two?

I am using a local account in bootstrap.ini to access the deployment share and 
the variable of workgroup is set.

However I am trying to have the computer join the domain and I see in the log 
file that the join domain setting keeps getting changed back to workgroup. I am 
wondering if this could be coming from the bootstrap.ini?

-Kyle
On May 22, 2016 9:55 AM, "Phil Schwan" 
> wrote:
The CS.ini file provides a set of extra rules for the Gather (ZTIGather.wsf) 
function to process.  This can include things like connecting to databases or 
providing logic around creating/combining new values.  ZTIGather ultimately 
ends up creating or modifying a number of Task Sequence variables that the TS 
can use throughout execution.  If you look at the ZTIGather.log file (or the 
section of smsts.log where it executes), you’ll see the variables being set in 
the TS environment.

-Phil
_
Phil Schwan | Technical Architect, Enterprise Windows Services
Microsoft VTSP (b-phs...@microsoft.com)
Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 
48075
Lync: 312.756.1626  Mobile: 419.262.5133
www.projectleadership.net 
[inkedin_logo-19x20]  
[witter-Logo1-20x20]   [ordpress-logo3] 

[escription: Description: Description: Arrow email]Lead with Strategy. Leverage 
Technology. Deliver Results.



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] 
On Behalf Of Wilcox, Kyle
Sent: Sunday, May 22, 2016 8:57 AM
To: mdtosd@lists.myitforum.com
Subject: [MDT-OSD] Customsettings.ini vs task sequence variables


What is the difference between customsettings.ini and task sequence variables

I have been using customsettings.ini for over a year now but never really had 
any idea what a task sequence variable was.

As I learn more they seem to be the same. Pros and cons?

-Kyle

**
Electronic Mail is not secure, may not be read every day, and should not be 
used for urgent or sensitive issues

RE: [MDT-OSD] Problem installing updates post install via MDT

[David Landry]

Thanks Erik,

I did the WSUS Cleanup Wizard. But I did not do the rest of what is in the link 
you sent. I will give that a shot.

Thanks you.

Best Regards,

Dave Landry
Site Support Administrator
Laird Technologies
1 Perimeter Road – Suite 700
Manchester, NH 03103
+1 603-935-7857
[Description: LairdLogo]


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of the codepoets
Sent: Thursday, May 12, 2016 12:42 PM
To: mdtosd@lists.myitforum.com
Subject: Re: [MDT-OSD] Problem installing updates post install via MDT

I would second that this is probably a WSUS issue. It sounds like you're seeing 
WSUS issues across the board, and you've verified the taking WSUS out of the 
loop resolves the issues. It might be beneficial to look at the following and 
take this in as a WSUS issue...

https://blogs.technet.microsoft.com/configurationmgr/2016/01/26/the-complete-guide-to-microsoft-wsus-and-configuration-manager-sup-maintenance/

I was able to resolve a lot of issues we had crop up with WSUS a few months ago 
by doing the maintenance in that blog post.

-erik

On Thu, May 12, 2016 at 8:22 AM, Keith Garner (Hotmail) 
<keith.gar...@hotmail.com<mailto:keith.gar...@hotmail.com>> wrote:
First off, the logs don’t match here. Hard to debug.

ZTIWindowsUpdate.log has a query between

Start Search...ZTIWindowsUpdate4/28/2016 12:04:31 PM 0 (0x)
Timeout Error WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS : Retry! 
(-2145107952<tel:%28-2145107952>)ZTIWindowsUpdate   
 4/28/2016 12:06:03 PM 0 (0x)

However I WIndowsUpdate2.log and WindowsUpdate3.log appear to be outside of the 
ZTIWindowsUpdate.log in time stamp.

A quick glance at the other logs don’t reveal anything.

I’m not a WSUS expert by any means, but my first thoughts are that you might 
have some kind of server corruption.

-k

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of David Landry
Sent: Thursday, May 12, 2016 6:23 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: [MDT-OSD] Problem installing updates post install via MDT

Hi All,

I have run into a brick wall. For 2 years now, our Windows 7 images (we only 
use Windows 7) updates via MDT installed updates on the first pass. What we 
have been seeing for the last 2-3 weeks is:


-  First pass searches for update and reboots within 2 mins and does 
not install any updates.

-  Second pass searches for update and reboots within 4 mins and does 
not install any updates.

-  The third, fourth, fifth, and sixth passes searches and just hangs 
there before reboots and does not install any updates.

-  The Seventh pass installs about 40 updates.

-  The 8th pass searches for about 2 ½ hours and does not install any 
updates.

-  I have installed Windows6.1-KB3138612-x64.msu, 
Windows6.1-KB3112343-x64.msu, Windows6.1-KB3102810-x64.msu into new test images 
based on articles I have read on the internet. But these have not helped the 
problem.

-  I’ve tested a new wim that had the contents of 
C:\Windows\SoftwareDistribution cleaned out. That didn’t help.

-  I thought about updating to Update 2 but didn’t see anything that 
would potentially help aside from better logging for the smsts.log file.

-  I have looked at most of the errors in the logs. But have not found 
a resolution that works.

-  I have included some logs from the testing I have been doing.



-  If I bypass the WSUS server and go directly to Microsoft for updates 
via MDT, updates start installing on the first pass.

-  I created a new image with all the updates in it and that did not 
error out, but instead reported back there were no updates available.

WU client versions during testing:7.6.7601.19016

7.6.7601.19077

7.6.7601.19161

MDT 2013 update 1 version:6.3.8298.1000

The entire process, imaging, drivers, all applications, and all updates used to 
take about 2 hours to complete. Now due to the update problem, it is taking 6+ 
hours per machine.

This is not just happening on my local MDT server, but from what I am hearing, 
it is occurring on all MDT servers corporate wide.

At this point I am leaning to either a WSUS problem of some kind such as Client 
version issue or a bad update as the culprit.

Anyone seen this before? Any ideas?

Best Regards,

Dave Landry

[MDT-OSD] Dynamic Platform Thermal Framework Driver and Control Vault driver issues

[David Landry]

Good Afternoon,

We just got in a new Dell E7450 in. After injecting the E7450 Dell driver CAB 
file into a folder named Latitude E7450, the laptop gets stuck in a 
continuous reboot loop after the OS is installed and configuring the drivers. 
There is no getting out of it. I identified the above DPTF driver as the 
problem.

Also the control vault drivers are injected but not getting installed.

Anyone imaging E7450 yet? Anyone seen either of these two issues?

Regards,

Dave Landry

RE: [MDT-OSD] WDS getting corrupt

[David Landry]

Thanks for the feedback Chris.

No one should have been accessing WDS at the time we updated WDS with the new 
boot WIMs. I was working with the site administrator helping him add an older 
model laptop (a Lenovo)  to MDT so he can image it. It would not load the WinPE 
boot image. It gave a TFTP time out error. I have seen this twice before. When 
I went to remove the WDS server and then re-add it, that is when I got the 
windows Deployment Service is corrupt message.

I have searched the internet and found lots of documents, blogs, and videos on 
what to do, but quite frankly, a lot of them seem incomplete or they contradict 
each other. Which brings me to you guys and gals.

So if I am understanding this right,  I am doing this correctly and not missing 
a step?

Thanks in advance,

Dave Landry

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Chris Catlett
Sent: Tuesday, February 17, 2015 7:08 PM
To: mdtosd@lists.myitforum.com
Subject: Re: [MDT-OSD] WDS getting corrupt

if someone was booting to that wim during the replace, it could do bad things.


Hi Everyone,

I am new to administrating to MDT and have encountered a problem 3 times. I am 
curious if I am doing something wrong.

The problem is, is when I add drivers to the Out-of-Box Drivers folder, WinPE, 
I update the deployment share to generate new boot WIMS.

I then import then into WDS  ServerBoot folder by choosing the replace option 
for each x86 and x64 wim. I am not shutting the WDS service down … or anything 
else.

I am supporting servers worldwide and on 3 occasions we could no longer boot 
into MDT even though 5 mins earlier we could. I then get an error saying 
Windows Deployment Service is corrupt and I am not able to recover from it even 
after running the commands to uninitialized and initialize the server.

Is this just bad luck or am I not doing something correctly and breaking WDS? I 
am left having to remove WDS from the server, reboot and reinstall WDS to get 
it to work.


Regards,

Dave Landry

[MDT-OSD] WDS getting corrupt

[David Landry]

Hi Everyone,

I am new to administrating to MDT and have encountered a problem 3 times. I am 
curious if I am doing something wrong.

The problem is, is when I add drivers to the Out-of-Box Drivers folder, WinPE, 
I update the deployment share to generate new boot WIMS.

I then import then into WDS  ServerBoot folder by choosing the replace option 
for each x86 and x64 wim. I am not shutting the WDS service down ... or 
anything else.

I am supporting servers worldwide and on 3 occasions we could no longer boot 
into MDT even though 5 mins earlier we could. I then get an error saying 
Windows Deployment Service is corrupt and I am not able to recover from it even 
after running the commands to uninitialized and initialize the server.

Is this just bad luck or am I not doing something correctly and breaking WDS? I 
am left having to remove WDS from the server, reboot and reinstall WDS to get 
it to work.


Regards,

Dave Landry

[MDT-OSD] Issues with multi-language Office install

[David Landry]

Hi All,

It appears I have a problem with the multi-language install for Office 2010.


a)  I have copied the Office language pack files to the root of the Office 
install folder.

b)  I have also put Office 2010 SP2 in the updates folder. Below are the 
settings in MDT 2012 for the install.

c)   OS Language pack files are in their own folders under Packages.

Command line on Details tab:
setup.exe /config ProPlus.WW\config.xml



[cid:image002.jpg@01D03AD5.E25A7B10]


Config.xml file:

Configuration Product=ProPlus
  !-- Display Level=full CompletionNotice=yes SuppressModal=no 
AcceptEula=no / --
  !-- Logging Type=standard Path=%temp% Template=Microsoft Office 
Professional Plus Setup(*).txt / --
  !-- USERNAME Value=Customer / --
  !-- COMPANYNAME Value=MyCompany / --
  !-- INSTALLLOCATION Value=%programfiles%\Microsoft Office / --
  !-- LIS CACHEACTION=CacheOnly / --
  !-- LIS SOURCELIST=\\server1\share\Office;\\server2\share\Office / --
  !-- DistributionPoint Location=\\server\share\Office / --
  !-- OptionState Id=OptionID State=absent Children=force / --
  !-- Setting Id=SETUP_REBOOT Value=IfNeeded / --
  !-- Command Path=%windir%\system32\msiexec.exe Args=/i 
\\server\share\my.msi QuietArg=/q ChainPosition=after Execute=install / 
--
  Display Level=Basic CompletionNotice=No SuppressModal=No 
AcceptEula=Yes /
  COMPANYNAME Value=Laird /
  Setting Id=SETUP_REBOOT Value=Never /
  AddLanguage Id=match /
  AddLanguage Id=cs-cz ShellTransform=Yes /
  AddLanguage Id=de-de /
  AddLanguage Id=en-us /
  AddLanguage Id=sv-se /
/Configuration

Comments from one site are as follows:

For your information, after installing a fresh MDT (German).The following 
settings are in English or Czech:

Internet Explorer English
Office Tools Czech, also if you right clicking an Office file (excel, word) the 
first three options: open, edit, new and print appears in Czech
Windows update page is in English

Comments from another site:

yesterday I  installed a new DELL Latitude E6440 with the W764Bit-2014Q4 image 
from our MDT in Mönchengladbach.
After the installation I got some languages mismatch. The basic installation is 
of course in german, but there some menus in another language which I think 
it`s in czech.

Win7 OS installed in  german with some context menus in czech

Office 2010 installed in german with some submenus in czech like the 
Office-Tools

Internet Explorer 9 installed in English


Can someone tell me if:


A.  I am going it wrong?

B.  Is there a setting, files, or something else I am missing?

C.  I am open to other methods of accomplishing this.


Any help / direction is welcome.

Thank you in advance,


Dave Landry

[MDT-OSD] ideas on automating all the downstream servers updated

[David Landry]

Hi All,

I have been tasked with the overhaul of the MDT server and imaging process for 
my company and have been presented with this question:

How can we automate getting all the downstream servers updated?

We have one master server which also acts as a North American Regional server. 
It also pushes out to one European Regional server and 2 Asian Regional 
servers. The Regional servers then replicate to other sites. A total of about 
42 sites in all.

Does anyone have an automated process? Or does everyone / most MDT admins 
manually replicate?

Thanks in advance,

Dave Landry

[MDT-OSD] Need to install Chinese Traditional in Office 2010

[David Landry]

Hi Everyone,

I have every OS language pack and Office 2010 language pack I need 
. except one - Chinese Traditional (zh-hk) language 
pack for Office 2010.

I cannot find it anywhere  Someone please tell me it does not exist (so I 
know I am not blind). Then, is there a way to get it on there? Should I be 
using zh-tw?

Any and all help is welcome.

Dave Landry

RE: [MDT-OSD] RE: EXTREMELY slow running MDT

[David Landry]

Thank you to all that replied.

What I did was delete all PXE Boot wims from MDT and WDS. I then updated the 
deployment share, and then added the new wims from MDT to WDS. This resolved 
the issue. I am not sure why it did not resolve it the first time .. but at 
this point it is a moot point.

Thanks again to all.



From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Keith Garner (Hotmail)
Sent: Tuesday, November 18, 2014 7:08 PM
To: mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: EXTREMELY slow running MDT

\\xxx\mdtfile:///\\xxx\mdt *is* the DeployRoot Setting in the 
litetouchPE_xxx.wim file on your local MDT server.

GO ahead and update your Boot images on the WDS Server to ensure you are using 
the correct one.

However, I personally recommend using %WDSServer% if you have that defined.
http://www.deployvista.com/Blog/tabid/70/EntryID/35/Default.aspx


From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry
Sent: Tuesday, November 18, 2014 1:04 PM
To: mdtosd@lists.myitforum.commailto:mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: EXTREMELY slow running MDT

Thanks Stephen.

I also found this in the BDD.log:


![LOG[Property DEPLOYROOT is now = 
\\xx\mdt]LOG]!time=11:46:37.000+000file:///\\xx\mdt%5dLOG%5d!%3e%3ctime=%2211:46:37.000+000
 date=11-17-2014 component=ZTIGather context= type=1 thread= 
file=ZTIGather

![LOG[Using from [DEFAULT]: DEPLOYROOT = 
\\xx\mdt]LOG]!time=11:46:37.000+000file:///\\xx\mdt%5dLOG%5d!%3e%3ctime=%2211:46:37.000+000
 date=11-17-2014 component=ZTIGather context= type=1 thread= 
file=ZTIGather

![LOG[-- Done processing X:\Deploy\Scripts\Bootstrap.ini 
--]LOG]!time=11:46:37.000+000 date=11-17-2014 component=ZTIGather 
context= type=1 thread= file=ZTIGather

![LOG[Remapping variables.]LOG]!time=11:46:37.000+000 date=11-17-2014 
component=ZTIGather context= type=1 thread= file=ZTIGather

![LOG[Property TaskSequenceID is now = ]LOG]!time=11:46:37.000+000 
date=11-17-2014 component=ZTIGather context= type=1 thread= 
file=ZTIGather

![LOG[Property DeploymentType is now = 
NEWCOMPUTER]LOG]!time=11:46:37.000+000 date=11-17-2014 
component=ZTIGather context= type=1 thread= file=ZTIGather

![LOG[Finished remapping variables.]LOG]!time=11:46:37.000+000 
date=11-17-2014 component=ZTIGather context= type=1 thread= 
file=ZTIGather

![LOG[ZTIGather processing completed 
successfully.]LOG]!time=11:46:37.000+000 date=11-17-2014 
component=ZTIGather context= type=1 thread= file=ZTIGather

![LOG[Command completed, return code = 0]LOG]!time=11:46:37.000+000 
date=11-17-2014 component=LiteTouch context= type=1 thread= 
file=LiteTouch

![LOG[Run WPEUtil.exe ListKeyboardLayouts 1033]LOG]!time=11:46:38.000+000 
date=11-17-2014 component=Wizard context= type=1 thread= 
file=Wizard

![LOG[Property KeyboardLocalePE is now = 
0409:0409]LOG]!time=11:47:22.000+000 date=11-17-2014 
component=Wizard context= type=1 thread= file=Wizard

![LOG[Property WizardComplete is now = Y]LOG]!time=11:47:22.000+000 
date=11-17-2014 component=Wizard context= type=1 thread= 
file=Wizard

![LOG[Validating connection to 
\\xx\mdt]LOG]!time=11:47:22.000+000file:///\\xx\mdt%5dLOG%5d!%3e%3ctime=%2211:47:22.000+000
 date=11-17-2014 component=LiteTouch context= type=1 thread= 
file=LiteTouch

![LOG[Property NotWizard is now = ]LOG]!time=11:47:28.000+000 
date=11-17-2014 component=Wizard context= type=1 thread= 
file=Wizard

![LOG[Property LeaveShareOpen is now = ]LOG]!time=11:47:28.000+000 
date=11-17-2014 component=Wizard context= type=1 thread= 
file=Wizard

![LOG[Property ValidateAgainstUNCPath is now = 
\\xx\mdt]LOG]!time=11:47:28.000+000file:///\\xx\mdt%5dLOG%5d!%3e%3ctime=%2211:47:28.000+000
 date=11-17-2014 component=Wizard context= type=1 thread= 
file=Wizard

![LOG[Property Definition is now = 
Credentials_ENU.xml]LOG]!time=11:47:28.000+000 date=11-17-2014 
component=Wizard context= type=1 thread= file=Wizard

![LOG[Microsoft Deployment Toolkit version: 
6.1.2373.0]LOG]!time=11:47:28.000+000 date=11-17-2014 component=Wizard 
context= type=1 thread= file=Wizard

![LOG[Not Wizard = True]LOG]!time=11:47:28.000+000 date=11-17-2014 
component=Wizard context= type=1 thread= file=Wizard

![LOG[Property UserCredentials is now = False]LOG]!time=11:47:33.000+000 
date=11-17-2014 component=Wizard context= type=1 thread= 
file=Wizard

![LOG[Validate Against UNC: 
\\xx\mdt]LOG]!time=11:47:33.000+000file:///\\xx\mdt%5dLOG%5d!%3e%3ctime=%2211:47:33.000+000
 date=11-17-2014 component=Wizard context= type=1 thread= 
file=Wizard

![LOG[Validate Against UNC: 
\\xx\mdt]LOG]!time=11:47:33.000+000file:///\\xx\mdt%5dLOG%5d!%3e%3ctime=%2211:47:33.000+000
 date=11-17-2014 component=Wizard context= type=1 thread= 
file=Wizard

![LOG[Mapped Network UNC Path Z:  = 
\\xx\mdt]LOG]!time=11

RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to install via MDT 2012

[David Landry]

Hi All,

Thanks for all the assistance. It is truly appreciated.

Keith,

Your script worked like a charm. My apologies for not trying this when you 
first suggested it. My lack of understanding what you were doing was 
responsible for my hesitation.

Thank you so much for your assistance.

Also, I am interested if anyone knows any easy to understand books on scripting 
for novices or internet courses that will help with learning how to create 
scripts?

Thanks in advance,

Regards,

Dave


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of elsalvoz
Sent: Monday, October 20, 2014 7:06 PM
To: mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to 
install via MDT 2012


To build on Michael's answer. Batch files have a hard time with UNC paths when 
running.

Try adding: PUSHD  %~dp0 at the first line and POPD at the last line

Cesar
On Oct 20, 2014 3:04 PM, Michael Niehaus 
michael.nieh...@microsoft.commailto:michael.nieh...@microsoft.com wrote:
It depends.  If you set up the batch file (.cmd or .bat) as an application, MDT 
will map a drive and run the command using the mapped drive, which matches what 
you described below.

But if you set up a “Run command line” task sequence step that just specifies 
something like this:


• Command line:  runme.cmd

• Working directory:  %DeployRoot%\Applications\MyFolder

Then it will likely fail as “runme.cmd” won’t see the working directory set to 
a UNC path; it will end up trying to run it from the default path, typically 
C:\Windows\System32.

You could specify this instead:


• Command line: runme.cmd

• Working directory:  %DeployDrive%\Applications\MyFolder

Also, pay attention to the return code from the last command the batch file 
runs.  If it is non-zero, you need to account for that, or tell the task 
sequence to ignore the error.

Using batch files is a bit of a pain overall, which is why scripts are 
preferred.

Thanks,
-Michael

From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com] 
On Behalf Of Keith Garner (Hotmail)
Sent: Monday, October 20, 2014 2:50 PM
To: mdtosd@lists.myitforum.commailto:mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to 
install via MDT 2012

That’s not how MDT would run. To simulate MDT, change to the network directory 
and run the script from there.

[cid:image001.png@01CFED0C.80DBC270]



From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry
Sent: Monday, October 20, 2014 1:47 PM
To: mdtosd@lists.myitforum.commailto:mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to 
install via MDT 2012

But not if I connect to the server from the target machine.

[cid:image002.png@01CFED0C.80DBC270]


Dave Landry
Site Support Administrator
Laird Technologies
1 Perimeter Road – Suite 700
Manchester, NH 03103
+1 603-935-7857tel:%2B1%20603-935-7857
[LairdLogo]

From: David Landry
Sent: Monday, October 20, 2014 4:39 PM
To: mdtosd@lists.myitforum.commailto:mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to 
install via MDT 2012

Yes, I can run the sep_install.bat from the local desktop and they work 
perfectly.

Dave Landry
Site Support Administrator
Laird Technologies
1 Perimeter Road – Suite 700
Manchester, NH 03103
+1 603-935-7857tel:%2B1%20603-935-7857
[LairdLogo]

From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of elsalvoz
Sent: Monday, October 20, 2014 4:24 PM
To: mdtosd@lists.myitforum.commailto:mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to 
install via MDT 2012


Do the scripts work when you run them manually?

Cesar
On Oct 20, 2014 12:24 PM, David Landry 
david.lan...@lairdtech.commailto:david.lan...@lairdtech.com wrote:
Hi All,

I have an MDT server where I want to set up SEP in application Deployment. 
Below is the scripts I have tried:

From Daniel:

@echo off
IF %ProgramFiles(x86)%==C:\Program Files (x86) goto x64 else goto x86
:x86
ECHO System is x86
msiexec /i “%~dp0SSEP_12.1.4013.4013_32bit\Sep.msi /qn /L*V log.txt 
SYMREBOOT=Suppress
goto exit
:x64
ECHO System is x64
msiexec /i “%~dp0SSEP_12.1.4013.4013_64bit\Sep64.msi /qn /L*V log.txt 
SYMREBOOT=Suppress
goto exit
:exit

-and 

@echo off
IF %ProgramFiles(x86)%==C:\Program Files (x86) goto x64 else goto x86
:x86
ECHO System is x86
msiexec /i SEP_12.1.4013.4013_32bit\Sep.msi /qn /L*V log.txt SYMREBOOT=Suppress
goto exit
:x64
ECHO System is x64
msiexec /i SEP_12.1.4013.4013_64bit\Sep64.msi /qn /L*V log.txt 
SYMREBOOT=Suppress
goto exit
:exit

The command lines have

RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to install via MDT 2012

[David Landry]

Yes, I can run the sep_install.bat from the local desktop and they work 
perfectly.

Dave Landry
Site Support Administrator
Laird Technologies
1 Perimeter Road – Suite 700
Manchester, NH 03103
+1 603-935-7857
[LairdLogo]

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of elsalvoz
Sent: Monday, October 20, 2014 4:24 PM
To: mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to 
install via MDT 2012


Do the scripts work when you run them manually?

Cesar
On Oct 20, 2014 12:24 PM, David Landry 
david.lan...@lairdtech.commailto:david.lan...@lairdtech.com wrote:
Hi All,

I have an MDT server where I want to set up SEP in application Deployment. 
Below is the scripts I have tried:

From Daniel:

@echo off
IF %ProgramFiles(x86)%==C:\Program Files (x86) goto x64 else goto x86
:x86
ECHO System is x86
msiexec /i “%~dp0SSEP_12.1.4013.4013_32bit\Sep.msi /qn /L*V log.txt 
SYMREBOOT=Suppress
goto exit
:x64
ECHO System is x64
msiexec /i “%~dp0SSEP_12.1.4013.4013_64bit\Sep64.msi /qn /L*V log.txt 
SYMREBOOT=Suppress
goto exit
:exit

-and 

@echo off
IF %ProgramFiles(x86)%==C:\Program Files (x86) goto x64 else goto x86
:x86
ECHO System is x86
msiexec /i SEP_12.1.4013.4013_32bit\Sep.msi /qn /L*V log.txt SYMREBOOT=Suppress
goto exit
:x64
ECHO System is x64
msiexec /i SEP_12.1.4013.4013_64bit\Sep64.msi /qn /L*V log.txt 
SYMREBOOT=Suppress
goto exit
:exit

The command lines have varied quite a bit. But I started with:
Cmd.exe /c sep_install.bat

The source/working directory in MDT on the software package is:
.\Applications\Symantec_Endpoint_Protection


The best I have been able to do is get the script to start (it opens a DOS 
window) then identifies the OS, but it dies right there. Sometimes with no 
error or return code, sometimes with a return code: 1.

Any help sure would be appreciated.

Thanks in advance


Dave Landry
Site Support Administrator
Laird Technologies
1 Perimeter Road – Suite 700
Manchester, NH 03103
+1 603-935-7857tel:%2B1%20603-935-7857
[LairdLogo]

From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com] 
On Behalf Of David Landry
Sent: Friday, October 17, 2014 4:38 PM
To: mdtosd@lists.myitforum.commailto:mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to 
install via MDT 2012

Hi Guys,

Thanks for the assistance. The DOS window comes up when the script starts but 
then it dies, windows close, and I get the white MDT completion window with no 
errors.

I am not sure at this point if the problem is in the .bat file or the command 
line?

Thanks again in advance,

Dave Landry


From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Keith Garner (Hotmail)
Sent: Friday, October 17, 2014 3:31 PM
To: mdtosd@lists.myitforum.commailto:mdtosd@lists.myitforum.com
Subject: RE: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to 
install via MDT 2012

Be aware of smart quotes…

Additionally, be aware that if you had one bad software package that was 
installed to c:\program files (x86) on a x86 system it would fail.

If you want to get cute…
@if not defined debug echo off

if /i %PROCESSOR_ARCHITECTURE%%PROCESSOR_ARCHITEW6432%==x86 (
   msiexec /i %~dps0SEP_12.1.4013.4013_32bit\Sep.msi /qn /L*V log.txt 
SYMREBOOT=Suppress
) else (
   msiexec /i %~dps0SEP_12.1.4013.4013_64bit\Sep64.msi /qn /L*V log.txt 
SYMREBOOT=Suppress
)


-k

From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Daniel Ratliff
Sent: Friday, October 17, 2014 11:04 AM
To: mdtosd@lists.myitforum.commailto:mdtosd@lists.myitforum.com
Subject: [MDT-OSD] RE: Can't seem to get Symantec Endpoint Protection to 
install via MDT 2012

Always use %~dp0 when calling files from a .bat file, especially when running 
from the network.

@echo off
IF %ProgramFiles(x86)%==C:\Program Files (x86) goto x64 else goto x86
:x86
ECHO System is x86
msiexec /i “%~dp0SEP_12.1.4013.4013_32bit\Sep.msi” /qn /L*V log.txt 
SYMREBOOT=Suppress
goto exit
:x64
ECHO System is x64
msiexec /i “%~dp0SEP_12.1.4013.4013_64bit\Sep64.msi” /qn /L*V log.txt 
SYMREBOOT=Suppress
goto exit
:exit


Daniel Ratliff

From: listsad...@lists.myitforum.commailto:listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of David Landry
Sent: Friday, October 17, 2014 1:55 PM
To: mdtosd@lists.myitforum.commailto:mdtosd@lists.myitforum.com
Subject: [MDT-OSD] Can't seem to get Symantec Endpoint Protection to install 
via MDT 2012

Hi All,

I have been having a heck of a time trying to get SEP to install. I have 
imported the installation files for both 32bit and 64bit (in separate folders) 
along with a .bat file to run them from MDT. The bat file is:

@echo off

[MDT-OSD] PXE boot problem on new MDT server

[David Landry]

Hi All,

I have migrated our file server (which also has MDT on it) to a new server.

The only issue I am having is with MDT. When I do a PXE boot it finds the new 
server and starts to load. I get to where I enter my credentials and I get an 
error Invalid credentials. The Network path was not found

I have checked the permissions and DHCP server options (also on the server). I 
originally had just 060 (on the original server), but was told to remove 060 
and configure 066 and 067 (neither were on the original server). No change 
after making these changes. I also have a server at another site that has MDT 
on it that is configured the same as the original server here. No problems at 
that site.

I also found that the bootstrap.ini file was pointing to  the wrong server. I 
fixed that, but it is still not working.

Anyone have any ideas?

Thanks in advance for your responses.

Dave