Jeffro

Untitled

Apr 3rd, 2011
620
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 42.40 KB | None | 0 0
  1. Keywords Date and Time Source Event ID Task Category
  2. Audit Success 3-4-2011 18:14:52 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  3.  
  4. Subject:
  5. Security ID: NULL SID
  6. Account Name: -
  7. Account Domain: -
  8. Logon ID: 0x0
  9.  
  10. Logon Type: 3
  11.  
  12. New Logon:
  13. Security ID: ANONYMOUS LOGON
  14. Account Name: ANONYMOUS LOGON
  15. Account Domain: NT AUTHORITY
  16. Logon ID: 0x4c0447c
  17. Logon GUID: {00000000-0000-0000-0000-000000000000}
  18.  
  19. Process Information:
  20. Process ID: 0x0
  21. Process Name: -
  22.  
  23. Network Information:
  24. Workstation Name: PISTOL
  25. Source Network Address: 192.168.1.113
  26. Source Port: 58427
  27.  
  28. Detailed Authentication Information:
  29. Logon Process: NtLmSsp
  30. Authentication Package: NTLM
  31. Transited Services: -
  32. Package Name (NTLM only): NTLM V1
  33. Key Length: 128
  34.  
  35. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  36.  
  37. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  38.  
  39. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  40.  
  41. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  42.  
  43. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  44.  
  45. The authentication information fields provide detailed information about this specific logon request.
  46. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  47. - Transited services indicate which intermediate services have participated in this logon request.
  48. - Package name indicates which sub-protocol was used among the NTLM protocols.
  49. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  50. Audit Success 3-4-2011 18:14:52 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  51.  
  52. Subject:
  53. Security ID: NULL SID
  54. Account Name: -
  55. Account Domain: -
  56. Logon ID: 0x0
  57.  
  58. Logon Type: 3
  59.  
  60. New Logon:
  61. Security ID: ANONYMOUS LOGON
  62. Account Name: ANONYMOUS LOGON
  63. Account Domain: NT AUTHORITY
  64. Logon ID: 0x4c0410a
  65. Logon GUID: {00000000-0000-0000-0000-000000000000}
  66.  
  67. Process Information:
  68. Process ID: 0x0
  69. Process Name: -
  70.  
  71. Network Information:
  72. Workstation Name: PISTOL
  73. Source Network Address: 192.168.1.113
  74. Source Port: 58426
  75.  
  76. Detailed Authentication Information:
  77. Logon Process: NtLmSsp
  78. Authentication Package: NTLM
  79. Transited Services: -
  80. Package Name (NTLM only): NTLM V1
  81. Key Length: 128
  82.  
  83. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  84.  
  85. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  86.  
  87. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  88.  
  89. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  90.  
  91. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  92.  
  93. The authentication information fields provide detailed information about this specific logon request.
  94. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  95. - Transited services indicate which intermediate services have participated in this logon request.
  96. - Package name indicates which sub-protocol was used among the NTLM protocols.
  97. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  98. Audit Success 3-4-2011 18:04:31 Microsoft-Windows-Security-Auditing 4634 Logoff "An account was logged off.
  99.  
  100. Subject:
  101. Security ID: Jeffro\Administrator
  102. Account Name: Administrator
  103. Account Domain: Jeffro
  104. Logon ID: 0x3a2aa7c
  105.  
  106. Logon Type: 2
  107.  
  108. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer."
  109. Audit Success 3-4-2011 18:04:27 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  110.  
  111. Subject:
  112. Security ID: Jeffro\Administrator
  113. Account Name: Administrator
  114. Account Domain: Jeffro
  115. Logon ID: 0x3a2aa7c
  116.  
  117. Privileges: SeSecurityPrivilege
  118. SeTakeOwnershipPrivilege
  119. SeLoadDriverPrivilege
  120. SeBackupPrivilege
  121. SeRestorePrivilege
  122. SeDebugPrivilege
  123. SeSystemEnvironmentPrivilege
  124. SeImpersonatePrivilege"
  125. Audit Success 3-4-2011 18:04:27 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  126.  
  127. Subject:
  128. Security ID: SYSTEM
  129. Account Name: Jeffro$
  130. Account Domain: WORKGROUP
  131. Logon ID: 0x3e7
  132.  
  133. Logon Type: 2
  134.  
  135. New Logon:
  136. Security ID: Jeffro\Administrator
  137. Account Name: Administrator
  138. Account Domain: Jeffro
  139. Logon ID: 0x3a2aa7c
  140. Logon GUID: {00000000-0000-0000-0000-000000000000}
  141.  
  142. Process Information:
  143. Process ID: 0x1c60
  144. Process Name: C:\Windows\System32\winlogon.exe
  145.  
  146. Network Information:
  147. Workstation Name: Jeffro
  148. Source Network Address: 127.0.0.1
  149. Source Port: 0
  150.  
  151. Detailed Authentication Information:
  152. Logon Process: User32
  153. Authentication Package: Negotiate
  154. Transited Services: -
  155. Package Name (NTLM only): -
  156. Key Length: 0
  157.  
  158. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  159.  
  160. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  161.  
  162. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  163.  
  164. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  165.  
  166. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  167.  
  168. The authentication information fields provide detailed information about this specific logon request.
  169. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  170. - Transited services indicate which intermediate services have participated in this logon request.
  171. - Package name indicates which sub-protocol was used among the NTLM protocols.
  172. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  173. Audit Success 3-4-2011 18:04:27 Microsoft-Windows-Security-Auditing 4648 Logon "A logon was attempted using explicit credentials.
  174.  
  175. Subject:
  176. Security ID: SYSTEM
  177. Account Name: Jeffro$
  178. Account Domain: WORKGROUP
  179. Logon ID: 0x3e7
  180. Logon GUID: {00000000-0000-0000-0000-000000000000}
  181.  
  182. Account Whose Credentials Were Used:
  183. Account Name: Administrator
  184. Account Domain: Jeffro
  185. Logon GUID: {00000000-0000-0000-0000-000000000000}
  186.  
  187. Target Server:
  188. Target Server Name: localhost
  189. Additional Information: localhost
  190.  
  191. Process Information:
  192. Process ID: 0x1c60
  193. Process Name: C:\Windows\System32\winlogon.exe
  194.  
  195. Network Information:
  196. Network Address: 127.0.0.1
  197. Port: 0
  198.  
  199. This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command."
  200. Audit Success 3-4-2011 18:03:08 Microsoft-Windows-Security-Auditing 4634 Logoff "An account was logged off.
  201.  
  202. Subject:
  203. Security ID: ANONYMOUS LOGON
  204. Account Name: ANONYMOUS LOGON
  205. Account Domain: NT AUTHORITY
  206. Logon ID: 0x37abd1d
  207.  
  208. Logon Type: 3
  209.  
  210. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer."
  211. Audit Success 3-4-2011 18:03:08 Microsoft-Windows-Security-Auditing 4634 Logoff "An account was logged off.
  212.  
  213. Subject:
  214. Security ID: ANONYMOUS LOGON
  215. Account Name: ANONYMOUS LOGON
  216. Account Domain: NT AUTHORITY
  217. Logon ID: 0x37aba16
  218.  
  219. Logon Type: 3
  220.  
  221. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer."
  222. Audit Success 3-4-2011 18:02:52 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  223.  
  224. Subject:
  225. Security ID: NULL SID
  226. Account Name: -
  227. Account Domain: -
  228. Logon ID: 0x0
  229.  
  230. Logon Type: 3
  231.  
  232. New Logon:
  233. Security ID: ANONYMOUS LOGON
  234. Account Name: ANONYMOUS LOGON
  235. Account Domain: NT AUTHORITY
  236. Logon ID: 0x37abd1d
  237. Logon GUID: {00000000-0000-0000-0000-000000000000}
  238.  
  239. Process Information:
  240. Process ID: 0x0
  241. Process Name: -
  242.  
  243. Network Information:
  244. Workstation Name: PISTOL
  245. Source Network Address: 192.168.1.113
  246. Source Port: 58371
  247.  
  248. Detailed Authentication Information:
  249. Logon Process: NtLmSsp
  250. Authentication Package: NTLM
  251. Transited Services: -
  252. Package Name (NTLM only): NTLM V1
  253. Key Length: 128
  254.  
  255. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  256.  
  257. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  258.  
  259. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  260.  
  261. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  262.  
  263. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  264.  
  265. The authentication information fields provide detailed information about this specific logon request.
  266. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  267. - Transited services indicate which intermediate services have participated in this logon request.
  268. - Package name indicates which sub-protocol was used among the NTLM protocols.
  269. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  270. Audit Success 3-4-2011 18:02:52 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  271.  
  272. Subject:
  273. Security ID: NULL SID
  274. Account Name: -
  275. Account Domain: -
  276. Logon ID: 0x0
  277.  
  278. Logon Type: 3
  279.  
  280. New Logon:
  281. Security ID: ANONYMOUS LOGON
  282. Account Name: ANONYMOUS LOGON
  283. Account Domain: NT AUTHORITY
  284. Logon ID: 0x37aba16
  285. Logon GUID: {00000000-0000-0000-0000-000000000000}
  286.  
  287. Process Information:
  288. Process ID: 0x0
  289. Process Name: -
  290.  
  291. Network Information:
  292. Workstation Name: PISTOL
  293. Source Network Address: 192.168.1.113
  294. Source Port: 58370
  295.  
  296. Detailed Authentication Information:
  297. Logon Process: NtLmSsp
  298. Authentication Package: NTLM
  299. Transited Services: -
  300. Package Name (NTLM only): NTLM V1
  301. Key Length: 128
  302.  
  303. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  304.  
  305. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  306.  
  307. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  308.  
  309. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  310.  
  311. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  312.  
  313. The authentication information fields provide detailed information about this specific logon request.
  314. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  315. - Transited services indicate which intermediate services have participated in this logon request.
  316. - Package name indicates which sub-protocol was used among the NTLM protocols.
  317. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  318. Audit Success 3-4-2011 18:02:20 Microsoft-Windows-Security-Auditing 4634 Logoff "An account was logged off.
  319.  
  320. Subject:
  321. Security ID: Jeffro\support
  322. Account Name: support
  323. Account Domain: Jeffro
  324. Logon ID: 0x335724b
  325.  
  326. Logon Type: 3
  327.  
  328. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer."
  329. Audit Success 3-4-2011 18:01:08 Microsoft-Windows-Security-Auditing 4634 Logoff "An account was logged off.
  330.  
  331. Subject:
  332. Security ID: Jeffro\support
  333. Account Name: support
  334. Account Domain: Jeffro
  335. Logon ID: 0x337aa59
  336.  
  337. Logon Type: 10
  338.  
  339. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer."
  340. Audit Failure 3-4-2011 18:00:37 Microsoft-Windows-Security-Auditing 6281 System Integrity "Code Integrity determined that the page hashes of an image file are not valid. The file could be improperly signed without page hashes or corrupt due to unauthorized modification. The invalid hashes could indicate a potential disk device error.
  341.  
  342. File Name: \Device\HarddiskVolume3\Windows\System32\l3codeca.acm "
  343. Audit Success 3-4-2011 18:00:22 Microsoft-Windows-Security-Auditing 4634 Logoff "An account was logged off.
  344.  
  345. Subject:
  346. Security ID: Jeffro\support
  347. Account Name: support
  348. Account Domain: Jeffro
  349. Logon ID: 0x337aa7b
  350.  
  351. Logon Type: 10
  352.  
  353. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer."
  354. Audit Success 3-4-2011 18:00:21 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  355.  
  356. Subject:
  357. Security ID: Jeffro\support
  358. Account Name: support
  359. Account Domain: Jeffro
  360. Logon ID: 0x337aa59
  361.  
  362. Privileges: SeSecurityPrivilege
  363. SeTakeOwnershipPrivilege
  364. SeLoadDriverPrivilege
  365. SeBackupPrivilege
  366. SeRestorePrivilege
  367. SeDebugPrivilege
  368. SeSystemEnvironmentPrivilege
  369. SeImpersonatePrivilege"
  370. Audit Success 3-4-2011 18:00:21 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  371.  
  372. Subject:
  373. Security ID: SYSTEM
  374. Account Name: Jeffro$
  375. Account Domain: WORKGROUP
  376. Logon ID: 0x3e7
  377.  
  378. Logon Type: 10
  379.  
  380. New Logon:
  381. Security ID: Jeffro\support
  382. Account Name: support
  383. Account Domain: Jeffro
  384. Logon ID: 0x337aa7b
  385. Logon GUID: {00000000-0000-0000-0000-000000000000}
  386.  
  387. Process Information:
  388. Process ID: 0x1c08
  389. Process Name: C:\Windows\System32\winlogon.exe
  390.  
  391. Network Information:
  392. Workstation Name: Jeffro
  393. Source Network Address: 79.186.194.220
  394. Source Port: 27051
  395.  
  396. Detailed Authentication Information:
  397. Logon Process: User32
  398. Authentication Package: Negotiate
  399. Transited Services: -
  400. Package Name (NTLM only): -
  401. Key Length: 0
  402.  
  403. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  404.  
  405. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  406.  
  407. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  408.  
  409. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  410.  
  411. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  412.  
  413. The authentication information fields provide detailed information about this specific logon request.
  414. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  415. - Transited services indicate which intermediate services have participated in this logon request.
  416. - Package name indicates which sub-protocol was used among the NTLM protocols.
  417. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  418. Audit Success 3-4-2011 18:00:21 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  419.  
  420. Subject:
  421. Security ID: SYSTEM
  422. Account Name: Jeffro$
  423. Account Domain: WORKGROUP
  424. Logon ID: 0x3e7
  425.  
  426. Logon Type: 10
  427.  
  428. New Logon:
  429. Security ID: Jeffro\support
  430. Account Name: support
  431. Account Domain: Jeffro
  432. Logon ID: 0x337aa59
  433. Logon GUID: {00000000-0000-0000-0000-000000000000}
  434.  
  435. Process Information:
  436. Process ID: 0x1c08
  437. Process Name: C:\Windows\System32\winlogon.exe
  438.  
  439. Network Information:
  440. Workstation Name: Jeffro
  441. Source Network Address: 79.186.194.220
  442. Source Port: 27051
  443.  
  444. Detailed Authentication Information:
  445. Logon Process: User32
  446. Authentication Package: Negotiate
  447. Transited Services: -
  448. Package Name (NTLM only): -
  449. Key Length: 0
  450.  
  451. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  452.  
  453. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  454.  
  455. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  456.  
  457. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  458.  
  459. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  460.  
  461. The authentication information fields provide detailed information about this specific logon request.
  462. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  463. - Transited services indicate which intermediate services have participated in this logon request.
  464. - Package name indicates which sub-protocol was used among the NTLM protocols.
  465. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  466. Audit Success 3-4-2011 18:00:21 Microsoft-Windows-Security-Auditing 4648 Logon "A logon was attempted using explicit credentials.
  467.  
  468. Subject:
  469. Security ID: SYSTEM
  470. Account Name: Jeffro$
  471. Account Domain: WORKGROUP
  472. Logon ID: 0x3e7
  473. Logon GUID: {00000000-0000-0000-0000-000000000000}
  474.  
  475. Account Whose Credentials Were Used:
  476. Account Name: support
  477. Account Domain: Jeffro
  478. Logon GUID: {00000000-0000-0000-0000-000000000000}
  479.  
  480. Target Server:
  481. Target Server Name: localhost
  482. Additional Information: localhost
  483.  
  484. Process Information:
  485. Process ID: 0x1c08
  486. Process Name: C:\Windows\System32\winlogon.exe
  487.  
  488. Network Information:
  489. Network Address: 79.186.194.220
  490. Port: 27051
  491.  
  492. This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command."
  493. Audit Success 3-4-2011 18:00:16 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  494.  
  495. Subject:
  496. Security ID: NULL SID
  497. Account Name: -
  498. Account Domain: -
  499. Logon ID: 0x0
  500.  
  501. Logon Type: 3
  502.  
  503. New Logon:
  504. Security ID: Jeffro\support
  505. Account Name: support
  506. Account Domain: Jeffro
  507. Logon ID: 0x335724b
  508. Logon GUID: {00000000-0000-0000-0000-000000000000}
  509.  
  510. Process Information:
  511. Process ID: 0x0
  512. Process Name: -
  513.  
  514. Network Information:
  515. Workstation Name: X2
  516. Source Network Address: -
  517. Source Port: -
  518.  
  519. Detailed Authentication Information:
  520. Logon Process: NtLmSsp
  521. Authentication Package: NTLM
  522. Transited Services: -
  523. Package Name (NTLM only): NTLM V2
  524. Key Length: 128
  525.  
  526. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  527.  
  528. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  529.  
  530. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  531.  
  532. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  533.  
  534. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  535.  
  536. The authentication information fields provide detailed information about this specific logon request.
  537. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  538. - Transited services indicate which intermediate services have participated in this logon request.
  539. - Package name indicates which sub-protocol was used among the NTLM protocols.
  540. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  541. Audit Success 3-4-2011 18:00:16 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  542.  
  543. Subject:
  544. Security ID: Jeffro\support
  545. Account Name: support
  546. Account Domain: Jeffro
  547. Logon ID: 0x335724b
  548.  
  549. Privileges: SeSecurityPrivilege
  550. SeTakeOwnershipPrivilege
  551. SeLoadDriverPrivilege
  552. SeBackupPrivilege
  553. SeRestorePrivilege
  554. SeDebugPrivilege
  555. SeSystemEnvironmentPrivilege
  556. SeImpersonatePrivilege"
  557. Audit Success 3-4-2011 18:00:16 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  558.  
  559. Subject:
  560. Security ID: Jeffro\support
  561. Account Name: support
  562. Account Domain: Jeffro
  563. Logon ID: 0x335724b
  564.  
  565. Privileges: SeSecurityPrivilege
  566. SeBackupPrivilege
  567. SeRestorePrivilege
  568. SeTakeOwnershipPrivilege
  569. SeDebugPrivilege
  570. SeSystemEnvironmentPrivilege
  571. SeLoadDriverPrivilege
  572. SeImpersonatePrivilege"
  573. Audit Success 3-4-2011 18:00:15 Microsoft-Windows-Security-Auditing 4634 Logoff "An account was logged off.
  574.  
  575. Subject:
  576. Security ID: Jeffro\support
  577. Account Name: support
  578. Account Domain: Jeffro
  579. Logon ID: 0x33523f6
  580.  
  581. Logon Type: 3
  582.  
  583. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer."
  584. Audit Success 3-4-2011 18:00:15 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  585.  
  586. Subject:
  587. Security ID: NULL SID
  588. Account Name: -
  589. Account Domain: -
  590. Logon ID: 0x0
  591.  
  592. Logon Type: 3
  593.  
  594. New Logon:
  595. Security ID: Jeffro\support
  596. Account Name: support
  597. Account Domain: Jeffro
  598. Logon ID: 0x33523f6
  599. Logon GUID: {00000000-0000-0000-0000-000000000000}
  600.  
  601. Process Information:
  602. Process ID: 0x0
  603. Process Name: -
  604.  
  605. Network Information:
  606. Workstation Name: X2
  607. Source Network Address: -
  608. Source Port: -
  609.  
  610. Detailed Authentication Information:
  611. Logon Process: NtLmSsp
  612. Authentication Package: NTLM
  613. Transited Services: -
  614. Package Name (NTLM only): NTLM V2
  615. Key Length: 128
  616.  
  617. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  618.  
  619. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  620.  
  621. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  622.  
  623. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  624.  
  625. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  626.  
  627. The authentication information fields provide detailed information about this specific logon request.
  628. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  629. - Transited services indicate which intermediate services have participated in this logon request.
  630. - Package name indicates which sub-protocol was used among the NTLM protocols.
  631. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  632. Audit Success 3-4-2011 18:00:15 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  633.  
  634. Subject:
  635. Security ID: Jeffro\support
  636. Account Name: support
  637. Account Domain: Jeffro
  638. Logon ID: 0x33523f6
  639.  
  640. Privileges: SeSecurityPrivilege
  641. SeTakeOwnershipPrivilege
  642. SeLoadDriverPrivilege
  643. SeBackupPrivilege
  644. SeRestorePrivilege
  645. SeDebugPrivilege
  646. SeSystemEnvironmentPrivilege
  647. SeImpersonatePrivilege"
  648. Audit Success 3-4-2011 18:00:15 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  649.  
  650. Subject:
  651. Security ID: Jeffro\support
  652. Account Name: support
  653. Account Domain: Jeffro
  654. Logon ID: 0x33523f6
  655.  
  656. Privileges: SeSecurityPrivilege
  657. SeBackupPrivilege
  658. SeRestorePrivilege
  659. SeTakeOwnershipPrivilege
  660. SeDebugPrivilege
  661. SeSystemEnvironmentPrivilege
  662. SeLoadDriverPrivilege
  663. SeImpersonatePrivilege"
  664. Audit Success 3-4-2011 18:00:08 Microsoft-Windows-Security-Auditing 4634 Logoff "An account was logged off.
  665.  
  666. Subject:
  667. Security ID: Jeffro\support
  668. Account Name: support
  669. Account Domain: Jeffro
  670. Logon ID: 0x302684b
  671.  
  672. Logon Type: 3
  673.  
  674. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer."
  675. Audit Success 3-4-2011 17:57:49 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  676.  
  677. Subject:
  678. Security ID: Jeffro\support
  679. Account Name: support
  680. Account Domain: Jeffro
  681. Logon ID: 0x302a311
  682.  
  683. Privileges: SeSecurityPrivilege
  684. SeTakeOwnershipPrivilege
  685. SeLoadDriverPrivilege
  686. SeBackupPrivilege
  687. SeRestorePrivilege
  688. SeDebugPrivilege
  689. SeSystemEnvironmentPrivilege
  690. SeImpersonatePrivilege"
  691. Audit Success 3-4-2011 17:57:49 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  692.  
  693. Subject:
  694. Security ID: SYSTEM
  695. Account Name: Jeffro$
  696. Account Domain: WORKGROUP
  697. Logon ID: 0x3e7
  698.  
  699. Logon Type: 10
  700.  
  701. New Logon:
  702. Security ID: Jeffro\support
  703. Account Name: support
  704. Account Domain: Jeffro
  705. Logon ID: 0x302a327
  706. Logon GUID: {00000000-0000-0000-0000-000000000000}
  707.  
  708. Process Information:
  709. Process ID: 0x4f4
  710. Process Name: C:\Windows\System32\winlogon.exe
  711.  
  712. Network Information:
  713. Workstation Name: Jeffro
  714. Source Network Address: 79.186.194.220
  715. Source Port: 26728
  716.  
  717. Detailed Authentication Information:
  718. Logon Process: User32
  719. Authentication Package: Negotiate
  720. Transited Services: -
  721. Package Name (NTLM only): -
  722. Key Length: 0
  723.  
  724. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  725.  
  726. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  727.  
  728. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  729.  
  730. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  731.  
  732. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  733.  
  734. The authentication information fields provide detailed information about this specific logon request.
  735. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  736. - Transited services indicate which intermediate services have participated in this logon request.
  737. - Package name indicates which sub-protocol was used among the NTLM protocols.
  738. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  739. Audit Success 3-4-2011 17:57:49 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  740.  
  741. Subject:
  742. Security ID: SYSTEM
  743. Account Name: Jeffro$
  744. Account Domain: WORKGROUP
  745. Logon ID: 0x3e7
  746.  
  747. Logon Type: 10
  748.  
  749. New Logon:
  750. Security ID: Jeffro\support
  751. Account Name: support
  752. Account Domain: Jeffro
  753. Logon ID: 0x302a311
  754. Logon GUID: {00000000-0000-0000-0000-000000000000}
  755.  
  756. Process Information:
  757. Process ID: 0x4f4
  758. Process Name: C:\Windows\System32\winlogon.exe
  759.  
  760. Network Information:
  761. Workstation Name: Jeffro
  762. Source Network Address: 79.186.194.220
  763. Source Port: 26728
  764.  
  765. Detailed Authentication Information:
  766. Logon Process: User32
  767. Authentication Package: Negotiate
  768. Transited Services: -
  769. Package Name (NTLM only): -
  770. Key Length: 0
  771.  
  772. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  773.  
  774. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  775.  
  776. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  777.  
  778. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  779.  
  780. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  781.  
  782. The authentication information fields provide detailed information about this specific logon request.
  783. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  784. - Transited services indicate which intermediate services have participated in this logon request.
  785. - Package name indicates which sub-protocol was used among the NTLM protocols.
  786. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  787. Audit Success 3-4-2011 17:57:49 Microsoft-Windows-Security-Auditing 4648 Logon "A logon was attempted using explicit credentials.
  788.  
  789. Subject:
  790. Security ID: SYSTEM
  791. Account Name: Jeffro$
  792. Account Domain: WORKGROUP
  793. Logon ID: 0x3e7
  794. Logon GUID: {00000000-0000-0000-0000-000000000000}
  795.  
  796. Account Whose Credentials Were Used:
  797. Account Name: support
  798. Account Domain: Jeffro
  799. Logon GUID: {00000000-0000-0000-0000-000000000000}
  800.  
  801. Target Server:
  802. Target Server Name: localhost
  803. Additional Information: localhost
  804.  
  805. Process Information:
  806. Process ID: 0x4f4
  807. Process Name: C:\Windows\System32\winlogon.exe
  808.  
  809. Network Information:
  810. Network Address: 79.186.194.220
  811. Port: 26728
  812.  
  813. This event is generated when a process attempts to log on an account by explicitly specifying that account’s credentials. This most commonly occurs in batch-type configurations such as scheduled tasks, or when using the RUNAS command."
  814. Audit Success 3-4-2011 17:57:44 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  815.  
  816. Subject:
  817. Security ID: NULL SID
  818. Account Name: -
  819. Account Domain: -
  820. Logon ID: 0x0
  821.  
  822. Logon Type: 3
  823.  
  824. New Logon:
  825. Security ID: Jeffro\support
  826. Account Name: support
  827. Account Domain: Jeffro
  828. Logon ID: 0x302684b
  829. Logon GUID: {00000000-0000-0000-0000-000000000000}
  830.  
  831. Process Information:
  832. Process ID: 0x0
  833. Process Name: -
  834.  
  835. Network Information:
  836. Workstation Name: X2
  837. Source Network Address: -
  838. Source Port: -
  839.  
  840. Detailed Authentication Information:
  841. Logon Process: NtLmSsp
  842. Authentication Package: NTLM
  843. Transited Services: -
  844. Package Name (NTLM only): NTLM V2
  845. Key Length: 128
  846.  
  847. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  848.  
  849. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  850.  
  851. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  852.  
  853. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  854.  
  855. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  856.  
  857. The authentication information fields provide detailed information about this specific logon request.
  858. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  859. - Transited services indicate which intermediate services have participated in this logon request.
  860. - Package name indicates which sub-protocol was used among the NTLM protocols.
  861. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  862. Audit Success 3-4-2011 17:57:44 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  863.  
  864. Subject:
  865. Security ID: Jeffro\support
  866. Account Name: support
  867. Account Domain: Jeffro
  868. Logon ID: 0x302684b
  869.  
  870. Privileges: SeSecurityPrivilege
  871. SeTakeOwnershipPrivilege
  872. SeLoadDriverPrivilege
  873. SeBackupPrivilege
  874. SeRestorePrivilege
  875. SeDebugPrivilege
  876. SeSystemEnvironmentPrivilege
  877. SeImpersonatePrivilege"
  878. Audit Success 3-4-2011 17:57:44 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  879.  
  880. Subject:
  881. Security ID: Jeffro\support
  882. Account Name: support
  883. Account Domain: Jeffro
  884. Logon ID: 0x302684b
  885.  
  886. Privileges: SeSecurityPrivilege
  887. SeBackupPrivilege
  888. SeRestorePrivilege
  889. SeTakeOwnershipPrivilege
  890. SeDebugPrivilege
  891. SeSystemEnvironmentPrivilege
  892. SeLoadDriverPrivilege
  893. SeImpersonatePrivilege"
  894. Audit Success 3-4-2011 17:57:42 Microsoft-Windows-Security-Auditing 4634 Logoff "An account was logged off.
  895.  
  896. Subject:
  897. Security ID: Jeffro\support
  898. Account Name: support
  899. Account Domain: Jeffro
  900. Logon ID: 0x3025c54
  901.  
  902. Logon Type: 3
  903.  
  904. This event is generated when a logon session is destroyed. It may be positively correlated with a logon event using the Logon ID value. Logon IDs are only unique between reboots on the same computer."
  905. Audit Success 3-4-2011 17:57:42 Microsoft-Windows-Security-Auditing 4624 Logon "An account was successfully logged on.
  906.  
  907. Subject:
  908. Security ID: NULL SID
  909. Account Name: -
  910. Account Domain: -
  911. Logon ID: 0x0
  912.  
  913. Logon Type: 3
  914.  
  915. New Logon:
  916. Security ID: Jeffro\support
  917. Account Name: support
  918. Account Domain: Jeffro
  919. Logon ID: 0x3025c54
  920. Logon GUID: {00000000-0000-0000-0000-000000000000}
  921.  
  922. Process Information:
  923. Process ID: 0x0
  924. Process Name: -
  925.  
  926. Network Information:
  927. Workstation Name: X2
  928. Source Network Address: -
  929. Source Port: -
  930.  
  931. Detailed Authentication Information:
  932. Logon Process: NtLmSsp
  933. Authentication Package: NTLM
  934. Transited Services: -
  935. Package Name (NTLM only): NTLM V2
  936. Key Length: 128
  937.  
  938. This event is generated when a logon session is created. It is generated on the computer that was accessed.
  939.  
  940. The subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
  941.  
  942. The logon type field indicates the kind of logon that occurred. The most common types are 2 (interactive) and 3 (network).
  943.  
  944. The New Logon fields indicate the account for whom the new logon was created, i.e. the account that was logged on.
  945.  
  946. The network fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
  947.  
  948. The authentication information fields provide detailed information about this specific logon request.
  949. - Logon GUID is a unique identifier that can be used to correlate this event with a KDC event.
  950. - Transited services indicate which intermediate services have participated in this logon request.
  951. - Package name indicates which sub-protocol was used among the NTLM protocols.
  952. - Key length indicates the length of the generated session key. This will be 0 if no session key was requested."
  953. Audit Success 3-4-2011 17:57:42 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  954.  
  955. Subject:
  956. Security ID: Jeffro\support
  957. Account Name: support
  958. Account Domain: Jeffro
  959. Logon ID: 0x3025c54
  960.  
  961. Privileges: SeSecurityPrivilege
  962. SeTakeOwnershipPrivilege
  963. SeLoadDriverPrivilege
  964. SeBackupPrivilege
  965. SeRestorePrivilege
  966. SeDebugPrivilege
  967. SeSystemEnvironmentPrivilege
  968. SeImpersonatePrivilege"
  969. Audit Success 3-4-2011 17:57:42 Microsoft-Windows-Security-Auditing 4672 Special Logon "Special privileges assigned to new logon.
  970.  
  971. Subject:
  972. Security ID: Jeffro\support
  973. Account Name: support
  974. Account Domain: Jeffro
  975. Logon ID: 0x3025c54
  976.  
  977. Privileges: SeSecurityPrivilege
  978. SeBackupPrivilege
  979. SeRestorePrivilege
  980. SeTakeOwnershipPrivilege
  981. SeDebugPrivilege
  982. SeSystemEnvironmentPrivilege
  983. SeLoadDriverPrivilege
  984. SeImpersonatePrivilege"
  985. Audit Success 3-4-2011 17:57:33 Microsoft-Windows-Security-Auditing 4732 Security Group Management "A member was added to a security-enabled local group.
  986.  
  987. Subject:
  988. Security ID: SYSTEM
  989. Account Name: Jeffro$
  990. Account Domain: WORKGROUP
  991. Logon ID: 0x3e7
  992.  
  993. Member:
  994. Security ID: Jeffro\support
  995. Account Name: -
  996.  
  997. Group:
  998. Security ID: BUILTIN\Administrators
  999. Group Name: Administrators
  1000. Group Domain: Builtin
  1001.  
  1002. Additional Information:
  1003. Privileges: -"
  1004. Audit Success 3-4-2011 17:57:29 Microsoft-Windows-Security-Auditing 4732 Security Group Management "A member was added to a security-enabled local group.
  1005.  
  1006. Subject:
  1007. Security ID: SYSTEM
  1008. Account Name: Jeffro$
  1009. Account Domain: WORKGROUP
  1010. Logon ID: 0x3e7
  1011.  
  1012. Member:
  1013. Security ID: Jeffro\support
  1014. Account Name: -
  1015.  
  1016. Group:
  1017. Security ID: BUILTIN\Users
  1018. Group Name: Users
  1019. Group Domain: Builtin
  1020.  
  1021. Additional Information:
  1022. Privileges: -"
  1023. Audit Success 3-4-2011 17:57:29 Microsoft-Windows-Security-Auditing 4724 User Account Management "An attempt was made to reset an account's password.
  1024.  
  1025. Subject:
  1026. Security ID: SYSTEM
  1027. Account Name: Jeffro$
  1028. Account Domain: WORKGROUP
  1029. Logon ID: 0x3e7
  1030.  
  1031. Target Account:
  1032. Security ID: Jeffro\support
  1033. Account Name: support
  1034. Account Domain: Jeffro"
  1035. Audit Success 3-4-2011 17:57:29 Microsoft-Windows-Security-Auditing 4738 User Account Management "A user account was changed.
  1036.  
  1037. Subject:
  1038. Security ID: SYSTEM
  1039. Account Name: Jeffro$
  1040. Account Domain: WORKGROUP
  1041. Logon ID: 0x3e7
  1042.  
  1043. Target Account:
  1044. Security ID: Jeffro\support
  1045. Account Name: support
  1046. Account Domain: Jeffro
  1047.  
  1048. Changed Attributes:
  1049. SAM Account Name: support
  1050. Display Name: <value not set>
  1051. User Principal Name: -
  1052. Home Directory: <value not set>
  1053. Home Drive: <value not set>
  1054. Script Path: <value not set>
  1055. Profile Path: <value not set>
  1056. User Workstations: <value not set>
  1057. Password Last Set: 4/3/2011 5:57:29 PM
  1058. Account Expires: <never>
  1059. Primary Group ID: 513
  1060. AllowedToDelegateTo: -
  1061. Old UAC Value: 0x15
  1062. New UAC Value: 0x10
  1063. User Account Control:
  1064. Account Enabled
  1065. 'Password Not Required' - Disabled
  1066. User Parameters: -
  1067. SID History: -
  1068. Logon Hours: All
  1069.  
  1070. Additional Information:
  1071. Privileges: -"
  1072. Audit Success 3-4-2011 17:57:29 Microsoft-Windows-Security-Auditing 4722 User Account Management "A user account was enabled.
  1073.  
  1074. Subject:
  1075. Security ID: SYSTEM
  1076. Account Name: Jeffro$
  1077. Account Domain: WORKGROUP
  1078. Logon ID: 0x3e7
  1079.  
  1080. Target Account:
  1081. Security ID: Jeffro\support
  1082. Account Name: support
  1083. Account Domain: Jeffro"
  1084. Audit Success 3-4-2011 17:57:29 Microsoft-Windows-Security-Auditing 4720 User Account Management "A user account was created.
  1085.  
  1086. Subject:
  1087. Security ID: SYSTEM
  1088. Account Name: Jeffro$
  1089. Account Domain: WORKGROUP
  1090. Logon ID: 0x3e7
  1091.  
  1092. New Account:
  1093. Security ID: Jeffro\support
  1094. Account Name: support
  1095. Account Domain: Jeffro
  1096.  
  1097. Attributes:
  1098. SAM Account Name: support
  1099. Display Name: <value not set>
  1100. User Principal Name: -
  1101. Home Directory: <value not set>
  1102. Home Drive: <value not set>
  1103. Script Path: <value not set>
  1104. Profile Path: <value not set>
  1105. User Workstations: <value not set>
  1106. Password Last Set: <never>
  1107. Account Expires: <never>
  1108. Primary Group ID: 513
  1109. Allowed To Delegate To: -
  1110. Old UAC Value: 0x0
  1111. New UAC Value: 0x15
  1112. User Account Control:
  1113. Account Disabled
  1114. 'Password Not Required' - Enabled
  1115. 'Normal Account' - Enabled
  1116. User Parameters: <value not set>
  1117. SID History: -
  1118. Logon Hours: All
  1119.  
  1120. Additional Information:
  1121. Privileges -"
  1122. Audit Success 3-4-2011 17:57:29 Microsoft-Windows-Security-Auditing 4728 Security Group Management "A member was added to a security-enabled global group.
  1123.  
  1124. Subject:
  1125. Security ID: SYSTEM
  1126. Account Name: Jeffro$
  1127. Account Domain: WORKGROUP
  1128. Logon ID: 0x3e7
  1129.  
  1130. Member:
  1131. Security ID: Jeffro\support
  1132. Account Name: -
  1133.  
  1134. Group:
  1135. Security ID: Jeffro\None
  1136. Group Name: None
  1137. Group Domain: Jeffro
  1138.  
  1139. Additional Information:
  1140. Privileges: -"
  1141. Audit Success 3-4-2011 17:57:18 Microsoft-Windows-Security-Auditing 5061 System Integrity "Cryptographic operation.
  1142.  
  1143. Subject:
  1144. Security ID: NETWORK SERVICE
  1145. Account Name: Jeffro$
  1146. Account Domain: WORKGROUP
  1147. Logon ID: 0x3e4
  1148.  
  1149. Cryptographic Parameters:
  1150. Provider Name: Microsoft Software Key Storage Provider
  1151. Algorithm Name: RSA
  1152. Key Name: TSSecKeySet1
  1153. Key Type: Machine key.
  1154.  
  1155. Cryptographic Operation:
  1156. Operation: Open Key.
  1157. Return Code: 0x0"
  1158. Audit Success 3-4-2011 17:57:18 Microsoft-Windows-Security-Auditing 5058 Other System Events "Key file operation.
  1159.  
  1160. Subject:
  1161. Security ID: NETWORK SERVICE
  1162. Account Name: Jeffro$
  1163. Account Domain: WORKGROUP
  1164. Logon ID: 0x3e4
  1165.  
  1166. Cryptographic Parameters:
  1167. Provider Name: Microsoft Software Key Storage Provider
  1168. Algorithm Name: Not Available.
  1169. Key Name: TSSecKeySet1
  1170. Key Type: Machine key.
  1171.  
  1172. Key File Operation Information:
  1173. File Path: C:\ProgramData\Microsoft\Crypto\RSA\MachineKeys\f686aace6942fb7f7ceb231212eef4a4_32a24a8b-216c-4245-9824-fbf86d2c4ea6
  1174. Operation: Read persisted key from file.
  1175. Return Code: 0x0"
Advertisement
Add Comment
Please, Sign In to add comment