certlm.msc - Short cut to open the certificate store for the local machine

Sometimes even small a thing can be a time saver.
So in Windows 2012 you can just type certlm.msc to start the certificates MMC with the local machine store.

Message: This account can't be used to access Outlook.com

Today I ran into an issue accessing the Office 365 Outlook Web Access.

First of all, I made the Office 365 setup for a new tenant. The school of my kids decided to test Office 365, right now they are on Google and they want teach the kids more then one cloud application.

For ADFS we already have a Windows Server 2012. So ADFS works great but the MSOL powershell commands are not working with 2012. But only this server has a public certificate, and the URL is used for other services as well. So I just added ADFS 2.0 to another server, moved the signing cert over and started the MSOL powershell commands. Then I just played copycat to get the relying party settings over to the 2012 ADFS server. After ADFS done I installed and ran DirSync. To verify my doing I went to http://outlook.com/domain.org and after ADFS authentication: BUMMER!

"This account can't be used to access Outlook.com"

So I did some web search, but nothing really helpful came up.
So I compared the relying party settings between the ADFS 2.0 server and the 2012 server and found that I missed to configure the hash algorithm to SHA-1. If it is SHA256 you will see the message above.

I suppose this is only one reason when you see that message because the message is kind of generic.

In-place migration Windows 2008 R2 to Windows 2012 Certification Authority

I migrated a couple of machine from Windows 2008 R2 to Windows 2012. Greatly it was working well also for remote machines and even a remote access server came back after a while and I could dial in again (Note: I had a SSH connection to the host for backup to get in - I am not that brave.)

Last migration I did was a CA and after migrating I could request certificates and I saw new CRLs. So all is good. Almost, I could not see the MMC for certificate templates and the certification authority.
I had to manually install them first.

or take the shortcut:

c:\>dism /online /enable-feature /featurename:CertificateServicesManagementTools

Small thing but good to know.

DHCP server migration - Error 32: Feature DHCP Server could not be exported.

During a DHCP Server 2008 R2 to Windows 2012, moving from one virtual machine to a new virtual machine I ran into error 32 during exporting the DHCP configuration from the source server.

btw: I like SMIG because it also moves all the active leases to the new server. A regular backup/restore don't.



PS C:\system\smig> Export-SmigServerSetting -FeatureID dhcp -path c:\system\dhcp
3 -verbose


cmdlet Export-SmigServerSetting at command pipeline position 1
Supply values for the following parameters:
Password: **********
Export-SmigServerSetting : Error 32: Feature DHCP Server could not be exported.
At line:1 char:25
+ Export-SmigServerSetting <<<<  -FeatureID dhcp -path c:\system\dhcp3 -verbose
    + CategoryInfo          : InvalidOperation: (:) [Export-SmigServerSetting]
   , Exception
    + FullyQualifiedErrorId : 32,Microsoft.Windows.ServerManager.Migration.Com
   mands.ExportSvrMigSettingCommand




           ItemType ID                              Success DetailsList
           -------- --                              ------- -----------
     WindowsFeature DHCP                              False {DHCP}
VERBOSE: Details:
VERBOSE:
VERBOSE: ID: DHCP.
VERBOSE: Title: DHCP Server
VERBOSE: Result: Failed
VERBOSE: Error 32: Feature DHCP Server could not be exported.
VERBOSE:
Export-SmigServerSetting : Gathering the specified migration data failed.
The migration operation encountered an error that could not be skipped.
At line:1 char:25
+ Export-SmigServerSetting <<<<  -FeatureID dhcp -path c:\system\dhcp3 -verbose
    + CategoryInfo          : InvalidOperation: (:) [Export-SmigServerSetting]
   , MigrationException
    + FullyQualifiedErrorId : Microsoft.Windows.ServerManager.Migration.Comman
   ds.ExportSvrMigSettingCommand
PS C:\system\smig> 


I did that many times before to migration from 2003 to 2008 R2. This time I just forgot to stop the DHCP service on the source server before running Export-SmigServerSetting.

Good luck!