De har missat att läsa instruktionen för uppdateringen.
We have today released an update to MacAdministrator 3.0. It can either
be obtained through the "Check for Updates" option under the File menu
in the Configuration Manager application, or downloaded from our FTP
server using the same download instructions as issued previously.
This update has been successfully tested with 10.3 (Panther), and the
only remaining 10.3 issue that we are aware of is that there seem to be
some quirks with SMB volume mounting, which we are currently looking
IMPORTANT: If you use "Check for Updates", then due to changes in how
it works, the following steps need to be taken:
• Launch the Configuration Manager, and select "Check for Updates" -
this will download a new Configuration Manager.
• Quit the Configuration Manager.
• If you are running a remote copy of the Configuration Manager, then
replace it with the new Configuration Manger which has been downloaded
to the shared MacAdministrator folder. If you are running the
Configuration Manager from a mounted MacAdministrator folder, then, due
to Finder caching, you may need to unmount and remount the
MacAdministrator folder before relaunching the Configuration Manager.
• Launch the new Configuration Manager, and select "Check for Updates"
again - this will download all of the other new components.
The changes made in this update are:
• Solved an issue whereby the date checking on bundles wasn't
configured correctly, which meant that when using the server installer
to upgrade an older MacAdministrator 3.0 installation, some of the
items may not have actually been updated.
NOTE: This only affected upgrading using the full server installer, it
did NOT affect Check for Updates.
Client Installer for Mac OS X
• Solved an issue which prevented the Client Installer from working on
MacAdmin Configuration Manager application
• Solved an issue whereby, in the Distribution Set interface, using
"Add files/folders" to upload a structure which contained a Delete
Placeholder or an Ignore Placeholder would cause it to crash.
• Added a "Remote Commands Timeout" option, which can be found through
the Preferences menu option. This specifies the number of seconds the
Configuration Manager should wait, when sending a remote command, for a
receive confirmation from a client machine before giving up and moving
to the next client machine. For instance, if you're sending a remote
command to twenty machines, and ten of them are actually switched off,
then this is the number of seconds it will wait on each of those ten
machines before assuming they're not available. By default this option
is now set to five seconds, although on quick networks a setting of two
seconds, or even one second, should work fine.
POPAuthenticator for Mac OS X
• Solved an issue with resolving DNS entries which caused
authentication to fail. This did NOT affect it if an IP address was
• Solved an issue which caused APOP authentication (the encrypted
version of POP) to fail.
NOTE: If you are interested in POP or APOP authentication then please
email firstname.lastname@example.org, and we can email you the POP
Mac OS X client software
• Solved an issue with AutoLogout whereby the AutoLogout warning would
sometimes appear even though the machine wasn't idle.
• Solved various memory issues in the Login process, which could
sporadically cause it to either drop into Darwin or get stuck during
the Login process.
• Solved the issue whereby upgrading from an older version of
MacAdministrator 3.0 could cause the client machine to crash at the
next login, which could be manually solved by then restarting the
Client machine. This was happening because some components are only
loaded at startup, and therefore until restarted there would still be
some old components running in memory. This was solved by updating the
MacAdmin Maintainer agent, which now works out whether the components
it has downloaded require a restart, and if they do then it will
automatically perform a restart.
The sequence that actually occurs here is worth bearing in mind:
1. Using either Check for Updates or the full installer will, on the
server, replace the old MacAdmin Maintainer agent with the new MacAdmin
Maintainer agent and install a new "Client Software MacOS X" folder,
which is the new name for the old "Client Software X" folder.
2. On the client machines, the first time the MacAdmin Maintainer agent
runs, which will still be the old version, it will download the new
MacAdmin Maintainer agent (replacing itself), and it will check the old
"Client Software X" folder, it will NOT check the new "Client Software
MacOS X" folder.
3. The second time that the MacAdmin Maintainer agent runs, which will
now be the new version, it will check the new "Client Software MacOS X"
folder, download any new components, and if necessary automatically
restart the machine.
The old "Client Software X" folder *MUST* be left in place during this
process, otherwise the old MacAdmin Maintainer agent will fail during
step 2. Once all of the client machines have updated themselves, you
can manually remove the old "Client Software X" folder from the server
if you wish, although it doesn't hurt to leave it there.
We have been double checking the Configuration Manager application
released in yesterday's update, and have found an issue. The issue is
that the Configuration Manager links against one of the MacOS X
encryption libraries, and this library has changed name between 10.2
(Jaguar) and 10.3 (Panther). The Configuration Manager in yesterday's
update is looking for the 10.3 library, and therefore will run fine on
10.3, but will fail to launch on 10.2. Theoretically MacOS X is
supposed to be intelligent enough to find the appropriate library on
either system, however in reality it doesn't actually seem to work that
way. However, we had actually already discovered and solved this issue
before releasing yesterday's update. The problem we've discovered today
is that that solution only involved changing the linking in the
Configuration Manager, and didn't actually involve changing any code -
which means the updated file was exactly the same size as the old file,
and therefore the updated file was omitted when building the update.
We have now updated both "Check for Updates" and the full installer,
both of which do now definitely contain the latest Configuration
Manager application which works on both 10.2 and 10.3.
However, this doesn't help anybody who has already downloaded
yesterday's update, and now can't launch the Configuration Manager.
Therefore there is now a disk image, containing just the new
Configuration Manager application, available for download from our web
Once you have downloaded this new Configuration Manager, and replaced
the existing Configuration Manager, then you will need to launch this
new Configuration Manager and do "Check for Updates" to obtain all of
the other updated components.
It's also possibly worth pointing out that the console is an extremely
useful debugging tool on MacOS X. For instance, if there is a problem
launching an application, then if you open the Console application (in
/Applications/Utilities), and either select "Open Console" (10.2) or
"Open Console Log" (10.3), this will display exactly what errors were
encountered during launch. The console also shows many other system
related errors, and is therefore always a useful tool to keep in mind
when trying to find the cause of any problems in MacOS X.
NOTE: The following only applies if you're using MacOS X Server to host
the shared MacAdministrator folder, it does not affect any other types
The only other potential issue when updating through "Check for
Updates" is permission problems - for instance, if some of the files
within the Configuration Manager package don't have the executable flag
set for the current user then it will fail to launch. "Check for
Updates" does attempt to ensure that permissions are correct in all
situations, however there are some situations which it simply can't
account for or correct. The underlying problem here is the confusion
between "AFP" permissions and local permissions on the server itself,
and the easiest way to avoid this confusion is to always run the
Configuration Manager remotely. This can be done by either placing a
copy of the Configuration Manager on another machine, or by mounting
the shared MacAdministrator folder and running the Configuration
Manager from within that mounted share.
Hi-resolution är rätt gulliga på så sätt att det känns lite som ett gäng amatörer ibland. Visst, MacAdmin är ett enormt bra program som har sparat mig många timmars arbete, men å andra sidan så har det aldrig fungerat felfritt för det finns alltid någon liten eller stor bugg. Lite "halvtaskig shareware"-känsla över det hela ibland....
Fast det verkar bara vara du och jag som använder oss utav det här på 99mac Conny!
Problemet är att Hi-Res försöker ta hänsyn till ALLA, det har jag sagt till dem att sluta med och instället leverera en mainstreamprodukt. Alla tekniker har sina speciella önskemål, jag menar att sådant får man fixa med applescript.