KACE Product Support

This will do the same thing, but use a drop down for departments instead.

# Edit This item to change the DropDown Values

 

[array]$DropDownArray = "Finance", "IT", "HR"

 

function Return-DropDown {

 

$Choice = $DropDown.SelectedItem.ToString()

$Form.Close()

# Edit for registy path

    New-Item -Path HKLM:\Software\KACE\Dept -Value $choice –Force

 

}

 

[System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")

[System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")

 

$Form = New-Object System.Windows.Forms.Form

 

$Form.width = 300

$Form.height = 150

$Form.Text = ”Select Department”

 

$DropDown = new-object System.Windows.Forms.ComboBox

$DropDown.Location = new-object System.Drawing.Size(100,10)

$DropDown.Size = new-object System.Drawing.Size(130,30)

 

ForEach ($Item in $DropDownArray) {

$DropDown.Items.Add($Item)

}

 

$Form.Controls.Add($DropDown)

 

$DropDownLabel = new-object System.Windows.Forms.Label

$DropDownLabel.Location = new-object System.Drawing.Size(10,10)

$DropDownLabel.size = new-object System.Drawing.Size(100,20)

$DropDownLabel.Text = "Departments"

$Form.Controls.Add($DropDownLabel)

 

$Button = new-object System.Windows.Forms.Button

$Button.Location = new-object System.Drawing.Size(100,50)

$Button.Size = new-object System.Drawing.Size(100,40)

$Button.Text = "Select a Department"

$Button.Add_Click({Return-DropDown})

$form.Controls.Add($Button)

 

$Form.Add_Shown({$Form.Activate()})

$Form.ShowDialog()

I'll probably use some form of this. With Powershell. This will prompt the user, and set the reg key based on what they select. Now hopefully they know what department they are in.

$title = "Message from Admin"
$message = "Please Select Your Department"

$Finance = New-Object System.Management.Automation.Host.ChoiceDescription "&Finance", `

    "Sets Finance as Department"

$IT = New-Object System.Management.Automation.Host.ChoiceDescription "&IT", `

    "Sets IT as Department."

$HR = New-Object System.Management.Automation.Host.ChoiceDescription "&HR", `

    "Sets HR as Department."

$Maintenance = New-Object System.Management.Automation.Host.ChoiceDescription "&Maintenance", `

    "Sets Maintenance as Department"

$options = [System.Management.Automation.Host.ChoiceDescription[]]($Finance, $IT, $HR, $Maintenance)

$result = $host.ui.PromptForChoice($title, $message, $options, 0) 

switch ($result)

    {  0 {New-Item -Path HKLM:\Software\KACE\Dept -Value Finance –Force}

 1 {New-Item -Path HKLM:\Software\KACE\Dept -Value IT –Force}

        2 {New-Item -Path HKLM:\Software\KACE\Dept -Value HR –Force}

        3 {New-Item -Path HKLM:\Software\KACE\Dept -Value Maintenance –Force}

    }

We bit the bullet and organized our Active Directory OUs according to department. I then created the necessary LDAP labels based on those OUs. It took a lot of time up front but it has been worth it in the long run. There have been other instances where having the departments "automatically updated" based on the OU have come in handy. For instance, we can easily make custom patch schedules for departments and as long as the machines are placed in the proper OU everything works smoothly. Moving the machine into the proper OU is part of our deployment workflow now so it happens 99% of the time.

Do you already have the asset info in a csv, or will you be flying blind?