2008 Windows Domain backward compatibility

Forums › Microsoft Windows › 2008 Windows Domain backward compatibility

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#70251 20-Oct-2010 19:59

I have installed 2008 to overcome the horror of Vista / Win 7 roaming profile changes (XP redirect disasters and Server 2003 file access issues), however the test environment first try with a 2003 server caused a logon of nearly 5 minutes, is this a known problem, or should I have selected a 2003 compatible domain?

gehenna

8667 posts

Uber Geek
+1 received by user: 3883

Moderator

Trusted

Lifetime subscriber

#394114 20-Oct-2010 20:00

Nope not a known problem, must be something you've configured incorrectly. 2008 server should be just as snappy for login as 2003 across all desktop OS versions.

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#394126 20-Oct-2010 20:20

thanks, that's reassuring, I wasn't keen on rolling everything back, I'll reinstall that server and try again. In the mean time I'll put a XP test box on and see how it goes.

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#394147 20-Oct-2010 20:56

XP tested out fine, phew. Noew, back to the reinstall of the 2003 server....

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#394965 23-Oct-2010 09:31

there still appears to be some major problems with my 2008 domain, does anyone know a article for 2008 first timers. I started on 2000 and have been using 2003 for a long time, and have setup the 2008 domain as I would have a 2003 domain (on the assumption that 2008 was an extension) however I've got serious problems with

1. authentication via RDP, works fine for the DCs but fails to authenticate for the same Domain Admin user on other 2008 servers, I've even manually added "Domain Admins" group to Remove Desktop access list (I had to do this to let the Domain Admin user open the Remote Access dialog on the host machines.

2. Unable to add Hyper-V to the domain (even though Virtual o/s within the Hyper-V added successfully, Domain Admin credentials are captured but after some time it returns "Error occurred attempting to join the domain":"network path was not found"

Shoes2468

794 posts

Ultimate Geek
+1 received by user: 79

#394978 23-Oct-2010 10:35

lyonrouge: I have installed 2008 to overcome the horror of Vista / Win 7 roaming profile changes (XP redirect disasters and Server 2003 file access issues), however the test environment first try with a 2003 server caused a logon of nearly 5 minutes, is this a known problem, or should I have selected a 2003 compatible domain?

1. What do you mean by selected a 2003 compatible domain? do you mean domain functional level?

2. What configuration are you trying to set up, are you adding a domain controller to the existing domain? are you adding a new domain to the forest? or creating a new domain in a new forest?

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#395032 23-Oct-2010 15:28

1. existing domain is on 2003 servers (at the 2003 functional level)

2. creating a completely new forest (2003 compatible) and domain (2008 only) on new network segment (separated from existing domain network by ISA 2006).

New World

Shop on-line at New World now for your groceries (affiliate link).

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#395033 23-Oct-2010 15:35

The following

2. Unable to add Hyper-V to the domain (even though Virtual o/s within the Hyper-V added successfully, Domain Admin credentials are captured but after some time it returns "Error occurred attempting to join the domain":"network path was not found"

Appears to have been an issue with reverse look-up which is now addressed.

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#395272 24-Oct-2010 17:15

the two Servers I'm having trouble with are Server 2008 R2 virtual harddrive clones. As I needed to stand up 4 servers, I installed once and ran the huge Windows Updates then shut it down, made a copy, changed the machine name and then activated it, and on and so forth. I'm wondering if these clones have an issue with being renamed causing the Remote Desktop to Fail?

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#395991 26-Oct-2010 20:36

the cloning does seem to be the issue. Although the instances appear to work fine in all other ways, remote desktop authentication fails. I've reinstalled one and it is now fine, I'll reinstall the others just in case I encounter other issues down the line.

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#397661 30-Oct-2010 09:39

All remaining servers have been reinstalled and activated and all is well.

lyonrouge

1993 posts

Uber Geek
+1 received by user: 20

Trusted

Lifetime subscriber

#401531 8-Nov-2010 08:10

With a plan to archive the existing domain behind another ISA server, I found during testing of cloning virtual Windows Server 2003 the problem lies with non-unique SID (the symptoms of this are much more evident in 2003, including exception messages that provided the lead I needed to find the related material). The solution to my 2008 cloning is found in the included system preparation tool.

c:\Windows\System32\sysprep\sysprep.exe