Re: [mssms] Internet Clients

[Jason Sandys]

ConfigMgr never ever cares if a system to be managed is joined to a domain.

Certificate enrollment is always a challenge and depends upon a lot of things 
but there is no easy answer here.

Web enrollment is one possibility (if the users are local admins which is bad 
of course): 
https://technet.microsoft.com/en-us/library/hh831649%28v=ws.11%29.aspx.

The certificate enrollment web service is another possibility: 
https://technet.microsoft.com/en-us/library/hh831822(v=ws.11).aspx

J

From:  on behalf of SCCM Admin 

Reply-To: "mssms@lists.myitforum.com" 
Date: Friday, March 24, 2017 at 7:23 PM
To: "mssms@lists.myitforum.com" 
Subject: [mssms] Internet Clients

To manage internet machines with Azure through the cloud management gateway do 
they have to be joined to the domain, or can they be treated as workgroup 
clients.

Also how would the client certificate be sent to those machines?

[mssms] Internet Clients

[SCCM Admin]

To manage internet machines with Azure through the cloud management gateway
do they have to be joined to the domain, or can they be treated as
workgroup clients.

Also how would the client certificate be sent to those machines?

Re: [mssms] BIOS FlashScreen Name Change / Delete

[Kevin Ray]

my bad page not found..any other

On Fri, Mar 10, 2017 at 1:13 PM, Chobeaux, Sebastien <
schobe...@csdccs.edu.on.ca> wrote:

