Windows Fails to Install
-
@zpoling For a test, you could try to remove the file before sysprep and capture and see if that resolves the problem.
-
@Quazz I’m sorry, do you mean remove the unattend file and upload the image without syspreping?
-
@zpoling You can sysprep, just with the unattend file removed.
-
@zpoling I think I ran into the same problem:
As I move fog to a new server I took the chance to upgrade Fog from 1.2 to trunk.With Fogserver 1.2 I used to install the legacy fog client in the image which worked without problems.
The new fog client, at least v0.10.6 seams to break windows setup. Uninstalling the client in the image solved the problem with the windows setup for me.
-
@michael_f said in Windows Fails to Install:
The new fog client, at least v0.10.6 seams to break windows setup. Uninstalling the client in the image solved the problem with the windows setup for me.
Ah. We’ve seen this before. The answer is to disable the FOG Service before you take the image, and then in your unattend.xml file re-enable the service after the unattend file is done with everything else.
-
Hi there!
I’m beeen searching for a sollution since 04/05/2016!
Didn’t find any solution & now you guys got the same problem as me!
I also think it is the FOG client. I prepped more images , and after the install from deepfreeze / fog client i get this error to.Big big problem
Tomorrow is my last day of internship so i can’t image 
^^ -
How do you disable? Just in the “services”?
What line do you need to add in the XML - file to activate this?Crap! I’m searching for a week behind this error and its FOG client grrrr
-
Yes, just disable it in service before taking the image.
Here’s a post that shows how, This particular person was experiencing a particular problem in this post, but these issues have since been resolved in the current FOG Client. What he says about enabling the service is still valid.
@boeleke @Psycholiquid said in Rename fails but adds client to domain.:
Ok using SVN 3702 with Client 0.9.0 I am getting the following happening:
I create the image in Audit mode
Install all software and updates Install FOG Service software 0.9.0In the SetupComplete.bat I have the following commands
sc config FOGService start= auto
net start FOGServiceSet windows to OOBE and reboot uploading image to FOG server.
Once complete I push the image out to one of the hosts I have setup in FOG right now. IT runs through the whole image setup and completes to the Desktop.
From there is joins the domain without trying to rename the computer at all. This create a problem as there will be multiple computers all trying to join the domain under the same name causing a trust issue in the process.
Here is the log from the computer I just did. Keep in mind this one is constantly rebooting due to it trying to change the name after it has already joined the domain:
Source: https://forums.fogproject.org/topic/5490/rename-fails-but-adds-client-to-domain/27
-
@Wayne-Workman said in Windows Fails to Install:
sc config FOGService start= auto
net start FOGServiceSooo only this 2 lines :
“sc config FOGService start= auto
net start FOGService”in my setupcomplete.cmd and it will work?
Oh my!Is it possible to remove this bug from the installer?
Its weird because the old V0.9 fog didn’t gave any problems to me -
@boeleke All I can say is try it and see.
To explain the problem in more detail, when your sysprep stuff is happening after deployment, the fog client starts up and does it’s thing too (rename, reboot, etc.), and breaks the unattend.xml and setup complete stuff. The simple answer is just to disable the service before taking the image, and set up your golden machine so that it re-enables the service after all your stuff is done.
Also - it’s not a bug. The FOG Client is designed to do it’s job.
-
@Wayne-Workman said in Windows Fails to Install:
@boeleke All I can say is try it and see.
To explain the problem in more detail, when your sysprep stuff is happening after deployment, the fog client starts up and does it’s thing too (rename, reboot, etc.), and breaks the unattend.xml and setup complete stuff. The simple answer is just to disable the service before taking the image, and set up your golden machine so that it re-enables the service after all your stuff is done.
Also - it’s not a bug. The FOG Client is designed to do it’s job.
But maybe a tip , put it in the wiki.
i searched like i was crazy last week to all forums. But maybe i’m wrong , i’m just going to try it out. I’ll update this tomorrow when i can test! Thanks! -
@Wayne-Workman OK, I thought about installing the fog client after imaging by calling the msi-package from setupcomplete.bat, but this way is even easier.
I can confirm this working for me.
Thank you!
-
I can confirm its also working for me :).
But if I was you guys , i would put this on the FOG-WIKI. @DevelopersThis is going to be a problem for many of us & maybe they stop earlier with FOG because that and the don’t know it
But thumbs up for the good work ;)! -
@boeleke @michael_f Ask and you shall receive.
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep -
Hi,
do you try to restore to vm? i’ve seen several error for example with virtual box when trying to restore an earlier captures sysprepped image.
If yes try the same image on real pyhsical hardware please.Regards X23
-
@Wayne-Workman This fixed my original issue as well. Thanks for the help!
-
TO clarify, are you guys putting this in setupcomplete
.cmdor setupcomplete.bat?I’ve not done this myself yet, so I’m just going off of what you all say.
-
@Wayne-Workman I had to look up where to put the script in the first place, and was instructed to use SetupComplete.cmd; that is what worked for me.
-
@zpoling Care to provide a screen shot or some steps?
-
@Wayne-Workman setupcomlete.cmd has to be placed under C:\Windows\Setup\scripts in the master system.
As the name indicates, the script is called by windows just after setup has finished.Btw. l set the Fog service to delayed start, ie I put
sc config FOGService start= delayed-auto
into the script.
I don’t know, if this is really necessary with the new fogclient, but it doesn’t harm.
Reason for this is i’ve got some computers which require delayed start with the legacy client (afair network doesn’t come up fast enough)
