Windows Server 2012 R2 - New Forest - Lowest forest fuctional level 2008

Hi,
I just setup a new win2k12 r2 forest. I notice the lowest forest functional level that I can select is only Windows Server 2008. How come 2003 is not on there when it is supported in the document below?
The following table shows the features that are available at each forest functional level.
http://technet.microsoft.com/en-us/library/understanding-active-directory-functional-levels%28v=ws.10%29.aspx
Thanks

Windows Server 2003 is in extended support and even the extended support will end next year - So setting up Windows Server 2003 DCs in a brand new forest of this date doesn't make sense (or at least it's not what Microsoft want you to do)
Enfo Zipper
Christoffer Andersson – Principal Advisor
http://blogs.chrisse.se - Directory Services Blog

Similar Messages

  • Adding second domain controller in Windows server 2012 R2

    Hello, our primary domain controller is currently on a machine that has Windows Server 2008 R2 Standard. We are planning to setup a second domain controller as a failover to our primary domain controller. My question is, can we have a secondary domain
    controller on a Windows Server 2012 R2 even if our primary domain controller is on a machine that has Windows Server 2008 R2?

    I think I found the answer to my question.
    http://technet.microsoft.com/en-us/library/dd464018(v=ws.10).aspx
    "In Windows Server 2012, Adprep.exe is integrated into the AD DS installation process and runs automatically as needed. For example, when you install the first domain controller that runs Windows Server 2012 into an existing domain and forest, then adprep
    /forestprep and adprep /domainprep automatically run and report the results of the operations.
    Some organizations may prefer to run Adprep.exe separately in advance of an AD DS installation. For this reason, Adprep.exe is also included in the \Support\Adprep folder of the operating system disk.
    In Windows Server 2012, there is only one 64-bit version of Adprep.exe. It can be run remotely from any server that runs a 64-bit version of Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012. The computer where you run it can be either
    domain-joined or in a workgroup.
    The version of Adprep.exe in Windows Server 2012 includes new syntax and parameter options in order to run it remotely. For more information, see
    Adprep."
    For more information about the objects and containers that are created when the schema is extended to support Windows Server 2012, see
    Windows Server 2012: Changes to Adprep.exe.

  • SQL Server 2008 R2 & 2008 R2 SP1 installation fails in Windows server 2012

    Hi All,
    I have a strange issue here. I have a Windows server 2012 VM where i want to deploy SQL 2008 R2 Enterprise edition.
    When i Run the setup every thing goes fine and during the installation wizard i get this error " The Folder path Program files contains  invalid characteristics. I get this error 3 - 4 times during the installation wizard and the installation fails.
    Below is the screenshot for the same.
    So i checked few articles regarding the compatibility issue and found the below article and upgraded my setup to SQL 2008 R2 SP1 using the below article.
    http://blogs.msdn.com/b/petersad/archive/2011/07/13/how-to-slipstream-sql-server-2008-r2-and-a-sql-server-2008-r2-service-pack-1-sp1.aspx
    Again i still see the same above errors and with that a new error related to a MOF File.
    Below are the contents of the error logs. Can some one assist on this issue.
    ======================================================
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068052692
      Exit facility code:            1212
      Exit error code:               1324
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2015-01-15 13:53:03
      End time:                      2015-01-15 14:04:29
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\Detail.txt
      Exception help link:           http%3a%2f%2fgo.microsoft.com%2ffwlink%3fLinkId%3d20476%26ProdName%3dMicrosoft%2bSQL%2bServer%26EvtSrc%3dsetup.rll%26EvtID%3d50000%26ProdVer%3d10.50.2500.0%26EvtType%3d0xA60E3551%400xD3BEBD98%401211%401
    Machine Properties:
      Machine name:                  ALPCLDSCOM01
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      Installation location:         D:\SQLServer2008R2_SP1\x64\setup\
      Installation edition:          ENTERPRISE
      Slipstream:                    True
      SP Level                       1
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 E2KLAB\SCOMAC
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Automatic
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     D:\SQLServer2008R2_SP1\SP
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  E2KLAB\SCOMAC
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 E2KLAB\SCOMAC
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           E2KLAB\Gautamr,E2KLAB\SCOMAC,E2KLAB\SCOM Admins
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\sql_common_core_loc_Cpu64_1033_1.log
      MSI error description:         The folder path 'Program Files' contains an invalid character.
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_135043\SystemConfigurationCheck_Report.htm
    Gautam.75801

    Hi Alberto,
    Still the same issue.
    I installed the SQL 2008 R2 without SP1 and changed the service accounts to system account and  repaired the .NET using the .NET Repair tool
    Also changed the installation directory to D:\ Drive this time. Still same issue.
    log file:
    ===============
    Overall summary:
      Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Exit code (Decimal):           -2068052692
      Exit facility code:            1212
      Exit error code:               1324
      Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
      Start time:                    2015-01-15 22:55:37
      End time:                      2015-01-15 23:07:32
      Requested action:              Install
      Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SQLSysClrTypes_Cpu64_1.log
      Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.2500.0
    Machine Properties:
      Machine name:                  ALPCLDSCOM01
      Machine processor count:       4
      OS version:                    Future Windows Version
      OS service pack:               
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                    Feature                
                     Language             Edition              Version         Clustered 
    Package properties:
      Description:                   SQL Server Database Services 2008 R2
      ProductName:                   SQL Server 2008 R2
      Type:                          RTM
      Version:                       10
      SPLevel:                       1
      Installation location:         D:\SQL Server 2008 R2 Datacenter edition for only Windows server 2008 R2\x64\setup\
      Installation edition:          ENTERPRISE
    User Input Settings:
      ACTION:                        Install
      ADDCURRENTUSERASSQLADMIN:      False
      AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      AGTSVCPASSWORD:                *****
      AGTSVCSTARTUPTYPE:             Automatic
      ASBACKUPDIR:                   Backup
      ASCOLLATION:                   Latin1_General_CI_AS
      ASCONFIGDIR:                   Config
      ASDATADIR:                     Data
      ASDOMAINGROUP:                 <empty>
      ASLOGDIR:                      Log
      ASPROVIDERMSOLAP:              1
      ASSVCACCOUNT:                  <empty>
      ASSVCPASSWORD:                 *****
      ASSVCSTARTUPTYPE:              Automatic
      ASSYSADMINACCOUNTS:            <empty>
      ASTEMPDIR:                     Temp
      BROWSERSVCSTARTUPTYPE:         Disabled
      CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
      CUSOURCE:                      
      ENABLERANU:                    False
      ENU:                           True
      ERRORREPORTING:                False
      FARMACCOUNT:                   <empty>
      FARMADMINPORT:                 0
      FARMPASSWORD:                  *****
      FEATURES:                      SQLENGINE,FULLTEXT,RS,SSMS,ADV_SSMS
      FILESTREAMLEVEL:               0
      FILESTREAMSHARENAME:           <empty>
      FTSVCACCOUNT:                  NT AUTHORITY\LOCAL SERVICE
      FTSVCPASSWORD:                 *****
      HELP:                          False
      INDICATEPROGRESS:              False
      INSTALLSHAREDDIR:              D:\Program Files\Microsoft SQL Server\
      INSTALLSHAREDWOWDIR:           D:\Program Files (x86)\Microsoft SQL Server\
      INSTALLSQLDATADIR:             <empty>
      INSTANCEDIR:                   D:\Program Files\Microsoft SQL Server\
      INSTANCEID:                    MSSQLSERVER
      INSTANCENAME:                  MSSQLSERVER
      ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
      ISSVCPASSWORD:                 *****
      ISSVCSTARTUPTYPE:              Automatic
      NPENABLED:                     0
      PASSPHRASE:                    *****
      PCUSOURCE:                     
      PID:                           *****
      QUIET:                         False
      QUIETSIMPLE:                   False
      ROLE:                          <empty>
      RSINSTALLMODE:                 DefaultNativeMode
      RSSVCACCOUNT:                  NT AUTHORITY\SYSTEM
      RSSVCPASSWORD:                 *****
      RSSVCSTARTUPTYPE:              Automatic
      SAPWD:                         *****
      SECURITYMODE:                  <empty>
      SQLBACKUPDIR:                  <empty>
      SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
      SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
      SQLSVCPASSWORD:                *****
      SQLSVCSTARTUPTYPE:             Automatic
      SQLSYSADMINACCOUNTS:           E2KLAB\Gautamr
      SQLTEMPDBDIR:                  <empty>
      SQLTEMPDBLOGDIR:               <empty>
      SQLUSERDBDIR:                  <empty>
      SQLUSERDBLOGDIR:               <empty>
      SQMREPORTING:                  False
      TCPENABLED:                    1
      UIMODE:                        Normal
      X86:                           False
      Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\ConfigurationFile.ini
    Detailed results:
      Feature:                       Database Engine Services
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
      Feature:                       Full-Text Search
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Reporting Services
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Complete
      Status:                        Failed: see logs for details
      MSI status:                    Passed
      Configuration status:          Passed
      Feature:                       Management Tools - Basic
      Status:                        Failed: see logs for details
      MSI status:                    Failed: see details below
      MSI error code:                1324
      MSI log file location:         C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\BestPracticesPolicies_Cpu32_1.log
      MSI error description:         The folder path 'Program Files (x86)' contains an invalid character.
      Configuration status:          Passed
    Rules with failures:
    Global rules:
    Scenario specific rules:
    Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20150115_225416\SystemConfigurationCheck_Report.htm
    Any other suggestion i can try ?
    Gautam.75801

  • Windows Server 2012/2012R2 NIC Teaming Mode

    Hi,
    Question 1:
    In Windows Server 2012 the following teaming mode was recommended for Hyper-V NIC teams:
    Teaming mode: Switch Independent
    Load balancing mode: Hyper-V Port
    All Adapers Active
    In a session at TechEd 2014 it was stated that Dynamic is the new recommendation for Windows Server 2012 R2. However, a Microsoft PFE stated a few weeks ago that he would still recommend Hyper-V Port for Windows Server 2012 R2. What is your opinions around
    this?
    Question 2:
    We have a Hyper-V Failover Cluster which isn`t migrated to 2012 R2 yet, it`s running 2012. In this cluster we use Switch Independent/Hyper-V Port for the team. We also use converged networking, having 2 physical adapters bound to the NIC team, as well as
    3 virtual adapters in the management OS for management, CSV and Live Migration. Recently one of the team NICs failed, and this incident also caused the cluster membership on the affected node to go offline even though the other team NIC was
    connected. Is this expected behaviour? Would the behaviour be different if 2012 R2 with Dynamic mode was being used?

    Hello,
    As for question number 1:
    For Hyper-V workload it's recommended to use Dynamic with
    Switch Independent mode. Why?
    This configuration will distribute the load based on the TCP Ports address hash as modified by the Dynamic load balancing algorithm. The Dynamic load balancing algorithm will redistribute flows to optimize team member bandwidth utilization so individual
    flow transmissions may move from one active team member to another.  The algorithm takes into account the small possibility that redistributing traffic could cause out-of-order delivery of packets so it takes steps to minimize that possibility.
    The receive side, however, will look identical to Hyper-V Port distribution.  Each Hyper-V switch port’s traffic, whether bound for a virtual NIC in a VM (vmNIC) or a virtual NIC in the host (vNIC), will see all its inbound traffic arriving on a single
    NIC.
    This mode is best used for teaming in both native and Hyper-V environments except when:
    1) Teaming is being performed in a VM,
    2) Switch dependent teaming (e.g., LACP) is required by policy, or
    3) Operation of a two-member Active/Standby team is required by policy. 
    As for question number 2:
    The Switch Independent/Hyper-V Port will send packets using all active team members distributing the load based on the Hyper-V switch port number.  Each Hyper-V port will be bandwidth limited to not more than one team member’s bandwidth because the port
    is affinitized to exactly one team member at any point in time. 
    In all cases where this configuration was recommended back in Windows Server 2012 the new configuration in 2012 R2, Switch Independent/Dynamic, will provide better performance.
    Microsoft recommend for a clustered Hyper-V deployment
    in Windows server 2012 to use Switch Independent/Hyper-V Port as you mentioned and to configure
    Hyper-V QoS that applies to the virtual switch. (Configure minimum bandwidth in
    weight mode instead of in bits per second and Enable and configure QoS
    for all virtual network adapters 
    Did you apply QoS on the Converged vSwitch after you
    created the team?? However Nodes are considered down if they do not respond to 5 heartbeats. The Switch Independent/Hyper-V Port does not cause the cluster to goes down if one NIC failed. The issue is somewhere else and not in the teaming mode
    that you choose.
    Hope this help.
    Regards,
    Charbel Nemnom
    MCSA, MCSE, MCS, MCITP
    Blog: www.charbelnemnom.com
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if
    a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Windows Server 2012 as NTP Server for Windows Server 2008R2 Domain Controller

    We have one domain with 3 Windows Server 2008R2 DC's. Our Edge router is configured to get the time from the internet, and was our timesource for the PDC emulator. But lately we have migrated our major routers to Cisco IOS15, and now the timeservice on the
    PDCe is unable to fetch the time. This is a known bug, as you can read here:
    http://social.technet.microsoft.com/Forums/ja-JP/b16de048-8642-4799-b85a-ad092e17dd47/windows-server-2012-ntp-version-compatibility
    Now I've found out that Windows Server 2012 does sync with the router. That's our DirSync server, and is in the same VLAN as our DC's. So I thought: I'll set up the Windows Server 2012 as new timeserver, so our PDCe can sync with that server. (Compony
    policy is that DC's don't talk to the internet). Everything seems alright.
    I've set:
    w32tm /config /manualpeerlist:<IP of router>,0x8 /syncfromflags:manual
    w32tm /config /reliable:yes
    Changed the registry with:
    HKLM\SYSTEM\CC\SERVICES\W32TIME\TIMEPROVIDERS\NTPSERVER - Enabled:1
    HKLM\SYSTEM\CC\SERVICES\W32TIME\Config - AnnounceFlags:A
    And stopped and started the W32Time service. I can see that the Windows 2012 server is fetching the correct time, and checked with NBTSTAT -NA that it's listening on port 123.
    But our PDCe doesn't sync. (also changed the config so it has the 2012 server as timesource). Get the EventID 47:
    Time Provider NtpClient: No valid response has been received from manually configured peer <w2012server> after 8 attempts to contact it. This peer will be discarded as a time source and NtpClient will attempt to discover a new peer with this DNS
    name. The error was: The peer is unreachable.
    What more can I try?

    It only shows me the 3 DC's:
    DC04.domain.local *** PDC ***[[::1]:123]:
        ICMP: 0ms delay
        NTP: +0.0000000s offset from DC04.domain.local
            RefID: 'LOCL' [0x4C434F4C]
            Stratum: 1
    DC03.domain.local[10.x.x.x:123]:
        ICMP: 0ms delay
        NTP: -0.0097028s offset from DC04.domain.local
            RefID: DC04.domain.local [10.x.x.x]
            Stratum: 2
    DC05.domain.local[10.x.x.x:123]:
        ICMP: 0ms delay
        NTP: -0.0127883s offset from DC04.domain.local
            RefID: W8D-VW-DC04.domain.local [10.x.x.x]
            Stratum: 2
    Warning:
    Reverse name resolution is best effort. It may not be
    correct since RefID field in time packets differs across
    NTP implementations and may not be using IP addresses.

  • Forest and domain functional level Windows Server 2012 R2 - what's new?

    Hi, I still can't find documentation about the new domain and forest functional levels in WS 2012 R2.
    a) "What's New in Active Directory in Windows Server 2012 R2"
    http://technet.microsoft.com/en-us/library/dn268294.aspx
    No word about it.
    b) "Understanding Domain and Forest Functional Levels"
    http://technet.microsoft.com/en-us/library/cc771294.aspx
    Still WS 2012.
    Thorsten

    For what's New in Active Directory in windows server 2012 R2,
    Read the following Blog
    http://policelli.com/blog/archive/2013/06/27/whats-new-in-active-directory-in-windows-server-2012-r2-preview/
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer".

  • How to install first forest and active directory on the windows server 2012 R2 core?

    hi to all
    i installed a windows server 2012 R2 Core edition on the server platform and i want install first forest and Domain on this server core by cmdlet...but i cannot install it. i search in the technet and other sites and blogs on the internet
    and i saw many commands that use for install it such as "DCpromo /unattend" and even
    "Install-addsforest" in the powershell but still i cannot get a result from these commands.
    i need step-by-step guide that help me for install new forest and domain in the server 2012 R2 core.
    thanks a lot friends

    C:\PS>Install-ADDSForest
    -DomainName mydomain.local -CreateDNSDelegation
    -DomainMode Win2012 -ForestMode Win2008R2
    -DatabasePath "d:\NTDS"
    -SysvolPath "d:\SYSVOL"
    -LogPath "e:\Logs"
    you can use above example
    Darshana Jayathilake

  • Rename forest domain name windows server 2012 R2

    I have single DC windows server 2012 R2 ex:abc.local i want to change forest domain name to ab.local?

    Hello,
    is that an already running domain or is the server just installed?
    If the latter demote and promote with the new name again.
    Best regards
    Meinolf Weber
    MVP, MCP, MCTS
    Microsoft MVP - Directory Services
    My Blog: http://msmvps.com/blogs/mweber/
    Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

  • One way trust relationship between different domain windows server 2012 in different forest

    I'd like to build trust correctly between the domains A.local and B.int. A.local is on a Windows 2012 . B.int is on a Windows 2012 . Both machines are
    connected to the same LAN. The forest level in A.local
    machine is Windows Server 2008 and The forest level in B.int
    is Windows server 2012.
    I want a one-way trust relationship, i.e. users from A.local gain access to B.local.
    my problem it i create the trust put when i go to validate the trust between A.Local and B.int give me this error :
     The secure channel (SC) reset on Active Directory Domain Controller \\dc2.B.int of domain B.int to domain A.Local failed with error: There are currently no logon servers available to service the logon request.
    NOTE : Recently I
    UPGRADE THE Active Directory FROM 2008 R2 TO 2012 and i ping on A.local to B.int
    it is ping by name and IP but from b.int ping by IP JUST >>>
    ihab

    Hi,
    yes i already do it the setup conditional forwarding between the 2 domains and
    the firewall it is off 
    ihab

  • (Request for:) Best practices for setting up a new Windows Server 2012 r2 Hyper-V Virtualized AD DC

    Could you please share your best practices for setting up a new Windows Server 2012 r2 Hyper-V Virtualized AD DC, that will be running on a new WinSrv 2012 r2 host server.   (This
    will be for a brand new network setup, new forest, domain, etc.)
    Specifically, your best practices regarding:
    the sizing of non virtual and virtual volumes/partitions/drives,  
    the use of sysvol, logs, & data volumes/drives on hosts & guests,
    RAID levels for the host and the guest(s),  
    IDE vs SCSI and drivers both non virtual and virtual and the booting there of,  
    disk caching settings on both host and guests.  
    Thanks so much for any information you can share.

    A bit of non essential additional info:
    We are small to midrange school district who, after close to 20 years on Novell networks, have decided to design and create a new Microsoft network and migrate all of our data and services
    over to the new infrastructure .   We are planning on rolling out 2012 r2 servers with as much Hyper-v virtualization as possible.
    During the last few weeks we have been able to find most of the information we need to undergo this project, and most of the information was pretty solid with little ambiguity, except for
    information regarding virtualizing the DCs, which as been a bit inconsistent.
    Yes, we have read all the documents that most of these posts tend point to, but found some, if not most are still are referring to performing this under Srvr 2008 r2, and haven’t really
    seen all that much on Srvr2012 r2.
    We have read these and others:
    Introduction to Active Directory Domain Services (AD DS) Virtualization (Level 100), 
    Virtualized Domain Controller Technical Reference (Level 300),
    Virtualized Domain Controller Cloning Test Guidance for Application Vendors,
    Support for using Hyper-V Replica for virtualized domain controllers.
    Again, thanks for any information, best practices, cookie cutter or otherwise that you can share.
    Chas.

  • Re-use Hyper V VM built in Windows Server 2008 R2 host in a new Windows Server 2012 host

    Hi Forum members,
    I was assigned a Windows Server 2008 R2 host machine with Hyper-V which I used to build many VM's for testing.  This host machine now is going to be replaced with a new Windows Server 2012 host machine.  Is it possible for me to continue
    to use those VM's without any migration (e.g. is it possible to import or simply move the *.vhd + *.avhd files from the 2008 Server to 2012 Server and use them)?
    Thanks and Regards,
    Hien

    That is the official statement of 'support'
    They will run, and you may need to do some custom configuration (such as using a legacy nic) but you can't call MSFT support and say your Server 2003 VM is broken on Hyper-V 2012 R2
    The act of importing the configuration and linking to the VHD and snapshots will work.
    The act of booting the VM and having the OS in the VM 100% happy is not automatic, but should work.
    It becomes a question of where do you place the risk.
    Brian Ehlert
    http://ITProctology.blogspot.com
    Learn. Apply. Repeat.

  • New Mac Pro (late 2013), Boot Camp, Windows Server 2012

    Does new Mac Pro (late 2013) support Windows Server 2012 install by Boot Camp?

    No.
    Boot Camp: System requirements for Microsoft Windows operating systems - Apple Support
    Apologies, Templeton Peck, did not see your post.

  • New Windows Server 2012 unable connect to Netlogon Service or update DNS records

    Hi everybody, all of my Windows Servers 2012 decided to collapse after innocuous group policy update that was meant to make user passwords more secure.
    The AD and DNS seem to be functioning "normally", I am able to add new Windows7 and Windows Server 2008 machines to the domain, I can see them in listed in the AD and DNS record are update correctly, however, as soon as I try to join Windows Server
    2012 it breaks.
    The event log is littered on the new server with:
    The system failed to register host (A or AAAA) resource records (RRs) for network adapter
    with settings:
               Adapter Name : {DB7F73CE-E011-4F3C-BEBC-2CE7A871DF51}
               Host Name : CHEETAH
               Primary Domain Suffix : somedomain.com
               DNS server list :
    192.168.0.5
               Sent update to server : <?>
               IP Address(es) :
    192.168.0.15
    The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running
    at this time.
    You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
    and
    Name resolution for the name _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.somedomain.com. timed out after none of the configured DNS servers responded.
    When I try to ping the primary DC (WS2003) it fails, the Secondary DC (WS2012) responds.
    The >nltest /sc_query:somedomain.com on Windows Servers 2012 returns:
    Flags: 0
    Trusted DC Name
    Trusted DC Connection Status Status = 1311 0x51f ERROR_NO_LOGON_SERVERS
    The command completed successfully
    yet it works on all other machines.
    I tried removing 2012 servers from the domain and rejoining - without success. The cookie crumbled when I added two new installations of Windows Server 2012 & 2008 and 2008 worked fine but 2012 showed same symptoms.
    There is one peculiar thing that I had noticed on all Windows 2012 machines, it constantly showing "Workplace Connection - Connecting" in the networks pane on the right side of the screen, which I can't say i ever noticed before.
    Unfortunately, the secondary DC is a multihoming server with Direct Access role - I am not sure if this may play some part but our existing configuration worked for a year now without any problems. Issue appeared when I changed the password complexity rule,
    which boggles the mind. I wonder if there has been some other changes in GPO that did not propagate from years ago and finally comeback to break things.
    Any suggestions would be really appreciated.
    wmin

    Hello Ace, i wish you a Happy New Year! I hope your break was enjoyable and filled with cheer.
    In the end I had to bite the bullet and reinstall all troublesome servers. Your recommendations from above removed some serious problems with the DA and DNS resolution.
    I was able to attach new server to the domain without any problems and begin painful process of rebuild.
    I have promoted TIGER to full DC controller role, but having some issues with replication. Although running >repadmid /showrepl gives positive
    feedback, the sysvol folder on the secondary DC is empty.
    Also there is a couple of warnings in the event log:
    Event ID 4012
    Log Name: DNS Server
    Source: DNS-Server-Service
    The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial
    synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server
    for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.
    - which has not repeated since 3rd of Jan.
    These events occur on the primary DC every few minutes:
    Event ID 1030
    Source: Userenv
    Log Name: NT AUTHORITY\SYSTEM
    Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Event ID 1058
    Source: Userenv
    Log Name: NT AUTHORITY\SYSTEM
    Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=somedomain,DC=com. The file must be present at the location <\\somedomain.com\sysvol\somedomain.com\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.
    (The network name cannot be found. ). Group Policy processing aborted.
    For more information, see Help and Support Center at
    http://go.microsoft.com/fwlink/events.asp.
    Should sysvol folder be shared on the secondary DC? Another interesting thing to point out is that
    \\somedomain.com\sysvol\somedomain.com\Policies\ can be access
    from all other machines except the DC1.
    Cheers!
    kind regards,
    wmin

  • Just FYI, new Windows Server 2012 R2 RRAS Multitenant Gateway Deployment Guide

    New! Windows Server 2012 R2 RRAS Multitenant Gateway Deployment Guide
    This new guide is available on the Web at
    http://technet.microsoft.com/en-us/library/dn641937.aspx. It is also available for download in Word format at TechNet Gallery at
    http://gallery.technet.microsoft.com/Windows-Server-2012-R2-37eb8e17
    If you work for a Cloud Service Provider (CSP) or an organization that's planning on deploying cloud technologies, you might be interested in the new Windows Server 2012 R2 RRAS Multitenant Gateway Deployment Guide.
    You may already know that in Windows Server® 2012 R2, the Remote Access server role includes the Routing and Remote Access Service (RRAS) role service. (It also includes DirectAccess and Web Application Proxy, however those role services will not be discussed
    in this article.)
    The new deployment guide demonstrates how to use Windows PowerShell to deploy RRAS as a virtual machine (VM)-based multitenant software gateway and Border Gateway Protocol (BGP) router that allows CSPs and Enterprises to enable datacenter and cloud network
    traffic routing between virtual and physical networks, including the Internet.
    You can use the gateway with VM networks by using either Hyper-V Network Virtualization or Virtual Local Area Networks (VLANs) - but using Network Virtualization is recommended due to VLAN limitations such as difficult management and a limited number of
    available VLAN IDs.
    If you're using System Center Virtual Machine Manager (SC VMM), you can use SC VMM to deploy Windows Server Gateway; however even if you are using SC VMM, you can manage the gateway with the same Windows PowerShell commands that are used for the RRAS Multitenant
    Gateway. (Some Windows Server Gateway features are configurable only with Windows PowerShell.)
    For information on deploying Windows Server Gateway with SCVMM, see the Test Lab Guide: Windows Server 2012 R2 Hyper-V Network Virtualization with System Center 2012 R2 VMM, at
    http://www.microsoft.com/download/details.aspx?id=39284
    With the RRAS Multitenant Gateway, you can create site-to-site VPN connections between your tenants' physical locations and your cloud datacenter. You can also provide tenants with point-to-site VPN connections that allow tenant Administrators to access
    and manage their VM resources from anywhere. The RRAS Multitenant Gateway also allows you to configure Network Address Translation (NAT), so that tenant VMs can access the Internet, and you can deploy dynamic routing by configuring the gateway and tenant gateways
    with BGP.
    Thanks -
    James McIllece

    Hi,
    It is very useful , thanks for your sharing .
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • New Windows Server 2012 install won't boot after installing Hyper-V role.

    I have just installed Windows Server 2012 onto a Dell PowerEdge R310.  Everything worked okay until I installed the Hyper-V role.  After that, when it tries to boot, I get "Your PC ran into a problem and needs to restart. We're just collecting
    some error info, and then we'll restart for you. (0% complete)" for a split second, then the system reboots into Automatic Repair mode.
    In Automatic Repair mode, my options are Refresh your system (which tells me the drive that Windows is on is locked), Reset your system (which tells me there is no partition), and Automatically Fix your PC (which tells me it can't fix it).
    I have updated to the latest version of the BIOS (1.11.0, which Dell states adds Windows Server 2012 support).
    I'm at a loss.. I've tried everything I can think of.  Has anyone run into this issue and figured out a solution?  The only references I can find to this issue talk about Gigabyte motherboards with USB 3.0, but this server pre-dates USB 3.0 by
    quite a bit.

    Hi,
    Not only the BIOS but the iDRAC and storage part also need to ne up date check, have a look at the following list to see what you need for Server 2012:
    http://en.community.dell.com/techcenter/os-applications/w/wiki/3868.dell-bios-support-for-windows-server-2012.aspx
    If any info was collected during the error then have a look in the event viewer or look for a kernel/memory dump file so you can try to find the issue, in many cases a driver, anti-virus sofware or 3rd part service can cause these kind of issues.
    When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer
    MCSE:Server Infrastructure, MCSE:Desktop Infrastructure, MCSA Server 2012, Citrix CCIA & CCEE, Cisco CCNA, VMware VCP 3/4/5 Blog: http://www.citrix-guru.com and http://www.rds-support.eu Twitter: @dnyvandam

Maybe you are looking for