@FlareImp Sorry for giving you an incomplete answer before. I thought you revered and installed 1.2.0 which would upgrade to RC15 without issue. There would be no need to drop the database in this case.

I’m glad you have it all sorted out. The 1.3.0RC series is so much better than 1.2.0. You will be glad you are on this release.

@Tom-Elliott Yeah, I thought it would come down to naming the snapins appropriately. In our case, I think most like to know what they’re signing up for. As such, I’ll just create a document for them to follow and then answer any questions that do come up from it.

Thanks for the help and assistance!

@Matthieu-Jacquart My thought was to take two spare computers aside, install FOG on one with DHCP too, then take it off-network with your spare switch. And we just work on adjusting the switch configuration until we get multicast working to the other computer.

The RC-15 works now for me when trying to import hosts. I am seeing the same issue as posted here though.

In any case my submitted issue will be resolved in the RC-15 release.

Thank you all for the assistance.

Ok I didn’t understand this that way.
Ok I’ll try it just to see if it works.
Thanks again George ; )

@bastienbalaud RC 15 hasn’t been released yet, so are you running the “working-RC-15” branch? Images being associated is not the same as the image “existing” on the node or nodes within your environment.

I use a slightly alternative method personally, where I run the powershell command from a batch script, which requires a slightly different approach.

Example:

powershell -Command "& {Set-ExecutionPolicy RemoteSigned; Import-Module PSWindowsUpdate; Get-WUInstall}"

@Tom-Elliott
Ok thanks

@Tom-Elliott
Hello,
Fog configuration page:
text alternatif
Fog general settings:
text alternatif
FOG services logs:
text alternatif
servicemaster.log:

[09-14-16 2:23:45 pm] FOGMulticastManager Start [09-14-16 2:23:45 pm] FOGMulticastManager forked child process (18686). [09-14-16 2:23:45 pm] FOGMulticastManager child process (18686) is running. [09-14-16 2:23:47 pm] FOGImageReplicator Start [09-14-16 2:23:47 pm] FOGImageReplicator forked child process (18735). [09-14-16 2:23:47 pm] FOGImageReplicator child process (18735) is running. [09-14-16 2:23:50 pm] FOGImageReplicator Start [09-14-16 2:23:50 pm] FOGImageReplicator forked child process (19050). [09-14-16 2:23:50 pm] FOGImageReplicator child process (19050) is running. [09-14-16 2:23:55 pm] FOGPingHosts Start [09-14-16 2:23:55 pm] FOGPingHosts forked child process (19218). [09-14-16 2:23:55 pm] FOGTaskScheduler Start [09-14-16 2:23:55 pm] FOGTaskScheduler forked child process (19219). [09-14-16 2:23:55 pm] FOGTaskScheduler child process (19219) is running. [09-14-16 2:23:55 pm] FOGPingHosts child process (19218) is running. [09-14-16 2:33:55 pm] FOGTaskScheduler child process (19219) exited with code 255. [09-14-16 2:38:55 pm] FOGTaskScheduler forked child process (21217). [09-14-16 2:38:55 pm] FOGTaskScheduler child process (21217) is running. [09-29-16 12:34:55 pm] Service_Signal_handler (18733) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (18733) killing child (18735). [09-29-16 12:34:55 pm] Service_Signal_handler (18733) exiting. [09-29-16 12:34:55 pm] Service_Signal_handler (18685) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (18685) killing child (18686). [09-29-16 12:34:55 pm] Service_Signal_handler (18685) exiting. [09-29-16 12:34:55 pm] Service_Signal_handler (19199) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (19199) killing child (19218). [09-29-16 12:34:55 pm] Service_Signal_handler (19199) exiting. [09-29-16 12:34:55 pm] Service_Signal_handler (19147) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (19147) killing child (21217). [09-29-16 12:34:55 pm] Service_Signal_handler (19147) exiting. [09-29-16 12:34:55 pm] Service_Signal_handler (18828) received signal 15. [09-29-16 12:34:55 pm] Service_Signal_handler (18828) killing child (19050). [09-29-16 12:34:55 pm] Service_Signal_handler (18828) exiting. [09-29-16 12:35:17 pm] FOGTaskScheduler Start [09-29-16 12:35:17 pm] FOGTaskScheduler forked child process (1718). [09-29-16 12:35:17 pm] FOGTaskScheduler child process (1718) is running. [09-29-16 12:35:17 pm] FOGImageReplicator Start [09-29-16 12:35:17 pm] FOGImageReplicator forked child process (1719). [09-29-16 12:35:17 pm] FOGImageReplicator child process (1719) is running. [09-29-16 12:35:17 pm] FOGMulticastManager Start [09-29-16 12:35:17 pm] FOGMulticastManager forked child process (1720). [09-29-16 12:35:17 pm] FOGMulticastManager child process (1720) is running. [09-29-16 12:35:17 pm] FOGImageReplicator Start [09-29-16 12:35:17 pm] FOGImageReplicator forked child process (1721). [09-29-16 12:35:17 pm] FOGImageReplicator child process (1721) is running. [09-29-16 12:35:18 pm] FOGPingHosts Start [09-29-16 12:35:18 pm] FOGPingHosts forked child process (2195). [09-29-16 12:35:18 pm] FOGPingHosts child process (2195) is running. [09-29-16 12:45:18 pm] FOGTaskScheduler child process (1718) exited with code 255. [09-29-16 12:50:18 pm] FOGTaskScheduler forked child process (5825). [09-29-16 12:50:18 pm] FOGTaskScheduler child process (5825) is running. [09-30-16 12:13:29 pm] Service_Signal_handler (1558) received signal 15. [09-30-16 12:13:29 pm] Service_Signal_handler (1558) killing child (1720). [09-30-16 12:13:29 pm] Service_Signal_handler (1558) exiting. [09-30-16 12:13:31 pm] Service_Signal_handler (1512) received signal 15. [09-30-16 12:13:31 pm] Service_Signal_handler (1512) killing child (1721). [09-30-16 12:13:31 pm] Service_Signal_handler (1512) exiting. [09-30-16 12:13:34 pm] Service_Signal_handler (1535) received signal 15. [09-30-16 12:13:34 pm] Service_Signal_handler (1535) killing child (1719). [09-30-16 12:13:34 pm] Service_Signal_handler (1535) exiting. [09-30-16 12:13:36 pm] Service_Signal_handler (1487) received signal 15. [09-30-16 12:13:36 pm] Service_Signal_handler (1487) killing child (5825). [09-30-16 12:13:36 pm] Service_Signal_handler (1487) exiting. [09-30-16 12:13:38 pm] Service_Signal_handler (1951) received signal 15. [09-30-16 12:13:38 pm] Service_Signal_handler (1951) killing child (2195). [09-30-16 12:13:38 pm] Service_Signal_handler (1951) exiting.

