ADFS Server on Windows 2012 R2 – AddressThe e-mail address of the userGiven NameThe given name of the userName

Setting up an ADFS 3.0 Server on Windows 2012 R2

On testing the setup, you receive an error that looks like this:

dkYfAUMU0yl74SE4kki4WC2wzYiQ2c5ea3sOz/KMfAk=f1EHPUY2buvcksrq2PV4Jzz1gPzqqsJLte1AgpTWwtQ0MnKMgzgVQ5OTSTcElWugzU4m3nZFOz0OmR9nUd/KaKasgnv0kxKO7SjuQ09VTtcIblHBwr/sRe13Q5pb6LeWC17g5/STWC4JMy9MjQzk97WvBLtNjlV77tijW9EK5XTQAuUqyXfbZsPuMw9hLZ7YBEEWB8SEmopUHWVGcVYAEjl3eFk+jqbPmL71K9OdlBM0l0BuzK9vr1rppjBHKUoWP7nuhiY9oohaVkktUA4pI9DhWhMwVhGx3Yr8VYyZtI65LfeIyyz2MzEhcxuzkaxory4VQdxn4af4r534mP5W5w==MIIC2DCCAcCgAwIBAgIQfjdRsjCXc75E99PlMFiDijANBgkqhkiG9w0BAQsFADAoMSYwJAYDVQQDEx1BREZTIFNpZ25pbmcgLSBpd2Vic2NybTE1LmNvbTAeFw0xNTAyMTgwNzQ3NTRaFw0xNjAyMTgwNzQ3NTRaMCgxJjAkBgNVBAMTHUFERlMgU2lnbmluZyAtIGl3ZWJzY3JtMTUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuThBgpEQ0IeqKWmaVdlY4idGsd7E/PiPdggk9Ol+wA/bYSSth4sHPOe2DWFu+IkgqaCKfZdCN6aI8TmQbfPjcqwlJSGqws2EFO/TULpbu/x1AwYV6J++BhpFD0iPbFPuypqGgC423+Z6RjP/99wU4tu5GtxvUD2L8iuW9AtXnZJy6MFDLmITVTWCzFQnPC7lGjY1mQ/XZXmidgq0f29qK1mvqGuwGT/BhQO1woj6O95gPhF3ZCMqW6h6ma0LjJhj1dR36NIs0k0sseUUjGbfOF81WZPm7e/HaDUJTF4ox51VIrf+Z7+HpUBCesYwFXhyCvYq6TIvY5NTkRWCKQ97mQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQBl4L7NIWBeoeQRJg9RlkDzs2stg7Q+tZ6tminURNOC8ch0vhITbCq60uKXBzXn9LTHex1iXNlyZwI5YGXbw9pBsybDPDFxtyBGAwi/EX8Y0xe7ePGs7jNaGDMywFofP61g64HIAey6YjvKYFPxMqZmDBrzIhNnZ44f/o07TTOCdZJkqh5L/Qjilzfw2bwVg3uGaFthrn1LkL9xB82kuuXYW1QWe37Y9Gwf57qTQo56S44pxBB8loKn4hkNaRdKCgNCH7Ary3uLmmaFP/ETucAkIcy9Y/wr+TEzDVvGkRqCaWLUKeOumc+p026Jv3r/ba4Iq2njfat/pNv+dRIqt/PKMIIC3jCCAcagAwIBAgIQFOgcyJdf6pRLRqk+kAcU1zANBgkqhkiG9w0BAQsFADArMSkwJwYDVQQDEyBBREZTIEVuY3J5cHRpb24gLSBpd2Vic2NybTE1LmNvbTAeFw0xNTAyMTgwNzQ3NTVaFw0xNjAyMTgwNzQ3NTVaMCsxKTAnBgNVBAMTIEFERlMgRW5jcnlwdGlvbiAtIGl3ZWJzY3JtMTUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA539QwHAojXm5lcKoRAAe3yoOQxCbItjkgWsomRat9/E9o+tpszADLfO6KcyIwmxMdcN1mIPzEUzW/Fc5biMGCK2jSNCKN9HXiABUXJcRa+iZ7RN7eFdmKcLXRWaAeqb/l0icuSqbKxxCb3gFnQUxpRar7gZmS6xrnz0MBkRI7LXD/Mp6kU0VnfAMHQf33Wt1LXf/+w+l9V78o5b95OylPleRA6dplNfv60GLemmXY45VTpPlBDV0gFBrkYgmg7DPhR0U3MY1RYuUAsWx3htY7S4oNTEbl96Hyel6UPWiqaZFeeN+3aujABohgHM0vVVndswyxe2pnMZtieWJ+pP8yQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQDjfiC4cMQ353SjBRAtbSH6hJ9zZ97yvguVNELyHojSUmi6VEHT6OWsntFWxPsGZvJ0Oq34KM4ZSrnq5QhrB4QuB26RLSw1yR9jBtZMTy/fGm4X25wczPCoZbkrySktPtyCVC3xJw6MKlwcZNGF/zOwoqjeY015Z4CGJsBijtd7MSBf+6ijAcGYdxC1bumB3vfsJ9bu1eVu9QRpDQm78zXpw/LBMj68RfiXz50WRlALa+ca7NqeVIKcSYx20JaSAoe6y1tWlAPVieGDpaXzpKFQ/fF1wIHjdc3euNeKAX/eaV56vCuBG4kwAjSSrawwt/nZ4nflpKVC8RLNgobeaDnTE-Mail AddressThe e-mail address of the userGiven NameThe given name of the userNameThe unique name of the userUPNThe user principal name (UPN) of the userCommon NameThe common name of the userAD FS 1.x E-Mail AddressThe e-mail address of the user when interoperating with AD FS 1.1 or AD FS 1.0GroupA group that the user is a member ofAD FS 1.x UPNThe UPN of the user when interoperating with AD FS 1.1 or AD FS 1.0RoleA role that the user hasSurnameThe surname of the userPPIDThe private identifier of the userName IDThe SAML name identifier of the userAuthentication time stampUsed to display the time and date that the user was authenticatedAuthentication methodThe method used to authenticate the userDeny only group SIDThe deny-only group SID of the userDeny only primary SIDThe deny-only primary SID of the userDeny only primary group SIDThe deny-only primary group SID of the userGroup SIDThe group SID of the userPrimary group SIDThe primary group SID of the userPrimary SIDThe primary SID of the userWindows account nameThe domain account name of the user in the form of domain\userIs Registered UserUser is registered to use this deviceDevice IdentifierIdentifier of the deviceDevice Registration IdentifierIdentifier for Device RegistrationDevice Registration DisplayNameDisplay name of Device RegistrationDevice OS typeOS type of the deviceDevice OS VersionOS version of the deviceIs Managed DeviceDevice is managed by a management serviceForwarded Client IPIP address of the userClient ApplicationType of the Client ApplicationClient User AgentDevice type the client is using to access the applicationClient IPIP address of the clientEndpoint PathAbsolute Endpoint path which can be used to determine active versus passive clientsProxyDNS name of the federation server proxy that passed the requestApplication IdentifierIdentifier for the Relying PartyApplication policiesApplication policies of the certificateAuthority Key IdentifierThe Authority Key Identifier extension of the certificate that signed an issued certificateBasic ConstraintOne of the basic constraints of the certificateEnhanced Key UsageDescribes one of the enhanced key usages of the certificateIssuerThe name of the certificate authority that issued the X.509 certificateIssuer NameThe distinguished name of the certificate issuerKey UsageOne of the key usages of the certificateNot AfterDate in local time after which a certificate is no longer validNot BeforeThe date in local time on which a certificate becomes validCertificate PoliciesThe policies under which the certificate has been issuedPublic KeyPublic Key of the certificateCertificate Raw DataThe raw data of the certificateSubject Alternative NameOne of the alternative names of the certificateSerial NumberThe serial number of a certificateSignature AlgorithmThe algorithm used to create the signature of a certificateSubjectThe subject from the certificateSubject Key IdentifierDescribes the subject key identifier of the certificateSubject NameThe subject distinguished name from a certificateV2 Template NameThe name of the version 2 certificate template used when issuing or renewing a certificate. The extension is Microsoft specific.V1 Template NameThe name of the version 1 certificate template used when issuing or renewing a certificate. The extension is Microsoft specific.ThumbprintThumbprint of the certificateX.509 VersionThe X.509 format version of a certificateInside Corporate NetworkUsed to indicate if a request originated inside corporate networkPassword Expiration TimeUsed to display the time when the password expiresPassword Expiration DaysUsed to display the number of days to password expiryUpdate Password URLUsed to display the web address of update password serviceAuthentication Methods ReferencesUsed to indicate all authentication methods used to authenticate the userClient Request IDIdentifier for a user sessionAlternate Login IDAlternate login ID of the user 

https://iwebscrm15.com/adfs/services/trust/2005/issuedtokenmixedasymmetricbasic256

