Posts made by mrayzies

With the help of a co-worker, I figured out a reasonable way to get into this situation!

Imagine you have “host1” with MAC address “de:ad:be:ef:00:01” in FOG. You queue up the task but the host never downloads it. When you examine it, you notice that host claims it is unregistered and after just a little bit of poking, you realize that some yahoo labeled it incorrectly and the MAC address is actually “de:ad:be:ef:00:02”. You hop back into the web interface, pull up “host1” and edit the MAC address to the correct value. However, once you save after having done that, you will end up with 2 host1’s: one will have the correct MAC, one will have the incorrect MAC. From then on operations (like delete) will get applied to both of them (as I noted above).

I don’t think you would run into this issue if you tried to register from the FOG client because it would inform you at that time the hostname you wanted was already in use. But I am not 100% sure on this.

@Wayne-Workman
Not a problem – with weird issues, it can be hard to find a good place to start.

@Tom-Elliot
I’m not quite sure what you are asking for when you mention the “direct path”. If you think this is fixed in the latest commit though, I can try to download and verify it works/doesn’t work.

I previously incorrectly stated that logging in and out fixed it – it does not, nor does opening up a fresh incognito tab.

It also seems that it’s not just the “list active tasks” portion of this web page but all categories of “Task Management” that get messed up.

“list all hosts” should show clickable links, but instead shows:

“active snapin tasks” doesn’t show its tasks:

“new search” seached for something without any input from me:

When they do display, the console does not log an error about ‘sub’ being undefined:

FOG 5688

When loading the task management page, sometimes active tasks are noted but not shown:

The apache logs have no errors. The access log looks normal:
POST /management/index.php?node=task&sub=active HTTP/1.1" 200 1288 "https://fog.xes-mad.com/management/index.php?node=task&sub=active" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/47.0.2526.73 Chrome/47.0.2526.73 Safari/537.36

The web console logs an error Uncaught ReferenceError: sub is not defined.

It has happened both on Chromium and Firefox (I.E. not tested).

It does not happen all the time, probably about a fifth of the time. Once it starts happening, it seems that the only way to fix it is to log out and back in.

As a side affect of this, the original host names of the machines that become duplicates remain registered in the database. Thus even though they don’t show up in the web interface, you can’t reuse those hostnames unless you delete from the database.

@Wayne-Workman

As I said, I’m like 99.9% certain that this was not how I originally got into this situation; however, I have been unable to get back to it in some sane way.

I agree that copying MAC addresses is strange and it is not something I would do otherwise.

If I figure out how I got to this in a sane way, I will let you know.

So I don’t believe this to be the way I originally got in this state, but here are steps to reproduce the end state:

1. select host
2. copy MAC
3. select different host
4. paste MAC and click update

Host list will now show duplicate hosts.

FOG 5688

In the web interface, clients that have the same host name have operations applied to all of them. This makes them impossible to separate, ultimately resulting in having to remove all hosts and then re-add them.

For example, I had a box “username1” (referred to as boxA) that I had deployed with FOG. However, after imaging, I realized I needed to use different hardware for this specific user and created a new host (referred to as boxB), with a different MAC, but the same hostname “username1”. Both boxA and boxB imaged correctly and seemed to function fine (e.g. both seemed to grab their respective Windows keys); however, I was unable to change the name of boxA without it also changing the name of boxB, i.e. renaming boxA from “username1” to “undeployed” ended up having both boxA and boxB with username “undeployed”.

I did not do further testing to see what would happen if I changed additional settings on these hosts, but presumably changes would be applied to both.

The only way I found to fix the situation was to delete one host (e.g. boxA) which would result in BOTH hosts being deleted (i.e. boxA and boxB) and then re-adding them with different names.

I was trying to build it from Visual Studio myself; however, I kept getting errors, like:

This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them. 
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
	 - Installer, "C:\Users\Administrator\Desktop\fog-client\Installer\Installer.wixproj"