> Hi, for Dell (I don’t use Lenovo) you’ll need Dell Command Configure
> (CCTK) and to change the owner tag use the parameter  *propowntag*
>
> *(cctk.cmd –propowntag NewCompagny*
>
> I think you can do it from winPe or full windows if you’re just changing
> that
>
> You’ll need to specify the bios password in the command line
>
> Have a look at this to see an example you can adapt
>
>
>
> https://www.scconfigmgr.com/2017/02/19/convert-from-bios-
> to-uefi-on-dell-systems-with-configmgr-current-branch-part-1/
>
>
>
> good luck
>
>
>
>
>
> *De :* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *De la part de* Kevin Ray
> *Envoyé :* vendredi 10 mars 2017 12:16
> *À :* mssms 
> *Objet :* Re: [mssms] BIOS FlashScreen Name Change / Delete
>
>
>
> Most are Dell and Lenovo
>
>
>
> On Fri, Mar 10, 2017 at 11:57 AM, Marable, Mike 
> wrote:
>
> It will depend on the manufacturer.  We have Dells and using their BIOs
> utility we set the splash screen to our company name.
>
>
>
> Who is the manufacturer of your hardware?
>
>
>
>
>
>
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kevin Ray
> *Sent:* Friday, March 10, 2017 11:47 AM
> *To:* mssms 
> *Subject:* [mssms] BIOS FlashScreen Name Change / Delete
>
>
>
> Hi All,
>
>
>
> Not much knowledge on BIOS Setup or update.
>
>
>
> So we have some machines with BIOS Flash screen with Old company name.. I
> would like to change or Clean the Flassh screen while booting the
> machine...we are doing wipe and load with New OS...
>
>
>
> Any help to quick start to understand the changed or Fix
>
>
>
> **
> Electronic Mail is not secure, may not be read every day, and should not
> be used for urgent or sensitive issues
>
>
>
>
>
>
>
> --
>
> AVIS IMPORTANT:
> Les renseignements contenus ou joints à ce courriel sont pour l'usage
> exclusif du destinataire ou de l'institution à qui ce courriel s'adresse et
> peuvent contenir des renseignements privilégiés, confidentiels et exempts
> de divulgation conformément à la Loi sur l'accès à l'information municipale
> et la protection de la vie privée.
> Dans l'éventualité que le récepteur du présent courriel n'est pas le
> destinataire concerné ou la personne autorisée à acheminer le message au
> destinataire concerné, vous êtes, par la présente, avisé(e), que toute
> divulgation, diffusion, distribution ou reproduction de la présente
> communication est strictement interdite.
> Si vous recevez ce message par erreur, veuillez immédiatement en informer
> l'expéditeur ou l'expéditrice par courriel et détruire celui-ci ainsi que
> toutes les pièces jointes qu'il comporte.
> Merci de votre collaboration.
>
>

Re: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

[Niall Brady]

hi Kevin
the following will do refreshes from PXE even if BitLockered as long as
you've an MBAM back end, do you ?

https://www.niallbrady.com/2016/05/17/introducing-the-windows-10-uefi-bitlocker-frontend-for-system-center-configuration-manager-current-branch/

On Fri, Mar 24, 2017 at 2:25 PM, Jerousek, Jeff 
wrote:

> How are you deploying the Task Sequence?
>
>
>
> Is this set?
>
>
>
> If you don’t tell it to access content directly it tries to download it on
> to a disk, if it’s bitLocked it can’t download anything.
>
>
>
> Niall Brady has some interesting posts on creating a partition for this
> when doing an In-Place Install on a bitLocked drive.
>
>
>
> Thanks,
>
> Jeff Jerousek 
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com] *On Behalf Of *Kevin Johnston
> *Sent:* Friday, March 24, 2017 7:50 AM
> *To:* mssms@lists.myitforum.com
> *Subject:* [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
>
>
>
> I should note that we also have a task sequence where we deploy Windows 7
> with bitlocker.
>
> We have no issues reimaging these machines. We do not get any errors.
>
>
>
> It seems weird that on a UEFI system a reimage fails.
>
>
>
> Also a note that the out of box Dell we got, was already bitlockered, so
> when we ran the TS to reimage it, we had no issues until we wanted to
> reimage the machine.
>
>
>
> I guess I need to dig a lot deeper into what is happening in bitlocker
> that may be causing this issue.
>
>
>
> Kevin
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com ] *On Behalf Of *Marable,
> Mike
> *Sent:* Friday, March 24, 2017 8:08 AM
> *To:* mssms@lists.myitforum.com
> *Subject:* [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled -
> fails
> *Importance:* Low
>
>
>
> When you attempt the 2nd build (where you’re getting the error) is it
> originating from a PXE boot or is the task sequence starting from within
> the full OS?
>
>
>
> If you’re PXE booting it, do you have a script to unlock BitLocker so that
> WinPE can access the disk?  If not then that is probably what is causing
> the problem.  You PXE boot and WinPE cannot access the BitLocker encrypted
> drive.  It sees that the drive is there but it cannot access the
> partition(s) so it kicks back the error that the drive must be formatted.
>
>
>
> Mike
>
>
>
>
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com ] *On Behalf Of *Kevin
> Johnston
> *Sent:* Friday, March 24, 2017 7:33 AM
> *To:* mssms@lists.myitforum.com
> *Subject:* [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
>
>
>
> Yes the drive is using bitlocker.
>
>
>
> Kevin
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com ] *On Behalf Of *Marable,
> Mike
> *Sent:* Friday, March 24, 2017 7:14 AM
> *To:* mssms@lists.myitforum.com
> *Subject:* [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled -
> fails
> *Importance:* Low
>
>
>
> Are you encrypting the drive at all?
>
>
>
> Mike
>
>
>
>
>
> *From:* listsad...@lists.myitforum.com [mailto:listsadmin@lists.
> myitforum.com ] *On Behalf Of *Kevin
> Johnston
> *Sent:* Friday, March 24, 2017 6:46 AM
> *To:* mssms@lists.myitforum.com
> *Subject:* [mssms] Reimaging a Dell that has UEFI enabled - fails
>
>
>
> We have a brand new out of the box Dell E7270 Latitude. The machine comes
> with UEFI already configured and we are imaging it with Windows 10.
>
>
>
> We PXE boot the machine, go through our SCCM task sequences to image the
> machine and everything appears to be great.
>
>
>
> We take this same machine we just imaged, remove it from SCCM and go to
> reimage this machine and right after we choose our Win10 Task Sequence we
> get the following message every time:
>
>
>
> “The task sequence was unable to locate a logical drive. The hard disk
> will need to be partitioned and formatted. Click OK to continue or Cancel
> to exit the task sequence”
>
>
>
> We have a bunch of older machines, that we do a BIOS to UEFI (which works
> fine) TS then image the machine same as above but again, when we want to
> reimage the same machine we get that same error each time.
>
>
>
> What we have done in the past is before we have to put in our SCCM TS
> password, we hit F8 and do a diskpart manually to wipe the disk, but this
> seems counter intuitive as the task sequence should be able to wipe the
> drive anyways as part of the task sequence.
>
> Plus when we do this, it does not seem to image properly after words
> meaning it fails each time.
>
>
>
> Has anyone seen this issue before? Is there something different we need to
> add to our TS in order for this to work?
>
>
>
> Thanks,
>
>
>
> KEVIN JOHNSTON
>
>
>
>
>
> **
> Electronic 

Re: [mssms] 2012 to 2016 upgrade with step issues

[Adam Juelich]

What is STEP?

Is your SCEP Client Policy set to install to those Windows Defender
machines, or did you deploy 'SCEP_Install.exe' to them separately?

They still need the 'Install' to be managed.  I found this out a month ago
as well.

On Fri, Mar 24, 2017 at 10:40 AM, Stuart Watret 
wrote:

> Someone on site did an in place upgrade of server 2012 r2 to 2016 server.
>
> Now defender and step are in a twist.
>
> I removed sccm, step and reinstalled sccm, this got defender back to being
> managed.
>
> He just came back to me to say step is back, sure enough defender is back
> to unmanaged.
>
> Anyone seen this, have any thoughts?
>
> Thanks
>
> Stuart
>
>

[mssms] 2012 to 2016 upgrade with step issues

[Stuart Watret]

Someone on site did an in place upgrade of server 2012 r2 to 2016 server.

Now defender and step are in a twist.

I removed sccm, step and reinstalled sccm, this got defender back to being 
managed.

He just came back to me to say step is back, sure enough defender is back to 
unmanaged.

Anyone seen this, have any thoughts?

Thanks

Stuart

[mssms] RE: Reimaging a Dell that has UEFI enabled - fails

[Jerousek, Jeff]

How are you deploying the Task Sequence?

Is this set?
[cid:image001.png@01D2A478.228A1070]

If you don't tell it to access content directly it tries to download it on to a 
disk, if it's bitLocked it can't download anything.

Niall Brady has some interesting posts on creating a partition for this when 
doing an In-Place Install on a bitLocked drive.

Thanks,
Jeff Jerousek

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 7:50 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

I should note that we also have a task sequence where we deploy Windows 7 with 
bitlocker.
We have no issues reimaging these machines. We do not get any errors.

It seems weird that on a UEFI system a reimage fails.

Also a note that the out of box Dell we got, was already bitlockered, so when 
we ran the TS to reimage it, we had no issues until we wanted to reimage the 
machine.

I guess I need to dig a lot deeper into what is happening in bitlocker that may 
be causing this issue.

Kevin

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 8:08 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

When you attempt the 2nd build (where you're getting the error) is it 
originating from a PXE boot or is the task sequence starting from within the 
full OS?

If you're PXE booting it, do you have a script to unlock BitLocker so that 
WinPE can access the disk?  If not then that is probably what is causing the 
problem.  You PXE boot and WinPE cannot access the BitLocker encrypted drive.  
It sees that the drive is there but it cannot access the partition(s) so it 
kicks back the error that the drive must be formatted.

Mike



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 7:33 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

Yes the drive is using bitlocker.

Kevin

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 7:14 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

Are you encrypting the drive at all?

Mike


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 6:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Reimaging a Dell that has UEFI enabled - fails

We have a brand new out of the box Dell E7270 Latitude. The machine comes with 
UEFI already configured and we are imaging it with Windows 10.

We PXE boot the machine, go through our SCCM task sequences to image the 
machine and everything appears to be great.

We take this same machine we just imaged, remove it from SCCM and go to reimage 
this machine and right after we choose our Win10 Task Sequence we get the 
following message every time:

"The task sequence was unable to locate a logical drive. The hard disk will 
need to be partitioned and formatted. Click OK to continue or Cancel to exit 
the task sequence"

We have a bunch of older machines, that we do a BIOS to UEFI (which works fine) 
TS then image the machine same as above but again, when we want to reimage the 
same machine we get that same error each time.

What we have done in the past is before we have to put in our SCCM TS password, 
we hit F8 and do a diskpart manually to wipe the disk, but this seems counter 
intuitive as the task sequence should be able to wipe the drive anyways as part 
of the task sequence.
Plus when we do this, it does not seem to image properly after words meaning it 
fails each time.

Has anyone seen this issue before? Is there something different we need to add 
to our TS in order for this to work?

Thanks,

KEVIN JOHNSTON



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



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

[mssms] RE: Reimaging a Dell that has UEFI enabled - fails

[Fusco, Brendan]

We also use BitLocker and have seen similar issues in the past. We now use a 
prestart script on our ConfigMgr boot media that offers the imaging technician 
the option to wipe the partition table (basically launch diskpart, select disk 
0, clean). This seems to have addressed all of the issues that we faced with 
reimaging existing machines with BitLocker encrypted disks in a wipe-and-reload 
scenario.

Brendan A. Fusco
Infrastructure Operations Architect
DePaul University Information Services

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Fast, David D.
Sent: Friday, March 24, 2017 8:44 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

I see the same thing when re-imaging a W10 Bitlockered system, would be 
interested in what you find out.

David


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 7:50 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

I should note that we also have a task sequence where we deploy Windows 7 with 
bitlocker.
We have no issues reimaging these machines. We do not get any errors.

It seems weird that on a UEFI system a reimage fails.

Also a note that the out of box Dell we got, was already bitlockered, so when 
we ran the TS to reimage it, we had no issues until we wanted to reimage the 
machine.

I guess I need to dig a lot deeper into what is happening in bitlocker that may 
be causing this issue.

Kevin

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 8:08 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

When you attempt the 2nd build (where you're getting the error) is it 
originating from a PXE boot or is the task sequence starting from within the 
full OS?

If you're PXE booting it, do you have a script to unlock BitLocker so that 
WinPE can access the disk?  If not then that is probably what is causing the 
problem.  You PXE boot and WinPE cannot access the BitLocker encrypted drive.  
It sees that the drive is there but it cannot access the partition(s) so it 
kicks back the error that the drive must be formatted.

Mike



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 7:33 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

Yes the drive is using bitlocker.

Kevin

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 7:14 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

Are you encrypting the drive at all?

Mike


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 6:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Reimaging a Dell that has UEFI enabled - fails

We have a brand new out of the box Dell E7270 Latitude. The machine comes with 
UEFI already configured and we are imaging it with Windows 10.

We PXE boot the machine, go through our SCCM task sequences to image the 
machine and everything appears to be great.

We take this same machine we just imaged, remove it from SCCM and go to reimage 
this machine and right after we choose our Win10 Task Sequence we get the 
following message every time:

"The task sequence was unable to locate a logical drive. The hard disk will 
need to be partitioned and formatted. Click OK to continue or Cancel to exit 
the task sequence"

We have a bunch of older machines, that we do a BIOS to UEFI (which works fine) 
TS then image the machine same as above but again, when we want to reimage the 
same machine we get that same error each time.

What we have done in the past is before we have to put in our SCCM TS password, 
we hit F8 and do a diskpart manually to wipe the disk, but this seems counter 
intuitive as the task sequence should be able to wipe the drive anyways as part 
of the task sequence.
Plus when we do this, it does not seem to image properly after words meaning it 
fails each time.

Has anyone seen this issue before? Is there something different we need to add 
to our TS in order for this to work?

Thanks,

KEVIN JOHNSTON



**

[mssms] RE: Reimaging a Dell that has UEFI enabled - fails

[Fast, David D.]

I see the same thing when re-imaging a W10 Bitlockered system, would be 
interested in what you find out.

David


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 7:50 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

I should note that we also have a task sequence where we deploy Windows 7 with 
bitlocker.
We have no issues reimaging these machines. We do not get any errors.

It seems weird that on a UEFI system a reimage fails.

Also a note that the out of box Dell we got, was already bitlockered, so when 
we ran the TS to reimage it, we had no issues until we wanted to reimage the 
machine.

I guess I need to dig a lot deeper into what is happening in bitlocker that may 
be causing this issue.

Kevin

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 8:08 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

When you attempt the 2nd build (where you're getting the error) is it 
originating from a PXE boot or is the task sequence starting from within the 
full OS?

If you're PXE booting it, do you have a script to unlock BitLocker so that 
WinPE can access the disk?  If not then that is probably what is causing the 
problem.  You PXE boot and WinPE cannot access the BitLocker encrypted drive.  
It sees that the drive is there but it cannot access the partition(s) so it 
kicks back the error that the drive must be formatted.

Mike



From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 7:33 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

Yes the drive is using bitlocker.

Kevin

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 7:14 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

Are you encrypting the drive at all?

Mike


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 6:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Reimaging a Dell that has UEFI enabled - fails

We have a brand new out of the box Dell E7270 Latitude. The machine comes with 
UEFI already configured and we are imaging it with Windows 10.

We PXE boot the machine, go through our SCCM task sequences to image the 
machine and everything appears to be great.

We take this same machine we just imaged, remove it from SCCM and go to reimage 
this machine and right after we choose our Win10 Task Sequence we get the 
following message every time:

"The task sequence was unable to locate a logical drive. The hard disk will 
need to be partitioned and formatted. Click OK to continue or Cancel to exit 
the task sequence"

We have a bunch of older machines, that we do a BIOS to UEFI (which works fine) 
TS then image the machine same as above but again, when we want to reimage the 
same machine we get that same error each time.

What we have done in the past is before we have to put in our SCCM TS password, 
we hit F8 and do a diskpart manually to wipe the disk, but this seems counter 
intuitive as the task sequence should be able to wipe the drive anyways as part 
of the task sequence.
Plus when we do this, it does not seem to image properly after words meaning it 
fails each time.

Has anyone seen this issue before? Is there something different we need to add 
to our TS in order for this to work?

Thanks,

KEVIN JOHNSTON



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



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



The information transmitted is intended only for the person or entity to which 
it is addressed and may contain confidential and/or privileged material. Any 
review, retransmission, dissemination or other use of, or taking of any action 
in reliance 

[mssms] RE: Reimaging a Dell that has UEFI enabled - fails

[Kevin Johnston]

I should note that we also have a task sequence where we deploy Windows 7 with 
bitlocker.
We have no issues reimaging these machines. We do not get any errors.

It seems weird that on a UEFI system a reimage fails.

Also a note that the out of box Dell we got, was already bitlockered, so when 
we ran the TS to reimage it, we had no issues until we wanted to reimage the 
machine.

I guess I need to dig a lot deeper into what is happening in bitlocker that may 
be causing this issue.

Kevin

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 8:08 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

When you attempt the 2nd build (where you're getting the error) is it 
originating from a PXE boot or is the task sequence starting from within the 
full OS?

If you're PXE booting it, do you have a script to unlock BitLocker so that 
WinPE can access the disk?  If not then that is probably what is causing the 
problem.  You PXE boot and WinPE cannot access the BitLocker encrypted drive.  
It sees that the drive is there but it cannot access the partition(s) so it 
kicks back the error that the drive must be formatted.

Mike



From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 7:33 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

Yes the drive is using bitlocker.

Kevin

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 7:14 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

Are you encrypting the drive at all?

Mike


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 6:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Reimaging a Dell that has UEFI enabled - fails

We have a brand new out of the box Dell E7270 Latitude. The machine comes with 
UEFI already configured and we are imaging it with Windows 10.

We PXE boot the machine, go through our SCCM task sequences to image the 
machine and everything appears to be great.

We take this same machine we just imaged, remove it from SCCM and go to reimage 
this machine and right after we choose our Win10 Task Sequence we get the 
following message every time:

"The task sequence was unable to locate a logical drive. The hard disk will 
need to be partitioned and formatted. Click OK to continue or Cancel to exit 
the task sequence"

We have a bunch of older machines, that we do a BIOS to UEFI (which works fine) 
TS then image the machine same as above but again, when we want to reimage the 
same machine we get that same error each time.

What we have done in the past is before we have to put in our SCCM TS password, 
we hit F8 and do a diskpart manually to wipe the disk, but this seems counter 
intuitive as the task sequence should be able to wipe the drive anyways as part 
of the task sequence.
Plus when we do this, it does not seem to image properly after words meaning it 
fails each time.

Has anyone seen this issue before? Is there something different we need to add 
to our TS in order for this to work?

Thanks,

KEVIN JOHNSTON



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



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

[mssms] RE: Reimaging a Dell that has UEFI enabled - fails

[Kevin Johnston]

Interesting

The 2nd attempt is within PXE, and I do not have any script to unlock the disk 
prior to it being wiped again.

I guess I would have expected others in the blog-o-sphere to have witnessed 
this issue before, maybe I just never come across a posting about this. It 
never even occurred to me about the disk being locked, even though that makes 
total sense.

So now I need to have a script run before I can choose my TS, to be able to 
unlock the disk to allow it to wipe...

Kevin

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 8:08 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

When you attempt the 2nd build (where you're getting the error) is it 
originating from a PXE boot or is the task sequence starting from within the 
full OS?

If you're PXE booting it, do you have a script to unlock BitLocker so that 
WinPE can access the disk?  If not then that is probably what is causing the 
problem.  You PXE boot and WinPE cannot access the BitLocker encrypted drive.  
It sees that the drive is there but it cannot access the partition(s) so it 
kicks back the error that the drive must be formatted.

Mike



From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 7:33 AM
To: mssms@lists.myitforum.com
Subject: [mssms] RE: Reimaging a Dell that has UEFI enabled - fails

Yes the drive is using bitlocker.

Kevin

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 7:14 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

Are you encrypting the drive at all?

Mike


From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 6:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Reimaging a Dell that has UEFI enabled - fails

We have a brand new out of the box Dell E7270 Latitude. The machine comes with 
UEFI already configured and we are imaging it with Windows 10.

We PXE boot the machine, go through our SCCM task sequences to image the 
machine and everything appears to be great.

We take this same machine we just imaged, remove it from SCCM and go to reimage 
this machine and right after we choose our Win10 Task Sequence we get the 
following message every time:

"The task sequence was unable to locate a logical drive. The hard disk will 
need to be partitioned and formatted. Click OK to continue or Cancel to exit 
the task sequence"

We have a bunch of older machines, that we do a BIOS to UEFI (which works fine) 
TS then image the machine same as above but again, when we want to reimage the 
same machine we get that same error each time.

What we have done in the past is before we have to put in our SCCM TS password, 
we hit F8 and do a diskpart manually to wipe the disk, but this seems counter 
intuitive as the task sequence should be able to wipe the drive anyways as part 
of the task sequence.
Plus when we do this, it does not seem to image properly after words meaning it 
fails each time.

Has anyone seen this issue before? Is there something different we need to add 
to our TS in order for this to work?

Thanks,

KEVIN JOHNSTON



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



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

[mssms] RE: Reimaging a Dell that has UEFI enabled - fails

[Kevin Johnston]

Yes the drive is using bitlocker.

Kevin

From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Marable, Mike
Sent: Friday, March 24, 2017 7:14 AM
To: mssms@lists.myitforum.com
Subject: [BULK] [mssms] RE: Reimaging a Dell that has UEFI enabled - fails
Importance: Low

Are you encrypting the drive at all?

Mike


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 6:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Reimaging a Dell that has UEFI enabled - fails

We have a brand new out of the box Dell E7270 Latitude. The machine comes with 
UEFI already configured and we are imaging it with Windows 10.

We PXE boot the machine, go through our SCCM task sequences to image the 
machine and everything appears to be great.

We take this same machine we just imaged, remove it from SCCM and go to reimage 
this machine and right after we choose our Win10 Task Sequence we get the 
following message every time:

"The task sequence was unable to locate a logical drive. The hard disk will 
need to be partitioned and formatted. Click OK to continue or Cancel to exit 
the task sequence"

We have a bunch of older machines, that we do a BIOS to UEFI (which works fine) 
TS then image the machine same as above but again, when we want to reimage the 
same machine we get that same error each time.

What we have done in the past is before we have to put in our SCCM TS password, 
we hit F8 and do a diskpart manually to wipe the disk, but this seems counter 
intuitive as the task sequence should be able to wipe the drive anyways as part 
of the task sequence.
Plus when we do this, it does not seem to image properly after words meaning it 
fails each time.

Has anyone seen this issue before? Is there something different we need to add 
to our TS in order for this to work?

Thanks,

KEVIN JOHNSTON



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

RE: [mssms] Reimaging a Dell that has UEFI enabled - fails

[Jeff Poling]

Is this an MDT integrated TS? If so, that message is from an mdt script….don't 
have the exact name off the top of my head.  If you click OK, it should perform 
the partition and format step, then proceed.

Jeff

Sent from my Windows 10 phone

From: Kevin Johnston
Sent: Friday, March 24, 2017 5:51 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Reimaging a Dell that has UEFI enabled - fails

We have a brand new out of the box Dell E7270 Latitude. The machine comes with 
UEFI already configured and we are imaging it with Windows 10.

We PXE boot the machine, go through our SCCM task sequences to image the 
machine and everything appears to be great.

We take this same machine we just imaged, remove it from SCCM and go to reimage 
this machine and right after we choose our Win10 Task Sequence we get the 
following message every time:

“The task sequence was unable to locate a logical drive. The hard disk will 
need to be partitioned and formatted. Click OK to continue or Cancel to exit 
the task sequence”

We have a bunch of older machines, that we do a BIOS to UEFI (which works fine) 
TS then image the machine same as above but again, when we want to reimage the 
same machine we get that same error each time.

What we have done in the past is before we have to put in our SCCM TS password, 
we hit F8 and do a diskpart manually to wipe the disk, but this seems counter 
intuitive as the task sequence should be able to wipe the drive anyways as part 
of the task sequence.
Plus when we do this, it does not seem to image properly after words meaning it 
fails each time.

Has anyone seen this issue before? Is there something different we need to add 
to our TS in order for this to work?

Thanks,

KEVIN JOHNSTON

[mssms] RE: Reimaging a Dell that has UEFI enabled - fails

[Marable, Mike]

Are you encrypting the drive at all?

Mike


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Kevin Johnston
Sent: Friday, March 24, 2017 6:46 AM
To: mssms@lists.myitforum.com
Subject: [mssms] Reimaging a Dell that has UEFI enabled - fails

We have a brand new out of the box Dell E7270 Latitude. The machine comes with 
UEFI already configured and we are imaging it with Windows 10.

We PXE boot the machine, go through our SCCM task sequences to image the 
machine and everything appears to be great.

We take this same machine we just imaged, remove it from SCCM and go to reimage 
this machine and right after we choose our Win10 Task Sequence we get the 
following message every time:

"The task sequence was unable to locate a logical drive. The hard disk will 
need to be partitioned and formatted. Click OK to continue or Cancel to exit 
the task sequence"

We have a bunch of older machines, that we do a BIOS to UEFI (which works fine) 
TS then image the machine same as above but again, when we want to reimage the 
same machine we get that same error each time.

What we have done in the past is before we have to put in our SCCM TS password, 
we hit F8 and do a diskpart manually to wipe the disk, but this seems counter 
intuitive as the task sequence should be able to wipe the drive anyways as part 
of the task sequence.
Plus when we do this, it does not seem to image properly after words meaning it 
fails each time.

Has anyone seen this issue before? Is there something different we need to add 
to our TS in order for this to work?

Thanks,

KEVIN JOHNSTON


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

[mssms] Reimaging a Dell that has UEFI enabled - fails

[Kevin Johnston]

We have a brand new out of the box Dell E7270 Latitude. The machine comes with 
UEFI already configured and we are imaging it with Windows 10.

We PXE boot the machine, go through our SCCM task sequences to image the 
machine and everything appears to be great.

We take this same machine we just imaged, remove it from SCCM and go to reimage 
this machine and right after we choose our Win10 Task Sequence we get the 
following message every time:

"The task sequence was unable to locate a logical drive. The hard disk will 
need to be partitioned and formatted. Click OK to continue or Cancel to exit 
the task sequence"

We have a bunch of older machines, that we do a BIOS to UEFI (which works fine) 
TS then image the machine same as above but again, when we want to reimage the 
same machine we get that same error each time.

What we have done in the past is before we have to put in our SCCM TS password, 
we hit F8 and do a diskpart manually to wipe the disk, but this seems counter 
intuitive as the task sequence should be able to wipe the drive anyways as part 
of the task sequence.
Plus when we do this, it does not seem to image properly after words meaning it 
fails each time.

Has anyone seen this issue before? Is there something different we need to add 
to our TS in order for this to work?

Thanks,

KEVIN JOHNSTON

RE: [mssms] RE: Windows Update Issues

[Mawdsley R.]

Bet it'll be the dual Nic.. You may need to configure IIS on the WSUS server to 
"Listen To all IPs".

Rich Mawdsley


From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] On 
Behalf Of Collin Murphy
Sent: 23 March 2017 17:50
To: Sherry Kissinger ; mssms@lists.myitforum.com
Subject: RE: [mssms] RE: Windows Update Issues

Rapid fail is off (Set to false)

When the app pool fails now it pops a .NET error on a pop up screen

35GB RAM allocated (out of 40GB)...but only 2000 clients

I did notice the NIC is at 50Mbps consistently

This system is also dual homes between two different networks.  The non-client 
network is not registering its DNS and pings from clients are resolving 
correctly.

Thank you

Sent from Mail for Windows 10

From: Sherry Kissinger
Sent: Thursday, March 23, 2017 1:21 PM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] RE: Windows Update Issues

https://www.mnscug.org/blogs/brian-mason/361-how-to-melt-a-sup

Disable RapidFail?  How much memory do you have allocated?

On Thu, Mar 23, 2017 at 11:20 AM, Collin Murphy 
> wrote:
Hello,

I have read that site often.  The wsus app pool will crash after some time 
after it has consumed all of the resources on that system (8 Procs, 32GB RAM).

I do not have any idea why the app pool would be consuming such a large amount 
of resources.

Sent from Mail for Windows 10

From: Sherry Kissinger
Sent: Thursday, March 23, 2017 11:42 AM
To: mssms@lists.myitforum.com
Subject: Re: [mssms] RE: Windows Update Issues

If you haven't read this... 
http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/

Maybe your sup apppool is crashing?

On Thu, Mar 23, 2017 at 9:48 AM, Mawdsley R. 
> wrote:
Check what your WindowsUpdate.log is saying, will give a more direct error.

When was the last time you cleaned up the Wsus database?

Thank you
Rich Mawdsley

From: listsad...@lists.myitforum.com 
[mailto:listsad...@lists.myitforum.com] 
On Behalf Of Collin Murphy
Sent: 23 March 2017 13:57
To: mssms@lists.myITforum.com
Subject: [mssms] Windows Update Issues

Hello,

Site: SCCM 1610 w/ KB3214042

I am experiencing significant issues with clients receiving updates.  Out of 
1500 systems 201 are compliant, 131 are non-compliant, and the remaining 1200 
are all in an Unknown State.

I have uninstalled WSUS, installed again, re-index, WSUS cleanup tasks, and 
still the same issue.  The IIS WSUS App Pool is taking up almost 32GB of RAM 
which seems very odd.


>From the WUAHandler.log I am seeing these errors on a client:



OnSearchComplete - Failed to end search job. Error = 0x80244007.

Scan failed with error = 0x80244007.



OnSearchComplete - Failed to end search job. Error = 0x8024401c.

Scan failed with error = 0x8024401c.



OnSearchComplete - Failed to end search job. Error = 0x80240440.

Scan failed with error = 0x80240440.



OnSearchComplete - Failed to end search job. Error = 0x8024402c.

Scan failed with error = 0x8024402c.




>From the ScanAgent.log I am seeing these errors on the same client as the 
>previous WUAHandler.log



CScanAgent::ScanCompleteCallback - failed at OnScanComplete with 
error=0x87d00631


I have also run this PS

get-hotfix | Where-Object {$_.installedon -gt (get-date).addmonths(-5)} | 
Sort-Object -property installedOn -Descending

The only results that are showing are updates installed from November of 2016.


I can provide more information or log snips at any time.

Any ideas would be greatly appreciated.

Thank you










--
Thank you,

Sherry Kissinger

My Parameters:  Standardize. Simplify. Automate
Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, 
http://www.smguru.org





--
Thank you,

Sherry Kissinger

My Parameters:  Standardize. Simplify. Automate
Blogs: http://www.mofmaster.com, http://mnscug.org/blogs/sherry-kissinger, 
http://www.smguru.org