Build 7501: Asset Deletion Issues
Platform:
HP ProLiant Blade BL460c G1
Windows Server 2003 R2 Enterprise Edition with SP2
Microsoft SQL Server 2005 SP2 + GDR (9.0.3054)
ServiceDesk Build 7501.
ServiceDesk Versioning:
Base Install: Build 7021.
Patch Order: 7022. 7500. 7501.
Database Type
Microsoft SQL 2005 DB.
Issue #1: Assets Being Deleted
A new asset is added to the database via "new scan" & utilizing the DNS name with domain credentials.
This asset is automatically assigned to a user (regardless if they were the last logged on or not) based on some unknown criteria.
Any PREVIOUSLY assigned workstation asset that this user was assigned to is completely removed from the asset database.
How on earth is an inventory system supposed to work correctly if everytime I'm adding a new asset to this system, it's first auto-assigning this device based on some unknown criteria, and secondly is auto-deleting an asset that is still in our inventory.
Issue #2: Asset Component Assignment Not Updating
An asset is added to the system via the "new scan" option.
This asset is then either automatically assigned (if the auto-assignment worked correctly), or else it is assigned as required to the appropriate AD user.
Next, an LCD Asset is added to the inventory. During asset creation, this item is marked as "In Use" and assigned to the previously created asset. Upon completing the asset creation, it is shown as only "in use" and not currently attached to any asset in the LCD Assets inventory screen. Clicking "in use" and re-assigning it to the same asset as before generates the appropriate workstation, user & department asset assignment.
Issue #1 is a production stopping critical bug. How can we have faith in an asset system that will randomly delete or remove assets? Simply re-adding them is NOT AN OPTION, as those assets may be housed off-site and inaccessible to ServiceDesk's scanning engine.
If we are to trust ServiceDesk for our asset inventory, then it needs to operate appropriately.
I'm open to providing any and all information required, but this bug needs to be addressed as soon as possible.
HP ProLiant Blade BL460c G1
Windows Server 2003 R2 Enterprise Edition with SP2
Microsoft SQL Server 2005 SP2 + GDR (9.0.3054)
ServiceDesk Build 7501.
ServiceDesk Versioning:
Base Install: Build 7021.
Patch Order: 7022. 7500. 7501.
Database Type
Microsoft SQL 2005 DB.
Issue #1: Assets Being Deleted
A new asset is added to the database via "new scan" & utilizing the DNS name with domain credentials.
This asset is automatically assigned to a user (regardless if they were the last logged on or not) based on some unknown criteria.
Any PREVIOUSLY assigned workstation asset that this user was assigned to is completely removed from the asset database.
How on earth is an inventory system supposed to work correctly if everytime I'm adding a new asset to this system, it's first auto-assigning this device based on some unknown criteria, and secondly is auto-deleting an asset that is still in our inventory.
Issue #2: Asset Component Assignment Not Updating
An asset is added to the system via the "new scan" option.
This asset is then either automatically assigned (if the auto-assignment worked correctly), or else it is assigned as required to the appropriate AD user.
Next, an LCD Asset is added to the inventory. During asset creation, this item is marked as "In Use" and assigned to the previously created asset. Upon completing the asset creation, it is shown as only "in use" and not currently attached to any asset in the LCD Assets inventory screen. Clicking "in use" and re-assigning it to the same asset as before generates the appropriate workstation, user & department asset assignment.
Issue #1 is a production stopping critical bug. How can we have faith in an asset system that will randomly delete or remove assets? Simply re-adding them is NOT AN OPTION, as those assets may be housed off-site and inaccessible to ServiceDesk's scanning engine.
If we are to trust ServiceDesk for our asset inventory, then it needs to operate appropriately.
I'm open to providing any and all information required, but this bug needs to be addressed as soon as possible.