[userosx]

Never mind, it looks like I missed the obvious, which was to specify a home folder. I assumed the home folder would just default to the local client if nothing was specified. Oops. Ugh.

[userosx]

Thanks for the response. My only requirement at this point is to merge the 10.5.7 update. My current installer is 10.5 and won’t work on my test system. Perhaps I can extract enough information out of the existing instadmg.bash script to accomplish this. I’ve done a lot of packaging, but I’ve never tried merging OS X updates.

[userosx]

Never mind, I figured it out. I just had to add a “socket” to the LaunchDaemon to allow for the network authentication.

[userosx]

[QUOTE][u]Quote by: thespider[/u][p]I solve this issue by only running the computer naming script, then it loads the launchd item for the ad bind script and reboots. Then after reboot, it binds. You could also do an if statement that would check to see if the computer is named correctly.

Rusty[/p][/QUOTE]

I like this idea… If my current method doesn’t work, I’ll have to give this a try. Well, I’m going to find out if my current method works in about an hour. 🙄

[userosx]

Both scripts are lengthy and written in a different language. However, I suppose I could have the daemon call a script that calls both scripts in succession… That might work… Why did I not think of that before? Well, hopefully it works…

[userosx]

I’ve been using the referenced command (systemsetup -setremotelogin on) for some time now, but I need to specify “Allow access for:”, “Only these users:”, Administrators. Is it possible to specify which user/group has ssh access via the command line? I found the plist file (/var/db/dslocal/nodes/Default/groups/com.apple.access_ssh.plist), but it appears dynamic and not something I could rewrite using defaults or plistbuddy. I’m guessing there’s a simpler way.

[userosx]

After reading that thread, I decided to give Iceberg a try. Personally, I like it better and it has made this process easier. Thanks for the info. 🙂

[userosx]

I have not heard of lingon before… All I can say is… This looks AWESOME! Far less tedious than looking through man pages attempting to decipher the appropriate syntax for launchd. THANK YOU! 😛

[userosx]

Well… today it’s decided to work… AND I’m trying NetRestore for the first time as well, although I see it’s End of Life was last November. 🙁
Welp, the next step is to see if the NetInstall is successful… /hopes

[userosx]

The OS version on both client and server is 10.5.6.

Since the NetInstall build never seems to complete in SIU/Automator, I assumed it had something to do with the fact it was a 300GB disk image. However, based on your response, it seems my assumption was incorrect.

I’ve been using SIU for the last few years and I’ve never tried NetRestore, although I’ve heard many, many references to it. I figure if SIU has always worked, there’s not much point in changing. However, it may be time to finally take a look.

Anyway, for whatever reason, after I build the image in InstaDMG, SIU/Automator just runs endlessly and the image never completes. I’ve been building images for about three years now and I’m used to getting a working build. 🙂 But this is my first attempt, so I’m bound to run into a problem here or there…

[Author]

Posts