[ingenious7]

Probably not the answer to your problem but I had a lot of problems trying to open a file and was getting weird error messages from Office because I still had the Office Mac 2004 Test Drive on the computer. It was in the Trash but still caused errors.

[ingenious7]

Hi

Have you tried unchecking the option ‘Merge with users dock’ in WGM. From the situation you have explained each user account should be given their own custom Dock arrangement. I can’t understand how they would be merging.

[ingenious7]

I am looking to answers for some of those questions as well. I am testing out my first Leopard client on my MCX-managed Tiger Server based network. I am having very mixed results at the moment. Authentication has quite a delay on it (about 30 seconds to a minute).

I can live with the slight delay at the moment. What I am really having trouble with is MCX settings. The leopard client will only use the MCX settings for the local accounts, not for network accounts. This is really frustrating and driving me crazy! We have no plans to upgrade to a Leopard server for a couple months at least, but we have another quantity of Leopard based iMacs coming for the start of next year and I desperately want this resolved.

Let’s hope somebody comes up with the answers to our questions! Maybe 10.5.1 will resolve some of these compatibility issues?

[ingenious7]

I was having the same problem when we upgraded to 10.4 in 2006. Try this:

Make sure you are logged in with an administrator account.

Open Terminal (/Applications/Utilities).

Create a backup of the current NFS Startup script with this command on a single line:

sudo cp /System/Library/StartupItems/NFS/NFS /System/Library/StartupItems/NFS/NFS.bak

Open the NFS Startup Item script for editing with nano by using this command:

sudo nano /System/Library/StartupItems/NFS/NFS

To locate the section of the script that starts automount, press Control-W, type “automounter”, and press Return.

Under the section “Start the automounter,” change the line that reads:

automount -m /Network -nsl -mnt ${AUTOMOUNTDIR}

to read:

automount -1 -m /Network -nsl -mnt ${AUTOMOUNTDIR}

Change the line that reads:

automount -m /automount/Servers -fstab -mnt /private/Network/Servers \

to read:

automount -1 -m /automount/Servers -fstab -mnt /private/Network/Servers \

Save the file (Control-O, Return), and exit nano (Control-X).

Reboot.

[ingenious7]

Thanks for the reply MacTroll. Really would prefer something free, so I’m looking into PyKota. Has anybody had any experience running this with the Mac OS X printing system? How well does it work.

I am really interested in showing the users what they have printed and how much they have left to print.

Cheers.

[ingenious7]

Hi,

Did you create the image and netinstall set on an G5 iMac? This can cause problems if you have created the image on say a G4.

I remember having a similar problem when we upgraded to new iMac G5s.

[ingenious7]

Are you using the Computer Management section in the WGM? If you are, try customizing the dock under the preferences for those labs.

If you are not, create a new list, click the button with “…” and add all of your iMacs. Then select the list, click preferences and set the dock you want to appear for users.

I would suggest unchecking the “Merge With Users”. This will prevent the system throwing up the default set of icons in addition to what you want.

[ingenious7]

I was sure I added it the same way. The only difference was that I renamed the script to login.sh. I don’t know if this made a difference or not.

[ingenious7]

For anyone interested, I found the solution –

[code]sudo -s
echo ‘#!/bin/sh’ > /Library/Management/login.sh
echo ‘echo $1: `date` >> /tmp/login.log’ >> /Library/Management/login.sh
chmod a+x /Library/Management/login.sh
defaults write /var/root/Library/Preferences/com.apple.loginwindow LoginHook /Library/Management/login.sh[/code]

This is like a test. To make sure it is working, log in as a user, and enter

[code]cat /tmp/login.log[/code]

My script works perfectly now. I can have login photos taken via iSight camera, and sent straight back to my desk. A little Big Brotherish I think. Oh well.

[ingenious7]

I would suggest, if you can’t get the Apple imaging software to create the image, try using Bombich’s Net Restore Helper ([url]www.bombich.com[/url]) to create the images.

I use that to create my images, with FCE and Adobe on the source dmg which brings the image files to aroud 35GB. I couldn’t see how 50GB images would be impossible so I would agree it is a bug in the Apple software.

I made the change to Net Restore Helper to create my images because of all the errors I faced in Apple’s software. Probably more of a user issue though. 😳

[ingenious7]

I found this in the System.log. It seems login scripts are crashing.

[code]May 7 11:57:39 imac-computer /System/Library/CoreServices/mcxd.app/Contents/Resources/MCXLoginLogoutScriptTool: login: “loginscripts” in “com.apple.mcxloginscripts” is not a CFArray.
May 7 11:57:39 imac-computer /System/Library/CoreServices/mcxd.app/Contents/Resources/MCXLoginLogoutScriptTool: login: /Volumes/Macintosh HD/CaptureUser returned 5; exiting.
May 7 11:57:39 imac-computer crashdump[165]: MCXLoginLogoutScriptTool crashed[/code]

What is a CFArray? Why would the MCXLoginLogoutScriptTool be crashing.

Surely somebody easily runs login scripts on OS X 10.4.9?!?
😕

[ingenious7]

This is the script I am running, and I am using an additional compiled script from [url]http://www.intergalactic.de/hacks.html[/url] called isightcapture.

[code]#/bin/bash
CallFile=/$(users)-$(date +%Y-%m-%d-%X).jpg

#echo $CallFile

/usr/local/bin/isightcapture $CallFile[/code]

Is there something wrong with the way I am coding this. I have even tried getting the script to do a mkdir to check it is running at login and nothing.

I have attempted to create a Login script using Mike Bombich’s LoginWindow Manager. Is there something I am missing?

[ingenious7]

Thanks for the reply.

I’ve run the script as root, and it looks like there may be an issue.

[ingenious7]

I’ve solved my problem.

By starting up the iMac in verbose mode I could see that the AFP share was being mounted correctly. The problem was with the NetInstall Set that I created using Bombich’s NetRestore Helper ([url]http://www.bombich.com/[/url]).

When I started the iMac up it just hung at the Apple Logo with the spinning cog. This is because it could not load the CoreVideo.framework because it could not be found. That meant it was not progressing to the GUI screen, and was loading up a Terminal, which I couldn’t see because of the Apple Logo.

I opened the NetInstall set, copied the CoreVideo.framework files from my 10.4.9 server, and that seemed to fix the problem.

I used the latest version of NetRestore Helper – 3.3.4. Maybe there is a problem with this, or was it something I was doing?

At least it is working now, so I am happy!

[ingenious7]

Thankyou mcnaugha!!!!

Many thanks. I made those changes and all is working fine. What did changing that file actually do? What would have caused the issue to happen in the first place?

I will being rollout of the NFS file via ARD.

[Author]

Posts