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

Sysprep on Win 8.1

Scheduled Pinned Locked Moved
Windows Problems
4
7
2.6k
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.
  • S
    skotteru
    last edited by Jul 30, 2015, 6:30 PM

    Hey All,

    Is sysprep absolutely necessary on a windows 8.1 image if it is being deployed to identical hardware?

    Thanks
    Scott

    1 Reply Last reply Reply Quote 0
    • W
      Wolfbane8653 Developer
      last edited by Wolfbane8653 Jul 30, 2015, 1:29 PM Jul 30, 2015, 7:28 PM

      Touchy subject…sysprep should be used at least for your licensing. As for drivers and hardware compatibility sysprep is not needed for identical hardware BUT make sure the host is not connected to your AD before uploading.

      FYI wifi profiles are not carried across on windows. Use xml files for this.

      1 Reply Last reply Reply Quote 0
      • S
        skotteru
        last edited by Jul 30, 2015, 7:32 PM

        We are running a KMS server so the License is just the generic KMS one… That should skirt the licesing issue, correct?

        Not hooked up to AD, using FOG for this, and even though we have Wifi… we like gig connection 😄

        Thanks for the reply @Wolfbane8653!

        1 Reply Last reply Reply Quote 0
        • S
          sudburr
          last edited by sudburr Jul 30, 2015, 1:41 PM Jul 30, 2015, 7:41 PM

          There are lots of Google opinions on this.

          It’s there for more than one reason.

          The easy answer is Microsoft’s; yes, sysprep.

          Emphasized YES if you’re using AD.

          [ Standing in between extinction in the cold and explosive radiating growth ]

          W 1 Reply Last reply Jul 30, 2015, 10:21 PM Reply Quote 0
          • W
            Wayne Workman @sudburr
            last edited by Wayne Workman Jul 30, 2015, 4:23 PM Jul 30, 2015, 10:21 PM

            @skotteru I use Active Directory and I deployed a whole lot of Win8.1 machines recently and I don’t sysprep. I maintain one image for each model of PC in my building - this is to keep my images lean and mean and fast - fast to deploy - fast to boot. (5 minute deployment time for 40GB image).

            You upload when the client is not on the domain, and use the fog client (Legacy and New works on 8.1) to join the domain after imaging.

            But you will find lots of mixed opinions on how to do it.

            You know what I say, now? Do what floats your boat, I don’t care lol. I’m maintaining an image per model! 🙂

            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!
            Daily Clean Installation Results:
            https://fogtesting.fogproject.us/
            FOG Reporting:
            https://fog-external-reporting-results.fogproject.us/

            1 Reply Last reply Reply Quote 1
            • S
              sudburr
              last edited by Jul 31, 2015, 12:38 AM

              One issue that is bubbling up from the ether of my memory involves AD and computer account passwords. The computer account password is maintained by the computer on the AD and as part of that identifier it involves the unique ID that the system generated for the OS by coming out of sysprep.

              Once you’re comfortable with generating answer files for sysprep it’s really a non-issue, quite easy and worth employing.

              Here-say, but I know a story from another administrator that involved an administrator HE knew who deployed an entire headquartered office building without sysprepping the image, which caused nightmares for their software licensing.

              Microsoft created it for a reason.

              [ Standing in between extinction in the cold and explosive radiating growth ]

              W 1 Reply Last reply Jul 31, 2015, 12:52 AM Reply Quote 0
              • W
                Wayne Workman @sudburr
                last edited by Wayne Workman Jul 30, 2015, 6:56 PM Jul 31, 2015, 12:52 AM

                @sudburr We had a issue with licensing when I first started deploying machines at my job about two years ago.

                Most Microsoft product licensing requires a minimum number of unique requests before it allows product activation. So we simply generated a bunch of fake requests and then all was fine. We’ve used this method at four different locations, on probably about 3,000 windows systems - over and over again. And being a school district that has as diverse of software requirements are there are educational areas, we’ve never had a problem.

                But again, whatever floats you boat! 🙂

                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!
                Daily Clean Installation Results:
                https://fogtesting.fogproject.us/
                FOG Reporting:
                https://fog-external-reporting-results.fogproject.us/

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

                173

                Online

                12.1k

                Users

                17.3k

                Topics

                155.4k

                Posts
                Copyright © 2012-2024 FOG Project