+21Casper Version 8.6
Mountain Lion
Although I have specified the computer name in the field for Casper Imaging and updated the information on the JSS with the checkmark as well, after imaging a system I notice that the computer has no name, all I get is localhost. Anyone else seen this issue?
Best answer by ernstcs
As I understand it, there may be hope in the next version of the Casper Suite to put this issue to rest...for now. In the mean time, although you all have some wonderful ways of doing this, I went an even more different route since I bind to AD and that part of the FirstRun works every time since the bind script in FirstRun uses the name in the script. =D
It's probably a terrible way to do it, but I read the computer name out of the AD settings at whatever point works and then pass that through to scutil. I found it more reliable to have a simple script part of first run that calls a custom triggered policy. The policy it calls installs a self-deleting StartupItem with the script below. After FirstRun finishes and reboots, the StartupItem runs and does the rest and then cleans itself up. You wouldn't need to output it to a file like I do, that I use for later reboots where another StartupItem renames the computers back to what they were when they were imaged to maintain the same name, you know the stupid (1) and (2) after the names, etc. I run another enroll command to make sure it does, that's been spotty as hell, too.
TEST TEST TEST, and if you have any questions, let me know. Thanks for all the responses folks!
YOU MUST CHANGE your plist file name, since it won't be UWEC like mine. Also, if you have a preference on computer name case, you'll have to work around that, too.
#!/bin/sh
## Delete an existing computername.conf file if it already exists
if [ -f /private/var/computername.conf ]; then
/bin/rm /private/var/computername.conf
fi
## Create new computername.conf file using AD binding information, and then set the computer name
if [ -f /Library/Preferences/OpenDirectory/Configurations/Active Directory/UWEC.plist ]; then
defaults read /Library/Preferences/OpenDirectory/Configurations/Active Directory/UWEC.plist trustaccount | sed '$s/.$//' > /private/var/computername.conf
set_name=`/bin/cat /private/var/computername.conf`
/usr/sbin/scutil --set ComputerName $set_name
/usr/sbin/scutil --set LocalHostName $set_name
jamf enroll
fi
+12cohawkeye,
Thought I'd chime in. Man, this is still going on, have been off the JN boards, thought it was fixed, but that could be in version 9.
Echo tkimpton. It works, not sure how or why, but it does. I tried to do a snapshot to see what is being installed, but to no avail. Put the patch pkg in your Casper Imaging configuration and wa la, the name will stick. It worked beautifully for me in my last JAMF environment and nothing was making the name stick, except this.
In fact the blank name issue came back because I didn't have the patch in my config, once i re added the patch, name sticks.
John K
+17John - if you don't want to download/use Pacificst, if you download the pkg and drag it into composer, in the left menu bar and select create source, it lets you see the contents of the pkg. You'll see it's basically just doing following (from scripts folder)
defaults delete "$2/Library/Preferences/SystemConfiguration/preferences" NetworkServices
defaults delete "$2/Library/Preferences/SystemConfiguration/preferences" CurrentSet
defaults delete "$2/Library/Preferences/SystemConfiguration/preferences" Sets
defaults delete "$2/Library/Preferences/SystemConfiguration/preferences" Model
rm "$2/Library/Preferences/SystemConfiguration/com.apple.smb.server.plist"
+1We no longer need to remove the preferences.plist with a FirstRun post build script. The naming issue has resolved itself when using the latest Casper Suite Tools.
Versions used:
Mac Mini Mid 2011
OS X 10.8.4
Composer 8.7
Casper Imaging 8.7
Process:
Updated our base OS from 10.8.3 to 10.8.4
Captured the image with Composer 8.7 (Using defaults options)
Updated NetBoot to OS to 10.8.4 with Casper Imaging 8.7
We have tested on two different models of Mac only at this stage, but will continue to test before release into production. I would be good to get others to see this has worked for them?
@CasperSally
No No No! Any pkgs that have preflight and post flight script will run on YOUR machine if you drag them in to Composer!
If you do this you could screw up hour machine!
This is why we use Pacifist!
@CasperSally
No No No! Any pkgs that have preflight and post flight script will run on YOUR machine if you drag them in to Composer!
https://jamfnation.jamfsoftware.com/featureRequest.html?id=1224
If you do this you could screw up your machine!
This is why we use Pacifist!
+3We're seeing this issue losing host name after first run reboot with OS X 10.8.3+ and Casper 8.64. We've had success applying the @drheiner package (http://home.comcast.net/~Nw_systems/Ivy_ACOE_OSX10.8_Patch.pkg) in the Casper Imaging target mode process immediately after the OS DMG (PKG set at priority 2). We'll keep testing but looks good for now.
+7As dsepton said, we'll keep testing for continued success w/ drheiner's pkg. A couple notes, though...
Daniel's pkg removes the following 4 entries from /Library/Preference/SystemConfiguration/preferences.plist
- NetworkServices
- CurrentSet
- Sets
- Model
It also removes the entire /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist file
We're using JAMF's method for "Creating a Minimal Base OS Image", https://jamfnation.jamfsoftware.com/article.html?id=313
This method employs Composer.app, which excludes /Library/Preferences/SystemConfiguration/preferences.plist by default (on v8.64 at least).
This begs the question:
Is /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist the lone culprit?
That plist contains items NetBIOSName, LocalKerberosRealm, WINS info among others.
I'll try a separate test where I exclude that .plist from a fresh OS X 10.8.4 (12E55) minimal base image.
Other notes: Casper Suite 8.64; OS X 10.8.4 (12E55).
Used a MacBookPro 15" Retina (Mid-2012) for minimal base OS image, so need to rev it when we get our newer gear. We've seen this issue on earlier Macs—from Mac Minis, iMacs, MacBook Airs, etc.
+9I am in the process of updating my netboot set with the newest version of Casper imaging and have already updated my server to 8.71. I will report back results concerning the combination of 8.71 and 10.8.4. Has anyone already tested 8.71 to see if the naming problem is fixed?
+20Well, I found this discussion again because my test machine is having its name nuked. >:(
10.8.4 NetBoot, 10.8.4 image push, Casper 8.71, and it's still an issue. Checked the preferences.plist, and sure enough the machine identifier is different from the machine I'm imaging.
Going to try the patch...
+20Patch worked. That's good news...sure wish this would be actually fixed, though.
+29Just ran into this at a client today, trying the patch as part of the imaging workflow.
+27I've found that adding a quick add package to any configuration works wonders. FYI, there are lots of threads using that as an answer and it appears good for normal configs compiled configs and prestages in my experience.
+4Not to beat a dead horse here, Just a question to the guys that have upgrade to 9.0 (or 9.12 as of 10/18/2013) is this issue fixed? I am gearing up our company, to upgrade to 9.0 coming up. I have also been looking at OS X 10.9 I can confirm my package still works on 10.9 (From our Casper Environment 8.72.... please test on yours ) I hoping though I won't have to use this anymore. Thoughts ?
+9I'd also be interested in knowing if anyone has experienced this when imaging Mavericks (10.9.X) with Casper 8.74?
+11
+10Running JSS 9.63 deploying OS X 10.10.2 on mid 2013 MBAirs via target mode imaging. Was having the same issues listed above.
I simply added a quickadd package to my imaging set to run at priority 2 right after the OS block copy and the issue was resolved. Am now trying this method with different hardware.
If I have Casper Imaging create a user account, then it fails again, but the user account is created. If I install a user account with a package from a source like CreateUsrPkg it fails.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
