Owners Manual

NOTE: Write intensive activities and processes leveraged by XC appliances, are intended to take
place on the SSDs and HDDs and not the boot device.
The hypervisor boot device is not intended for application use.
WARNING: Adding additional write intensive software to the SATADOM boot disk results in heavy
wear on the device beyond design specifications resulting in premature hardware failure.
You should not run applications on the hypervisor operating system.
Examples of write intensive applications
Following are the examples of write intensive applications:
System Center Agents.
System Center Configuration Manager (CCMExec.exe).
System Center Operations Manager (MonitoringHost.exe).
Writeintensive Agents.
Databases.
Disk management utilities (third-party disk defragmentation or partitioning tools).
Additional roles outside of the appliance’s intended use (web server, domain controller, RDS, and so
on.).
Clientbased Antivirus.
Run Virtual Machines directly on the SATADOM. Ensure that the Virtual Machines run on Solid State
Drives (SSDs) and Hard Disk Drives (HDDs).
Removing the SATADOM
Prerequisites
1. Ensure that you read the Safety instructions.
2. Follow the procedure listed in Before working inside your system.
CAUTION: Many repairs may only be done by a certified service technician. You should only
perform troubleshooting and simple repairs as authorized in your product documentation, or as
directed by the online or telephone service and support team. Damage due to servicing that is
not authorized by Dell is not covered by your warranty. Read and follow the safety instructions
that came with the product.
Steps
1. Unplug the power cable from the SATADOM J_TBU connector.
2. Press the lock release on the SATADOM and pull it up and away from the system.
NOTE: After removing the SATADOM, place it in an anti-static container for reuse, return, or
temporary storage.
NOTE: Dell recommends that you do not modify the SATADOM Read/Write default setting.
54