System information for mac os x 10. • Overview: View the specification information about your Mac. (You can see the versions, modification dates, and locations of each software item.) To open System Information and display the system report, click the Launchpad icon in the Dock, click Other, then click System Information. • Your computer’s software, including the operating system, apps, and kernel extensions. In the System Information app on your Mac, choose Window > About This Mac, and then click any of the following. You can view information about your Mac, including the model name, the macOS version you’re using, and more. This feature is not available right now. Please try again later. I'm running MS Office 2011 on a Mac (High Sierra). Two problems have cropped up recently. Problem 1: Files - Answered by a verified Microsoft Office Technician. We use cookies to give you the best possible experience on our website. ![]() Now that macOS 10.13 High Sierra is out, it’s time to start taking about High Sierra stuff! Munki 3 added support for upgrading macOS via the Install macOS.app for Sierra and High Sierra. How to get mac address for my samsung galaxy 3. A Munki admin need only download the installer from the App Store, and do munkiimport /Applications/Install macOS High Sierra.app to import the High Sierra installer into their Munki repo. But there’s a wrinkle. Many people (including yours truly) were sometimes getting an installer application “stub” when downloading the Install macOS High Sierra application from the App Store. This “stub” application did not include the Contents/SharedSupport folder or its (very important) contents. The needed resources were instead downloaded “on-the-fly” when you ran the Install macOS High Sierra application. This “stub” application is not useful as something to import into your Munki repo, or to use with AutoDMG or autonbi, or similar things. For these you really want the full installer, that is, one that contains all the needed installation resources in Contents/SharedSupport. Many theories and ideas were put forth as to what caused one to get the stub vs the full installer. While I’m still not 100% sure about this, I think we’ve narrowed in on the cause. It appears that when the App Store is downloading the installer app, it also uses softwareupdate to get the resources that normally reside in Contents/SharedSupport. If com.apple.SoftwareUpdate has been configured to use a CatalogURL that points to a softwareupdate catalog that does not contain product URLs for the needed Install macOS High Sierra resources, you get the “stub” application instead. If, however, softwareupdate is using either Apple’s default CatalogURL, or is pointed to an internal CatalogURL that contains the needed products, you get the full installer. Currently, the needed resources are Product 091-34298, “Install macOS High Sierra”, but this will almost certainly change over time. TL;DR: to get a full High Sierra installer from the App Store, make sure softwareupdate is pointed at Apple’s softwareupdate servers or an internal server in which you have synced and made available the “Install macOS High Sierra” product. Thanks to many people on the MacAdmins Slack for chipping in with their observations. Ian Rohrbach says: I maintain a small network of office Macs (without OS X Server) and every machine is downloading the ‘stub’ tiny installer rather than the complete installer via App Store. None of the machines have altered the catalog or run a beta release, which makes the stub installer even more curious to me. As an admin (and user!) it drives me nuts that we can not download the complete installers directly from like you can with Combo Updates, but I digress. Here you say: “TL;DR: to get a full High Sierra installer from the App Store, make sure softwareupdate is pointed at Apple’s softwareupdate servers or an internal server in which you have synced and made available the “Install macOS High Sierra” product.” But how do you do that? What is the proper software update command to point to the proper server to download the full installer? ![]() Can you provide the full command necessary? Removing the softwareupdate.plist has no impact. Thank you in advance for elaborating further on this solution. From what I can tell, it is impacting a lot of people in similar shoes. Posted: Today at 1:00 PM by tnielsen Thanks How are you guys disabling this for new computers that have never had office on them? The plist isn't there so it won't write. Since the apps are sandbox, the plist never shows up. I'm thinking I'm missing something. Whether or not the plist is present doesn't prevent the defaults write command from taking place. For the main commands to nix the splash screen, this is set once on a machine-level before the applications are launched and is immediate. The autoupdate disable has to be done in the user, but could be written into the User Template folder to take effect for each user when they first login. Existing users would need the command run for each account. I found today as of the 9.93 release (maybe before?) that there is a new built-in Managed Preferences template already for 'Microsoft Office Auto Update' which has the WhenToCheck and HowToCheck options pre-built, and supports custom settings (i.e. ChannelName = 'External'). I'm testing a profile now to push some of our advanced users to use the InsiderFast channel with daily checks, and another for 'normal' users (without Admin rights, ideally) to Manual check, External ChannelName, and DisableInsiderCheckbox. Did you find anything else out about this? I had setup some options for the autoupdate2 using Managed Preferences, but also discovered after the fact that they appear to be deprecated now. Trying to find all of the available options for MAU, as I DO want to enable AutoUpdate (as of MAU 3.6 I think, the process runs as System and doesn't prompt users for Admin credentials to install the updates).
0 Comments
Leave a Reply. |