Ensure full DNS resolution is in place before starting of the host name of the appliance.
Be aware unless licensed the PowerPathVE has a 45 day trail license.
The PowerPathVE Virtual Appliance will support multiple vCenters.
Create a AD service account
Create a new Role in vCenter called “PowerPathVE licensing”
Assign the role the following permissions in vCenter
Global | Health
Host | CIM | CIM Interaction
Assign permissions for the AD USer created with this new role at the vCenter Level in vCenter
At the DC level create a Network Protocol Profile in vCenter if one doesn’t exist this is based on the PortGroup the vm will be for deployment
Give it a name and confirm which PortGroup it will be associated with
Set up IP4 Info, do not enable
Leave IP6 blank
Set DNS and Proxy if required
Confirm the changes
Deploy OVF, via the normal vCenter wizard, follow the defaults until network settings.
Select the port group you associated the Network Profile with initially at step 2d
Then customize the image as required in the design and set Root password as per deployment wizard
Confirm changes and select to power on after completion.
Once booted up, access the console
Agree to license
Once booted and license is accepted and you have a login prompt at the console, open a browser and go to https://hostname/,. you will be presented with the EMC login page.
Login using Root and password created during the OVF Deployment
Go to the Vmware vCenter Servers Tab
Add vCenter using the credentails created earlier
You will see the host connected, with a username and green tick, it will take a few minutes for the data to update
After this the PowerPath Licenses must be installed.
SRM EXtra step