Posts made by dylan123

@sebastian-roth said in Climbing Imaging Speed:

@dylan123 said in Climbing Imaging Speed:

I don’t think that’s the case as I’m able to move a file from the FP server down to my computer at 60-110MB/s so I don’t think there’s any shaping of that kind on the network.

Traffic shaping can be implemented on protocol/port basis. So transferring files through let’s say SMB might work at full speed but NFS could be slow.

Then as well there is one question not being asked as far as I can see. Is this imaging multicast or unicast and how many clients at any one time?

Fair call, I’d like to think there’s no shaping though due to the fact it’s only myself and my manager in the IT team and we haven’t really had the need to shape traffic. I suppose it could be been set prior to us but I think it’s unlikely.

I believe I’m doing a unicast image (since I haven’t used the multicast image tab), typically it’s just the one client however I kicked off two not that far apart just to see if the speed would drop back on the first but that continued to rise whilst the first one started at about 5/6, but that’s more a slow climbing to begin with so I couldn’t see if both were capable of hitting 15+ together or if/when they’d peak.

@wayne-workman said in Climbing Imaging Speed:

It’s possible the network admin has implemented some sort of traffic shaping on your network that is causing this behavior.

I don’t think that’s the case as I’m able to move a file from the FP server down to my computer at 60-110MB/s so I don’t think there’s any shaping of that kind on the network.

It’s not really an issue though, I was just more curious as to why it does it as it does and whether it was a common thing or not which it doesn’t appear to be.

Just wondering whether anyone has climbing imaging speed when doing images?

When I start an image it will begin at around 5GB/min but the longer it goes the faster it gets, up to around 10-15GB/min. I don’t exactly think it’s peaking as I had two running two images side by side, one towards the end doing 15GB/min and the other doing 5-6GB/min which has it over 20GB/min and once the first one stopped it’s not as if the other one instantly jumped up, just a steady climb.

I seem to recall this happening with my other FOG set up in the past, not exactly an issue as it does the job I was just more curious as to why it does this and whether everyone experiences this or just myself?

I was wondering if when booting to FOG on a machine if another tab could be added with the ‘Advanced Actions’ type services.

Currently I believe there’s a Memtest86+ option. I guess the ‘Tesk Disk’ options would be nice but mainly for myself at this stage, I’d like the ability to fast/full wipe machines that mightn’t currently be on the FOG system that I’d be getting rid of without first having to add them to the system so I can set up a task to do a full wipe.

I’d try boot the laptop normally with the adapter connected to your laptop, open up cmd > type ‘getmac’ and get the mac for the usb hub.

Once you’ve got the mac, open up the fog server, create a new host and give it the mac address of the USB hub and also add ‘has_usb_nic=1’ to the kernel arguments.

From there, you want to give it the capture/deploy tasks and with any luck you’ll see a similar kind of issue but it telling you to remove the hub, reconnect and hit enter before continuing on with the process - maybe go through a dumb switch to ensure it gets network connectivity almost instantly once it’s plugged in again.

@Tom-Elliott said in Single disk, resizable - failed to set disk guid:

@dylan123 So the issue, if you’d like it fixed for now (I’ll relook at this code though).

Can you open the file, and add the /dev/sda components?

In other words make the file read as:

/dev/nvme0n1 dcfabb9e-4507-415e-b9a9-e437017df63b
/dev/nvme0n1p1 1:0C86C94F86C939CA 1:9c90a090-937d-4c9b-9a25-0381f463b590
/dev/nvme0n1p2 2:6CCA-8BF5 2:7e69ccb9-b499-4bf5-8528-293b71e42988
3:2de320a9-99b6-4191-aeeb-1c15e96fae1d
/dev/nvme0n1p4 4:CC34D93B34D9296A 4:b1911679-d848-4e8b-82fc-98616b55452e

Hey @Tom Elliott, tried the above code and that worked perfectly!

Will download the new init’s as suggested and see if that works also, thanks.

Hey @Tom-Elliott, see below for the content of that file -
/dev/sda dcfabb9e-4507-415e-b9a9-e437017df63b
/dev/sda1 1:0C86C94F86C939CA 1:9c90a090-937d-4c9b-9a25-0381f463b590
/dev/sda2 2:6CCA-8BF5 2:7e69ccb9-b499-4bf5-8528-293b71e42988
3:2de320a9-99b6-4191-aeeb-1c15e96fae1d
/dev/sda4 4:CC34D93B34D9296A 4:b1911679-d848-4e8b-82fc-98616b55452e

