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

    Word - temp environmental variable

    Scheduled Pinned Locked Moved Unsolved
    Windows Problems
    4
    21
    9.3k
    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.
    • george1421G
      george1421 Moderator @John Johnson
      last edited by

      @John-Johnson Again, I want to restate this is not a FOG issue.

      You are sysprepping it so that is fine/good.

      1. Are you using an unattend.xml file? If so, that is good.
      2. If you are using the unattend.xml file does it contain this line: <CopyProfile>true</CopyProfile> ??
      3. And when you fixed the reference image, were you logged in as the Administrator?

      If you answered no to any of the questions above, I understand how/why the fix is gone. Because when you sysprep the image all profiles are reset except the administrator’s account. When you have the copyprofile set to true then when you sysprep the image the Administrator’s account is copied to the default profile. And the default profile is the basis for all new users after imaging is complete.

      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!

      J 1 Reply Last reply Reply Quote 1
      • J
        John Johnson @george1421
        last edited by

        @george1421 I am using an unattend.xml file and the fix was done under administrator. Yes the line is in the sysprep file. Our file is called unattend64.xml to keep it separate from the 32 bit machines.

        george1421G 1 Reply Last reply Reply Quote 0
        • J
          John Johnson @Tom Elliott
          last edited by

          @Tom-Elliott I’m not blaming it on fog. I know it has something to do with the way this machine is handling Office but I can’t figure out what is different than any other machine I image.

          george1421G 1 Reply Last reply Reply Quote 0
          • george1421G
            george1421 Moderator @John Johnson
            last edited by

            @John-Johnson said in Word - temp environmental variable:

            @Tom-Elliott I’m not blaming it on fog. I know it has something to do with the way this machine is handling Office but I can’t figure out what is different than any other machine I image.

            No problem, just trying to make it clear to future readers of this thread where the problem is not.

            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
            • george1421G
              george1421 Moderator @John Johnson
              last edited by

              @John-Johnson said in Word - temp environmental variable:

              @george1421 I am using an unattend.xml file and the fix was done under administrator. Yes the line is in the sysprep file. Our file is called unattend64.xml to keep it separate from the 32 bit machines.

              Understood, we use a similar structure for the unattend.xml file. That is disappointing that this setting did not remain after sysprep. At this point I’m not sure what to look at next.

              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!

              J 1 Reply Last reply Reply Quote 0
              • J
                John Johnson @george1421
                last edited by

                @george1421 I am thinking that maybe this is a result of upgrading to the Anniversary update after installing Office. It has a way of changing things. So I am going to rebuild, do the Anniversary update and then install Office.

                george1421G 1 Reply Last reply Reply Quote 0
                • george1421G
                  george1421 Moderator @John Johnson
                  last edited by

                  @John-Johnson While I can’t speak for your process, we just completed the 1607 refresh of our golden image. We use MDT to go from DVD to our golden image (and not go the upgrade route). The image works properly in the test lab and we are about ready to release it for use.

                  I can tell you for Win10 CBB v1607 you MUST install the Sep 20 accumulative update or your systems will not get updated from WSUS (ever). There are documented bugs in 1607 (big time).

                  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
                  • J
                    John Johnson
                    last edited by

                    I was able to make an image successfully. Windows 10 is a different animal and you have to do things just right or it will fail.

                    Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                    • Wayne WorkmanW
                      Wayne Workman @John Johnson
                      last edited by

                      @John-Johnson What is it that you did? I’m asking for future readers.

                      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/

                      J 1 Reply Last reply Reply Quote 0
                      • J
                        John Johnson @Wayne Workman
                        last edited by

                        @Wayne-Workman said in Word - temp environmental variable:

                        @John-Johnson What is it that you did? I’m asking for future readers.

                        I kept it offline until I could get Administrator activated. Once logged into Administrator my user account was safe from Microsoft’s unwanted pushed apps.

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

                        207

                        Online

                        12.1k

                        Users

                        17.3k

                        Topics

                        155.4k

                        Posts
                        Copyright © 2012-2024 FOG Project