Manage Office365 with local domain controller

Microsoft’s official stance on removing your legacy hybrid Exchange server is that you must also disable Directory Synchronization, and move to a “cloud-only” scenario. The reason being: having no on-premises Exchange server changes how you manage certain mailbox attributes–e.g. without the Exchange server in place, you must use ADSIedit or a third-party tool to do simple tasks like add alias addresses–and these methods are technically unsupported. Here are some references on this topic:



Continue reading Manage Office365 with local domain controller

Manage Office 365 Mailboxes using Directory Synchronization w/o Hybrid Exchange

When you have a hybrid environment configured between Exchange 2010 or 2013 and Office 365, then you will probably have noticed that mailbox creation and management happens on-premises. For example, to create a new mailbox, you would initiate this process from the local Exchange server instead of the Office 365 portal (e.g. New-RemoteMailbox).


Continue reading Manage Office 365 Mailboxes using Directory Synchronization w/o Hybrid Exchange

Migrate from SBS to Server 20xx Standard



First move all mailboxen from the SBS including the hidden Exchange boxes.

Create a new member server and promote it to DC.

Move FSMO Roles

The five FSMO roles are:

  1. Schema Master
  2. Domain Naming Master
  3. Infrastructure Master
  4. Relative ID (RID) Master
  5. PDC Emulator


The FSMO roles are going to be transferred, using the following three MMC snap-ins :

  • Active Directory Schema snap-in  : Will be used to transfer the Schema Master role
  • Active Directory Domains and Trusts snap-in : Will be used to transfer the Domain Naming Master role
  • Active Directory Users and Computers snap-in : Will be used to transfer the RID MasterPDC Emulator, and Infrastructure Master roles

Note: The following steps are done on the Windows Server 2008 machine that I intend to set as the roles holder ( transfer the roles to it )

Lets start transferring the FSMO roles.

  • Using Active Directory Schema snap-in to transfer the Schema Master role 

    You have to register schmmgmt.dll in order to be able to use the Active Directory Schema snap-in

  1. Click Start > Run 
  2. Type regsvr32 schmmgmt.dll
  3. Click OK

    A popup message will confirm that schmmgmt.dll was successfully registered. Click OK 

  4. Click Start Run, type mmc, then click OK
  5. Click File > then click Add/Remove Snap-in…
  6. From the left side, under Available Snap-ins, click on Active Directory Schema, then click Add > and then click OK

  7. Right click Active Directory Schema, then click Change Active Directory Domain Controller…
  8. From the listed Domain Controllers, click on the domain controller that you want to be the schema master role holder and then click on OK

    You will receive a message box stating that the schema snap-in is not connected to a schema operations master. That is for sure, as we have not yet set this Windows Server 2008 domain controller as a Schema Master role holder. This will be done in the next step. Click OK

  9. In the console tree, right click Active Directory Schema [DomainController.DomainName], and then click Operations Master…
  10. On the Change Schema Master page, the current schema master role holder will be displayed ( ex. ELMAJ-DC.ELMAJDAL.NET) and the targeted schema holder as well (ex. ELMAJ-DC2K8.ELMAJDAL.NET). Once you click Change, the schema master holder will become 
     , click Change

    Click Yes to confirm the role transfer

    The role will be transferred and a confirmation message will be displayed. Click OK

    Then click Close, as you can see in the below snapshot, the current schema master is ELMAJ-DC2K8.ELMAJDAL.NET

  • Using Active Directory Domains and Trusts snap-in to transfer the Domain Naming Master Role

Continue reading Migrate from SBS to Server 20xx Standard

Move mailboxes exchange 2010 powershell

Moving mailboxes in case of vss errors on esx veeam ackup.


Create new store.

Get-Mailbox | Sort database, name | Format-Table name, database

Get-Mailbox | Sort database, name | Format-Table name, database

Local move request of mailboxes

View progress

Exchange 2010 Export mail to PST and disable autodiscover

Make sure Exchange 2010 is patched till SP3.

First take rights to import / export.

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User support

Restart exchange powershell, otherwise the commands will not be reconised.

Make a share with rights for: Exchange Trusted Subsystem.
Start the first export!
New-MailboxExportRequest -Mailbox support -FilePath \\servername\PST\support.pst

View statistics: Get-MailboxExportRequest | Get-MailboxExportRequestStatistics

You can also export all mailboxen on the server: foreach ($i in (Get-Mailbox)) { New-MailboxExportRequest -Mailbox $i -FilePath “\\servername\PST\$($i.Alias).pst” }

Remove old exports: [PS] C:\>Get-MailboxExportRequest | where {$_.status -eq “Completed”} | Remove-MailboxExportRequest

After exporting / importing to 365, dont forget to disable the old autodiscover.

Get-AutodiscoverVirtualDirectory | fl Name, Server, InternalUrl, Identity

Remove-AutodiscoverVirtualDirectory –Identity “Insert identity value here

Set-ClientAccessServer –Identity ServerName -AutoDiscoverServiceInternalUri $null


Usg pro

Vandaag de hele dag bezig geweest en heb nu internet rechtstreeks van de NT naar USG,
Bovendien werkt IPTV ook!

Even vooraf: Vergeet stap 9 niet.

1 ) Controller uit het netwerk halen
2 ) USG gereset naar factory defaults
3 ) Ik heb de configuratie overgenomen van even naar beneden scrollen en daar staat zijn /config/config.boot file.
4 ) Aanpassen van next hop IP, mac address in het config.boot bestand EN BELANGRIJK: controleer de poort topografie, die is gebaseerd op een andere router. Voor USG Pro geldt:

eth0 = LAN/IPTV
eth1 = LAN2 (Gebruik ik niet)
eth2 = WAN
eth3 = WAN2 (Gebruik ik niet)

Zorg dus dat je dat aanpast in de config.boot file

5 ) /config/config.boot op USG hernoemen naar config.boot_OLD
6 ) Nieuwe config.boot file op de juiste plek zetten (/config/config.boot) in USG
7 ) Reboot USG
8 ) Internet werkt meteen 8)
9 ) Bovenaan staat een script dat de next hop blijft checken en eventueel aanpast. Installeer die! Dat bleek bij mij de oorzaak dat IPTV het niet meteen deed.

LET OP: Als je de controller weer aansluit kun je weer opnieuw beginnen, want die past vermoed ik de config.boot file aan.

Zou fijn zijn als er iemand een tip heeft hoe ik deze configuratie kan behouden maar dan MET controller in het netwerk.


Windows server 2016 was released for public (GA) on mid oct 2016. Its exciting time as businesses are already working on migrating their services in to new windows server 2016 infrastructures. In this post, I am going to explain how you can migrate from active directory running on windows server 2012 R2 to windows server 2016 active directory. The same steps are valid for migrating from windows server 2012, windows server 2008 R2 and windows server 2008.

In my demo setup, I have a windows server 2012 R2 domain controller as PDC. I setup windows server 2016 and already added to the existing domain.



WordPress Appliance - Powered by TurnKey Linux