September 2009 - Posts
To enable auto-forwarding of email within ESM:
- Drill down in ESM into Global Settings or hub transport (exchange 2007)
- Right-click on Internet Message Formats in the left pane.
- Then double-click the Default format in the right pane.
- Select the Advanced tab, and then verify that "Allow Automatic Forwards" is enabled.
Message Format tab for remote domain properties
.gif)
here in this link how to create e-mail fowarding rules in outlook web access
http://onlinehelp.hostbasket.com/shared-mailhosting/office-mail-exchange-2007/outlook-web-access-2007/990-manual-to-create-e-mail-forwarding-rules-in-outlook-web-access-2007-owa.html
more about Managing Remote Domains setting in this link
http://technet.microsoft.com/en-us/library/aa996309.aspx
when you create a mailbox using the Exchange 2003 tools (ADUC), Your Exchange 2007 mailbox will indicate that it's a "Legacy" mailbox and will therefore be blocked from using some of the new E2k7 features
to reset the mailbox setting use this command:
Set-Mailbox -ApplyMandatoryProperties -Identity ShowInAddressBookUser -V
new-GlobalAddressList "Default Global Address List" -RecipientFilter {(Alias -ne $null -and (ObjectClass -eq 'user' -or ObjectClass -eq 'contact' -or ObjectClass -eq 'msExchSystemMailbox' -or ObjectClass -eq 'msExchDynamicDistributionList' -or ObjectClass -eq 'group' -or ObjectClass -eq 'publicFolder'))}
or create a GAL for the DAN company, run the following command.
New-GlobalAddressList -Name "DAN GAL" -IncludedRecipients MailboxUsers -ConditionalCompany dan
Remove-GlobalAddressList -Identity "DAN" -DomainController ex7k.dan.com
or delete the gal using "adsiedit"
for hidden a mailbox use this command:
Set-Mailbox "Mailbox Name" -HiddenFromAddressListsEnabled $true
When NSLOOKUP starts, before anything else, it checks the computer's network configuration to determine the IP address of the DNS server that the computer uses.
Then it does a reverse DNS lookup on that IP address to determine the name of the DNS server
create a reverse zone in Simple DNS Plus, click the "Records" button, select "New" -> "Zone", select "Reverse Zone
to create a resource config use this syntex
Set-ResourceConfig -DomainController server1.dan.com -ResourcePropertySchema ("Room/room222","Equipment/Projector","Room/8Seats","Equipment/Whiteboard")
NOTE:
|
| All entries must start with either Room/ or Equipment/. Setting a new entry using the Set-ResourceConfig cmdlet will overwrite all existing entries, and not add a new entry to the list. Use the Get-ResourceConfig cmdlet to query the existing entries, and then append to the list. |
Service 'MSExchangeTransport' failed to reach status 'Running' on this server
Disable IPv6
- Open Registry with "Regedit"
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
- Create a dword (32-bit) value and name it as "Disabled Components" and then click OK
- Double click "Disabled Components" and type 0xffffffff(hexadecimal value) or 4294967295 (Decimal value)
Please note: The above value 0xffffffff(hexadecimal value) or 4294967295 (Decimal value) will disable all IPv6 components, except the IPv6 loopback interface.
To use the Exchange Management Shell to update an offline address book
Update-OfflineAddressBook -Identity "My OAB"
To use the Exchange Management Shell to view and modify offline address book settings
In this cluster type nodes do not share the same physical storage; instead, the passive node continuously replicates database updates, but not the OAB files. Therefore, as the OAB Generation process needs access to the results of previous generation, only one CCR cluster node is able to generate the OAB data files, making such cluster basically asymmetric with regard to OABGen.
To control this behavior the Exchange setup process creates the registry value 'SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\OABGen-Server\EnableOabGenOnThisNode' which contains name of the node installed first, and from now on assumed as ‘primary’ cluster node. Whenever cluster has failed over to the ‘secondary’ node, the scheduled or forced OAB Generation task will log the event id 9395 and finishes.
Event Type: Error
Event Source: MSExchangeSA
Event Category: OAL Generator
Event ID: 9395
Date: 2007-01-26
Time: 1:55:10
User: N/A
Computer: OABGen-Server
Description:
OALGen is running on CCR cluster node which does not have registry value 'SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\OABGen-Server\EnableOabGenOnThisNode' or it is not set to this node name. OAB generation will not be performed.
How To Fix
This is an expected error if the ‘primary’ CCR node is temporarily unavailable, so just make sure it is back online . Otherwise, the following registry key needs to be in place and contain valid cluster node name: HKLM\System\CurrentControlSet\Services\MSExchangeSA\Parameters\Server-Name\EnableOabGenOnThisNode ="ThisNodeName".
NOTE: Make sure that you updated the registry value on the CCR node to be the name of the CCR node.