Last active 2 months ago
So we all know now that Apple has made it not possible to upgrade machines from Sierra to High Sierra using standard imaging. I believe High Sierra and later will still be able to be imaged, but going from Sierra to High Sierra is essentially like going from OS 9 to OS X. I just want to let people know that CloneDeploy can still be used if you build a NetInstall set instead of a NetRestoret set. This allows you still run a windows server running clonedeploy to deploy to macs. What's different about the 2 is that NetRestore would just copy an image down to the drive and call it a day. Well in order for any machine to run High Sierra, the client is required to do a firmware update that can only be triggered via an actual install. So that being said, just create a second Clonedeploy server and instead of creating a NetRestore.nbi use Automator or System Image utility to create a NetInstall.nbi. This will allow you to "netboot" your Mac clients to the actual High Sierra installer Via Netinstall and perform the upgrade.
We also use Munki here where i work too, so we just add the munkitools.pkg to the automator workflow so that once the OS finishes installing, it installs munkitools and the client checks in with munki and pulls down and installs the required applications for the device. This is the best workaround i have found so far until we get all our clients to High Sierra where we can then mess around with testing imaging again.
Hope this helps,
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.
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"
I have tried clean installing 4 times and for the life of me i can't log into the web UI with clonedeploy/password? I even tried a tip i saw on here with editing the password for user clonedeploy in the database but still nothing? Am i missing something? Is there a new username and password? I'm running this on server 2008 R2 in case that matters. Thanks!