Monthly Archives: March 2020

Migrating User and Password Objects between Active Directory Forests

As part of some internal lab work, I had to move the user objects with their passwords to a new forest. It was key to migrate the passwords to ensure that disruption to the users was minimized.

To migrate the users, I used the Microsoft Active Direction Migration Tool (ADMT + documentation) alongside the Password Migration Service.

In this blog post I am going to cover;

  • Create connectivity between both AD Forests
  • 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.

DNS setup

You need to configure conditional forwarders between your forests, so they can resolve one another.

On the source domain controller;

  1. Open up the DNS console, and right click the Conditional Forwarder folder to create a new record.
  2. 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.

It is also a good idea to add the target domain DNS suffix to your Source DC network adapter, this allows for short name resolution.

Repeat the same steps on the target domain controllers, pointing the conditional forwarder to your source domain.

After this, ensure you can successfully look up the domains from another with the correct Domain controller IP addresses being returned. Also check short name resolution works.

Create Active Directory Forest Two-Way Trust

Next you need to create a forest trust

  • You can read about the different options here

I will create a two-way forest trust which means we are able to authenticate users between domains, and this trust will be removed after I’ve migrated the users.

On the source domain controller

  1. Open Active Directory Domains and Trusts. right click your domain name and go to properties
  2. Click the trusts tab, and click the new trust button
  3. Enter the name of your target domain
  4. Select forest trust
  5. Select two-way trust
  6. Select forest wide trust
  7. Enter trust password (you will use this when you create the trust on the target domain side)
  8. Click next x2
  9. If you click to confirm the trust at this point, it will fail as it does not exist on the target domain side yet. (See screenshots)

Installing the ADMT software

Install this on your Target domain controller, or a machine in target domain. There is a requirement for an SQL server to host a database. I used SQL Express for the lab setup.

Installing the Password Migration Service

First you must generate an encryption key from a DC in your target domain. Open CMD as administrator and run;

admt /key option:create /sourcedomain:{source domain name} /keyfile:{folder path to save the file} /Keypassword:*

Using * for the pwd flag, will then prompt you for the password when the command is run

On your source domain, in the built-in Administrators group, add in the domain administrator from your target domain.

On the domain controller in your source domain, install the Password Migration Service.

When prompted, install the service as the domain admin from your target domain, this account will be added the log on as service right.

A reboot of the machine where this service is installed will be needed.

After the reboot, you will need to manually start the “Password Export Server Service”, after you’ve migrated your users, for security, you should stop this service.

Creating a user list for migration

The last step before migration, is creating a CSV file with a list of the users we want to migrate. I will do this using a simple PowerShell command

get-aduser –filter * -searchbase {OU full path} | Export-csv {path}

You can be more complex if you need to target users who are part of a security group or multiple OUs.

You will need to edit this CSV to use the accepted headers for use as an “include file” for ADMT. You can follow the official documentation for these headers.

Migrating users between AD Forests

Ok, we’ve finished the prep work. Now time to migrate the users.

  1. Open up ADMT console, right click on the Migration tool folder and select “User Account Migration Wizard”
  2. Type in your source domain, and select your target domain from the drop down
  3. Select the option “read objects from include file”
  4. Set your include file location and Source OU where your users are located
  5. Select the option to migrate the user’s passwords
  6. Select account options for after the migration
    1. If selected SID History Migration, accept the options
  7. Input the domain admin detail to authenticate to the Source Domain
  8. Configure user options for after the migration
  9. Select any user object attributes you do not want to be migrated
  10. Select your option for how to handle user conflicts
  11. Complete the user migration wizard
  12. Watch the progress, you also have easy access to view the logs from here
  13. Configure user’s password so that they do not need changing upon next login.
get-aduser -filter * -searchbase {OU path} | set-aduser -changepasswordatlogon $false


Hope this helps someone out there, I recommend that you read the ADMT document first before undertaking a migration of AD users in production, and then test in a lab environment.

Powershell snippet – text to secure string and output to XML file

Below is a quick Powershell command I use to convert passwords to secure strings and output to an XML file, I can encrypt that XML file locally on the machine where any scripts need to run from, and call it in another Powershell script.

$secpasswd = ConvertTo-SecureString "VMware1!" -AsPlainText -Force

#The logic used here between the brackets is Username,Password, where we call our previous variable

$mycreds = New-Object System.Management.Automation.PSCredential ("administrator", $secpasswd) 

$mycreds | export-clixml -path c:\temp\password.xml

It’s quick and easy to use, there will be other ways that may work better for you, if so, drop them in the comments.

vRSLCM – vRA fails to update from 8.0 to 8.0.1 – LCMVRAVACONFIG90030

When updating my vRealize Automation instance from 8.0 to 8.0.1, I ran into an issue;



vRA VA Upgrade Status Check failed.

Upgrade prepare on vRA VA sc-dc1-vra001.simon.local failed with state error. To know more about the failure, run command "vracli upgrade status --details" on the vRA VA sc-dc1-vra001.simon.local. If the prepare upgrade issue is fixed outside vRSLCM, the vRSLCM request can be proceeded to next step by clicking RETRY with proceedNext property set to true. Optionally, the whole upgrade can be cancelled and started afresh by clicking RETRY with cancelAndStartAfresh property set to true. If both the retry properties are set to true,cancelAndStartAfresh property will take precedence and will be honoured

I logged into my vRA node, and ran the recommended command “vracli upgrade status –details”. This basically told me no running application servers were running. Which was odd, as my vRA installation was working.

So I ran “vracli status” and immediately seen that I had some issue with my database in the vRA node. I’m unsure if this was a pre-upgrade issue, or happening during the upgrade.

[ERROR] Exception while getting DB nodes.
Error getting database node status

I decided to run “” which re-runs all the Kubernetes configuration, thus killing and restarting all the services. This seemed to resolve my issue, as running the upgrade again worked as expected.

If you encounter this situation, I would recommend you contact VMware Support for guidance, and information as to why your services have stopped. As this is in my lab environment, I do not have the same considerations as those that run production.

Windows Server 2019 Evaluation – Activation fails

I had issues converting one of my evaluation installations of Windows Server 2019 to a fully licensed copy. I’d extended the evaluation a few times using “slgmr /rearm” a few times, but had finally decided I was going to move this setup into production.

The issue

When going through the settings UI to activate, I could see an error message as below, and clicking the “Change product key” option did nothing.

Running through the CLI using “slmgr.vbs” also returned errors;


Cscript.exe %windir%\system32\slmgr.vbs /ipk {key}


0xC004F069 On a computer running Microsoft Windows non-core edition, run 'slui.exe 0x2a 0xC004F069' to display the error text.

Following the rabbit down the hole;


slui.exe 0x2a 0xC004F069 


Code: 0xC004F069
The Software Licensing Service reported that the product SKU is not found.
The fix

Continue reading Windows Server 2019 Evaluation – Activation fails

Kubernetes basics – kubeadm token create –print-join-command

Recently I’ve been using the fantastic resources to start learning Kubernetes (it’s the next big thing don’t you know). The course I’ve been following;

When running the command below, I lost connectivity to my master, which means I missed the print out of my join command to run on my woker nodes;

sudo kubeadm init --pod-network-cidr=

I was a little stumped how I get access to the print out again, and running the Kubeadm init, failed as initiation had already been done.

The fix for this was rather simple it seems by running the below;

kubeadmin token create --print-join-command

I was then given a new output to copy and paste to into my worker nodes. Don’t worry about the previous token that was issued, this will expire after 24 hours, which is the default timer.