[eholtam]

For those that have just gotten 12.1.0 to work there’s now a 12.1.1 update out.
Office 2004 got an update as well. Plus the XML converter tool is now 1.0.

[eholtam]

Sorry, Quark was dumped by the curb when we went to OS X and we never looked back.
Good luck.

[eholtam]

Going off Patrick’s suggestion you could have the remote machines add a line to the end of the one document on the server in the format that ARD uses to Import into a Scanner.

From the Apple ARD Admin guide found at ( http://images.apple.com/remotedesktop/pdf/AdministratorsGuide20061116.pdf ):

You can import a list of computers into Apple Remote Desktop by importing a file
listing the computers’ IP addresses. The list can be in any file format (text, spreadsheet,
word processor) and must contain either IP addresses or fully qualified domain names
(such as foo.example.com).

So each computer could add its FQDN to the end of the file so you could later import that file as needed.

On a simpler note couldn’t you just create a bunch of saved scanners in ARD for the network ranges you’re interested in?

-Eric

[eholtam]

We are seeing it and the fix you referenced is what we’re using as well.
No idea why its happening, though.

[eholtam]

First thing to check is to make sure the file is executable in the NetRestore Post-Actions folder.

If it is try putting in some logging and echo out the hwAddress value to see if its getting what you think it should be getting.

[eholtam]

It looks like, according to Workgroup Manager, the Software Update policy can be applied to any level (User, Computer and Group).
The User setting would override the Computer setting would override the Group setting.

-Eric

[QUOTE][u]Quote by: pteeter[/u][p]For some reason I’m revisiting this issue.

To control /Library/Preferences/com.apple.SoftwareUpdate CatalogURL (software update server for every user on the machine) must the managed preference be configured for a machine account?

Or can this be applied, through OD, via a user/group login managed preference?

[/p][/QUOTE]

[eholtam]

Usually when I have problems like this in packaging FileWave filesets I log in as root and create the set. It could be some funky permissions issue that your local admin doesn’t have rights to. Its worth a shot.

-Eric

[eholtam]

Its just adding extra time with all the unnecessary updates. If a user didn’t update since 10.5 the 10.5.3 combo update would be the same as their upgrade path as well.

[eholtam]

You didn’t say what OS version your clients are on so I’ll assume Tiger because we’ve seen this issue with our Tiger build.
Are your clients also bound to AD for authentication? If so check to see what order the Authentication paths are in in /Applications/Utilities/Directory Access. In our case we had to switch them from what our Panther build had to the opposite order. I don’t recall if that was to move AD on top of LDAP or vice versa. But play around with that setting and see if that makes a difference. It did for us.

-Eric

[eholtam]

Well I seemed to have solved my problem by destroying and recreating from backup the OD master while the computer is named correctly.
Everything seems to be named correctly now.
The commands I used were:

[code]
sudo slapconfig –destroyldapserver
sudo slapconfig -createldapmasterandadmin diradmin “Directory Admin” 1000 “dc=YOUR,dc=DOMAIN,dc=com”
enter the password for diradmin
sudo slapconfig -mergedb -f /Users/admin/Desktop/LDAP-BACKUP-ARCHIVE.sparseimage
[/code]

I also wanted to disable Kerberos on the OD master as we don’t use it for authentication (strictly AD for that)
[code]
In Terminal issue the command
sso_util remove -k -a diradmin -p -r HOSTNAME.AD.MDP.COM

Launch Workgroup Manager
Enable the preferences “Show “All Records” tab and inspector”
Click the target icon that appears next to user/group/computers
Select “Config” from the popup menu
Highlight “Kerberos:SERVERNAME
Delete
Highlight KerberosKDC
Delete
[/code]

[eholtam]

We’ve had success.
What we did was create a startup item that launches a custom installation script that installs the QT package, plus a few other updates.

The StartupParameters.plist for the startup items contains:

[code]
{
Description = “instaDMGStartup”;
Provides = (“instaDMGStartup”);
Uses = (“Disks”);
OrderPreference = “Last”;
}
[/code]

-Eric

[eholtam]

That’s a slick fix. I wish I knew that sooner. Learn something new every day…

Just make sure the ‘installer’ command using $UPDATE_PKG is in quotes to preserve the spaces in the path.

I didn’t know this would work before so I don’t know if anything will hang it up. Most every .pkg file has pretty standard characters. I’d say assume user’s custom .pkg files won’t include any characters other than Apple’s supplied .pkg files..which have consistently been alpha-numeric.

The issue of specifying the order of installations is still there though.

[eholtam]

The way I read it is it a way of slipstreaming Mac OS X installations.
So instead of having to install custom applications, run scripts, etc, after installing an OS build you can just package those custom bits up into Apple .pkg installers and have this tool install and run those on the new OS for you. And once you have those bits in .pkg format then future OS updates will be a breeze. There’ll be a little work up front to get all your custom actions into .pkg format but after that the ROI will be evident.

[Author]

Posts