McAfee Endpoint Encryption 7.0 – Fatal Error: [0xEE0E0001]

Errors

1. Fatal Error [ee000007] Internal initialization error
2. Fatal error: File access error at startup 
3. Fatal error: 0xEE0D0001 - Failed to read registry file

Solution 1 :

If Expresscache application installed must remove else install Latest Lenovo Express cache tool.

ExpressCache software is incompatible with Opal and software disk encryption

Although this article specifically cites Lenovo, this issue is not unique to Lenovo systems. Since the original publishing date of this article, other manufacturers' systems, including Dell laptops, have been reported to also incur this issue.

Lenovo has reported the following issue with the licensed ExpressCache software with the following types of encryption products:

Refer Link:  https://kc.mcafee.com/corporate/index?page=content&id=KB82028

Senorio 2

Change the following registry items. Each has a DWORD called “Start” it will have a value of “3”. Change it to “0”

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\pciide
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\msahci
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStorV
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\iaStor
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\atapi
 Restart the PC, enter the BIOS and change the SATA Operation setting from “RAID On” to “AHCI”

Refer Link: https://benddiscount.com/2013/06/26/mcafee-endpoint-encryption-7-0-fatal-error-0xee0e0001/

vmware workstation hyper-v unsupported

Installing Hyper-V Role in VMware Workstation; error Hyper-V cannot be installed: A hypervisor is already running

1. Shut down the virtual machine.
2. Open the VM’s .VDX configuration file from the VM’s working directory.
3. Add the following three new entries to the .VDX configuration
4. In the last line we will add this code and save it:
5. After that edit the setting on VM from vmware workstation select Processors and check the 
            ✔ Virtualize Intel VT-x/EPT or AMD-V/RVI.
           ✔  Virtualize CPU Performance counters.

hypervisor.cpuid.v0 = “FALSE”

This option tricks the Windows Server 2012 into “thinking” it is not running in a virtualized instance

mce.enable = “TRUE”

This option enables Machine Check Exception (MCE), which enable the Windows Server 2012 VM to report CPU hardware issues

vhv.enable = “TRUE”  This option enables nested virtualization.

Now the configurations is done, now Power on this virtual machine and install Hyper-V Role.

503 service unavailable" error when connecting to vSphere Web Client

After Restart Vcenter windows server more than 1 hours the vSphere Web Client its showing  503 Service Unavailable issue.

some web research after found below solution thanks to TERENCE LUK

Solution:

Verify that vCenter Server services are running using this command (this can be ran on a Windows installation or Appliance):

Im using windows vcenter server.

service-control --status --all

From the vcenter windows server, 

C:\Program Files\VMware\vCenter Server\bin

here some service not starting.

the message is presented is if the Postgres database is unable to start thus causing the vCenter login portal to not load.  For this example, the reason why the Postgres database engine would not start is because the Windows Server hosting the vCenter services and Postgres database had the security permissions for the Log on as a batch job overwritten by a group policy in the domain.  This is what was displayed when I checked the vCenter Windows Server Log on as a batch job policy accounts:

my  domain policy disabled Log on as a batch job.

after some small changes my default domain policy.

Added these accounts to the Log on as a batch job policy of effective GPO. To add the accounts, navigate to Computer Configuration > Windows Settings >Security Settings>Local Policies > User Rights Assignment > Log on as a batch job

• cm
• content-library
• eam
• imagebuilder
• mbcs
• netdumper
• perfcharts
• rbd
• vapiEndpoint
• vmware-vpostgres
• vsan-health
• vsm
• vsphere-client
• vsphere-ui

Reboot the vCenter Server.

after restart vcenter server wailt 10 to 15 mints

check  the vCenter services by running this command:

service-control --start --all

you do not have permission view this object vcenter 6.5

vSphere vCenter error: You do not have permission to view this object or this object does not exist

vSphere 6.5 vCenter error: You do not have permission to view this object or this object does not exist

Windows AD account being used may not be administration member of the myadmin.com domain identity source domain provided by the vCenter Single Sign-On system.

Solution:

Log onto vCenter using the administrator account for the vsphere.local. 

In vSphere web client, navigate to Administration -> Single Sign On -> Users and Groups -> select the ADMINISTRATOR group name and add the Windows AD domain account or group to be used for administration of the vSphere infrastructure.

Add windows Login user Administrator group.