sexta-feira, junho 15, 2012

Your Out of Office cannot be displayed, because the server is currently unavailable. Try again later.

When you have a CAS load balance and use a virtual name to access its virtual directories, e.g. rather than the server name, you have to configure the internalURL and externalURL of all virtual directories. The problem occours if you change them through EMC, doing so you'll miss some virtual directories that can be managed only through EMS. EWS (Exchange Web Services) is one of these virtual directories and it's responsible for OOF.

To configure the proper URL for EWS run the following commands on EWS:

Set-webservicesvirtualdirectory –Identity –internalurl “https:///ews/exchange.asmx” –externalurl “https:///ews/exchange.asmx”

In order to configure all virtual directories' URL there is a script to help changing all virtual directories.

#Changing InternalURL Path
$urlpath = Read-Host "Type Internal Client Access FQDN starting with http:// or https://"
Set-AutodiscoverVirtualDirectory -Identity * –internalurl “$urlpath/autodiscover/autodiscover.xml”
Set-ClientAccessServer –Identity * –AutodiscoverServiceInternalUri “$urlpath/autodiscover/autodiscover.xml”
Set-webservicesvirtualdirectory -Identity * –internalurl “$urlpath/ews/exchange.asmx”
Set-oabvirtualdirectory –Identity * –internalurl “$urlpath/oab”
Set-owavirtualdirectory –Identity * –internalurl “$urlpath/owa”
Set-ecpvirtualdirectory –Identity * –internalurl “$urlpath/ecp”
Set-ActiveSyncVirtualDirectory -Identity * -InternalUrl "$urlpath/Microsoft-Server-ActiveSync"
#Changing ExternalURL Path
$urlpath2 = Read-Host "Type External Client Access FQDN starting with http:// or https://"
Set-AutodiscoverVirtualDirectory -Identity * –externalurl “$urlpath2/autodiscover/autodiscover.xml”
Set-ClientAccessServer –Identity * –AutodiscoverServiceInternalUri “$urlpath2/autodiscover/autodiscover.xml”
Set-webservicesvirtualdirectory –Identity * –externalurl “$urlpath2/ews/exchange.asmx”
Set-oabvirtualdirectory –Identity * –externalurl “$urlpath2/oab”
Set-owavirtualdirectory –Identity * –externalurl “$urlpath2/owa”
Set-ecpvirtualdirectory –Identity * –externalurl “$urlpath2/ecp”
Set-ActiveSyncVirtualDirectory -Identity * -ExternalUrl "$urlpath2/Microsoft-Server-ActiveSync"
#get commands to doublecheck the config
get-AutodiscoverVirtualDirectory | fl identity,internalurl, externalurl
get-ClientAccessServer | fl identity,AutodiscoverServiceInternalUri
get-webservicesvirtualdirectory | fl identity,internalurl,externalurl
get-oabvirtualdirectory | fl identity,internalurl,externalurl
get-owavirtualdirectory | fl identity,internalurl,externalurl
get-ecpvirtualdirectory | fl identity,internalurl,externalurl
get-ActiveSyncVirtualDirectory | fl identity,internalurl,externalurl

Outlook uses the Internet Explorer proxy configuration to access any Exchange web service, such as OAB, Autodiscover and EWS, so make sure the internal Client Access FQDN is in the proxy exception list.

quarta-feira, outubro 26, 2011

How to configure an authoritative time server in Windows Server

To get the time in Windows domain environment synchronized on PDC server run the command below:

w32tm /config /manualpeerlist: peers /syncfromflags:manual /reliable:yes /update

where peers is the time server that your PDC will sync. If you want to use more than one time server put them between "" and the servers name should be space-delimited.

Example used in Brazil:
w32tm /config /manualpeerlist: "" /syncfromflags:manual /reliable:yes /update

After restart the Windows Time service on PDC server, then run W32tn /resync.


SMS Distribution Manager failed to initialize the network abstraction layer (NAL)

I had this problem on SCCM 2007 SP2 R3 installed on Windows Server 2008 R2 SP1.

To fix this annoying issue is necessary to rebuid the NAL: 

Rebuild NAL:

1. Stop sms_site_component_manager and sms_executive service.

2. New a registry key: HKLM\software\wow6432node\microsoft\Nal\server\providers

3. Add a Reg_Multi_SZ value under it. The name should be “Active Order

4. Double click it, input the value

5. Open comman
d line window. Go to the SCCM installation path. By default it will under “\program files (x86)\microsoft configuration manager\bin\i386” folder.

6. Run following command line:

regsvr32 abnwsvr.dll
regsvr32 falsvrn.dll
regsvr32 mslmsvrn.dll

7. After all the .dll is registry successfully, there will be 2 new value generated under the Active Order.

8. Then we will do a site reset. Close the SCCM console if it is opened. Go to “Start\All programs\microsoft system center\configuration manager 2007\configmgr setup

9. When the setup is launched, please choose “Perform site maintenance or reset this site”.

NOTE: It is not default choice, please make sure the choose of “” here to avoid remove the site by mistake!

10. Choose the “Re-apply default file and registry permissions on this site server

