You are not logged in.

Announcement

[2017.09.08] DeployStudio build v1.7.8 (checksum, release note).
[2016.08.26] DeployStudio build v1.6.19 (release note).
[2013.02.23] DeployStudio last universal build v1.5.17 (release note).

#1 Re: Future » macOS Server Changes » 2018-04-12 23:14:14

> admin wrote:

> Hi guys, we do not plan to port DeployStudio Server to another platform.
If the T2 ship with secure boot and disk encryption is generalized to the whole Mac family, there will be no more space for monolithic and modular imaging.
In that context we believe that DEP/VPP/MDM is the way to go.

So, we’ll do our best to support current hardware as long as macOS supports imaging, but it’s time to get prepared for modern deployment programs and solutions.
----------------------------------------------------

The question now is, what is the future of Deploy Studio?  Modern deployment programs and solutions, in their current state, is so slow...  Also, it is VERY hard to deploy custom configurations that exist to all users using something like JAMF.  Hell, I have better luck with Apple Remote Desktop sending out these configurations than with JAMF.  My main concern with the new chip is the lockdown of the User Template area.  I use that extensively in my labs. If I can't get there, my job is going to be even harder.

#3 Re: Future » New iMac Pro is the End of Mac Imaging! (Redux) » 2018-03-06 23:51:58

> joopjuh wrote:

> An iMac Pro will not NetBoot as it will not accept it or appear when you boot with alt.
You can select it as a startup disk but that will not work.
What works is an external drive created with the deploystudio assistant.
This will boot the device (when you allow it to. Lower security in the recovery mode) and start up deploystudio connecting to your servers.
Next step is to find out what the best way is to deploy an image on the device.
I've been able to deploy AFPS images onto other machines however this device is different and comes with extra's which will need to be investigated before i deploy anything.


Look forward to your findings.

#4 Re: Future » User Template package » 2018-03-06 23:50:31

The process is essentially the same as it has been in days past.  The kicker is that you have to disable SIP before you do anything.  After that, the process is the same.  Typically, I will re-enable SIP once I am done.

#5 Re: Future » Will Deploy Studio continue to be updated ? » 2018-02-08 19:30:33

I totally agree...  Thank you for all your hard work and efforts.  I hope that Apple's new way of doing things doesn't derail DS.  I like DS FAR more than I do JAMF.

#6 Re: Debug » Deploy Studio Working in 10.13.2 » 2018-01-25 18:11:32

> woneal1983 wrote:

> So for everyone having issue with Deploy Studio using High Sierra i might have a fix. After setting everything correctly like my 10.12.6 server i kept getting restarts when loading. It would get to about 1/3 the way and restart. I first thought it might be the NBI file so i tried different ones. None worked. I even tried my 10.12.6 one that i had and kept getting NFS mount refused errors. At first i didnt think nothing of it until i came across a programmed called NFSManager. Once loaded, I checked the server shared descriptions. There were none. This was odd because there should have been one or two there. SO i added the shared deploystudio folder, the netbootsp0, and the netbootclientssp0 folders. I also made sure they could be mounted inside the folder and that everyone could get to them. After doing that i can now deploy images with my server being 10.13.2 now.

>I think 10.13.2 has an issue with NFS so my guess in the next update there needs to be a fix to where the NFS folders are added correctly because i think this is the issue alot of people are having. I hope this helps people out. It took a a week to figure this out. Thanks

>Edit: The program is free but it will pop up for you to buy. Just fix the NFS stuff and your golden. I know DJ or Tommy will read this but your welcome. :)

Can you expand on this a little?  I don't know what you are talking about with the server shared descriptions.

#7 Re: Usage » Repository access error » 2017-12-20 20:05:48

Only have a couple minutes, but I’m not jumping subnets at all. This is just to get it to work on one subnet. When I cross subnets, I boot from a USB NetBoot drive that points to the server. I’m trying to get my network guys to put all my labs on one subnet so I don’t have to deal with Flashdrives.

#8 Re: Usage » Repository access error » 2017-12-20 00:25:16

I was able to get the repository to mount on 10.12.6 after a handful of things were in place.

1. static IP
2. hostname associated in DNS with that static IP
3. DS admin pointing to hostname (not IP)
4. NetBoot set pointing to hostname (not IP)

If any one of these points at the server's IP, the repository will not mount...either locally or on computers that have been Netboot.

10.13.2 however, I am not even getting that far.  DS is telling me that the NetBoot set is completed successfully, but when I try to boot from it, something fails, and the computer restarts.  The server is a 2017 iMac that came with Sierra on it, the computers I am trying to boot with are also 2017 models, but they come with SSD's and High Sierra installed from Apple.  I am about to go on winter break, I am probably going to ask if I can take one of the newest iMac's home to play with. 

