• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    SSID issue after deployment

    Scheduled Pinned Locked Moved
    General Problems
    4
    7
    724
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • C
      Corentin
      last edited by

      Hi ! After I deployed images on computer, I realized that the SSID of the copied image were the same on all deployed workstations so when I try to integrate these worksations in a domain it makes conflicts between all workstations. Is there a way to change SSID for each workstations ?
      I work on Windows 10 and on FOG 1.5.9
      Sorry for my english.

      george1421G Matthieu JacquartM 2 Replies Last reply Reply Quote 0
      • george1421G
        george1421 Moderator @Corentin
        last edited by

        @corentin Yes sysprep the image before capture. This is not specifically a FOG problem, but a windows system preparation step that is missing. If you don’t use sysprep then every cloned image with have the same system ID.

        Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

        1 Reply Last reply Reply Quote 0
        • Matthieu JacquartM
          Matthieu Jacquart @Corentin
          last edited by

          @corentin Bonjour Corentin, je suppose que tu es français ^^
          Effectivement il faut toujours faire un sysprep avant de remonter l’image, ça permet de générer un nouvel SSID pour les postes déployés. Si besoin d’aide je te laisse m’envoyer un message privé avec ton adresse mail pour qu’on puisse échanger plus facilement 😉
          Matthieu

          Fog 1.5.9.138
          Debian 11
          Vmware ESXi

          B 1 Reply Last reply Reply Quote 1
          • C
            Corentin
            last edited by

            Merci @Matthieu-Jacquart ! En effet je suis français, je vais t’envoyer un message privé pour plus d’informations 🙂
            Thank you @george1421 !

            1 Reply Last reply Reply Quote 0
            • B
              Bristow 0 @Matthieu Jacquart
              last edited by

              @matthieu-jacquart

              Je suis aussi preneur de documentation par rapport à cela et notamment sysprep.

              Autre solution, cloner le poste sorti du domaine et l’intégrer à posteriori.

              Matthieu JacquartM 1 Reply Last reply Reply Quote 0
              • Matthieu JacquartM
                Matthieu Jacquart @Bristow 0
                last edited by

                @bristow-0 Je t’envoi un mp 😉
                Effectivement sortir le poste du domaine est une base, mais il me semble que le SSID de Windows reste le même et donc cela peut être bloquant dans le cadre d’un serveur WSUS ou de clé KMS (tous les postes ne seraient vu que comme un seul). J’ai des collègues qui n’ont pas de WSUS ni KMS et donc ils sortent juste le poste du domaine avant de capturer l’image.
                Matthieu

                Fog 1.5.9.138
                Debian 11
                Vmware ESXi

                george1421G 1 Reply Last reply Reply Quote 0
                • george1421G
                  george1421 Moderator @Matthieu Jacquart
                  last edited by

                  @matthieu-jacquart Sorry I can only write in english.

                  Its best if you DO NOT connect your mother/master image to active directory before you capture the image. I’m sure my environment is different than you, but we use MDT to create the golden image, sysprep then capture with FOG. At no time is the golden image connected to AD before capture with FOG. The first time the target computer image is connected to AD is on the final hardware.

                  Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

                  1 Reply Last reply Reply Quote 1
                  • 1 / 1
                  • First post
                    Last post

                  153

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project