@ayy_nelson Ah the DFL is Windows Server 2008 R2.

Would you think this would be the sole reason FOG is incompatible with this type of version?

I am looking into running it via a script, but would love to get the domain join on FOG working, if it’s possible!

Thanks again!

@sebastian-roth OK I see, it actually returns two backslashes “\” between the domain and username. Using FogDebugger

So was thinking was it not parsing through to the client correctly

@sebastian-roth We have AD on Win Server 2016, however FOG is running on Ubuntu on XenServer.

Is that what you was asking?

@sebastian-roth Thanks, I did use domain\username and also username and still same issue.

Using Fog 1.5.9
Fog client 0.12.0

When I use the Fog debugger, the FogCycle.txt returns the ADUser field as “Domain.local\\username”

Should that be correct? I am using just username in the field on the FOG GUI.

Hi,

After deploying a Win10 machine, I had configured Active Directory within Fog management:

Domain: domainName.local
Join after Deploy: ticked
OU: Left blank
Username: domainName\AdminUsername
Password: AdminPassword
Password legacy: Left blank
Name change: ticked

I get the following message:

HostnameChanger Logon failure: unknown username or bad password, code = 1326

I checked other forums and I tried without domain in username still same issue. I used Add-Computer CMDlet and joins the PC manually with no issues.

There is no NetDom command in Windows 10, so not sure if this may be an issue?

Otherwise can anyone see any issues?

Thanks

@george1421 OK I see, and thanks for that!

I went through the dirty bit and realised Sysprep was the issue in hand, as it was re-imaging over the same sysprepped image which seems to cause issues with cloning.

Removing the bit didn’t seem to work, so I then had to completely re-install a fresh Windows and start over again, and ran sysprep and fog cloned it successfully.

I see why using VM would be easier as you can sysprep as many as you need etc.

Thanks!

@george1421

I am hoping I can use we transfer to upload images which is jpeg files:

https://we.tl/t-PocCHt3U8I

I am actually using physical workstations as we want to prep drivers/updates on these specific models so when deployed, no need to update or run software like Dell Update Commander to get latest drivers when all up to date.

But would you still recommend capturing from a VM then?

How would you get around after using Sysprep a few times? Windows Reset?

Thanks!

Hi team,

I was able to sysprep (oobe) a Windows system and capture an image on FOG boot, however I had to reboot back into system to make a few more changes to allow FOG client to re-enable after deploy.

Now when I re-run the sysprep tool (tried audit and oobe), I get the following error messages:


I have looked at other forum pages of this error and I have already confirmed the SystemReserved partition is not assigned any letter.

Can anyone see the error?
Also not sure if the images uploaded OK? It keeps saying failed when trying to upload file nor image?

Thanks

@george1421 OK great, I will deploy it with a batch and see how I get one. Thanks again

@george1421 OK thank you for the info.

Eset requires an exe installer rather than an MSI file. However there is no exe option in the snapin type, only MSI and other options. I have tried Powershell but that didn’t work.

Which option shall I choose to deploy exe snapins? I have the latest Fog, 1.5.9.