Why is this? The fix by adding the NoDomainUser registry value does not completely fix the issue. This is because at this point no Credential has been created in the Credential store.Īnd the user has to perform activation again (even within the same RDS session).

However, when the user closes Office (in the case Word) and opens another Office application, he’s now suddenly being prompted with the error “ Sorry, we cannot verify the license currently installed for this product” Error code 0x80004005 The user finishes the activation and is seems to have been successful when checking the account tab in Word at that time. This is expected behavior in environments where federation is not in place.

Registry value NoDomainUser is configured to 1 (Advised by Microsoft in case of the scenario above) also see Ī new user who doesn’t have a profile yet, logs on for the first time and launches an Office application for the first time and gets prompted with the Office 365 activation screen.

Federation is not in place so activation relies on a user activating manually once by entering his O365 credentials.

An RDS environment that hosts one or more RDSH servers with Office 2013 Click 2 Run installed.

Pokemon leaf green game for mobile