RE: [mssms] UEFI Windows 10 via SCCM/MDT OSD

2016-09-13 Thread Brian Illner 
TS has been available for about a month now, so don’t think that is it.

BRIAN ILLNER | Canal Insurance Company
864.250.9227
864.679.2537 Fax
Visit canalinsurance.com<http://canalinsurance.com> for news and information.
[cid:image001.jpg@01D20DA5.2AD8EC70]
[cid:image002.jpg@01D20DA5.2AD8EC70]<https://www.linkedin.com/company/canal-insurance-company>
WARNING:  As the information in this transmittal (including attachments, if 
any) may contain confidential, proprietary, or business trade secret 
information, it should only be reviewed by those who are the intended 
recipients.  Unless you are an intended recipient, any review, use, disclosure, 
distribution or copying of this transmittal (or any attachments) is strictly 
prohibited.   If you have received this transmittal in error, please notify me 
immediately by reply email and destroy all copies of the transmittal.  While 
Canal believes this transmittal to be free of virus or other defect, it is the 
responsibility of the recipient to ensure that it is virus free and no 
responsibility is accepted by Canal (or its subsidiaries and affiliates) for 
any loss or damage arising therefrom.
From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Adam Juelich
Sent: Tuesday, September 13, 2016 8:39 AM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] UEFI Windows 10 via SCCM/MDT OSD

Not sure this bug is still there.  Try scheduling the TS for the past, about a 
week and try again.

On Tue, Sep 13, 2016 at 7:27 AM, Brian Illner 
<brian.ill...@canal-ins.com<mailto:brian.ill...@canal-ins.com>> wrote:
We’re attempting to set up a Windows 10 OSD for UEFI with Secure Boot.

My (gen2) test VM boots to PXE and can start the task sequence just fine, but 
the OSD wizard does not allow us to select an image. That window is completely 
empty.

The correct OS image is distributed, its assigned in the correct task sequence 
and appears in its references tab.

I’ve already got a boot up script that synchs the VM time, so it’s not that 
either.

Any other ideas on whats going on?

ConfigMgr 1607
ADK Win10 1607

BRIAN ILLNER | Senior Systems Administrator
864.250.9227
864.679.2537 Fax

Canal Insurance Company
400 East Stone Avenue
Greenville, SC 29601
Visit canalinsurance.com<http://canalinsurance.com> for news and information.
[cid:image001.jpg@01D20DA5.2AD8EC70]
[cid:image002.jpg@01D20DA5.2AD8EC70]<https://www.linkedin.com/company/canal-insurance-company>
WARNING:  As the information in this transmittal (including attachments, if 
any) may contain confidential, proprietary, or business trade secret 
information, it should only be reviewed by those who are the intended 
recipients.  Unless you are an intended recipient, any review, use, disclosure, 
distribution or copying of this transmittal (or any attachments) is strictly 
prohibited.   If you have received this transmittal in error, please notify me 
immediately by reply email and destroy all copies of the transmittal.  While 
Canal believes this transmittal to be free of virus or other defect, it is the 
responsibility of the recipient to ensure that it is virus free and no 
responsibility is accepted by Canal (or its subsidiaries and affiliates) for 
any loss or damage arising therefrom.

Re: [mssms] UEFI Windows 10 via SCCM/MDT OSD

2016-09-13 Thread Adam Juelich 
Not sure this bug is still there.  Try scheduling the TS for the past,
about a week and try again.

On Tue, Sep 13, 2016 at 7:27 AM, Brian Illner 
wrote:

> We’re attempting to set up a Windows 10 OSD for UEFI with Secure Boot.
>
>
>
> My (gen2) test VM boots to PXE and can start the task sequence just fine,
> but the OSD wizard does not allow us to select an image. That window is
> completely empty.
>
>
>
> The correct OS image is distributed, its assigned in the correct task
> sequence and appears in its references tab.
>
>
>
> I’ve already got a boot up script that synchs the VM time, so it’s not
> that either.
>
>
>
> Any other ideas on whats going on?
>
>
>
> ConfigMgr 1607
>
> ADK Win10 1607
>
>
>
> *BRIAN* *ILLNER* *|* Senior Systems Administrator
> 864.250.9227
> 864.679.2537 Fax
>
> Canal Insurance Company
> 400 East Stone Avenue
> Greenville, SC 29601
>
> Visit canalinsurance.com for news and information.
>
> 
>
> *WARNING*:  *As the information in this transmittal (including
> attachments, if any) may contain confidential, proprietary, or business
> trade secret information, it should only be reviewed by those who are the
> intended recipients.  Unless you are an intended recipient, any review,
> use, disclosure, distribution or copying of this transmittal (or any
> attachments) is strictly prohibited.   If you have received this
> transmittal in error, please notify me immediately by reply email and
> destroy all copies of the transmittal.  While Canal believes this
> transmittal to be free of virus or other defect, it is the responsibility
> of the recipient to ensure that it is virus free and no responsibility is
> accepted by Canal (or its subsidiaries and affiliates) for any loss or
> damage arising therefrom.*
>
>

[mssms] UEFI Windows 10 via SCCM/MDT OSD

2016-09-13 Thread Brian Illner 
We're attempting to set up a Windows 10 OSD for UEFI with Secure Boot.

My (gen2) test VM boots to PXE and can start the task sequence just fine, but 
the OSD wizard does not allow us to select an image. That window is completely 
empty.

The correct OS image is distributed, its assigned in the correct task sequence 
and appears in its references tab.

I've already got a boot up script that synchs the VM time, so it's not that 
either.

Any other ideas on whats going on?

ConfigMgr 1607
ADK Win10 1607

BRIAN ILLNER | Senior Systems Administrator
864.250.9227
864.679.2537 Fax

Canal Insurance Company
400 East Stone Avenue
Greenville, SC 29601
Visit canalinsurance.com for news and information.
[cid:image001.jpg@01D20D98.A140E320]
[cid:image002.jpg@01D20D98.A140E320]
WARNING:  As the information in this transmittal (including attachments, if 
any) may contain confidential, proprietary, or business trade secret 
information, it should only be reviewed by those who are the intended 
recipients.  Unless you are an intended recipient, any review, use, disclosure, 
distribution or copying of this transmittal (or any attachments) is strictly 
prohibited.   If you have received this transmittal in error, please notify me 
immediately by reply email and destroy all copies of the transmittal.  While 
Canal believes this transmittal to be free of virus or other defect, it is the 
responsibility of the recipient to ensure that it is virus free and no 
responsibility is accepted by Canal (or its subsidiaries and affiliates) for 
any loss or damage arising therefrom.