Installing the ADMT software + Password Migration Service
Creating a user list for migration
Migrating User objects + Passwords between AD Forests
Create connectivity between both AD Forests
There must be IP network connectivity between the DC’s in your Forests.
You need to configure conditional forwarders between your forests, so they can resolve one another.
On the source domain controller;
Open up the DNS console, and right click the Conditional Forwarder folder to create a new record.
Enter your target domain name and IP address/es of your domain controllers in the target domain. Select “store this conditional forwarder in active directory”, to replicate to other DCs in the source domain.
Error Code: LCMMIGRATION15102
vRSLCM Migration Failed with SSH is not enabled or Root credential invalid. Please make sure SSH is enabled or porvide the correct root credential by adding the credential to the home page locker app
Pretty obvious error, however the provided root credentials were correct, and I could use putty to connect to my existing LCM instance.
The best news about this release is the “easy installer“, which also allows you to migrate from older versions. In this post, I’ve documented the screenshots in steps for you, as I know many of you out there like to see the end to end process before you undergo an update yourself, so you know what to expect.
During this migration process the following will happen;
New LCM virtual appliance deployed
New IDM appliance deployed (unless you select to link to an existing environment)
Existing LCM settings and content will be migrated
In the event you are unable to upgrade before the End of General Support (EOGS) and are active on Support and Subscription, you have the option to purchase extended support in one year increments for up to two years beyond the EOGS date.
Expect this to be more costly than general support.
SLA’s are more akin to that of basic support rather than production support
Annual security patch. Includes catastrophic/critical security fixes only
Ability to create hot patches for Severity 1 issues only
Technical Guidance for vSphere 5.5 is available until September 19, 2020 primarily through the self-help portal.
During the Technical Guidance phase, VMware does not offer new hardware support, server/client/guest OS updates, new security patches or bug fixes unless otherwise noted.
For example, there was no SPECTRE/Meltdown security patches released for vSphere 5.1
It’s not only the core vSphere 5.5 products that are affected, as we can see from the End-of-Support tracking page provided by virten.net. There are other VMware solutions that you have deployed that may also need upgrading.