Thanks, that what I was wondering.

@Tom-Elliott Oh, I somehow missed that. Nevermind then. -y does it all.

@Olduser said in Windows 7 64 bits image:

Again I like to thank all of you for doing wonderful work.

so true 😉

Also all FOG snapins are completely unattended. So are FOG Printers.

Sweet! That’s all I needed. Thanks for the info and the quick response!

@Wayne-Workman OMG no 🙂 but i could be some… I know that old discussions… it’s an image solution. I only share what my crank mind is dreaming about 😉

Regards X23

Applause 🙂

George is right. The devs have made strides in supporting upgraded systems where all sorts of things are off/wonky due to migration not being perfect. That said, most people fail at this process because it’s perhaps beyond their skill level to fix, and when they ask for help on the forums, we have to start from zero with troubleshooting because it could be anything if it’s not obvious, and there have been a lot that haven’t been obvious fixes. I’d always recommend a clean build as George said.

Forum maintenance moving to General Topics / General

@x23piracy said in FOG 1.3 and old clients:

@plegrand said in FOG 1.3 and old clients:

@Joe-Schmitt
Thanks for your answer.
But yesterday it didn’t works even i reset encryption data. I had to install manually the new client version

can we see a client log from a non updating client please?

I had the same issue, reset encryption but it client did not auto update. My fix was the GPO to install the new client as mentioned earlier.

I got an authentication error on the log.

Was just looking to see if i uploaded an error log on my old posts

Many thanks, and appologies as I was away from the forum for a week. I will try your suggestion and update the results here.

@Tom-Elliott
Thanks - looks like that might work, as the interface name shows up on the graph now. I won’t know until I do some fogging. Thanks!

https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_FTP

@george1421 +1 for a wiki page. This is really useful stuff and I only found out about it when coming onto the forums and talking with George. Without the forums, I wouldn’t have ever found this out/get it working.

Just returning here to let everyone know that, I don’t fail due to it, but the messages will report as Fail/Done depending on the status for the removal bits and pieces.

@cnkpadobi said in Issues Deploying an Image:

Should I upgrade also the latest Ubutu 16.04

No, I wouldn’t. Unless you have nothing to loose.

I recommend that new server builds - if you’re going to use Ubuntu - use the latest LTS version which is 16.04.

But, FOG 1.3.0 Release Candidate will run on Ubuntu 14.04.

@cnkpadobi If this thread’s original problem is solved, please create a new thread.

@Wayne-Workman

Thanku so much… I will follow these steps and it and it is very helpful thanks for your support… i will let you know if i stuck some where.

Regards,
MOhit

@Wayne-Workman said in To SysPrep or Not, That is the Question.:

I don’t sysprep and I have heavily used KMS at work. I got around the threshold issue by using a “charger” program that I found online, this application just sends a bunch of fake requests to the KMS box until the threshold is reached. Then all computers in the environment happily activate without issue

In any case, this is definitely not the right way to do this.

If you’re not going to Sysprep and you are using KMS, you should be re-arming your Windows and Office installation immediately before capturing the image:

–Windows: slmgr -rearm
–Office: %OfficeProgramDirectory%\ospprearm.exe

I’ve don’t remember of anyone trying… And I’ve been around here for about 2 years.