Set Building at Imaging Time?

[tuinte]

Hey all:

JSS 9.21

We have network segments to set a machine's building, but sometimes we're imaging (Netboot, Casper Imaging) a computer not at the destination office, so it gets the Building it was imaged in, not the Building we want. Anybody dealing with this?

The dream for our setup would be the ability to assign a Building to each Configuration, as our Configurations are mostly determined by office. I feel like I'm missing something obvious, though.

(I know Sites can be set at Imaging, but all our Smart Groups make use of the Building criterium, and though everyone's Site is the same as its Building, Sites has the heavy limitation of only one being applicable to one smart group/policy.)

Any help is appreciated!

Michael

EDIT: Grammar cleanup.

[pcarrier]

There is a setting in Network Segments to overwrite settings in inventory. Try checking that box and anytime the user enters that segment their building and department will be changed in inventory.

[pcarrier]

Duplicate Please Disregard!

[pcarrier]

Duplicate Please Disregard!

[tuinte]

I had looked into that, but I do want the Building setting to be permanent once set to the correct building. I'm testing creating a QuickAdd package, one for each office configuration, with the Building setting, to be installed on first boot when imaging. I'm guessing it will work, but 99.9% of the QuickAdd is completely redundant, so it kind of has that icky stink of inefficiency all over it. I'm working on my OCD.

M

[bentoms]

@tuinte Are these for like a 1-1 deployment?

Do you know the end users whom will be having the devices & do you use something like AD?

[JRM]

Just a thought - By forcing the building, one also forces them to try to use that building's distribution point - which could be extremely slow over a possible WAN/Internet connection. Doing any sort of package based post imaging steps could be a nightmare forcing the building.

[tuinte]

Distribution Point is determined by network segment, regardless of Building. You did, however, give me a panic attack for a second.

[tuinte]

@bentoms][/url:

Yeah, we're just imaging a machine on the spot. As of now, the workflow is:

1) Netboot machine
2) Image with appropriate configuration (named after Building)
3) Going into the JSS and manually updating the Building
4) Give computer to new employee

Not a huge deal or anything, but we just want to get rid of step 3. It's that little annoying task that hangs around.

Yes, we're using AD. What's your idea?

M

[Cyrus11]

I've recently had to deal with this issue and I fixed it by editing the LDAP mapping in system settings to pull the relevant department/building information from fields in the LDAP server. You still have to create the Buildings and Departments in the Network Organization pane to match the ones you use in LDAP, but once you're done, user initiated enrollment using the quickadd package will assign the location based upon the user and whatever policies you have associated with location/department as well.

[Cyrus11]

I'm a button masher!

[bentoms]

@tuinte. It was something along the lines of what @Cyrus11 said.

Use the JSS's LDAP mappings & adding to a user manually through the JSS.

OR

Populate the user data at login by enabling the setting in the JSS & then rubbing the below at every login:

sudo JAMF recon $3