7 Replies Latest reply on Nov 9, 2018 10:41 PM by shivkumar4

    Linux Machine to Domain

    laya_09 Lurker

      Hi All,

       

      I am able to use Customization scripts to join a Windows Machine to a domain once built within VRA. Question is how can i do the same for a Linux Machine ?

       

      was thinking of using Install Ansible run playbook on local host to join domain, uninstall Ansible during the creation of the machine within VRA. but there has to be a more simpler way

        • 1. Re: Linux Machine to Domain
          daphnissov Champion
          Community WarriorsvExpert

          If you want to talk about what's simplest, it's probably using the SovLabs Active Directory module where you define an AD profile

           

           

          it automatically creates a property group for you, and then you simply attach it to any blueprint that you want to join AD.

           

          • 2. Re: Linux Machine to Domain
            laya_09 Lurker

            Hi Daphnissov

             

            This would join both Linux and Windows to a Domain allowing Red Hat user to log with there AD user and password.

             

            I was looking at installing Ansible on the Red hat machine and playing a join.yml script and calling that during creation from Software components and removing both Ansible and that playbook once finished.

            • 3. Re: Linux Machine to Domain
              daphnissov Champion
              Community WarriorsvExpert

              This would join both Linux and Windows to a Domain allowing Red Hat user to log with there AD user and password.

              It will join any machines present in this blueprint, be they Windows or Linux. There are many other ways to customize on what blueprints/machines this runs, but this is the simplest.

               

              I was looking at installing Ansible on the Red hat machine and playing a join.yml script and calling that during creation from Software components and removing both Ansible and that playbook once finished.

              That is a ton of unnecessary work. This module does not depend on anything inside the guest to have AD adds and removes work. You're giving yourself work here with this method that doesn't need to exist.

              • 4. Re: Linux Machine to Domain
                jsauter Novice

                easy if i own your product, but i don't so it's really a sales pitch question and u just happened to be there with an answer. right?

                • 5. Re: Linux Machine to Domain
                  jsauter Novice

                  easy if i own your product, but i don't so it's really a sales pitch question and u just happened to be there with an answer. right?

                  • 6. Re: Linux Machine to Domain
                    daphnissov Champion
                    Community WarriorsvExpert

                    Actually, no, that's not right. It's not *my* product, first of all. Second of all, OP asked what was the "simplest" way, and the answer in my opinion (and in the opinion of many) is to use the SovLabs module for that, which does cost money. If OP had asked what was "cheapest" then that would not have been a proposed solution.

                    • 7. Re: Linux Machine to Domain
                      shivkumar4 Novice

                      One of the trickiest aspects of getting Linux to play well with Windows is the Windows Domain. For the longest time this was a challenge most were simply not ready (or able) to handle.Where DOMAIN_NAME is the name of the Windows domain you want to join and USER is the user you authenticate with. You will be prompted for your user password and, upon successful authentication, you will have officially joined that domain! You should be able to do things like browse all machines on your network domain as well as connect to your Exchange server using Evolution!.