Error message when you try to connect to Office 365 Forest with Exchange Management Shell (EMS) or Exchange Management Console (EMC): “The WinRM client… cannot determine the content type of the HTTP response from the destination computer”

Posted on April 2, 2013 by Idit Bnaya

In my case I add a problem to connect to Office365 forest with my domain credentials .

When trying to connect to Office365 Forest using EMC with my admin onmicrosoft (admin@domain.onmicrosoft.com) user it worked fine.

When trying to connect to Office365 Forest using EMC by checking the “Logon with default credentials” :

image

I got the following error :

image

When trying to write my user name and password in the domain , I got the following error :

clip_image001

 

Solution :

The solution was very simple , all I had to do is to write my full domain User Principal name (UPN) : Idit@domain.com and it worked

* If you are still getting the same error , try to follow this article : http://support.microsoft.com/kb/2028305

 

Good luck Smile

Posted in Office365, Office365 Proplus | Leave a comment

Error message when you try to connect to Office 365 Forest with Exchange Management Shell (EMS) or Exchange Management Console (EMC): "The WinRM client… cannot determine the content type of the HTTP response from the destination computer"

Posted on April 2, 2013 by Idit Bnaya

In my case I add a problem to connect to Office365 forest with my domain credentials .

When trying to connect to Office365 Forest using EMC with my admin onmicrosoft (admin@domain.onmicrosoft.com) user it worked fine.

When trying to connect to Office365 Forest using EMC by checking the “Logon with default credentials” :

image

I got the following error :

image

When trying to write my user name and password in the domain , I got the following error :

clip_image001

 

Solution :

The solution was very simple , all I had to do is to write my full domain User Principal name (UPN) : Idit@domain.com and it worked

* If you are still getting the same error , try to follow this article : http://support.microsoft.com/kb/2028305

 

Good luck Smile

Posted in Office365, Office365 Proplus | Leave a comment

Office365 proplus – Enable BlackBerry

Posted on March 21, 2013 by Idit Bnaya

1. Login to your office 365 portal online  – portal.microsoftonline.com

2. Under – Service settings –> Mobile –>  Enable service

image

Posted in Office365, Office365 Proplus | Leave a comment

Office 365 – Set multiple Federated Domains

Posted on March 20, 2013 by Idit Bnaya

you currently have an AD FS 2.0 server that is configured to support a single federated domain .

you need to use SSO to Login to Office365 with more then one domain.

