August 2007 - Posts
Hello Folks,
Today we are gonna play with the Unified Message, we will be enabling an Unfiied Messaging user and we will be visualizing how to configure some UM feature on OWA and Outlook 2007. Let's go..
First of all, Open the Exchange Management Console, choose the user and click on Enable Unified Messaging.. on the Toolbox Actions. By the way, you need a UM Server deployed in your network.

Enable Unified Messaging. We can assign a pre-defined UM Policy, clicking on Browse..

Choosing a pre-existent UM policy.

Now, we can set up a mailbox extension number and specify the PIN's user. Let's click on "Automatically generate PIN to access Outlook Voice Access", click on Enabled.

Now on the user side that user will receive a message with their PIN.

The user has a news option under Options at OWA called Voice Mail. In this section the user can set up his OVA (Outlook Voice Access) features, such as Missed Call Notifications, Reset PIN and define which folder will be readed by OVA.

On the Outlook 2007, the user will have a new tab called
Voice Mail with the same options that we have just seen on the OWA.

In this post we have seen how to enabled an user to use the UM features, and we also saw how to configure the UM feature on the OWA and Outlook 2007.
Best Regards,
Anderson Patricio
Technorati : Exchange Server 2007, Unified Messaging, Voice Access
Del.icio.us : Exchange Server 2007, Unified Messaging, Voice Access
Ice Rocket : Exchange Server 2007, Unified Messaging, Voice Access
Hello Folks,
Today my second article about Resource Forest in Exchange Server 2007 was published. Check this out: http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/deploying-exchange-resource-forest-part2.html
If you have any comments about this article you can drop me a line .
Best Regards,
Anderson Patricio.
Technorati : Exchange Server 2007, Resource Forest
Del.icio.us : Exchange Server 2007, Resource Forest
Hello Folks,
In Exchange Server 2007, the Global message size limit parameter cannot be changed using either Exchange Management Console or Exchange Management Shell, here they are:
-
Outgoing message size (submissionContentLenght)
-
Incoming Message Size (delivContLength)
-
Maximum number for recipients (msExchRecipLimit)
To change those values, we can use the legacy Exchange System Manager or the AdsiEdit.msc, as it follows:
Open Adsiedit.msc
Expand Configuration / <cn=configuration,dc=your,dc=domain,dc=local> / Services / <organization name> / Global Settings
Right-Click on Message Delivery and click on Properties

We also have the Organization limits in Exchange Server 2007 which is applied to all Hub Transport Servers. We can configure the Organization limits through the set-Transportconfig cmdlet, we have the following parameters:
-MaxRecipientEnvelopeLimit
-MaxSendSize
-MaxReceiveSize
When we have Global limits and Message limits the lowest value takes precedence. It's recommended to use both limits with the same value.
Best Regards,
Anderson Patricio
Technorati : ADSIEdit, Exchange 2007, Organization, Size Limits
Del.icio.us : ADSIEdit, Exchange 2007, Organization, Size Limits
Hello folks,
I have just published an article about Dial tone in Exchange Server 2007 at OutlookExchange.com (www.OutlookExchange.com). It will be three articles and the second and third will be available next week.
You can check this out at: http://www.outlookexchange.com/Articles/AndersonPatricio/AndersonPatricio_c1p1.asp
Best Regards,
Anderson Patricio
Technorati : Article, Dial Tone, Exchange Server 2007
Del.icio.us : Article, Dial Tone, Exchange Server 2007
Ice Rocket : Article, Dial Tone, Exchange Server 2007
Hello Folks,
The major prerequisites for Exchange Server 2007 are .Net Framework, MMC 3.0 and PowerShell installed before we deploy Exchange Server 2007.
.Net Framework and MMC 3.0 features have already installed in the Windows 2008 by default, so we have to install PowerShell and to accomplish this task we have to follow these steps:
-
Open Server Manager (Start/ Administrative Tools/ Server Manager)
-
Click on Features, then click on Add Features
-
Choose PowerShell on that list, and then click Next

Click on the image to enlarge
Final screen of the Windows PowerShell installation

Click on the image to enlarge
Now, we have to wait the Exchange Server 2007 SP1 to deploy Exchange Server 2007 on Windows Server 2008, but all Exchange Server 2007 prerequisites are done :)
Best Regards,
Anderson Patricio
Hello Folks,
If you are receiving the following message: "Access to the address list service on all Exchange 2007 servers has been denied." when you are creating a new user in Exchange Server 2007 or moving a user from Exchange Server 2003 to an Exchange Server 2007.
You might receive this error message in your event viewer as well:
Could not read the Security Descriptor from the Exchange Server object with guid=4E192984E512D349A973E39108D868AD. As a result the Proxy Address Calculation RPC interface will not be available on the local Exchange Server.
So.. What's the solution:
To validate what's is server you can run the get-exchangeserver | select name,guid to see which version is not in the Exchange Servers group. Then, add that server into the Exchange Servers group.
If you are running CCR, just move the servers between the nodes (move-clusteredmailboxserver), if you are using a mailbox server just restart it.
Solution #02
Validate if the service Microsoft System Attendant is running.
Best Regards,
Anderson Patricio
Technorati : Access to address list service on all Exchange 2007 servers has been denied, error, kb
Del.icio.us : Access to address list service on all Exchange 2007 servers has been denied, error, kb
Ice Rocket : Access to address list service on all Exchange 2007 servers has been denied, error, kb