11. Click Next till finish. Then reset the site is doing.

12. After finish, there will be a new key generated. It called “Connections”, there is a value under it, it is “Operational Active Order”.


13. After that, the NAL seems rebuild. Restart the server, then your Distribution Point will be working fine.


segunda-feira, outubro 17, 2011

Not able to access the Hyper-V host machine share from guest VM

To get rid off this problem disable NetDMA following these steps

  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate the following registry subkey, and then click it:
  3. Double-click the EnableTCPA registry entry.
    Note If this registry entry does not exist, right-click Parameters, point to New, click DWORD Value, typeEnableTCPA, and then press ENTER.
  4. To disable NetDMA, type 0 in the Value data box, and then click OK.


quarta-feira, maio 18, 2011

Problems with ECP after applying Exchange 2010 SP1

If you are facing with the following problem when accessing the ECP:

Request for URL 'https://localhost/ecp/default.aspx?rfr=owa' failed with the following error:
System.TypeInitializationException: The type initializer for 'Microsoft.Exchange.Configuration.TenantMonitoring.TenantMonitor' threw an exception. ---> System.FormatException: Input string was not in a correct format.

On Event Viewer you can find this error:
MSExchange Control Panel - EventID 4

You can fix this problem going to C:\Windows\System32 and running lodctr /r, after the command finishes run iisreset /noforce.

Ussually this issue occours after update the Exchange 2010 to SP1.

quarta-feira, fevereiro 02, 2011

Microsoft Exchange: Stores fail to start with 0x8004010f error

I was recently involved in a migration from a legacy Exchange 2000 Organization to a new Exchange 2007 deployment. All was going well until the Information Store service on the Exchange 2000 Server was restarted, but failed to start due to the following error:

Unable to initialize the Microsoft Exchange Information Store service. Error 0x8004010fEvent ID: 5000 Source: MSExchangeIS
On attemping to start the Information Store manually, I was greeted with a not-particularly-verbose error stating the process failed with service-specific error code ’0′.
The issue was caused in this case by the X400 address, required by Exchange 2000/2003 for internal communications, being removed from the Default Recipient policy. Although legacy Exchange organizations require this address, Exchange 2007 deployments without any legacy Exchange Servers will function without the address , and it is possible some aspect of the new server configuration removed the entry.
To restore the address, open Exchange System Manager on a legacy Exchange Server and edit the Default Recipient Policy. If no X400 address is present, add a new X400 address into the Recipient Policy using the appropriate information. Since removing an entry from a Recipient Policy does not remove the entry from existing mailboxes, I retrieved the required settings from an existing mailbox using the management tools on the new Exchange 2007 Server.
Once the address is added, or if it was present already but unchecked, you need to enable the entry. Attempting to check or uncheck the entry in ESM will more than likely result in an error:
X400 address cannot be disabled using Exchange System Manager
X400 address cannot be disabled using Exchange System Manager
This error is to be expected, since Exchange 2000/2003 requires the X400 address and will therefore prevent any attempt to remove it as a safety precaution. To enable the address, you need to perform a low-level edit using ADSIEdit on a Domain Controller.
Usual warnings apply – ADSIEdit can make permanent and potentially destructive changes to Active Directory. Use the tool at your own risk and with proper backups in place.
In ADSIEdit at a Domain Controller, expand the Configuration Naming Context and drill down through CN=Services > CN=Microsoft Exchange > CN= > CN=Recipient Policies. Right click the Default Policy and choose Properties. You will notice the X400 address is listed within the ‘disabledGatewayProxy’ attribute. To enable:
  1. Edit the disabledGatewayProxy attribute and remove the X400 address.
  2. After pressing the ‘Remove’ button, the X400 configuration contents generated by Exchange are placed into the textarea. Copy this data.
  3. Close the attribute so it is now stored blank. Edit the ‘gatewayProxy’ attribute, which is the location for enabled entries in the policy, and add the X400 contents from your clipboard.
  4. Store your changes, then wait for or manually force Active Directory replication prior to restarting the Exchange Services.
Viola! Your IS service should now start and you can mount the stores. If the X400 issue was not the culprit, it is more than likely permissions within Active Directory. Verify the Exchange 2000/2003 computer is a member of the legacy Exchange Domain Servers group, and that group is in turn a Member Of the Exchange Enterprise Servers security group. You should then use ADSIEdit to check and reset certain permissions; the changes required are detailed over at Technet.

terça-feira, janeiro 04, 2011

Exchange error MSExchangeIS Mailbox Store - EventID 10001

After moving a mailbox to another database you may start getting the following event log, even if the moving was sucessful:

Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          04/01/2011 21:10:35
Event ID:      10001
Task Category: Background Cleanup
Level:         Warning
Keywords:      Classic
User:          N/A
Mailbox cleanup could not completely remove the mailbox for user ff783a8e-2dc9-4af7-bab5-435d4b841b2f (Root Fid 2-225C78C) following mailbox removal. Encountered error 0xfffffae8. Should this message continue to persist for the same mailbox, it may be indicative of a problem that requires further investigation. 

To stop recieving this log just dismount and mount the previous and the current database for the specified mailbox.