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

    Windows 8.1 Imaging Guide?

    Scheduled Pinned Locked Moved
    Windows Problems
    4
    7
    3.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.
    • B
      Bob Martens
      last edited by

      Does anyone have an overview of imaging Windows 8.1 machines in a higher ed environment?

      1 Reply Last reply Reply Quote 0
      • 2
        2cool4me4
        last edited by

        I’m assuming that you have your clients registered in the FOG database already. I am also assuming very basic knowledge of this process, sorry if I come off harsh.

        Coming from the same boat right now, I’ll be happy to help.

        The basic things you’ll need to do are:

        1. Install Windows 8.1 on your master machine. If you have proper Volume Licensing media, it won’t ask you for an activation key.

        2. Set up your Windows machine and perform updates. Try to perform as many as possible. This will increase your image size but will reduce network traffic.

        3. Now that that’s done, run sysprep /audit from an elevated command line. This may take a while. The system will reboot into Audit mode. You will be logged in as Administrator. Delete the user account you created while installing updates.

        4. Make your needed changes. This can include installing software, changing settings in Group Policy Editor (that’s important), and installing FOG Service (That’s the most important). Basically, make your image yours. Install large programs like Microsoft Office. I do not recommend installing software like Chrome, Java, or Flash at this point because they update quite often. Use Snapins for that. Also, do not install printers, use FOG for that.

        5. Run disk cleanup and delete everything. It can’t hurt, right?

        6. Since you’re sure that all those Windows updates haven’t broken anything by now, you can delete old versions of updates. Use the command

        [CODE]Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase[/CODE]

        as seen [URL=‘http://technet.microsoft.com/en-us/library/dn251565.aspx’]here[/URL]. Then defrag the system.

        1. TAKE A BACKUP IMAGE NOW!!!

        2. Now we’re getting down and dirty. You want to use unattended.xml files so that you won’t have to touch every machine you image. See [URL=‘http://technet.microsoft.com/en-us/library/cc749317(v=ws.10).aspx’]here[/URL] to get started. You will need the [URL=‘http://www.microsoft.com/en-us/download/details.aspx?id=39982’]Windows 8.1 ADK[/URL], but only the Deployment Tools part. You’ll also need a technician computer running Windows 8.1 to install the ADK on.

        3. With your new unattend.xml in hand, sysprep your machine. You can use the .bat file [URL=‘http://www.fogproject.org/wiki/index.php/Sysprep_for_Windows_7’]here[/URL] to help you with this process. You’ll need to rename your unattend.xml to unattend.noskiprearm.xml.

        4. Capture an image from your machine. Make sure that it doesn’t reboot after the imaging task.

        5. Apply this image to another machine. See if it completes Windows setup and goes to a login prompt. If yes, congrats! You imaged Windows 8.1! If not, there’s a problem with your unattend.xml. Go on…

        6. Hit something with a hammer.

        not really.

        Take your master machine to the backup image you created before and see what’s wrong with your unattend.xml. I’ll be happy to help with this.

        And that’s basically it. If anyone stumbles across this and sees that I’ve missed something, please tell me. 🙂

        Debian Jessie
        Intel Xeon 5130
        2GB RAM

        If you ever need it, you know…

        1 Reply Last reply Reply Quote 0
        • B
          Bob Martens
          last edited by

          Thanks. Looks like we have some work to do.

          1 Reply Last reply Reply Quote 0
          • 2
            2cool4me4
            last edited by

            Yes, you do. I’ve been learning how to do it as I go, so it’s been pretty slow. I hope that helps you out.

            Debian Jessie
            Intel Xeon 5130
            2GB RAM

            If you ever need it, you know…

            1 Reply Last reply Reply Quote 0
            • N
              need2 Moderator
              last edited by

              Excellent guide. Thanks for sharing this.

              1 Reply Last reply Reply Quote 0
              • 2
                2cool4me4
                last edited by

                Oh, since I’m guessing that you’re going to be setting up Office, I’ll tell you how to do that, too.

                1. Put your Office setup CD in the tray, if applicable

                2. Using Run or an elevated command line, run [Office Setup Location]\setup.exe /admin

                3. Customize your installation. I don’t know the options off the top of my head, but you’ll want to accept the EULA, put in your key (MAK or KMS can be set up), and set it to not install programs that you probably don’t need, like Exchange. Look through the rest of the options to see if you find anything else you’d like to set.

                4. Use File -> Save to get a Microsoft Office install file. Run this and you should be good to go.

                Debian Jessie
                Intel Xeon 5130
                2GB RAM

                If you ever need it, you know…

                1 Reply Last reply Reply Quote 0
                • x23piracyX
                  x23piracy
                  last edited by

                  Hi,

                  you can also integrate office updates into the installation,
                  download needed update files, extract them and place the msu file in the office updates folder:

                  [IMG]http://i.imgur.com/7WbPihg.png[/IMG]

                  To automate office installtion use config.xml

                  [CODE]<Configuration Product=“ProPlusr”>
                  <Display Level=“basic” CompletionNotice=“no” SuppressModal=“yes” AcceptEula=“yes” />
                  <USERNAME Value=“Bla” />
                  <COMPANYNAME Value=“Bla2” />
                  <!-- <INSTALLLOCATION Value=“%programfiles%\Microsoft Office” /> -->
                  <!-- <LIS CACHEACTION=“CacheOnly” /> -->
                  <!-- <LIS SOURCELIST=“\server1\share\Office;\server2\share\Office” /> -->
                  <!-- <DistributionPoint Location=“\server\share\Office” /> -->
                  <!-- <OptionState Id=“OptionID” State=“absent” Children=“force” /> -->
                  <!-- <Setting Id=“SETUP_REBOOT” Value=“IfNeeded” /> -->
                  <!-- <Command Path=“%windir%\system32\msiexec.exe” Args=“/i \server\share\my.msi” QuietArg=“/q” ChainPosition=“after” Execute=“install” /> -->
                  </Configuration>[/CODE]

                  It can happen that your office doesn’t have the admin folder then you cannot run setup.exe /admin,
                  then you will need to download adm templates for the desired office version, extract them and place
                  the admin folder in the office install folder, after that setup.exe /admin will work.

                  [IMG]http://i.imgur.com/3JO0yyD.png[/IMG]

                  [IMG]http://i.imgur.com/rQlRDnb.png[/IMG]

                  [url]http://www.microsoft.com/en-us/download/details.aspx?id=35554[/url]

                  [IMG]http://i.imgur.com/9lY72l2.png[/IMG]

                  Regards X23

                  ║▌║█║▌│║▌║▌█

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

                  257

                  Online

                  12.0k

                  Users

                  17.3k

                  Topics

                  155.2k

                  Posts
                  Copyright © 2012-2024 FOG Project