[patchsmyle]

I see now. I had not glanced at the file format and only looked at contents missing that the package was a VISE installer.

So, this means you would need to wrap your own package. I cannot wrap one and share it without stepping on copy-write distribution. But I would use a tool to monitor if there are any additional files beyond the Auto Update app itself.

There are a few out there. More then I am mentioning here.
logen, fs_event, [url=http://www.macupdate.com/info.php/id/19141/fseventer]fseventer[/url], even Apple’s package maker can collect a DIFF output.

[patchsmyle]

Microsoft did not do any one any favors to find the correct link to download. If you scroll half way down the page, you will see a three pane section at the bottom. It has the label “Detail” above it. That pane you can scroll down in. You will then see the link to download it. Adding the link to the page again [url=http://www.microsoft.com/mac/downloads.mspx?pid=Mactopia_Office2008&fid=31BC88ED-DF2D-471A-B4B5-66C2A51C8BEA#viewer]here[/url].

Some one at Microsoft should be shot for the poor UI design on the page.

[patchsmyle]

If you reread my post, my suggestion was to download the update from microsoft website. That version comes as an installer, not a .app.

[patchsmyle]

[QUOTE][u]Quote by: thespider[/u][p]Has anyone tried the Microsoft Auto Update 2.1.1? It’s an .app so I am going to try to repackage it.[/p][/QUOTE]

No need to. As Microsoft already has packaged it for you. Again, from their website, you can download the auto-update update that is an Apple Package installer:
[url=http://www.microsoft.com/mac/downloads.mspx?pid=Mactopia_Office2008&fid=31BC88ED-DF2D-471A-B4B5-66C2A51C8BEA#viewerurl]AutoUpdate 2.1.1[/url]

[patchsmyle]

Adding the follow up Office 2008 version 12.0.1 update is just as easy. If you download the update directly from Microsoft’s website, it is just a normal package installer. Just place this installer after the main install.

File can be downloaded from [url=http://www.microsoft.com/downloads/details.aspx?FamilyId=8FE8C32A-6D7A-482B-97C6-42562F089EE4&displaylang=en/url]Microsoft[/url]

[patchsmyle]

I have discovered the last piece of the process to allow this to work.

Perform an install with the site-license serial number. In the /Application/Microsoft Office 2008/Office/ folder, there is a “SetupInfo.plist” file. Create a second custom installer that only installs the SetupInfo.plist file into the correct directory “/Application/Microsoft Office 2008/Office/”.

And tada! you now have a pre-configured INSTALLED, InstaDMG instaler!

[patchsmyle]

I realize this is over a year overdue to reply. But there is another trick. You can tell the computer force sleep the display with the computer on.

Command: /usr/bin/pmset force -a displaysleep 1

Note: the “1” is in secords before sleeping the display.

Fred L.

[patchsmyle]

The Authentication failure is due to Backup Exec on the PC. Do me a favor and thank them very much! *grumble*. They basically hacked together a backup exec client for the mac. There isn’t any “user” name used to authenticate to a mac. However, there is a password. What is not documented well, is the password of the ACCOUNT you use to log INTO Backupexec is the password used to try to authenticate to the box. NOT the password used under the machine viewing section. So, what ever password is used to get to the BackupExec Console on your PC, is the password you need to assign to the backupexec clients configuration.

On a similar note, you will notice the BackupExec client for mac installs a startup item in /System/Library/StartupItems/. This is NOT the right place to have it run. If you boot your server in “Safe” mode, the backup exec client will STILL load. I recommend to move it from /System/Library/StartupItems/ to /Library/StartupItems/. Makes things easier to troubleshoot if you encounter problems.

FYI, be aware of the following issues with BackupExec:

1. Does not copy resource forks well. (intermittently looses the resource forks)
2. Does not capture ANY ACL information.
3. Does not capture user/owner information on files
4. Strips off meta-data related to the file (aka spotlight information, embedded icons).

I found out the hard way this issue removed any relationship to the parent file, and had to recreate every link to the graphic files. Quark files were considered unknown files since Quark doesn’t even have a .suffix to their files. Be warned.

[patchsmyle]

Apple intentionally disabled Spotlight from being enabled across an AFP connection in 10.4.

[Author]

Posts