[tlarkin]

Update:

So, I downloaded the newest instaDMG build off the Google projects site and am building a new vanilla OS. I got my 10.5.0 DMG that I already created in the base OS folder and am running the instaup2date python script now.

Does it matter that I am using an existing disk image of my 10.5.0 retail DVD, or do I need to allow instaDMG to create it?

#EDIT

So far so good, seems to be running but is very slow. I just tossed my retail image of 10.5.0 in the base OS folder and ran the python update script. Seems to be working as far as I can tell.

[tlarkin]

[QUOTE][u]Quote by: foilpan[/u][p]”compile” is the casper term, and i’m not entirely sure how their process differs.

but, yes, i’ve built 10.5.8 and 10.6.3 images including all recent updates with instadmg. just use the most recent version, build on the same major OS version as mentioned above, and it should work.[/p][/QUOTE]

All I got is a 10.5.0 retail DVD which I use plus the 10.5.8 combo updater. Like I said, every package installs just fine except for the newest ones which are flat packages. Let me take a look at instaDMG but I found the documentation a bit lacking last time, and I don’t want any user’s created in my image either. I do all of that post image script.

Thanks for your help.

[tlarkin]

[QUOTE][u]Quote by: foilpan[/u][p]have you tried building an image via just the instadmg script and not using casper’s workflow? i’ve never had any major problem that way.[/p][/QUOTE]

No I haven’t but when I posted on the Casper mailing list an Apple engineer told me this was a bug with Apple. I also have an open Enterprise support ticket on this with Apple as well, and they confirmed the bug.

So let me get this straight. You can compile an up-to-date OS image by using a retail disk image + combo updaters and Apple updates for everything and it works fine for you?

[tlarkin]

10.5.8 compiled. Certain new updates that are only in flat packages like safari 4 and java 6 will not install in my compiled image. I am using the instaDMG support in the Casper Suite to make this disk image. This is a bug, according to people at Apple, that involves flat packages not being able to be installed on a compiled image via instaDMG. Everything across my enterprise in 10.5.8, all servers and all clients.

[tlarkin]

I think if maybe I just delete this…

/System/Library/CoreServices/Software Update.app/Contents/Resources/SoftwareUpdateCheck

It is a completely separate app with in software update that seems to auto check for updates. I wonder if I just delete it…?

[tlarkin]

I guess you could use the mkdir command and create a folder called exactly what you want, and have the mount symbolically link that folder. Since the folder will be called what you want, but it will link to /volumes/x that would achieve what you wanted to.

[tlarkin]

Specific users should own their sites folder to begin with, or what exactly is your question. Is this for you, or is this so your users can host sites off your server?

[tlarkin]

I can not figure out your problem either and google searches point me to your posts here and posts on the apple board. Have you contacted Apple about this? I am taking a total shot in the dark here but it sounds to me like minor BSD database corruption. I could be wrong though.

[tlarkin]

Was it a full back up that included passwords? Or just a plain text export of users/groups? When this problem occurs, what else is shown in the system log and what is shown in the server logs?

[tlarkin]

Did you upgrade from 10.4 server to 10.6, or did you wipe and reload? I am sure that directory services has had a bit of an overhaul since the release of 10.4.11 all the way to 10.6.2. I know that I had several bug reports filed with Apple and Directory Services with my enterprise support last year.

If you created the sadmin account locally during initial set up of OS X Server, and it cannot read the user, then your local BSD database is corrupting and directory services cannot read that user account.

[tlarkin]

Whenever I need to use a password in a script I always make it self destruct and then purge the logs. I know that keeping passwords in scripts is not considered best practice but all of my scripts that have passwords are typically post image scripts. Then they self destruct and flush the logs.

[tlarkin]

Well, assuming this is 10.4 or higher you can create a launchd item that will run at start up regardless of who logs into the machine if you put the agent in /Libarary/LaunchDaemons and then use launchctl to load it. Autofs will still parse entries in /etc/fstab so you can always put them in there as well, but I have had mixed results with this method when I have tried it myself.

[tlarkin]

If you go into WGM, and select the user group or computer group you want to manage and add the managed client app to the details side you can set specific MCX settings, that will be applied to that group. If you add the plist that controls the desktop you can hard code the settings in XML what you want it to be. Then set the path to the background picture and users will not be able to change it.

[tlarkin]

I have had sketchy results with upgrades which is why I wipe and reload

[tlarkin]

Did you wipe and reload or upgrade?

[Author]

Posts