Server

• FOG Version: 1.4.0-RC-4
• OS: Ubuntu

Client

• Service Version:
• OS:

Description

Hey guy, created an image of a surface pro 3 60gb as a single disk, resizable. Pushed it to a 250gb surface pro 3 and I get an error at the end. The surface pro 3 then boots up fine and appears to work so I’m mainly just curious as to what the following error actually means (also means the task remains in the system because of the error) -

Not a huge problem as I can create and use the ‘not resizable’ option (would be nice for the 1-2 60gb Surface Pros we have). I was just wanting to know what this problem actually means as the computer I deployed the image to appears to be working fine.

@fry_p So if I’m understanding correctly, you’ve got your Surface with a USB hub directly connected to that. From that you’ve plugged in your surface adapter to one of those ports? Kind of makes sense with it struggling given it’s trying to get the IP from the other adapter.

I think to get this working together you’d want turn your surface on with the USB hub connected. CMD > getmac to figure out the mac address for both the HUB ethernet and the surface adapter. Then you can open up the fog dashboard, create a new host, manually add both mac addresses (making the surface adapter the primary one). Then under the FOG_KERNEL_ARGS section, add has_usb_nic=1. I imagine the next time you try to image it with all of that connected it should work.

With all of that said, do you really need to use the USB hub? Can you not just plug the surface usb > Ethernet adapter in directly? I haven’t done a full test with my 4 yet, but I know with the 3, the surface keyboard worked fine plugged in so I didn’t really have any need for the usb hub.

Out of interest Fry, looking at the image you’ve attached in the OP, is your surface still attached to the docking station as the charger looks like the fat one for the docking station rather then just the power lead which is much thinner? Just curious as to whether having that disconnected makes any difference as it might be trying to read the docking station USB interfaces instead o the one directly connected to the surface?

@Wayne-Workman said in Surface 3 - Unable to obtain DHCP:

@dylan123 I added the link to your solution post in the wiki. One day I (or someone else) can go through it all and make a formal article.

Sounds great, happy to help if required in more detailed instructions if needed

@Tom-Elliott said in Surface 3 - Unable to obtain DHCP:

@dylan123 So if you added has_usb_nic=1 to the FOG_KERNEL_ARGS field in fog settings, this would be the reason you “didn’t have to add it back”. This “flag” doesn’t automatically set itself, so the only way to have it “preset” is if you entered this in FOG Configuration Page->FOG Settings->Expand All->FOG_KERNEL_ARGS

Think I was half correct with what I said, I must have had the host with the mac still added. Interestingly though, I’ve found I don’t need that command for the surface 3s.

• So basically in the config > fog settings > fog_kernel_args section, that’s blank.
• In my host section, it only contains two laptops that are both the HP models I’ve been previously working with, no surfaces.
• I can then turn on any surface 3 and it will boot to the fog menu where I can either quick register it (not much point) or deploy the surface 3 image I took yesterday.
  *I did a quick register of the surface 3 given I thought it automatically added the has_usb_nic=1 to the arg section however it didn’t. It still added the surface to my list of hosts though
• I then tried with a surface 4, it booted to the fog section but when I selected ‘quick register’ I got then ‘unable to obtain DHCP address’ type error message which suggests for the surface 4, I need to have the has_usb_nic=1 argument.

Just thought it was interesting how that worked, probably come across that though with other people that have been trying to image surfaces.

Finally have some success!

I think it’s been a mixture of things that have made it work this time compared to other attempts. I just tried with ipxe7156.efi instead of ipxe.efi which is what I was trying the other day (I know I previously used ipxe7156.efi with no success) and I was able to quick register it and begin the capture process, rather interesting that it was able to do the quick register and create it’s own host kernel argument of the - has_usb_nic=1 without me having to put that in which is nice. Also had a dumb switch in the middle along with doing more updates so I’m not sure what part has fixed it for me but it appears to be working!

Process for mine which is basically very similar to Scott’s well written instructions but will add everything I’ve done in case it helps someone in the future:

DHCP Server Settings
067 - ipxe7156.efi

Fog Client Version
Upgraded to FOG 1.4.0-RC-4
Upgraded Kernel Versions so both bzImage and bzImage32 versions are 4.10.9

Connection Setup
Network > dumb switch > Microsoft Surface Ethernet to USB Adapter (model:1663) > Surface 3/4 (4 I’ve got to the quick register page, haven’t tested further yet).
Left Surface keyboard plugged in

