Topics created by kwetiaw

While I’m super glad to have pushed up RC-25, I just wanted others to understand the idea.

The original issue is I switched over to a much less SQL tasking request system. Basically, the way things where (while much progress had been made originally anyway) very sql taxing. For a host, you might have had 12 separate SQL queries per each host to get the data.

I figured out a nicer mechanism around this, but missed two steps. While I was testing things, I was very minimally doing so just ensuring things were operational, not necessary “working” if that makes sense.

To fix this particular issue I basically had to have the class load itself again which doesn’t do much to get away from sql queries.

I’ve since fixed this issue, tested, and validated it’s operational and functional as well without the excess SQL queries which will be available for RC-26.

Just thought it’d be good to give everyone a heads up on it.

Thanks.

@Daniel-Miller

I am at this specific point with regards to attempting to download the cert.

@Wayne-Workman absolutely weird.
I used the same technique with snap in pack on different folder and it worked without issue in the past. Only this time around with system32 folder.

I even tried with xcopy!

Anyway, thanks for your help, appreciate it and I will check further to see if AV is a culprit here.

Cheers

@george1421 said in Microsoft Surface Pro 4 with Surface Docking Station - Unable to get boot file:

@Wayne-Workman Do you think we have enough discrete bits of information to make a wiki page on the surface pro 4? As these devices become more popular I can see the volume of quesitons increase. Having one location (you look here->) would add real value from a support perspective.

I still want to do this, will start work on it maybe tomorrow - it may take the entire morning to do, this will be a large article.

@Wayne-Workman said in Microsoft Surface Pro 4 with Surface Docking Station - Unable to get boot file:

@kwetiaw I’m linking threads that deal with the Surface Pro 4 here for you to read through. All of the below threads are marked as solved. As George already said, I’d like to compile all of this information into a single #wiki article, but I don’t have a SP4 to test with. I will be out for several days after tonight.

https://forums.fogproject.org/topic/6515/surface-pro-4-won-t-get-to-registration-menu

https://forums.fogproject.org/topic/8181/surface-pro-4-image-capture

https://forums.fogproject.org/topic/7660/surface-pro-4-on-7977

https://forums.fogproject.org/topic/7353/surface-pro-4-unable-to-image

https://forums.fogproject.org/topic/8323/several-problems-with-surface-pro-4

thanks for all the reply. I will give it try and see how I go with it.

Thanks!

@kwetiaw Well, dnsmasq in proxy mode might be a different story. I have to admit that I read your initial post about using dnsmasq because you are not allowed to touch the real DHCP servers but somehow wasn’t aware of that fact when posting my answer.

From the dnsmasq man page:

For directly connected networks (ie, networks on which the machine running dnsmasq has an interface) the netmask is optional: dnsmasq will determine it from the interface configuration. For networks which receive DHCP service via a relay agent, dnsmasq cannot determine the netmask itself, so it should be specified, otherwise dnsmasq will have to guess, based on the class (A, B or C) of the network address.

So we are back to my question on how is you server (running dnsmasq) connected to those two networks?

Maybe this could work (if you have two different NICs for those two networks - please post the full output of ip a s on that server):

dhcp-range=eth0,10.3.0.1,proxy dhcp-range=eth1,10.40.0.1,proxy

@Avaryan Thanks matey.

I shouldve mentioned my environment on my post. Windows 10 Enterprise and I just tested with the powershell script you mentioned.

WORKED FLAWLESSLY!!!

Thanks and really really appreciated!

This issue only appears to happen on windows 10 installations. It would seem the legacy client uninstaller is not fully compatible (of sorts) with windows 10.