https://wiki.fogproject.org/wiki/index.php?title=Add_%26_Extend_a_2nd_Virtual_HDD

@anthonyglamis yes. There’s a article all about ftp. “Troubleshoot FTP” in the wiki.

@Mentaloid I tried messing with it for a while, it’s the tilde characters messing it up.

You can create a .txt file and upload that if you want.

@Developers this would be a good example of a “forums issues”.

@Sebastian-Roth absolutely no offense to the OP but I say this as sincere as I can be, I wish someone who knows what they are doing would make a tutorial on how to use virtualbox with fog. And I only ask because we keep seeing these problematic virtualbox threads over and over.

Not to change your mind at all, but is sysprep necessary?

To me it’s always been burdensome, I’ve been imaging with ghost and fog and other solutions for a while now, I’ve probably imaged well over 3,000 machines by now. I’ve never sys-prepped and I’ve installed just about every mainstream piece of software under the sun without issue. Every time someone suggests to me that it’s necessary - I point to my entire building that is running fine without being sysprepped, and I point to other buildings, other organizations, and my past jobs that are doing fine without it.

I’d suggest seeing if you can get it working without sys-prep first.

Does June 25th sound good for the next one? 10 AM Central Standard again?

@Ph3noM said:

@Tom-Elliott said:

the Hostname_early fog setting item

I don’t find it on the web interface …

(Forgive me i am a beginner in the computer networking)

Web Interface -> FOG Configuration -> FOG Settings -> General Settings -> FOG_CHANGE_HOSTNAME_EARLY

@apathetic_admin Don’t beat yourself up over something you didn’t know. What’s important is you asked for help where you needed it - instead of just giving up or being too proud to ask for help.

Part of being good in I.T. / comp-sci is knowing where to get answers.

@ManofValor Yes, everything in fog must be defined in one place or another in the DB, which means creating it in the Web Interface. You must create a storage node definition for the NAS.

@BardWood I don’t think it will work. The FOG Trunk methods involved with synchronizing storage nodes with their masters has greatly changed, along with the ability to now cross-share images with storage groups. I would not advise mixing versions as you would like, I think it’ll only lead to disaster. The location plugin has also been modified to cause remote nodes at a remote location to PXE boot directly from their local node. Also, the 1.2.0 nodes probably can’t support this functionality

You’d be better off just updating everything to fog trunk, OR just staying at 1.2.0 till 1.3.0 is released.

@Psycholiquid You could just use msiexec in a startup script to pull the client off of everything. Let that run a few days and then remove it.

Then let a few days go - and then deploy it to every client via startup script.

Why aren’t the new computers getting imaged with an image that has a client installed?

@adukes40 I did a little Google searching on that, that line does set a generic name.

Seems it’s un-doing the Early Hostname Changer’s work perhaps?

The current development branch automatically uses the right kernel as far as x86/x64 goes. Since your new to fog and are setting it up for the first time, I’d really urge you to go with Trunk. 1.2.0 is very dated and doesn’t support a lot of things that you will find you need. And FOG Trunk, I feel, is very close to release-ready. That said, there will be minor bugs here and there, just report them, the fog team fixes them pretty fast (we are well known for our quickness and take pride in it). Here’s how to upgrade to trunk: https://wiki.fogproject.org/wiki/index.php?title=Upgrade_to_trunk There are some installation tutorials that use FOG Trunk in our wiki, including Fedora 21, 23, and CentOS 7. If you wanna stick with Debian, that’s great! Write us an article!

And for the boot files, what you need is to setup your DHCP server to identify the vendor class ID (option 60) that the clients report, and give the boot file out according to that. There is an entire Wiki article just for this, right here: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence

I’d be happy to help you out further if you have any questions.

@MRCUR said in Windows 10 unattend.xml (sysprep answer file) challenge:

@Arrowhead-IT You have to be on the network selection screen in OOBE to get into audit mode. (I know this is completely non-obvious - it’s a very MS thing to do.)

