I’ve bought this used Z620, currently the system doesn’t have any OS installed or storage device attached. I’m just testing/checking the Intel AMT/MEBX of this workstation.
Configuration:
BIOS: latest version v3.96
Chipset (from HWInfo): Intel C602 (Patsburg-A) (Upgrade ROM0 (base))
CPU: Xeon E5-2695v2
Graphic card: Quadro K620.
Intel AMT option is enabled in the BIOS, but I don’t see any method to access the MEBx to configure. Nothing in the one-time boot menu, POST messages, or press Ctrl + P (said to be the combination key to access Intel MEBx) doesn’t trigger anything. Viewing the “System Information” in the BIOS, the following two options are marked as Disabled:
- ME Firmware Version
- ME Management Mode
I’ve tried installing Windows 10 and ran the Intel ME firmware update installer (latest version 71913272-81723002 Rev.A downloaded from [1]). However, the ME firmware installer also gave out some error 8743 about firmware not available/ not connected (?!)
How do I enable them? Thanks.
[1]: https://support.hp.com/gb-en/drivers/sel…station/5225037
EDIT: Edited to list full configuration in the 1st post.
What is the PCH (chipset) of the motherboard and what CPU is currently installed? Download Intel (Converged Security) Management Engine: Drivers, Firmware and Tools > ME System Tools v8, run MEInfo -verbose and show me the results.
Thanks.
The Chipset (from HWInfo): Intel C602 (Patsburg-A) (Upgrade ROM0 (base))
CPU: Xeon E5-2695v2
As the HP website says the workstation may have v7 or v8, so beside the results from MEInfo v8, I also post results from MEInfo v7 below.
V8:
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.
FW Status Register1: 0x00004181
FW Status Register2: 0x163B0100
CurrentState: Init
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: Bring Up
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: Debug Error
ModeOfOperation: Normal
ICC: No valid OEM data, ICC not programmed
PhaseStatus: UNKNOWN
HECI device is found to be disabled.
Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Windows OS Version : 6.2.9200 ""
OS BIOS Support : UEFI
Table Type 0 ( 0x 00 ) found, size of 24 (0x 18 ) bytes
Table Type 1 ( 0x 01 ) found, size of 27 (0x 1B ) bytes
Table Type 2 ( 0x 02 ) found, size of 15 (0x 0F ) bytes
Table Type 3 ( 0x 03 ) found, size of 22 (0x 16 ) bytes
Table Type 4 ( 0x 04 ) found, size of 42 (0x 2A ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 7 ( 0x 07 ) found, size of 19 (0x 13 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 9 ( 0x 09 ) found, size of 17 (0x 11 ) bytes
Table Type 11 ( 0x 0B ) found, size of 5 (0x 05 ) bytes
Table Type 16 ( 0x 10 ) found, size of 23 (0x 17 ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 19 ( 0x 13 ) found, size of 31 (0x 1F ) bytes
Table Type 19 ( 0x 13 ) found, size of 31 (0x 1F ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 17 ( 0x 11 ) found, size of 34 (0x 22 ) bytes
Table Type 18 ( 0x 12 ) found, size of 23 (0x 17 ) bytes
Table Type 32 ( 0x 20 ) found, size of 20 (0x 14 ) bytes
Table Type 26 ( 0x 1A ) found, size of 22 (0x 16 ) bytes
Table Type 28 ( 0x 1C ) found, size of 22 (0x 16 ) bytes
Table Type 27 ( 0x 1B ) found, size of 15 (0x 0F ) bytes
Table Type 29 ( 0x 1D ) found, size of 22 (0x 16 ) bytes
Table Type 39 ( 0x 27 ) found, size of 22 (0x 16 ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 41 ( 0x 29 ) found, size of 11 (0x 0B ) bytes
Table Type 207 ( 0x CF ) found, size of 9 (0x 09 ) bytes
Table Type 13 ( 0x 0D ) found, size of 22 (0x 16 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 8 ( 0x 08 ) found, size of 9 (0x 09 ) bytes
Table Type 127 ( 0x 7F ) found, size of 4 (0x 04 ) bytes
Error 9458: Communication error between application and Intel(R) ME module (FW Update client)
Error 9459: Internal error (Could not determine FW features information)
V7:
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Intel(R) MEInfo Version: 7.1.50.1166
Copyright(C) 2005 - 2011, Intel Corporation. All rights reserved.
Platform stepping value is 5
FW Status Register1: 0x00004181
FW Status Register2: 0x163B0100
CurrentState: Init
ManufacturingMode: Disabled
FlashPartition: Valid
OperationalState: Bring Up
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: Debug Error
ModeOfOperation: Normal
ICC: No valid OEM data, ICC not programmed
PhaseStatus: UNKNOWN
HECI device is found to be disabled.
SMBIOS Table Data
Starting address: 0
Table Size in Bytes: 0 ( 0x0 )
Number of Table Entries: 0 ( 0x0 )
Virtual mapping of complete Table: 2 4kB Pages
PMXUtil: Error during PMX Call: PMxDrv!MAPPHYS - Bad Input Parameters
SM BIOS table entry point structure not found
SMBIOS Table Data
Starting address: 0
Table Size in Bytes: 0 ( 0x0 )
Number of Table Entries: 0 ( 0x0 )
Virtual mapping of complete Table: 2 4kB Pages
PMXUtil: Error during PMX Call: PMxDrv!MAPPHYS - Bad Input Parameters
SM BIOS table entry point structure not found
Error 1002: Failed to retrieve Intel (R) ME FW Version
Error 9458: Communication error between application and Intel(R) ME module (FW Update client)
Error 9459: Internal error (Could not determine FW features information)
The PCH and CPU are vPro compatible but the ME firmware is corrupted. It needs to be repaired first. You need read/write access to the ME region of the SPI/BIOS chip. Follow [Guide] Unlock Intel Flash Descriptor Read/Write Access Permissions for SPI Servicing to check if you have read/write access and how to get it otherwise.
I don’t really understand on the calculation of Yes/No bits mentioned in "B. Read/Write Access Permissions" section in the linked guide. However, I managed to get the following info:
1. HP Z620’s Maintenance Guide indicates that the motherboard has a "ME/AMT flash override" header. It’s a 3 pin header, so I changed the jumper.
Intel(R) MEInfo Version: 8.1.56.1541
Copyright(C) 2005 - 2014, Intel Corporation. All rights reserved.
FW Status Register1: 0x1E040192
FW Status Register2: 0x10520100
CurrentState: Recovery
ManufacturingMode: Enabled
FlashPartition: Valid
OperationalState: Bring Up
InitComplete: Initializing
BUPLoadState: Success
ErrorCode: No Error
ModeOfOperation: Unsecured mode by H/W jumper
ICC: No valid OEM data, ICC not programmed
PhaseStatus: UNKNOWN
2.
Intel (R) Flash Programming Tool. Version: 8.1.60.1561
Copyright (c) 2007 - 2014, Intel Corporation. All rights reserved.
Platform: Intel(R) Patsburg Chipset - Reserved DID 0x1D41
Reading HSFSTS register… Flash Descriptor: Valid
— Flash Devices Found —
W25Q128BV ID:0xEF4018 Size: 16384KB (131072Kb)
- Reading Flash [0x1000000] 16384KB of 16384KB - 100% complete.
Writing flash contents to file "spi.bin"…
Memory Dump Complete
FPT Operation Passed
3.
Intel (R) Flash Programming Tool. Version: 8.1.60.1561
Copyright (c) 2007 - 2014, Intel Corporation. All rights reserved.
Platform: Intel(R) Patsburg Chipset - Reserved DID 0x1D41
Reading HSFSTS register… Flash Descriptor: Valid
— Flash Devices Found —
W25Q128BV ID:0xEF4018 Size: 16384KB (131072Kb)
— Flash Image Information –
Signature: VALID
Number of Flash Components: 1
Component 1 - 16384KB (131072Kb)
Regions:
Descriptor - Base: 0x000000, Limit: 0x000FFF
BIOS - Base: 0x510000, Limit: 0xFFFFFF
ME - Base: 0x005000, Limit: 0x50FFFF
GbE - Base: 0x001000, Limit: 0x002FFF
PDR - Base: 0x003000, Limit: 0x004FFF
Master Region Access:
CPU/BIOS - ID: 0x0000, Read: 0x1B, Write: 0x1A
ME - ID: 0x0000, Read: 0x0D, Write: 0x0C
GbE - ID: 0x0118, Read: 0x08, Write: 0x08
Total Accessable SPI Memory: 16384KB, Total Installed SPI Memory : 16384KB
FPT Operation Passed
0x1B, 0x1A, 0x0D etc… are what I don’t understand, don’t know if they are Yes or No. Still, hope that I’ve retrieved the correct information.
Alright, you found the FD unlock jumper so read/write access to the ME firmware is now possible. The latest BIOS package from HP does seem to include a full SPI/BIOS image so repairing will be easier. I extracted the ME region only, which I have attached below alongside the actual full SPI image (which probably won’t be required). Use Flash Programming Tool with command “fptw64 -me -f sp100699_J61_0396_ME.bin”, set the jumper back to its original position and run FPT again with command “fptw64 -greset”. After the reboot, your ME (and thus AMT) firmware should now be operational.
sp100699_J61_0396.rar (5.77 MB)
Thank you very much, @plutomaniac ! I was concerned that there would be some complicated instructions to follow, some hex-editing work to do etc… didn’t think someone would prepare all files ready-to-flash 
However, while waiting for your reply, I read some other threads ("Clean Dumped regions" and "ME Analyzer") and as I have never done these "chip re-flashing/re-programing", so to be sure that I’ll process the steps correctly, please let me ask some last questions. (And sorry if any wording is unpleasant, they’re not intentional, as I’m not a native English speaker).
1. The latest BIOS bin file v3.96 Rev A (from which you extracted the ME Region) has release date of 2019, but ME Analyzer detects that its ME version is 8.1.60.1561 dated from 2014.
While there was another "Firmware" section on the driver page which lists an "Intel Management Engine Firmware Update and Utilities" version 71913272-81723002 Rev.A. This, in turn, contains a "8.1.72.3002.bin" dated 2017 
So, should/may/is it possible to use this 2017 version? Or is it because we should just use the one that goes with the BIOS file first to see if it works, and then we’ll update the ME later?
Side note: The one dumped from my Z620 is 8.1.52.1496
2. The "…ME.bin" you attached still has
- "Descriptor Region> Descriptor Map> Number of Flash Components" set to 2.
- All anti-theft stuff is still left as is.
Is this totally normal? (The workstation doesn’t have any anti-theft, obviously. I’m just not sure about that "number of flash components")
3. HWInfo reports that the chipset is Patsburg A, but those bin files from HP all says Patsburg T. I guess this is totally normal, too?
4.
Does this mean I have to do it when the computer is still running (electricity is on)? Usually when I do things to computer motherboards, internal components etc… I turn off the computer and unplug all electric cords.
Once again, thank you.
1. When re-flashing the ME firmware at the SPI chip, it needs to be Configured with model specific settings (done by HP) so it the image type needs to be EXTR (as explained at the (CS)ME thread). The update provided at HP’s website is meant for FWUpdate tool, which does not deal with ME settings/data. You need to first flash a configured ME firmware and then update via FWUpdate tool to whatever you want and are able to. You could take the SPI image from HP, run it though [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization and use the latest ME firmware to create a pre-updated (ME firmware wise) SPI image but why go through all this trouble for no reason? You can just flash an EXTR ME firmware now, as provided by HP, and then use FWUpdate to update to the last (platform is EOL).
2. A ME firmware region image contains the ME firmware only, not the rest of the SPI/BIOS chip components. That includes Flash Descriptor. What you are seeing at FITC are placeholders. You can see the actual values if you load the full 16MB SPI image. Well, in your case, sort-of. As explained at D3.5 of [Guide] Clean Dumped Intel Engine (CS)ME/(CS)TXE Regions with Data Initialization, FITC v8 has various problems working with Patsburg (C600/X79) images so it is best to avoid messing with that particular combination. In your case, that’s not needed though because we have pre-made Configured ME firmware image (actually full SPI image) from HP themselves.
3. Doesn’t matter. Probably not even Intel understood those old Patsburg SKU names. Ignore it.
4. Yes, but you can do it however you want. Basically, once you re-flash you need to reset the jumper (otherwise the ME will remain in Recovery mode) and perform a global reset (CPU + ME) so that the ME can detect the changes and make itself + AMT operational again. Do it like this to be 100% safe: re-flash, shutdown, remove all power for 1 minute (AC w/o RTC, that triggers a manual global reset btw), reset the jumper, power on, run “fptw64 -greset” (for good measure) and after the reboot the ME/AMT/MEBx should be operational.
Thank you very much again for your very detailed explanation, @plutomaniac ! I flashed your fixed “…ME.bin” right away, performed the “100% safe” steps, and happy tears almost went out of my eyes when I saw the POST message “Press Ctrl+P to access MEBx setup…”, lol 
I performed some configuration and now I can do some remote actions, things are looking good. However, there is no KVM/Remote Desktop (i.e. view the live screen). Don’t know if it’s because this Z620 system doesn’t support or because there is not an Intel integrated graphic chip (did some quick search and saw some posts mentioning that).
Happy to hear it all worked out. From what I can see at FITC, all C600 SKUs have KVM disabled so it must be a PCH/CPU thing and yes, the lack of an iGPU is probably the reason.
Luckily I found Win-Raid. Used to bump into some threads here via google search. Intel AMT is not mandatory in my setup (just wanted to try it out) and didn’t expect I could get the solution from a non-HP forum, turned out it’s the opposite. Obviously, as a place for advanced users with deep knowledge on things related to BIOS, firmware etc…, this should be the first place I should look for solution of this issue 
So yeah, the issue is “officially” sorted out now. Thank you @plutomaniac , I’ll see if I still have any BIOS, firmware… things that need to be solved