Surface BIOS Settings
Turn Trusted Platform Module off
Turn Secure Boot off
Change boot so network is allowed rather than just SSD - Network > SSD

Choose whether to quick register a client or capture/deploy an image.

Once all the above is set up then it’s basically how you do any other FOG image apart from having to disconnect and reconnect the USB network adapter.

Steps -

1. Ensure setup is plugged in as mentioned in the connection setup above
2. Hold volume down, press power on and hold volume down until red Surface screen appears then let go
3. Surface should start booting into fog
4. When prompted to unplug USB Nic, plug back in and hit the enter on Surface keyboard
5. If you’re quick registering, you should be able to select that option. If you’re capturing/deploying, it should automatically begin that process as you’ve set in the task manager on your FOG system.

Thanks for your assistance @Scott-Adams @george1421 @Tom-Elliott @Wayne-Workman

Thinking aloud, I suppose there isn’t really a way to register all my Surface machines because since I’m using the USB adapters and they’re the device that contains the MAC address (as I found out when I tried register the Surface 4 only to find it was listed as the Surface 3 model I did the quick register for before). Not really the end of the world if that’s the case as I can still create the images required and then just deploy it to the Surface as I wish.

@Wayne-Workman said in Surface 3 - Unable to obtain DHCP:

@dylan123 Have you tried George’s suggestion about a powered usb 2.0 hub ? You should be able to get one for less than ten dollars online.

I haven’t yet Wayne mainly due to the fact Scott had success with the same adapter I’ve been attempting to use.

That said, I’m willing to buy one to test with as it would be great to be able to create images of our Surface 3/4s with FOG if possible

I imagine I should be able to buy any USB 2.0 to Ethernet adapter or is there a particular model/brand I should be looking at? I’ve been through some of the threads, particularly the one I linked earlier in this thread with Sarge and his Surface 4. He linked an Amazon 2.0 USB to Ethernet adapter but that’s currently no longer stocked so I can’t purchase that (probably take a while for it to be shipped to Aus anyways).

Think I’ll just go with this if I don’t need to be going for a particular brand/model - http://www.msy.com.au/peripherals/15841--edimax-eu-4208-usb20-10-100-ethernet-adapter.html

I could get one with USB ports as well but I’m thinking that might be a chance to cause another issue although it would be nice not having to swap from keyboard to Ethernet quickly!

Just giving this a bump to see if anyone else has any other ideas of what I can try?

Ran the latest update again to get 1.4.3 but still no luck.

Using USB ethernet, I get to the stage of unplugging and replugging before getting the error message -

Unplug and replug although when I unplug it says "usb2-port1: cannot disable (err = -32)
Failed to get an IP via DHCP! Tried on interfaces(s):

Using the dock with only ethernet connected it just fails to speak with the DHCP.

Both attempts have gone through a dumb switch as well just to ensure they don’t hang without connection to the network.

Maybe it just won’t work with the surface’s I’ve got, just thought I’d give this one final try.

@Joe-Schmitt said in Adding Machine to Domain using Active Directory:

@dylan123 said in Adding Machine to Domain using Active Directory:

So I’ve attempted to deploy an image onto the domain

Images should never be pre-joined to the domain, Active Directory is fundamentally incompatible with handling that scenario. Either use setupcomplete.cmd in sysprep to join the domain, or the FOG Client.

Yeah wasn’t the first thing I tried, more was testing it just to see if it made a difference.

Wasn’t aware the FOG Client was required to make the active directory feature work. Have since installed and tested, can confirm it worked.

Thanks for your help Joe.

Server

• FOG Version: 1.4.0-RC-1
• OS: Ubuntu 16.04.2 LTS

Client

• Service Version: Windows Server 2012 R2
• OS: Windows 10

Description

Hey all,

So I’ve attempted to deploy an image onto the domain however I’m getting this message when I attempt to log into the machine with an account on the domain “The security database on the server does not have a computer account for this workstation trust relationship.”

I believe the issue is on the DC rather then anything to do with FOG as the FOG section appears to work fine, I can put in an incorrect password and the above message goes away and it replaced with an incorrect username/password. I’m assuming there’s something I need to change on my DC but I can’t find what that would be, hoping someone else on here has come across a similar issue or has an idea of what I could possibly do to fix it?

Extra info:

On the server event log I do get a 5723 Event ID error with the following message -

---

The session setup from computer ‘L003’ failed because the security database does not contain a trust account ‘L003$’ referenced by the specified computer.

