Posts made by MadsMagnus

@Wayne-Workman

Do you know if it is the OA/OEM key that you fx would find on the COA of a machine - or the “translated” product key that is used once a machine is running W10? Because I cannot seem to find my original key anywhere once W10 is installed.

@Wayne-Workman

I just tried adding some real hosts (non VM), they are renaming just fine.

@URfog

Yeah maybe it will work if I am part of an AD, but the machine I am testing this on is the Windows image - so no AD for this bad boy.

@Wayne-Workman

This worked perfectly. Now the log just says:

“Users still logged in and enforce is disabled, delaying any further actions”

I cannot seem to find a solution to this, let alone understand what they mean by “enforce”

@Joe-Schmitt

Not exactly sure what you mean by that.

But I do see this in the log:
Authentication ERROR: Could not get security token
Authentication ERROR: Could not find file C:\Program Files (x86)\FOG\token.dat

@Tom-Elliott

Server updated to 7907 but still the same… Does the newest trunk have an updated FOGservice aswell?

Unable to get subsection
Object reference not set to an instance of an object
Unable to run module
Object reference not set to an instance of an object

@Tom-Elliott

Literally my apache2 log does not have a new post since monday… A lot has happened since monday ^^ But I probably got the FOG server running properly there.

I will snapshot my VM and give it an update.

@Tom-Elliott

I see nothing in my apache2 log since monday… Quite strange.

@Tom-Elliott

I am getting this error too. When you say update, do you mean the server or client services?

@Wayne-Workman

When you say product key, you mean the newly generated product key from Windows 10 yes? Because right now I am trying to get this running by using our Windows 7 COA keys.

@Wayne-Workman

Yeah I think I have understand the fact that I must upgrade/clean install Windows 10 (and enter key) before the machine is “upgraded”.

So what do you guys do about embedded Windows keys on laptops? Do I really have to dig em all out 1 by 1?

But just to be clear, once the machine is upgraded - the product key part on FOG should work - yes?

@Quazz

Yes I am aware that it needs to be build 1511 before Win7/Win8 keys are eligible. But I still feel that this problem, with FOG being involed, is a whole different ballgame?

Hi there

Finally I have my FOG running properly and everything seems to be good to go. BUT, I have come across a problem.

As of right now my unattend.xml has a generic Windows 10 key, as I have been told that it is neccasary to have a key in the answerfile? Maybe I should try without it unless you guys know for certain.

The problem is: I have a bunch of Dell machines with OEM Win7 licenses attached. These keys are the oldschool type with a physical label on the side - so I even know every single key (no need for ROM digging). All these machines need to be upgraded/updated, as I only know 2 ways to do so:

1. Windows Upgrade on existing W7 installation.
2. Clean install, type in existing key - Apparently this also activates properly.

I know now that if I try with a unique answerfile, including the key bound to the machine, the sysprep does NOT activate the key. Neither will manual activation after imaging is complete.

I see that the new FOG has a spot for “Product Key”, perhaps this is meant for something?

The last thing is the rename part. Formerly I have had the computername part of the unattend.xml filled out with “RENAME” - and it would then give the newly imaged PC a name corresponding to the ID applied via FOG… But now I see that my machine is named “RENAME” after imaging…

That was a mouthful… I hope you guys can help me :S So far I love FOG but I am also new to it all.

Okay so it seemed our DHCP had a secret Scope Option that was overriding our initial undionly.kpxe. It was set to run pxelinux.0 - so when we changed it my VMWare machine has no issues booting on undionly.kpxe

Solved!

@george1421

7785

Yeah I have not had this problem before I updated. I was running 0.32 for a long time, which then was using the old PXE boot option. After the update I changed it to undionly. The reason of course for updating, was to capture Windows 10 and not just Windows 7.

@george1421

Hi again george.

1.2.0 trunk - stable didn’t work for me… (strange right)
VMWare 8? Does that hit it right?
PheonixBIOS - I guess thats the VMWares own BIOS or something.
The DHCP option is set to use undionly.kpxe as instructed by the guide.

Hi there

So it seems I finally got everything running, but it seems the VM I use for my Windows 10 image has a problem downloading files properly?

1st attempt of registration stalled on bzImage load.
2nd attempt couldnt reach the iPXE boot menu, as bg.png could not load (just a load of dots).
3rd attempt stopped at 72% on loading bzImage.
4th attempt stopped at the next loading AFTER bzImage. And now again, I am stalling at bzImage.

What can I do to fix this? I can see contact on the fog backend (graphs are popping up when I try to register), but only in small spikes and not continuous contact…

@george1421

It is just a random VM machine running off a Dell server - not sure which kind. I just checked up on the machine this morning and it is still just at “bzImage …” with like a million dots by now…

@george1421

Okay so as a part of the webacces fix, i upgraded to version 7785. This clearly did the trick, as now the clients also seem to PXE boot properly. However now, as I am trying to do a registration of my W10 image, it is just stuck at “bzImage…” etc. The dots just seem to keep going. I will be leaving in a sec so I will see how it stands tomorrow. But I suppose I have to open another thread, as the issue has changed, correct? I would imagine we are seeing that the VMs NIC isn’t recognized by the base kernel.

@Tom-Elliott

Updating to version 7785 seemed to do the trick. Webacces is now full functional. Moving on to the next problem.

Thank you all SO SO much for your help