Provisioning Services has the ability to run a Target Device from a vDisk in Standard Image Mode, meaning that the vDisk is in a read-only state.
Changes to the vDisk are stored in one of three locations:
- RAM cache
- Target Device hard drive (Local hard drive which rules out Thin Clients)
- Server side cache, using disk space on the Provisioning Services Server
Changes to the disk are not persistent and are lost if the Target Device is rebooted.
Q: So if a Target Device is accessing a vDisk in Standard image mode, where is the “debug” or “trace” log written to? Indeed, can one take a trace from a PVS Target Device? Continue reading “How to enable advanced logging in Provisioning Services 6.1 including Target Devices”