Jump to content

Recommended Posts

Posted

Hi,

 

We'd like to rename our Mac to have a standard naming convention like our PC's execpt that we can't seem to configure a workflow to do this for us.

 

We'd like to prompted for a new hostname (MAC-ASSETID), Mac to be renamed to this name. OD to be populated with this new name and computer account in AD to be updated.

 

Does anyone have a workflow that does this?

 

Thanks,

 

Michael

Posted
You want the HostName Form - it doesn't let you do anything when creating the workflow but when you run the workflow as part of your build, you are prompted for station details
Posted

I've tried that too.

 

I created a new task called rename.

 

Set the first stage as HostName Form, second as configure with the rename option selected.

Posted
When doing this hostname rename, I found it worked a lot better when run close to the start of the deployment workflow. Try running as second or third step before reinstallation of the image.
Posted

We don't want to have to redeploy just to rename.

 

Our clients are all working fine but we want to change the name. This name needs to be updated in AD and OD too.

Posted (edited)

You don't have to… just create a workflow without the reimage step. Easy

 

You still have to tidy up your OU though..

Edited by Oddbod
Posted (edited)

I'm having another attempt at this and I still can't figure it out.

 

I've attached screenshot of the task sequence in deploystudio with domain name obscured with any app deployment removed. Am I missing anything glaringly obvious?

The usernames and passwords work with the unedited deployment task, so I know they are correct.

The name changes in workgroup manager but the OD and AD are not changed..

 

1.JPG

2.JPG

3.JPG

4.JPG

 

Thanks,

 

Michael

Edited by linkazoid
Posted

Configure task step before hostname task step,

else computer name won't be available for use as hostname, so will be skipped (and default OU_Group entry for last connection attempt will be used)

Then tidy up OU_Group as there will be new entries…

Swings and roundabouts for this bit of maintenance… what you automate in one, you have to handball in the other but ymmv.

When I mentioned this to my NM about how we could handle this via mac address recognition, his reply was “this is a college, students will attempt MAC address spoofing”

…mind you, based on what was being taught in their computer science lessons, I doubt any student would have heard about spoofing ( or how to do it)

No, this was not a major fee-paying college, some of the students were here because ‘it was this or the dole queue’

Posted

Spoofing MAC addresses in OS X (and probably Windows) requires administrator privileges with root access as well as an understanding of the command line. I'm not saying it's impossible but seeing as students in most educational institutions log on as network users with no admin privileges by default then I doubt if they could do it even if they knew how to.

 

Antonio Rocco (ACSA)

Posted (edited)

Erm… they teach them about it on the Cisco section of the CS course, so that they are aware of it and how to trace it… but you are right… it should be a rarity.

However, what students learn, they inevitably try (sigh)

I suppose it keeps us on our toes, I suppose that's why the CompSci dept are disconnected from the rest of the network most of the time too!

Edited by Oddbod
Posted
Cheers for the help guys, but we still can't get this to work. :(

 

It still only seems to update the deploystudio database with the correct name.

 

Yep, that's all it does. It won't have authorisation to change the OU entry - you have to do that bit by hand. I'm sure it's scriptable as you can run a shell script option, but I can do the OU group admin myself.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...