We may be having this issue with our Windows 7 x32 task sequence. Windows 7
x64 works, and we think it has to do with a certificate issue that may be
unique to the x32 client? I wanted to see if this was possibly the same
issue you guys had... Were you trying to deploy Win 7 x32 or Win 7 x64?


On Thu, Aug 22, 2013 at 6:36 PM, Richard Zuraff <[email protected]
> wrote:

>  I'm wondering if we need to open a case on it.
>
> On Aug 22, 2013, at 6:26 PM, "Aaron Czechowski" <
> [email protected]> wrote:
>
>   Outside of our bug database? J Not that I’m aware. The issue was
> originally raised to us from support, so no Connect feedback item on it.
> I’m checking with the folks in support whether anything else was done to
> document the issue.****
>
> ** **
>
> Aaron****
>
> ** **
>
> ** **
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Richard Zuraff
> *Sent:* Thursday, August 22, 2013 2:19 PM
> *To:* <[email protected]>
> *Subject:* Re: [mssms] SCCM 2012 WinPE issue.****
>
> ** **
>
> Is this documented anywhere as a bug? ****
>
>
> On Aug 22, 2013, at 12:36 PM, "Aaron Czechowski" <
> [email protected]> wrote:****
>
>  This should be addressed in R2 Preview. ****
>
>  ****
>
> Aaron****
>
>  ****
>
>  ****
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *CESAR.ABREG0 .
> *Sent:* Wednesday, August 21, 2013 4:55 PM
> *To:* [email protected]
> *Subject:* Re: [mssms] SCCM 2012 WinPE issue.****
>
>  ****
>
> So are. CU2****
>
> On Aug 21, 2013 4:53 PM, "Richard Zuraff" <[email protected]>
> wrote:****
>
>  We are on CU2 and are seeing it. ****
>
>
> On Aug 21, 2013, at 5:49 PM, "Daniel Ratliff" <[email protected]> wrote:
> ****
>
>  This sounds like an issue we were seeing pre CU2 but with DPs not MPs.
> Microsoft basically said when we distribute content we have to add all DPs
> otherwise it will always try to download from the DP that doesn't have the
> content. We upgraded to CU2 over the weekend but haven't tested yet.
>
> -Daniel Ratliff
>
> -----Original Message-----
> *From: *CESAR.ABREG0 . [[email protected]]
> *Sent: *Wednesday, August 21, 2013 06:26 PM Eastern Standard Time
> *To: *[email protected]
> *Subject: *Re: [mssms] SCCM 2012 WinPE issue.****
>
> We are having the same exact symptoms in our environment, the only
> difference is that one of our 4 MPs is part of an 'untrusted domain'
> environment in a DMZ and is not internet facing one, our 5th that is not
> online yet, will be an internet facing one. ****
>
>  ****
>
> Out bootdisk has 3 primary MPs in the options but the client wants to get
> pol from our 4th MP which is not part of the MP options. One of our team
> members directed the question to MS rep but no response yet. We removed the
> role from the Site System for now since we is not in production yet.****
>
>  ****
>
> I will relay any findings that we get or workarounds. ****
>
>  ****
>
> On Wed, Aug 21, 2013 at 3:01 PM, Richard Zuraff <
> [email protected]> wrote:****
>
>  I’m having an issue with our OSD booting from PXE.  Everything was
> working correctly until we setup an external facing management point for
> our Internet facing clients.  Once we did that our imaging via PXE\Boot CD
> stopped working.  We are now getting the external Management Point instead
> of the internal one.  It’s unable to find any DP’s with the imaging content
> on it even though the internal and external DP’s have the imaging content
> on them.  If we remove the external MP everything works fine. ****
>
>  ****
>
> How does it determine the MP during WinPE?  Any ideas on where to start
> troubleshooting this issue?****
>
>  ****
>
>  ****
>
>  ****
>
> Thanks****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
>  ****
>
>   ****
>
>
>
> 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.*
> ***
>
>   ****
>
>   ****
>
> ** **
>
> ** **
>
>
>



Reply via email to