1、When you fetch an object from the server, the USN is also fetched and brought to the client side.
當(dāng)您從服務(wù)器獲取一個對象時，USN也被獲取并傳遞到客戶端。

2、Each domain controller maintains a USN that is specific to that domain controller.
每個域控制器都維護(hù)特定于該域控制器的USN。

3、In such cases, the USN value has a special value that signals the CE server to skip the USN check.
在這些情況中，US n值有一個表示CE服務(wù)器跳過usn檢查的特殊值。

4、USN rollback can occur because these tombstoned objects don't hang around indefinitely.
因為這些邏輯刪除對象不會無限期保留，所以可能會發(fā)生usn回滾。

5、But this is not the only way that a DC's USN can be incremented.
但這并不是增加dc的usn的唯一方式。

6、If you later fetch or refresh any properties from the server, the current USN is obtained as well.
如果您稍后從服務(wù)器獲取或刷新任何屬性，也會獲取當(dāng)前usn。

7、Actually, the CE progression pattern for USN is only vaguely specified.
事實上，ce對usn的遞增模式的指定是模糊的。

8、The incrementing of the USN is not, strictly speaking, under your control.
嚴(yán)格來說，USN的遞增是不受我們控制的。

9、Results 55 cases 39.85 % of USN were found in 138 patients with stroke.
結(jié)果　 138例腦中風(fēng)患者發(fā)生單側(cè)空間忽略者 5 5例 ,占 39.85 %。