Monday, July 4, 2022
  • Home

October 11th, 2010 by admin


You are using Quest Notes Migrator for Exchange (NME) to migrate from Lotus Dominos to Exchange Online/Exchange On-premise, and on migrating the user accounts, new emails are no longer entering Lotus Dominos.

grand online casino bonus slots free
Problem Statement:

You want to have a copy of the new email stored in Lotus Dominos and have a copy forwarded to Exchange Online/Exchange On-premise.


To be exact, there is no solution to this, as Quest NME tool doesn't allow the support to have a copy left on the Lotus Dominos before forwarding it to Exchange Online/Exchange on-premise.

However it might be possible (correct me if I'm wrong) to configure Lotus Dominos directly to leave a copy before forwarding it, if NME tool modifies Lotus Dominos parameters directly.

Posted in Uncategorized | Comments Off on

October 11th, 2010 by admin

Question: I already have imported the Relying Party metadata, and configured the claims rules. SP-initiated request is working. However, how do I do an IDP initiated request?

Answer: Once the ADFS 2.0 is configured, both SP and IDP initiated request should work by default.

IDP Initiated link example:

Note: ADFS in bold is the server name of of the ADFS server. delphi math

Posted in Uncategorized | Comments Off on

October 11th, 2010 by admin


If your Office 365 environment is using multiple domain (eg,;, and you would like to setup ADFS for your Office 365 environment, by executing the below, it fails:

Convert-MsolDomainToFederated -DomainName

The error shows that the Office 365 tenant has another domain registered with it.


Will need to recreate the Relying Party that the Convert-MsolDomainToFederated PS Script has created, and rerun the above with the -SupportMultipleDomain:

Convert-MsolDomainToFederated -DomainName -SupportMulitpleDomain
Update-MsolFederatedDomain -DomainName -SupportMulitpleDomain

Do the above for all the different domains. virtual treeview delphi

Posted in Uncategorized | 14 Comments »

October 11th, 2010 by admin

Again, with the importance of having a fast connectivity speed to cloud offerings, there are extra links for you to have a more accurate speed details to the cloud.

Use the following appropriate links to do your own speed test based on your Office365 service location:




For Lync:

Let me know if this helps!

Posted in Uncategorized | Comments Off on

October 11th, 2010 by admin

For a particular customer, internet speed to any local servers (and download from certain overseas servers) is really fast – they are getting full speed that the ISP is offering.

However, to check what speed your internet connectivity is getting from Microsoft Online Services (Yes, for those of you are planning to move to Office365 or is already on Office365), you can check on the speed that you are getting at:

Wait for it…

(Speed test requires your computer to have Java installed)

gaming club online casino slots real money
So what does it test?

– Download and Upload speed to Microsoft Online Services
– Routes/hops that passes through the ISPs and the latency + packet loss
– Download capacity that it can reach

A sample test result can be viewed here.

Posted in Uncategorized | Comments Off on

October 11th, 2010 by admin

When setting up Office365/Exchange 2010, it is very common to assist the customer to create distribution groups.

This is my way to script it to speed up the creation of the distribution groups:.

1. Create a CSV file for each distribution group. For my case, I have _AllStaff.CSV created. See below link for the sample of the file.


2. Use Powershell and run the following:


(The above should be the filename of your CSV file).

New-DistributionGroup -Name “_All Staff” -alias $name -primarysmtpaddress $ -memberdepartrestriction closed

(Modify the bold items to the right Distribution Group name and domain name)

Import-csv ”
D:\$name.csv” | foreach {add-distributiongroupmember -identity $ -member $_.EmailAddress}

(Point the location to the CSV file, and also specify the correct distribution group name)

What's your way in creating the distribution group?

Новости и Обзоры Онлайн Игр

Posted in Uncategorized | Comments Off on

October 11th, 2010 by admin


IIS Servers in a DMZ Zone, configured in a Workgroup.

Clustered File Servers in the corporate network, in a Domain environment.

All servers are running Windows Server 2008 R2.


When IIS web app tries to access the clustered file server hosted in the domain, it shows Access Denied.

Path to Solution:

On running Procmon.exe, w3wp.exe shows that it is trying to authenticate using whichever account. So I check my IIS Config and make sure that it is using an account which has rights to access the cluster file server in the domain.

Solution 1 – Ensure that your IIS is configured correctly with a user account that has the access rights to the cluster file server.

Specify the correct user account under Identity in the Advanced Setting

Select the Application Pool that this web application should use.

If the above does not solve the problem, please continue with Solution 2.

Solution 2 – Ensure that the username and password is the same between the domain server and the Workgroup IIS Server

If my clustered file server is using the following name:

User: domain\webapp
Password: Pa$$w0rd

Then my Workgroup IIS Server should have a local user created with the following name:

User: IISSERVER\webapp
Password: Pa$$w0rd

(IISSERVER is the name of the IIS Server)

(Make sure that all of your IIS Servers have the same username and password created as well)

Solution 3 – Use ICACLS.EXE to provide the rights to the clustered files

Now that you have the same user created on both server (Domain and Workgroup), we will have to use ICACLS.exe to provide the permission (No, using the GUI does not work):

1. Map the shared cluster to Y: Drive

2. Open Command Prompt and execute the following:


(Replace the SHAREDFOLDER to the folder that your web application needs to access; Replace the WEBAPP with the username that you created in Solution 2)

Hope this helps someone out there!

Posted in Uncategorized | Comments Off on

October 11th, 2010 by admin

Recently I was doing an email migration from Exchange On-premise to Office365, and the customer's environment is not suitable to use Dirsync.

This means that I will need to export the X500 address from my local Active Directory and import it into Office365.

Here is the brief steps if you are facing this issue:

Export the LegacyExchangeDN and mail field in your AD:
1. In your DC server, run Command Prompt
2. Run the command:
csvde -f c:\sample.csv -l legacyexchangedn,mail

Now, with that .csv file, make sure that it has a “mail” and “legacyexchangedn” under the heading. See my attached sample file: sample CSV with LegacyExchangeDN

Import the legacyexchangedn/X500 into Office365/Exchange Online using PowerShell:

1. Connect to Exchange Online. using PowerShell
2. Run the command:

Import-CSV C:\sample.csv | foreach {

free poker games online casinon spela blackjack for fun
$user=Get-Mailbox $_.mail

Set-Mailbox $_.mail -EmailAddresses $user.EmailAddresses


To check if the address has been added:
Get-Mailbox $user | FL emailaddresses

Posted in Uncategorized | Comments Off on

October 11th, 2010 by admin

If your customer has an environment that can't setup Dirsync (perhaps they are not on Windows Server 2003 DC and above), and you would want to create users manually, here is what you should do:

1. Create a CSV and use Administrative Portal | Users | Add Bulk Users to import the users.

2. Export the X500 addresses from Exchange 2003 server (You can refer to this link on how to do it).

3. Import the X500 addresses that you have exported from your local Exchange 2003 to Office365. You will have to do the following in Exchange Online Powershell:

$foo = get-mailbox jabez
$foo.emailaddresses += “X400:C=Malaysia;DC=domain;DC=com”
$foo | set-mailbox

If you are doing a temporary co-existence without using the recommended approach (Exchange 2010 Hybrid), you may also want to:

1. Create mail-enabled users with external email addresses to If you have 100 Exchange on-premise users, then you will have to create 100 extra mail-enabled users that points to the email account.

2. Create a forwarding from the Exchange on-premise to Office365

Posted in Uncategorized | Comments Off on

October 11th, 2010 by admin

Q: What is the minimum size for the quorum disk for a Microsoft Cluster?

A: 500MB

(Sorry for the short post. From now onwards, I will be using this blog to post short important notes regarding Microsoft technologies. But might still have long winded posts once in a blue moon) 🙂

Posted in Uncategorized | Comments Off on

October 11th, 2010 by admin


You installed and synchronize your AD Objects using DirSync, and Microsoft sends you lots of emails with the following content:

The following errors occurred during synchronization:

stained glass tools


Error Description

On-premises object ID

CYHN Unable to update this object because the following attributes associated with this object have values that may already be associated with another object in your local directory services: [ProxyAddresses X500:/o=ABX/ou=First Administrative Group/cn=Recipients/cn=CYHN;]. Correct or remove the duplicate values in your local directory. Please refer to for more information on identifying objects with duplicate attribute values. yhYEVVU28epkIUrQw/Q==


Microsoft Office 365 detects lots of duplicates ProxyAddresses that was synced from the local on-premise server.


These PowerShell script should help you gather the information needed to resolve this issue. Once the multiple instances on the same email address is removed from the various AD accounts dirsync should work without errors.

get-contact | where {$_.WindowsEmailAddress -match ” “} |ft identity

get-msoluser | where {$_.ProxyAddresses -match ” “} |ft userprincipalname

Get-MsolGroup | where {$_.ProxyAddresses -match ” “} |ft displayname, emailaddress

get-mailbox | where {$_.EmailAddresses -match ” “} | fl Name, RecipientType, EmailAddresses

get-DistributionGroup | where {$_.EmailAddresses -match ” “} | fl Name, EmailAddresses

get-user | where {$_.WindowsEmailAddress -match ” “} |ft identity

Posted in Uncategorized | 955 Comments »