It appears it’s an issue with the Unattend.xml file. I’ve tried one that has worked in the past and that’s absolutely fine.

Thanks for the help, gents!

the recovery/reserved partitions are automatically detected and should be set in the “fixed” partition list. Chances are, it would seem, that this didn’t get set for some reason? It looks at the label’s that windows typically defines. If the recovery/reserved was setup as a custom partition, most likely the label didn’t get applied as would happen in a “default” scenario?

You should be able to correct this behaviour by adding the partition number to the fixed partition file. For windows 10, I believe the partition number used for recovery|reserved is number 3.

Resizable partitions use the filesystem volume to determine if it’s viable for resize. Windows reserved/recovery from at least windows 7 on typically has this as an NTFS partition.

@Jonathan-Cool Use this: http://windowsafg.no-ip.org/

@aharrison For in the FWIW bucket. The for win10 the panther folders gets searched first for the unattend file first and then on down the line: https://technet.microsoft.com/en-us/library/cc749415(v=ws.10).aspx

MS Recommends that you place the file in the panther folder (either unattend, or panther directly). Then calling out the specific path to it isn’t required. I always do include the specific path out of habit.

@Quazz Yep, after shutdown and wol i get pxe. It may well be a bios issue, but I think the hybrid shutdown is happening even when fast startup is disabled. I have just put the question on Dell forums, I’ll see if they have any ideas and report back if they do.

Just Kidding :))))) I just added the other architectures under the helpful little NOTE: and it works just great! I Skim too much and don’t read enough. You guys are great.

@Raj-G under <settings pass=“specialize”>

<component name=“Microsoft-Windows-UnattendedJoin” processorArchitecture=“amd64” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“http://schemas.microsoft.com/WMIConfig/2002/State” xmlns:xsi=“http://www.w3.org/2001/XMLSchema-instance”>
<Identification>
<JoinWorkgroup>Workgroup</JoinWorkgroup>
<Credentials>
<Password></Password>
<Username></Username>
</Credentials>
<JoinDomain></JoinDomain>
<MachineObjectOU></MachineObjectOU>
</Identification>
</component>

the above is for 64-bit… if you’re ever unsure use WAIK to generate your unattend file for you if you don’t feel comfortable doing it manually

Yeah, not closed until it’s actually working.

@Troye-Johnson this issue is patched in v0.11.12.

@Joe-Schmitt Thank you for your post, this was the problem.

@RobTitian16

Q1 Batch file: This is an independent batch file from MDT. We do a few clean up actions just before sysprep and power off. We do this via a batch file and at the end of the batch file it runs the sysprep command with a consistent syntax. That way we get the same exact action every time we build a master image and then sysprep it. It could be done manually by copy and paste, but its much easier to run the batch file. We do have the sysprepit.cmd file as well as some branding stuff installed as a MDT package. That is how it gets copied over to the reference image as a MDT package.

Q2 CAB file: Understand there are 2 different cab files in play here. We install the winpe cab file in the reference image since that contains the core drivers we need post deployment. The driver path /images/drivers/{hardware_type}/{os_type}/{arch}/{driver files} is the extract of the model specific cab file. If you give me a specific dell model I can point you to the proper cab file.

@dustindizzle11 Thank you for sharing what you’ve learned> I’m sure it will help others as they find this thread in the future. Well done!!

@Bob-Henderson You might enjoy Snappy Driver Installer, although this is generally more useful if you get all sorts of models accross the floor, rather than expected ones as it will have drivers for close to everything. (compressed)

You’re scheduling a capture task in the web interface, right? How many FOG servers do you have?

@Joe-Schmitt said in Adding Machine to Domain using Active Directory:

@dylan123 said in Adding Machine to Domain using Active Directory:

So I’ve attempted to deploy an image onto the domain

Images should never be pre-joined to the domain, Active Directory is fundamentally incompatible with handling that scenario. Either use setupcomplete.cmd in sysprep to join the domain, or the FOG Client.

Yeah wasn’t the first thing I tried, more was testing it just to see if it made a difference.

Wasn’t aware the FOG Client was required to make the active directory feature work. Have since installed and tested, can confirm it worked.

Thanks for your help Joe.

Bumping this thread.

@oraniko you need to keep in mind the client runs as Windows service, which gets run as SYSTEM (that is, a non-interactive user). This means you’ll need to take non-supported approach to get this working. Change
net use r: \ph.ph.biu.ac.il\Programs MYPASSWORD /user:DOMAIN\MYUSERNAME
to
net use r: \ph.ph.biu.ac.il\Programs MYPASSWORD /user:DOMAIN\MYUSERNAME /persistent:yes

Now, you need to keep in mind SYSTEM now owns this network mapping, and so only SYSTEM can remove it. In addition, Microsoft doesn’t really support this, so its likely the drive will show as disconnected for all users, but it should still be accessible if they try to open it.

Perhaps a better approach would be to make a GPO logon script to auto mount these network shares.

Did not mean to insinuate that it was the fault of the FOG client, as I’ve seen it before even when not using FOG.

Do you know of a way to have it use the original Administrator user folder and not create a new one?

For reference:
When creating the image I’m hitting Ctrl + Shift + F3 to boot to Audit mode during the Windows install.

During the Specialize phase of sysprep with the Microsoft Windows Deployment component I’m creating a synchronous command to activate the admin account.
net user administrator /active:yes

During the OOBE phase I set the password as well as auto logon details.

This is really a minor issue, but there have been times where it would have been helpful to be able to deploy files straight to the admin desktop; which would be difficult if the directory name isn’t always the same.

@jayrob86 See if this works. https://github.com/wayneworkman/fog-community-scripts/blob/master/exportFromDB/exportTableToCSV.sh

Thanks, Tom, that’s worked, I knew there was something extra to do with the encryption data that I needed to do, but couldn’t remember.

Dan