Map Drive on Windows Server 2003 R2 at System Boot

[CPressland]

Could have been something I miss configured. But setup was as follows:

Create VM,

Install Server 2012,

Add AD DC as a role,

Join existing forest,

Joined 2008 forest 44kenlane.com,

Played around with things, edited users, etc,

No further symptoms for like two weeks.

Upon rebooting Server 2008r2 the symptoms began.

Eventually removed 2012 from domain. Issue solved.

[+BudMan MVC]

I can not find anything that says 2012 "requires" ipv6 -- now some components do, like remote direct access.

I see this

http://technet.microsoft.com/en-us/library/hh831743

At least one Active Directory domain must be deployed with at least one Windows Server 2003, Windows Server 2008 R2, Windows Server 2008 or Windows Server 2012-based domain controller (an Internet Protocol version 6 [iPv6]-capable domain controller and global catalog)

But sure looks like you need IPv4 as well -- WTF, you going to say a component requires IPv6, then then also require IPv4 is just broke if you ask me!

http://technet.microsoft.com/en-us/library/hh831633

Configure your internal network interface with a static Internet Protocol version 4 (IPv4) address configuration.

Having things that only use IPv6 while it is not not the dominate protocol is causing more issues than its possibly helping. Your application should be able to use either or! Same **** with their homegroups, for it to work you have to use have ipv6, but it doesn't actually use IPv6 for what your doing with it.

If you going to use IPv6 in your AD, then clearly their are things that have to be configured! So that could be your problem. But if your not using direct remote access, I can find nothing that "states" you have have Ipv6 enabled on 2012.

To be honest I have having a hard time finding any good information on bringing up 2012 in a 2008r2 setup.

I find stuff that says not to disable IPv6 -- but that type of advice is BS. You sure an the hell do not need teredo running, and depending on your setup your not going to need isatap or tunnels either. So if you want people to use Ipv6 - then give the correct steps to disable the features of it that are not needed.

Or better yet have them disabled by default, and give instructions on how to bring up the protocols/features they need.

Having everything enabled out of the back is just BAD BAD BAD practice! Did they not learn their lesson when they had services enabled out of the box before like IIS and FTP, and messenger, etc.