I've been able to get almost all the way there...!!! I got my script to work for Windows 7 when it is called by unattend.xml in the Microsoft-Windows-Deployment phase of the Deploy task sequence/settings -- minisetup.
The only remaining problem I have is that that phase of the Windows minisetup occurs AFTER the domain join attempt. Is that correct? And if Yes, what can I do to make the Task Sequence try to join the domain again? Would there be a better way to establish the 802.1x secured network connection prior to the domain join attempt in minisetup? I think I'll try to move my script into the Build and Capture and see what happens. From: [email protected] [mailto:[email protected]] On Behalf Of Miller, Todd Sent: Tuesday, December 08, 2015 5:34 PM To: [email protected] Subject: [MDT-OSD] 802.1x for the Windows 7 phase I have the WinPE phase working great with 802.1x wired security thanks to the tips from this list. I am now struggling with Windows 7. I have a script that will provide credentials to the Wired interface and set the dot3svc to Automatic. I am attempting to run that script from the Microsoft-Windows-Deployment section of unattend.xml. The script gets a failure 0x1 exit code in setupact.log, but If I copy the command line out of Unattend,xml and run it in an F8 command window, it works fine. Now I am thinking maybe I would be better off adding the profile into the build and capture process so that when the image is deployed it already has the user profile added to the Local Area Connection and has dot3svc already set to automatic. Would those kind of changes survive Sysprep? Could I just import the profile into the LAN configuration prior to sysprep and then it would just be there for when windows runs through minisetup? Would that work or do I need to figure out what's up with the Unattend.xml thing? ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________ ________________________________ Notice: This UI Health Care e-mail (including attachments) is covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may be legally privileged. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. ________________________________