https://iwebscrm15.com/adfs/services/trust/2005/issuedtokenmixedsymmetricbasic256

https://iwebscrm15.com/adfs/services/trust/13/issuedtokenmixedasymmetricbasic256

https://iwebscrm15.com/adfs/services/trust/13/issuedtokenmixedsymmetricbasic256

https://iwebscrm15.com/adfs/ls/

http://iwebscrm15.com/adfs/services/trust

https://iwebscrm15.com/adfs/services/trust/2005/issuedtokenmixedasymmetricbasic256

https://iwebscrm15.com/adfs/ls/

MIIC2DCCAcCgAwIBAgIQfjdRsjCXc75E99PlMFiDijANBgkqhkiG9w0BAQsFADAoMSYwJAYDVQQDEx1BREZTIFNpZ25pbmcgLSBpd2Vic2NybTE1LmNvbTAeFw0xNTAyMTgwNzQ3NTRaFw0xNjAyMTgwNzQ3NTRaMCgxJjAkBgNVBAMTHUFERlMgU2lnbmluZyAtIGl3ZWJzY3JtMTUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuThBgpEQ0IeqKWmaVdlY4idGsd7E/PiPdggk9Ol+wA/bYSSth4sHPOe2DWFu+IkgqaCKfZdCN6aI8TmQbfPjcqwlJSGqws2EFO/TULpbu/x1AwYV6J++BhpFD0iPbFPuypqGgC423+Z6RjP/99wU4tu5GtxvUD2L8iuW9AtXnZJy6MFDLmITVTWCzFQnPC7lGjY1mQ/XZXmidgq0f29qK1mvqGuwGT/BhQO1woj6O95gPhF3ZCMqW6h6ma0LjJhj1dR36NIs0k0sseUUjGbfOF81WZPm7e/HaDUJTF4ox51VIrf+Z7+HpUBCesYwFXhyCvYq6TIvY5NTkRWCKQ97mQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQBl4L7NIWBeoeQRJg9RlkDzs2stg7Q+tZ6tminURNOC8ch0vhITbCq60uKXBzXn9LTHex1iXNlyZwI5YGXbw9pBsybDPDFxtyBGAwi/EX8Y0xe7ePGs7jNaGDMywFofP61g64HIAey6YjvKYFPxMqZmDBrzIhNnZ44f/o07TTOCdZJkqh5L/Qjilzfw2bwVg3uGaFthrn1LkL9xB82kuuXYW1QWe37Y9Gwf57qTQo56S44pxBB8loKn4hkNaRdKCgNCH7Ary3uLmmaFP/ETucAkIcy9Y/wr+TEzDVvGkRqCaWLUKeOumc+p026Jv3r/ba4Iq2njfat/pNv+dRIqt/PKE-Mail AddressThe e-mail address of the userGiven NameThe given name of the userNameThe unique name of the userUPNThe user principal name (UPN) of the userCommon NameThe common name of the userAD FS 1.x E-Mail AddressThe e-mail address of the user when interoperating with AD FS 1.1 or AD FS 1.0GroupA group that the user is a member ofAD FS 1.x UPNThe UPN of the user when interoperating with AD FS 1.1 or AD FS 1.0RoleA role that the user hasSurnameThe surname of the userPPIDThe private identifier of the userName IDThe SAML name identifier of the userAuthentication time stampUsed to display the time and date that the user was authenticatedAuthentication methodThe method used to authenticate the userDeny only group SIDThe deny-only group SID of the userDeny only primary SIDThe deny-only primary SID of the userDeny only primary group SIDThe deny-only primary group SID of the userGroup SIDThe group SID of the userPrimary group SIDThe primary group SID of the userPrimary SIDThe primary SID of the userWindows account nameThe domain account name of the user in the form of domain\userIs Registered UserUser is registered to use this deviceDevice IdentifierIdentifier of the deviceDevice Registration IdentifierIdentifier for Device RegistrationDevice Registration DisplayNameDisplay name of Device RegistrationDevice OS typeOS type of the deviceDevice OS VersionOS version of the deviceIs Managed DeviceDevice is managed by a management serviceForwarded Client IPIP address of the userClient ApplicationType of the Client ApplicationClient User AgentDevice type the client is using to access the applicationClient IPIP address of the clientEndpoint PathAbsolute Endpoint path which can be used to determine active versus passive clientsProxyDNS name of the federation server proxy that passed the requestApplication IdentifierIdentifier for the Relying PartyApplication policiesApplication policies of the certificateAuthority Key IdentifierThe Authority Key Identifier extension of the certificate that signed an issued certificateBasic ConstraintOne of the basic constraints of the certificateEnhanced Key UsageDescribes one of the enhanced key usages of the certificateIssuerThe name of the certificate authority that issued the X.509 certificateIssuer NameThe distinguished name of the certificate issuerKey UsageOne of the key usages of the certificateNot AfterDate in local time after which a certificate is no longer validNot BeforeThe date in local time on which a certificate becomes validCertificate PoliciesThe policies under which the certificate has been issuedPublic KeyPublic Key of the certificateCertificate Raw DataThe raw data of the certificateSubject Alternative NameOne of the alternative names of the certificateSerial NumberThe serial number of a certificateSignature AlgorithmThe algorithm used to create the signature of a certificateSubjectThe subject from the certificateSubject Key IdentifierDescribes the subject key identifier of the certificateSubject NameThe subject distinguished name from a certificateV2 Template NameThe name of the version 2 certificate template used when issuing or renewing a certificate. The extension is Microsoft specific.V1 Template NameThe name of the version 1 certificate template used when issuing or renewing a certificate. The extension is Microsoft specific.ThumbprintThumbprint of the certificateX.509 VersionThe X.509 format version of a certificateInside Corporate NetworkUsed to indicate if a request originated inside corporate networkPassword Expiration TimeUsed to display the time when the password expiresPassword Expiration DaysUsed to display the number of days to password expiryUpdate Password URLUsed to display the web address of update password serviceAuthentication Methods ReferencesUsed to indicate all authentication methods used to authenticate the userClient Request IDIdentifier for a user sessionAlternate Login IDAlternate login ID of the user 

https://iwebscrm15.com/adfs/services/trust/2005/certificatemixed

https://iwebscrm15.com/adfs/services/trust/mex

https://iwebscrm15.com/adfs/ls/

