Windows 7 joins to the domain without requiring netdom.

I image windows 7 pro 32 and 64 bit using sysprep. I do not use Fogprep, as it’s not required with Windows 7 and FOG 0.32.

These are the steps I used to get it working:

1. Run FOGCrypt on a windows machine to encrypt your password.
2. When you install the FOG client, make sure to enable the hostnamechanger portion
3. Enable the hostname changer portion on the FOG settings of the server.
4. Input the AD join information in the FOG settings. I use domain\username for the username. Password is the encrypted password from step 1. Domain is the FQDN of the domain, like my.domain.com
5. Make sure the hosts are setup to join AD in the Active Directory menu item on the hosts screen.

After you do this, image a client. It should boot to windows, rename, reboot, join domain, and reboot. I do not use FOG to put client into a specific OU, just the default Computers (which you can redirect I hear, but have no experience). After computers join the domain, I put the computers into specific OU’s and groups for policy and management.

If you need help making a custom kernel, just keep up with what you’ve done, post your questions, and we’ll help as best we can. It appears daunting, but after you run through it a few times on a VM, it’s gets simple.

I did not see anything in those logs. Can you remove the snap-in and files from fog and recreate it, then try to push it out again? See if you get the same error.

Ajay, please start a new thread and give as much information as possible. If you would like, reference this thread if it contains relevant information.

Generally, we need to know what version of FOG on what OS. Is it a (N)ormal server or a (S)torage node?

I’m not as familiar with Capone as the rest of FOG, but try changing the image name to something without spaces or special characters and see if that helps. Just a guess, but the bash script that is processing your request may error out on the name, but display a misleading error message.

Please do not cross-post. Pick a forum and post your question. If you are not getting the response you need, feel free to PM a community manager and we can move it to a more relevant forum area or try to answer it ourselves.

I have merged your threads. If you feel this question is in the wrong forum, let me know.

check the apache log on the FOG server. It appears that whatever page the FOG client is requesting when it sees it has a snap-in waiting is not working well with your snap-in.

I think FogCrypt requires .NET. I’m not sure which versions, but you might try the .NET verifier tool and make sure you have 2, 3, 3.5, or 4 working and see if FOGCrypt will work for you.

storage nodes within the same storage group are replicated by LFTP, where the master [B]pushes[/B] it’s images to the other member nodes in the same storage group. The master does all the work, the non-master storage nodes just need to be ready to receive the images via FTP.

Everything I have read says do NOT install or update windows store apps in audit mode. MS says you can side load LOB apps if you need, but do not update or install any store apps before the oobe has run. It kills the sysprep run with an error about the apps not being provisioned for all users.

I think the suggested way is to use powershell scripts run at the end of oobe to install and update any apps from the store.

I am experimenting with Windows 8 and FOG 0.32. I set my OS type to Vista and use Multiple Partition Single Disk. I am not using FOGPrep, but going through sysprep in audit mode to setup the system, then sysprep to oobe.

My only issue is not FOG related afaik, my systems aren’t generated unique CMID’s. I do have them auto activating Windows and Office 2013 against a Server 2012 domain controller though, so it’s a partial success.

There is no mass upload built into FOG. It’s meant more for a mass deploy. That being said, it’s open source and can be modified to do whatever you want. Sorry.

domain\username

I could not get it to work otherwise. I don’t know if it’s a problem with FOG, or something specific to my DNS/NetBIOS/etc setup.

I actually tried to create something like this, but the process dynamically creating an image definition during registration was a bit tough.

Unless you have recompiled your client and fogcrypt packages to use a custom string, don’t post your encrypted AD passwords on the forums.

My AD setup is: domain: mydomain.com, username: [B]domain\username[/B], then password (encrypted with FogCrypt).

if you are going to create a master image, you should probably go into the custom disk configuration in windows and choose to make the partition smaller than max disk size.

For example, I’m creating the master image for Windows 7 Pro on a new workstation that has a 1TB HDD, but I may need to deploy it to a bunch of workstations that have between 160GB and 1TB HDD. During the windows setup, choose the advanced options for disk setup, and make the window partition 80GB to 160GB depending on your needs. Leave the rest of the 1TB HDD unpartitioned (other than the special Win7 partition that it makes automatically).

If you do this, then you won’t have a problem choosing the Multiple Partition - Single Disk image type option in FOG and deploying to a variety of disks.

Another option, is to use GPARTED on a USB bootable flash drive, and reducing the size of the windows partition down before you take the master image. GPARTED should let you shrink the partition down without corrupting windows. Make sure to leave enough free space for Windows to operate, which I think is about 10% (so if you used 30GB for the install, don’t shrink below 33GB).

You may want to research IP directed broadcasts. The issue of getting WOL to work between different subnets and VLAN’s is not a FOG specific issue, so there is lots of information on the next about it. Cisco may also be able to help if you have a support contract with them.

FOG tracks computers by MAC address. AD does not. Finding a unique attribute to link FOG to AD is the key. If you do that, writing the app to link the two should be simple.

Each storage node has a maximum number of slots it will image concurrently. Once that is reached, it queues the rest. The clients check in every 10 seconds to see if a slot has opened up and if they are next in line to grab that slot.

I think you just need to select all the machines you want to image, throw them into a group, and tell the group to deploy the images. It should queue them and process more as they finish.

If all machines are the same image, consider multitasking. If not, set the storage node max # of clients to 3 so that only 3 are ever imaging at the same time.

read the wiki guide on compiling a custom kernel. Then do it yourself on a virtual machine just so you can say you’ve done it. You don’t have to make a good working kernel first try, just getting familiar with the process goes a long way to understanding.

Do this and your questions should answer themselves.