Posts made by UWPVIOLATOR

@joe-schmitt How can I check? Are you saying that after the snapin runs (which takes a few min) that FOG is trying to delete the snapin but cant because its still in use?

@sebastian-roth Yes everything else works and this snapin did install but it never tells FOG so the task never clears and then the next time the client does a check in it will try to install all over again.

FOG 1.4.4
Ubuntu 16.04

This has been an issue for awhile. After a snapin deploys and installs as part of the imaging process. You can see in the logs as the snapin finishes then it reboots. After the reboot it then tries to do the snapin all over again. It does appear to only be this 1 snapin. Zenworks Agent. It worked just fine for us for a long time but seems like 1.4.4 did something to it. Suggestions?

 2/12/2018 11:46 AM SnapinClient C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe
 2/12/2018 11:46 AM Bus Emmiting message on channel: Notification
 2/12/2018 11:46 AM SnapinClient Starting snapin
 2/12/2018 11:47 AM SnapinClient Snapin finished
 2/12/2018 11:47 AM SnapinClient Return Code: 0
 2/12/2018 11:47 AM Bus Emmiting message on channel: Notification
 2/12/2018 11:47 AM Service ERROR: Unable to run module
 2/12/2018 11:47 AM Service ERROR: The process cannot access the file 'C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe' because it is being used by another process.

After Reboot tries to install again

------------------------------------------------------------------------------
---------------------------------SnapinClient---------------------------------
------------------------------------------------------------------------------
 2/12/2018 11:51 AM Client-Info Client Version: 0.11.12
 2/12/2018 11:51 AM Client-Info Client OS:      Windows
 2/12/2018 11:51 AM Client-Info Server Version: 1.4.4
 2/12/2018 11:51 AM Middleware::Response Success
 2/12/2018 11:51 AM SnapinClient Running snapin ZenAgent 11.4.3 x64
 2/12/2018 11:51 AM Middleware::Communication Download: http://fogserver/fog/service/snapins.file.php?mac=10:60:4B:75:37:98&taskid=151804
 2/12/2018 11:52 AM SnapinClient C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe
 2/12/2018 11:52 AM Bus Emmiting message on channel: Notification
 2/12/2018 11:52 AM SnapinClient Starting snapin
 2/12/2018 11:53 AM SnapinClient Snapin finished
 2/12/2018 11:53 AM SnapinClient Return Code: 0
 2/12/2018 11:53 AM Bus Emmiting message on channel: Notification
 2/12/2018 11:53 AM Service ERROR: Unable to run module
 2/12/2018 11:53 AM Service ERROR: The process cannot access the file 'C:\Program Files (x86)\FOG\tmp\ZenAgent.64.Complete.11.4.3.exe' because it is being used by another process.

@wayne-workman as in RC12? Ok I have another Issue I will be posted but testing again to make sure I can replicate it before posting. Its with Snapins not reporting they are finished and then keep trying to run over and over again. Windows 10 and Windows 7.

Trying to avoid updating to RC and waiting for next stable but if its fixed in an RC we might have to go for it.

FOG 1.4.4
Ubuntu 16.04

This has been an issue for awhile. When creating new groups by searching Host and using checkbox to select. FOG is adding in all the latest registered devices into the group regardless if you checked them or not. If you go to the group then Membership and add from there works.

@joe-schmitt Thank you. Question we are still on 1.4.4 can I use the new client with that or do we need to update the server?

@uwpviolator said in Client 0.11.12, Windows 10 1709 - Reboot fails:

@joe-schmitt First try it broke Windows. Cant event get past setup.

I did not remove the old client before installing this one. After I removed it then installed the new one it appears to work.

@joe-schmitt First try it broke Windows. Cant event get past setup.

@joe-schmitt I installed your nightly client build. It does not work and I can not even start the service. Gives me this error.

