Introduction
Depending on the device you have deployed, it may include a Service Tag, Hardware ID, or MAC address on the device itself, or its packaging.
This information is used to log into the Management Console, and when adding assets in the MDR Portal.
This article shows how to find the credential for the different sensor types:
Compact series
The status page password for Compact series sensors use a concatenation of "fieldeffect_" and the 15-character service tag, found on the bottom of the sensor.
Example login credentials for a Compact series sensor would be as follows: Service tag: 12345678-9012-345 Username: appliance-config Password: fieldeffect_123456789102345 (fieldeffect_15 character service tag, hyphens removed)
The image below shows an example of the service tag on the bottom of a Compact series sensor.

Shuttle and Oscar series
The status page password for Shuttle and Oscar series sensors use a concatenation of:
- "fieldeffect_"
- The letter "M" to denote the sensor's MAC address.
- The second half (last 6 characters) of the sensor's MAC address.
- Do not include the ":" between each character set
Example login credentials for a Shuttle or Oskar series would be as follows: MAC address: 80:EE:73:F1:B2:C3 Username: appliance-config password: fieldeffect_MF1B2C3 (fieldeffect_M+last 6 characters of the MAC address)
The image below shows an example of the MAC address on Shuttle and Oskar sensors.

Business and Enterprise series
The status page password for Business and Enterprise series sensors use a concatenation of "fieldeffect_" and the 7-character service tag.
Example login credentials for a Business or Enterprise series sensor would be as follows: Service Tag:F9HGKC5 Username: appliance-config Password: fieldeffect_F9HGKC5 (fieldeffect_7 digit service tag)
An example password for a Compact series sensor would be: fieldeffect_F9HGKC5
The image below shows an example of the service tag on a Business or Enterprise series sensor.

Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article