Posts tagged Exchange
How to create an Exchange Edge Connector
Nov 10th
- Create a server that you plan to install Edge services onto. For maximum security, it is recommend to not join this server to your domain. Instead the server will communicate with Active Directory Application Mode (ADAM) for its authentication processes creating a read only AD replication from your servers.
- Install the Exchange Edge Services service onto the server and apply all the applicable patches.
- Open the Exchange Management Shell on the Edge Transport server, and enter the following command:
New-EdgeSubscription –file "C:\edge-subscription.xml"
- Exchange will display a rather ominous warning message. This warning just tells you about all of the types of objects that will be overwritten or deleted during the subscription process. Press Y when the warning asks you if you want to continue, and the new file for subscription will be created.
- Exchange server will now have created a XML file named edge-subscription.xml, which it will place in the Edge Transport server’s C:\ location. At this time the command will also create an ADAM account.
- Copy the XML file to the Hub Transport server where you want the Edge Transport server to connect to. If you are connecting to both machines through remote desktop you can cut and paste the file between the two servers.
- Be sure to login with an account that is both a local administrator and a member of the Exchange Organization Administrator’s group. Open the Exchange Management Console on the Hub Transport server and navigate through the console tree to Organization Configuration > Hub Transport.
- Select the Edge Subscription tab and then click the New Edge Subscription link found in the Actions pane. The New Edge Subscription dialog box asks you which Active Directory site the Edge Transport server should become a part of. If your domain consists only of a single site, then it will be the only selectable option. If you have multiple sites, then you should make the Edge Transport server a member of the site that has the best connectivity to the perimeter network.
- After selecting the Active Directory site in which the Edge Transport server will be included, it’s time to import the XML file that was created earlier. Browse browse for and select the subscription.xml file that was copied earlier in step 6.
- Make sure to select the Automatically Create A Send Connector for this Edge Subscription checkbox adn then click the New button to import the XML file and create the Edge Subscription.
- This completes setting up the Edge connector for Exchange. You will see a new send connector which is what is used for the server to talk external network mail servers.
How to customize the OWA login screen
Oct 16th
For a Configuration in Which SSL Is Required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0- Start the Internet Information Services (IIS) Manager snap-in.
- Expand the local computer, expand Sites, and then click Default Web Site.
- At the bottom of the Default Web Site Home pane, click Features View if this option is not already selected.
- In the IIS section, double-click HTTP Redirect.
- Click to select the Redirect requests to this destination check box.
- Type the absolute path of the /owa virtual directory. For example, type https://mail.domain.local/owa.
- Under Redirect Behavior, click to select the Only redirect requests to content in this directory (not subdirectories) check box.
- In the Status code list, click Found (302).
- In the Actions pane, click Apply.
- For the new settings to take effect, start a command prompt, and then run the command:
IISReset
When you configure redirection from a top-level directory in Windows Server 2008, the settings are propagated to lower-level directories. For example, when you configure redirection to the /owa virtual directory as shown in the previous procedures, the settings that you configured on the Default Web Site also appear on the HTTP Redirect page of all the virtual directories, such as /Autodiscover, /Exchange, and /Public. Therefore, you must remove redirection from all the virtual directories except the one that you want redirected.
I took this from the Technet Reference site. Please have a look here for OWA redirection in more deails, or how to deal with it in Exchange 2003.
Exchange 2007 to 2010 Client Access Server Migration Problems
Sep 30th
Currently, in the process of preparing to migrate to Exchange 2010 there is a problem I have come across with the client access service. When trying to browse:
Microsoft Exchange > Microsoft Exchange On-Premises > Server Configuration > Client Access > Outlook Web App (Tab) or Exchange ActiveSync (Tab)
Doing a bit of digging I tried running the command manually from the Exchange 2010 Command Console. With the example command of: Get-OwaVirtualDirectory (Alternatively querying a specific server with Get-OwaVirtualDirectory -servername “<servername>” returned back the proper information from the Exchange 2010 server machine.)
I got the error:
An IIS directory entry couldn’t be created. The error message is Access is denied.
. HResult = -2147024891
+ CategoryInfo : NotInstalled: (<mailstorename>\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory], IISGeneralCOMException
+ FullyQualifiedErrorId : 4B6B88BA,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory
So searching around on Google I found an answer located here from TechNet.
First what I did was go ahead and install the RPC over HTTP proxy just incase. (ignore the WindowsPowerShell command warning.)
servermanagercmd.exe -I RPC-over-HTTP-proxy
How to install RPC over HTTP Proxy
Next I had to go to each of my Exchange 2007 server machines and add in the Exchange Trusted Subsystem to each of the Exchange 2007 server’s Local Users and Groups > Administrators group. As seen below:
Add Exchange Trusted Subsystem to each 2007 server
Finally, reboot all of the Exchange 2007 machines with the newly added local administrator Exchange Trusted Subsystem. From your Exchange 2010 re-run the Get-OwaVirtualDirectory and you will get information from all of your Exchange servers. The error in the EMC will also go away as well. As can be seen below.
Exchange Get-OwaVirtualDirectory Success
Outlook problem viewing MAPI List on Japanese Client
Sep 30th
Windows Vista/7 finally adds support for having multiple languages for the menu system which should have been included way back in the Windows XP era.
Anyways to the problem. This applies to computers with the Japanese language pack installed. However, it might apply to other systems using multi-byte fonts. When you try to view the (default) “All Address Lists” and such they will appear empty. The Windows XP/Office 2003 machines would show the MAPI listing with no problems. However, all the Vista/Win7 machines either with Office 2003 or 2007 would not show anything in the MAPI listing. After trying several things, I found the solution and it was so simple. If your location is set to Japan/Japanese you need to change the way that Windows is doing the lookup inside of the region properties from doing XJIS lookup to Radical/Stroke lookup. You’ll be able to see your global lists again.
The process goes as follows:
Regional and Language Options > Formats (tab) > “Customize this format…”
Region and Language Settings Screen
Customize Regional Options > Sorting (tab)
Change XJIS to Radical/Stroke
Customize Regional Options
Userenv and Outlook Connection Error
Nov 19th
There was a problem with a client PC today using Windows XP and Office 2007.
Outlook 2007 was reporting the Exchange server as Offline and would not reconnect to the Exchange server. Looking through the Eventlog, there was a Userenv error of 1517. This probably had a part in causing the system to not connect correctly to the Exchange server.
If you have a system that is experiencing a Userenv 1517 error:
Windows saved user <user name> registry while an application or service was still using the registry during log off. The memory used by the user’s registry has not been freed. The registry will be unloaded when it is no longer in use. This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.
The resolution I found for this was to:
- Open the “Active Directory Users and Computers”
- Locate the “Computer” object and reset it.
- Remove the PC from the domain.
- Add the PC back into the domain.
This seemed to fix the Userenv error.
Once this was fixed, there was still the Outlook Connection Error on the same account with different PCs. With the following error:
Cannot open your default email-folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folder with your offline folder files.
The steps I took to resolve this were:
- Deleting the account from the Control Panel > Mail area .
- Open the folder where the OST/PST files are stored and remove all files but the PSTs. (You can move the OST file to another location if you do not want to delete it quite yet).
- I am not sure if this helped but I also ran the command “outlook.exe /cleanprofile” (For 2007)
- Then I opened the dysfunctional account in the Webmail system.
- (The trickiest part?) Refresh the webmail and let it talk to the Exchange server for a bit. In my case it was about 5 minutes. Right after logging into webmail and then trying to run Outlook again still generated the same error.
- After waiting for a short while, restarting Outlook worked again and the user could access mail again.
Why I had to log into webmail and wait I really don’t know. But it seemed to fix whatever connection/sync problems the user was having.
Hope this helps anyone that might encounter the same problem.
Recent Comments