Last active 2 weeks ago
I thought i would add this as well that i found. Apparently HighSierra has a build in command line utility that can install packages post install...so this could be interesting to use in a NetInstall session....
The big draw back of DeployStudio is the fact that it needs to be ran on Apple hardware. That's what made CloneDeploy so awesome, the fact that i run it on Windows Server VM in my VMware ESXi environment. I think it's comical how apple requires Apple hardware to run their Server OS, yet they don't make any enterprise grade rack mountable hardware anymore more...It makes me want to ask them "So what do you have in your data center in Cupertino? 500 Mac Mini's all stacked on top of each other?". If Apple could just check their pride at the door and allowed there server software to be licensed to run on ESXi on any blade severs then none of this would be an issue...but they will never check such pride as long as they can sell Mac Mini's to suckers who need them....
So i sat through Apples tech update today where they spoke about the death of monolithic imaging. The reason this will not work with APFS volumes boils down to the fact that in order to update a system to High Sierra, the installer physically updates the machines firmware in order to support the new file system. That being said, one way around this (as promoted by Apple at this event) was to go back to the old NetInstall method. So in theory, clonedeploy could be used to mimic Apple NetInstall instead of Netboot in order to do an actual install of the OS which in turn will trigger the firmware update install on the client. After the install i would think it would be possible for clonedeploy to THEN install an MDM/Munki agent in order to pull down the apps needed? I'm not saying this would happen anytime soon as we all know you are super busy, but i just wanted to give you some insight into my takeaway from the event today in hopes it saves you some time and research.
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
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?
Ok no problem i know it's beat. I'll mess around with it more and report back if i find anything. Thanks!
I'm starting to think it has to be something with Server 2008 R2 not being compatible with the installer? Comparing your folder structure in IIS with the one i have it seems like i am missing folders that should be installed? I also used this guys suggestion because i ran into the same issue as him where i had to add the clonedeploy site manually in ISS because the installer never created it. Here is a screen shot on my IIS view.
HTTP Error 404.0 - Not Found
The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.
Detailed Error Information
Module IIS Web Core
Error Code 0x80070002
Requested URL http://clonedeploy.natickps.org:80/clonedeploy/api/token
Physical Path C:\Program Files (x86)\clonedeploy\frontend\clonedeploy\api\token
Logon Method Anonymous
Logon User Anonymous
Judging by the logs and from what i see in the database it looks to me like it has something to do with the user token?
2017-09-27 13:20:00,456  DEBUG FrontEndLog Error With Token API: System.Xml.XmlException: '"' is an unexpected token. Expecting white space. Line 1, position 50.
at System.Xml.XmlTextReaderImpl.Throw(Exception e)
at System.Xml.XmlTextReaderImpl.DtdParserProxy.System.Xml.IDtdParserAdapter.Throw(Exception e)
at System.Xml.DtdParser.ParseExternalId(Token idTokenType, Token declType, String& publicId, String& systemId)
at System.Xml.DtdParser.ParseInDocumentDtd(Boolean saveInternalSubset)
at System.Xml.DtdParser.Parse(Boolean saveInternalSubset)
at System.Xml.DtdParser.System.Xml.IDtdParser.ParseInternalDtd(IDtdParserAdapter adapter, Boolean saveInternalSubset)
at System.Xml.Linq.XDocument.Load(XmlReader reader, LoadOptions options)
at System.Xml.Linq.XDocument.Parse(String text, LoadOptions options)
at RestSharp.Deserializers.XmlDeserializer.Deserialize[T](IRestResponse response)
at RestSharp.RestClient.Deserialize[T](IRestRequest request, IRestResponse raw)
Also below the login button on the web UI it says "Could Not Contact Token API"