Solved

Exchange Management Shell Help

Posted on 2009-04-08
5
388 Views
Last Modified: 2013-11-29
Hello all,
I need a way to extract users whose RTCSIPPrimaryUserAddress does not match thier PrimarySMTPAddress. I've tried C:\>get-mailbox -resultsize unlimited | Where-Object {$_.PrimarySMTPAddress -ne $_.RTCSIPPrimaryUserAddress} but it returns all 15,000 mailboxes.  Is there a way to filter out the SIP: from RTCSIPPrimaryUserAddress.  After I've extracted the list I will need to have these two attributes match.  i.e., user1@domain.com and sip:user1@domain.com
C:\>get-mailbox -resultsize unlimited | Where-Object {$_.PrimarySMTPAddress -ne $_.RTCSIPPrimaryUserAddress}

Open in new window

0
Comment
Question by:albertbr
  • 4
5 Comments
 
LVL 10

Expert Comment

by:jayca
ID: 24103778
Wish I could help, normally I would just say disable the users, then enable with the wizard and select the "Use email address" as the SIP URI...

Whatever you do, run DBIMPEXP before you modify anything, that way if something goes wrong, your user contacts are preserved.

Might test it out on 1 user, if you see no result, try restarting the services after the change is made...
0
 

Author Comment

by:albertbr
ID: 24116452
Using [PS] C:\>get-qaduser  -SizeLimit 100 -includedproperties Email,msRTCSIP-PrimaryUserAddress | where {$_.Email -notlike "$_.msRTCSIP-PrimaryUserAddress"} | Select Displayname, Email, msRTCSIP-PrimaryUserAddress
is still not returning mismatches.  I've tried match, notmatch, like,  notlike, etc.
Is there a way to get it to ignore "sip:"?
0
 

Author Comment

by:albertbr
ID: 24116531
Forgot to mention that the second one is done in the Quest shell.  I discovered that the exchange shell would not return the SIP property.
0
 

Accepted Solution

by:
albertbr earned 0 total points
ID: 24157142
Resolved it with:
get-qaduser -SizeLimit 0 -IncludedProperties "msRTCSIP-PrimaryUserAddress" | select name,email,"msRTCSIP-PrimaryUserAddress" | export-csv C:\report.csv
0
 

Author Comment

by:albertbr
ID: 24157163
The SIP attributes are AD and not mailbox attributes.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
In this video we show how to create a mailbox database in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Servers >> Data…

867 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now