1. 3 weeks ago

    So after some messing around i have got 1.3 to a point where i can boot into the Sierra NBI. But when the clonedeploy_login.command it tells me it can't contact CloneDeploy Server. I know the stable version has a "service" within the "web" folder where the client.asmx file resides that is normally called when the script is ran. However on 1.3 beta i noticed there is no "service" folder aynmore? Should i edit the /usr/local/bin/weburl file to point it to another service on the 1.3 server?

  2. clonedeploy

    Oct 2 Administrator

    Did you use the new autoclonedeploynbi? Yes the service url did change, it's now just base url. So it would just be something like

    I would probably hold off on doing anything. I'm planning on releasing 1.3.0 very soon.

    On a side note: The macOS imaging environment didn't get much attention. But some tests with Sierra were positive, core storage is definitely not working. I'm not sure if it makes much sense to continue the mac environment with Apple's latest anti-imaging moves. Currently everything I've read states that high sierra cannot be imaged, more specifically APFS.

  3. Yeah i read some stuff about that too....seems Apple is always moving one step back when it comes to enterprise. Luckily this guy is at least still working on the AutoCasperNBI & AutoImagrNBI


or Sign Up to reply!