Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
WANTED: PowerShell script to change voicemail playback for all users to LIFO

Answered WANTED: PowerShell script to change voicemail playback for all users to LIFO

  • Friday, May 04, 2012 2:35 PM
     
     
    Sign In to Vote
    0

    We are having a problem with high memory utilization on our UM servers which causes stuttering during playback of greetings and messages and MS has "identified" this as a known issue that will be addressed in SP2 RU3 in July or August.  It is related to the voicemail playback order that can be modified by the end-uer in OWA. According to our support rep at MS,  "There is a problem we have identified with the SA when the play order is set to oldest -> newest. "

    MS would like us to have users change to Last In, First Out as a work-around but I do not want to bother all our users.  I would like to run a script to modify this for all users but cannot seem to find one.  Hoping to find a PS pro here who can assist.

    Environment:

    HP DL360 G7
    Server 2008 R2 Standard SP1; 64 bit
    2 X 2.4 GHz Quad Core Intel Xeon
    12 GB Ram
    Exchange 2010 Standard, SP2

    Thanks in advance,

    John


     

All Replies

  • Friday, May 04, 2012 5:26 PM
     
     Answered
    Sign In to Vote
    1
    It appears that this setting is either in the mailbox of the user or in a binary blob of an attribute of the AD account.  No Exchange-based shell commands can do what you are looking for.  The users (or someone with full mailbox rights) will need to log into ECP for those mailboxes and make that change manually.
     
  • Friday, May 04, 2012 5:41 PM
     
     
    Sign In to Vote
    0
    Thanks for the quick response.  If that is the case, is there any way of identifying the users that have FIFO set?
     
  • Friday, May 04, 2012 5:50 PM
     
     
    Sign In to Vote
    0

    Unfortunately if that were possible then it might very well be possible to modify it.  Wish I could give you a better answer than no. :(

    May the 4th be with you...

     
  • Friday, May 04, 2012 6:42 PM
     
     
    Sign In to Vote
    0

    Hmmm, with 1500 users that is going to be a problem....

    Thanks again for your help

     
  • Friday, May 04, 2012 6:43 PM
     
     
    Sign In to Vote
    0
    Since MS is having you do this, see if they will provide you with a script or method of automating that process.
     
  • Friday, May 04, 2012 7:52 PM
     
     
    Sign In to Vote
    0

    Yep, I've already asked.  They said the fix will be in UR3 but I want the Hotfix now.  We have been fighting this since deployment in December of 2011 and I have been dealing with India support the whole time.  We finally got it escalated yesterday and within 2 hours had an answer that it was "A known problem".  I really wish they would have told India that 5 months ago.

     
  • Thursday, May 10, 2012 4:14 PM
     
     Answered
    Sign In to Vote
    0

    I would like to update this thread.  It turns out that the issue where FIFO is set only affects the system when users have more than 50 voicemail messages in their inbox (or any sub-folder) and they receive a new message.  If they dial the subscriber access number they will be prompted for their pin and at that point the system will just play a tone repeatedly.  If you run get-umactivecalls |fl >c:\umactivecalls.csv and view the file you will see the active calls.  In the list of active calls you will have an extension that shows "disconnected".  This is one of your problem users.  If you contact this user chances are that they will confirm the number of voicemails in their inbox is greater than 50 and they are using FIFO when listening to voicemail messages.

    Some work-arounds include having users listen to messages through Outlook or by using play on phone, changing the playback order to LIFO (last in, first out) which is the default or keeping the voicemail count to less than 50 in their inbox.

    Microsoft has confirmed this is a problem and will be including a fix in SP2 RU3.

     
  • Thursday, May 10, 2012 4:33 PM
     
     
    Sign In to Vote
    0
    Thanks for updating your thread and helping others that might be in the same situation.