Add me in as well!

Sent from my iPhone

On Jul 31, 2017, at 9:43 PM, Ashutosh Mishra 
<ashutosh3...@gmail.com<mailto:ashutosh3...@gmail.com>> wrote:

I would also be interested in your BIOS scripts? If you could share please.

Regards,
Ashu

On 1 August 2017 at 01:24, Troy Nines 
<troy.ni...@franklin.edu<mailto:troy.ni...@franklin.edu>> wrote:
Chris,

I'd also be interesting in see your BIOS script(s)

Thanks,
Troy

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com>] 
On Behalf Of Bateman, Vern
Sent: Sunday, July 30, 2017 10:24 AM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: RE: [MDT-OSD] HP EliteBook 840 G4 and 850 G4

Chris,

I would be interested in seeing your BIOS script as well..

Thanks,

Vern Bateman

From: listsad...@lists.myitforum.com<mailto:listsad...@lists.myitforum.com> 
[mailto:listsad...@lists.myitforum.com] On Behalf Of Brucker, Chris
Sent: Thursday, July 27, 2017 4:08 PM
To: mdtosd@lists.myitforum.com<mailto:mdtosd@lists.myitforum.com>
Subject: Re: [MDT-OSD] HP EliteBook 840 G4 and 850 G4

We update the BIOS for all of our models each month. So far it works out pretty 
well. I'm happy to share the scripts that we use if you are interested.

Thanks,
Chris Brucker

On Jul 27, 2017, at 6:00 PM, Ryan Dunt 
<ryan.d...@bakertilly.com<mailto:ryan.d...@bakertilly.com>> wrote:
CAUTION: The e-mail below is from an EXTERNAL source. Please do not open 
attachments or click links from an unknown or suspicious origin.

We just ran into an issue with imaging 840 and 850 G4 via SCCM. The TS would 
bomb out on BitLocker and also failed when turning of BitLocker steps in the TS 
and trying to manually encrypt after TS is complete. After some back and forth 
with HP and digging on our own, we found the culprit to be BIOS v1.05 to be the 
root cause. We have some "older" G4s that had v1.03 and they worked fine. The 
200 machines we recently ordered shipped with 1.05 and ruined our lives for a 
couple days, but when running the BIOS update from within the BIOS. It found 
1.06 was available. This update was nowhere to be found during our searches 
earlier this week. Magically it is now available on HPs site.

Needless to say getting the machines to v1.06 resolved the issue.

Seems like these BIOS updates are coming out quite often. Do others proactively 
update BIOS or only as needed when an issue in your environment arises?

Thanks,
Ryan
Baker Tilly Virchow Krause, LLP Confidentiality Notice: This message is being 
sent by Baker Tilly Virchow Krause, LLP. It is intended exclusively for the 
individuals and entities to which it is addressed. This communication, 
including any attachments, may contain information that is proprietary, 
privileged, confidential, including information that is protected under the 
HIPAA privacy rules, or otherwise legally exempt from disclosure. If you are 
not the named addressee, you are not authorized to read, print, retain, copy or 
disseminate this message or any part of it. If you have received this message 
in error, please notify the sender immediately by email and delete all copies 
of this message. This message is protected by applicable legal privileges and 
is confidential. Tax advice, if any, contained in this communication was not 
intended or written to be used by any taxpayer for the purpose of avoiding 
penalties.
________________________________
The information contained in this message from First Financial Bancorp or its 
affiliates and any attachments are confidential. It is not intended for 
transmission to, or receipt by, anyone other than the addressee(s), or a person 
authorized to deliver it to the named addressee(s). If you have received this 
message in error, you are prohibited from copying, distributing or using the 
information. Please contact the sender immediately by return email and delete 
the original message.

You've received this email from someone at Affinity Credit Union. We understand 
- you get a lot of emails and may not want to get any more from us. We'll be 
sad to see you go, but you can unsubscribe from our mailing list by clicking on 
this 
link<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.affinitycu.ca%2FYourCreditUnion%2FContactUs%2FPages%2Funsubscribe.aspx&data=02%7C01%7Ctroy.nines%40franklin.edu%7C9a92af3566d140da5fe408d4d756ef71%7C5f846636437d46ba9152d0632a997016%7C0%7C0%7C636370215770819026&sdata=LT5eUgeMLAcJGLerlvBjWMvP3d4tn%2Fdjf%2FJSxtReDxU%3D&reserved=0>.

________________________________

CONFIDENTIALITY STATEMENT MESSAGE: This e-mail and any attachments may contain 
confidential and privileged information. It is intended for the sole use of the 
individual(s) to whom it is specifically addressed and should not be read by, 
or delivered to, any other person. The act of having communicated by email in 
no way waives any privilege or confidentiality that may be claimed over these 
communications. If you are not the intended recipient, please notify the sender 
immediately by return e-mail, delete this e-mail and destroy all copies. Any 
dissemination or use of this information by a person other than the intended 
recipient is not authorized and may be illegal. We thank you in advance for 
your cooperation. Affinity Credit Union is committed to protecting personal 
information in a manner that is accurate, confidential, secure, and 
responsible. We have taken precautions against viruses, but take no 
responsibility for loss or damage that may be caused by its contents. Unless 
otherwise stated, opinions expressed in this email are those of the author and 
are not necessarily endorsed by the author's employer.


________________________________

CONFIDENTIALITY NOTICE: This communication with its contents may contain 
confidential and/or legally privileged information. It is solely for the use of 
the intended recipient(s). Unauthorized interception, review, use or disclosure 
is prohibited and may violate applicable laws including the Electronic 
Communications Privacy Act. If you are not the intended recipient, please 
contact the sender and destroy all copies of the communication.

Reply via email to