TDX ITAM/Sassafras Asset Verification

Required for: All new computers coming into the Purdue environment

When to be completed:

1. When a new Windows or Apple computer is deployed.
2. When a Windows or Apple computer is reimaged and/or repurposed.

*Please do not give replacement computers the same name as their predecessor*

Instructions for validating a new device in TDx ITAM/Sassafras web interface.

1. Connect to the campus VPN if you are off campus.
2. Login to the TDx ITAM/Sassafras web interface https://pwlkeyserver.itap.purdue.edu.
   
   
3. Select the Computer link from the page menu and select all in scope. Confirm you can see the Search for a Computer field, too.
   
   
    
4. Search for an asset by either Name or Service Tag using the Search for a Computer field.
   1. If no computer is found, it means it doesn’t have the ITAM client installed, or the ITAM client is installed, but the asset hasn’t checked in with the ITAM server; off campus connections require the campus VPN connection before an asset can check in. Computers ordered with Autopilot will have the client installed automatically.
      
      
5. Select the asset to view properties; add the information from the TDX ticket to the following fields for the asset validation process:
   1. Categorization - once you move the asset to the Division it belongs in, mark it Anchored, so it stays in the Division it was moved to.
      
      
       
   2. Asset – add data necessary for ISO audit purposes. If something is not available, leave the field blank.
      
      
       
      1. Department - the end user's department as it is listed in Success Factors AND TeamDynamics. If this is a shared device, list the department that paid for it.
      2. Location - city the asset is located in. Hammond, Westville, Fort Wayne, Indianapolis, West Lafayette, Columbus, etc. If the asset is located outside of Indiana, please put REMOTE.
      3. Building – university building code for the building asset is located in. If the asset is REMOTE, please put REMOTE.
      4. Room – if known, add the room the asset is located in. If the asset is REMOTE, leave this field blank.
      5. Owner – this is the top level of an organization. Examples: WL Office of the Provost, WL College of Veterinary Medicine, PFW - Academic Accountability and Student Success, and PNW - College of Engineering and Sciences. If you need assistance determining the owner, reach out to the PUIT Asset Manager.
      6. Managed by – use the applicable support group in this field.
         1. FW Purdue IT - CSS
         2. FW Purdue IT - LS
         3. INDY Purdue IT - CSS
         4. NW Purdue IT - CSS
         5. Purdue IT – NW
         6. Purdue IT – WL CSS
         7. WL Purdue Athletics IT
         8. WL Purdue IT - RHTS
         9. ​​WL Purdue IT - LS
         10. WL Purdue TAP IT
      7. Confirmed by – click on Confirm and Lock the asset record information.
          
   3. If this is a primary machine, complete the Custom field Primary User; if this is not a primary machine, move to Step 5.d. 
      
      
       
   4. Depending on the verification type, add the appropriate asset note (see examples):
      1. Net new ticket <insert ticket>
      2. Net new ticket <insert ticket>; no primary user (shared workstation)
      3. Replacement ticket <insert ticket>; replaced <insert old computer name>
      4. Replacement ticket <insert ticket>; replaced <insert old computer name>; this asset is running a campus digital sign
      5. Use the Notes field to capture any important information someone would need to know about this asset
         
         
6. Close the Asset record and click Save.