[knowmad]

got a script example for adding the mac address to the local record?
knowmad

[knowmad]

pteeter, i too was of the opinion (noted in the other office thread) that rolling my own was better…. then I played with the droplet… it works and it makes life easier and less time consuming because, although the updates take forever to run, they do indeed work and I can do other things while they work.
Plus they all take choices files which makes fine tuning simple.
give it a whirl, you might find it simplifies things in the long run.
knowmad

[knowmad]

as soon as I can download it, I am going to test the hell out of it. THANK YOU!
Mind if I steal bits of your code to make some related scripts?
I will post or email what I do andof course give you full credit.
knowmad
(ps, your email must have been spam-blocked, but the post here works just as well.)

[knowmad]

it seems Google is getting faster at indexing because a quick search for ‘hdiutil error 49153’ turns up this discussion at the top of the list ( [url]http://tinyurl.com/3jyb7x[/url] ) but moving on from that starting point I find:
([url]http://www.maclife.com/forums/topic/78898[/url]) this fellow who was doing some coding and came across the same error, he found that he could force the disk to unmount using [code]sudo chroot /Volumes/10-4-base/[/code] which you might want to play with but it still does not answer the question as to why this is happening and I have the feeling won’t really fix your issue…..

Which brings me to a question – is your image usable? ie are you just annoyed and worried at the error or is there a real issue of no image/non-usable image?

back to our search for a solution (I am avoiding work right now)
hmmmm, i found many references to the error, and all seem to agree, it refers to a disk or image that cannot be unmounted because it is missing or damaged. SO, i think we need to see how you shifted your temp directory….. or maybe some other path is incorrect…..
basically, more details please.
knowmad

[knowmad]

not exactly on-topic but I figured that you might be interested in this, found it a while ago (week? two weeks?) on macosxhints.com
[code]
#remove itunes store links (save bandwith)
defaults write com.apple.iTunes show-store-arrow-links -bool FALSE[/code]

useful in its own way…..

[knowmad]

ah, ok, thanks, that I can work with…. any idea if it will work on a non-booted volume or do i need to create a startup script/daemon/something?
knowmad
(beginning my own research now)

[knowmad]

ok, stupid question time: is lpadmin a plist? an mcx record? more details please
knowmad

[knowmad]

Larkost… didn’t you write a tool that basically does the plist populating (among other things)?

[knowmad]

Any chance you have done further work on this that you can share with us? I know of at least one other thread trying to figure this one out…..
Any updates, even ones declaring ‘i tried this and this and then gave up” are very useful.

[QUOTE][u]Quote by: jdyck[/u][p]Hey, that’s perfect!!! I had played around with the security add-trusted-cert command but kept getting errors… I think because I was trying to do the -p eap part, which kept giving an error. This works though, which is fantastic. Thanks a bunch, now just need to revisit my scripts to auto-generate the 802.1x config to see if that works.[/p][/QUOTE]

can you post those scripts in whatever tested/untested form you have?

Knowmad

[knowmad]

true enough BUT…… what about using PHDs for a one time full backup and then after it is all back down on the new setup throtteling the space back to normal levels.
In the past I have had issues with users and network space, the upshot always was “save it in a folder that gets backed up, or face the consequences” we had over 5k users so broad all encompassing policies like that were normal.

[knowmad]

FYI I already ran the QT7.5.5 installer in instaDMG and it ran flawlessly….

[knowmad]

which actually makes this a wonderful way to create a new user but keep old data…. you would need to do some scripting of your own but with the bombich scripts to work from (and the createuser) it should be easy….. no wait…… I have more ideas….. how complicated would you like this to get?
Steps
1) Run backup script
2) have it store the data somewhere network accessible
3) put the new image onto the machine having created your image to have a script (see step five) that looks for basic data from a text file
4) create and place the text file into the correct spot. This is assuming that you put the image onto the machine manually and while it is in target mode. The text file contains the username, comp name, password of the user, as well as the unique location of the data stored by the backup script
5) reboot allowing your wonderful new script to run. Said script will take the data out of the text file, populate the CreateUser script with it (password in clear text because you will clean up after yourself) then it will\
6) run create user which has been modified to kick off the
7) restore data script pointing at the unique location on the network which has been modified to kick off
8) the clean up script to remove traces of the clear text password…. (or you could use the hash and kill this portion but whatever)

or some variation thereof

this (if I had time and more skill) could be fun to do.

[knowmad]

I am really confused (a constant state of being but in this case it applies to somethings you said)
the upshot of your reply seems to be that if you put the updates where they belong then it works and if you put them where they don’t belong than it does not work…… am I missing something?

also, in your zero-payload installer package, the script you are running… does it reference the instadmg image by name or by $3 ?
what is the name of your boot drive?
Are you certain that pmset will work on a non-booted volume? I have a vauge recollection of it being a boot volume only option…
Have you looked into setting this stuff via mcx record? that I know works (I have done it myself) and it also lets you set it permanently, if you don’t want users playing with it.
Otherwise you might make your pmset script into a boot script, run it the first time or every time …. whatever you need.
Knowmad

[knowmad]

There was an extended discussion of this in the past… check out this thread:
[url]https://www.afp548.com/forum/viewtopic.php?forum=45&showtopic=20630&highlight=wireless[/url]
I did not re-read it just now but I remember that there was some serious scripting acrobatics necessary to get it running properly…. and had to be set on first boot not in instadmg… something to do with mac addresses and signed keys and whatnot…..
Later this week I too will be tackling this issue…. so keep me posted on your progress and I will do the same.
knowmad

[knowmad]

can you give us more details?
InstaDMG is supposed to re-point all installs to the current image mount…. do you have an unusual installerchoices file? have you altered your instadmg script drastically?
The more details you can give the more likely we (read: larkost) are to have a quick and/or useful answer.

[Author]

Posts