Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Suggested Answer
  • Replies replies
    41
  • Answers answer
    1
  • Subscribers subscribers
    27
  • Views views
    1691
  • Users 0 members are here
Related
Options

Has anyone experience with migrating from DSfW to MS AD?

Franz Sirl

Hi,

has anyone here ever migrated from DSfW to MS AD? Especially I want to keep as much of the

current setup as possible, like DomainName, DomainSID, DomainGUID and user info.

Is that even possible?

regards,

Franz Sirl

Parents

  • Suggested Answer

    0

    Interesting.  I would think if you could install a Windows DC in your environment as a secondary DC it would work.  After transferring your FSMO roles you should technically be able to decommission the DSfW server.  So I would first join a server to the Domain, promote the server to a DC, move the FSMO roles and decommission the DSfW server.  The interesting part would be how Windows handles being promoted in the environment.  The fact that you have DSfW means you already have most of the attributes needed to preform the promotion of a Windows DC in a DSfW environment.

  • 0 in reply to 

    Would really like to hear the results if someone tries it.

  • 0 in reply to 

    Fell a tad behind, realized I need some actual Domain Dependent item running Test environment with following configuration:

    • OES - Primary eDir Server
    • OES-File - File Server
    • OES-AD - DSfW Server
    • Win-RDSGW - RDS GateWay
    • WIN-RDSBKR - RDS Connection Broker
    • WIN-SH01 - RDS Session Host 1
    • Win-SH01 - RDS Session Host 2

    Found out a Windows DC will not communicate with a DSfW server.  Windows cannot read Novell DNS and DNS is critical for AD

Reply
  • 0 in reply to 

    Fell a tad behind, realized I need some actual Domain Dependent item running Test environment with following configuration:

    • OES - Primary eDir Server
    • OES-File - File Server
    • OES-AD - DSfW Server
    • Win-RDSGW - RDS GateWay
    • WIN-RDSBKR - RDS Connection Broker
    • WIN-SH01 - RDS Session Host 1
    • Win-SH01 - RDS Session Host 2

    Found out a Windows DC will not communicate with a DSfW server.  Windows cannot read Novell DNS and DNS is critical for AD

Children

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.