MS should watch themselves… If they keep making things more and more difficult, and Linux distros keep making things more and more easy… well then… You know.

also @Andy-Abplanalp is right, you do have a typo in the boot file as well, in addition to the other problems pointed out.

It’s undionly.kpxe, not undionly.kxpe

Well, 1.2.0 hasn’t changed since it was released. And many folks are running it on Ubuntu 14. It’s most likely credentials related. Did you actually reset the local fog user’s password in Ubuntu’s OS via CLI?

Also, the IMAGE Size on server field is dependent on FTP as well. If your manually moving it but it STILL cannot see the size, then it’s your ftp credentials.

Please go through the credentials and passwords area of that wiki article again.

I also wouldn’t call a RAW image a success. It’s more of a stalemate.

@Tom-Elliott said in fog client, do i need it?:

@robertkwild The client is needed if you need the host to join to domain.

The purpose of the FOG Client is multi-fold.

The client allows the host to automatically:

1. Auto logout – Enables auto logout of users if inactive for specified period of time. 5 minute’s is the minimum time as all others are way too soon, sometimes people may just be on a phone, or had to step out for a bathroom break.
2. Client Updater – (Only on legacy clients) Allows the client to update it’s modules if you had to customize things, or found a more recent build was needed for your environment.
3. Directory Cleaner – (Only on legacy clients – Only worked with Windows XP) Enables the client to remove directories on the host automatically. It lost operation after Windows XP due to UAC controls and better security mechanisms especially needed. Removed completely from the New client.
4. Display Manager – (Legacy clients and at least through 0.9.12 of the new client, might come back if the need is strong enough though you can achieve the same results using a snap in.) Enables the client to adjust the resolution of the system on a per system basis, or global basis.
5. Green FOG – Allows you to specify a shutdown and/or Restart for hosts. These are scheduled on 24 hour time blocks. You schedule the time and action you want to take at that time. The client will schedule what you need for those times.
6. Host Registration – Registers additional mac addresses to a pre-existing host if registered. The New client will also register the host under a pending status if the host is not already registered.
7. Hostname Changer – Changes the hostname and joins the domain automatically.
8. Printer Manager – Manages Printers for the host. Legacy client only added printer or added/removed printers. The No management for both new and legacy simply does nothing. Will remove all printers under Add/Remove type and only add back the printers as needed (Only Assigned Printers). Under Add Only (now FOG Managed Printers) only manages printers that are listed under the printer’s GUI and those that are assigned to that host. In legacy client, it only added printers and never removed. Under the new client, it will ONLY manage printers assigned meaning if you remove a printer from a host, the new client will remove that printer.
9. Snapins – Allows you to install programs or run scripts on the host similar to GPO or PDQDeploy.
10. Task Reboot – This will just check if the client is in a tasking (other than a snapin tasking). If it is in a tasking, and the module is enabled, the host will be told to reboot. There is a third portion though in that if the user is logged in, and enforce is not enabled nothing will happen.
11. User Cleanup – (Legacy clients only and again only on Windows XP). Works similar to Directory Cleanup but the entries you make are “safe” user profiles. If the user is not under this listing, it will be deleted. Will not work with the new client, and even legacy clients will not work on anything beyond Windows XP due to UAC and Interactive Service utilities.
12. User Tracker – Just tracks who logs in/out of a client.

Added to the wiki here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Additional_Details

@abulhol Normally they are set by the installer on a fresh installation of 1.2.0. That said, 1.2.0 was imperfect in many ways. Stable - but imperfect. FOG Trunk (which is what will be 1.3.0 eventually) fixes all these issues. Also, no fog installer will ever just change what you have set in the DB, fog assumes the admin knows best. and in storage management, all the stuff in there is stored in the DB.

@DarkEnergy said in Invalid GPT table:

How can I solve this particular issue? Where do I need to make the changes?

@Tom-Elliott said in Invalid GPT table:

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