Back in October I did a session at Microsoft Campus Days in Copenhagen about Exchange 2010 and Forefront Protection for Exchange and Forefront Online Protection.
At Microsoft Campus Days 2011 back in october I was attending with a session and I was also interviewed by Bjarne Dollerup. Watch the interview here (it is in danish).
To my english readers, this post is for the a Danish TechNet Quiz run by Microsoft Denmark and it is published only in Danish.
Denne julekalender låge er udvidet til at indeholde en række forskellige spørgsmål, alle Microsoft Unified Communications relateret.
Dagens spørgsmål:
Med Exchange 2007 så vi en ny Administrative Group og denne gruppe var navngivet som en form for GUID, så der ikke ville være konflikt med eksisterende Exchange implementeringer, denne gruppen hed og hedder stadig i Exchange 2010 (FYDIBOHF23SPDLT) – Men der er mere bag denne såkaldte GUID, hvad står dette reelt for ?
Hvilken attribute er brugt til at sortere Exchange CAS servers in-site ?
Hvilken attribute er sat kun for linked mailboxes ?
Proceduren er næsten den samme som sidst, første mail med flest rigtige svar i min mailbox vil være den lykkelige vinder af en super gadget gave fra Bjarne Dollerups (gave)sæk.
This is notes from a recent troubleshooting case. The client received the error: 420 4.2.0 RESOLVER.ADR.Ambiguous; ambiguous address and a lot of messages ended up in the Submission queue with this error.
The error came after running GALsync. We have two Exchange 2010 forests and was running GALsync between the two. Forest A (contoso) was using one address space (contoso.dk) and Forest B (nwtraders) was using several address spaces (nwtraders.dk, litware.dk etc).
Everything working fine between contoso.dk and nwtraders.dk, the two main address spaces, but the problem with 420 4.2.0 RESOLVER.ADR.Ambiguous; ambiguous address, came when trying to send to address space litware.dk from Forest A.
The error was caused by duplicate SMTP proxy addresses.
I have seen it before where GALsync created a contact during a sync to the target forest even though the user was already migrated to the target forest. Then we have the both a mail contact and mail user had the same SMTP address and messages to this user will be queued.
In this case the issue was quite similar, although the client had created the extra mail user themselves and when GALSync created the mail contact, the problem came.
The solution was to clean up in the proxy addresses of the two objects (mail user and mail contact) and good way of checking this is using ADSI Edit to see and confirm the proxy addresses of the objects.
Microsoft has now released mobile clients for Lync, they are long awaited in the community.
Lync 2010 for Windows Phone is now available for download via Windows Marketplace and that Lync 2010 clients for iPhone, iPad, Android, and Nokia Symbian have been submitted for approval to their respective app stores.
Exchange 2010 SP2 has finally been made available as download by the Exchange Team, this download is long awaited by many, because of the many new cool features, such as:
Outlook Web App (OWA) Mini
Cross-Site Silent Redirection
Hybrid Configuration Wizard
Address Book Policies
Read more about the new SP2 features in one of my older blog posts: .
The SP2 sets new pre-requirements to Windows, to install and upgrade from SP1. It requires an additional Windows role, which was not part of the SP1 pre-requirements. Which is:IIS 6 WMI Compatibility” not being installed. Which is:
IIS 6 WMI Compatibility
To install this before starting the SP2 install/upgrade, start a PowerShell and run:
Import-Module ServerManager
Add-WindowsFeature Web-WMI
This Windows role is required for Mailbox and CAS roles.
This is Peter Schmidt's personal blog. Here you will find my notes from the field, along with the latest news, scripting, tips about Microsoft technologies such as Exchange, Lync, IIS etc. Read more about the site and me under the About page.
Follow Me