MIIC3jCCAcagAwIBAgIQFOgcyJdf6pRLRqk+kAcU1zANBgkqhkiG9w0BAQsFADArMSkwJwYDVQQDEyBBREZTIEVuY3J5cHRpb24gLSBpd2Vic2NybTE1LmNvbTAeFw0xNTAyMTgwNzQ3NTVaFw0xNjAyMTgwNzQ3NTVaMCsxKTAnBgNVBAMTIEFERlMgRW5jcnlwdGlvbiAtIGl3ZWJzY3JtMTUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA539QwHAojXm5lcKoRAAe3yoOQxCbItjkgWsomRat9/E9o+tpszADLfO6KcyIwmxMdcN1mIPzEUzW/Fc5biMGCK2jSNCKN9HXiABUXJcRa+iZ7RN7eFdmKcLXRWaAeqb/l0icuSqbKxxCb3gFnQUxpRar7gZmS6xrnz0MBkRI7LXD/Mp6kU0VnfAMHQf33Wt1LXf/+w+l9V78o5b95OylPleRA6dplNfv60GLemmXY45VTpPlBDV0gFBrkYgmg7DPhR0U3MY1RYuUAsWx3htY7S4oNTEbl96Hyel6UPWiqaZFeeN+3aujABohgHM0vVVndswyxe2pnMZtieWJ+pP8yQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQDjfiC4cMQ353SjBRAtbSH6hJ9zZ97yvguVNELyHojSUmi6VEHT6OWsntFWxPsGZvJ0Oq34KM4ZSrnq5QhrB4QuB26RLSw1yR9jBtZMTy/fGm4X25wczPCoZbkrySktPtyCVC3xJw6MKlwcZNGF/zOwoqjeY015Z4CGJsBijtd7MSBf+6ijAcGYdxC1bumB3vfsJ9bu1eVu9QRpDQm78zXpw/LBMj68RfiXz50WRlALa+ca7NqeVIKcSYx20JaSAoe6y1tWlAPVieGDpaXzpKFQ/fF1wIHjdc3euNeKAX/eaV56vCuBG4kwAjSSrawwt/nZ4nflpKVC8RLNgobeaDnTMIIC2DCCAcCgAwIBAgIQfjdRsjCXc75E99PlMFiDijANBgkqhkiG9w0BAQsFADAoMSYwJAYDVQQDEx1BREZTIFNpZ25pbmcgLSBpd2Vic2NybTE1LmNvbTAeFw0xNTAyMTgwNzQ3NTRaFw0xNjAyMTgwNzQ3NTRaMCgxJjAkBgNVBAMTHUFERlMgU2lnbmluZyAtIGl3ZWJzY3JtMTUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuThBgpEQ0IeqKWmaVdlY4idGsd7E/PiPdggk9Ol+wA/bYSSth4sHPOe2DWFu+IkgqaCKfZdCN6aI8TmQbfPjcqwlJSGqws2EFO/TULpbu/x1AwYV6J++BhpFD0iPbFPuypqGgC423+Z6RjP/99wU4tu5GtxvUD2L8iuW9AtXnZJy6MFDLmITVTWCzFQnPC7lGjY1mQ/XZXmidgq0f29qK1mvqGuwGT/BhQO1woj6O95gPhF3ZCMqW6h6ma0LjJhj1dR36NIs0k0sseUUjGbfOF81WZPm7e/HaDUJTF4ox51VIrf+Z7+HpUBCesYwFXhyCvYq6TIvY5NTkRWCKQ97mQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQBl4L7NIWBeoeQRJg9RlkDzs2stg7Q+tZ6tminURNOC8ch0vhITbCq60uKXBzXn9LTHex1iXNlyZwI5YGXbw9pBsybDPDFxtyBGAwi/EX8Y0xe7ePGs7jNaGDMywFofP61g64HIAey6YjvKYFPxMqZmDBrzIhNnZ44f/o07TTOCdZJkqh5L/Qjilzfw2bwVg3uGaFthrn1LkL9xB82kuuXYW1QWe37Y9Gwf57qTQo56S44pxBB8loKn4hkNaRdKCgNCH7Ary3uLmmaFP/ETucAkIcy9Y/wr+TEzDVvGkRqCaWLUKeOumc+p026Jv3r/ba4Iq2njfat/pNv+dRIqt/PKurn:oasis:names:tc:SAML:1.1:nameid-format:emailAddressurn:oasis:names:tc:SAML:2.0:nameid-format:persistenturn:oasis:names:tc:SAML:2.0:nameid-format:transientMIIC3jCCAcagAwIBAgIQFOgcyJdf6pRLRqk+kAcU1zANBgkqhkiG9w0BAQsFADArMSkwJwYDVQQDEyBBREZTIEVuY3J5cHRpb24gLSBpd2Vic2NybTE1LmNvbTAeFw0xNTAyMTgwNzQ3NTVaFw0xNjAyMTgwNzQ3NTVaMCsxKTAnBgNVBAMTIEFERlMgRW5jcnlwdGlvbiAtIGl3ZWJzY3JtMTUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA539QwHAojXm5lcKoRAAe3yoOQxCbItjkgWsomRat9/E9o+tpszADLfO6KcyIwmxMdcN1mIPzEUzW/Fc5biMGCK2jSNCKN9HXiABUXJcRa+iZ7RN7eFdmKcLXRWaAeqb/l0icuSqbKxxCb3gFnQUxpRar7gZmS6xrnz0MBkRI7LXD/Mp6kU0VnfAMHQf33Wt1LXf/+w+l9V78o5b95OylPleRA6dplNfv60GLemmXY45VTpPlBDV0gFBrkYgmg7DPhR0U3MY1RYuUAsWx3htY7S4oNTEbl96Hyel6UPWiqaZFeeN+3aujABohgHM0vVVndswyxe2pnMZtieWJ+pP8yQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQDjfiC4cMQ353SjBRAtbSH6hJ9zZ97yvguVNELyHojSUmi6VEHT6OWsntFWxPsGZvJ0Oq34KM4ZSrnq5QhrB4QuB26RLSw1yR9jBtZMTy/fGm4X25wczPCoZbkrySktPtyCVC3xJw6MKlwcZNGF/zOwoqjeY015Z4CGJsBijtd7MSBf+6ijAcGYdxC1bumB3vfsJ9bu1eVu9QRpDQm78zXpw/LBMj68RfiXz50WRlALa+ca7NqeVIKcSYx20JaSAoe6y1tWlAPVieGDpaXzpKFQ/fF1wIHjdc3euNeKAX/eaV56vCuBG4kwAjSSrawwt/nZ4nflpKVC8RLNgobeaDnTMIIC2DCCAcCgAwIBAgIQfjdRsjCXc75E99PlMFiDijANBgkqhkiG9w0BAQsFADAoMSYwJAYDVQQDEx1BREZTIFNpZ25pbmcgLSBpd2Vic2NybTE1LmNvbTAeFw0xNTAyMTgwNzQ3NTRaFw0xNjAyMTgwNzQ3NTRaMCgxJjAkBgNVBAMTHUFERlMgU2lnbmluZyAtIGl3ZWJzY3JtMTUuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuThBgpEQ0IeqKWmaVdlY4idGsd7E/PiPdggk9Ol+wA/bYSSth4sHPOe2DWFu+IkgqaCKfZdCN6aI8TmQbfPjcqwlJSGqws2EFO/TULpbu/x1AwYV6J++BhpFD0iPbFPuypqGgC423+Z6RjP/99wU4tu5GtxvUD2L8iuW9AtXnZJy6MFDLmITVTWCzFQnPC7lGjY1mQ/XZXmidgq0f29qK1mvqGuwGT/BhQO1woj6O95gPhF3ZCMqW6h6ma0LjJhj1dR36NIs0k0sseUUjGbfOF81WZPm7e/HaDUJTF4ox51VIrf+Z7+HpUBCesYwFXhyCvYq6TIvY5NTkRWCKQ97mQIDAQABMA0GCSqGSIb3DQEBCwUAA4IBAQBl4L7NIWBeoeQRJg9RlkDzs2stg7Q+tZ6tminURNOC8ch0vhITbCq60uKXBzXn9LTHex1iXNlyZwI5YGXbw9pBsybDPDFxtyBGAwi/EX8Y0xe7ePGs7jNaGDMywFofP61g64HIAey6YjvKYFPxMqZmDBrzIhNnZ44f/o07TTOCdZJkqh5L/Qjilzfw2bwVg3uGaFthrn1LkL9xB82kuuXYW1QWe37Y9Gwf57qTQo56S44pxBB8loKn4hkNaRdKCgNCH7Ary3uLmmaFP/ETucAkIcy9Y/wr+TEzDVvGkRqCaWLUKeOumc+p026Jv3r/ba4Iq2njfat/pNv+dRIqt/PKurn:oasis:names:tc:SAML:1.1:nameid-format:emailAddressurn:oasis:names:tc:SAML:2.0:nameid-format:persistenturn:oasis:names:tc:SAML:2.0:nameid-format:transient

When you find this

Typically when you test at a URL that looks like this: https://adfs.iwebscrm15.com/federationmetadata/2007-06/federationmetadata.xml (With you domain name in it)

Solution:

On Internet Explorer / Internet Options / Local Intranet / Sites

Add the domain name with a wild card to your safe sites:

IE Safe Sites

Advance

Ie Safe Sites Advance

Adding the *.domain.com  to the safe sites list

*.domain.com Safe Sites.png

Add 

Now hitting the URL to test: https://sts.iwebscrm15.com/federationmetadata/2007-06/federationmetadata.xml

Gives a better result and expected result

ADFS 3.0 Test Results

Catalook Credit Card Dropdown Expiry Year

Catalook Credit Card Dropdown Year

We experienced a problem with the store checkout only listing a creadit card expiry date up to 2015 

Thus the drop down selector in the Credit Card field for expiry date would not allow years fat enough into the future that the customer could select the correct expiry date.

Catalook Credit Card Dropdown
The solution we found was this:


Navigating to the “Your Cart” module. You can do this by login in as an admin (not host) and buying a product. When it takes you to the cart module…
Select Edit Skin from the module menu.
Grab the code there, and paste into notepad etc. And look to the code that looks like this.  
ListItem Value=”09″ Selected=”True”>2009
ListItem Value=”15″>2015
ListItem Value=”16″>2016
ListItem Value=”17″>2017
ListItem Value=”18″>2018
ListItem Value=“19″>2019
ListItem Value=“20″>2020
Make it look like this exactly for the update at this time.

This will give you a larger future expiry date.

How to Set up CRM 2015 IFD on Windows 2012 and ADFS 3.0

We already have a popular post for the configuration of IFD setup with CRM 2013 and CRM 2011. Now we are updating this post to support CRM 2015.

Microsoft have a compatibility listing for CRM 2015 here: http://support.microsoft.com/kb/3018360

