cancel
Showing results for 
Search instead for 
Did you mean: 

Workstation Registration

George_Knight
Confirmed Champ
Confirmed Champ

When a PC or Laptop is registered in Workstation Registration what does OnBase actually look at? It does not appear to be the hostname as we have had multiple instances of PC/Laptops and even Citrix servers (working as end user PCs) that received BIOS updates and resulted in duplicate hostnames in the OnBase Workstation Registration list. The new instance does not have any licenses so we have to re-register the new instance of the same hostname which results in two os the same hostname with the same license registration.

We would like to determine what OnBase actually looks at to determine a new machine versus one it already knows.

1 ACCEPTED ANSWER

Justin_Fandl
Content Contributor
Content Contributor

Hey George,

 

Feel free to reference the following article to see the specific characteristics used to define workstation registration (LINK). In short, OnBase identifies a workstation based on 14 different machine variables (serial number, model, processor ID, etc.) using WMI.

 

Thanks,

Justin

View answer in original post

3 REPLIES 3

Justin_Fandl
Content Contributor
Content Contributor

Hey George,

 

Feel free to reference the following article to see the specific characteristics used to define workstation registration (LINK). In short, OnBase identifies a workstation based on 14 different machine variables (serial number, model, processor ID, etc.) using WMI.

 

Thanks,

Justin

George_Knight
Confirmed Champ
Confirmed Champ

Thanks Justin. This is very helpful. We need to have those who push the BIOS updates warn us as to when these occur then we will check Workstation Registration for duplicate hostnames. We will register the the new instance and revoke the old instance.

Steven_Hyde
Champ in-the-making
Champ in-the-making

We just ran into the issue this past week. We are planning on doing Monthly Firmware/BIOS updates and I don't see manually fixing 100's of workstations as a viable solution. Did you find another way to avoid this?

 

Thanks, Steve