tag:blogger.com,1999:blog-6922655.post7982023991404729369..comments2024-02-20T06:12:25.537-05:00Comments on Chuck Steel: Deploying Winclone Image Packages with DeployStudioChuck Steelhttp://www.blogger.com/profile/09752674139617832756noreply@blogger.comBlogger34125tag:blogger.com,1999:blog-6922655.post-79183704675027253892017-01-31T14:18:51.290-05:002017-01-31T14:18:51.290-05:00@Chuck Steel thank you. It worked the second time....@Chuck Steel thank you. It worked the second time. As far as non-sysprepped windows packages, any suggestions on what to do in those situations? I used the same work flows as your tutorial, but get the "bless" error when trying to start into the Windows partition. MrTech2017https://www.blogger.com/profile/09146446490291486917noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-87248489625970894582017-01-30T14:21:04.561-05:002017-01-30T14:21:04.561-05:00@MrTech2017 My guess is that one of your packages ...@MrTech2017 My guess is that one of your packages isn't completing installation. You can try netbooting again and looking at the DeployStudio finalize log to see what might be hanging up. You can also check the /var/log/install.log.Chuck Steelhttps://www.blogger.com/profile/09752674139617832756noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-40703150159326361772017-01-30T09:41:20.951-05:002017-01-30T09:41:20.951-05:00This comment has been removed by a blog administrator.MrTech2017https://www.blogger.com/profile/09146446490291486917noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-84005015590825735042017-01-30T09:41:20.451-05:002017-01-30T09:41:20.451-05:00This comment has been removed by a blog administrator.MrTech2017https://www.blogger.com/profile/09146446490291486917noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-61421193375662743992017-01-30T09:39:59.469-05:002017-01-30T09:39:59.469-05:00I'm running into a minor issue where it keeps ...I'm running into a minor issue where it keeps running "installer:PHASE:Running Package scripts..." over and over again and doesn't stop. This is after everything has been run and it is doing it in the DeployStudio Finalize script log. Any thoughts? Is it safe to stop it and assume all went through?MrTech2017https://www.blogger.com/profile/09146446490291486917noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-633602630481972912017-01-24T15:16:18.207-05:002017-01-24T15:16:18.207-05:00@Chuck Steel, thank you for all your help. All of ...@Chuck Steel, thank you for all your help. All of the scripts ran before the package install. It's been sitting on that step for about 10 minutes, so I'm hoping for the best! Any input on the average time the step will usually take? Thank you once again for all of your help. ThinkB!G_techhttps://www.blogger.com/profile/14681061829881547949noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-36573083561576057872017-01-24T14:21:56.226-05:002017-01-24T14:21:56.226-05:00@Chuck Steel
It looks like I saved the link and i...@Chuck Steel<br /><br />It looks like I saved the link and it added a bunch of unnecessary lines. Going to try again by just copying the script directly instead of saving the link. Will try again! Thank you. ThinkB!G_techhttps://www.blogger.com/profile/14681061829881547949noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-15169035913167811332017-01-24T13:57:41.407-05:002017-01-24T13:57:41.407-05:00It looks like you have an error in the disable_sip...It looks like you have an error in the disable_sip.sh script, make sure that the syntax is correct and there aren't any special characters that might have been inadvertently copied.Chuck Steelhttps://www.blogger.com/profile/09752674139617832756noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-32791670854256511472017-01-24T13:17:42.296-05:002017-01-24T13:17:42.296-05:00@ThinkB!G_tech, check the DeployStudio logs to see...@ThinkB!G_tech, check the DeployStudio logs to see if one of the steps failed. What is in your workflow after the disable_sip script?Chuck Steelhttps://www.blogger.com/profile/09752674139617832756noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-45693818153221168292017-01-24T13:04:55.553-05:002017-01-24T13:04:55.553-05:00I have a 2016 MacBook Pro with touchpad (1TB Fusio...I have a 2016 MacBook Pro with touchpad (1TB Fusion Drive). I did everything to the tee on your list for making all the workflows. The Mac partition installed, then the disable_spi script ran as well. After that, it just booted to the Mac partition. I'm stuck after that because it didn't even attempt to run any of the other scripts or install the winclone package. Any thoughts?ThinkB!G_techhttps://www.blogger.com/profile/14681061829881547949noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-78130812283033284722017-01-09T16:27:35.785-05:002017-01-09T16:27:35.785-05:00I can confirm I was able to use WinClone 4.4 and c...I can confirm I was able to use WinClone 4.4 and created a Windows 10 image on 10.11.6 iMac. I Shrank it and made it "Make Self Extracting..." and used DeployStudio 1.6.15 that was built on 10.10 and running on a Mac Mini server running 10.6.8. I know what a mouth full but it worked for me!! Our next CAD Lab will be Windows Machines as they spend most of their time there anyway. Just wanted to share my experience in getting this to work and not getting the "waiting on pigz" message. Good luck!TechGuyhttps://www.blogger.com/profile/08124133021765484470noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-19248427918427544562016-07-08T10:09:45.148-04:002016-07-08T10:09:45.148-04:00I'm sure i'll post it to ITNinja, i've...I'm sure i'll post it to ITNinja, i've posted some things there before... <br /><br />It actually ended up being pretty simple. <br /><br />I split the partition equally, boot off a UEFI USB thumb drive i created with KACE. I build my image in Audit mode, so i take the same image i use on my Dells and create a pre-install task to set up the disks properly and then KACE pushes the image to the appropriate partition.<br /><br />Once the image is on the mac, i boot back to mac and tell WinClone to allow the partiton to be EFI bootable. This is the hardest part. If i knew what this code was, we could automate it some more. Once that's set you're all done! boot back to the Windows partition and let KACE do it's magic. I do have to have a post-install for the chipset drivers, but other than that it's pretty much the same as my PCs.<br /><br />-SteveSCDavishttps://www.blogger.com/profile/15364853741284290939noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-14332790161840987132016-07-08T09:51:52.512-04:002016-07-08T09:51:52.512-04:00Thanks, @SCDavis. I would be interested in seeing ...Thanks, @SCDavis. I would be interested in seeing what you've done. Perhaps you can post it on ITNinja for others to see?<br /><br />Yes, my process does leave SIP disabled. You could enable it by booting into the DeployStudio runtime again and running the appropriate commands, but since I can't easily automate that part I made the decision to leave it disabled. There are ways to automate that entire process but I'm just being lazy at this point.Chuck Steelhttps://www.blogger.com/profile/09752674139617832756noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-16191048133699014912016-07-08T09:39:56.525-04:002016-07-08T09:39:56.525-04:00Hey Chuck,
Not sure if interested, but i've b...Hey Chuck, <br />Not sure if interested, but i've been able to get my Win10 image deployed to my new macs (16,2) using KACE. I could give you more info on my process if interested.<br /><br />I'm wondering if your SIP script permanently disables SIP on the macs. that's one of the main problems we're seeing as we don't want to have to touch all our macs.<br /><br />-SteveSCDavishttps://www.blogger.com/profile/15364853741284290939noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-20938010239750610142016-06-08T11:46:13.809-04:002016-06-08T11:46:13.809-04:00@Retro Robot I was having same issue with DS 1.7.2...@Retro Robot I was having same issue with DS 1.7.2 and NBI 10.11.X hanging with my winclone at "waiting for pigz". It's something with 10.11.X NBI. The very instant I netbooted to 10.10.X NBI, it no longer hung at "waiting for pigz"Anonymoushttps://www.blogger.com/profile/13769348963693808345noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-14175493597916622922016-06-06T14:04:58.755-04:002016-06-06T14:04:58.755-04:00Thanks for following up,
I did a lot of test and...Thanks for following up, <br /><br />I did a lot of test and I figured out that the script was not running correctly with blank spaces. Maybe it's the way I copied it from web and saved it. I rewrote most of what I needed in another file and it worked perfectly. <br /><br />Everything's good for now. Just need to perfect my Windows 10 master image.Anonymoushttps://www.blogger.com/profile/17334970242730726513noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-80871434714376133532016-06-06T12:34:23.642-04:002016-06-06T12:34:23.642-04:00An update to @mrcil20's comment. It looks like...An update to @mrcil20's comment. It looks like DeployStudio might delete the /etc/deploystudio folder before the bootcamp naming script runs. I'm not sure what would cause that but one solution is to have the scripts copy the tools and bootcampname file to /etc/ds_tools instead of /etc/deploystudio/ds_tools.<br /><br />I'm not sure if this will work well on a fusion drive, I would recommend checking the WinClone documentation on that front.<br /><br />I have not seen the two Macintosh HD problem in my environment.Chuck Steelhttps://www.blogger.com/profile/09752674139617832756noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-36980957348407193532016-06-03T19:41:02.489-04:002016-06-03T19:41:02.489-04:00Hi Chuck,
This is a great write up. I'm hoppi...Hi Chuck,<br /><br />This is a great write up. I'm hopping to try it on Monday. Can I use this same workflow on a fusion drive? if not any suggestions? I also have run into the same issue as @Grendizer<br /><br />On reboot holding the Option Key, I am presented with two Macintosh HD along with the Windows. If I select the 2nd Macintosh it boots the same OS has the first Macintosh HD. Grendizer said...Anonymoushttps://www.blogger.com/profile/13064655675589683057noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-50123251947851883322016-06-02T11:09:10.456-04:002016-06-02T11:09:10.456-04:00Thanks for this. I have followed your directions ...Thanks for this. I have followed your directions perfectly but I am getting the error, Cannot bless. Any ideas? Unknownhttps://www.blogger.com/profile/15252332265800591312noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-7298869918985455662016-06-01T10:22:22.792-04:002016-06-01T10:22:22.792-04:00@mrcil20, when you created the workflow did you in...@mrcil20, when you created the workflow did you include step 2, h? It sounds like the script that sets the computer name isn't running. Make sure that step happens after the Winclone image is deployed.Chuck Steelhttps://www.blogger.com/profile/09752674139617832756noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-8287260678590986762016-06-01T09:30:04.279-04:002016-06-01T09:30:04.279-04:00Hi Chuck,
I use your walkthrough to clone my d...Hi Chuck, <br /> I use your walkthrough to clone my dual boot macs and it helped me a lot. Thanks.<br />I have a problem though with my windows computer renaming.<br /><br />As far as I can see, my Deploystudio database Windows name gets in the /etc/deploystudio/bootcampname file correctly but when I check in my sysprep file before starting Windows, the * string is not replaced with what's in the file and I don't know how to debug this. Nothing special about this in the logs.<br /><br />Can you help me debug this?<br />Thanks a lot!Anonymoushttps://www.blogger.com/profile/17334970242730726513noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-57715644258398570322016-02-19T16:07:43.930-05:002016-02-19T16:07:43.930-05:00@Retro Robot I have seen many issues when the serv...@Retro Robot I have seen many issues when the server is running 10.11.x and is a deploy studio server.cem62793https://www.blogger.com/profile/11652505699525125827noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-43193114686861463012016-02-19T15:41:49.430-05:002016-02-19T15:41:49.430-05:00The libraries required by pigz aren't included...The libraries required by pigz aren't included in the DeployStudio Netboot set, so the .winclone image won't deploy. You can read more about the issue here:<br />http://www.deploystudio.com/Forums/viewtopic.php?id=7518<br />Chuck Steelhttps://www.blogger.com/profile/09752674139617832756noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-88452682259276471762016-02-19T15:24:26.310-05:002016-02-19T15:24:26.310-05:00@cem62793 I am running DS v1.7.2 on OS X 10.11.3 w...@cem62793 I am running DS v1.7.2 on OS X 10.11.3 w/ Server v5.0.15. My DS netboot set was created in this environment as well. Attempting to deploy a Windows 7 image captured with Winclone Pro 4.4 and deployment to a MacBook Retina Mid2012 running OS X 10.11.3. Retro Robothttps://www.blogger.com/profile/01684074358373110692noreply@blogger.comtag:blogger.com,1999:blog-6922655.post-78261198774118537592016-02-19T14:56:10.516-05:002016-02-19T14:56:10.516-05:00@Retro Robot Are you running the latest version of...@Retro Robot Are you running the latest version of deploy studio, also what version of the OS is your deploy server running?cem62793https://www.blogger.com/profile/11652505699525125827noreply@blogger.com