This is so frustrating.

#9 Re: Usage » Repository access error » 2017-12-13 18:27:20

> hqonline wrote:

> > Trikster wrote:

> Wish I had better news for you here...  I have the same issue on multiple machines running the same server, OS, and DS versions.  I can easily remote into the server with AFP and SMB, using the credentials that DS uses.  Repository on DS...no luck.

Here is my post regarding the issue: http://www.deploystudio.com/Forums/viewtopic.php?id=7978

Have yet to figure out a solution. I have recently got my hands on a 2017 model iMac with Sierra on it.  I am going to put HS on it along with DS to see if its the relative age of the computers I usually use that is causing the issue.


Hi

Iv'e re-installed my server with 10.12 now and running 5.3.1. In 5.4 file share service is missing but in 5.3 it's there. Hopefully this will work again.

Thanks for answering.

Regards,
hq
---------------------------

On Server 5.4, the file share service is in the Sharing Pane of System Preferences.  Why Apple thinks this is somehow better, I am not sure.

#10 Re: Future » New iMac Pro is the End of Mac Imaging! (Redux) » 2017-12-13 02:04:23

Seems that Apple has forgotten that there are lab computers that need custom configs in the User Template...  Can't really do that kind of stuff with Jamf.  Why does Apple not like imaging?

#11 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2017-12-06 04:22:58

It would be great if the DS team would chime in. My organization just got JAMF, which is fine for individual computers. It sucks for labs that have custom configurations.

#12 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2017-11-22 23:08:41

> cem62793 wrote:

> > Trikster wrote:

> > cem62793 wrote:

> I have been able to deploy a HFS+ copy of High Sierra with the workflow we use for everything else. It does give quite a few errors but it does finish successfully. The thing to note is I had to create the deploy image for the HFS+ copy of High Sierra using Deploy Studio not AutoDMG.

Did you have to do anything special to capture the image?  I have been unable to do that either.

I just installed high sierra on a md101, used the users reset script and then captured the image with the deploy studio workflow for creating a master from a volume.

Users reset script?

#13 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2017-11-15 18:21:13

> cem62793 wrote:

> I have been able to deploy a HFS+ copy of High Sierra with the workflow we use for everything else. It does give quite a few errors but it does finish successfully. The thing to note is I had to create the deploy image for the HFS+ copy of High Sierra using Deploy Studio not AutoDMG.

Did you have to do anything special to capture the image?  I have been unable to do that either.

#14 Re: Usage » Repository access error » 2017-11-13 18:12:38

Wish I had better news for you here...  I have the same issue on multiple machines running the same server, OS, and DS versions.  I can easily remote into the server with AFP and SMB, using the credentials that DS uses.  Repository on DS...no luck.

Here is my post regarding the issue: http://www.deploystudio.com/Forums/viewtopic.php?id=7978

Have yet to figure out a solution. I have recently got my hands on a 2017 model iMac with Sierra on it.  I am going to put HS on it along with DS to see if its the relative age of the computers I usually use that is causing the issue.

#15 Re: Usage » trimforce enable as part of the Workflow? » 2017-11-13 18:04:16

I was never able to get it to run.  What I ended up doing was creating a task in Apple Remote Desktop and sent it out as root.

#16 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2017-11-07 01:19:18

Has anyone been able to do an HFS+ restore of High Sierra?  I can't seem to do that either.  Hoping to have a brand new 2017 iMac in hand this week to test.  I think that the computers I am currently using are just too old to talk to each other once High Sierra is added to the mix.  Regular Sierra and below, zero issues.

#19 Re: Usage » DS 1.7.7 and APFS restore of 10.13 is possible :-) ! » 2017-10-24 00:23:19

> shovett wrote:

> hopefully someone can point me in the right direction. We have been using DS for years now..have never really had an issue until High Sierra came along.

> We can create an image and deploy High Sierra on older Mac Pro models. When we try this on the new 2017 Mac Pro, we always boot to the folder with a question mark after restore.

> This is what we have done.

> Mac Pro updated with latest OS updates.
> Update DS to 1.7.8. on server running 10.8
> Created .nbi file on target Pro that has been updated with the latest High Sierra updates.
> Copied .nbi to DS and enabled it.
> We can boot to the new .nbi (bit slower than previous .nbi files) and create a master form the volume. This master is then copied to the APFS folder in DS.
> We boot to .nbi and restore the master we have created Which shows as filename.i386.apfs.dmg. Select first disk available.
> It completes the restore fine and we select QUIT.
> The Pro then boots to the ? folder

