I would say this topic is solved and I appreciate the support.

@Arrowhead-IT This actually worked for me!

@george1421 This worked. Arrowhead IT suggested the same.

@george1421 said in Windows 10 sysprep error.:

@John-Johnson just for clarity the power shell script that ArrowHead-IT posted (same as what I posted only through the link) corrected your issue? You were able to update your win10 with all of the updates from the internet and you applied the adobe updates? I just want to ensure your workflow was the same and the only thing you changed was the powershell script.

Yes. I was able to lift my image to fog by using powershell as the user and removing the offending apps.

@george1421 I can fix this image and use it now. Thanks

@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.

I found out that the error was caused because the fog account was not recreated when we upgraded. All is well now except for name changing and getting them on the domain automatically. I think that is also a password issue.

I am trying to lift a Windows 10 image for a Dell Optiplex 3010 and get an error that says;

• Error returned: Type: 2, File: /var/www/fog/lib/fogftp.class.php, Line: 463, Message ftp_login(): Login incorrect., Host 10.254.164.13, Username: fog *Reattempting to update database…Failed

The image appears to lift okay but goes into a continuous loop with that error until I kill the job on the server.

I don’t know how to fix this.

This came across the screen but it continued to image…

See attached:

@Wayne-Workman Can you install over the top of the fog client or would you have to remove it.

I currently have 1.2.0

How do I get to this download?

@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.

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.

@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.

@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.

@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.