OK I tried it without the Group Policies and get the same result. When I capture the image I get the following warning messages
No answer file could be found
No answer file could be found
Unable to copy unattend.xml for sysprep, not found
(I believe I got these same messages with I captured my x64 image which works.
The x64 image was captures with the same task sequence.)
After rebooting the system that I just captured I am unable to log on - I get -
Administrator account is disabled. That's the same message I get when I build
an image from the one I captured. I think I am normally able to log on to the
rebooted system that was captured.
Thanks for any help you can provide.
Curt
From: [email protected] [mailto:[email protected]] On
Behalf Of [email protected]
Sent: Thursday, October 31, 2013 7:08 AM
To: [email protected]
Subject: [MDT-OSD] RE: Windows 8.1 x86 Deployment Issue
I'm not setting that in local policy, try pulling that out, and if it deploys,
just apply the reg keys later in the process.
Christopher Catlett
Consultant | Detroit
[MCTS_2013_small]
Sogeti USA
Office 248-876-9738 |Fax 877.406.9647
26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456
www.us.sogeti.com<http://www.us.sogeti.com/>
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Curt Finley
Sent: Wednesday, October 30, 2013 6:39 PM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: Windows 8.1 x86 Deployment Issue
It is using the X86 PE
It starts to deploy. It just seems to lock the Admin account before it's done
setting up the computer.
On the computer I created the image from I created a group policy that sets the
lock screen to a different image (instead of that crazy rainbow thing) and sets
it so you can't change it. That wouldn't cause this would it? The exact GPs
are
Local Computer Policy\Computer Configuration Administrative Tools\Control
Panel\Personalization\Force a specific default lock screen image
Local Computer Policy\Computer Configuration Administrative Tools\Control
Panel\Personalization\Prevent changing lock screen image
This is one of a few differences between this and the X64 image I built.
Curt
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of
[email protected]<mailto:[email protected]>
Sent: Wednesday, October 30, 2013 2:53 PM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: Windows 8.1 x86 Deployment Issue
When it PXE's, is it using a x86 or x64 PE?
Iirc, x64 can only deploy x64 OS (and hardware and OS arch must match on UEFI
machines)
Christopher Catlett
Consultant | Detroit
[MCTS_2013_small]
Sogeti USA
Office 248-876-9738 |Fax 877.406.9647
26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456
www.us.sogeti.com<http://www.us.sogeti.com/>
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Curt Finley
Sent: Wednesday, October 30, 2013 5:37 PM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: Windows 8.1 x86 Deployment Issue
Thanks for your replies.
I created a new task sequence and this time I did not modify the unattend.xml
file. I got the same results. The differences between the previous
unattend.xml and the new one are
1) The old one has a section as shown below (I changed the password
below). The new one looks the same except PlainText is True and the password
is shown in plain text.
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup"
processorArchitecture="x86" publicKeyToken="31bf3856ad364e35"
language="neutral" versionScope="nonSxS"
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State";>
<UserAccounts>
<AdministratorPassword>
<Value>ABC</Value>
<PlainText>false</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value>XYZ==</Value>
<PlainText>false</PlainText>
</Password>
2) The new one doesn't have a pointer to the catalog file I copied from
the X86 machine.
<cpi:offlineImage cpi:source="catalog://wdsmdt4/mdtproduction$/operating
systems/windows 8.1 enterprise x86 custom
image/w81-x86-002_capture-001ddrive.clg"
xmlns:cpi="urn:schemas-microsoft-com:cpi" />
3) The new one doesn't have the modifications I made in the previous
version.
<TimeZone>Pacific Standard Time</TimeZone>
<TaskbarLinks>
<Link0>%ALLUSERSPROFILE%\Microsoft\Windows\Start
Menu\Programs\Microsoft Office 2013\Excel 2013.lnk</Link0>
<Link1>%ALLUSERSPROFILE%\Microsoft\Windows\Start
Menu\Programs\Microsoft Office 2013\Outlook 2013.lnk</Link1>
<Link2>%ALLUSERSPROFILE%\Microsoft\Windows\Start
Menu\Programs\Microsoft Office 2013\PowerPoint 2013.lnk</Link2>
<Link3>%ALLUSERSPROFILE%\Microsoft\Windows\Start
Menu\Programs\Microsoft Office 2013\Word 2013.lnk</Link3>
</TaskbarLinks>
<CopyProfile>true</CopyProfile>
Since the new one doesn't reference the catalog and since it still doesn't
work, it may be safe to assume it is not the catalog that is causing the
problem. Also, since you said you have used the same procedure without
negative consequence.
My ADK (8.100.26020) and MDT (6.2.5019) were downloaded 10/24 so I assume they
are the re-released version.
Curt
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of
[email protected]<mailto:[email protected]>
Sent: Wednesday, October 30, 2013 1:52 PM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: Windows 8.1 x86 Deployment Issue
I've had no issue creating the catalog for a x86 image, on my x64 deployment
server.
I'm using the re-release of the ADK 8.1 and MDT 2013 (host is windows 8.1, but
that should not matter.)
Christopher Catlett
Consultant | Detroit
[MCTS_2013_small]
Sogeti USA
Office 248-876-9738 |Fax 877.406.9647
26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456
www.us.sogeti.com<http://www.us.sogeti.com/>
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Curt Finley
Sent: Wednesday, October 30, 2013 4:48 PM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: Windows 8.1 x86 Deployment Issue
Thanks for your suggestion.
The unattend.xml files are identical with exception of processorArchitecture,
WIM filename/path and the catalog filename/path.
But that does bring up one possible issue. The server is obviously 64 bit. My
understanding is that you can't create a catalog for a 32 bit image on a 64 bit
machine. I copied the deployment share to a 32 bit machine, created the
catalog there and copied the catalog back to my server. Perhaps that caused
the problem?
Curt
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Daniel Ratliff
Sent: Wednesday, October 30, 2013 1:01 PM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: Windows 8.1 x86 Deployment Issue
Sounds like an unattend.xml issue. I am not too well versed in configuring it
properly, but that's the first place I would look.
Daniel Ratliff
From: [email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Curt Finley
Sent: Wednesday, October 30, 2013 3:41 PM
To: [email protected]<mailto:[email protected]>
Subject: [MDT-OSD] Windows 8.1 x86 Deployment Issue
I created a custom Win 8.1 x64 image, captured it and am able to deploy it.
When I PXE boot the system copies of the image, reboots and goes through a
number of phases such as Getting devices ready, Getting ready, Finalizing your
settings ,.... I created a custom Win 8.1 x86 image (I thought the same way as
I did the x64 image) but when I PXE boot it, it copies the image, reboots and
presents me with a logon prompt. It does not go through the Getting devices
ready, ... phases. When I attempt to log on it tells me the Administrator
account has been disabled. If I subsequently try to deploy an image to the
same machine it says there is an existing in-progress deployment that is not in
an expected state and it asks if I want to start a new deployment. I've
created and captured the x86 image twice but I apparently made the same mistake
because I'm getting the same result. Can someone clue me in on what I might be
doing differently than when I created the X64 image? If not, perhaps you could
give me a hint on how to diagnose the issue?
I'm running MDT 2013 on Server 2012 R2. It's a completely new server - not
upgraded from a previous version of MDT.
Thanks for your help.
Curt
The information transmitted is intended only for the person or entity to which
it is addressed
and may contain CONFIDENTIAL material. If you receive this material/information
in error,
please contact the sender and delete or destroy the material/information.
<<inline: image001.jpg>>