No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
	 - Service, "C:\Users\Administrator\Desktop\fog-client\Service\Service.csproj"
	 - PipeClient, "C:\Users\Administrator\Desktop\fog-client\PipeClient\PipeClient.csproj"
	 - Tray, "C:\Users\Administrator\Desktop\fog-client\Tray\Tray.csproj"
	 - UserService, "C:\Users\Administrator\Desktop\fog-client\UserService\UserService.csproj"
	 - UpdateWaiter, "C:\Users\Administrator\Desktop\fog-client\UpdateWaiter\UpdateWaiter.csproj"
	 - UpdateHelper, "C:\Users\Administrator\Desktop\fog-client\UpdateHelper\UpdateHelper.csproj"
	 - Debugger, "C:\Users\Administrator\Desktop\fog-client\Debugger\Debugger.csproj"
	 - PipeServer, "C:\Users\Administrator\Desktop\fog-client\PipeServer\PipeServer.csproj"
	 - Handlers, "C:\Users\Administrator\Desktop\fog-client\Handlers\Handlers.csproj"
	 - Modules, "C:\Users\Administrator\Desktop\fog-client\Modules\Modules.csproj"
	 - .nuget, ".nuget"
	 - FOGService.Tests, "C:\Users\Administrator\Desktop\fog-client\FOGService.Tests\FOGService.Tests.csproj"
	 - AbstractService, "C:\Users\Administrator\Desktop\fog-client\AbstractService\AbstractService.csproj"
	 - SetupHelper, "C:\Users\Administrator\Desktop\fog-client\SetupHelper\SetupHelper.csproj"
	 - PowerCLI, "C:\Users\Administrator\Desktop\fog-client\PowerCLI\PowerCLI.csproj"
	 - PrinterManagerHelper, "C:\Users\Administrator\Desktop\fog-client\PrinterManagerHelper\PrinterManagerHelper.csproj"
	 - ShutdownGUI, "C:\Users\Administrator\Desktop\fog-client\ShutdownGUI\ShutdownGUI.csproj"
	 - FOGService, "C:\Users\Administrator\Desktop\fog-client\FOGService.sln"

But it sounds like you might not be surprised by that. Could you send me a build please?

Thanks for working on this so fast. I will test it out today.

I’ll actually be out til Monday the 28th – I’m sure you have holiday plans (or at least take some time off!), but I’ll make some decision on Monday when I evaluate my schedule.

@Jbob

Ahh, thanks for that documentation.

I see in it specifically that it states "To use the keys listed here (which are GVLKs), you must first have a KMS host running in your deployment. ", so that isn’t for us. But I’m sure someone will find it useful.

I was talking about the CRON job.

And OK – sorry to barge in on the conversation.

@Wayne-Workman
I think there should be an option in .fogsettings to skip this altogether, not because of system resources, but occasionally I might want to poke at the system (e.g. add a temporary VIP for testing something else) and unless the coding is air-tight, it might kick off some horrible changes.

It seems to be the same end result, not sure if it is the same cause.

Feel free to close this though and I’ll watch the other one – sorry I didn’t find that one in my search

One potential think to note is that it seems like you got to that state from quick/full host registration, whereas I got to this state by entering data directly into the web interface.

I’ve saw several related threads to the product key input, but not my issue specifically.

FOG 5688

In both Firefox (Linux v43.0), Chromium (Linux v47.0.2526.73) and Chrome (Windows v47.0.2526.106), my product key input shows 3 additional characters if the element is inspected, e.g.:

<input id="productKey" type="text" name="key" value="11111-22222-33333-44444-55555���">

Occasionally, when altering the contents of the input, those characters become visible in the actual display.

Despite this, I have had hosts successfully activate windows, so it seems the client either ignores or doesn’t receive those characters.

Occasionally, those characters are expanded (I’m not sure what the trigger is), and then something like this happens:

<input id="productKey" type="text" name="key" value="11111-22222-33333-44444-55555&amp;IUML;&amp;IQUEST;&amp;FRAC12;-&amp;IUML;&amp;IQUEST;&amp;FRAC12;&amp;IUML;&amp;IQUEST;&amp;FRAC12;&amp;IUML;&amp;IQUEST;&amp;FRAC12;&amp;IUML;&amp;IQUEST;&amp;FRAC12;&amp;IUML;&amp;IQUEST;&amp;FRAC12;�����"></input>

When this happens, the FOG client will note an invalid product key in its log.

As an update for the test I promised – the newly imaged host imaged properly the first time; however, on subsequent imaging attempts, windows fails to activate, but it is not activating the key shown in the web interface, but is trying to activate the MAK key (the key that was present in the unattend.xml) – this step is failing because that MAK key has been burned out. I have tried renaming the host, and even though the client recognizes that change, it does not grab the updated key. Interestingly, it will notice that the key is malformed if I remove some of its contents; restoring the full key only gets it back into trying the MAK key.

You might be able to get useful information if you check out the client’s POST requests – if you have any type of switch that can mirror traffic for you, mirror the client’s traffic to a machine that’s just running tcpdump/wireshark, then do an upload/download while capturing to see exactly what’s going on. I was able to fix quite a few issues for my setup and it was pretty easy to see what was going wrong (e.g. the client was sending FTP requests to the wrong server, the client was accessing an HTTP path that didn’t exist, etc).

Lead thinks using those in an image would violate MS terms, I don’t suppose you have any links to MS documentation stating its OK to use such generic keys in unattend xmls ?