The Development Setup

 Once again we are running this configuration as a test environment for development. As such we will be running, we are running the server on a Hyper V server. A single VM machine, that is running a fully patched version of:

  • Windows 2012 R2 SP2 64 Bit – (MSDN File: en_windows_server_2012_r2_x64_dvd_2707946
  • SQL 2014 R2 64 Bit – SQL Server 2014 Standard Edition x64 – (MSDN File: en_sql_server_2014_standard_edition_x64_dvd_3932034) – Patched to SP2
  • Microsoft Dynamics CRM Server 2015 (x86 and x64) – DVD (English) – (MSDN File: en_microsoft_dynamics_crm_server_2015_x86_x64_dvd_5853339)
NOTE: The Domain we have used for setup with this dev server is: iwebscrm15.com You can substitute your domain in place throughout these step by step IFD instructions CRM 2015.

Installing CRM 2015

We pretty much followed a combination of these instructions:
http://blogs.msdn.com/b/niran_belliappa/archive/2013/11/05/step-by-step-installing-dynamics-crm-2013-on-windows-server-2012.aspx

During the install, we were asked to install services associated with the services required for CRM 2015.

CRM 2015 Install Process

We Selected all options on install:

Screenshot 2015 02 12 14 57 24

We selected the default account for authority. Note that the blog referenced above suggests a dedicated account for security. As we are setting up a dev environment we did not bother with this.

CRM 2015 Security Account

IMPORTANT

Create a new Website with port 5555

CRM 2015 IFD Website 5555

As we intend to set up the Email Router service on this server later, we set this server “VSERVER06” in this instance as the server for email router service:

CRM 2015 Email Router Server

We set “CRM2015” As the default initial test environment deployment.

CRM 2015 Default Deployment

Reporting Server defaulted to the server name/reportserver

CRM 2015 Report Server

We received a few warnings about the install:

CRM 2015 Install Warnings

For a deployment that is more secure, the Microsoft Dynamics CRM Sandbox Processing Service should be run under a least-privileged domain user account that is not shared by other Microsoft Dynamics CRM services on this computer.

For a deployment that is more secure, the Microsoft Dynamics CRM VSS Writer Service should be run under a least-privileged domain user account that is not shared by other Microsoft Dynamics CRM services on this computer.

Data encryption will be active after the install or upgrade. We strongly recommend that you copy the organization encryption key and store it in a safe place. For more information, see http://go.microsoft.com/fwlink/?LinkId=316366.

The only one of real interest in our Dev environment would be the last item. making a backup of data encryption keys is always a good idea. 

Test First

Test that your CRM setup is working. Go to the local computer name (ours is vserver06) on the correct port: http://vserver06:5555

We called our Deployment of CRM – “CRM2015″ So the URL redirects to: http://vserver06:5555/CRM2015/main.aspx

Because we were were logged in as the server administrator, we were able to load

CRM 2015 Initial Login 

Apply a Wildcard SSL Certificate

In CRM, the accessing of deployments is handled by the sub domains. So if we call a deployment “business1″ we will access that as: https://business1.domain.com

For testing, we purchased a standard Wildcard SSL certificate that applied that to the IIS Server 

In our case we registered a test domain: iwebscrm15.com and set the SSL wildcard to: *.iwebscrm15.com and applied that cert to the server.

Application for a certificate

Here, I will be a wildcard certificate, for example, describes how to create a certificate:

1) Open IIS Manager

2) Click the server name in the main screen double click Server Certificates

3) In the right panel, click Create Certificate Request…

image

4) fill in the following diagram each column, click Next

image

5) Cryptographic Service Provider Properties page change the Bit Length to 2048 click Next.

Screenshot 2014 07 05 18 50 18

6) In the File Name page, enter C: \ req.txt , and then click Finish. (You can save it any place you like, with any name)

7) Open the certificate in Notepad, and copy the contents.

Screenshot 2014 07 05 18 53 05

This is the text that is pasted into the Start SSL Certificate request page to generate the certificate:

Screenshot 2014 07 05 18 55 03

8) After you finish generating the certificate text in StartSSL.com you get a bunch of code that looks similar to the request code. Copy that generated code

9) Paste the code back into a new Text / Notepad Document on the Web server, but call it something that ends in .cer  (not .txt). 

10) back to the IIS Manager, click No. 3)  Step graph Complete Certificate Request …

11) Select the the file you created at point 9 above to complete the request.

12) Click OK.
Note: We did get an error message: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
In this instance, it turned out to be a crappy Microsoft Error. After doing some research, we found that it was likely meaningless and the cert installed correctly. We rebooted the machine and logged in again, to find that the CERT was there installed as we wanted it to be.

Binding site for the default SSL certificate

1) Open IIS Manager.

2) In the Connections panel, expand Sites , click Default Web Site.

3) In the Actions pane, click Bindings.

image

4) In the Site Bindings dialog box, click Add.

5) Type select HTTPS.

6) SSL Certificate , select the certificate you just created *. contoso.com , and then click OK.

Screenshot 2015 02 18 18 03 45

 Ours is *.iwebscrm15.com

CRM 2015 SSL

7) Click Close.

For the CRM 2015 binding site SSL certificate

This is in effect repeating the above process like you did for the default certificate, but using a different port (444 for example). This way you are binding the same certificate to the two websites in your IIS instance.

1)Open IIS Manager.

2) In the Connections panel, expand Sites , click CRM Web Site.

3) In the Actions pane, click Bindings.

4) In the Site Bindings dialog box, click Add.

5) Type select HTTPS.

6) SSL Certificate , select the certificate you just created *. contoso.com .

7) Port to select a different 443 (e.g. 444 ) and port number, and then click OK

 SSL CERT CRM 2015

IFD CRM 2015 CERT.png

8) Click Close.

 

DNS configuration

We are going to add a few DNS “A” records so that the records listed in point 1-4 below in DNS Goal are resolving correctly to the IP address of your CRM server.

There are two ways you can achieve the desired result. But first lets understand the desired result.

  1. We make the assumption that your server is running at least one static IP address.
  2. Because this is Internet Facing, that IP needs to be accessible to the world.
  3. That same IP can be used for access to your server both internally on the matching we are playing with, and externally form anyone on the net.
Lets Get Basic

Start a Command Prompt, and work out what your IP address of the server is.

Click START > RUN > CMD

Type IPCONFIG – Enter

Under the name: IPv4 Address is a number that looks like: 66.34.204.220

image

That is Your IP Address of the Server.

The DNS Goal

Make sure that when you PING xxx.domain.com that it points to that IP address. Both for the world and for you when you do that on your server.

(xxx is the sub domain that we are about to configure.)

To configure CRM, we need some sub domains to point to the server IP.

Adding records in DNS like this:

Screenshot 2014 07 05 19 28 02

  1. sts.domain.com
  2. auth.domain.com
  3. dev.domain.com
  4. Your ORG name.  org.domain.com (Where ORG is the CRM deployment name of your organization or organizations), e.g.
  5. crm2015.iwebscrm15.com (We usually set up a dev environment with CRM2015 being the year of the version. Just something we select to do).
  6. adfs.domain.com (used for reference to the ADFS server)
  7. one for the root domain so that domain.com points to the same server. (This is for the ADFS logout URL)

CRM 2015 IFD DNS SETTINGS

We have two setup here: CRM and CRM2015. So we need to configure crm.iwebscrm15.com and crm2015.iwebscrm15.com (Not necessary but our choice for this instance).

Test DNS

You must be able to ping all of those names and get the correct server IP address. Both from computers on the internet, and from the server. At the command prompt, type “ping sts.iwebscrm15.com” for example with our config. Ping them all to be sure you get them correct. 

Note: If you have added the DNS records, but still encounter name resolution problems, you can try running on the client ipconfig / flushdns to clean up the cache. You can also click the DNS server root and click CLEAR CACHE so that the server is responding with the latest updates.

image

Note: Don’t bother proceeding past this step if you cannot ping your sub domains internally and externally correctly.

 

Firewall configuration

You need to set the firewall to allow the CRM 2015 and the AD FS 3.0 port used by the incoming data stream. HTTPS (SSL) is the default port 443.

For Initial setup testing etc. We recommend just turning the thing off. Better start from a place where it does not muck you around, then turn it all back on after you are successful.

1) In Windows 2012 I can’t frigging work out how to find anything. Literally!  But most things you can search for. As is the case here if you search for “Firewall”. Select the firewall option:

Screenshot 2015 02 18 18 14 37

2) Select Turn Windows Firewall on or off

Screenshot 2015 02 18 18 16 04

4) Turn Off or On Firewall

Screenshot 2014 07 05 19 33 53

