How to set computer name using K1000 database during SDA deployment?

Hi all !

We are in the process of automating the reinstallation of our Windows PCs. We deploy them thanks to SDA (K2000). In addition, we would like to retrieve the names of the PCs that were used in SMA (K1000).

Is there a way to do it?

The documentation indicates that the "Get / SetComputerName" task is used to read the K1 database. Does K1 refer to the K1000 database? What command should I run to read this database?

Can the KUID also help find the name stored in SMA?

Here is the order of tasks we currently use:

  Pre-installation task:

  • Get Computer Name
  • Diskpart Windows 10

  Intermediate tasks:

  • Set Computer Name

  Post-installation tasks:

  • KMS
  • VNC
  • Apply a KUID value to the K1000 agent
  • Agent installation
  • Inventory
  • Bitlocker activation
  • Driver installation

Thanks everyone!

0 Comments   [ + ] Show comments

Answers (2)

Posted by: Nico_K 1 year ago
Red Belt

  • I believe I actually have the complete command. I forgot to add the additional information (IP addresses, username and password).
    I can't test yet, my virtual machines appear to be offline. I will be back next week. - superdada 1 year ago
  • Hello, I did some test and indeed it works. - superdada 1 year ago
Posted by: superdada 1 year ago
White Belt

Following this idea, I would also like to use get / setcomputername multiple times during a single install.

So it would look something like this:

  • The administrator can decide to rename the PC.

getcomputername_x64.exe /timeout:120 /dialog

  • The PC retrieves the name found in the K1000 database.

setcomputername_x64.exe /k1mysql /k1ipaddress: /k1dbname:ORG1 /k1dbuser:***** /k1dbpass:******

  • If the administrator renamed the PC, then applied the new name.

setcomputername_x64.exe /notrandom

I am currently having an error while retrieving the admin name backup file:

Unable to open x:\18DBF23F5848, it may not exist. Was GetComputerName.exe used as a preinstall task ?

Do you know how to fix this error?

Could the switch /drive: solve the problem? If so, I didn't understand how it works either.

Thank you in advance !

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