Proxies of chosen policy:. SMTP: Site1. Proxies in change list:. Proxies to generate:. Conflicts during generation:. Proxies generated:. Proxies written to recipient:. This event will give you more insight as to the decisions made in the proxy generation step, as well as a nice summary of the applicable policies. This can save you the work of reading through the events.
At the end of the evaluation process, if no changes are needed you'll see an Event Category: Address List Synchronization. In some cases you'll see the even when it seems clear that changes should have been made.
For instance, you may be looking at a recipient with no proxy addresses at all. You see events indicating that recipient policies match the user, yet the evaluation process logs this event indicating no changes are needed. This behavior is typical of a situation where a proxy generator has failed to load. See KB: for more details on this problem. If changes were made, you should see 3 events:. Completed the transaction Finally, at the end of the evaluation of this recipient, you'll get two more events:.
Thread 12b8: waiting for next Address List transaction. By carefully analyzing the events logged while processing a recipient, many common RUS issues can be identified. This results in the application log quickly overwriting itself and makes it difficult to follow the sequence of events described above.
When troubleshooting the RUS, it is best to avoid Rebuilding or Applying and instead focus on a single test user and use only Update Now to check for new and modified objects. When issues do occur there are three basic steps to troubleshooting RUS. To begin troubleshooting RUS we first determine if we have more than one recipient policy, if so, set the schedule for all but one to Never Run. In the case of multiple policies, you may be required to go back and enable another policy if you find nothing wrong with the first.
Just ensure that only one policy is scheduled to run at a time. With the schedule configured, the next step is to enable Diagnostic Logging and set it to log the maximum amount of events on the following services and objects. Note: Proxy Generation is not available on Exchange servers. Finally create a test object for the RUS to stamp. Figure 1: Diagnostic Logging. With Diagnostic Logging enabled, wait a few minutes and you should see two events show up in the Application event log with IDs and These events verify that RUS has started.
If you do not get these messages, restart the Microsoft Exchange System Attendant service. If event ID appears, but you never get event ID , you are performing this task on a front-end server. Locate the uSNChanged value and record it. Next open up the Event Viewer on the Exchange server you have enabled logging on and search for. When the search is done, open the first event in the list that will include information about the last search completed by the RUS. A value for this parameter requires the Get-Credential cmdlet.
To pause this command and receive a prompt for credentials, use the value Get-Credential. For more information, see Get-Credential. The DomainController parameter specifies the domain controller that's used by this cmdlet to read data from or write data to Active Directory.
You identify the domain controller by its fully qualified domain name FQDN. For example, dc The Identity parameter specifies the recipient that you want to update. You can use any value that uniquely identifies the recipient. For example:.
The WhatIf switch simulates the actions of the command. You can use this switch to view the changes that would occur without actually applying those changes. You don't need to specify a value with this switch. To see the input types that this cmdlet accepts, see Cmdlet Input and Output Types. If the Input Type field for a cmdlet is blank, the cmdlet doesn't accept input data.
To see the return types, which are also known as output types, that this cmdlet accepts, see Cmdlet Input and Output Types.
0コメント