FRS to DFSR migration (Child domain)

Planning on migrating FRS to DFSR for a child domain, I know this is a per domain process.
It shouldn't matter which domain is migrated first, the child or root. But to doublecheck : The plan is to migrate they child domain and the root domain will take a couple of months before it's prepared. Does it matter? Even though i'm pretty certain it
doesn't matter because it's a per domain process, but wanted to verify.

> It shouldn't matter which domain is migrated first, the child or root.
No, it doesn't.
Martin
Mal ein
GUTES Buch über GPOs lesen?
NO THEY ARE NOT EVIL, if you know what you are doing:
Good or bad GPOs?
And if IT bothers me - coke bottle design refreshment :))

Similar Messages

  • FRS to DFSR Migration and Riverbed RODCs

    As I understand it, Riverbed RoDCs are only there to grab session keys from AD in order to optimize SMB traffic. Please correct me if I'm wrong. 
    I'm in the middle of trying to migrate from FRS to DFSR for SYSVOL, but when moving from the Start to Prepared state, DFSRMig complains that the Riverbed RoDCs aren't following. 
    C:\Users\adminaccountname>dfsrmig /getmigrationstate
    The following Domain Controllers are not in sync with Global state ('Prepared'):
    Domain Controller (Local Migration State) - DC Type
    ===================================================
    xxx1a-xxx-xx05 ('Start') - Read-Only DC
    xxx1a-xxx-xx03 ('Start') - Read-Only DC
    xxx1a-xxx-xx04 ('Start') - Read-Only DC
    Pretty sure this is entirely out of my control and there might be a mode of operations on the Riverbed side that needs to be raised along with the functional level of the forest and domain, but I'm getting nothing from the Riverbed documentation that I can
    get my hands on. I'm waiting to hear from our networking team. 
    In the meantime, has anyone had any experience with this?

    Hi,
    Migration from one stable state to another can take an extended period, especially if some of the domain controllers are read-only. In these cases, migration may not reach a consistent state on all domain controllers for a long time after you change the
    global migration state.
    For more and detail information, please refer to:
    Troubleshooting SYSVOL Migration Issues
    http://technet.microsoft.com/en-us/library/dd639976(v=ws.10).aspx
    Hope this helps.
    Regards.
    If you have any feedback on our support, please click
    here
    Vivian Wang

  • General SYSVOL migration from FRS to DFSR

    Hi all.
    I have a question regarding Sysvol Migration from FRS to DFSR.
    We have migrated all of our Domain Controllers from Server 2003 to Server 2008 R2 about 2 years ago.
    I know that if Server 2003 was in use initially and you upgrade to Server 2008 R2, you need to do a FRS to DFSR migration in order for you Sysvol to make use of DFSR.
    My question is if we are upgrading now to server 2012 R2 would there be a time that this would happen automatically or do we still need to do the sysvol migration before upgrading to server 2012 R2.
    Another question I have is do we need to do the FRS to DFSR migation on all our child domains as well ?
    Many thanks for your time.
    Your answers would be appreciated.
    Kind Regards,
    Shaun

    Hi There.
    Yes that would be great. I would probably use the active directory removal method but I dont know if this would work as its the last domain contoller and it is not replicating with the top level domain at the moment.
    NTDSUTIL would probably need to be used ro list the servers in that domain and remove them and then if I'm correct I would need to remove the domain namig contect with the instructions below.
    Removing Orphaned Domains from Active Directory
    Determine the domain controller that holds the Domain Naming Master Flexible Single Master Operations (FSMO) role. To identify the server holding this role:
    Start the Active Directory Domains and Trusts Microsoft Management Console (MMC) snap-in from the
    Administrative Tools menu.
    Right-click the root node in the left pane titled
    Active Directory Domains and Trusts, and then click Operations Master.
    The domain controller that currently holds this role is identified in the Current Operations Master frame.NOTE: If this changed recently, not all computer may have received this change yet due to replication.
    For more information about FSMO roles, click the following article number to view the article in the Microsoft Knowledge Base:
    197132 Windows 2000 Active Directory FSMO Roles
    Verify that all servers for the domain have been demoted.
    Click Start, point to Programs, point to
    Accessories, and then click Command Prompt.
    At the command prompt, type: ntdsutil.
    Type: metadata cleanup, and then press ENTER.
    Type: connections, and then press ENTER. This menu is used to connect to the specific server on which the changes will occur. If the currently logged-on user is not a member of the Enterprise Admins group, alternate credentials can be supplied
    by specifying the credentials to use before making the connection. To do so, type:
    set creds domainname username password , and then press ENTER. For a null password, type:
    null for the password parameter.
    Type: connect to server <var>servername</var> (where <var>servername</var> is the name of the domain controller holding the Domain Naming Master FSMO Role), and then press ENTER. You should receive confirmation that the connection is successfully
    established. If an error occurs, verify that the domain controller being used in the connection is available and that the credentials you supplied have administrative permissions on the server.
    Type: quit, and then press ENTER. The Metadata Cleanup menu is displayed.
    Type: select operation target, and then press ENTER.
    Type: list domains, and then press ENTER. A list of domains in the forest is displayed, each with an associated number.
    Type: select domain <var>number</var>, and then press ENTER, where <var>number</var> is the number associated with the domain to be removed.
    Type: quit, and then press ENTER. The Metadata Cleanup menu is displayed.
    Type: remove selected domain, and then press ENTER. You should receive confirmation that the removal was successful. If an error occurs, please refer to the Microsoft Knowledge Base for articles on specific error messages.
    Type: quit at each menu to quit the NTDSUTIL tool. You should receive confirmation that the connection disconnected successfully.
    Thanks again for all your help.
    Regards.
    Shaun

  • Active Directory migration from domain X to Y

    Hey Guys 
    Planning to migrate Child domain to another child domain inter forest with ADMT 
    we do have a small environment with Active directory integrated DNS, I do have a rough knowledge of migrating domains but still if there is any checklist kind of thing on priority (i.e migrate users first then do groups then computers then GPO) and let me
    know how much time it will take for 500 users 800 machines and 400 groups approximately .
    We do not have techinical Architecture guys to plan up , Please list out any excel sheets for migration if any
    Went through n number of blogs but still did not get any proper info about this , Thank you in advance

    1) I would recommend you first run a test of the steps in test before you do this in production.  Otherwise your production becomes test.
    2) By doing in test, you have taken a large amount of the risk out of the upgrade since, in test you should be able to look for any unforseen issues.  The easiest way to test is to build a virtual fence from production and clone the DC's and member
    servers that you want to test against (This is assuming you are running in a virtual environment).  Ensure that you production environment is error free.
    http://blogs.dirteam.com/blogs/paulbergson/archive/2009/01/26/troubleshooting-active-directory-issues.aspx
    3) There should be no downtime at all, you can just extend the schema and then promote a new 2012 DC (I would recommend R2 if you can).
    4) Before you do the schema extension you should take 2 backups on two different DC's.  Taking two gives you less of a chance of a problem if one of the backups fails.
    5)
    Take a backup
    Extend the schema
    Join the 2012 R2 servers to the domain
    Add the ADDS role to the 2012 R2 member servers
    Promote the 2012 R2 DC's
    Transfer the FSMO roles to the 2012 R2 DC's (Not required but recommended)
    If you want to retire the 2003 DC's, then you will need to make sure that any clients pointing to the 2003 DC's for DNS are pointing to other DC's.
    If you do retire the 2003 then you can think about updating the DFL and FFL of the domain and forest.
    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security, BS CSci
    2012, 2008, Vista, 2003, 2000 (Early Achiever), NT4
    Twitter @pbbergs http://blogs.dirteam.com/blogs/paulbergson
    Please no e-mails, any questions should be posted in the NewsGroup.
    This posting is provided AS IS with no warranties, and confers no rights.

  • Migrated domain replication from FRS to DFSR. Domain query

    Hello,
    I run 3 domain controllers, all on the same LAN; the PDC is on 2008R2 and the others on 2012
    I have today migrated from FRS to DFSR.
    Without going through all the errors that dcdiag is now showing, I have a simple query. When our domain was setup, it was named COMPANY   ie. not COMPANY.LOCAL.    It has all seemed to work OK for ages but in DNS Forward Lookup Zones I see
    the following folders:
    _msdcs.company
    company
    company.company
    In company.company are just the 3 domain controllers. Can I delete this folder?
    Other question at this stage is about DNS forwarders. All LAN PCs point to the 3 x DCs for their DNS servers, and DNS Server is running on all 3 DCs. Should I put my ISPs DNS servers in the forwarders or not, and do I use root hints? (I have 2 ISPs so don't
    know which ISP will be used by any PC as the router load balances)
    many thanks in advance

    Hi,
    Yes, i think you could delete the folder, if the replication is ok.
    You could use your ISPs DNS server as a forwarders.
    http://blogs.technet.com/b/tugait/archive/2014/02/11/dns-forwarders-vs-root-hints.aspx
    Regards.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • User Migration from Parent Domain to Child Domain..The user is enabled with Exchange 2010 Mailbox in Parent Domain

    We currently have a single Windows 2008 R2 Active Directory domain controller, and an Exchange 2010 server. We are in the process of adding a child domain on a second Active Directory server for an offsite office location for a subdivision of our company.
    The two locations will be connected via VPN.
    Currently users exist on the root domain with Exchange accounts who will be moving to the new offsite company/location. We would like to be able to move these user accounts to the child domain while maintaining their existing Exchange mailboxes and
    email addresses. Is this possible, and if so how would we do it?

    Hi Srinivasa,
    According to your description, I think you have done all the preparation.
    For DL migration, the following article may give your some hints:
    How to Migrate Distribution Groups Across a Forest
    Good Luck!
    Niko Cheng
    TechNet Community Support

  • Migrate Users from a child domain to a root domain in different forest

    Hello,
    it supported to migrate users from child source doman to target root domain?
    I established a trust, but i don't see child domain at ADMT installed on target domain DC. Source root domain is visible

    You should not be needed to establish a trust as all domains within the same forest already trust each other - are you sure those domains belong to the same forest? You can find out using the following command:
    nltest /DOMAIN_TRUSTS
    If ADMT dosen't show a partiuclar domain in the dropdown list, you can/have to type the domain name manually.
    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

  • Migrating to Lync in a child domain from OCS in a Parent domain

    I am looking to migrate from OCS to Lync 2010.  I have gotten as far as deploying the target pool, but when I try and merge the topologies it fails.
    OCS is in The root domain of my forest but Lync is planned for the primary Child domain where 80% of my users live.  I just need to know if this is a supported migration scenario for Lync.  If it is how do I merge the two topologies, as it looks
    like the merge tool is only looking at the child domain for the configuration of OCS?
    Jeff

    Hi,
    Did you build a new pool with Side by side approach?
    It is supported to migrate Lync from one domain to another domain in the same forest. Here is the supported server migration paths in the link below:
    http://technet.microsoft.com/en-us/library/gg425764.aspx
    For the issue merge topology failed, did you receive any error message from FE server Event Viewer?
    The Lync server default sip domain should be the same when migrating from OCS to Lync server. If not, you can add sip domain in Lync topology and then run the command such as below on Lync FE server:
    Set-CsSipDomain –Identity new sip domain name –IsDefault $True    
    Note: (change new sip domain name to your Lync server sip domain name)
    Then run OCS merge again to test the issue again.
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Migrating 2 domains into child domains in a new forest

    I have a unique senario in which my company merged with another. 
    My Company:
    Windows 2003 AD
    Exchange 2003 SP3
    192.x.x.x
    New Company
    Windows 2008 AD
    Exchange 2010
    10.x.x.x
    Each domain has its own resources, servers and workstations.  For political reasons we still need some management seperation. 
    My Goals:
    Create a new root neutral forest/domain. 
    Migrate both domains to 2 child domains under this new root
    Bring the domain to 2012 R2
    Create a single Exchange 2010/2013 cluster with all mailboxes
    What is the best way to accomplish this? Where exactly does Exchange sit?
    Thanks!

    Hi,
    >>What is the best way to accomplish this?
    In Active Directory, we can use ADMT to do the migration. However, if we need Inter-forest migration from Domain Controller 2003 to Domain Controller 2012, at this time MS
    has not ADMT for Windows Server 2012. We can downgrade our forest and Domain functional level to Windows Server 2008 R2, add an additional Domain Controller 2008 R2 and use ADMT 3.2 for migration. After migration is completed, we can demote Domain Controller
    2008 R2 and raise again FFL & DFT to Windows Server 2012.
    Regarding specific procedures for performing the migration, the following article can be referred to as reference.
    Interforest Migration with ADMT 3.2 - Part 1
    http://social.technet.microsoft.com/wiki/contents/articles/11996.interforest-migration-with-admt-3-2-part-1.aspx
    Interforest Migration with ADMT 3.2 - Part 2
    http://social.technet.microsoft.com/wiki/contents/articles/16208.interforest-migration-with-admt-3-2-part-2.aspx
    Interforest Migration with ADMT 3.2 - Part 3
    http://social.technet.microsoft.com/wiki/contents/articles/16621.interforest-migration-with-admt-3-2-part-3.aspx
    >>Where exactly does Exchange sit?
    For mailbox migration, in order to get better help, we can ask for suggestions in the following exchange forum.
    Exchange Server 2013- Setup, Deployment, Updates, and Migration
    http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrdeploy
    Best regards,
    Frank Shen

  • Addint a child domain process hangs in Replicating the schema directory partition

    Hello everyone,
    for practice proposes and exam preparations I have my own virtual private network setup on an PowerEdge R905 Machine (which is a beast) I have two networks and windows server 2008R2 on a DMZ zone setup as router to rout traffic between two of my networks.
    My two networks are 192.168.10.0 - and 192.168.20.0. the 10 network has its own active directory setup, now on my 20 network I am trying to deploy a child domain. during the process everything is going just fine BUT the process of promoting the domain gets
    stuck on Replicating The Schema Directory Partition. Can anyone tell me what the issue might be ? I tried everything that I could think of such as:
    made sure the 20 network server is pointed to the DNS on the 10th server.
    you can ping the IP address and the FQDN of 10 network from the 20 network.
    I made sure all firewalls are disabled on both networks
    on my 10 network I have created sites  and assigned the right subnets for each site
    so please any hint and explanation is greatly appreciated

    If firewalls are disabled between the 2 subnets then you are sure that all of the below ports are opened:
    Client Port(s)
    Server Port
    Service
    49152 -65535/UDP
    123/UDP
    W32Time
    49152 -65535/TCP
    135/TCP
    RPC Endpoint Mapper
    49152 -65535/TCP
    464/TCP/UDP
    Kerberos password change
    49152 -65535/TCP
    49152-65535/TCP
    RPC for LSA, SAM, Netlogon (*)
    49152 -65535/TCP/UDP
    389/TCP/UDP
    LDAP
    49152 -65535/TCP
    636/TCP
    LDAP SSL
    49152 -65535/TCP
    3268/TCP
    LDAP GC
    49152 -65535/TCP
    3269/TCP
    LDAP GC SSL
    53, 49152 -65535/TCP/UDP
    53/TCP/UDP
    DNS
    49152 -65535/TCP
    49152 -65535/TCP
    FRS RPC (*)
    49152 -65535/TCP/UDP
    88/TCP/UDP
    Kerberos
    49152 -65535/TCP/UDP
    445/TCP
    SMB
    49152 -65535/TCP
    49152-65535/TCP
    DFSR RPC (*)
    Then make sure that the other subnet is across route not across NAT to avoid a lot of additional configurations.
    Regards,
    Housam Smadi

  • FRS and DFSR replication

    Hi all,
    fase 1
    My domain controllers are both Windows 2003 R2 and Windows 2008 and Windows 2008R2. Domain functional level is Windows 2003
    fase 2
    I upgrade all my domain controllers to Windows 2008R2 and raised the domain functional level to Windows 2008R2.
    Now do domain controllers replicate via DFS-R? Have I to make some operation to get all replication works via DFS-R?

    Hi,
    Domain controllers use a special shared folder named SYSVOL to replicate logon scripts and Group Policy object files to other domain controllers. Windows 2000 Server and Windows Server 2003 use File Replication Service (FRS) to replicate SYSVOL, whereas
    Windows Server 2008 uses the newer DFS Replication service when in domains that use the Windows Server 2008 domain functional level, and FRS for domains that run older domain functional levels.
    To use DFS Replication to replicate the SYSVOL folder, you can either create a new domain that uses the Windows Server 2008 domain functional level, or you can use the procedure that is discussed in this document to upgrade an existing domain and migrate
    replication to DFS Replication.
    There are many helpful articles for you to refer to to migrate sysvol replication form FSR to DFSR. Please refer to the below link to find a article you want to follow:
    http://blogs.technet.com/b/askds/archive/2009/05/01/sysvol-migration-from-frs-to-dfsr-whitepaper-released.aspx
    Regards,
    Yan Li
    Yan Li
    TechNet Community Support

  • Post SYSVOL DFSR migration

    Hi all,
    I believe my question is similar to this one:  http://social.technet.microsoft.com/Forums/windowsserver/en-US/735b1cd7-bd92-4ef6-82a1-e4b900f03d36/migrated-sysvol-to-dfsr-successfullydo-i-need-to-stop-and-disable-ntfrs
    The short and skinny of it is that a few months ago, I finished migrating my domain controllers away from using FRS in favor of DFSR.  The FRS service is still enabled and, they try to locate and share the .\windows\sysvol folder.  This generates
    NtFrs event ID's 13539, 13552 and 13555 on DC's that were around during the migration.  As far as I can tell, this doesn't actually hurt anything as DFSR works well.
    I have tried to remove the relevant registry entries for the FRS replica sets, but they come back after restarting the FRS service and I get a fresh set of errors in my NtFrs logs.  
    According to this, http://blogs.technet.com/b/filecab/archive/2008/03/19/sysvol-migration-series-part-5-migrating-to-the-eliminated-state.aspx,
    the following excerpt describes what should happen regarding the now defunct FRS service.
       If
    the FRS service is running on the domain controller, it is then stopped. It deletes the Active Directory configuration settings required for the FRS service to replicate the SYSVOL share between domain controllers. Thus, all global settings of the FRS
    service that pertain to the SYSVOL content set are deleted.
    The ‘SYSVOL’ folder which was being replicated by the
    FRS service is now deleted. Note that if you have Windows Explorer or the command shell open on the domain controller and if the current directory corresponds to the ‘SYSVOL’ folder location, the DFS Replication service will be unable to delete
    this folder owing to sharing violations.
    The old sysvol folders are definitely gone.  But, the service is still running and still have replica sets in the registry.  DfsrMig reports the Global state as Eliminated and is consistent.
    The bottom line of my question is whether or not I can safely disable the FRS service, assuming that there are no other replica sets for FRS.  If anyone would like to expound on that with more information about the replica sets returning (on DC's that
    were around during the migration) or why the FRS service wasn't stopped by the DFS replication service, et cetera, feel free.  I would be interested.  But the primary concern is with disabling the FRS service.
    Thank you very much in advance. 
    -Trevor

    You can safely disable the File Replication Service (FRS) Service on those DCs.
    Enfo Zipper
    Christoffer Andersson – Principal Advisor
    http://blogs.chrisse.se - Directory Services Blog

  • Exchange 2010 unable to find objects in child domain via ESM

    I am having a problem on Exchange 2010 which relates to mailboxes whose AD account is in a child domain in the AD forest.
    We have two domains A & B in the forest. The site which hosts E2010 only has DCs from domain A (root domain). These DCs are set as Global Catalogues.
    All Exchange servers (2 x CAS & 2 x Mailbox) installed in Domain A (primary site) can resolve domain B and performing nslookups for domain B on these server displays the DCs installed
    in domain B at remote sites.
    I am migrating some resource mailboxes with AD accounts in domain B and need to set them up as room mailboxes to enable the auto accept bookings feature.
    After migrating the mailboxes via the EMS to set the mailbox as a room, below is the error I get:
    [PS] C:\Windows\system32>set-mailbox mtgrm1@domainB
     -Type Room
    The operation couldn't be performed because object 'mtgrm1@ domainB' couldn't be found on 'DC01.domainA.com'.
        + CategoryInfo          : NotSpecified: (0:Int32) [Set-Mailbox], ManagementObjectNotFoundException
        + FullyQualifiedErrorId : 9E6F6A1,Microsoft.Exchange.Management.RecipientTasks.SetMailbox
    I have also tried using only the alias and the object CN:
    set-mailbox mtgrm1 -Type Room
    set-mailbox –identity 'domainB/Sitename/ Users/MSX Resource Accounts/Conf MtgRm1 (Video)' -Type Room
    but get the same error.
    All employee mailboxes from Domain B have been migrated to Exchange 2010 from 2003 and are working with no problems.
    I have confirmed domain B has been prepared for E2010 - In the Microsoft Exchange System Objects container in AD there is the global group Exchange Install Domain Servers.
    Event ID 2080
    Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1864). Exchange Active Directory Provider has discovered the following servers with the following characteristics:
     (Server name | Roles | Enabled | Reachability | Synchronized | GC capable | PDC | SACL right | Critical Data | Netlogon | OS Version)
    In-site:
    dc02.domainA.COM           
    CDG 1 7 7 1 0 1 1 7 1
    DC01.domainA.com            
    CDG 1 7 7 1 0 1 1 7 1
     Out-of-site:
    DC03.domainA.COM          
    CDG 1 0 0 1 0 0 0 0 0
    dc04.domainA.COM           
    CDG 1 0 0 1 0 0 0 0 0
    Please note the Out of site DCs are for our Exchange failover site which is currently down due to the storms on the East Coast.
    Does Exchange 2010 require a local DC for the second domain installed in the sites which host Exchange? If not, any advise on what else I can look at will be appreciated.
    Thanks.

    Hi there,
    If the questions is answered, please mark it accordingly. Thanks. 
    Fiona Liao
    TechNet Community Support

  • Active Directory: 2003 to 2012 R2 Upgrade across single forest with child domains

    I just have a quick questions about something that should be simple. We will be upgrading our current domain from Windows 2003 functionality to Windows 2012 R2.  This forest has domain and two child domains.  I have two questions.  Since we
    have to do this in a few steps in order to get up to 2012 functionality I am wondering where is it consider best practice to start?  In the Root (top level) domain of the forest or in one of the child domains?  I want to say the root (top level)
    domain is where I would place my first Windows 2012 R2 box and promote it to a domain controller.  Then move to the child domains one the root domain controllers have all be replaced with Server 2012.
    Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.

    Yes.  We are working with the client to migrate any dependencies off these 3 NT legacy domains.  We will be able to decommission 2 of the 3 without any issues.  However, they still have an old NT box running SQL 6.5 databases for a application
    still in production.  Yes, they are very aware that NT isn't supported, that that version of SQL isn't supported, and that this will hold up their upgrade.
    Our plans for them will be to deploy all new Windows Server 2012 R2 domain controllers but keep the domain and the forest functionality at 2003 in order to support that final NT Legacy domain until they can get that application migrated.
    Once that NT domain is decommissioned then we can raise the functionality of the rest of their domains from 2003 to 2012 R2.
    Kristopher Turner | Not the brightest bulb but by far not the dimmest bulb.

  • Parent child domain best practice

    Currently we have multiple location, each location has its own AD and DNS, they are not connected to each other.
    Mostly the user at these location do not login/access resources of the other location. The few user that needed to login/access resources at multiple location have one account per location. This was fine since we had very few user who
    needed multiple account, but now with their number growing it is creating problems for many of the users.
    We are planning to redo our AD infra structure by installing new AD's on windows 2012 R2 Servers. We would like to setup one parent domain and multiple child domain (one per location).
    Users created on parent domain should be able to login/access resources from each location whereas user of a child domain should be able to only login/access resources at their location.
    Can someone please recommend a best way to do this?
    SKR

    if you are planning on redoing your AD infra, do not create additional AD domains, but rather CONSOLIDATE what you already have into one AD forest with one AD domain. Create OUs to manage objects differently or allow different teams to have their own delegation,
    and create AD sites/subnets to optimize replication and authentication.
    To consolidate AD domains see:
    http://jorgequestforknowledge.wordpress.com/2006/12/27/migrating-stuff-with-admtv3/
    http://jorgequestforknowledge.wordpress.com/2014/06/19/microsoft-released-an-admt-version-to-also-support-w2k12r2/
    Cheers,
    Jorge de Almeida Pinto
    Principal Consultant | MVP Directory Services | IAM Technologies
    COMMUNITY...:
    DISCLAIMER: This post is provided "AS IS" with no warranties of any kind, either expressed or implied, and confers no rights! Always evaluate/test yourself before using/implementing this!

Maybe you are looking for