Just turn it all off for now. (Remember to come back, turn it on and allow access for the unusual port 444 that you configured earlier for the SSL on the CRM site. But for testing and setting up… the last things you want is to be banging your head agains a firewall.

Screenshot 2015 02 18 18 18 31

Configuration Claim-based authentication -internal access

Configure the internal access Claim-based authentication requires the following steps:

  • Install and configure AD FS 3.0
  • Set Claims-based authentication configuration CRM 2015 server.
  • Set the Claims-based authentication configuration AD FS 3.0 server.
  • Test claims-based authentication within the access.

Install and configure ADFS 3.0

CRM 2015 with a variety of STS provider ( STS Provider ) together. This article uses Active Directory Federation Services (AD FS) 3.0 to provide a security token service (security token service ).

Note: AD FS 2.0 will be installed to the default site, so install AD FS 3.0 , you must have CRM 2015 installation in the new site. (Remember we said that earlier)

IIS Looks like this if it is correctly installed: image

If you only see the default website with CRM installed in that. Start AGAIN!

If you have it all correct at this point. Probably a good time to take a SnapShot (backup of the virtually system) and label it something you remember.

CRM 2015 Setup with Snapshots.png 

Install ADFS Server Role

From Server Manager – Add A Server role for: Active Directory Federation Services

Screenshot 2014 07 05 19 39 54 

Screenshot 2015 02 18 18 24 23

Screenshot 2015 02 18 18 24 53

Screenshot 2015 02 18 18 25 34

Click Install at the last step.

Screenshot 2015 02 18 18 26 20

After if Finishes: 

Configure the Fediration service on this server

Click the Configure the Federation Services on this server.

Configure AD FS 3.0

1 Click on Configure the federation service on this server.

2 In the AD FS 3.0 Management page , click AD FS 3.0 Federation Server Configuration Wizard .

3 In the Welcome page , select Create the first federation server in a federation server farm, and then click Next.

Screenshot 2014 07 05 19 43 52

4 Select next to continue with the current administrator (must be a domain admin).

Screenshot 2014 07 10 16 34 34

5 Choose your SSL certificate (the one we created and imported above i.e. *.iwebscrm15.com ) ,add a Federation Service name ( Selecting the second one for the dropdown in this instance iwebscrm15.com, don’t select the one with the wildcard in the name, so not the *.iwebscrm15.com for example.), then Select a Service Display Name for your business – selecting the one that is NOT starting with a *, then click Next.

CRM 105 ADFS Setup

6 Open PowerShell and run the following command: “Add-KdsRootKey -EffectiveTime (Get-Date).AddHours(-10)”

 Screenshot 2014 07 10 16 40 55

Screenshot 2015 02 18 18 42 53

If you don’t you will se the error: Group Managed Service Accounts are not available because the KDS Root Key has not been set.

7 We specified the Administrator account for the service account, as security is not our primary concern here with a Dev environment. You could and probably should use a defined account for a production environment.

ADFS Service Account

7 Create a database on this server using Windows Internal Database (we suggest using the SQL instance in the step below), click Next.

Screenshot 2014 07 10 16 43 30

Or use the local SQL instance etc if you have one. (Because we have SQL installed on this same server. We are using this SQL instance for the database host. 

Screenshot 2015 02 18 18 44 11

8 Review Options click Next

 

Screenshot 2015 02 18 18 49 339 Pre-requisits checklist, click Configure

Screenshot 2014 07 10 16 45 44

10 You should see a message that “This Server was successfully configured

Screenshot 2015 02 18 18 53 47

11 Close out the Instillation progress window

Screenshot 2015 02 18 18 54 07

Screenshot 2015 02 18 18 54 33

Verify the AD FS 3.0 is working

Follow the steps below to verify that the AD FS 3.0 is working :

1 Open Internet Explorer.

Under Internet Options

IE Options

Security / Local Intranet

Screenshot 2015 02 19 08 49 36

Sites / Advanced

IE Sites Advance

Add *.domain.com to the websites. In our case here we added: *.iwebscrm15.com

ADFS Local Intranet Sites

Close all this down when added.

2 Now we need browse to the the federation metadata in Internet explorer to test access is working. 

Use this URL below as an example to browse to your own server. Remembering that we set up a DNS entry earlier for “ADFS’ on your domain, thus you should be able to browse to the URL below replacing our domain name with yours and have it access the server we are configuring.

https://adfs.iwebscrm15.com/federationmetadata/2007-06/federationmetadata.xml (Replace your domain name in place of ours)

3. to ensure that no certificate associated with the warning appears, and you can view the certificate to be sure it is showing.

ADFS IFD CRM 2015 Test

Check the certificate is correct and working by clicking on the padlock looking thing and viewing certificate.

Screenshot 2015 02 19 09 00 40

 

Claims-based authentication configuration CRM 2015 server

After you install and configure the AD FS 3.0 , we need to configure the Claims-based authentication before setting CRM 2015 binding types and the root domain.

1 Open the CRM Deployment Manager.

CRM 2015 Deployment Manager Launch

2 In the Actions pane , click Properties .

CRM 2015 Internal CRM Settings

3 Click the Web Address page.

4 In the Binding Type , select HTTPS .

Screenshot 2014 07 10 17 09 07

5. You can most likely select Apply at this point, and the default internal address for the CRM will work fine. We however we had you created a new A record in the DNS for “internalcrm” and pointed it to this new server. This allows us to user a clear path for the internal URL.

6 For example, internalcrm.iwebscrm15.com:444 for our install. (you can use your own domain internalcrm.domain.com:444)
Note: We use the :444 as this is the HTTPS binding that we applied to the Microsoft Dynamics CRM Website in IIS

Screenshot 2015 02 19 18 18 28 

CRM 2015 Web Addresses

7 Click OK.

8 In the Deployment Manager console tree, right-click Microsoft Dynamics CRM, and then click Configure Claims-Based Authentication.

Screenshot 2014 07 10 17 59 37

9 Click Next on the Welcome page

10  On the Specify the security token service page, enter the Federation metadata URL, in our case because we setup a DNS record for “adfs” we are going to use that: https://adfs.iwebscrm15.com/federationmetadata/2007-06/federationmetadata.xml
Note: that this is the same URL we tested ADFS was set up correctly on in the steps above. Also note that the step of adding the domain to internal sites in the IE security settings that we did above is an important one! If you can’t hit that URL on the web browser of the server and get a clean XML defined page, then you deployment will not work.

CRM 2015 Claims Based Authentication

11 Click Next then select the certificate that we created perviously for the *.domain connection

CRM 2015 Claims Based Authentication

12 Select Next
Note: At this point it is possible to get an error something along the lines of “Encrypted Certificate Error”. This is implying that the account used to run CRM does not have access to the Private Key of the certificate being used. Skip forward to point 25 below, and add the service accounts that CRM is using to the private key of the certificate to be used. This will ensure that this next configuration step has access to the certificate. Then come back to this point and continue. 

Screenshot 2014 07 10 18 09 58

13 Select Apply (BUT – NOT FINISH)

Screenshot 2014 07 10 18 10 31

14 IMPORTANT – Click View Log File

Screenshot 2015 02 19 16 26 26

15 Scroll to the end, and Copy the URL from the bottom of the file.

Screenshot 2015 02 19 18 26 29

This will be used in the next configuration.
Note: that this is different to the URL used in step 4 above, as it represents the internal URL. Subtle but vital (and the cause of frustration the first 10 times we tried this). In our case the URL looked like this: https://internalcrm.iwebscrm15.com:444/FederationMetadata/2007-06/FederationMetadata.xml

16 Click Finish.

Set the CRM AppPool account and the Microsoft Dynamics CRM Encryption certificate.

17 Right Click the Start Button and select RUN

18 Type MMC and enter

Run MMC

19 Select File / Add/Remove Snap-in

Add Remove Snap-in

20 Select Certificates and Add

Add Certificates MMC

21 Select Computer Account

Computer Account

22 Local Computer is selected, so click Finish

Screenshot 2015 02 19 16 57 47

23 Expand the console tree / Personal / Click Certificates

Screenshot 2015 02 19 17 00 09

24 Right click the certificate we used for the CRM endpoint, and select All Tasks / Manage Private Keys

CRM IFD Manage Private Keys

25 Select Add

Screenshot 2015 02 19 17 04 11

26 Select Advanced

Screenshot 2015 02 19 17 11 47

27 Select Find Now

Screenshot 2015 02 19 17 12 34

28 Scroll Down and Find the NETWORK SERVICE Account

Network Service Account

29 Select OK / OK

Screenshot 2015 02 19 17 15 08

Ensuring that the NETWORK SERVICE has Read Access

Screenshot 2015 02 19 17 40 44

Note: We have used the NETWORK SERVICE account here because that is the one associated with the CRMAppPool used in IIS by default for the Microsoft Dynamics CRM Website that was automatically configured with the CRM setup.

Screenshot 2015 02 19 17 19 28

CRMAppPool

If you are using another account for running the application pool, then you should ensure that this account has access to the encryption certificate. Some details can be found here.

30 Validate that you can browse to the URL above. If you cannot view this in a browser, then have a look again at your permissions on the certificate in relation to the account on the application pool in IIS for CRM. Read above: Claims-based authentication configuration CRM 2015 server.

Screenshot 2015 02 19 18 24 33

Once you can browse this URL, you are done if it fails, then repeat the process till you can access the URL on the server in question. Note: Often it is confusion over the port :5555 that defaults in CRM Deployment Manager Web settings and the HTTPS Port :444 that we defined in the binding for the Microsoft CRM Dynamics Website. So double check that you have the correct port set in the Deployment Manager, then run the steps again following that setting.

Claims-based authentication configuration AD FS 3.0 server

After completion of the previous step, the next step we need AD FS 3.0 to add and configure the statement provider trust ( claims Provider trusts ) and the relying party trust ( Relying Party trusts ).

Configure claims provider trusts

Start AD FS 3.0 Management. In the Navigation Pane, expand Trust Relationships, and then click Claims Provider Trusts. Under Claims Provider Trusts, right-click Active Directory, and then click Edit Claims Rules.

Screenshot 2014 07 10 18 27 02


In the Rules Editor, click Add Rule, In the Claim rule template list, select the Send LDAP Attributes as Claims template, and then click Next

Screenshot 2014 07 10 18 27 33


Step10: Create the following rule

Claim rule name: UPN Claim Rule (or something descriptive)
Attribute store: Active Directory
LDAP Attribute: User Principal Name
Outgoing Claim Type: UPN

Screenshot 2014 07 10 18 34 58

Click Finish, and then click OK to close the Rules Editor

After you enable claims-based authentication, you must configure Dynamics CRM Server 2015 as a relying party to consume claims from AD FS 3.0 for authenticating internal claims access.

Start AD FS Management. On the Actions menu located in the right column, click Add Relying Party Trust. In the Add Relying Party Trust Wizard, click Start.

On the Select Data Source page, click Import data about the relying party published online or on a local network, and then type the URL you copied earlier from the log file during the creation of the CRM Claims Based Authentication. e.g. https://internalcrm.iwebscrm15.com:444/FederationMetadata/2007-06/FederationMetadata.xml

Screenshot 2014 07 10 18 38 23

On the Specify Display Name page, type a display name, such as CRM Claims Relying Party, and then click Next.

Screenshot 2014 07 10 18 40 57

Click Next on the multi-factor authentication options.

Screenshot 2014 07 10 18 41 35

On the Choose Issuance Authorisation Rules page, leave the Permit all users to access this relying party option selected, and then click Next.

Screenshot 2014 07 10 18 41 44

On the Ready to Add Trust page Click Next

Screenshot 2015 02 19 19 02 22

On Finish Page, click the checkbox option to Open the Edit Claim Rules, Next, and then click Close.

Screenshot 2015 02 19 19 04 59

The Rules Editor appears, click Add Rule. Otherwise, in the Relying Party Trusts list, right-click the relying party object that you created, click Edit Claims Rules, and then click Add Rule.

Screenshot 2014 07 10 18 42 52

In the Claim rule template list, select the Pass Through or Filter an Incoming Claim template, and then click Next.

Screenshot 2014 07 10 18 44 21

Create the following Rule #1
Claim rule name: Pass Through UPN (or something descriptive)
Incoming claim type: UPN
Pass through all claim values

Click Finish.

Screenshot 2014 07 10 18 44 59

Screenshot 2014 07 10 18 50 07

In the Rules Editor, click Add Rule, in the Claim rule template list, select the Pass Through or Filter an Incoming Claim template, and then click Next

Screenshot 2014 07 10 18 50 26

Create the following Rule #2

Claim rule name: Pass Through Primary SID (or something descriptive)
Incoming claim type: Primary SID
Pass through all claim values

Click Finish

Screenshot 2014 07 10 18 51 11

Screenshot 2014 07 10 18 51 23

In the Rules Editor, click Add Rule. In the Claim rule template list, select the Transform an Incoming Claim template, and then click Next.

Screenshot 2014 07 10 18 51 59

Create the following rule #3

Claim rule name: Transform Windows Account Name to Name (or something descriptive)
Incoming claiming type: Windows account name
Outgoing claim type: * Name
Pass through all claim values

Screenshot 2015 02 19 19 10 09

Click Finish, and when you have created all three rules, click OK to close the Rules Editor.

Screenshot 2014 07 10 18 53 20

Click OK

Enable Forms Authentication

AD FS in Windows Server 2012 R2, forms authentication is not enabled by default.

Open the AD FS management console and click Authentication Policies. Under Primary Authentication, Global Settings, Authentication Methods, click Edit.

Screenshot 2015 02 19 19 13 39

Under Intranet, enable (check) Forms Authentication

Screenshot 2014 08 02 18 06 40

So now we have claims setup for CRM.

Add the ADFS server to the Local intranet zone.

We previously added the *.domain.com or in our case, *.iwebscrm15.com to the Local intranet zone in Internet explorer on the server. If you have not done this you should do it now. Then:

1. Select the Advanced tab. Scroll down and verify that under Security Enable Integrated Windows Authentication is checked.

Screenshot 2015 02 19 19 37 22

2. Click OK to close the Internet Options dialog box.You will need to update the Local intranet zone on each client computer accessing Microsoft Dynamics CRM data internally. 

Specify the security token service

1 Open a command line tool .

2 Enter the following command : ( application, in your own environment, substitute the name of the name of the command line )

c: \> setspn -a http/sts1.iwebscrm15.com fserver4\VSERVER06

fserver4\VSERVER08 = the domain / machine name of the server.

Screenshot 2015 02 19 21 33 22

c: \> iisreset

 

Configure Internet-Facing Deployment in CRM Deployment Manager.

1 Open the CRM Deployment Manager.

2 In the tree structure , right-click Microsoft Dynamics CRM , and then click Configure Internet-Facing Deployment.

Screenshot 2014 08 02 18 14 52

3 Click Next.

Screenshot 2014 08 02 18 15 20

4 Fill in the correct domain information for the Web Application

Thus we use:

  • Web Application Server Domain: iwebscrm15.com:444
  • Organization Web Service Domain: iwebscrm15.com:444
  • Web Service Discovery Domain: dev.iwebscrm15.com:444 
     Screenshot 2015 02 19 20 15 10

Leave the Default option for the Internet Facing Server Location

Screenshot 2015 02 19 20 17 15

System Checks work

Screenshot 2015 02 19 20 18 19

IFD Summary looks like this. Then Apply

Screenshot 2015 02 19 20 19 00

Finish

Screenshot 2015 02 19 20 19 41

9. Open a command line tool, run: iisreset

Screenshot 2015 02 19 22 11 38

 

ADFS Relying Party Trust for the IFD Endpoint

Effectively you are creating the third Relying party trust in your deployment and the second that you have manually set up at this point. We are doing this again as this is now for the IFD endpoint.

Step 1: Start AD FS Management. On the Actions menu located in the right column, click Add Relying Party Trust. In the Add Relying Party Trust Wizard, click Start.

image

Step 2: On the Select Data Source page, click Import data about the relying party published online or on a local network, and then type the URL to locate the federationmetadata.xml file. This federation metadata is created during IFD Setup.

For example, https://auth.iwebscrm.com:444/FederationMetadata/2007-06/FederationMetadata.xml (Remember to replay your domain for ours)

Type this URL in your browser and verify that no certificate-related warnings appear.

Screenshot 2015 02 19 21 50 58

Step 3: On the Specify Display Name page, type a display name, such as CRM IFD Relying Party, and then click Next

image

Step4: On the Choose Issuance Authorization Rules page, leave the Permit all users to access this relying party option selected, and then click Next.

Screenshot 2015 02 19 21 51 44

Click Next

image

Screenshot 2015 02 19 21 52 25

Step 5: On the Ready to Add Trust page, click Next, and then click Close.

Step 6: If the Rules Editor appears, click Add Rule. Otherwise, in the Relying Party Trusts list, right-click the relying party object that you created, click Edit Claims Rules, and then click Add Rule

image

Step 7: In the Claim rule template list, select the Pass Through or Filter an Incoming Claimtemplate, and then click Next.

image

Step 8: Create the following rule#1

Claim rule name: Pass Through UPN (or something descriptive)

Incoming claim type: UPN

Pass through all claim values

Click Finish

image

Step 9: In the Rules Editor, click Add Rule, and in the Claim rule template list, select the Pass Through or Filter an Incoming Claim template, and then click Next

image

Step 10: Create the following rule#2

Claim rule name: Pass Through Primary SID (or something descriptive)

Incoming claim type: Primary SID

Pass through all claim values

Click Finish

image

Step 11: In the Rules Editor, click Add Rule. In the Claim rule template list, select the Transform an Incoming Claim template, and then click Next.

image

Step 12: Create the following rule #3

Claim rule name: Transform Windows Account Name to Name (or something descriptive)

Incoming claim type: Windows account name

Outgoing claim type: Name

Pass through all claim values

Click Finish, and when you have created all three rules, click OK to close the Rules Editor.

image

Now, you should see three Relying Party Trusts in the ADFS Trust Relationships.

Screenshot 2015 02 19 22 23 41


Test External Access to CRM 2015 with IFD

Now, you should use the claims certified external access CRM 2015 a. In IE the browser CRM 2015 external address (for example: https://crm2015.iwebscrm15.com:444/main.aspx ), you will see the following pages:

Screenshot 2015 02 19 22 20 28

Enter the user name password in the format “domain\username”  and pass. You should get in fine.

 

Turn the Firewall Back On

As you may expect, this is a rather important last step

1. Turn on all Firewall Settings as they were at the start

Screenshot 2015 02 19 22 50 17

2. Click Advanced Settings 

Screenshot 2015 02 19 22 51 06

3. Click Inbound Rules / New Rule

Screenshot 2015 02 19 22 52 22

4. Select Port / Next

Screenshot 2015 02 19 22 46 28

5. Select TCP and Specify Port 444

Screenshot 2015 02 19 22 46 54

6. Allow the Connection

Screenshot 2015 02 19 22 47 08

7. Domain, Private and Public all ticked.

Screenshot 2015 02 19 22 47 28

8. Give it a name like: CRM Port 444

Screenshot 2015 02 19 22 47 46

And you are about finished. Remember if in the future you are mucking with something and getting no place. Turn off the Firewall as a starting point. Banging heads with firewalls is a waste of time!

Remember to test access again externally!

 

Your Feedback and Our Services

Please post a comment or note if you have anything to add about these notes. We welcome feedback that helps us improve them.

If you have a need for CRM 2015 Developer Services, we offer professional services and support for CRM 2015. This includes upgrade services for upgrading from any of the past CRM releases to new ones. We also write custom plugin solutions and are specialists with advanced web services and portals that connect to CRM for many applications. http://www.interactivewebs.com/crm

 

 

 

Enabling Replication Failed The System Cannot Find the Path Specified Hyper-V

Enabling Replication Failed The System Cannot Find the Path Specified Hyper-V

While trying to replicate a Hyper-V server you receive the following error:

Enabling replication failed

Hyper-V failed to enable replication for virtual machine “Machine Name”: The system cannot find the path specified. (I0x80070003). (Virtual machine ID “ID Number”)

HyperV Replication Failed Path

Cause

The likely cause is that you have removed the path that was set under the replication server (or receiving servers) replication settings.

Under the Hyper-V Setting on the receiving or replication server, click on the “Replication Configuration Enabled as a Replication server”

Screenshot 2014 10 09 02 47 09

The Fix

Browse to the directory defined under “Specify the default location to store replica files” and ensure that the path is valid. 

The likely cause is that the folder defined here was removed and needs to be redefined. This can happen when you are cleaning shop.

Replciation Folder Selection Hyper-V

 

 

How to Disable the CRM 2013 Welcome Screen Popup

CRM 2013 has an annoying CRM 2013 Welcome Popup (First Things First)

CRM 2013 Welcome Popup

Not exactly sure why they did not predict the need to turn of this popup Organisation by organisation, however the solution is to just turn it off for good.

The Solution

On the CRM server, run “Regedit.exe” as an administrator.

  • Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSCRMAdd  and right click to new 32 Bit DWord

CRM Stop Popup

 

  • Name the new Dword: DisableNavTour

DisableNavTour

  • Set the Data Value to 1

Screenshot 2014 08 29 18 18 17

  • Restart IIS

Screenshot 2014 08 29 18 20 11

That’s it, your CRM server should never show the Popup again.

adfs/services/trust/mex Returns 503 on CRM 2013 Windows 2012 IFD – MEX EndPoint Fix

When browsing to your CRM server: /adfs/services/trust/mex  you receive an 503 Error.

In our case this was to “https://sts1.iwebscrm.com/adfs/services/trust/mex” and we received the 503 Error. This became evident as we were testing the importing and upgrading of custom JS scripts from CRM 4.0 and CRM 2011 to use the new SDK in CRM 2013. When we used fiddler to look at why the test environment failed we noticed a call to the ADFS mex endpoint.

Screenshot 2014 08 29 00 54 30

Looking at the ADFS Logs for the server will show a 102 Error:

There was an error in enabling endpoints of Federation Service. Fix configuration errors using PowerShell cmdlets and restart the Federation Service.

Additional Data
Exception details:
System.ServiceModel.AddressAlreadyInUseException: There is already a listener on IP endpoint 0.0.0.0:808. This could happen if there is another application already listening on this endpoint or if you have multiple service endpoints in your service host with the same IP endpoint but with incompatible binding configurations. —> System.Net.Sockets.SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted
at System.Net.Sockets.Socket.DoBind(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Bind(EndPoint localEP)
at System.ServiceModel.Channels.SocketConnectionListener.Listen()
— End of inner exception stack trace —
at System.ServiceModel.Channels.SocketConnectionListener.Listen()
at System.ServiceModel.Channels.ConnectionAcceptor.StartAccepting()
at System.ServiceModel.Channels.ExclusiveTcpTransportManager.OnOpen()
at System.ServiceModel.Channels.TransportManager.Open(TransportChannelListener channelListener)
at System.ServiceModel.Channels.TransportManagerContainer.Open(SelectTransportManagersCallback selectTransportManagerCallback)
at System.ServiceModel.Channels.TcpChannelListener`2.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Dispatcher.ChannelDispatcher.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at Microsoft.IdentityServer.ServiceHost.STSService.StartSTSService(ServiceHostManager serviceHostManager, ServiceState serviceState)

The Cause

This is caused because the CRM Sandbox service is using port 808.  As you can read here: http://technet.microsoft.com/en-us/library/hh699823.aspx

The Fix

The fox for this is very easy. We need to use a PowerShell command to set the nettcpport port to 809 for ADFS.

1. Open PowerShell

2. Type: Set-ADFSProperties –nettcpport 809

3. Hit enter

Screenshot 2014 08 29 00 57 21

4. Use the Services to restart ADFS or restart the entire server. 

Now browsing to the URL will give a result looking more like this:

Screenshot 2014 08 29 00 58 16

CRM 2013 Warning Data encryption will be active after the install or upgrade.

When importing a database from CRM 2011 to CRM 2013, you may receive an error:

Screenshot 2014 08 21 16 27 06

Data encryption will be active after the install or upgrade. We strongly recommend that you copy the organization encryption key and store it in a safe place. For more information, see http://go.microsoft.com/fwlink/?LinkId=316366.

Understanding This

Microsoft Dynamics CRM 2013 uses standard SQL Server cell level encryption for a set of default entity attributes that contain sensitive information, such as user names and email passwords for Server-Side Sync and authentication tokens for Yammer integration capabilities.  This feature can help organizations meet FIPS 140-2 compliance by ensuring that the data is encrypted “at rest” so that local database admins cannot read the data in the database tables directly.  For Microsoft Dynamics CRM Online, all new and upgraded organizations use data encryption.  For on-premise versions of Microsoft Dynamics CRM 2013, users who have the system administrator security role (and in the PrivUserGroup) can activate data encryption or change the encryption key after data encryption is enabled in the Settings > Data Management > Data Encryption area.  After you activate data encryption, you cannot turn it off. NB: For on-premises versions of Microsoft Dynamics CRM:

  • Changing the encryption key requires SSL configured on the Microsoft Dynamics CRM website. (This requirement can be averted by a work-around described herein, which should only be used for testing purposes.  The point of having data encryption is to have data be encrypted both in transit and at rest.)
  • It is a best practice is to change the encryption key once every year.
  • The encryption key is required to activate data encryption when you import an organization database into a new deployment or a deployment that has had the configuration database (MSCRM_CONFIG) re-created after the organization was encrypted.  You can copy the original encryption key to Notepad and paste it into the Settings > Data Management > Data Encryption dialog box after the organization import is completed.
  • When you re-enter the data encryption key, we recommend that you run the Microsoft Dynamics CRM web application using Internet Explorer to paste the encryption key into the Data Encryption dialog box.

Copy your organization data encryption key.  It is strongly recommend that you make a copy of your data encryption key.  This is particularly important for on-premise deployments that may need to reactivate data encryption after a redeployment or failure recovery.

 

How to copy a CRM 2013 Data Encryption Key for an Organization

  1. Sign in to Microsoft Dynamics CRM as a user with the system administrator security role.
  2. Go to Settings > Data Management > Data Encryption.
  3. In the Data Encryption dialog box, select Show Encryption Key, in the Current encryption key box select the encryption key, and copy it to the clipboard.


CRM 2013 Data Encryption https errorHowever, if the Microsoft Dynamics CRM website is not configured for HTTPS/SSL, the Data Encryption dialog box will not be displayed.  Instead, you’ll get the error noted at the right.  For a more secure deployment, we recommend that you configure the website for HTTPS/SSL.  As a work-around, it is possible to get at the CRM 2013 Data Encryption settings even if the website is not configured for HTTP/SSL.  To do so, use a tool that can be used to modify CRM database tables, such as Microsoft SQL Server Management Studio and open the configuration database (MSCRM_CONFIG); in the DeploymentProperties table, set DisableSSLCheckForEncryption to 1.  In order to set the property use the following SELECT and UPDATE statements:

<span style="color: #000000;">SELECT [ColumnName],[BitColumn]
FROM [MSCRM_CONFIG].[dbo].[DeploymentProperties]
WHERE ColumnName='DisableSSLCheckForEncryption'
 
UPDATE [MSCRM_CONFIG].[dbo].[DeploymentProperties]
SET [BitColumn]=1
WHERE ColumnName='DisableSSLCheckForEncryption'</span>

CRM 2013 Data Encryption KeySaving CRM 2013 Data Encryption w Unicode

After performing an IISReset on the CRM Server, you’ll be able to see the encryption screen.  Paste the encryption key in to a text editor, such as Notepad. As a best practice, save the text file that contains the encryption key on a computer in a secure location on an encrypted hard drive.  Also note that if you keep the default encryption key with all the special hieroglyphic characters, you’ll need to save the file with Unicode encoding — see screenshot below.  Also, note, there is one data encryption key per organization.

Testing our system, I backed-up our test Adventure Works CRM organization database, and restored it as AdvWrks2.  I imported (re-deployed) the AdvWrks2 database to create a new CRM org.  I browsed to Settings => Admin => Users, and selected my User.  I changed the Primary E-mail address and hit save.  Here’s where I got a “Data Encryption error — There are encrypted fields in the organization database, but the data encryption feature isn’t activated.” What this means is that the org that I originally backed-up had encryption enabled, and we copied and re-deployed that org to the new org — which is now requiring data encryption be activated with the Encryption Key from the original org. I went ahead and activated using the Encryption Key that I had previously saved, and got the good news that the Encryption Key was activated successfully.
CRM 2013 Data Encryption - encryption not activated error

So we’ve seen CRM 2013 Data Encryption be activated automatically, by simply installing CRM, as noted in the highlighted paragraph at the top of this post. We also know that Data Encryption will be enabled on all CRM Online deployments.

We’ve further seen that when an encrypted CRM database is restored and redeployed it requires that data encryption be activated with the appropriate encryption key. If you ever think you may want to restore your CRM organization database for disaster recovery or redeploy your CRM system for testing or operational reasons, you simply must save off the encryption key of your existing CRM system. 

Reference: http://www.crmphilly.com/crm-2013-data-encryption/

CRM 2011 to 2013 “Database cannot be started in this edition of SQL Server” error when restoring a Microsoft Dynamics CRM database.

When restoring a database that is a backup of a CRM 2011 database and you are restoring it to a CRM 2013 server running SQL 2012 but not Enterprise, you may receive an error: 

“Database cannot be started in this edition of SQL Server” error when restoring a Microsoft Dynamics CRM database.

This error only happens when the original SQL instance was running an enterprise version and the destination server is not.

Screenshot 2014 08 21 15 45 58

The Cause

When Microsoft Dynamics CRM 2011 is installed using a Microsoft SQL Server Enterprise edition, a partition is created for the auditing functionality of Dynamics CRM 2011. The AuditBase table uses partitioning which is only available for Microsoft SQL Server Enterprise.

The Solution

Use the following Steps and Script to remove the partitioning. The following script recreates all the indexes on the Primary partition and then drops the partition.

Be sure to have a database backup of the ‘Org_MSCRM’ before performing the following steps. 

1. Restore the ‘Org_MSCRM’ database to a Microsoft SQL Server Enterprise edition. It is recommended to backup and restore the database instead of running the script on the production database.

2. Run the following script against the restored database.

IF EXISTS (SELECT name FROM sys.partition_schemes WHERE name='AuditPScheme')
BEGIN
 SELECT 
  CASE WHEN ind.type != 1 
   THEN 
    'DROP INDEX [dbo].[AuditBase].' + QUOTENAME(ind.name) + ' ' 
   ELSE ' ' 
  END + 
  'CREATE ' + CASE is_unique WHEN 1 THEN 'UNIQUE ' ELSE '' END  +
  ind.type_desc + ' INDEX ' + QUOTENAME(ind.name  COLLATE SQL_Latin1_General_CP1_CI_AS )  + ' ON [dbo].' +  QUOTENAME(OBJECT_NAME(object_id)) + ' (' +
   
  REVERSE(SUBSTRING(REVERSE((
   SELECT name + CASE WHEN sc.is_descending_key = 1 THEN ' DESC' ELSE ' ASC' END + ','
   FROM
    sys.index_columns sc
    JOIN sys.columns c ON sc.object_id = c.object_id AND sc.column_id = c.column_id
   WHERE
    OBJECT_NAME(sc.object_id) = 'AuditBase' AND
    sc.object_id = ind.object_id AND
    sc.index_id = ind.index_id
   ORDER BY index_column_id ASC
   FOR XML PATH('')
        )), 2, 8000)) + ')' +
  CASE WHEN ind.type = 1 
   THEN 
    ' WITH (DROP_EXISTING = ON) ON [PRIMARY]' 
   ELSE 
    ' ' 
  END  as Script 
 INTO #indexesScript
 FROM sys.indexes ind
 JOIN sys.partition_schemes ps on ind.data_space_id=ps.data_space_id 
 WHERE
  OBJECT_NAME(object_id) = 'AuditBase'
  AND ps.name = 'AuditPScheme' 
  AND is_unique_constraint = 0 
 SELECT * FROM #indexesScript 
 
 DECLARE @recreateScript nvarchar(max)
 DECLARE indScript CURSOR FOR
 SELECT Script FROM #indexesScript
 OPEN indScript
 FETCH NEXT FROM indScript INTO @recreateScript
 
 WHILE @@FETCH_STATUS = 0   
 BEGIN   
  BEGIN TRANSACTION t1
  Execute sp_executesql @recreateScript
  
  IF @@ERROR > 0
  BEGIN 
   ROLLBACK TRAN t1
   declare @message varchar(max)
   set @message = 'Audit history recreate index failed. SQL: ' + @recreateScript 
      RAISERROR (@message, 10,1)
  END
  ELSE
  BEGIN
   COMMIT TRAN
  END
  FETCH NEXT FROM indScript INTO @recreateScript   
 END   
 DROP PARTITION SCHEME AuditPScheme
 DROP PARTITION FUNCTION AuditPFN
  
 CLOSE indScript   
 DEALLOCATE indScript 
 DROP TABLE #indexesScript
END

3. Once the script is complete you can backup the database and now you should be able to restore the database to a Microsoft SQL Server Standard edition.

Editing (Without Word) and Deleting Content

You’ve got this website and you want to change some of your wording because it just doesn’t feel right, it’s only a quick change and you’re not on your computer so you don’t have Word. Not a problem! Step 1, log in to your website using the login link in the top right.

loginImage

Now the magic can happen. Go to the section of the page you’re not happy with, put your mouse over it and a border will appear around it, in the bottom left of this newly bordered box you’ll see those 2 wonderful words “Edit Content”, click them.

editContent

A new page will load displaying your content, go in and change whatever wording you’d like then scroll down a little and click Save.

contentEditor

Undoing Changes

Crisis! You’ve accidentally rid of something you really needed and you can’t remember what it was! Crisis averted. Go back into “Edit Content” scroll all the way down to the bottom. You will see “Version History” with an arrow next to it, click it and it will expand down with the last few changes.

versionHistory

Select the last version you know was safe and click the little green button to the right of it. When you scroll up your content will be back how it was, (now you can make more changes if you want), click “Save”. Done!

Maybe you’ve decided it’s all wrong! It has to go! Very carefully put your mouse over the gear symbol next to the edit pencil, hover over it and a menu will appear. In there you’ll see “Delete”, click to remove it, but only if you’re sure!

deleteModule

Editing Websites With Word 365

It is time! Your website is up and running, but you’ve got some information burning away that needs to go on the website. Step 1: Log in to the website (top right hand corner of the site).

loginImage

Now you’re logged in, you’ll see a bit black bar at the top of the screen, we need to edit the page, so click on “Edit Page” to the top right hand side of the page. Then in the menu that opens, click “Edit this Page”.

editMode

Next, in the top right of the area you want to edit you’ll see 3 icons, hover over the pencil to show a menu. Click “Edit in Word” (To see how to do it without Microsoft Word check out our post on “Editing (Without Word) and Deleting Content”).

editInWord

If this is your first time, something strange will happen, a box will open and tell you that you need to install something. Lets get briefly technical for those who care, but you can skip to the next paragraph if you just want to get on with it. We’ve installed something called a “module” that will allow the website to open Word 365 and Accept information from Word 365 because we built it to suit Microsoft’s software. They however did not build Word with us in mind (rude right?), so this software install lets Word know how to send your content to the website.

downloadAddin

We now need to install this bit of software so click “Download Word Addin” Then follow the install prompts to get Word 365 comfortable with our software.

When complete we can open our content in Word 365 and edit the  content in the same way we would edit any other document, then it’s just a matter of clicking the big orange “Publish” and your website gets updated!

publishContent

1 2 3 35