[knowmad]

There is a much simpler way of doing this, though it is very UN-instaDMG-ish in its execution………..
1) Install Office on a clean machine.
2) Update the hell out of it.
3) Grab JUST the office folder from the applications folder and package it.
4) Create a one time login script that runs the office first run (essentially, open word once, then quit it, very simple).
5) Install your re-packaged office and your one time login script via instaDMG.
DONE!

No mucking around, no major surgery and nothing that will kill other parts of the system/software/brain
I know it is not very much inline with the InstaDMG way of thinking except on the most basic level, which is to simplify your life as an admin.
The updates (so far as I can tell) update the first run info as well as the already installed pieces, net result is that you can now ‘re-install’ from an updated office folder.

On the other hand, your work is GREATLY appreciated. Going forward it will make it possible to add just some updates and be done/happy with that.
So, thank you.

[knowmad]

Check your user numbers…. did you pick UIDs? or did you let create user grab them?
The last time I saw something like this it turned out my user setup was majorly off. At the time I was trying to figure out how to hide a user in leopard (leopard was new and the ins-outs were not clear yet). I gave my admin account a sub 500 number and to my great chagrin I logged in as html parser (or something). Then I listed all the users on the machine and discovered I had chosen (by random) an already assigned useID. It totally screwed with my system and I had a heck of time getting anything to work properly as that user.
If you check the thread over here: [url]http://forums.macosxhints.com/showthread.php?t=80670[/url] you will find the entire list of user IDs and group IDs that are built in.
You could (I guess) do it for yourself with [code]dscl . -list /Groups PrimaryGroupID[/code] and [code]dscl . -list /Users UniqueID[/code] and then make absolute certain your setup (both ldap and local) are not walking all over that list. Lastly, and very importantly, if the user hasno rights to his own home drive he will get an error similar to the one you saw regarding the location of home folder…… or you could be pointing it to a nonexistent directory…. check for typos.
Anyway, that is how I would start troubleshooting this.

[knowmad]

[QUOTE][u]Quote by: pteeter[/u][p]

larkost – I have to ask…are you (the creator) and me the only people using InstaUp2Date?[/p][/QUOTE]

nope, just the most knowledgeable

[knowmad]

[quote]International: enable character palette and show input menu in menu bar

Hi Knowmad,

which item should I add in WM to gain access to the international settings? I tried adding /S/L/CS/ManagedClient but no luck with that one…

tried also with “/S/L/CS/Language Chooser” but WM is not allowing me to add it

Eric

[/quote]

Eric,

ok, well…… I have no idea. a couple of days after my last post I left my job and moved across country. I have literally not been near a mac for two months. I will be doing a lot of work on this for my new job, but not until next week when I get my new build station. At that time I will look into answering your question.
In the mean time, anyone else want to take stab at it?
(sorry)
knowmad
(edited because i can’t count)

[knowmad]

wait, no, not exactly.
if you UPGRADE you will create a situation that allows the issue to persist.
If instead you archive and install or image you machine, install a fresh OS 10.5 and then migrate your account, the issue will go away.
In truth I have never run an ‘upgrade’ from 10.4 to 10.5 so I don’t have that issue as a first hand experience, but it has been reported in other places.

but yes, if you install 10.5, the issue goes away.
Best way I know of to do it, make an image of your current machine, put it some place safe. Wipe the drive, install OSX.5, create a throw away user on the machine, mount the image of the old machine, run the migration utility, log in as yourself and dump the throw away user.
OR
install OSX 10.5 and start using it from scratch.
either which way, it works.

[knowmad]

wow, that went MONTHS without being caught.
yes, you are correct, I meant new.

Before you do this, you need to know a few things.
in 10.4.11, while this fix does fix some of the wierd behavior, it screws up others and makes more issues than it is worth.
I found that the best thing to do was either keep a second image just for those laptops (they had special chipset in general) OR go to 10.5
nothing else really seemed to fix things long run.
sorry

[knowmad]

dsenableroot can be made to do a non-booted volume, but it must be done with a pre-built hash or it will not work.

[knowmad]

heh, I posted without seeing gneagle’s post… we basically said the same thing ‘use MCX’ but he did a better job of pointing to resources. Good on you!

To answer, I don’t think I have any other MCX how-tos, but I will check.

[knowmad]

I ran into this issue when I accidentally packaged apps as root.
It was a permission error.
Once I corrected the owner and removed the accidental sticky bit… it worked.
give that a try…. you never know

[knowmad]

[quote]Appearance: change highlight color
Spaces: enable and add to menu bar
International: enable character palette and show input menu in menu bar
Security: disable auto-login, set a master password, and turn on the firewall
Bluetooth: turn off and enable Bluetooth status in menu bar
Accounts: display login window as name and password
TimeMachine: do not show menu bar item
Universal Access: enable flash screen when an alert sound occurs[/quote]

OK, a lot of this stuff (and some of the other stuff you have talked about) is easier done through MCX records. This topic has been covered elsewhere many times (links to come when I get the chance) and is worth looking up. It all depends on how tightly you want to control this. If you download Server Admin and use the WorkGroup Admin tool (names of tools are approximate, I have a bad habit of using a shorthand for my own thoughts that then eclipses the actual name in my mind)to set policy for a guest computer and add that to your image… a lot of it can be done that way easily and semi-permanently.

Setting the login window to User/Pass, disabling autologin, disabling bluetooth, time machien not in bar, Universal access, turn on firewall… these are most easily set through MCX/workgroup admin.

The other thing you can do is set up a ‘new user’ exactly how you want it to be, then copy that profile into the English.lproj folder (/System/Library/User\ Template/English.lproj) of your image. Then all new users will have those settings as default. Does not work for system level settings such as MasterPassword.

I hope this was helpful.

[knowmad]

the plugin will ‘auto heal’ when next the program is run

[knowmad]

when your all done, please post the working final routine for this

[knowmad]

[QUOTE][u]Quote by: akinspe[/u][p]

Sorry for those who tried 1.0.1 and had trouble. This is what happens when you get no sleep from a newborn.

[/p][/QUOTE]

CONGRATULATIONS!

there goes your productivity.

[knowmad]

what os is your build box running? (ie the machine running the script, not the os that the script is building)
I ran into a similar issue the first time I tried to run instadmg as I was using a tiger box to build a leopard image.
the OS would not install but the script ran all the way through, result was that I had a tiny small image with no useful data.

[knowmad]

I have not seen this yet but:
1) have you tried making an image of the second disc and making certain it is mounted before you kick off the script… I know it is not supported but maybe, just maybe…..
2) Check your choices file, you are likely installing something that is an ‘extra’ item coming off the second disk. Those extras are better off being run as stand alone installers in the custom packages group/section of the process.
3) Rule of thumb, if you don’t need it, don’t install it. iChat and Mail are not NEEDED, though they don’t seem to cause issues if installed.
just my two cents

[Author]

Posts