@Joe-Schmitt Another thing I am seeing is on 2 different models. HP Elitebook 840 G1 and a HP Elitedesk 8300. The 840 will start the fog service, name and join domain but not do the final reboot. The 8300 doesn’t start FOG. Setupcomplete.cmd worked as the FOG service is set to Automatic but again its a reboot to start up.

@Joe-Schmitt Same power error. It looks like it named and joined the domain but it did not reboot that final time. The registry settings are still there so that should of worked.

@joe-schmitt So I tired to run the KB and it doesn’t really run or show it ran but no error. I did do the registry edit and am testing now. But we are not using copyprofile because of the other issues, so hopefully the settings stick.

I am having the a similar issue. Windows 10 EDU 1709. FOG 1.4.4

@bob-henderson I have done this with 1709 and it worked just fine. Review your unattended file or create a test one with just the driver location changed to C:\drivers.

Is everything else working in your unattended file or working at all? Are you actually calling Sysprep to use your unattended file?

@george1421 @Bob-Henderson

George, I think Bob is skipping over the editing of the FOG Scripts. Bob, if you have made the changes to unattended that still does nothing to tell FOG to drop your driver folder into C:\Drivers. See the following reply.

@george1421 said in Windows 10 Drivers Not Copying:

@uwpviolator Well then, I think you might want to change up your fog.drivers script a bit. Right now its working fine for win7 but not win10. So in the first script you posted modify this section of code.

#############################################
dots "Preparing Drivers"
# below creates local folder on imaged pc
# this can be anywhere you want just remember
# to make sure it matches throughout! (case IS important here)
clientdriverpath="/ntfs/Windows/inf/Drivers"
remotedriverpath="/images/drivers/$machine/$osn/$arch"

to this

#############################################
dots "Preparing Drivers"
# below creates local folder on imaged pc
# this can be anywhere you want just remember
# to make sure it matches throughout! (case IS important here)
if [ $osid -eq 9 ]
then
    clientdriverpath="/ntfs/Drivers"
else
    clientdriverpath="/ntfs/Windows/inf/Drivers"
fi
remotedriverpath="/images/drivers/$machine/$osn/$arch"

You might ask, so what will that do for you? The patch tests to see what OS you are deploying. If the OSID==9 then you are deploying a win10 image. In that case it will copy the drivers to C:\Drivers, all other OS’ the drivers will be copied to C:\Windows\Inf\Drivers.

Then in your unattend.xml file, tell oobe to look in c:\Drivers for its files.

@Tom-Elliott @george1421 you guys can make this as resolved. Thanks

@george1421 @Tom-Elliott

Yes, I have tested and adding the lines of code fixed it. It now dropps the files to C:/Drivers which is not wiped out. Now I need to update unattend file to reflect this change.

#############################################
dots "Preparing Drivers"
# below creates local folder on imaged pc
# this can be anywhere you want just remember
# to make sure it matches throughout! (case IS important here)
if [ $osid -eq 9 ]
then
    clientdriverpath="/ntfs/Drivers"
else
    clientdriverpath="/ntfs/Windows/inf/Drivers"
fi
remotedriverpath="/images/drivers/$machine/$osn/$arch"```

@tom-elliott

Fog Node
/images/drivers/model name/win7/x64
/images/drivers/model name/win10/x64

Fog.drivers
Copies folder to c:/windows/inf/drivers

Works for Win 7. Not for Win 10

Run debug, stop after driver copy. cd to c:/windows/inf/drivers. x64 is there on the HD. When rebooting and going through sysprep is where it seems to be removing that folder. Thought it might be unattended file but just did it with no unattended and still nothing.

So I will make the changes but this might just be something with Win 10 1709?

@george1421

So doing this will not affect Win 7 as it will only copy to C:/drivers if Win 10 correct?

@george1421 @Tom-Elliott

Uploaded fresh image no unattended file. Still no files on HD. See my last reply. Which one do I replace in my fog.drivers file?