There is now a rollup 2 for AD FS 2.0 (http://support.microsoft.com/kb/2681584) that works in conjunction with the “SupportMultipleDomain” switch to enable the AD FS server to support this scenario without requiring additional AD FS 2.0 servers.

Steps to add more federated domains :

  1. Open the Microsoft Online Services Module.
  2. Run $cred=Get-Credential. When the cmdlet prompts you for credentials, type your Office 365 administration account credentials.
  3. Run Connect-MsolService -Credential $cred. This cmdlet connects you to Office 365. Creating a context that connects you to Office 365 is required before running any of the additional cmdlets installed by the tool.
  4. Run Set-MsolAdfscontext -Computer <AD FS 2.0 primary server>, where <AD FS 2.0 primary server> is the internal FQDN name of the primary AD FS 2.0 server. This cmdlet creates a context that connects you to AD FS 2.0.
  5. Ensure you are able to update the current trust (Office 365 – Set multiple Federated Domains
  6. After and only after ensuring you can update the trust perform the following on the AD FS Primary server, once you complete this step users won’t be able to logon (if you have multiple servers this will only affect the users for this one server):
    • Open the “AD FS 2.0 Management Console”
    • Navigate to the Relying Parties node (Trust Relationships |Relying Party Trusts)
    • Delete the Relying party “Microsoft Office 365 Identity Platform” or “Microsoft Online Trust”

image

7. Update-MsolFederatedDomain -DomainName <domain> -SupportMulitpleDomain where <domain> is the domain is your current federated domain

8. Run Convert-MsolDomainToFederated -DomainName <NewDomain> -SupportMulitpleDomain where <NewDomain> is the domain to be converted. This cmdlet changes the domain from standard authentication to single sign-on.
For example Convert-MsolDomainToFederated –DomainName cloud.co.il –SupportMulitpleDomain

9.Run Update-MsolFederatedDomain -DomainName <NewDomain> -SupportMulitpleDomain where <NewDomain> is the domain you just converted
For example Update-MsolFederatedDomain –DomainName cloud.co.il -SupportMulitpleDomain

image

Good Luck!

Posted in ADFS, Office365 | 1 Comment

ADFS proxy service failed to start – Error 1053

Posted on March 20, 2013 by Idit Bnaya

 

The ADFS Proxy wizard failed with the following error – “Unable to start AD FS 2.0 Windows service”

image

Event viewer :

“The AD FS 2.0 Windows Service service failed to start due to the following error:

The service did not respond to the start or control request in a timely fashion.”

image

Solution :

Add the entry below to Microsoft.IdentityServer.Servicehost.exe.config file, located in the ADFS 2 install directory (default <C:\Program Files\Active> Directory Federation Services 2.0)

<runtime>

<generatePublisherEvidence enabled=”false”/>

</runtime>

Posted in Office365 | Leave a comment

Office 365 tenant version

Posted on March 13, 2013 by Idit Bnaya

Office 365 tenant must be version 15.0.000.0 or higher for the hybrid deployment to function correctly with Exchange 2013.

To verify the version and status of your existing Office 365 tenant, do the following:

  1. Connect to the Office 365 tenant using remote Windows PowerShell
  2. After connecting to the Office 365 tenant, run the following command:

Get-OrganizationConfig | Format-List AdminDisplayVersion,IsUpgradingOrganization

    3. Verify that your Office 365 tenant and status meet the following requirements :

  • AdminDisplayVersion parameter value is greater than 15.0.000.0
  • IsUpgradingOrganization parameter value is False

For example, “0.20 (15.0.500.5)” and “False”.

 

Good Luck!

Posted in Office365 | Leave a comment

Office 365 -Exchange 2003 issue – NDR 5.4.6 Routing Loop

Posted on February 27, 2013 by Idit Bnaya

I had this problem with one of my office 365  costumers  when i tried to send emails from on premises mailbox to the cloud and got this NDR:

Your message did not reach some or all of the intended recipients.

Subject:    test from on premises 4
Sent:    2/27/2013 7:10 PM

The following recipient(s) could not be reached:

  i386 user1 on 2/27/2013 7:10 PM
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients.  Contact your administrator.
<exh2003.domain.com #5.4.6>

Solution:

First I created on the  Exchange 2003 server  an SMTP connector that will route any mail destined for *.mail.onmicrosoft.com to the hybrid Exchange 2010 server

Then I changed the tenantID.mail.onmicrosoft.com SMTP address space to Internal Relay instead of Authoritative Exchange 2003 will send the message  through the Exchange 2010 server using the TLS secured connection.

Exchange 2003 connector properties :

image

image

image

Exchange 2010 – Accepted domain

image

 

Good luck!

Posted in Office365 | Leave a comment

Show who holds the FSMO roles in the domain and forest.

Posted on February 14, 2013 by Idit Bnaya

log onto a domain controller and run the following command.

netdom query fsmo

clip_image001

Posted in Active Directory, Windows | Leave a comment

Export Exchange legacy DN For contacts or users to a csv file with Csvde

Posted on February 12, 2013 by Idit Bnaya

Open CMD:

Run:

 

For contacts:

Csvde -d  “OU=MyContacts,DC=Idit,DC=local” -r “(objectClass=contact)” -f c:\Idit-Contacts.csv

For users:

Csvde -d  “OU=MyContacts,DC=Idit,DC=local” -r “(objectClass=users)” -f c:\Idit-Users.csv

 

Posted in Exchange 2010, Microsoft Exchange | Leave a comment

Exchange 2010 – How to change the default language for NDR’s in Exchange 2010:

Posted on February 12, 2013 by Idit Bnaya

How to change the default language for NDR’s in Exchange 2010:

get-transportconfig | set-transportconfig -ExternalDsnLanguageDetectionEnabled $false -ExternalDsnDefaultLanguage en-us -InternalDsnLanguageDetectionEnabled $false -InternalDsnDefaultLanguage en-us

Posted in Exchange 2010, Microsoft Exchange | Leave a comment