Snow Leopard is not supported in 8.8. You will need to move to 9.0 SP2.
Snow Leopard is not supported in 8.8. You will need to move to 9.0 SP2
Maybe I'm misinterpreting the change log ( http://cswebtools.landesk.com/downloads/ServicePack/LD88-SP4-ReadMe.htm )
I thought SP4 added support for Snow Leopard.
- Added Client Support for Windows 7.
- OSD/provisioning support for Windows 7
- Client support for Windows 7 does not include Windows Firewall support.
- Client support for Windows 7 does not include Profile Migration support.
- Client Support for Host Intrusion Prevention and Connection Control Manager is not available on 64bit operating systems.
- Added Support for Intel AMT 6.0 platform.
- Updated AV Engine to SDK 8.
- Client support for Mac OS X Snow Leopard (10.6).
- Client support for Windows Server 2008 R2.
Could you please clarify?
- Added Client Support for Windows 7.
I asked around and verified that it is not supported in 8.8. It was going to be and was never added. That file should have been changed.
It is pretty shocking that something like that was missed. I hope that is fixed ASAP.
I've done further testing and I am seeing the same issue on 10.5 Leopard machines. Anyone have any troubleshooting ideas?
I just grabbed the Office 2011 iso and zipped up the mpkg on my mac and transferred it over to my LD8.8 sp4 package share. Then I was able to deploy it silently without any problems. Did you check the free disk space to make sure there was enough? And did you zip it up on a mac? Windows kills .pkg files. Also maybe try a different distribution method to see if you are just having a problem with a certain setting in your environment. I created a policy supported push task and removed bandwidth detection and multicast for speed purposes.
Also SP4 does have some support for 10.6 just not full functionality. For instance OSD will not work on any newer hardware.
I apologize for the delay but it has been a busy few weeks.
I've finally had a chance to do some more testing. I've got a fresh install of Leopard (10.5) on a Macbook Pro with the Landesk agent installed. I've tested and I'm still getting the same issue with the file being created but never actually downloading (0 KB).
I've tested on both Leopard and Snow Leopard with both push and policy supported push distribution methods.
Assuming there is nothing else to be done, I guess I'll have our Landesk Administrator look into it.
Also, I just wanted to point out that the SP4 patch notes STILL haven't been updated to reflect the limitations in 8.8 SP4 support. Is there somewhere I can find an accurate set of patch notes? Specifically, I'd like to confirm which parts of Snow Leopard aren't supported along with if 8.8 SP4 actually has OSD/provisioning support for Windows 7.
George if you are still having trouble deploying office you should call into support. It will be faster then going back and forth here.
been trying to deploy office 2011... can you give me details on how you push it out using a ZIP .... new to MAC software distribution
Craig did you get it working?
not yet.... i found instructions on MS site on how to create a PKG using apple's package maker but that has not worked so far either
When you open your Office 2011 DMG or put in the disk the file that should be contained in their should be a mpkg already. At least it is on my media. It is called Office Installer.mpkg. So you should't have to create a pkg file. You have 2 choices. If you have a DMG you can just use it as your distribution package (as windows will not open a dmg file so the file permissions are safe) or you can zip the mpkg file and use it for a distribution package.
I worked with George today and we figured out what was keeping his Software Distribution tasks from working correctly.
Failure = WINS
Talk about an oxymoron...
Basically it came down to the fact that his Software Distribution package used an http link with the WINS name of the core server like so:
If you took this link and opened safari on the mac, the link would fail. If you replaced the Core server name with the Fully Qulaified Domain Name (FQDN) it found the file, like so:
We then opened the Software Distribution package and changed the Http link to use the FQDN. We then saved the Package and reset the Hash. Next we created a new task and pushed it out to a machine......
Win =Fully Qualified Domain name.
The WINS in their network environment could be setup to work correctly and do the Name resolution, but this is what we did to make it work in the mean time. Let me know if this helps anyone else!
On a Side note --- You might also want to check that you have the latest Mac rollup applied on your core. This roolup is available under the Patch and compliance tool in Security. Check the LANdesk Updates and look for the newest Mac Rollup. After the Mac Rollup is applied you will need to supdate and deploy new Mac agents. While this process can take some time, every rollup released helps expand and streamline the Mac LANDesk Agent's capabilities.
Kothoga -- Technical Support Engineer