@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.
Hello, I am trying to follow along with this and kinda get the basics. Does anyone have more examples? Maybe something with a Foreach? Couple things I am looking at doing. Looking to be able to scan laptops and put them into a To Be Image Group. I would like to pull all the info into a SQL table to better run query from and link to other databases for running reports. Then from there I would either use a import-csv and for each what I wanted to change or outright state the Host ID and what I wanted to change.
Also how can I select all attributes that are applied to the host? Get-FogObject -type Object -CoreObject host | Select-Object * does not give me all attributes to the host but this will give me Get-FogObject -type Object -CoreObject host | Select-Object id,name,primac
Can you guys try this. I am out until Monday.
@Wayne-Workman Updating to latest version resolved this issue. Thank you
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.
@joe-schmitt All we need is for FOGService to do its thing. So if that is not needed for it then I will remove it.
@sebastian-roth I guess, we keep seeing it spike but we are going to switch from Ubuntu to Centros and then upgrade FOG to 1.5.0 in the next few weeks.
Now this is a dirty way to do it as I don’t have the MYSQL skills or database background. What you can do it go to reports and run an inventory report. Export that. Now cant the column that has the hostname and change it to what you want. Find and replace or just trim your hostname down to asset tag them add whatever your naming convention is. So now you have a new column of hostname and the MAC address that was exported from inventory report. Follow the format for CSV upload here https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Hosts
Now under the 4th column add “Description” name this something like import and the date. This will be used to group the hosts you just imported. Go into FOG add whatever hosts you want to change to a group. Delete that group and check and delete hosts. NOTE this will remove all history assigned images settings and login history (Hence Dirty Way) Now import the hosts you want back in. After you successfully import your assets back in go to the hosts tab and search the description you added on import. Select all those hosts and add them to a group to apply all the new settings to. Once you add service settings and AD info they will start renaming your computers and depending on your settings may or may not reboot the computer.
I uploaded it again and I didn’t do anything different and it worked. Could it be something with FOG running into issues capturing? I saw in update notes that there has been some error checking added. Is that possibly the issue?
Destination Disk is 128GB SSD capture VM is 250GB.
Image is Single Disk - Resizable
I did test a MS Tools convert as I tried to convert my current image to UEFI to save time but got the same error. Then I made a brand new image UEFI image and captured it and got the error above. Then captured ita again and it worked. Then captured again and got the error. Its just not consistent.
CentOS Linux 7.7.1908
FOG 1.5.6
Sorry to make another post about this but I did not see resolutions from the other ones. We just got new devices in Optiplex 3070 that cant legacy boot Windows anymore so we have to create a UEFI image. While trying to do this I am getting Error trying to restore GPT partition tables. Exit returned code 4.
How do I fix this issue or what am I doing wrong? Note, my virtual machine HD is 250GB but the image is only 23GBish. (I have the larger HD as I use this base image to create other images that are much larger) I did this for my MBR image and that was just fine only the GPT UEFI image is giving me grief.
Also I cant get VMware Workstation to upload via UEFI so I have to change it to BIOS and PXE boot it in legacy mode to capture image.
I am going to assume I have to upgrade FOG?
@Tom-Elliott @george1421 I have someone from Zen support looking at it now. But I am going to assume they find the same issue and tell me to deal with it but we will see. Is there a way to run a .exe then keep going with the .bat? If I can do that then I can make this work.
@Tom-Elliott The log part never worked. I dont think you can make your own log location by the looks of it. I agree with -U it is not needed. The issue I think I have now is 1 the installer is not listening to the augments and 2 because its not listening to augments to goes ahead and reboots before finishing the .bat script and doesnt tell FOG it done.
@george1421 Sorry for long response time. So here is what happens. Run the cmd manually it will run and install but still ask for reboot thus I cant get the echo Exit Code is %errorlevel%. Run the came cmd with FOG it force reboots but doesn’t tell FOG it completed thus it loops installing over and over.
@george1421 Its this. Even when running quietly it still pops this up.
@Sebastian-Roth Its Zenworks 17.4 Agent Updater. Its custom to our environment so not expecting others to have it. I just have never had a plain .exe run and FOG not record it as complete.
Usage: ZenAgentUpdater.x64.17.4.exe <options>
BUILDTIME <options> are:
-f <file> = add <file> to extractor
-o <outf> = create extractor named <outf>
(default is wrapped.exe)
RUNTIME <options> are:
-l = list contents only (do not extract)
-n = no command execution (extract only)
-x = suppress reboot command passed to ZENPreAgent(Manual Reboot)
-q = show no reboot prompt(quiet install)
-m = have a rebootless agent with limited agent if opting for silent install(-q)
-Z = log ZESM setup.exe installation
-U = force uninstall previous ZENworks Desktop Management agent
-k <registration key> = register with the specified registration key after install
-c <file> = custom standalone install file
-d <dest> = extract files to <dest>
(default is C:\Windows\novell\zenworks\stage\)
-A <file> = read arguments from file
-b <component> = block installation of component."component" can be a single component or a comma separated list of ZENworks components
Supported component names:fde,zesm,asset,policies,bundles,patch,users,imaging
-K <flags> = pass flags to install drivers for component."component" flags need to be passed for ZESM,FDE,FLA,ASD in the given order.Pass 1 to enable drivers and 0 to disable driver installation for the corresponding component
For example passing 1110 meaning install drivers for ZESM,ZFDE and FLA but skip driver installation for ASD.
OTHER <options> are:
-v = be verbose
-h = help (show this message)
hit any key to continue
The install is finishing. I might try the quite switch. But if I just do it with a script FOG completes the task once the script runs I believe. The only issue then is it will keep trying to delete the .exe as it thinks its done but it will be locked.