Search results for 'app:weblogs' matching tags 'exchange', 'Outlook', and 'Microsoft Provisioning Services'

DNS Server service refuse name resolution on Windows Server 2008 R2

TBittner — Fri, 06 Jan 2012 06:00:00 GMT

It has been already from nearly two years ago, that under certain circumstances DNS Server service on Windows Server 2008 R2 refuse to resolve internet domain name addresses.

This issue occurs if Windows Server 2008 R2 DNS Server is used without forwarders configured, just relying on root hints entries querying for internet domain name resolution.

The issue was, that after a while the DNS Server service can’t handle the catched entries on the DNS cache and refuse name resolution.

Now Microsoft published a hotfix to fix this issue, which was still persistent on Windows Server 2008 R2 with Service Pack 1.

Get the hotfix here:

http://support.microsoft.com/kb/2508835

Exchange 2010 Service Pack 2 available

TBittner — Mon, 05 Dec 2011 06:00:00 GMT

You can download it from here

http://www.microsoft.com/download/en/details.aspx?id=28190

Exchange 2010 SP2 is a complete installation software pack, so for new Exchange installations, you can use it to start with from scratch.

Also when you use it for updating your current installations, be aware that you need Schema- and/or Organisaiton Administrator rights, because it contains a Schema update for your Active Directory.

And this Schema update needs to be execute in the domain where the Schema Master Role exist. So run setup /prepareAD not in the domain where you operate your Exchange Servers, it will not work. You need to go to the root domain, if there is the Schema Master or you have to move the Schema Master on to a domain controller in the domain where you operate your Exchange environment.

And remember that you should wait for replication across your AD after you’ve performed the Exchange 2010 SP2 Schema update.

During you’re waiting for replication, you can use the time to install the ‘IIS 6 WMI Compatibility’ feature. It is mandatory for your following Exchange 2010 SP2 installation, because of the new ‘Outlook Mini’ feature, which requires this feature on your CAS server roles.

Schedule

5 minutes for /prepareAD
15 minutes for replication (more if you have higher replication times set on your site links)
5 minutes for feature prerequisits
30 minutes for finishing SP2 setup per system

so you should be through with it within a hour for your first system and schedule 30 minutes for every following systems …

Reboot after SP2 installation should not be necessary.

And think about to disable Anti Virus Scanning on the box you’re going to perform Exchange 2010 SP2 Setup for upgrade.

Read the prerequisits before starting your installation

http://technet.microsoft.com/en-us/library/bb691354.aspx

Exchange for Hosters

TBittner — Tue, 30 Aug 2011 05:00:00 GMT

As you know, this feature was removed from the current version of Exchange. There are some features back with Exchange 2010 SP1 back not as we had it in the past with legacy versions.

Now with Exchange 2010 SP2 we will get back functionality on a standard On-Premise Exchange environment.

Read

http://blogs.technet.com/b/hameroff/archive/2011/08/08/so-you-want-to-host-exchange.aspx

and

http://blogs.technet.com/b/exchange/archive/2011/08/30/exchange-server-2010-sp2-and-support-for-hosting-exchange.aspx

Secure Access to your Cloud Services

TBittner — Tue, 22 Feb 2011 06:00:00 GMT

Moving to the Cloud is going on and so we will have more and more On-Premise and Cloud environments living site by site.

Securing access to Cloud Services will be more relevant for the future.

A great article on this topic has been published by Yuri Diogenes, Senior Security Support Escalation Engineer on Microsoft Forefront Team.

http://technet.microsoft.com/en-us/magazine/gg607680.aspx