FileWave Alliance

The Official Community Forum
  • Page:
  • 1

TOPIC: IVS wait time to start image

IVS wait time to start image 24 Jul 2017 22:22 #2626

  • Jeff Uchtman
  • Jeff Uchtman's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 7
  • Thank you received: 0
How can I cut down the ridiculous 90 second wait to start imaging a machine to say 10 seconds? If I started to image, I really don't need 90 seconds to back out.

Thanks
-jeff

IVS wait time to start image 26 Jul 2017 16:43 #2627

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 103
  • Karma: 4
  • Thank you received: 13
Are you talking about the NetBoot or PXE process before the image is restored? If so I don't think there's a way around that. Otherwise I'm not sure what other delay you're talking about.

IVS wait time to start image 26 Jul 2017 17:48 #2628

  • Jeff Uchtman
  • Jeff Uchtman's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 7
  • Thank you received: 0
The 90 second wait before the imagining starts Bao. Glad to see your monitoring the forums !

IVS wait time to start image 26 Jul 2017 21:25 #2629

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 103
  • Karma: 4
  • Thank you received: 13
I think you already got your answer directly via email from someone else but for anyone else interested I wanted to post the solution here. This is not supported in any way so if you break your IVS you're on your own.

1. Edit line 507 in the /imaging/resources/generic/bootup_script.app/Contents/Resources/bootup_script.py file on the IVS and change default=90 to your desired value. BE SURE TO MAKE A COPY OF THIS FILE FIRST.
2. Delete the existing NBI with rm -rf /imaging/netboot/NetBoot/NetBootSP0/Image.nbi.
3. Download the NBI script and run it again to replace the NBI you deleted in the previous step.

IVS wait time to start image 26 Jul 2017 21:53 #2630

  • Jeff Uchtman
  • Jeff Uchtman's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 7
  • Thank you received: 0
Yes I did Bao. I am seeing some black screen boots after imaging. Seems a reboot will take care of it but the machine fails to name at that point. Do you know anything about this?

-Jeff

IVS wait time to start image 26 Jul 2017 22:04 #2631

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 103
  • Karma: 4
  • Thank you received: 13
Sorry, I don't. I've never seen that behavior when reimaging my Mac.

What kind of name is assigned to the client? Are you using a placeholder entry or is this an existing Mac? Someone mentioned the possibility of invalid characters like extra spaces or special characters in the placeholder computer name. Aside from that suggestion I can't think of anything else.

IVS wait time to start image 27 Jul 2017 12:34 #2632

  • Jeff Uchtman
  • Jeff Uchtman's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 7
  • Thank you received: 0
I just checked and we did have a space in the placeholder. I will give it another try. Thanks for the tip.

-Jeff

IVS wait time to start image 28 Jul 2017 00:10 #2635

  • Jeff Uchtman
  • Jeff Uchtman's Avatar Topic Author
  • Offline
  • 2nd Level - Yellow Belt
  • 2nd Level - Yellow Belt
  • Posts: 7
  • Thank you received: 0
<rant>OK, cut the wait time down from 90 seconds to 10 seconds, good. Changed appliance NICS from E1000 to VMXNET3 (1Gb to 10GB) good but should have been done by FileWave. Now the netboot time. Over 3 minutes and 45 seconds of which 1/2 the time the NIC is not doing much of anything. Another wait time built into the netboot script, not sure. I can image a single machine in 5 minutes and 42 seconds (11GB compressed image), not bad but can I get it lower? When facing thousands of machines to image and High Sierra a distant hope for true slim imaging every second counts. Any ideas? </rant>

Thanks
-Jeff

IVS wait time to start image 03 Aug 2017 17:55 #2644

  • Bao Tran
  • Bao Tran's Avatar
  • Offline
  • FileWave Staff
  • FileWave Staff
  • Posts: 103
  • Karma: 4
  • Thank you received: 13
The OVF defaults to the Intel E1000 because that's the only adapter that's also supported by VirtualBox. Some customers import the IVS into VirtualBox rather than VMware.

The most obvious way to scale is to have multiple IVS's with each one supporting a single to a few subnets (depending on the size of those subnets). Of course you'd have to modify your IP helpers for each subnet to point to their assigned IVS.
  • Page:
  • 1