Clients DNS and Winodws 2008 R2

After adding a WIndows 2008 R2 domain controller to our windows 2003 domain
can I continue to point clients to a Windows 2003 domain controller and
bypass them authenticating to the Windows 2008 R2 DC? I am just trying to
think if a backup plan if there are any compatibility issues, etc. with the
new 2008 R2 domain controller.

Thanks.

Howdie!

2010 schrieb:
> After adding a WIndows 2008 R2 domain controller to our windows 2003 domain
> can I continue to point clients to a Windows 2003 domain controller and
> bypass them authenticating to the Windows 2008 R2 DC? I am just trying to
> think if a backup plan if there are any compatibility issues, etc. with the
> new 2008 R2 domain controller.

The authentication process hasn't changed between the versions. You can
still use the 2003-DC's IP address with all client machines as the
preferred DNS server but I don't see a reason to not roll out the
2008R2-DC's IP address as the secondary DNS server.

If it feels okay for you, you may want to partially-deploy the new DC as
a DNS server by splitting the DHCP scopes to have certain clients use
the Server2008DC for authentication and others not.

Cheers,
Florian
--
Microsoft MVP - Group Policy
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.
Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste

Hello 2010,

You didn't point to a DC from the client, it is the DNS server to contact
to find a DC for authentication. If your DCs are also DNS server this is
correct. In this case i suggest to use AD integrated zones in DNS.

But it is always good to have more then on DNS server, at least 2, in the
domain for failover and redundancy, and have the clients configured to use
them on the NIC.

In a single forest domain, like domain.com, you should also make all DCs
Global catalog server.

Because with 2008 coming also new security groups for example in AD, move
all FSMO roles to the newest OS DC in the domain.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> After adding a WIndows 2008 R2 domain controller to our windows 2003
> domain can I continue to point clients to a Windows 2003 domain
> controller and bypass them authenticating to the Windows 2008 R2 DC?
> I am just trying to think if a backup plan if there are any
> compatibility issues, etc. with the new 2008 R2 domain controller.
>
> Thanks.
>

nope

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Identity & Access - Directory Services #

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test ANY suggestion in a test environment before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------

"2010" <2010@discussions.microsoft.com> wrote in message
news:F40642B3-48BB-4CD8-837B-35ED811C85A9@microsoft.com...
>
> After adding a WIndows 2008 R2 domain controller to our windows 2003
> domain
> can I continue to point clients to a Windows 2003 domain controller and
> bypass them authenticating to the Windows 2008 R2 DC? I am just trying to
> think if a backup plan if there are any compatibility issues, etc. with
> the
> new 2008 R2 domain controller.
>
> Thanks.
>
> __________ Information from ESET Smart Security, version of virus
> signature database 4507 (20091014) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
>
>
>

__________ Information from ESET Smart Security, version of virus signature database 4507 (20091014) __________

The message was checked by ESET Smart Security.

http://www.eset.com