@Vanlue-IT-Guy There were activation issues in that version. Update and it should work.

@Wayne-Workman I didn’t get a chance to test this snapin as I needed to have it done the following Monday. What I ended up doing was installing office 2013 and just not open it at all as the timer for office will not start until you open any of the applications.

@atarone I believe the answers you seek lay ahead… https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

@reub_rester Depends on what is acting as a DNS server.

I doubt your fog server is acting as a DNS server, because if it was you would know about it.

You need to create an A record on whatever is doing DNS for your environment.

Don’t forget that the machine account in AD has a password, this gets changed on a regular basis, this happens invisibly, it is a function of the way AD words.
From memory it gets changed every 30 days, and as I say is completely invisible to users and admins, the last changed date can be read from AD via LDAP, although it needs a bit of work to translate it into human readable format.
If you image a PC without sysprep, when you deploy that image it will not join the domain if the machine account password has changed.
This will need the PC to be deleted and re-added to AD to resolve.

This actually makes me wonder about the possibility of something similar to a task for imaging groups of hosts, but using multicast instead of singlecast.

Multicast session name could be the group name + incrementing number or something.

@tprice What new documentation (for future readers)?

@Scott-B just about every printer in the building is a different model. of which we have about 100. Some are USB, some network.

I manage the network ones with Active Directory without issue - it’s just this one printer being stupid. It needs replaced. It doesn’t even have drivers for Windows 7, I finagled Windows Vista drivers onto Windows 7 as a local TCP/IP installation before. It’s just impossible to deploy with Active Directory - everything I’ve tried has failed - and I’ve tried a lot.

Fog was my last resort.

But, here in the future, if it proves to be reliable and I think it will be, I want to use FOG for printer management because it’ll lighten the load on our DCs.

@Wayne-Workman Great video. Yeah, your image size isn’t large enough to find the standard transfer rates. Just as the transfer settles down its done. (not a bad thing). In our virtual environment we can pull a sustained 6-7GB transfer rate. That is with a VM with 2 vCPU and 2GB of RAM running on a 24 core processor. But again as long as the server can move the image from disk to net pretty quick, all of the heavy lifting is done by the client. On a e6410 with a HDD we can get no more than 4.5GB/min exchanging that HDD with SSD increases the transfer to 6.1GB/min on the same hardware.

Just for comparison, when I was working with that intel NUC as the FOG server. That dual core celeron with an 256GB SSD was able to transfer at 5GB/min to a e6410 with a SSD. So really the FOG server isn’t the key to deployment speed. It more compression used and target computer performance.

But either way FOG is darn impressive that it can wake the computer up and deploy a new image in under 3 minutes. With that you could almost reimage a whole computer lab {between classes} at any school system. That is impressive.

@george1421

Sorry for the long delay I have been swamped with other project. Thank you for getting back with me and the link to the guide. I will look into possibly upgrading that server to 2012. Thank you again for all of your assistance, it really is appreciated.

Thanks,

Anthony

I couldn’t resist the challenge. This should get you pretty close.

#!/bin/bash . /usr/share/fog/lib/funcs.sh; mkdir /ntfs 2>/dev/null echo "Mounting Windows File System"; mount.ntfs-3g "/dev/sda2" /ntfs 2>/tmp/mntfail mntRet="$?"; if [ ! "$mntRet" = "0" ] then echo "Failed to mount Windows partition"; echo ""; cat /tmp/mntfail; echo ""; sleep 12; exit 1; fi #Mount successful echo "******************************************************"; read -p "Enter your room number " rn echo "setx /M RoomNumber \"${rn}\" " >>/ntfs/Windows/Setup/Scripts/SetupComplete.cmd echo "******************************************************"; umount /ntfs sleep 5;

@Sebastian-Roth said in BASH on Windows 10 … and maybe FOG also?:

as well do Intel Macs (confirmed in my own lab!!)…

Any news on that subject? My organization has thousands of Macs. Is it easier now?

@ITCC Would you be willing to get a step-by-step guide for Debian ready? Would be a great starting point.

I’m sort of ashamed that I haven’t done any of the things I said I’d do in this thread yet 😕 I’ll make it a point to test out the various file types soon.

@chimchild That would do it. I favor iptables for major network appliances. It’s commands and config make more sense to me than firewalld does.

@C-M said in How do fog images work and can it do this?:

I’d prefer the thin method as it seems easier to keep up to date and add and remove apps at will.

Both thin and fat images have their place. If you update your images every quarter (to have the latest windows updates) then adding in your software is not a big deal (as long as MDT does it). There isn’t any more work involved than having a thin image and layering on the applications post deployment. Plus with a fat image I can go from bare metal to fully deploy and ready to move to the work site in about 13 minutes. That is with MS Office, SAP GUI, AutoCAD, and a few other PIG applications.

Using a fat image (and a multicast deployment) I can redeploy to a whole lab (50 workstations) in about 20 minutes. With that said there is also uses for thin images where you might have a dynamic application load. In that case we push the image out with FOG and then use PDQ Deploy to deploy the application set to the workstation. (I could use FOG Snapins for this too, we just had PDQ Deploy setup first).

Nope not a problem. But its easier with dhcp.

You may be able to do what you want using snapins and a 3rd party tool.

i believe i was able to get the esxi iso to boot using memdisk iso raw

Yeah that makes more sense