> Is this just not possible at the moment? What would cause the ? folder error.

> We have tried erasing the SSD in Disk Utility in the .nbi to APFS before we restore. So far we just cannot get the image to boot after its restored.

> thanks for reading


Does the target computer have the firmware installed onto it before the imaging process?

#20 Re: Debug » 1.7.8 on macOS 10.13 - DS Repository Access error & logs » 2017-10-11 19:41:18

Thank you for the response. The DS server is a dedicated box that sits on my desk. For ease of setup, the passwords are pretty simple. I can connect to the box via SMB and the same credentials without issues. I have tried with the SMB1 option checked, but I don’t remember if I did with this configuration. I will try again. I have been working on this issue for weeks, I have tried darn near everything. I wonder if the keyboard issue might have something to do with it.

#21 Re: Debug » 1.7.8 on macOS 10.13 - DS Repository Access error & logs » 2017-10-10 22:33:40

Any ideas folks?  I am stuck at this point and cannot think of any way around it...

#22 Re: Usage » Deployment Q's: How to push out Adobe CC package to Computer Lab » 2017-10-05 19:41:46

Would it not be easier to just use Apple Remote Desktop to push out the package?  What would be the benefit of using DS here?

#23 Debug » 1.7.8 on macOS 10.13 - DS Repository Access error & logs » 2017-10-04 22:36:40

Trikster
Replies: 3

After a week of trying different settings I was finally able to get the NetBoot image created with 1.7.8 on 10.13 to boot.  Still takes about 6 minutes, but it boots.  Now, when DS starts the workflow selector, I am getting the ole Repository Access error.  I have tried every configuration that I can think of on both the DS Assistant for the server itself, as well as the NetBoot Image.  I have tried the full DNS name, DNS short name, DNS short name .local, static IP address...nothing works.  I can use the OS Go > Connect to Server using all of those options and can connect just fine.  Heck, I even sat with both my working El Cap DS next to my High Sierra DS and went screen by screen, making sure the setup matches (the the change to HTTP and SMB, since HS can't use NFS and AFP).  No luck.

One bit of information I was able to get was a screenshot of the logs on the target computer showing where it fails.  It seems to be failing when DS is:

Mounting repository share point...
/bin/mkdir /tmp/DSNetworkRepository 2>&1
/bin/chmod 777 /tmp/DSNetworkRepository 2>&1
/bin/chmod 777 /tmp/DSNetworkRepository 2>&1 (yes, its listed twice in the log)
Mount call...
mount_smbfs: server rejected the connection: Authentication error
Parsing result...
Mount failed cleaning local mount point...

Before it mounts the repository share point, the logs show that the user "ds" was successfully authenticated.  Logs show its connected to the server and that the server is reachable on port 445.

Ideas?

#24 Re: Debug » [1.7.8] Netboot slow, graphics corruption » 2017-10-04 00:22:24

> mjsanders wrote:

> 10.13 netboot is know to be slow, even slower than 10.12. But my clients usually netboot in max 6-10 minutes (I did not time, but estimate)
Slow graphics is also know issue, most noticably on Mac's with 'better' GPU's. Reason; the .nbi is created from the Recovery HD partition, that only contains basic drivers.

> Tip: if you are not restoring APFS, and your hardware does not require new versions of .nbi, keep on using your trusted .nbi.
I have used a 10.11 .nbi to restore 10.12 for a long time, until we got newer hardware that forced me to use 10.12.x nbi's.

> update: my MacBook Air 2015 netboots from a 10.13 .nbi  in between 3min39 to 4min20 (to the DS runtime) (separate network),


I have finally got a netboot set that actually boots.  Still slow as hell (6-7 minutes), but a new issue has cropped up.  Will not mount the DS repository.  I have tried so many different configurations, that I am losing track of what I have tried.  I need to get this up and running before November as I will be getting approximately 100 brand new Mac's that I will have about a day and a half to deploy.  I don't have any 2017 machines to test on, so I am using the most current model I have (2015) with High Sierra on it.  I have a few ideas on how to get the other 200 computers in my stable upgraded to HS, I just need to get this damn NBI and Repository to work.

#25 Re: Debug » [1.7.8] Netboot slow, graphics corruption » 2017-10-02 19:34:46

Tried to do different Net Boot Images with slightly different properties/options.  None of these worked at all.  After 45 minutes of attempted boot, I gave up and turned off the computer manually.  I am not finding a lot of success with DS created NBI's.  Should I try another method?

Board footer

Powered by FluxBB