Yes i think you can move it where you want, just put the right UNC link in your script.
But what the size of your image ?
The OS drive that I imaged is 20GB I made the primary partition as small as possible as suggested in the docs. The actual deployment files created (the .tbi and accompanying files) are about 10GB.
Can I just copy the .exe or do I need to move across and dll's or any associated files that the exe may use?
For sure, copy all the files..
1 of 1 people found this helpful
You would only need to move the Imagew.exe. It is a stand alone exe.
This may be a dumb question, but are you using preferred servers or are you writing different templates to call the files from the different servers?
Right now I have everything manually pointed to one server. I have not gotten to setting up preferred servers yet. After folloing the docs step by step for things that I have done so far LD OSD seems very fickle and a pain in the rear. I am working towards getting provisioning set up. Now that I have my image working and my software packages working. Although am I missing something that when doing provisioning you have to manually add the machine into LD first? You can't just PXE boot the machine and kick of the provisioning process? several other apps that I have used allow you to do that and it seems counter productive to have to boot up the machine to get mac info etc. and have to manually add the machine into LD before you are able to start provisioning.
Or am I just royally missing something?
Thanks again guys.
All you really need is the MAC and to know what the device name will be. You add it (takes a few seconds) and when the process is complete the device has been properly name and joined to the domain. If the device already had an agent or is otherwise searchable in the console then of course you will not have to add it bare metal.
If the images are pulling from a local resource then it certainly should not be taking the amount of time you are describing and the location of ImageW will not be the issue.
I permit to use this topic to talk about long time for OSD deploying.
I have the same thing, about 1h30 for +/- 20 Go, i use local resource.
Do you know what i have to check ?
Thanks to all of you guys for your input. I moved everything over from my datacenter and am running the entire deployment system on a local gigabit switch and it is taking 30 minutes capture an image and just shy of an hour to deploy. So it seems like most of it is some sort of latency or routing in the network