Posts made by VincentJ

Just installed a fresh windows 10 professional and it also has error 87.

Can i make the client output everything it’s trying to execute?

Indeed, I only reimaged once so i could exclude any errors on the first one.

Same issue with the administrator account and password.

Do you have windows 10 machines, with the anniversary update applied, running with successful domain joins? (Version 1607)

I have been looking at the domain join scripts, do you use the netapi32.dll NetJoinDomain because the client is unable to run Powershell commands?

I deliberately changed the password to be wrong… and i get a different error telling me the username / password is wrong.

I know the username and password are correct. and the domain is correct because i’m looking at it in AD Users and Computers and Group Policy and in the fog gui.

no OU set.

Set a specific user ‘fogad’ as a domain admin
Tested a manual domain join on a different VM, imaged from the same master as this one.

reset the info in the AD section of that host and first typed the password into notepad to confirm it’s the same as it should be.

I don’t see anywhere i could be getting it wrong.

Even double checked the client can ping domain.lan

I specifically set this host’s AD settings. Have not set the default ones yet.

I have also tried the cleartext password (Thank-You for adding that) as well as the old encrypted one in the other box.

Fog Client 0.11.5
Fog Server 1.3.0-RC-8
Client OS - Windows 10 (including anniversary update)

Hostname successfully changes but domain join shows error code 87 (The Parameter is incorrect.

I have checked the domain - manual joins function.
Checked time and timezone - all OK
Reimaged and tried again to make sure there was no problem there.
Tried multiple usernames and passwords - Domain admin and specifically created user for fog.

25% Packetloss… Guess China’s firewall doesn’t like it…

Downloading inits, kernels, and the fog client… Failed!

Looking through code to download manually.

Some of the places do not seem to exist.

https://github.com/FOGProject/fog-client/releases/download/${clientVer}/FOGService.msi
https://github.com/FOGProject/fog-client/releases/download/${clientVer}/SmartInstaller.exe

FOGProject/fog-client has no releases directory that i can see.

My Storage nodes are dumb NFS servers.

Will upgrade to trunk and see if the issue is resolved.

I am testing for a new image.

Fog Server is 1.2 - VM. Storage is on an independent device.
Test VM is 4GB RAM, 2 vCPU.

Imaging works perfectly, however with the latest Windows 10 updates… After installing Fog Client from 1.2 it does not change the hostname at all.

The same fog server with the same client on windows 7 does function.

According to the logs:
The client connects to the server,
Client starts FOG.HostNameChanger
Client starts the hostname change process
HostnameChanger Yields to other subservices
HostnameChanger attempts to contact the server,
Module is active
HostnameChanger Hostname is upto date.

However… The hostname is Desktop-xxxxxxxx
The hostname in FOG is set to WIn10test2

So, the Hostname is not upto date as the client seems to think.

If the NAS can be an NFS and FTP server, skip the fog server and use the NAS as the only storage node.

@Sebastian-Roth

So that gives us an ISO that installs on whatever VM the user creates and also probably installs on physical machines as well… Everything done

Tom
People using their hypervisors will often start to get to know this system. Making a VM on ESXi or XenServer or Virtualbox is relatively easy.

Stops all the discussion about which hypervisor or the specifications of the VM. If it’s easy to reproduce then lets go for it.

Tom - How much work would be needed to hand make the linux over a standard install of debian with SSH? Debian isn’t too much of a disk hog anyway so is it really worthit?

@andyroo54

What use would a GUI serve when the whole of FOG is done over a web interface? Just make the console say ‘Go to x.x.x.x for web interface’

as for OS… we could argue all day between Debian/Ubuntu/CentOS and others…

Same with Hypervisor… we could argue all day about VMWare, XenServer, Hyper-V, Proxmox and thats without Virtualbox/Bhyve/KVM and anything else you can run.

I know it’s more work… but an ISO would get rid of this argument. How much actual work is it to script an installer of linux and make it run the installer on boot?

32/64bit - just specify only 64 bit… Can’t think of a good reason not to use 64 bit in this day.

So now we’ve gone from 250gb to 512gb…

Next we’ll get the angry person who says their storage broke all their other VMs because they overallocated and filled things up.

Saying that the other things can be adjusted… The people who don’t know what they’re doing wont know to change them and will manage to break things somehow.

Happy users might tell a couple of others… Unhappy users are generally much more vocal.

Instead of a VM, could you create a netinstall iso that downloads and installs the OS for you and then launches the FOG installer.

Smaller download, runs on any VM that has internet access, lets the user set their own RAM, vCPUs, HDD and Networking.

You will NEVER please everyone… for me a 250GB VHD would be way too big… for someone else it would be way too small…

2vCPU - reasonable for most, but my home hypervisor wouldn’t run it properly as it’s only on a celeron. 1vCPU, could we run into issues where there isn’t enough CPU? (Neither would a HP Microserver)

1GB RAM - should run OK… but someone will moan that their low end PC ran out of RAM running it… Someone else will moan that it should have more…

In order to run FOG, they need to change their DHCP, You shouldn’t force this onto the FOG server because it could lead to them effectively killing their network when their DNS doesn’t work. They need to know what they are doing to some degree or we will just end up with angry people who don’t have a clue moaning on the forums, giving FOG a bad name.

There is no replacement for knowing your own environment and how it works. We should emphasize that this is not ‘easy peasy’ and will require some level of knowlegde.

@andyroo54

Considering I don’t use the actual Fog server for image storage I can keep the ‘appliance’ very small.
If I stored my images in my Fog VM it would mean that VM would need to expand to huge levels.

Making NAS NFS storage more normal would make a VM Appliance easier.
If we keep storage inside the VM you will get massive arguments about how big the VHD should be.

Installing Debian (My preference) and running the install script isn’t exactly hard.
Someone planning to image computers would need to know more than that to get running in the first place.

I would try to use KMS if you can, if your doing this for OEM it will be a pain…

You could run the script via batch file, snapins, wpkg, opsi, GPO. It all depends how you are setup and how your environment works.

I put the FOG server on a VM, and then have storage on my NAS.

Most NAS’ can function as a storage node if you configure it correctly, I normally use FreeNAS.

This is the process for a KMS Server… so use the part that you need.

slmgr.vbs -ipk FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4
slmgr.vbs -skms IPADDRESS:1688
slmgr.vbs -ato
slmgr.vbs -dlv > c:\KMS.log

The key is the public KMS one that you input into clients.

Mod edited to use code box.

should be able to make a batch file or something to do it.

https://technet.microsoft.com/en-us/library/dn614984.aspx