There is a problem, I have no more logs, look at the dates, it seems that since the 1.2 to 1.3 update FOG write nothing.

And I have a issue with all FOG services:
text alternatif

@Joe-Schmitt said in Fog Upgraded to 1.3.0 RC 11 - Snapins not deploying - 'Newtonsoft.Json.Linq.JObject'.:

@Duncan could you please perform the following steps:

Stop the fog service on this machine (net stop fogservice) Download https://github.com/FOGProject/fog-client/releases/download/0.11.5/Debugger.exe to this machine Go to your FOG Server’s web portal, pull up this host and hit Reset Encryption Data Run Debugger.exe Type middleware configuration server http://FOG-SERVER/fog (replace FOG-SERVER with your server’s IP) Type middleware authentication handshake Type dump cycle save

It will generate FOGCycle.txt in the same directory as Debugger.exe. Please open up this file, remove your active directory account information (your ad password will be in plain text), and then upload that file here. Once done, go to the host in the FOG web server again and hit Reset Encryption Data once more. You can then start the service back up.

This is #wiki worthy for the FOG Client article - for troubleshooting.

@BStalker That version of fog is very old. You should move off of the unstable trunk version to the latest release candidate. Instructions are here: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

@fpsacha After upgrading to RC-14; once I defined the master node (the fog server itself) and made sure all passwords were the same, the process has run seamlessly.

@ek_N said in Update Version: 1.3.0-RC-14, Can't capture image from Virtualbox.:

i guess it might take some time before it applies.

No, changes in Windows DHCP are immediate.

@dcorpening You would probably be best off upgrading to FOG Trunk. It would also be helpful if you could post a short video of the boot process so we can see it, or a series of pictures of the last thing the computer is saying before exiting to the local Windows.

@Tom-Elliott I just shared the file with you.

George : no proxy is used.
Wayne : GREAT ! It’s working. Thanks a lot ! and indeed it was 1.3.0

Philippe

The bug is now fixed in working-RC-15 branch.

@Sozen Please move to FOG 1.3.0 RC, you can find instructions here: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk

10-4. Thanks for the info, the link, and the quick response! I’ll mark this as solved. Thanks again!

It exports the definitions (the pointers) as a image_export.csv (Comma Separated Value) text file.

This file can be edited!

If after exporting your complete list of images from one server, you want to then import just one of those images to another server you edit the original exported .csv . I use Microsoft Excel.

Delete the lines for the images you are not interested in, then save that new .csv .

On the destination server you then import the updated .csv. The contents of which are then merged into that server’s database.

One of the nicer bits about the exported .csv is that the creation date and image size are saved and imported along with all the other pertinent fields. Do not worry about the image ID #, that is not saved or imported.

Of course you will still need to copy the actual image files referenced by the image definition onto the destination server.