USER ACTION
If this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn’t require any action at this time. If this is a Read-Only Domain Controller and ‘L003$’ is a legitimate machine account for the computer ‘L003’ then ‘L003’ should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem:

If ‘L003$’ is a legitimate machine account for the computer ‘L003’, then ‘L003’ should be rejoined to the domain.

If ‘L003$’ is a legitimate interdomain trust account, then the trust should be recreated.

Otherwise, assuming that ‘L003$’ is not a legitimate account, the following action should be taken on ‘L003’:

If ‘L003’ is a Domain Controller, then the trust associated with ‘L003$’ should be deleted.

If ‘L003’ is not a Domain Controller, it should be disjoined from the domain.

---

Inside the DC it’s not creating the machine when it attempts to add the computer. I have tried to manually create the machine then deploy it again but I still get the same issue.

I’ve also tried adding the laptop to the domain, capturing it, giving the computer a new name both using the AD section and not and deploying the image but I get the same issue as above every time. If I put the name back to what it was when I had it on the domain for the capture and redeploy with that it works.

So obviously the issue is that for whatever reason it’s not creating the machine in the DC however I’m not sure what I should be looking at for that. Everything online with the above event ID error just says to remove the machine from the domain and re-add it however that defeats the whole purpose of it.

Any thoughts/ideas would be great.

@Scott-Adams Yeah Surface Pro 3.

Build version is 14393 for both the 3’s based on what it says in system information.

@Scott-Adams Thanks for the clear instructions Scott, gave it a shot but didn’t work unfortunately.

• Added mac address manually by going host > create new host, as suggested and it skips the countdown window like it knows the task it has been assigned (capture).

• It says it received DHCP answer on interface net0, speaks to fog server before going to next page

• message at top says - i8042: Can’t read CTR while initializing i8042

• continues on, says to unplug your device and replug as you suggested.

• Unplug and replug although when I unplug it says "usb2-port1: cannot disable (err = -32)

• hit enter and plug usb Ethernet back in quickly

• Failed to get an IP via DHCP! Tried on interfaces(s):

• Says to check network set up and try again. Eventually says press enter to continue.

• ssh-keygen generating new host keys

• starting sshd: ok

• then I get these four lines -
  In: failed to create symbolic link ‘/dev/fd/fd’: No such file directory
  In: failed to create symbolic link ‘/def/stdin’: File exists
  In: failed to create symbolic link ‘/dev/stdout’ : File exists
  In: failed to create symbolic link ‘/dev/stderr’: File exists
  Running post init scripts…

• Next page, No network interfaces found (verifyNetworkConnection)
  args passed:
  Kernel variables and settings - which is rather long so I won’t bother typing unless it will be of use.

ev/fd/fd no such file or directory
failed /dev/stdin: file exists.

---

These were all tried with ‘has_usb_nic=1’ in the host kernel arguments and I tried ipxe.efi, ipxe7156.efi, snp.efi and snponly.efi

When it says it failed to get DHCP, tried on Interface(s): and it doesn’t list any, I feel that is where it might be going wrong but that’s just a guess on my part.

@Tom-Elliott Thanks Tom, added that in the section you suggested however it’s still not behaving as it should.

Boots to the FOG menu and with the countdown I plug in the surface keyboard so I’m able to select one of the options - any time I unplug the USB Ethernet adapter and put in a keyboard, the keyboard will not respond. Also tried from the docking station with the keyboard and USB adapter but same issue as below.

Once I select my option (whether it’s through using the dock or the surface keyboard), I do get the unplug/replug message as Scott mentioned. When I unplug it, it says "startusb usb2-port1: cannot disable (err = -32). Hit enter and it sleeps for 5 seconds before I get the "Failed to get an IP via DHCP! Tried on interfaces(s): " Also tried not removing the USB adapter and just hitting enter but It’s still unable to get a DHCP address.

When I check to see whether the machine is compatible with FOG, it’s still not able to determine its own mac address when I select that setting so the change to the kernel hasn’t appeared to have helped.

@Scott-Adams Thanks for the suggestion Scott, to be able to add the kernel argument, you need to be able to register the host first right? I’m unable to register my surface with either the quick or the full register (get the same error back as seen in the 3rd picture). Or is there another way to add the kernel argument?

Also since you’ve had success with your adapter, what model is it? I’ve got the 1663 so just curious as to whether we’re using the same one or not as it would help determine whether that’s part of my issue or there’s something else that needs to be done.