Last active [hidden]
Everything you need can be done with Sysprep.
CloneDeploy will modify the file to rename the computer.
The answer file will join to the domain for you, no CloneDeploy process required
The answer file can specify the OU, you can then use CloneDeploy sysprep tags to modify the OU for different computers if you want.
Therefore you would only need 1 sysprep answer file without any additional scripts.
Is there any software that could be doing something to the partition table? Since the upload worked before you installed all the software, that would be my guess. Is there any security software?
1.) What screen did it stop on?
2.) Did the mac pro come with Sierra or High Sierra?
Upgrade windows version to 1.3.3 if not already
Export the database
Install 1.3.3 on Linux following the guide
Import the database
Update the distribution point passwords in the web ui
Can you attach your web.config
Is the computer registered?
In your apache config for clonedepoy, clonedeploy.conf, do you have this block?
<Location "/clonedeploy/public/macos_nbis"> Allow from all Order allow,deny SetHandler default-handler </Location>
If so try changing the location to /clonedeploy/api/public/macos_nbis
You should be able to check the apache access logs to see what's happening
It should only take about 5 minutes. Guessing that something still is not setup correct. If the Mac can't find the nbi it won't error out. It will just look like it's copying when it really isnt
How long is forever?
What exact OS version did you make an NBI from? There is a bug with High Sierra that causes the transfer to take too long, sometimes.
You can move the NBI anywhere you want, it just needs to be served from a web server, can't use smb.