Key features
User Synchronization
- Daily cron jobs sync users from Azure AD groups.
- Inactive users remain visible unless removed from Azure.
- Guest users can be marked separately or assigned to a “service account” department.
- Deleted users move to a deleted list but may reappear if still active in Azure.
Department & Service Accounts
- Departments updated automatically via Azure sync.
- Manual updates possible but may be overridden by sync.
- Service accounts can be grouped under a dedicated “Service Account” department.
Mac Agent Installation
- Agent installation required for Mac devices to sync data.
- Logs accessible via Mac terminal (Library/Logs/Mac Agent).
- Data posting verified through server inventory details.
- Troubleshooting involves reinstalling agent and checking logs.
Notification & Procurement Workflow
- Notifications triggered for procurement requests, supplier invitations, quotation uploads, and status changes.
- Procurement team members receive CC notifications.
- Approval possible via email (approve/reject buttons) or portal login.
- PAB (Procurement Approval Board) members receive direct notifications.
Multi-Company Asset Management
The system supports multiple companies within the same portal. Companies such as Trade King, Konish Mining, Trade King Home Care, Big Tree, and Dairygold can be maintained separately. The system applies a company-matching rule between the user and asset before an asset can be allocated. An asset belonging to one company cannot be allocated to a user belonging to another company. Assets can be organized according to the company and location to help maintain separation between different Rashmi Group entities.
Company-Wise Inventory Visibility
Asset and device visibility can be restricted based on the user's company. Managers should be able to view only the inventory belonging to their respective company. The same company-wise restriction can also be applied to Network Inventory, so a manager working under one company does not see the network inventory of other companies.
Network Inventory
Newly discovered computers can initially appear in the Trade King Network Inventory. The inventory can be reviewed and the company of the discovered asset can be changed. Once an asset is assigned to its correct company, the expected behavior is that it should no longer remain visible in the common network inventory and should instead appear under the appropriate company's inventory.
Company and Location Mapping
Locations can be created for individual companies, and assets can be mapped to those locations. Company and location information can then be used to segregate assets and users. The discussion also considered automatically identifying companies based on IP address ranges or domain information. IP-based company allocation was discussed as a possible future approach, while domain-based mapping was also considered.
Active Directory Agent
An AD agent can be installed on the domain controller to discover machines connected to the Active Directory environment. The discovered systems can then be synchronized into the portal, after which assets can be assigned to users and companies.
Non-AD Agent
A non-AD agent can be installed on machines that are not connected through Active Directory. This provides an alternative mechanism for discovering and collecting device information. The discussion also highlighted using AD and non-AD/agent-based discovery together as backup mechanisms so that asset information is less likely to be missed.
Asset Allocation
After devices are discovered and users are imported, assets can be allocated to the appropriate users. The user and asset company must match before the allocation can be completed.
Network Troubleshooting
The discussion covered troubleshooting network discovery when machines were not communicating with the AD agent. Checks included ping connectivity, firewall policies, RPC, SMB, WMI, ports, services, and log files. The team also checked whether discovered machines were successfully synchronizing their information to the portal.
Separate Instance
The Tradeking setup uses a separate instance dedicated to the Tradeking environment, rather than sharing the same instance with other clients.
Company Management
The system supports multiple companies under the Rashmi Group environment. Users, assets, departments, and locations can be associated with the appropriate company.
Location Management
Locations can be created and associated with companies. The discussion included examples of different company locations and assigning users according to those locations.
Department Management
Departments can be configured for users and organizational activities. The discussion specifically covered department configuration and company-wise department handling.
User Import
Users can be imported using an Excel format. The discussion covered importing user information along with details such as location and department.
Internal Location Management
The system supports internal places within locations. Internal place information can be used for more detailed asset and organizational mapping. The discussion also identified branch code as a mandatory requirement for internal places.
Role and Permission Management
Roles and permissions can be configured to control what users can access and what actions they can perform. The discussion covered IT admin privileges and controlling access for users and devices.
Asset Management
Devices can be added and managed according to company and location. The discussion included device addition, editing, transfer, and device check-in/check-out activities.
Device Check-In and Check-Out
The ITM system provides device check-in and check-out functionality for managing device allocation and movement between users.
Ticket Management
Ticket-related configuration was also discussed, including company, employee, department, location, and ticket-related information.
Procurement Management
The procurement module supports configuration of shipping/delivery addresses based on the selected company and location. GST details can also be configured according to company or branch/location requirements. The module provides an Import Items option for adding multiple PO items through an Excel template instead of entering every item manually. The discussed import template contains fields such as Item Name, Description, Quantity, Unit, Budget Category, and Location. The procurement process also includes delivery instructions, location selection, item details, terms and conditions, and company-wise GST information.
Service Desk
The Service Desk supports creating tickets through email. However, the meeting identified an intermittent issue where emails received from certain automated/router email IDs do not consistently generate service tickets and require technical investigation.
Patch Management
The Patch Management module provides device-specific patch information and logs. Administrators can check incomplete or failed patch entries and review error information for individual devices. Patch troubleshooting includes checking exit codes, such as Error 1070, and investigating runtime dependencies such as .NET Framework and C++ Runtime when required. Patches can be reviewed based on severity categories such as Critical, Medium, and Low.