I’ve been dealing with this issue for a good while now and there are countless articles online that talk about this but there hasn’t been a solid fix yet. In most cases users are playing with the Finder and Sidebar preferences but without luck. This is one of the only steps that seems to gets messed up with permissions errors or bad links when you use a default profile script. Everything else seems to work but starting with OS X 10.10 this has been broken.
The cons to this route is that fact that you need to remove/delete the user you build your default profile from but if you are really only building your image to deploy this really isn’t a big deal. If you need to go back and make adjustments to the profile just create that same user again, make your needed adjustments run the default user profile script then remove the user again.
It is an extra step but it’s a step that makes a lot of people happy. We have tons of students and faculty that will love to have these links back in the finder again.
For future “Default User Profile” scripts I think I’ll go back to creating an alternate user from “Administrator” and start using a user called “default”. This way I can keep the local “Administrator” in place and just use the “Default” user for creating a custom user.
If you’ve run into the issue of imaging a BootCamp partition and it won’t boot into Windows or you see the message that the Windows Bootcamp partition cannot be blessed then you may get the run around trying to find a quick simple solution as I had.
Luckily WinClone has a quick built in option/utility that will make your Windows BootCamp partition properly boot.
If you are running on a new model Mac you could have an issue where the Mac does not allow you to boot into the newly created Bootcamp image. To get around this we need to make the Bootcamp partition EFI bootable by using Winclone. You should see your Bootcamp partition on the left side of the program and you will need to right click on the Windows BootCamp partition and select “Make EFI Bootable”. You do not need to do this for older hardware which should be 2014 and older Macs.
Right now there maybe scripts or other work arounds to do this but since we already own a copy of WinClone this makes quick work of this issue.
Prior to OS X 10.9 Mavericks here at the college we would use the option in the “Directory Utility” app to mount the Active Directory home drives. This was done by checking off “Use UNC path from Active Directory” but with OS X 10.9 Mavericks & OS X 10.10 Yosemite there was the adoptions of SMB2 which does not play well with Microsoft’s version of SMB. We would have drives mounting but not the drives we wanted. We would normally want their home folder mounted as (ex. /studentname) but instead it was now being mounted as (ex. share/studentname). This is how we’ve been running for the past two years and haven’t had much luck fixing it.
Today with the help of a co-worker we were able to come up with an AppleScript that fixes this. Below is the simple script that I saved as an executable app and placed into the /Library/Scripts folder in our images. From here I added the app as a login item in the default profile. Once any user logs in the script would check to see what the users name is then look to Active Directory to poll what their Home Drive is. Next the script converts the backwards slashes “\” (used in the Windows World) to forward slashes “/” (Unix World) then mounts the drive.
I’ve been testing this on a number of stations and now have it deployed out to some of our labs.
If you want to use this script you need to make sure you go into “Directory Utility” and un-check “Use UNC path from Active Directory” since we no longer need this and now relying on this AppleScript to do the work.
In the script provided you will need to change “DOMAIN” to your campus domain. For an example our college it’s just “CAMPUS”.
Here’s the script below to use or feel free to download it:
When I have the free time I want to convert this into a .plist script to use with launch daemon instead of relying on an app in the login items to make it a little cleaner. Until then this will do the trick and something that I’ve been looking into for some time now without success.
Hope this helps out others that have been looking for a similar solution.
Here at work we have a 2008 Xserve and for the past couple years I’ve only used it as a simple file share server since the highest OS that could be installed was OS X10.7 Lion. I would love to use the server for more since it has plenty of HD space and when it comes down to it, the Xserve is still a powerful computer.
A couple weeks ago I decide to get the server running with OS X 10.10 Yosemite by doing a couple upgrades along with a OS X 10.10 modified install. At first I upgraded the ram to 16GB then installed OS X 10.10.3 Yosemite with the help of an article here https://github.com/TMRJIJ/OS-X-Yosemite-on-Unsupported-Macs that explains how to create an OS X 10.10 Install on a USB stick or drive that is modified to install on older hardware. Once I had the modified OS Install I plugged into the server and installed 10.10.3 without any issues until I realized how laggy the video was. This was both local video output and through screen sharing.
I think one of the big reason Apple removed Xserve from later OS’s past 10.7 Lion was due to the video card. OS X has become very dependent on the GPU and since the stock video cards in the Xserve are bottom of the line the cards they just could not handle 10.10 Yosemite. So from here I got looking online to find a fix.
After looking around I can across a video here https://youtu.be/9AZzSgIYIac where “N90X” decided to give this same project a try and he ended up swapping out the video card. With the help of this I was able to track down a video card off eBay that was originally a stock card for Mac Pro’s. The card I purchased was a “Apple 630-9643 Mac Pro A1289 NVIDIA GeForce GT 120 512MB Video Card”.
As soon as I received the card I quickly installed it to now find the server running smooth video. Both the card video output and screen sharing ran smooth without any issues. So far everything looks great and you would never know this server was never supported.
The one issue I know of for this setup is OS Updates. If I were to update the server to 10.10.4 when it comes out the server will not boot as the update will replace the “PlatformSupport.plist” file which essentially tells the OS which hardware is approved to run. With that said, theres a quick fix, simply replace it. Just keep a backup of the file and once you do an update you can either throw the server into Target mode and replace /System/Library/CoreServices/PlatformSupport.plist or just add in the server model & ID info. For my setup I partitioned the primary HD and keep the old OS X 10.7 Lion install so I just need to boot into the old OS, replace the file then reboot.
All in all Yosemite works great on a 2008 Xserve after modifying a 10.10 Install and upgrading the video card. From here I will be installing Server App and using more features that Server App offers. It’s a great server for DeployStudio, OS Updates and more.
A few images of the server:
Install of OS X 10.10.3 Yosemite on Xserve
Xserve with upgraded ram to 16GB and the new/used video card
Old Xserve Video Card
New/Used Video Card that was needed to get the server running video properly
This past year I’ve been looking to step away from using Faronics Deep Freeze and find an alternative that will handle a similar task of cleaning the user profiles after a restart, set time or day of the week. Sure Deep Freeze has a lot of benifits but we wanted to look into a cheaper solution. For the past few months I’ve been running this setup in our busiest area at our campus (our student commons) and it has been working great.
Why do we need it? In the run of a day or week we can have countless users logging into a mac desktop using Active Directory credentials and over time the user profiles can eat away at the HD space. That said your average user is browsing the net and so their user profile may only be a small percentage but mixed in with users that dump files onto the desktop or other areas this space can build up fast. This is where Deep Freeze came into play. Deep Freeze would clean up the computer after a restart or set schedule to help keep the comptuer HD clear of un wanted files.
What do these scripts do? With the below scripts in place they essentialy remove any unwanted users. By default the script is set to remove all users except for the “Administrator” & “Shared” user. All other users will be removed. This can be adjusted easily to add other local users. The script included is set to run at 3:30am every Saturday morning. We went with this since most computers are sitting with a 1TB HD and we do not expect computer to fill up that quick. Having it set to a week also gives users a grace period for their files. If they forget to copy/backup files one day they will still be there the next day (unless it’s the next day that the scipt is set to run). The other benifit is that if there is a power bump their files will still be located on the computer once it is turned back on.
How do these scripts work? There are three files as listed below. #1 is the launchd file that will run on schedule to run to run the primary script that does the work. File #1 is the file you can edit to adjust the time or day you wish to have the script run. ** Keep in mind, if you make changes after the script is deployed you will want to make sure you unload the .plist file and then reload the updated file.
File #2 is the actual script that does thew work to remove the users. There arre two main steps. The first step will remove all uses except for “Administrator” & “Shared”. The second step dumps the files located in /private/var/folders/*. This folder contains cache files from the users that have logged in. We do not want to remove the fodler itself, just the contents.
File #3 is a simple command script that loads file #1. We use deploy studio for deployment so having this as part of the workflow just loads #1 script so we do not need to send out the command over ARD or manually.
On your Deploy Studio server go to your “DeployStudio” shares. This folder is normally at the root of your HD as the shares folder for Deploy Studio. (This can also be named something else or located elsewhere but most often this is the name and location. In the “Files” folder you need to copy the first two files “com.mactech.cleanusers.plist” & “delete_non_admins.sh”. Next go to the scripts folder and copy the ”load_cleanusers.command” file to this location.
From here open up the “DeployStudio Admin” application. For deployment you need to add these files into a workflow and run these files during post ghost.
To add the two files “com.mactech.cleanusers.plist” & “delete_non_admins.sh” you need to add “File Copy” into your workflow twice as seen in this image.
Since we already added the need files you just need to choose the “File” dropdown menu and pick the files as you can see in these images. As seen in the images you want to make sure each file is placed into the correct location. “com.mactech.cleanusers.plist” will be copied to “/Library/LaunchDaemons” & “delete_non_admins.sh” will be copied to “Library/Scripts”. Also make sure you “Automate” these tasks.
The next step in the workflow is to add “Generic”. With this step in the workflow select the “Command” dropdown menu and choose “load_cleanusers.command”. Make sure you check off “Postponed execution” & “Automate”.
From here the script will be loaded when the computer finishes post ghost.
The script by default that’s included is set to wipe all users except for the “Administrator” & the “Shared” user. If you have other users that you want keep on the system you can alter the “delete_non_admins.sh” script to reflect users you want to keep on the computer. You wouldn’t normally install this on laptops or individual computers but if you do make sure this script reflects the users that need their profiles keep.
As this script sits it is set to wipe the other users every Saturday Morning at 3:30am. You can easily change this by opening the “com.mactech.cleanusers.plist” file and adjusting the “StartCalendarInterval”.
Hope this helps those out that are looking for a DF alternative.