Topics created by robertkwild

@robertkwild said in syspreping a vanilla windows golden image:

i found this, you can sysprep win10 up to 1001 times

Just to be a bit snarky, if you have to sysprep your image 1000 times, I think you might be doing something wrong or IT should not be your field of work.

But on the less snarky side its good to know the number and hopefully I’ll never personally need it. As I said we use MDT to build the golden image so I get a fresh from DVD image (with current windows updates) each time the golden image is recreated.

ok job done.

just renamed the images dir to something else, made a new images dir, in fstab mounted the raid6 in the images dir and re ran the setup shell script

i did a capture and a deploy and all is now good

thank you all for your help!!!

sorted it out, i had to enable port fast on the cisco switch for the port(s)

the reason it took ages to get a dhcp address is because when port fast is disbaled it takes 30 seconds for it to give it a lease address

@robertkwild said in creating an image container for windows server 2012 r2:

so for normal cloning i can use “single disk resizable”?

Please read this: https://wiki.fogproject.org/wiki/index.php?title=Managing_FOG#Images

If you don’t need to deploy to a smaller size disk you might consider using this image type as it’s less likely to cause an issue and image size on the server is still as small as with resizable image type.

Xen defaults to BIOS though in 8+ you can switch to EFI and I’m pretty sure new versions of ESXi default to EFI. Can you confirm which you have on each?

@dvorak You’d need it in the ISO.

PXE is before the system is loaded, and as such cannot trigger actions at the HDD level beyond loading a Disk, Boot Rom, or whatever.

@robertkwild In addition to the link posted by @igorpa2 and in addition to this wiki article refered to by @Sebastian-Roth, there is a tool called updateIP.

updateIP was created as a easy to use tool for updating your FOG server’s IP settings after you’ve updated the OS’s IP. I would highly recommend it.

@robertkwild To clarify, I’m not sure if that’s what’s causing it, just an idea to try out.

You can do a clean shutdown with shutdown -s -t 0

@Sebastian-Roth I would think if one only wanted the system to shutdown after a full registration you could update the iPXE FOG Menu item for full registration and add in shutdown=1 to the Boot Options field.

I have not personally tried doing that, so its only an educated guess.

@Tom-Elliott Maybe add another user confirmation to make clear this will overwrite an existing image…?

lovely stuff, job done -

kernel http://fog/listing/centos7_1804/images/pxeboot/vmlinuz ks=http://fog/listing/centos7_1804/ks.cfg
initrd http://fog/listing/centos7_1804/images/pxeboot/initrd.img
boot || goto MENU

How do I setup my fog server so that it deploys the kickstart file to a host via PXEboot

@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:

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. 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. 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. 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. 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. 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. Hostname Changer – Changes the hostname and joins the domain automatically. 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. Snapins – Allows you to install programs or run scripts on the host similar to GPO or PDQDeploy. 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. 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. 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

@robertkwild As I posted in the other thread,

“I would recommend that you install the FOG trunk version (1.2.0 trunk a.k.a pre1.3.0) and not 1.2.0 stable if you need support for uefi, gpt, and windows 10 support. https://wiki.fogproject.org/wiki/index.php/Upgrade_to_trunk
You can install the trunk version directly and don’t need to install 1.2.0 stable first. Just go directly to the trunk. Use svn or git to get the installer then launch the installer. For Centos FOG installs clean without any problems.”