![]() So in theory, in your environment, you could "block" the 10.9.5 update be using the "ignore" flag in the built-in command line softwareupdate tool. To get the update to show as available again you will need to do the following command ``` Sudo softwareupdate -ignore OSXUpdCombo10.9.5 Now when you run ``` You can then choose to ignore software updates based on the list like this ``` Software Update found the following new or updated software: On my 10.9.3 machine this was the result: Software Update Tool ![]() To get a text list of the available software. On a test machine you can run sudo softwareupdate -list I guess all I'm saying is that while I agree troubleshooting and solving the actual problem is best, lets try not to be too harsh and judge those that don't (yet) have expert troubleshooting skills. Maybe he was under pressure from teachers and students to prevent the systems from booting into a black screen and it wouldn't have been unreasonable for him to conclude that blocking the update until he was able to spend the time figuring out the issue was the quickest course of action. Same would be true for many folks here.īut take a quick look at ahopkins' profile here and you'll see he's been a teacher for the last 20 years and only in the last year took on a technology role, so he's still learning this stuff. People like yourselves are experienced master technicians and solving a black screen at boot issue is probably like a walk in the park. That said, we also have to take into account everyone's individual skill level here. I sometimes have a bad habit of jumping in and providing an answer or possible solution without actually stopping to ask what the real need is for the request. ![]() I would agree with your assessment that just blocking things because of an initial problem isn't the best approach. Since they're able to install it at all I assume they have admin rights on their Macs, which means its really kind of impossible to stop them from installing it if they are determined reasonable, which is kind of why I suggested in the second half of my last post that I personally would try to solve the black screen issue and also offer the update in Self Service to ensure the proper update is being applied, rather than attempting to block it. Otherwise you're really playing a game of whack-a-mole. That way you get to control what gets installed and they get to install something they obviously want to install. If so, consider actually posting that into Self Service for your students to install. You may want to see if the Combo update actually installs OK and doesn't cause the black screen problem. We avoid installing the latter 'delta' updates because they traditionally tend to be more problematic. The former will update anything from 10.9.0 through 10.9.4, and the latter will only update a system already on 10.9.4. Have you tried that?Īlso, are you sure the students are installing the "Combo" update and not just the regular or delta update. Its possible a simple PRAM reset might resolve some of those cases. Personally though, I would try to address the black screen issue. If its set up to only block "Installer.app" and you enable the option for exact matching, it should ignore the command line "installer" process, meaning scripted installs or Casper Suite pushes shouldn't be affected. But any other valid packages that are double clicked on would also be blocked with that method. Unlike full OS installers which are actually applications with an executable, double clicking a package installer simply opens the installer app, so that's the only process that could be blocked. When you open those the only process that shows up is "Installer.app" as I mentioned above. You can't block the Combo or delta update installers like that with Restricted Software.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |