Monday, 24 March 2014

Office365: Force DirSync to synchronize AD with the cloud

If you don't want to wait for dirsync to operate within its interval, you could force it to make instant synchronization.
To do this, follow the procedure:

1.Run Powershell
2.Go to the directory where you have installed dirsync tool.
In my case it was:
Program Files\Windows Azure Active Directory Sync
3.Run the script:
4.In new window which will appear, run 

The directory has been synchronized.

Wednesday, 12 March 2014

Exchange 2010/2013: Reconnect mailboxes for deleted users

When you delete user account from AD and not delete mailbox itself, it is possible to reconnect this mailbox to the other user.
First find in which database this mailbox exists. If you remember only name of the user, you can use -match operator:

Get-MailboxDatabase|Get-MailboxStatistics|where {$_.displayname -match "Kowalski"}|fl displayname,mailboxguid

Then you should get MailboxGuid you need.
Next, select or create mail disabled user and point it with connect-mailbox command

Connect-Mailbox MailboxGuidhere -database databasename -user newuser

Office365: Cannot use connect-msolservice cmd-let

When I've tried to use Connect-MSolService to manage users in Office365 from powershell it turned out that I can't use this cmd-let.

I thought that I didn't install some of components probably, but this was not the case.
I'm in the middle of migration from on-premises to the cloud.

I have not finished configuring main domain and I've tried to connect to Office365 with the main domain which MX record still points to on-premises server.

If you need to manage user accounts in Office365 and you didn't moved your domain the cloud, use the WWW panel(EAC).

After migration I still cannot use MSolService module.
I've found the right reason: the module was in System32 path folder, which is used by 32bit systems.
After moving it to the same place in SysWow64 path, module has been loaded correctly.
So, the really fix is:
Copy folders MSOnline and MSOnlineExtended from C:\Windows\System32\WindowsPowershell\v1.0\Modules

Saturday, 1 March 2014

Exchange2013: SP1 has been released!

SP1 for Exchange 2013 has been released. You can download it   h e r e
Some known issues are now fixed:
  • 2860242 HTML format is lost after saving as an MSG file in Exchange 2013
  • 2900076 Mailbox quota warning message uses an incorrect language in Exchange Server 2013
  • 2910199 "Reply all by IM" chat window displays seven recipients in Outlook Web App
  • 2913999 Meeting request body and instructions are lost in delegate's auto-forwarded meeting request
  • 2918655 Microsoft.Exchange.Servicehost.exe crashes after you enable FIPS
  • 2918951 Users cannot access public folders after you upgrade to Exchange Server 2013 Cumulative Update 3
  • 2925281 Outlook connectivity issue if SSLOffloading is "True" in Exchange 2013
  • 2925544 Empty ExternalURL value for ActiveSync virtual directory after build-to-build upgrade of Exchange Server 2013
  • 2927708 Resource mailboxes that are created by EAC will not be updated by policies in Exchange Server 2013
  • 2928748 Default from delegate's address in shared mailboxes in Exchange Server 2013
  • 2928803 Long server connection for Outlook after a database failover in Exchange Server 2013
  • 2930346 POP3 access does not work if the name of the resource mailbox differs from the user's name
  • 2930348 Manual redirection occurs in Outlook Web App if External URLs in each site are the same
  • 2930352 Outlook Web App cross-site silent redirection does not work in Exchange Server 2013