Search results for 'app:weblogs' matching tags 'Active Directory' and 'Windows Client'

Exchange Display Names as email addresses on Hybrid Environments

TBittner — Mon, 09 Jan 2012 06:00:00 GMT

If you don’t take care, that the on premise and the 365 cloud Exchange of your organization is not well connected via a dedicated TLS connection, you will get into thsi issue when user display names are shown as email addresses.

Read the following article, which discuss this issue and how to take care to avoid occuring this on such environments:

http://blogs.technet.com/b/hot/archive/2012/01/09/display-names-appear-as-email-addresses-in-cloud-when-sent-from-on-premise.aspx

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

Windows Anti-Virus Exclusion List

TBittner — Wed, 17 Aug 2011 05:00:00 GMT

A comprehensive all exclusion list for Windows Server Systems has been published on TechNet Wiki.

http://social.technet.microsoft.com/wiki/contents/articles/953.aspx

Best Practise Roaming Profiles and Folder Redirection

TBittner — Thu, 14 Jul 2011 05:00:00 GMT

Here is a very detailed article from Microsoft MVP Alan Burchill from Australia going through the configuration of Roaming Profiles and Folder Redirection. And showing the specific Group Policy Settings to achieve a user friendly feature deployment.

A must have to read

http://www.grouppolicy.biz/2010/08/best-practice-roaming-profiles-and-folder-redirection-a-k-a-user-virtualization/

Error 0x80070035 – The network path was not found

TBittner — Thu, 30 Jun 2011 05:00:00 GMT

In an environment with Site-to-Site VPNs and Windows 7 clients on the branch offices you can be faced with the Error 0x80070035 – The network path was not found, when users try to access file services provided with DFS shares.

The standard protocol used to access file services is SMBv1 and SMBv2, depending on legacy client and servers or current version OS client and server like Windows 7 and Windows Server 2008 R2.

There is a bug in the Mrsxsmb10.drv driver, causing some trouble.

Read the MSKB article

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

and apply the hotfix to fix the problem.

New IE9 Group Policies and how to apply

TBittner — Tue, 15 Mar 2011 05:00:00 GMT

All new group policies coming with IE9 are listed on this page on TechNet with a description how to apply with group policy management console.

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

Windows Server 2008 R2 refuse to resolve external FQDN

TBittner — Fri, 08 Oct 2010 05:00:00 GMT

No, it is not the dot in the hierachy on DNS Server which makes him a Root DNS.

So looking for this is obvious. And what if you find, that DNS Root Servers are listed and forwarders are able to ping, but recursive name resolution still doesn’t work.

When you look up the new features and changes coming with Windows Server 2008 R2, you will find something about EDns (EDNS). What is this?

It is an additional OPT record and mandatory for DNSSEC. So it is first enabled by default with Windows Server 2008 R2. It was already available since Windows Server 2003, but not enabled by default.

So you are wondering when you execute following from command prompt:

dnscmd /config /EnableEDNSProbes 0

your DNS Server is now able to provide name resolution for your external internet addresses.

Read Scott Forsyth’s Blog for more details

http://weblogs.asp.net/owscott/archive/2009/09/15/windows-server-2008-r2-dns-issues.aspx

More Performance with SMBv2x on Windows and NetApp

TBittner — Wed, 22 Sep 2010 05:00:00 GMT

NetApp has prepared an interesting performance test with new SMBv2.x available with Windows 7 and Windows Server 2008. The NetApp OnTap operating system has already been updated to support SMBv2.

Find here the result figures about performance increase with SMBv2.x

Win7 and Windows Server 2008 and R2 SMBv2 and v2.1 and Riverbed

TBittner — Mon, 06 Sep 2010 05:00:00 GMT

Who designs distributed network infrastructures with high bandwidth connected sites and accelerates traffic with Riverbed appliances will loose many nice communication features comming with WinVista or Win7 and Windows Server Systems 2008 and 2008R2.

One of the known features in communication between Windows Vista or Windows 7 and Windows Server 2008 or 2008R2 devices is SMBv2.0 or SMBv2.1.

The ‘old’ SMBv1 has been designed centuries ago when 10MBit Ethernet infrastructure was common. It delivers by design maximum of 10 MByte/s data throughput, so even when Ethernet infrastructures reached 100MBit bandwidth, you could easily use maximum SMBv1 delivers.

With Ethernet infrastructures based on high bandwidth, faster protocols are relevant.

So with SMBv2.0 or SMBv2.1 it can be possible to reach a few hundreds of MByte/s data throughput when both devices supporting this.

But if your devices are behind connections which supposed to be fast because you implemented Riverbed appliances, you will possibly fail.

Not only that Riverbed currently doesn’t support SMB Digital Signing, if it is not a member of the Windows domain the client and server belong to, but the Rivebed appliance only support SMBv1.0.

And not worse enough. If there is a pre-existing SMBv2 CIFS session that pre-dates activation of the Riverbed, then the Windows client will cache the fact that it is using SMBv2 session with that particular Windows 2008 server. There is nothing the Riverbed applicance can do to force that Windows client to use SMBv1 for that server, because the Windows client has already successfully set up an SMBv2 session, and it will always use SMBv2 for that server until it is rebooted. Because the appliance can’t address protocol chattiness issues for SMBv2, it will disable latency optimization and only apply SDR data reduction. To resolve this situation, you need to reboot the Windows client while the applicance is active, and the Riverbed device will force the client to use SMBv1 when the client re-establishes the CIFS session after reboot.

If optimization for SMB signing is configured, then the Riverbed will deliver optimized performance for the SMB signed SMBv1 traffic after forcing the negotiation down from SMBv2.