Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpeditor domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home1/briangon/public_html/wp-includes/functions.php on line 6114 Supportishere.com - Part 15
In Windows 8, the “Display Rotation Tool” is not a required application as published. If you are receiving the “Unsupported Touchpad Device” error and you have the correct Versapad touchpad driver installed, then simply un-install the Display Rotation Tool. All front panel buttons should still work, including the Display Rotation button.
The CF-19 Win8 x64 bundle was updated to address this error on 8/26/14: https://panaconsulting.egnyte.com/dl/gE7vj2e83e
UEFI requires x64 AND FAT32. FAT32 only supports up to 4GB file sizes. Image files (.WIMs) are normally well larger that this.
I came across a great blog post (Link Here). The guy updated the built-in LTIApply.swf to auto apply an SWM file if available. He also wrote a Powershell UI, which didn’t work for me. No matter, I pulled out the LTIApply.wsf he made, dropped it in my Media\Content\Deploy\Scripts folder (overwrite existing). And split my WIM using the imagex utility, which is builtin into Windows ADK.
Roughly every year each Toughbook model is either revved to the latest Intel Chipset, GPU, WWAN card, WLAN card, etc. In most cases, these changes do NOT change the first 5 characters of the model number. The forst 5, CF-19, CF-31, CF-53, normally do not change for up to 5 years. The reason behind it is Docking Stations!, people heavily invest on Docking Stations when installing them in vehicles and we also do when it comes to testing and working with Partners to properly protect the Toughbook and User when in use. The docking stations are normally tied to the 1st 5 characters of the model, and rely on the chassis staying the same for as long as possible. We lead the industry in this regard averaging roughly 5 revisions/marks before changing our chassis.
This is a great resource to quickly determine what “Mark” level a Toughbook model is.
New method for enabling TPM is to enable it via WinPE before the OS is applied. See video below. And here is the script that was used.
https://gallery.technet.microsoft.com/scriptcenter/780d167f-2d57-4eb7-bd18-84c5293d93e3
Breakdown of units that display prompt and units that do not.
Display Prompts on enable:
CF-H2A (Mk1)
No Display of prompts: on enable:
CF-H2C (Mk2), CF-H2F (Mk3), FZ-G1A (Mk1), FZ-G1F (Mk2)
I also came across a very useful script that displays the status of the TPM in Windows. Make sure you run the VBS as an Administrator.
In Panasonic Toughbook’s BIOS’s you MUST set the Supervisor Password in order to enable the TPM chip. If you are not fond of having a supervisor password, or wish to enable TPM programmatically, try the following.
Use the built-in Windows command line tool “manage-bde”.
manage-bde.exe -tpm -TurnOn
On older Toughbook laptops (i.e. pre-31Mk2, 19Mk2, 53), you may need to perform a “Shutdown” and manual “Power-On”. See image below for example prompt. There is NO way around this, other than getting a custom BIOS produced. On older Toughbook models like the pre-31Mk2, 19Mk2, 53, encountering a need for a “Shutdown” and manual “Power-On” might sometimes be the norm. In cases like these, there’s often no way around this process without resorting to a custom BIOS. Additionally, when dealing with these older models, using laptop docking stations might offer a workaround or added convenience. These docking stations can provide extra ports, charging capabilities, and streamline connectivity, potentially mitigating the need for frequent shutdowns and manual restarts by ensuring a smoother, more comprehensive system setup.
* Newer prompt appears even when Task Sequence triggers a reboot after executing “manage-bde ..” command.
If you are still running into issues enabling TPM, try the “EnableBitLocker.vbs” script. If TPM is not enabled, on 1st run it will auto enable it, and on 2nd run it will enable BitLocker.
And lastly, if you are still having issues, request a custom BIOS be produced for your Organization with the TPM already enabled. This can take a couple of weeks to get produced, but may end up being the best option for your situation.
Once TPM is enabled, you can now initiate BitLocker, which is best done via GPO. I suggest this, because there is a GPO setting, which enforces the Toughbook/pad to backup the recovery key to AD before initiating BitLocker (Require BitLocker backup to AD DS)