1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
1093
1094
1095
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116
1117
1118
1119
1120
1121
1122
1123
1124
1125
1126
1127
1128
1129
1130
1131
1132
1133
1134
1135
1136
1137
1138
1139
1140
1141
1142
1143
1144
1145
1146
1147
1148
1149
1150
1151
1152
1153
1154
1155
1156
1157
1158
1159
1160
1161
1162
1163
1164
1165
1166
1167
1168
1169
1170
1171
1172
1173
1174
1175
1176
1177
1178
1179
1180
1181
1182
1183
1184
1185
1186
1187
1188
1189
1190
1191
1192
1193
1194
1195
1196
1197
1198
1199
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228
1229
1230
1231
1232
1233
1234
1235
1236
1237
1238
1239
1240
1241
1242
1243
1244
1245
1246
1247
1248
1249
1250
1251
1252
1253
1254
1255
1256
1257
1258
1259
1260
1261
1262
1263
1264
1265
1266
1267
1268
1269
1270
1271
1272
1273
1274
1275
1276
1277
1278
1279
1280
1281
1282
1283
1284
1285
1286
1287
1288
1289
1290
1291
1292
1293
1294
1295
1296
1297
1298
1299
1300
1301
1302
1303
1304
1305
1306
1307
1308
1309
1310
1311
1312
1313
1314
1315
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340
1341
1342
1343
1344
1345
1346
1347
1348
1349
1350
1351
1352
1353
1354
1355
1356
1357
1358
1359
1360
1361
1362
1363
1364
1365
1366
1367
1368
1369
1370
1371
1372
1373
1374
1375
1376
1377
1378
1379
1380
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396
1397
1398
1399
1400
1401
1402
1403
1404
1405
1406
1407
1408
1409
1410
1411
1412
1413
1414
1415
1416
1417
1418
1419
1420
1421
1422
1423
1424
1425
1426
1427
1428
1429
1430
1431
1432
1433
1434
1435
1436
1437
1438
1439
1440
1441
1442
1443
1444
1445
1446
1447
1448
1449
1450
1451
1452
1453
1454
1455
1456
1457
1458
1459
1460
1461
1462
1463
1464
1465
1466
1467
1468
1469
1470
1471
1472
1473
1474
1475
1476
1477
1478
1479
1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
1495
1496
1497
1498
1499
1500
1501
1502
1503
1504
1505
1506
1507
1508
1509
1510
1511
1512
1513
1514
1515
1516
1517
1518
1519
1520
1521
1522
1523
1524
1525
1526
1527
1528
1529
1530
1531
1532
1533
1534
1535
1536
1537
1538
1539
1540
1541
1542
1543
1544
1545
1546
1547
1548
1549
1550
1551
1552
1553
1554
1555
1556
1557
1558
1559
1560
1561
1562
1563
1564
1565
1566
1567
1568
1569
1570
1571
1572
1573
1574
1575
1576
1577
1578
1579
1580
1581
1582
1583
1584
1585
1586
1587
1588
1589
1590
1591
1592
1593
1594
1595
1596
1597
1598
1599
1600
1601
1602
1603
1604
1605
1606
1607
1608
1609
1610
1611
1612
1613
1614
1615
1616
1617
1618
1619
1620
1621
1622
1623
1624
1625
1626
1627
1628
1629
1630
1631
1632
1633
1634
1635
1636
1637
1638
1639
1640
1641
1642
1643
1644
1645
1646
1647
1648
1649
1650
1651
1652
1653
1654
1655
1656
1657
1658
1659
1660
1661
1662
1663
1664
1665
1666
1667
1668
1669
1670
1671
1672
1673
1674
1675
1676
1677
1678
1679
1680
1681
1682
1683
1684
1685
1686
1687
1688
1689
1690
1691
1692
1693
1694
1695
1696
1697
1698
1699
1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1734
1735
1736
1737
1738
1739
1740
1741
1742
1743
1744
1745
1746
1747
1748
1749
1750
1751
1752
1753
1754
1755
1756
1757
1758
1759
1760
1761
1762
1763
1764
1765
1766
1767
1768
1769
1770
1771
1772
1773
1774
1775
1776
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1803
1804
1805
1806
1807
1808
1809
1810
1811
1812
1813
1814
1815
1816
1817
1818
1819
1820
1821
1822
1823
1824
1825
1826
1827
1828
1829
1830
1831
1832
1833
1834
1835
1836
1837
1838
1839
1840
1841
1842
1843
1844
1845
1846
1847
1848
1849
1850
1851
1852
1853
1854
1855
1856
1857
1858
1859
1860
1861
1862
1863
1864
1865
1866
1867
1868
1869
1870
1871
1872
1873
1874
1875
1876
1877
1878
1879
1880
1881
1882
1883
1884
1885
1886
1887
1888
1889
1890
1891
1892
1893
1894
1895
1896
1897
1898
1899
1900
1901
1902
1903
1904
1905
1906
1907
1908
1909
1910
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1926
1927
1928
1929
1930
1931
1932
1933
1934
1935
1936
1937
1938
1939
1940
1941
1942
1943
1944
1945
1946
1947
1948
1949
1950
1951
1952
1953
1954
1955
1956
1957
1958
1959
1960
1961
1962
1963
1964
1965
1966
1967
1968
1969
1970
1971
1972
1973
1974
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
|
# SOME DESCRIPTIVE TITLE.
# Copyright (C) Ansible project contributors
# This file is distributed under the same license as the Ansible package.
# FIRST AUTHOR <EMAIL@ADDRESS>, 2022.
#
msgid ""
msgstr ""
"Project-Id-Version: Ansible devel\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-03-01 20:16+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Generated-By: Babel 2.9.0\n"
#: ../../rst/os_guide/index.rst:5
msgid "Using Ansible on Windows and BSD"
msgstr "Ansible ã® Windows ããã³ BSD ãžã®ã€ã³ã¹ããŒã«"
#: ../../rst/os_guide/index.rst:9
msgid "**Making Open Source More Inclusive**"
msgstr "**å€æ§æ§ãåãå
¥ãããªãŒãã³ãœãŒã¹ã®åŒ·å**"
#: ../../rst/os_guide/index.rst:11
msgid "Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. We ask that you open an issue or pull request if you come upon a term that we have missed. For more details, see `our CTO Chris Wright's message <https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language>`_."
msgstr "Red Hat ã§ã¯ãã³ãŒããããã¥ã¡ã³ããWeb ããããã£ãŒã«ãããé
æ
®ã«æ¬ ããçšèªã®çœ®ãæãã«åãçµãã§ããŸãããŸãã¯ããã¹ã¿ãŒ (master)ãã¹ã¬ãŒã (slave)ããã©ãã¯ãªã¹ã (blacklist)ããã¯ã€ããªã¹ã (whitelist) ã® 4 ã€ã®çšèªã®çœ®ãæãããå§ããŸããåé¡ã®ããçšèªãèŠã€ããå Žåã¯ãåé¡ãäœæãããããã«èŠæ±ãäœæããŠãã ããã詳现ã¯ã`åŒç€Ÿ ã® CTOãChris Wright ã®ã¡ãã»ãŒãž <https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language>`_ ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/index.rst:13
msgid "Welcome to the Ansible guide for Microsoft Windows and BSD. Because Windows is not a POSIX-compliant operating system, Ansible interacts with Windows hosts differently to Linux/Unix hosts. Likewise managing hosts that run BSD is different to managing other Unix-like host operating systems. Find out everything you need to know about using Ansible on Windows and with BSD hosts."
msgstr "Microsoft Windows ããã³ BSD ã® Ansible ã¬ã€ããžãããããWindows 㯠POSIX æºæ ã®ãªãã¬ãŒãã£ã³ã°ã·ã¹ãã ã§ã¯ãªããããAnsible 㯠Linux/Unix ãã¹ããšã¯ç°ãªãæ¹æ³ã§ Windows ãã¹ããšå¯Ÿè©±ããŸããåæ§ã«ãBSD ãå®è¡ãããã¹ãã®ç®¡çã¯ãä»ã® Unix ã©ã€ã¯ãªãã¹ããªãã¬ãŒãã£ã³ã°ã·ã¹ãã ã®ç®¡çãšã¯ç°ãªããŸããWindows ããã³ BSD ãã¹ã㧠Ansible ã䜿çšããéã«ç¥ã£ãŠããã¹ãããšããã¹ãŠç¢ºèªããŠãã ããã"
#: ../../rst/os_guide/intro_bsd.rst:4
msgid "Managing BSD hosts with Ansible"
msgstr "Ansible ã䜿çšãã BSD ãã¹ãã®ç®¡ç"
#: ../../rst/os_guide/intro_bsd.rst:6
msgid "Managing BSD machines is different from managing other Unix-like machines. If you have managed nodes running BSD, review these topics."
msgstr "BSD ãã·ã³ã®ç®¡çã¯ãä»ã® Unix ç³»ãã·ã³ã®ç®¡çãšã¯ç°ãªããŸããBSD ãå®è¡ããŠãã管çããŒãã䜿çšããŠããå Žåã¯ã以äžã®ãããã¯ã確èªããŠãã ããã"
#: ../../rst/os_guide/intro_bsd.rst:12
msgid "Connecting to BSD nodes"
msgstr "BSD ããŒããžã®æ¥ç¶"
#: ../../rst/os_guide/intro_bsd.rst:14
msgid "Ansible connects to managed nodes using OpenSSH by default. This works on BSD if you use SSH keys for authentication. However, if you use SSH passwords for authentication, Ansible relies on sshpass. Most versions of sshpass do not deal well with BSD login prompts, so when using SSH passwords against BSD machines, use ``paramiko`` to connect instead of OpenSSH. You can do this in ansible.cfg globally or you can set it as an inventory/group/host variable. For example:"
msgstr "Ansible ã¯ããã©ã«ã㧠OpenSSH ã䜿çšããŠç®¡çããŒãã«æ¥ç¶ããŸããããã¯ãèªèšŒã« SSH éµã䜿çšããŠããå Žå㯠BSD ã§åäœããŸãããã ããèªèšŒã« SSH ãã¹ã¯ãŒãã䜿çšããå ŽåãAnsible 㯠sshpass ã«äŸåããŸããsshpass ã®ã»ãšãã©ã®ããŒãžã§ã³ã¯ BSD ã®ãã°ã€ã³ããã³ããã«é©åã«å¯Ÿå¿ã§ããŸããããããã£ãŠãBSD ãã·ã³ã«å¯Ÿã㊠SSH ãã¹ã¯ãŒãã䜿çšããå Žåã¯ãOpenSSH ã®ä»£ããã« ``paramiko`` ã䜿çšããŠæ¥ç¶ããŠãã ããããã㯠ansible.cfg ã§ã°ããŒãã«ã«è¡ãããšãã§ããŸãããinventory/group/host å€æ°ãšããŠèšå®ããããšãã§ããŸãã以äžã«äŸã瀺ããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:25
msgid "Bootstrapping BSD"
msgstr "BSD ã®ããŒãã¹ãã©ãã"
#: ../../rst/os_guide/intro_bsd.rst:27
msgid "Ansible is agentless by default, however, it requires Python on managed nodes. Only the :ref:`raw <raw_module>` module will operate without Python. Although this module can be used to bootstrap Ansible and install Python on BSD variants (see below), it is very limited and the use of Python is required to make full use of Ansible's features."
msgstr "Ansible ã¯ããã©ã«ãã§ãšãŒãžã§ã³ãã¬ã¹ã§ããã管çããŒã㧠Python ãå¿
èŠã«ãªããŸãã:ref:`raw <raw_module>` ã¢ãžã¥ãŒã«ã®ã¿ã Python ãªãã§åäœããŸãããã®ã¢ãžã¥ãŒã«ã䜿çšã㊠Ansible ãããŒãã¹ãã©ããã㊠BSD ããªã¢ã³ãã« Python ãã€ã³ã¹ããŒã«ã§ããŸã (äžèšåç
§) ããPython ã¯éåžžã«å¶éãããŠãããAnsible ã®æ©èœãå®å
šã«æŽ»çšããã«ã¯ Python ã䜿çšããå¿
èŠããããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:29
msgid "The following example installs Python which includes the json library required for full functionality of Ansible. On your control machine you can execute the following for most versions of FreeBSD:"
msgstr "次ã®äŸã§ã¯ãAnsible ã®å®å
šãªæ©èœã«å¿
èŠãª json ã©ã€ãã©ãªãŒãå«ã Python ãã€ã³ã¹ããŒã«ããŠããŸããã³ã³ãããŒã«ãã·ã³ã§ã¯ãã»ãšãã©ã®ããŒãžã§ã³ã® FreeBSD ã§æ¬¡ã®ããã«å®è¡ã§ããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:36
msgid "Or for OpenBSD:"
msgstr "OpenBSD ã®å Žåã¯ã次ã®ã³ãã³ãã䜿çšããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:42
msgid "Once this is done you can now use other Ansible modules apart from the ``raw`` module."
msgstr "ãããå®äºãããšã``raw`` ã¢ãžã¥ãŒã«ä»¥å€ã®ä»ã® Ansible ã¢ãžã¥ãŒã«ã䜿çšã§ããããã«ãªããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:45
msgid "This example demonstrated using pkg on FreeBSD and pkg_add on OpenBSD, however you should be able to substitute the appropriate package tool for your BSD; the package name may also differ. Refer to the package list or documentation of the BSD variant you are using for the exact Python package name you intend to install."
msgstr "ãã®äŸã§ã¯ãFreeBSD ã§ã¯ pkg ããOpenBSD ã§ã¯ pkg_add ã䜿çšããŠããŸãããã䜿ãã® BSD ã«åãããŠé©åãªããã±ãŒãžããŒã«ãéžæããŠãã ããããŸããããã±ãŒãžåãç°ãªãå ŽåããããŸããã€ã³ã¹ããŒã«ãã Python ããã±ãŒãžåã«ã€ããŠã¯ã䜿çšããŠãã BSD ã®ããã±ãŒãžãªã¹ããããã¥ã¡ã³ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/intro_bsd.rst:50
msgid "Setting the Python interpreter"
msgstr "Python ã€ã³ã¿ãŒããªã¿ãŒã®èšå®"
#: ../../rst/os_guide/intro_bsd.rst:52
msgid "To support a variety of Unix-like operating systems and distributions, Ansible cannot always rely on the existing environment or ``env`` variables to locate the correct Python binary. By default, modules point at ``/usr/bin/python`` as this is the most common location. On BSD variants, this path may differ, so it is advised to inform Ansible of the binary's location. See :ref:`INTERPRETER_PYTHON`. For example, set ``ansible_python_interpreter`` inventory variable:"
msgstr "ããŸããŸãª Unix ç³»ãªãã¬ãŒãã£ã³ã°ã·ã¹ãã ããã£ã¹ããªãã¥ãŒã·ã§ã³ããµããŒãããããã«ãAnsible ã¯åžžã«æ¢åã®ç°å¢å€æ°ã ``env`` å€æ°ãé Œãã«æ£ãã Python ãã€ããªãŒãæ¢ãããšã¯ã§ããŸãããããã©ã«ãã§ã¯ãã¢ãžã¥ãŒã«ã¯æãäžè¬çãªå Žæã§ãã ``/usr/bin/python`` ãæããŸããBSD ç³»ã§ã¯ããã®ãã¹ãç°ãªãå Žåãããã®ã§ããã€ããªãŒã®å Žæã Ansible ã«ç¥ãããããšãæšå¥šãããŸãã:ref:`INTERPRETER_PYTHON` ãåç
§ããŠãã ãããããšãã°ã``ansible_python_interpreter`` ã€ã³ãã³ããªãŒå€æ°ãèšå®ããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:63
msgid "FreeBSD packages and ports"
msgstr "FreeBSD ããã±ãŒãžããã³ããŒã"
#: ../../rst/os_guide/intro_bsd.rst:65
msgid "In FreeBSD, there is no guarantee that either ``/usr/local/bin/python`` executable file or a link to an executable file is installed by default. The best practice for a remote host, with respect to Ansible, is to install at least the Python version supported by Ansible, for example, ``lang/python38``, and both meta ports ``lang/python3`` and ``lang/python``. Quoting from */usr/ports/lang/python3/pkg-descr*:"
msgstr "FreeBSD ã§ã¯ã``/usr/local/bin/python`` å®è¡å¯èœãã¡ã€ã«ãŸãã¯å®è¡å¯èœãã¡ã€ã«ãžã®ãªã³ã¯ã®ãããããããã©ã«ãã§ã€ã³ã¹ããŒã«ãããä¿èšŒã¯ãããŸãããAnsible ã«é¢é£ããŠãªã¢ãŒããã¹ãã®ãã¹ããã©ã¯ãã£ã¹ã¯ãå°ãªããšãAnsible ããµããŒããã Python ããŒãžã§ã³ïŒäŸïŒ``lang/python38`` ããã³ ``lang/python3`` ãš ``lang/python`` äž¡æ¹ã®ã¡ã¿ããŒãïŒãã€ã³ã¹ããŒã«ããããšã§ãã*/usr/ports/lang/python3/pkg-descr* ããã®åŒçš:"
#: ../../rst/os_guide/intro_bsd.rst:73
msgid "Quoting from */usr/ports/lang/python/pkg-descr*:"
msgstr "*/usr/ports/lang/python/pkg-descr* ããã®åŒçšïŒ"
#: ../../rst/os_guide/intro_bsd.rst:81
msgid "As a result, the following packages are installed:"
msgstr "ããã«ããã以äžã®ããã±ãŒãžãã€ã³ã¹ããŒã«ãããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:90
msgid "and the following executables and links"
msgstr "ããã«ã以äžã®å®è¡ãã¡ã€ã«ãšãªã³ã¯ãã€ã³ã¹ããŒã«ãããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:104
msgid "INTERPRETER_PYTHON_FALLBACK"
msgstr "INTERPRETER_PYTHON_FALLBACK"
#: ../../rst/os_guide/intro_bsd.rst:106
msgid "Since version 2.8 Ansible provides a useful variable ``ansible_interpreter_python_fallback`` to specify a list of paths to search for Python. See :ref:`INTERPRETER_PYTHON_FALLBACK`. This list will be searched and the first item found will be used. For example, the configuration below would make the installation of the meta-ports in the previous section redundant, that is, if you don't install the Python meta ports the first two items in the list will be skipped and ``/usr/local/bin/python3.8`` will be discovered."
msgstr "ããŒãžã§ã³ 2.8 以éãAnsible ã«ã¯ãPython ãæ€çŽ¢ãããã¹ã®äžèŠ§ãæå®ããããã®äŸ¿å©ãªå€æ° ``ansible_interpreter_python_fallback`` ãçšæãããŠããŸããã:ref:`INTERPRETER_PYTHON_FALLBACK`ããåç
§ããŠãã ããããã®äžèŠ§ãæ€çŽ¢ããèŠã€ãã£ãæåã®é
ç®ã䜿çšãããŸããããšãã°ã以äžã®èšå®ã§ã¯ãåã®ã»ã¯ã·ã§ã³ã®ã¡ã¿ããŒãã®ã€ã³ã¹ããŒã«ãåé·ã«ãªããŸããã€ãŸããPython ã¡ã¿ããŒããã€ã³ã¹ããŒã«ããªããšããªã¹ãã®æåã® 2 ã€ã®é
ç®ãçç¥ããã``/usr/local/bin/python3.8`` ãæ€åºãããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:113
msgid "You can use this variable, prolonged by the lower versions of Python, and put it, for example, into the ``group_vars/all``. Then, override it for specific groups in ``group_vars/{group1, group2, ...}`` and for specific hosts in ``host_vars/{host1, host2, ...}`` if needed. See :ref:`ansible_variable_precedence`."
msgstr "Python ã®äžäœããŒãžã§ã³ã§å»¶ã°ãããŠãããã®å€æ°ã䜿ããäŸãã°``group_vars/all``ã«å
¥ããŸãããããŠãå¿
èŠã«å¿ããŠ``group_vars/{group1, group2, ...}``ã®ç¹å®ã°ã«ãŒãã«å¯ŸããŠããŸã``host_vars/{host1, host2, ...}``ã®ç¹å®ãã¹ãã«å¯ŸããŠããªãŒããŒã©ã€ãããŸãã:ref:`ansible_variable_precedence`ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/intro_bsd.rst:117
msgid "Debug the discovery of Python"
msgstr "Python ã®æ€åºã®ãããã°"
#: ../../rst/os_guide/intro_bsd.rst:119
msgid "For example, given the inventory"
msgstr "ããšãã°ã以äžã®ã€ã³ãã³ããªãŒãæ³å®ããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:138
msgid "The playbook below"
msgstr "以äžã®Playbook ã«ããã"
#: ../../rst/os_guide/intro_bsd.rst:159
msgid "displays the details"
msgstr "詳现ã衚瀺ãããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:192
msgid "You can see that the first item from the list ``ansible_interpreter_python_fallback`` was discovered at the FreeBSD remote host. The variable ``ansible_playbook_python`` keeps the path to Python at the Linux controller that ran the playbook."
msgstr "ãªã¹ãã®æåã®ã¢ã€ãã ``ansible_interpreter_python_fallback`` ã FreeBSD ãªã¢ãŒããã¹ãã§æ€åºãããŠããããšãåãããŸããå€æ° ``ansible_playbook_python`` ã¯ãPlaybook ãå®è¡ãã Linux ã³ã³ãããŒã©ãŒã§ Python ãžã®ãã¹ãä¿æããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:194
msgid "Regarding the warning, quoting from :ref:`INTERPRETER_PYTHON`"
msgstr "èŠåã«é¢ããŠã:ref:`INTERPRETER_PYTHON`ããã®åŒçš"
#: ../../rst/os_guide/intro_bsd.rst:203
msgid "You can either ignore it or get rid of it by setting the variable ``ansible_python_interpreter=auto_silent`` because this is, actually, what you want by using ``/usr/local/bin/python`` (*\"interpreters installed later may change which one is used\"*). For example"
msgstr "å€æ° ``ansible_python_interpreter=auto_silent`` ãèšå®ããããšã§ããããç¡èŠãããããŸãã¯åãé€ãããšãã§ããŸããããã¯ãå®éã« ``/usr/local/bin/python`` ã䜿çšããŠåžæãããã®ã ããã§ãïŒ*ãåŸã§ã€ã³ã¹ããŒã«ãããã€ã³ã¿ãŒããªã¿ãŒã«ããã䜿çšããããã®ãå€ããå ŽåããããŸãã*ïŒã以äžã«äŸã瀺ããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:226
msgid ":ref:`interpreter_discovery`"
msgstr ":ref:`interpreter_discovery`"
#: ../../rst/os_guide/intro_bsd.rst:227
msgid "`FreeBSD Wiki: Ports/DEFAULT_VERSIONS <https://wiki.freebsd.org/Ports/DEFAULT_VERSIONS>`_"
msgstr "`FreeBSD Wiki: Ports/DEFAULT_VERSIONS <https://wiki.freebsd.org/Ports/DEFAULT_VERSIONS>`_"
#: ../../rst/os_guide/intro_bsd.rst:231
msgid "Additional variables"
msgstr "è¿œå ã®å€æ°"
#: ../../rst/os_guide/intro_bsd.rst:233
msgid "If you use additional plugins beyond those bundled with Ansible, you can set similar variables for ``bash``, ``perl`` or ``ruby``, depending on how the plugin is written. For example:"
msgstr "Ansible ã§ãã³ãã«ãããŠãããã©ã°ã€ã³ä»¥å€ã®ãã©ã°ã€ã³ã䜿çšããå Žåã¯ããã©ã°ã€ã³ã®èšè¿°æ¹æ³ã«å¿ã㊠``bash``ã``perl``ããŸã㯠``ruby`` ã«åæ§ã®å€æ°ãèšå®ã§ããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:243
msgid "Which modules are available?"
msgstr "å©çšå¯èœãªã¢ãžã¥ãŒã«"
#: ../../rst/os_guide/intro_bsd.rst:245
msgid "The majority of the core Ansible modules are written for a combination of Unix-like machines and other generic services, so most should function well on the BSDs with the obvious exception of those that are aimed at Linux-only technologies (such as LVG)."
msgstr "Ansible ã®ã³ã¢ã¢ãžã¥ãŒã«ã®å€§åã¯ãUnix ç³»ãã·ã³ãšä»ã®æ±çšãµãŒãã¹ãçµã¿åãããŠèšè¿°ãããŠãããããLinux ã«éå®ãããã¯ãããžãŒ (LVG ãªã©) ã察象ãšãããã®ãé€ãããã®å€§åã BSD äžã§æ£åžžã«æ©èœããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:248
msgid "Using BSD as the control node"
msgstr "ã³ã³ãããŒã«ããŒããšããŠã® BSD ã®äœ¿çš"
#: ../../rst/os_guide/intro_bsd.rst:250
msgid "Using BSD as the control machine is as simple as installing the Ansible package for your BSD variant or by following the ``pip`` or 'from source' instructions."
msgstr "BSD ãã³ã³ãããŒã«ãã·ã³ãšããŠäœ¿çšããããšã¯ãBSD ããªã¢ã³ãã® Ansible ããã±ãŒãžãã€ã³ã¹ããŒã«ãããã``pip`` ãŸãã¯ãfrom sourceãã®æ瀺ã«åŸãã®ãšåããããç°¡åã§ãã"
#: ../../rst/os_guide/intro_bsd.rst:255
msgid "BSD facts"
msgstr "BSD ãã¡ã¯ã"
#: ../../rst/os_guide/intro_bsd.rst:257
msgid "Ansible gathers facts from the BSDs in a similar manner to Linux machines, but since the data, names and structures can vary for network, disks and other devices, one should expect the output to be slightly different yet still familiar to a BSD administrator."
msgstr "Ansible ã¯ãLinux ãã·ã³ãšåæ§ã®æ¹æ³ã§ BSD ãããã¡ã¯ããåéããŸãããããŒã¿ãååãæ§é ã¯ããããã¯ãŒã¯ããã£ã¹ã¯ãããã³ãã®ä»ã®ããã€ã¹ã«ããç°ãªãå¯èœæ§ããããããBSD 管çè
ã«ãšã£ãŠã¯åºåãå€å°ç°ãªããã®ã®ãŸã 銎æã¿ãããããšãæåŸ
ã§ããŸãã"
#: ../../rst/os_guide/intro_bsd.rst:262
msgid "BSD efforts and contributions"
msgstr "BSD ã®åãçµã¿ããã³è²¢ç®"
#: ../../rst/os_guide/intro_bsd.rst:264
msgid "BSD support is important to us at Ansible. Even though the majority of our contributors use and target Linux we have an active BSD community and strive to be as BSD-friendly as possible. Please feel free to report any issues or incompatibilities you discover with BSD; pull requests with an included fix are also welcome!"
msgstr "BSD ãµããŒã㯠Ansible ã«ãšã£ãŠéèŠã§ããè²¢ç®è
ã®å€§å㯠Linux ã䜿çšããŠããŸãããAnsible ã«ã¯æŽ»çºãª BSD ã³ãã¥ããã£ãŒããããå¯èœãªéã BSD ãã¬ã³ããªãŒã§ããããã«åªããŠããŸããBSD ã«é¢ããåé¡ãéäºææ§ãçºèŠããå Žåã¯ãé æ
®ãªããå ±åãã ããã"
#: ../../rst/os_guide/intro_bsd.rst:269
msgid ":ref:`intro_adhoc`"
msgstr ":ref:`intro_adhoc`"
#: ../../rst/os_guide/intro_bsd.rst:270
msgid "Examples of basic commands"
msgstr "åºæ¬ã³ãã³ãã®äŸ"
#: ../../rst/os_guide/intro_bsd.rst:271
msgid ":ref:`working_with_playbooks`"
msgstr ":ref:`working_with_playbooks`"
#: ../../rst/os_guide/intro_bsd.rst:272
msgid "Learning ansible's configuration management language"
msgstr "Ansible ã®èšå®ç®¡çèšèªã®æŠèŠ"
#: ../../rst/os_guide/intro_bsd.rst:273
msgid ":ref:`developing_modules`"
msgstr ":ref:`developing_modules`"
#: ../../rst/os_guide/intro_bsd.rst:274
msgid "How to write modules"
msgstr "ã¢ãžã¥ãŒã«ã®æžãæ¹"
#: ../../rst/os_guide/intro_bsd.rst:275
msgid "`Mailing List <https://groups.google.com/group/ansible-project>`_"
msgstr "`Mailing List <https://groups.google.com/group/ansible-project>`_"
#: ../../rst/os_guide/intro_bsd.rst:276
msgid "Questions? Help? Ideas? Stop by the list on Google Groups"
msgstr "ã質åã¯ããããŸããããµããŒããå¿
èŠã§ããããææ¡ã¯ããããŸãããGoogle ã°ã«ãŒãã®äžèŠ§ãã芧ãã ããã"
#: ../../rst/os_guide/intro_bsd.rst:277 ../../rst/os_guide/windows_dsc.rst:507
#: ../../rst/os_guide/windows_faq.rst:256
#: ../../rst/os_guide/windows_setup.rst:498
#: ../../rst/os_guide/windows_usage.rst:518
#: ../../rst/os_guide/windows_winrm.rst:1012
msgid ":ref:`communication_irc`"
msgstr ":ref:`communication_irc`"
#: ../../rst/os_guide/intro_bsd.rst:278 ../../rst/os_guide/windows_dsc.rst:508
#: ../../rst/os_guide/windows_faq.rst:257
#: ../../rst/os_guide/windows_setup.rst:499
#: ../../rst/os_guide/windows_usage.rst:519
#: ../../rst/os_guide/windows_winrm.rst:1013
msgid "How to join Ansible chat channels"
msgstr "Ansible ãã£ãããã£ã³ãã«ãžã®åå æ¹æ³"
#: ../../rst/os_guide/windows_dsc.rst:4
msgid "Desired State Configuration"
msgstr "Desired State Configuration"
#: ../../rst/os_guide/windows_dsc.rst:7 ../../rst/os_guide/windows_usage.rst:11
msgid "Topics"
msgstr "ãããã¯"
#: ../../rst/os_guide/windows_dsc.rst:10
msgid "What is Desired State Configuration?"
msgstr "Desired State Configuration ãšã¯"
#: ../../rst/os_guide/windows_dsc.rst:11
msgid "Desired State Configuration, or DSC, is a tool built into PowerShell that can be used to define a Windows host setup through code. The overall purpose of DSC is the same as Ansible, it is just executed in a different manner. Since Ansible 2.4, the ``win_dsc`` module has been added and can be used to take advantage of existing DSC resources when interacting with a Windows host."
msgstr "Desired State Configuration (DSC) ã¯ãPowerShell ã«çµã¿èŸŒãŸããããŒã«ã§ãã³ãŒãã«ãã£ãŠ Windows ãã¹ãã®ã»ããã¢ãããå®çŸ©ããããã«äœ¿çšããããšãã§ããŸããDSC ã®å
šäœçãªç®ç㯠Ansible ãšåãã§ãããå®è¡æ¹æ³ãç°ãªãã ãã§ããAnsible 2.4 ããã¯ã``win_dsc`` ã¢ãžã¥ãŒã«ãè¿œå ãããWindows ãã¹ããšã®ãããšãã®éã«ãæ¢åã® DSC ãªãœãŒã¹ã掻çšããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:17
msgid "More details on DSC can be viewed at `DSC Overview <https://docs.microsoft.com/en-us/powershell/scripting/dsc/overview?view=powershell-7.2>`_."
msgstr "DSC ã®è©³çŽ°ã¯ã`DSC Overview <https://docs.microsoft.com/en-us/powershell/scripting/dsc/overview?view=powershell-7.2>`_ ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_dsc.rst:20
#: ../../rst/os_guide/windows_setup.rst:11
msgid "Host Requirements"
msgstr "ãã¹ãèŠä»¶"
#: ../../rst/os_guide/windows_dsc.rst:21
msgid "To use the ``win_dsc`` module, a Windows host must have PowerShell v5.0 or newer installed. All supported hosts can be upgraded to PowerShell v5."
msgstr "``win_dsc`` ã¢ãžã¥ãŒã«ã䜿çšããã«ã¯ãWindows ãã¹ãã« PowerShell v5.0 以éãã€ã³ã¹ããŒã«ãããŠããå¿
èŠããããŸãããµããŒã察象ã®ãã¹ãã¯ãã¹ãŠãPowerShell v5.0 ã«ã¢ããã°ã¬ãŒãããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:24
msgid "Once the PowerShell requirements have been met, using DSC is as simple as creating a task with the ``win_dsc`` module."
msgstr "PowerShell ã®èŠä»¶ãæºãããŠããã°ãDSC ã䜿çšããããšã¯ã``win_dsc`` ã¢ãžã¥ãŒã«ã§ã¿ã¹ã¯ãäœæããã®ãšåããããç°¡åã§ãã"
#: ../../rst/os_guide/windows_dsc.rst:28
msgid "Why Use DSC?"
msgstr "DSC ã䜿çšããçç±"
#: ../../rst/os_guide/windows_dsc.rst:29
msgid "DSC and Ansible modules have a common goal which is to define and ensure the state of a resource. Because of this, resources like the DSC `File resource <https://docs.microsoft.com/en-us/powershell/scripting/dsc/reference/resources/windows/fileresource>`_ and Ansible ``win_file`` can be used to achieve the same result. Deciding which to use depends on the scenario."
msgstr "DSC ãš Ansible ã¢ãžã¥ãŒã«ã«ã¯ããªãœãŒã¹ã®ç¶æ
ãå®çŸ©ããŠä¿èšŒãããšããå
±éã®ç®çããããŸãããã®ãããDSC `ãã¡ã€ã«ãªãœãŒã¹ <https://docs.microsoft.com/en-us/powershell/scripting/dsc/reference/resources/windows/fileresource>`_ ã Ansible``win_file`` ã®ãããªãªãœãŒã¹ã䜿çšããŠãåãçµæãåŸãããšãã§ããŸããã©ã¡ãã䜿çšãããã¯ãã·ããªãªã«ãã£ãŠç°ãªããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:35
msgid "Reasons for using an Ansible module over a DSC resource:"
msgstr "DSC ãªãœãŒã¹ã§ Ansible ã¢ãžã¥ãŒã«ã䜿çšããçç±:"
#: ../../rst/os_guide/windows_dsc.rst:37
msgid "The host does not support PowerShell v5.0, or it cannot easily be upgraded"
msgstr "ãã¹ãã PowerShell v5.0 ããµããŒãããŠããªãããŸãã¯ç°¡åã«ã¢ããã°ã¬ãŒãã§ããªã"
#: ../../rst/os_guide/windows_dsc.rst:38
msgid "The DSC resource does not offer a feature present in an Ansible module. For example, win_regedit can manage the ``REG_NONE`` property type, while the DSC ``Registry`` resource cannot"
msgstr "DSC ãªãœãŒã¹ã¯ãAnsible ã¢ãžã¥ãŒã«ã«ååšããæ©èœãæäŸããªããããšãã°ãwin_regedit 㯠``REG_NONE`` ã®ããããã£ãŒã¿ã€ãã管çã§ããŸãããDSC ã® ``Registry`` ãªãœãŒã¹ã§ã¯ç®¡çã§ããŸããã"
#: ../../rst/os_guide/windows_dsc.rst:41
msgid "DSC resources have limited check mode support, while some Ansible modules have better checks"
msgstr "DSC ã®ãªãœãŒã¹ã¯ãã§ãã¯ã¢ãŒãã®ãµããŒããéãããŠããããAnsible ã¢ãžã¥ãŒã«ã®äžã«ã¯ããåªãããã§ãã¯æ©èœãæã€ãã®ããã"
#: ../../rst/os_guide/windows_dsc.rst:43
msgid "DSC resources do not support diff mode, while some Ansible modules do"
msgstr "DSC ãªãœãŒã¹ã§ã¯å·®åã¢ãŒãããµããŒããããªãããäžéšã® Ansible ã¢ãžã¥ãŒã«ã§ã¯ãµããŒãããã"
#: ../../rst/os_guide/windows_dsc.rst:44
msgid "Custom resources require further installation steps to be run on the host beforehand, while Ansible modules are built-in to Ansible"
msgstr "ã«ã¹ã¿ã ãªãœãŒã¹ã§ã¯ãäºåã«ãã¹ãäžã§è¿œå ã®ã€ã³ã¹ããŒã«æé ãå®è¡ããå¿
èŠãããããAnsible ã¢ãžã¥ãŒã«ã¯ Ansible ã«çµã¿èŸŒãŸããŠãã"
#: ../../rst/os_guide/windows_dsc.rst:46
msgid "There are bugs in a DSC resource where an Ansible module works"
msgstr "Ansible ã¢ãžã¥ãŒã«ãæ©èœãã DSC ãªãœãŒã¹ã«ãã°ããã"
#: ../../rst/os_guide/windows_dsc.rst:48
msgid "Reasons for using a DSC resource over an Ansible module:"
msgstr "Ansible ã¢ãžã¥ãŒã«ã§ DSC ãªãœãŒã¹ã䜿çšããçç±:"
#: ../../rst/os_guide/windows_dsc.rst:50
msgid "The Ansible module does not support a feature present in a DSC resource"
msgstr "Ansible ã¢ãžã¥ãŒã«ã¯ãDSC ãªãœãŒã¹ã«ååšããæ©èœããµããŒãããŠããªã"
#: ../../rst/os_guide/windows_dsc.rst:51
msgid "There is no Ansible module available"
msgstr "å©çšå¯èœãª Ansible ã¢ãžã¥ãŒã«ããªã"
#: ../../rst/os_guide/windows_dsc.rst:52
msgid "There are bugs in an existing Ansible module"
msgstr "æ¢åã® Ansible ã¢ãžã¥ãŒã«ã«ãã°ããã"
#: ../../rst/os_guide/windows_dsc.rst:54
msgid "In the end, it doesn't matter whether the task is performed with DSC or an Ansible module; what matters is that the task is performed correctly and the playbooks are still readable. If you have more experience with DSC over Ansible and it does the job, just use DSC for that task."
msgstr "ã€ãŸããšãããã¿ã¹ã¯ã DSC ã§å®è¡ãããã Ansible ã¢ãžã¥ãŒã«ã§å®è¡ããããã¯éèŠã§ã¯ãããŸãããéèŠãªã®ã¯ãã¿ã¹ã¯ãæ£ããå®è¡ãããPlaybook ãèªããããšã§ããAnsible ããã DSC ã®æ¹ã䜿çšããçµéšããããããã§å¿
èŠãªããšãã§ããã®ã§ããã°ããã®ã¿ã¹ã¯ã«ã¯ DSC ã䜿çšãããšè¯ãã§ãããã"
#: ../../rst/os_guide/windows_dsc.rst:60
msgid "How to Use DSC?"
msgstr "DSC ã®äœ¿çšæ¹æ³"
#: ../../rst/os_guide/windows_dsc.rst:61
msgid "The ``win_dsc`` module takes in a free-form of options so that it changes according to the resource it is managing. A list of built-in resources can be found at `resources <https://docs.microsoft.com/en-us/powershell/scripting/dsc/resources/resources>`_."
msgstr "``win_dsc`` ã¢ãžã¥ãŒã«ã¯ã管çããŠãããªãœãŒã¹ã«å¿ããŠå€åããããã«ãããªãŒãã©ãŒã ã®ãªãã·ã§ã³ãåãå
¥ããŠããŸããçµã¿èŸŒãŸããŠãããªãœãŒã¹ã®ãªã¹ãã¯ã`resources <https://docs.microsoft.com/en-us/powershell/scripting/dsc/resources/resources>`_ ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_dsc.rst:65
msgid "Using the `Registry <https://docs.microsoft.com/en-us/powershell/scripting/dsc/reference/resources/windows/registryresource>`_ resource as an example, this is the DSC definition as documented by Microsoft:"
msgstr "`Registry <https://docs.microsoft.com/en-us/powershell/scripting/dsc/reference/resources/windows/registryresource>`_ ãªãœãŒã¹ãäŸã«ãšããšããã㯠Microsoft ãææžåããDSCã®å®çŸ©ã§ãã"
#: ../../rst/os_guide/windows_dsc.rst:82
msgid "When defining the task, ``resource_name`` must be set to the DSC resource being used - in this case, the ``resource_name`` should be set to ``Registry``. The ``module_version`` can refer to a specific version of the DSC resource installed; if left blank it will default to the latest version. The other options are parameters that are used to define the resource, such as ``Key`` and ``ValueName``. While the options in the task are not case sensitive, keeping the case as-is is recommended because it makes it easier to distinguish DSC resource options from Ansible's ``win_dsc`` options."
msgstr "ã¿ã¹ã¯ãå®çŸ©ããéã«ã¯ã䜿çšãã DSC ãªãœãŒã¹ã ``resource_name`` ã«èšå®ããå¿
èŠããããŸãããã®å Žåã``resource_name`` 㯠``Registry`` ã«èšå®ããå¿
èŠããããŸãã``module_version`` ã¯ã€ã³ã¹ããŒã«ãããŠãã DSC ãªãœãŒã¹ã®ç¹å®ã®ããŒãžã§ã³ãåç
§ããããšãã§ããŸããã空çœã«ãããšããã©ã«ãã§ææ°ããŒãžã§ã³ã«ãªããŸãããã®ä»ã®ãªãã·ã§ã³ã¯ ``Key`` ã ``ValueName`` ã®ããã«ãªãœãŒã¹ãå®çŸ©ããããã®ãã©ã¡ãŒã¿ãŒã«ãªããŸããã¿ã¹ã¯ã®ãªãã·ã§ã³ã¯å€§æåå°æåãåºå¥ããŸããããDSC ãªãœãŒã¹ã®ãªãã·ã§ã³ãš Ansible ã®``win_dsc`` ã®ãªãã·ã§ã³ãåºå¥ããããããããã«ã倧æåå°æåããã®ãŸãŸã«ããŠããããšãæšå¥šãããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:91
msgid "This is what the Ansible task version of the above DSC Registry resource would look like:"
msgstr "äžèšã® DSC ã¬ãžã¹ããªãŒãªãœãŒã¹ã® Ansible ã¿ã¹ã¯ããŒãžã§ã³ã¯ã以äžã®ããã«ãªããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:103
msgid "Starting in Ansible 2.8, the ``win_dsc`` module automatically validates the input options from Ansible with the DSC definition. This means Ansible will fail if the option name is incorrect, a mandatory option is not set, or the value is not a valid choice. When running Ansible with a verbosity level of 3 or more (``-vvv``), the return value will contain the possible invocation options based on the ``resource_name`` specified. Here is an example of the invocation output for the above ``Registry`` task:"
msgstr "Ansible 2.8 ããã``win_dsc`` ã¢ãžã¥ãŒã«ã¯ãAnsible ããã®å
¥åãªãã·ã§ã³ã DSC å®çŸ©ã§èªåçã«æ€èšŒããŸããã€ãŸãããªãã·ã§ã³åãééã£ãŠããããå¿
é ãªãã·ã§ã³ãèšå®ãããŠããªãã£ãããå€ãæå¹ãªéžæè¢ã§ãªãã£ãããããšãAnsible ã¯å€±æããŸããAnsible ãåé·ã¬ãã« 3 ä»¥äž (``-vvv``) ã§å®è¡ããå Žåãæ»ãå€ã«ã¯ãæå®ããã ``resource_name`` ã«åºã¥ããŠå¯èœãªåŒã³åºããªãã·ã§ã³ãå«ãŸããŸãã以äžã¯ãäžèšã® ``Registry`` ã¿ã¹ã¯ã®åŒã³åºãåºåã®äŸã§ãã"
#: ../../rst/os_guide/windows_dsc.rst:158
msgid "The ``invocation.module_args`` key shows the actual values that were set as well as other possible values that were not set. Unfortunately, this will not show the default value for a DSC property, only what was set from the Ansible task. Any ``*_password`` option will be masked in the output for security reasons; if there are any other sensitive module options, set ``no_log: True`` on the task to stop all task output from being logged."
msgstr "``invocation.module_args`` ããŒã¯ãèšå®ãããå®éã®å€ãšãèšå®ãããªãã£ãä»ã®å¯èœãªå€ã衚瀺ããŸããDSC ããããã£ãŒã®ããã©ã«ãå€ã¯è¡šç€ºããããAnsible ã¿ã¹ã¯ã§èšå®ãããå€ã®ã¿ã衚瀺ãããŸãã``*_password`` ãªãã·ã§ã³ã¯ãã»ãã¥ãªãã£ãŒäžã®çç±ããåºåã§ã¯ãã¹ã¯ãããŸããä»ã«æ©å¯æ§ã®é«ãã¢ãžã¥ãŒã«ãªãã·ã§ã³ãããå Žåã¯ãã¿ã¹ã¯ã« ``no_log: True`` ãèšå®ããŠããã¹ãŠã®ã¿ã¹ã¯åºåããã°ã«èšé²ãããªãããã«ããŠãã ããã"
#: ../../rst/os_guide/windows_dsc.rst:167
msgid "Property Types"
msgstr "ããããã£ãŒã¿ã€ã"
#: ../../rst/os_guide/windows_dsc.rst:168
msgid "Each DSC resource property has a type that is associated with it. Ansible will try to convert the defined options to the correct type during execution. For simple types like ``[string]`` and ``[bool]``, this is a simple operation, but complex types like ``[PSCredential]`` or arrays (like ``[string[]]``) require certain rules."
msgstr "å DSC ãªãœãŒã¹ããããã£ãŒã«ã¯ãããã«é¢é£ä»ããããã¿ã€ãããããŸããAnsible ã¯ãå®è¡æã«å®çŸ©ããããªãã·ã§ã³ãæ£ããã¿ã€ãã«å€æããããšããŸãã``[string]`` ã ``[bool]`` ã®ãããªåçŽãªã¿ã€ãã§ã¯ãããã¯åçŽãªæäœã§ããã``[PSCredential]`` ãé
å (``[string[]]`` ãªã©) ã®ãããªè€éãªã¿ã€ãã§ã¯ãç¹å®ã®ã«ãŒã«ãå¿
èŠã§ãã"
#: ../../rst/os_guide/windows_dsc.rst:175
msgid "PSCredential"
msgstr "PSCredential"
#: ../../rst/os_guide/windows_dsc.rst:176
msgid "A ``[PSCredential]`` object is used to store credentials in a secure way, but Ansible has no way to serialize this over JSON. To set a DSC PSCredential property, the definition of that parameter should have two entries that are suffixed with ``_username`` and ``_password`` for the username and password, respectively. For example:"
msgstr "``[PSCredential]`` ãªããžã§ã¯ãã¯èªèšŒæ
å ±ãå®å
šãªæ¹æ³ã§ä¿åããããã«äœ¿çšãããŸãããAnsible ã«ã¯ããã JSON ã§ã·ãªã¢ã«åããæ¹æ³ããããŸãããDSC PSCredential ããããã£ãŒãèšå®ããã«ã¯ããã®ãã©ã¡ãŒã¿ãŒã®å®çŸ©ã«ããŠãŒã¶åãšãã¹ã¯ãŒãããããã ``_username`` ãš ``_password`` ããµãã£ãã¯ã¹ã«ãã 2 ã€ã®ãšã³ããªãŒãè¿œå ããå¿
èŠããããŸããããšãã°ã以äžã®ããã«ãªããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:190
msgid "On versions of Ansible older than 2.8, you should set ``no_log: true`` on the task definition in Ansible to ensure any credentials used are not stored in any log file or console output."
msgstr "2.8 ããå€ãããŒãžã§ã³ã® Ansible ã§ã¯ãAnsible ã®ã¿ã¹ã¯å®çŸ©ã« ``no_log: true`` ãèšå®ããŠã䜿çšããèªèšŒæ
å ±ããã°ãã¡ã€ã«ãŸãã¯ã³ã³ãœãŒã«ã®åºåã«ä¿åãããªãããã«ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:194
msgid "A ``[PSCredential]`` is defined with ``EmbeddedInstance(\"MSFT_Credential\")`` in a DSC resource MOF definition."
msgstr "``[PSCredential]`` ã¯ãDSC ãªãœãŒã¹ã® MOF å®çŸ©ã«ãããŠ``EmbeddedInstance(\"MSFT_Credential\")`` ãšå
±ã«å®çŸ©ãããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:198
msgid "CimInstance Type"
msgstr "CimInstance ã¿ã€ã"
#: ../../rst/os_guide/windows_dsc.rst:199
msgid "A ``[CimInstance]`` object is used by DSC to store a dictionary object based on a custom class defined by that resource. Defining a value that takes in a ``[CimInstance]`` in YAML is the same as defining a dictionary in YAML. For example, to define a ``[CimInstance]`` value in Ansible:"
msgstr "``[CimInstance]`` ãªããžã§ã¯ãã¯ãDSC ããã®ãªãœãŒã¹ã§å®çŸ©ãããã«ã¹ã¿ã ã¯ã©ã¹ã«åºã¥ããŠãã£ã¯ã·ã§ããªãŒãªããžã§ã¯ããæ ŒçŽããããã«äœ¿çšãããŸãã``[CimInstance]`` ãåã蟌ãå€ã YAML ã§å®çŸ©ããããšã¯ãYAML ã§ãã£ã¯ã·ã§ããªãŒãå®çŸ©ããããšãšåãã§ããããšãã°ãAnsible ã§``[CimInstance]`` ã®å€ãå®çŸ©ããå Žåã¯ã以äžã®ããã«ãªããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:213
msgid "In the above example, the CIM instance is a representation of the class `MSFT_xWebAuthenticationInformation <https://github.com/dsccommunity/xWebAdministration/blob/master/source/DSCResources/MSFT_xWebSite/MSFT_xWebSite.schema.mof>`_. This class accepts four boolean variables, ``Anonymous``, ``Basic``, ``Digest``, and ``Windows``. The keys to use in a ``[CimInstance]`` depend on the class it represents. Please read through the documentation of the resource to determine the keys that can be used and the types of each key value. The class definition is typically located in the ``<resource name>.schema.mof``."
msgstr "äžèšã®äŸã§ã¯ãCIM ã€ã³ã¹ã¿ã³ã¹ã¯ãã¯ã©ã¹ `MSFT_xWebAuthenticationInformation <https://github.com/dsccommunity/xWebAdministration/blob/master/source/DSCResources/MSFT_xWebSite/MSFT_xWebSite.schema.mof>`_ ã®è¡šçŸã§ãããã®ã¯ã©ã¹ã¯ã``Anonymous``ã``Basic``ã``Digest``ã``Windows`` ãšãã 4 ã€ã®ããŒã«å€æ°ãåãå
¥ããŸãã``[CimInstance]`` ã§äœ¿çšããããŒã¯ããããè¡šçŸããã¯ã©ã¹ã«ãã£ãŠç°ãªããŸãã䜿çšã§ããããŒãšåããŒã®å€ã®ã¿ã€ãã«ã€ããŠã¯ããªãœãŒã¹ã®ããã¥ã¡ã³ããåç
§ããŠãã ãããã¯ã©ã¹ã®å®çŸ©ã¯ãéåžžã``<resource name>.schema.mof`` ã«ãããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:222
msgid "HashTable Type"
msgstr "HashTable ã¿ã€ã"
#: ../../rst/os_guide/windows_dsc.rst:223
msgid "A ``[HashTable]`` object is also a dictionary but does not have a strict set of keys that can/need to be defined. Like a ``[CimInstance]``, define it as a normal dictionary value in YAML. A ``[HashTable]]`` is defined with ``EmbeddedInstance(\"MSFT_KeyValuePair\")`` in a DSC resource MOF definition."
msgstr "``[HashTable]`` ãªããžã§ã¯ãããã£ã¯ã·ã§ããªãŒã§ãããå®çŸ©ã§ãã/ããªããã°ãªããªãå³å¯ãªéµã®ã»ããããããŸããã``[CimInstance]`` ã®ããã«ãYAML ã§éåžžã®ãã£ã¯ã·ã§ããªãŒå€ã®ããã«å®çŸ©ããŸãã``[HashTable]]`` ã¯ãDSC ãªãœãŒã¹ã® MOF å®çŸ©ã«ãã㊠``EmbeddedInstance(\"MSFT_KeyValuePair\")`` ãšå
±ã«å®çŸ©ãããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:229
msgid "Arrays"
msgstr "é
å"
#: ../../rst/os_guide/windows_dsc.rst:230
msgid "Simple type arrays like ``[string[]]`` or ``[UInt32[]]`` are defined as a list or as a comma-separated string which is then cast to their type. Using a list is recommended because the values are not manually parsed by the ``win_dsc`` module before being passed to the DSC engine. For example, to define a simple type array in Ansible:"
msgstr "``[string[]]`` ã ``[UInt32[]]`` ã®ãããªåçŽãªã¿ã€ãã®é
åã¯ããªã¹ããŸãã¯ã³ã³ãåºåãã®æååãšããŠå®çŸ©ãããããããã¿ã€ãã«ãã£ã¹ããããŸãããªã¹ãã䜿çšãããšãDSC ãšã³ãžã³ã«æž¡ãåã« ``win_dsc`` ã¢ãžã¥ãŒã«ã§å€ãæåã§è§£æãããªããããæšå¥šãããŸããããšãã°ãAnsible ã§åçŽãªã¿ã€ãã®é
åãå®çŸ©ããã«ã¯ã次ã®ããã«ããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:251
msgid "Complex type arrays like ``[CimInstance[]]`` (array of dicts), can be defined like this example:"
msgstr "``[CimInstance[]]`` (ãã£ã¯ã·ã§ããªãŒã®é
å) ã®ãããªè€éãªã¿ã€ãã®é
åã¯ã次ã®äŸã®ããã«å®çŸ©ã§ããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:269
msgid "The above example is an array with two values of the class `MSFT_xWebBindingInformation <https://github.com/dsccommunity/xWebAdministration/blob/master/source/DSCResources/MSFT_xWebSite/MSFT_xWebSite.schema.mof>`_. When defining a ``[CimInstance[]]``, be sure to read the resource documentation to find out what keys to use in the definition."
msgstr "äžèšã®äŸã¯ã`MSFT_xWebBindingInformation <https://github.com/dsccommunity/xWebAdministration/blob/master/source/DSCResources/MSFT_xWebSite/MSFT_xWebSite.schema.mof>`_ ã¯ã©ã¹ã® 2 ã€ã®å€ã®ããé
åã§ãã``[CimInstance[]]`` ãå®çŸ©ãããšããªãœãŒã¹ããã¥ã¡ã³ããåç
§ããŠãå®çŸ©ã§äœ¿çšããããŒã確èªããŠãã ããã"
#: ../../rst/os_guide/windows_dsc.rst:274
msgid "DateTime"
msgstr "æ¥æ"
#: ../../rst/os_guide/windows_dsc.rst:275
msgid "A ``[DateTime]`` object is a DateTime string representing the date and time in the `ISO 8601 <https://www.w3.org/TR/NOTE-datetime>`_ date time format. The value for a ``[DateTime]`` field should be quoted in YAML to ensure the string is properly serialized to the Windows host. Here is an example of how to define a ``[DateTime]`` value in Ansible:"
msgstr "``[DateTime]`` ãªããžã§ã¯ãã¯ã`ISO 8601 <https://www.w3.org/TR/NOTE-datetime>`_ ã®æ¥æãã©ãŒãããã§æ¥ä»ãšæéãè¡šã DateTime æååã§ãã``[DateTime]`` ãã£ãŒã«ãã®å€ã¯ãæååã Windows ãã¹ãã«é©åã«ã·ãªã¢ã©ã€ãºãããããã«ãYAML ã§åŒçšããå¿
èŠããããŸãã以äžã¯ãAnsible ã§``[DateTime]`` ã®å€ãå®çŸ©ããæ¹æ³ã®äŸã§ãã"
#: ../../rst/os_guide/windows_dsc.rst:292
msgid "All the values above are equal to a UTC date time of February 22nd 2019 at 1:57pm with 31 seconds and 2311892 milliseconds."
msgstr "äžèšã®ãã¹ãŠã®å€ã¯ãUTCã® æ¥ä»æå»ã 2019 幎 2 æ 22 æ¥ååŸ 1 æ 57 å 31 ç§ 2311892 ããªç§ã§ããããšãšåãã§ãã"
#: ../../rst/os_guide/windows_dsc.rst:296
msgid "Run As Another User"
msgstr "å¥ã®ãŠãŒã¶ãŒãšããŠå®è¡"
#: ../../rst/os_guide/windows_dsc.rst:297
msgid "By default, DSC runs each resource as the SYSTEM account and not the account that Ansible uses to run the module. This means that resources that are dynamically loaded based on a user profile, like the ``HKEY_CURRENT_USER`` registry hive, will be loaded under the ``SYSTEM`` profile. The parameter ``PsDscRunAsCredential`` is a parameter that can be set for every DSC resource, and force the DSC engine to run under a different account. As ``PsDscRunAsCredential`` has a type of ``PSCredential``, it is defined with the ``_username`` and ``_password`` suffix."
msgstr "ããã©ã«ãã§ã¯ãDSC ã¯åãªãœãŒã¹ããAnsible ãã¢ãžã¥ãŒã«ã®å®è¡ã«äœ¿çšããã¢ã«ãŠã³ãã§ã¯ãªããSYSTEM ã¢ã«ãŠã³ããšããŠå®è¡ããŸããã€ãŸãã``HKEY_CURRENT_USER`` ã®ã¬ãžã¹ããªãŒãã€ãã®ããã«ããŠãŒã¶ãŒãããã¡ã€ã«ã«åºã¥ããŠåçã«èªã¿èŸŒãŸãããªãœãŒã¹ã¯ã``SYSTEM`` ã®ãããã¡ã€ã«ã§èªã¿èŸŒãŸããŸãã``PsDscRunAsCredential`` ã¯ãDSC ãšã³ãžã³ãå¥ã®ã¢ã«ãŠã³ãã§å®è¡ãããããã«ããã¹ãŠã® DSC ãªãœãŒã¹ã«èšå®ããããšãã§ãããã©ã¡ãŒã¿ãŒã§ãã``PsDscRunAsCredential`` ã¯ã¿ã€ãã ``PSCredential`` ãªã®ã§ããµãã£ãã¯ã¹ ``_username`` ãš``_password`` ã§å®çŸ©ãããŠããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:306
msgid "Using the Registry resource type as an example, this is how to define a task to access the ``HKEY_CURRENT_USER`` hive of the Ansible user:"
msgstr "ã¬ãžã¹ããªãŒãªãœãŒã¹ã¿ã€ããäŸãšããŠäœ¿çšããAnsible ãŠãŒã¶ãŒã® ``HKEY_CURRENT_USER`` ãã€ãã«ã¢ã¯ã»ã¹ããã¿ã¹ã¯ãå®çŸ©ããæ¹æ³ã説æããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:323
msgid "Custom DSC Resources"
msgstr "ã«ã¹ã¿ã ã® DSC ãªãœãŒã¹"
#: ../../rst/os_guide/windows_dsc.rst:324
msgid "DSC resources are not limited to the built-in options from Microsoft. Custom modules can be installed to manage other resources that are not usually available."
msgstr "DSC ã®ãªãœãŒã¹ã¯ãMicrosoft ã®çµã¿èŸŒã¿ãªãã·ã§ã³ã«éå®ãããŸãããã«ã¹ã¿ã ã¢ãžã¥ãŒã«ãã€ã³ã¹ããŒã«ããããšã§ãéåžžã§ã¯å©çšã§ããªãä»ã®ãªãœãŒã¹ã管çããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:328
msgid "Finding Custom DSC Resources"
msgstr "ã«ã¹ã¿ã ã® DSC ãªãœãŒã¹ã®èŠã€ãæ¹"
#: ../../rst/os_guide/windows_dsc.rst:329
msgid "You can use the `PSGallery <https://www.powershellgallery.com/>`_ to find custom resources, along with documentation on how to install them on a Windows host."
msgstr "`PSGallery <https://www.powershellgallery.com/>`_ ã䜿çšãããšãã«ã¹ã¿ã ãªãœãŒã¹ãšãããã Windows ãã¹ãã«ã€ã³ã¹ããŒã«ããæ¹æ³ã«é¢ããããã¥ã¡ã³ããèŠã€ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:332
msgid "The ``Find-DscResource`` cmdlet can also be used to find custom resources. For example:"
msgstr "``Find-DscResource`` ã³ãã³ãã¬ããã䜿çšããŠãã«ã¹ã¿ã ãªãœãŒã¹ãæ€çŽ¢ããããšãã§ããŸãã以äžã«äŸã瀺ããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:342
msgid "DSC resources developed by Microsoft that start with ``x`` means the resource is experimental and comes with no support."
msgstr "Microsoft ãéçºãã DSC ãªãœãŒã¹ã§ã``x`` ã§å§ãŸããã®ã¯ãå®éšçãªãªãœãŒã¹ã§ããããµããŒãããªãããšãæå³ããŠããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:346
msgid "Installing a Custom Resource"
msgstr "ã«ã¹ã¿ã ãªãœãŒã¹ã®ã€ã³ã¹ããŒã«"
#: ../../rst/os_guide/windows_dsc.rst:347
msgid "There are three ways that a DSC resource can be installed on a host:"
msgstr "DSC ãªãœãŒã¹ããã¹ãã«ã€ã³ã¹ããŒã«ããæ¹æ³ã¯ 3 ã€ãããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:349
msgid "Manually with the ``Install-Module`` cmdlet"
msgstr "``Install-Module`` ã³ãã³ãã¬ãããæåã§äœ¿çš"
#: ../../rst/os_guide/windows_dsc.rst:350
msgid "Using the ``win_psmodule`` Ansible module"
msgstr "Ansibleã¢ãžã¥ãŒã« ``win_psmodule`` ã䜿çš"
#: ../../rst/os_guide/windows_dsc.rst:351
msgid "Saving the module manually and copying it to another host"
msgstr "ã¢ãžã¥ãŒã«ãæåã§ä¿åããŠå¥ã®ãã¹ãã«ã³ããŒ"
#: ../../rst/os_guide/windows_dsc.rst:353
msgid "The following is an example of installing the ``xWebAdministration`` resources using ``win_psmodule``:"
msgstr "以äžã¯ã``win_psmodule`` ã䜿çšã㊠``xWebAdministration`` ãªãœãŒã¹ãã€ã³ã¹ããŒã«ããäŸã§ãã"
#: ../../rst/os_guide/windows_dsc.rst:363
msgid "Once installed, the win_dsc module will be able to use the resource by referencing it with the ``resource_name`` option."
msgstr "ã€ã³ã¹ããŒã«ãããšãwin_dsc ã¢ãžã¥ãŒã«ã¯ã``resource_name`` ãªãã·ã§ã³ã§ãªãœãŒã¹ãåç
§ããããšã§ããªãœãŒã¹ã䜿çšã§ããããã«ãªããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:366
msgid "The first two methods above only work when the host has access to the internet. When a host does not have internet access, the module must first be installed using the methods above on another host with internet access and then copied across. To save a module to a local filepath, the following PowerShell cmdlet can be run:"
msgstr "äžèšã®æåã® 2 ã€ã®æ¹æ³ã¯ããã¹ããã€ã³ã¿ãŒãããã«ã¢ã¯ã»ã¹ã§ããå Žåã«ã®ã¿æ©èœããŸãããã¹ããã€ã³ã¿ãŒãããã«ã¢ã¯ã»ã¹ã§ããªãå Žåã¯ããŸãã€ã³ã¿ãŒãããã«ã¢ã¯ã»ã¹ã§ããå¥ã®ãã¹ãäžã§äžèšã®æ¹æ³ã䜿çšããŠã¢ãžã¥ãŒã«ãã€ã³ã¹ããŒã«ãããããã³ããŒããå¿
èŠããããŸããã¢ãžã¥ãŒã«ãããŒã«ã«ã®ãã¡ã€ã«ãã¹ã«ä¿åããã«ã¯ã次㮠PowerShell ã³ãã³ãã¬ãããå®è¡ããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:376
msgid "This will create a folder called ``xWebAdministration`` in ``C:\\temp``, which can be copied to any host. For PowerShell to see this offline resource, it must be copied to a directory set in the ``PSModulePath`` environment variable. In most cases, the path ``C:\\Program Files\\WindowsPowerShell\\Module`` is set through this variable, but the ``win_path`` module can be used to add different paths."
msgstr "ããã«ããã``C:\\temp`` ã®äžã«``xWebAdministration`` ãã©ã«ããŒãäœæããããã®ãã£ã«ããŒã¯ã©ã®ãã¹ãã«ãã³ããŒã§ããããã«ãªããŸããPowerShell ããã®ãªãã©ã€ã³ãªãœãŒã¹ãèŠãããã«ã¯ãç°å¢å€æ° ``PSModulePath`` ã§èšå®ããããã£ã¬ã¯ããªãŒã«ã³ããŒãããŠããå¿
èŠããããŸããã»ãšãã©ã®å Žåã¯ããã®å€æ°ãéããŠãã¹ ``C:\\Program Files\\WindowsPowerShell\\Module`` ãèšå®ãããŸããã``win_path`` ã¢ãžã¥ãŒã«ã䜿çšããŠç°ãªããã¹ãè¿œå ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_dsc.rst:384
msgid "Examples"
msgstr "äŸ"
#: ../../rst/os_guide/windows_dsc.rst:386
msgid "Extract a zip file"
msgstr "zip ãã¡ã€ã«ã®å±é"
#: ../../rst/os_guide/windows_dsc.rst:398
msgid "Create a directory"
msgstr "ãã£ã¬ã¯ããªãŒã®äœæ"
#: ../../rst/os_guide/windows_dsc.rst:421
msgid "Interact with Azure"
msgstr "Azure ã®æäœ"
#: ../../rst/os_guide/windows_dsc.rst:444
msgid "Setup IIS Website"
msgstr "IIS Web ãµã€ãã®ã»ããã¢ãã"
#: ../../rst/os_guide/windows_dsc.rst:499
#: ../../rst/os_guide/windows_usage.rst:510
#: ../../rst/os_guide/windows_winrm.rst:1004
msgid ":ref:`playbooks_intro`"
msgstr ":ref:`playbooks_intro`"
#: ../../rst/os_guide/windows_dsc.rst:500
#: ../../rst/os_guide/windows_faq.rst:251
#: ../../rst/os_guide/windows_setup.rst:491
#: ../../rst/os_guide/windows_usage.rst:511
#: ../../rst/os_guide/windows_winrm.rst:1005
msgid "An introduction to playbooks"
msgstr "Playbook ã®æŠèŠ"
#: ../../rst/os_guide/windows_dsc.rst:501
#: ../../rst/os_guide/windows_faq.rst:252
#: ../../rst/os_guide/windows_setup.rst:492
#: ../../rst/os_guide/windows_usage.rst:512
#: ../../rst/os_guide/windows_winrm.rst:1006
msgid ":ref:`playbooks_best_practices`"
msgstr ":ref:`playbooks_best_practices`"
#: ../../rst/os_guide/windows_dsc.rst:502
#: ../../rst/os_guide/windows_faq.rst:253
#: ../../rst/os_guide/windows_setup.rst:493
#: ../../rst/os_guide/windows_usage.rst:513
#: ../../rst/os_guide/windows_winrm.rst:1007
msgid "Tips and tricks for playbooks"
msgstr "Playbook ã®ãã³ããšè£æ"
#: ../../rst/os_guide/windows_dsc.rst:503
#: ../../rst/os_guide/windows_setup.rst:494
#: ../../rst/os_guide/windows_usage.rst:514
#: ../../rst/os_guide/windows_winrm.rst:1008
msgid ":ref:`List of Windows Modules <windows_modules>`"
msgstr ":ref:`List of Windows Modules <windows_modules>`"
#: ../../rst/os_guide/windows_dsc.rst:504
#: ../../rst/os_guide/windows_setup.rst:495
#: ../../rst/os_guide/windows_usage.rst:515
#: ../../rst/os_guide/windows_winrm.rst:1009
msgid "Windows specific module list, all implemented in PowerShell"
msgstr "Windows åºæã®ã¢ãžã¥ãŒã«ãªã¹ã (ãã¹ãŠ PowerShell ã«å®è£
)"
#: ../../rst/os_guide/windows_dsc.rst:505
#: ../../rst/os_guide/windows_faq.rst:254
#: ../../rst/os_guide/windows_setup.rst:496
#: ../../rst/os_guide/windows_usage.rst:516
#: ../../rst/os_guide/windows_winrm.rst:1010
msgid "`User Mailing List <https://groups.google.com/group/ansible-project>`_"
msgstr "`User Mailing List <https://groups.google.com/group/ansible-project>`_"
#: ../../rst/os_guide/windows_dsc.rst:506
#: ../../rst/os_guide/windows_faq.rst:255
#: ../../rst/os_guide/windows_setup.rst:497
#: ../../rst/os_guide/windows_usage.rst:517
#: ../../rst/os_guide/windows_winrm.rst:1011
msgid "Have a question? Stop by the google group!"
msgstr "ã質åã¯ããããŸãããGoogle Group ãã芧ãã ããã"
#: ../../rst/os_guide/windows_faq.rst:4
msgid "Windows Frequently Asked Questions"
msgstr "Windows ã«é¢ãããããã質å (FAQ)"
#: ../../rst/os_guide/windows_faq.rst:6
msgid "Here are some commonly asked questions in regards to Ansible and Windows and their answers."
msgstr "ããã§ã¯ãAnsible ããã³ Windows ã«é¢ãããããã質åãšãã®åçã玹ä»ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:9
msgid "This document covers questions about managing Microsoft Windows servers with Ansible. For questions about Ansible Core, please see the :ref:`general FAQ page <ansible_faq>`."
msgstr "æ¬ã¬ã€ãã§ã¯ãAnsible ã䜿çšãã Microsoft Windows ãµãŒããŒã®ç®¡çã«é¢ãã質åã«ã€ããŠèª¬æããŸããAnsible Core ã«é¢ãã質åã¯ãã:ref:`äžè¬ç㪠FAQ ããŒãž <ansible_faq>`ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:14
msgid "Does Ansible work with Windows XP or Server 2003?"
msgstr "Ansible ã¯ãWindows XP ãŸã㯠Server 2003 ã§åäœããŸãã"
#: ../../rst/os_guide/windows_faq.rst:15
msgid "Ansible does not work with Windows XP or Server 2003 hosts. Ansible does work with these Windows operating system versions:"
msgstr "Ansible ã¯ãWindows XP ãŸã㯠Server 2003 ãã¹ãã§ã¯åäœããŸãããAnsible ã¯ã以äžã® Windows ãªãã¬ãŒãã£ã³ã°ã·ã¹ãã ããŒãžã§ã³ã§åäœããŸãã"
#: ../../rst/os_guide/windows_faq.rst:17
msgid "Windows Server 2008 :sup:`1`"
msgstr "Windows Server 2008 :sup:`1`"
#: ../../rst/os_guide/windows_faq.rst:18
msgid "Windows Server 2008 R2 :sup:`1`"
msgstr "Windows Server 2008 R2 :sup:`1`"
#: ../../rst/os_guide/windows_faq.rst:19
msgid "Windows Server 2012"
msgstr "Windows Server 2012"
#: ../../rst/os_guide/windows_faq.rst:20
msgid "Windows Server 2012 R2"
msgstr "Windows Server 2012 R2"
#: ../../rst/os_guide/windows_faq.rst:21
msgid "Windows Server 2016"
msgstr "Windows Server 2016"
#: ../../rst/os_guide/windows_faq.rst:22
msgid "Windows Server 2019"
msgstr "Windows Server 2019"
#: ../../rst/os_guide/windows_faq.rst:23
msgid "Windows 7 :sup:`1`"
msgstr "Windows 7 :sup:`1`"
#: ../../rst/os_guide/windows_faq.rst:24
msgid "Windows 8.1"
msgstr "Windows 8.1"
#: ../../rst/os_guide/windows_faq.rst:25
msgid "Windows 10"
msgstr "Windows 10"
#: ../../rst/os_guide/windows_faq.rst:27
msgid "1 - See the :ref:`Server 2008 FAQ <windows_faq_server2008>` entry for more details."
msgstr "1 - 詳现ã¯ã:ref:`Server 2008 FAQ <windows_faq_server2008>` ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:29
msgid "Ansible also has minimum PowerShell version requirements - please see :ref:`windows_setup` for the latest information."
msgstr "ãŸããAnsible ã«ã¯ PowerShell ã®æå°ããŒãžã§ã³èŠä»¶ããããŸããææ°æ
å ±ã¯ã:ref:`windows_setup`ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:35
msgid "Are Server 2008, 2008 R2 and Windows 7 supported?"
msgstr "Server 2008ã2008 R2ãWindows 7 ã«å¯Ÿå¿ããŠããŸãã"
#: ../../rst/os_guide/windows_faq.rst:36
msgid "Microsoft ended Extended Support for these versions of Windows on January 14th, 2020, and Ansible deprecated official support in the 2.10 release. No new feature development will occur targeting these operating systems, and automated testing has ceased. However, existing modules and features will likely continue to work, and simple pull requests to resolve issues with these Windows versions may be accepted."
msgstr "Microsoft 㯠2020 幎 1 æ 14 æ¥ã«ãããã®ããŒãžã§ã³ã® Windows ã® Extended Support ãçµäºããAnsible 㯠2.10 ã®ãªãªãŒã¹ã§å
¬åŒãµããŒããçµäºããŸããããããã®ãªãã¬ãŒãã£ã³ã°ã·ã¹ãã ã察象ãšããæ°æ©èœã®éçºã¯ä»åŸè¡ããããèªåãã¹ããçµäºããŠããŸããããããæ¢åã®ã¢ãžã¥ãŒã«ãæ©èœã¯åŒãç¶ãåäœããå¯èœæ§ãããããããã® Windows ããŒãžã§ã³ã«é¢ããåé¡ã解決ããããã®ç°¡åãªãã«èŠæ±ã¯æ¿èªãããå¯èœæ§ããããŸãã"
#: ../../rst/os_guide/windows_faq.rst:39
msgid "Can I manage Windows Nano Server with Ansible?"
msgstr "Ansible 㧠Windows Nano Server ã管çã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:40
msgid "Ansible does not currently work with Windows Nano Server, since it does not have access to the full .NET Framework that is used by the majority of the modules and internal components."
msgstr "Ansible ã¯çŸåšãWindows Nano Server ã§ã¯åäœããŸãããããã¯ã倧éšåã®ã¢ãžã¥ãŒã«ãå
éšã³ã³ããŒãã³ãã§äœ¿çšãããŠããå®å
šãª .NET ãã¬ãŒã ã¯ãŒã¯ã«ã¢ã¯ã»ã¹ã§ããªãããã§ãã"
#: ../../rst/os_guide/windows_faq.rst:47
msgid "Can Ansible run on Windows?"
msgstr "Ansible 㯠Windows ã§å®è¡ã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:48
msgid "No, Ansible can only manage Windows hosts. Ansible cannot run on a Windows host natively, though it can run under the Windows Subsystem for Linux (WSL)."
msgstr "ããããAnsible 㯠Windows ãã¹ãã®ã¿ã管çã§ããŸããAnsible 㯠Windows ãã¹ãäžã§ã¯ãã€ãã£ãã«å®è¡ã§ããŸããããWindows Subsystem for Linux (WSL) ã®äžã§å®è¡ã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:51
msgid "The Windows Subsystem for Linux is not supported by Ansible and should not be used for production systems."
msgstr "Windows Subsystem for Linux 㯠Ansible ã§ã¯ãµããŒããããŠããªããããå®çšŒåã·ã¹ãã ã«ã¯äœ¿çšããªãã§ãã ããã"
#: ../../rst/os_guide/windows_faq.rst:54
msgid "To install Ansible on WSL, the following commands can be run in the bash terminal:"
msgstr "WSL ã« Ansible ãã€ã³ã¹ããŒã«ããã«ã¯ãbash ã¿ãŒããã«ã§ä»¥äžã®ã³ãã³ããå®è¡ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:63
msgid "To run Ansible from source instead of a release on the WSL, simply uninstall the pip installed version and then clone the git repo."
msgstr "WSL ã®ãªãªãŒã¹ã§ã¯ãªããœãŒã¹ãã Ansible ãå®è¡ããã«ã¯ãã€ã³ã¹ããŒã«ãã pip ãã¢ã³ã€ã³ã¹ããŒã«ããgit ãªããžããªãŒã®ã¯ããŒã³ãäœæããŸãã"
#: ../../rst/os_guide/windows_faq.rst:75
msgid "If you encounter timeout errors when running Ansible on the WSL, this may be due to an issue with ``sleep`` not returning correctly. The following workaround may resolve the issue:"
msgstr "WSL äžã§ Ansible ãå®è¡ãããšãã«ã¿ã€ã ã¢ãŠããšã©ãŒãçºçããå Žåã¯ã``sleep`` ãæ£ããè¿ãããªãåé¡ãåå ãšãªã£ãŠããå¯èœæ§ããããŸãã以äžã®åé¿çã«ããããã®åé¡ã解決ãããå ŽåããããŸãã"
#: ../../rst/os_guide/windows_faq.rst:83
msgid "Another option is to use WSL 2 if running Windows 10 later than build 2004."
msgstr "å¥ã®ãªãã·ã§ã³ãšããŠããã«ã 2004 ããã Windows 10 以äžãå®è¡ããŠããå Žå㯠WSL 2 ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_faq.rst:91
msgid "Can I use SSH keys to authenticate to Windows hosts?"
msgstr "SSH ããŒã䜿çšã㊠Windows ãã¹ããžã®èªèšŒãè¡ãããšã¯ã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:92
msgid "You cannot use SSH keys with the WinRM or PSRP connection plugins. These connection plugins use X509 certificates for authentication instead of the SSH key pairs that SSH uses."
msgstr "WinRM ãŸã㯠PSRP connection ãã©ã°ã€ã³ã§ SSH éµã䜿çšããããšã¯ã§ããŸããããããã® connection ãã©ã°ã€ã³ã¯ãèªèšŒã« SSH ã䜿çšãã SSH ããŒãã¢ã䜿çšãã代ããã«ãX509 蚌ææžã䜿çšããŸãã"
#: ../../rst/os_guide/windows_faq.rst:96
msgid "The way X509 certificates are generated and mapped to a user is different from the SSH implementation; consult the :ref:`windows_winrm` documentation for more information."
msgstr "X509 蚌ææžãçæããããŠãŒã¶ãŒã«ãããã³ã°ãããæ¹æ³ã¯ãSSH ã®å®è£
ãšã¯ç°ãªããŸãã詳现ã¯ã:ref:`windows_winrm` ã®ããã¥ã¡ã³ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:100
msgid "Ansible 2.8 has added an experimental option to use the SSH connection plugin, which uses SSH keys for authentication, for Windows servers. See :ref:`this question <windows_faq_ssh>` for more information."
msgstr "Ansible 2.8 ã«ã¯ãèªèšŒã« SSH éµã䜿çšãã SSH connection ãã©ã°ã€ã³ã Windows ãµãŒããŒã§äœ¿çšããå®éšçãªãªãã·ã§ã³ãè¿œå ãããŸããã詳现ã¯ã:ref:`this question <windows_faq_ssh>`ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:107
msgid "Why can I run a command locally that does not work under Ansible?"
msgstr "Ansible ã§æ©èœããªãã³ãã³ããããŒã«ã«ã§å®è¡ã§ããã®ã¯ãªãã§ãã"
#: ../../rst/os_guide/windows_faq.rst:108
msgid "Ansible executes commands through WinRM. These processes are different from running a command locally in these ways:"
msgstr "Ansible ã¯ãWinRM ãä»ããŠã³ãã³ããå®è¡ããŸãããããã®ããã»ã¹ã¯ã以äžã®æ¹æ³ã§ããŒã«ã«ã§ã³ãã³ããå®è¡ããã®ãšã¯ç°ãªããŸãã"
#: ../../rst/os_guide/windows_faq.rst:111
msgid "Unless using an authentication option like CredSSP or Kerberos with credential delegation, the WinRM process does not have the ability to delegate the user's credentials to a network resource, causing ``Access is Denied`` errors."
msgstr "CredSSP ã Kerberos ã®ãããªèªèšŒãªãã·ã§ã³ã䜿çšããŠãèªèšŒæ
å ±ã®å§è²ãè¡ã£ãŠããªãéããWinRM ããã»ã¹ã«ã¯ãŠãŒã¶ãŒã®èªèšŒæ
å ±ããããã¯ãŒã¯ãªãœãŒã¹ã«å§è²ããæ©èœããªãã``Access is Denied`` ãšã©ãŒãçºçããŸãã"
#: ../../rst/os_guide/windows_faq.rst:116
msgid "All processes run under WinRM are in a non-interactive session. Applications that require an interactive session will not work."
msgstr "WinRM ã§å®è¡ããããã¹ãŠã®ããã»ã¹ã¯ãé察話åã»ãã·ã§ã³ã§ãã察話åã»ãã·ã§ã³ãå¿
èŠãšããã¢ããªã±ãŒã·ã§ã³ã¯æ©èœããŸããã"
#: ../../rst/os_guide/windows_faq.rst:119
msgid "When running through WinRM, Windows restricts access to internal Windows APIs like the Windows Update API and DPAPI, which some installers and programs rely on."
msgstr "WinRM ãä»ããŠå®è¡ããå ŽåãWindows ã¯ãäžéšã®ã€ã³ã¹ããŒã©ãŒãããã°ã©ã ãäŸåããŠãã Windows Update API ã DPAPI ãªã©ã® Windows å
éš API ãžã®ã¢ã¯ã»ã¹ãå¶éããŸãã"
#: ../../rst/os_guide/windows_faq.rst:123
msgid "Some ways to bypass these restrictions are to:"
msgstr "ãããã®å¶éãåé¿ããæ¹æ³ã¯æ¬¡ã®ãšããã§ãã"
#: ../../rst/os_guide/windows_faq.rst:125
msgid "Use ``become``, which runs a command as it would when run locally. This will bypass most WinRM restrictions, as Windows is unaware the process is running under WinRM when ``become`` is used. See the :ref:`become` documentation for more information."
msgstr "``become`` ã䜿çšãããšãããŒã«ã«ã§å®è¡ãããšããšåãããã«ã³ãã³ããå®è¡ã§ããŸãã``become`` ã䜿çšãããšãWindows ã¯ããã»ã¹ã WinRM ã®äžã§å®è¡ããŠããããšã«æ°ã¥ããªããããã»ãšãã©ã® WinRM ã®å¶éãåé¿ããããšãã§ããŸãã詳现ã¯ã:ref:`become` ã®ããã¥ã¡ã³ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:130
msgid "Use a scheduled task, which can be created with ``win_scheduled_task``. Like ``become``, it will bypass all WinRM restrictions, but it can only be used to run commands, not modules."
msgstr "``win_scheduled_task`` ã§äœæã§ãããã¹ã±ãžã¥ãŒã«ãããã¿ã¹ã¯ã䜿çšããŸãã``become`` ãšåæ§ã«ãWinRM ã®å¶éããã¹ãŠåé¿ã§ããŸãããã¢ãžã¥ãŒã«ã§ã¯ãªãã³ãã³ãã®å®è¡ã«ã®ã¿äœ¿çšã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:134
msgid "Use ``win_psexec`` to run a command on the host. PSExec does not use WinRM and so will bypass any of the restrictions."
msgstr "``win_psexec`` ã䜿çšããŠãã¹ãã§ã³ãã³ããå®è¡ããŸããPSExec 㯠WinRM ã䜿çšããªããããããããå¶éãåé¿ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:137
msgid "To access network resources without any of these workarounds, you can use CredSSP or Kerberos with credential delegation enabled."
msgstr "ãããã®åé¿çãåããã«ãããã¯ãŒã¯ãªãœãŒã¹ã«ã¢ã¯ã»ã¹ããã«ã¯ãèªèšŒæ
å ±ã®å§è²ãæå¹ã«ãã CredSSP ãŸã㯠Kerberos ã䜿çšããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:140
msgid "See :ref:`become` more info on how to use become. The limitations section at :ref:`windows_winrm` has more details around WinRM limitations."
msgstr "become ã®äœ¿çšæ¹æ³ã«é¢ãã詳现ã¯ãã:ref:`become`ããåç
§ããŠãã ããã:ref:`windows_winrm` ã®å¶éã®ã»ã¯ã·ã§ã³ã«ã¯ãWinRM å¶éã®è©³çŽ°ãèšèŒãããŠããŸãã"
#: ../../rst/os_guide/windows_faq.rst:144
msgid "This program won't install on Windows with Ansible"
msgstr "ãã®ããã°ã©ã ããAnsible ãã€ã³ã¹ããŒã«ãããŠãã Windows ã«ã¯ã€ã³ã¹ããŒã«ãããŸãã"
#: ../../rst/os_guide/windows_faq.rst:145
msgid "See :ref:`this question <windows_faq_winrm>` for more information about WinRM limitations."
msgstr "WinRMã®å¶éã®è©³çŽ°ã¯ãã:ref:`ãã¡ãã®è³ªå <windows_faq_winrm>`ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:148
msgid "What Windows modules are available?"
msgstr "ã©ã®ãã㪠Windows ã¢ãžã¥ãŒã«ãå©çšã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:149
msgid "Most of the Ansible modules in Ansible Core are written for a combination of Linux/Unix machines and arbitrary web services. These modules are written in Python and most of them do not work on Windows."
msgstr "Ansible Core ã® Ansible ã¢ãžã¥ãŒã«ã®å€ãã¯ãLinux/Unix ãã·ã³ãšä»»æã® Web ãµãŒãã¹ã®çµã¿åãããæ³å®ããŠèšè¿°ãããŸãããããã®ã¢ãžã¥ãŒã«ã¯ Python ã§èšè¿°ãããŠããããã®ã»ãšãã©ã Windows ã§ã¯åäœããŸããã"
#: ../../rst/os_guide/windows_faq.rst:153
msgid "Because of this, there are dedicated Windows modules that are written in PowerShell and are meant to be run on Windows hosts. A list of these modules can be found :ref:`here <windows_modules>`."
msgstr "ãã®ãããPowerShell ã§èšè¿°ãããŠãããWindows ãã¹ãã§å®è¡ããããšãç®çãšããŠããå°çšã® Windows ã¢ãžã¥ãŒã«ããããŸãããããã®ã¢ãžã¥ãŒã«ã®äžèŠ§ã¯ãã:ref:`here <windows_modules>`ãã«ãããŸãã"
#: ../../rst/os_guide/windows_faq.rst:157
msgid "In addition, the following Ansible Core modules/action-plugins work with Windows:"
msgstr "次㮠Ansible Core ã¢ãžã¥ãŒã«ããã³ã¢ã¯ã·ã§ã³ãã©ã°ã€ã³ã¯ãWindows ã§åäœããŸãã"
#: ../../rst/os_guide/windows_faq.rst:159
msgid "add_host"
msgstr "add_host"
#: ../../rst/os_guide/windows_faq.rst:160
msgid "assert"
msgstr "assert"
#: ../../rst/os_guide/windows_faq.rst:161
msgid "async_status"
msgstr "async_status"
#: ../../rst/os_guide/windows_faq.rst:162
msgid "debug"
msgstr "debug"
#: ../../rst/os_guide/windows_faq.rst:163
msgid "fail"
msgstr "fail"
#: ../../rst/os_guide/windows_faq.rst:164
msgid "fetch"
msgstr "fetch"
#: ../../rst/os_guide/windows_faq.rst:165
msgid "group_by"
msgstr "group_by"
#: ../../rst/os_guide/windows_faq.rst:166
msgid "include"
msgstr "include"
#: ../../rst/os_guide/windows_faq.rst:167
msgid "include_role"
msgstr "include_role"
#: ../../rst/os_guide/windows_faq.rst:168
msgid "include_vars"
msgstr "include_vars"
#: ../../rst/os_guide/windows_faq.rst:169
msgid "meta"
msgstr "meta"
#: ../../rst/os_guide/windows_faq.rst:170
msgid "pause"
msgstr "pause"
#: ../../rst/os_guide/windows_faq.rst:171
msgid "raw"
msgstr "raw"
#: ../../rst/os_guide/windows_faq.rst:172
msgid "script"
msgstr "script"
#: ../../rst/os_guide/windows_faq.rst:173
msgid "set_fact"
msgstr "set_fact"
#: ../../rst/os_guide/windows_faq.rst:174
msgid "set_stats"
msgstr "set_stats"
#: ../../rst/os_guide/windows_faq.rst:175
msgid "setup"
msgstr "setup"
#: ../../rst/os_guide/windows_faq.rst:176
msgid "slurp"
msgstr "slurp"
#: ../../rst/os_guide/windows_faq.rst:177
msgid "template (also: win_template)"
msgstr "template (win_template ãåæ§)"
#: ../../rst/os_guide/windows_faq.rst:178
msgid "wait_for_connection"
msgstr "wait_for_connection"
#: ../../rst/os_guide/windows_faq.rst:180
msgid "Ansible Windows modules exist in the :ref:`plugins_in_ansible.windows`, :ref:`plugins_in_community.windows`, and :ref:`plugins_in_chocolatey.chocolatey` collections."
msgstr "Ansible Windows ã¢ãžã¥ãŒã«ã¯ã:ref:`plugins_in_ansible.windows`ã:ref:`plugins_in_community.windows`ãããã³ :ref:`plugins_in_chocolatey.chocolatey` ã³ã¬ã¯ã·ã§ã³ã«ååšããŸãã"
#: ../../rst/os_guide/windows_faq.rst:183
msgid "Can I run Python modules on Windows hosts?"
msgstr "Windows ãã¹ã㧠Python ã¢ãžã¥ãŒã«ãå®è¡ã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:184
msgid "No, the WinRM connection protocol is set to use PowerShell modules, so Python modules will not work. A way to bypass this issue to use ``delegate_to: localhost`` to run a Python module on the Ansible controller. This is useful if during a playbook, an external service needs to be contacted and there is no equivalent Windows module available."
msgstr "ã§ããŸãããWinRM æ¥ç¶ãããã³ã«ã¯ PowerShell ã¢ãžã¥ãŒã«ã䜿çšããããã«èšå®ãããŠãããããPython ã¢ãžã¥ãŒã«ã¯åäœããŸããããã®åé¡ãåé¿ããã«ã¯ã``delegate_to: localhost`` ã䜿çšã㊠Ansible ã³ã³ãããŒã©ãŒäžã§ Python ã¢ãžã¥ãŒã«ãå®è¡ããæ¹æ³ããããŸããããã¯ãPlaybook äžã«å€éšãµãŒãã¹ã«æ¥ç¶ããå¿
èŠããããåçã® Windows ã¢ãžã¥ãŒã«ããªãå Žåã«äŸ¿å©ã§ãã"
#: ../../rst/os_guide/windows_faq.rst:193
msgid "Can I connect to Windows hosts over SSH?"
msgstr "SSH çµç±ã§ Windows ãã¹ãã«æ¥ç¶ã§ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:194
msgid "Ansible 2.8 has added an experimental option to use the SSH connection plugin to manage Windows hosts. To connect to Windows hosts over SSH, you must install and configure the `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ fork that is in development with Microsoft on the Windows host(s). While most of the basics should work with SSH, ``Win32-OpenSSH`` is rapidly changing, with new features added and bugs fixed in every release. It is highly recommend you `install <https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH>`_ the latest release of ``Win32-OpenSSH`` from the GitHub Releases page when using it with Ansible on Windows hosts."
msgstr "Ansible 2.8 ã«ã¯ãSSH connection ãã©ã°ã€ã³ã䜿çšã㊠Windows ãã¹ãã管çããå®éšçãªãªãã·ã§ã³ãè¿œå ãããŸãããWindows ãã¹ãã« SSH æ¥ç¶ããã«ã¯ãMicrosoft ãšå
±åã§éçºäžã® `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ ãã©ãŒã¯ã Windows ãã¹ãã«ã€ã³ã¹ããŒã«ããŠèšå®ããå¿
èŠããããŸããåºæ¬çãªæ©èœã®ã»ãšãã©ã¯ SSH ã§åäœããã¯ãã§ããã``Win32-OpenSSH`` ã¯ãªãªãŒã¹ããšã«æ°æ©èœãè¿œå ããããããã°ãä¿®æ£ãããããšãæ¥éã«å€åããŠããŸããWindows ãã¹ã㧠Ansible ã䜿çšããéã«ã¯ãGitHub Releases ããŒãžãã ``Win32-OpenSSH`` ã®ææ°ãªãªãŒã¹ã `ã€ã³ã¹ããŒã« <https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH>`_ ããããšã匷ãæšå¥šãããŸãã"
#: ../../rst/os_guide/windows_faq.rst:203
msgid "To use SSH as the connection to a Windows host, set the following variables in the inventory:"
msgstr "Windows ãã¹ããžã®æ¥ç¶ã« SSH ã䜿çšããã«ã¯ãã€ã³ãã³ããªãŒã«ä»¥äžã®å€æ°ãèšå®ããŸãã"
#: ../../rst/os_guide/windows_faq.rst:214
msgid "The value for ``ansible_shell_type`` should either be ``cmd`` or ``powershell``. Use ``cmd`` if the ``DefaultShell`` has not been configured on the SSH service and ``powershell`` if that has been set as the ``DefaultShell``."
msgstr "``ansible_shell_type`` ã®å€ã¯ã``cmd`` ãŸã㯠``powershell`` ã®ããããã§ãªããã°ãªããŸãããSSH ãµãŒãã¹ã§ ``DefaultShell`` ãèšå®ãããŠããªãå Žå㯠``cmd`` ã䜿çšããŠã``DefaultShell`` ãšããŠèšå®ãããŠããå Žå㯠``powershell`` ã䜿çšããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:219
msgid "Why is connecting to a Windows host through SSH failing?"
msgstr "SSH ãä»ãã Windows ãã¹ããžã®æ¥ç¶ã«å€±æããã®ã¯ãªãã§ãã?"
#: ../../rst/os_guide/windows_faq.rst:220
msgid "Unless you are using ``Win32-OpenSSH`` as described above, you must connect to Windows hosts using :ref:`windows_winrm`. If your Ansible output indicates that SSH was used, either you did not set the connection vars properly or the host is not inheriting them correctly."
msgstr "äžèšã®ããã« ``Win32-OpenSSH`` ã䜿çšããŠããå Žåãé€ããWindows ãã¹ããžã®æ¥ç¶ã«ã¯ :ref:`windows_winrm` ã䜿çšããå¿
èŠããããŸããAnsible ã®åºå㧠SSH ã䜿çšããããšè¡šç€ºãããå Žåã¯ãæ¥ç¶ããŒãæ£ããèšå®ãããŠããªããããã¹ãã«æ£ããç¶æ¿ãããŠããŸããã"
#: ../../rst/os_guide/windows_faq.rst:224
msgid "Make sure ``ansible_connection: winrm`` is set in the inventory for the Windows host(s)."
msgstr "Windows ãã¹ãã®ã€ã³ãã³ããªãŒã« ``ansible_connection: winrm`` ãèšå®ãããŠããããšã確èªããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:228
msgid "Why are my credentials being rejected?"
msgstr "èªèšŒæ
å ±ãæåŠãããã®ã¯ãªãã§ãã"
#: ../../rst/os_guide/windows_faq.rst:229
msgid "This can be due to a myriad of reasons unrelated to incorrect credentials."
msgstr "ããã¯ã誀ã£ãèªèšŒæ
å ±ãšã¯ç¡é¢ä¿ã®ãå€çš®å€æ§ãªãã®ãåå ã§ããå¯èœæ§ããããŸãã"
#: ../../rst/os_guide/windows_faq.rst:231
msgid "See HTTP 401/Credentials Rejected at :ref:`windows_setup` for a more detailed guide of this could mean."
msgstr "ãã®çŸè±¡ã®è©³çŽ°ã«ã€ããŠã¯ã:ref:`windows_setup` ã®ãHTTP 401/èªèšŒæ
å ±ã®æåŠããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:235
msgid "Why am I getting an error SSL CERTIFICATE_VERIFY_FAILED?"
msgstr "SSL CERTIFICATE_VERIFY_FAILED ãšã©ãŒãçºçããã®ã¯ãªãã§ãã"
#: ../../rst/os_guide/windows_faq.rst:236
msgid "When the Ansible controller is running on Python 2.7.9+ or an older version of Python that has backported SSLContext (like Python 2.7.5 on RHEL 7), the controller will attempt to validate the certificate WinRM is using for an HTTPS connection. If the certificate cannot be validated (such as in the case of a self signed cert), it will fail the verification process."
msgstr "Ansible ã³ã³ãããŒã©ãŒã Python 2.7.9 以éãŸã㯠SSLContext ãããã¯ããŒãããå€ãããŒãžã§ã³ã® Python (RHEL 7 ã® Python 2.7.5 ãªã©) ã§åäœããŠããå Žåãã³ã³ãããŒã©ãŒã¯ WinRM ã HTTPS æ¥ç¶ã«äœ¿çšããŠãã蚌ææžãæ€èšŒããããšããŸãã蚌ææžãæ€èšŒã§ããªãå Žå (èªå·±çœ²å蚌ææžã®å Žåãªã©) ã¯ãæ€èšŒããã»ã¹ã«å€±æããŸãã"
#: ../../rst/os_guide/windows_faq.rst:242
msgid "To ignore certificate validation, add ``ansible_winrm_server_cert_validation: ignore`` to inventory for the Windows host."
msgstr "蚌ææžã®æ€èšŒãç¡èŠããã«ã¯ãWindows ãã¹ãã®ã€ã³ãã³ããªãŒã« ``ansible_winrm_server_cert_validation: ignore`` ãè¿œå ããŠãã ããã"
#: ../../rst/os_guide/windows_faq.rst:248
msgid ":ref:`windows`"
msgstr ":ref:`windows`"
#: ../../rst/os_guide/windows_faq.rst:249
msgid "The Windows documentation index"
msgstr "Windows ããã¥ã¡ã³ãã®ç®æ¬¡"
#: ../../rst/os_guide/windows_faq.rst:250
#: ../../rst/os_guide/windows_setup.rst:490
msgid ":ref:`about_playbooks`"
msgstr ":ref:`about_playbooks`"
#: ../../rst/os_guide/windows_performance.rst:4
msgid "Windows performance"
msgstr "Windows ããã©ãŒãã³ã¹"
#: ../../rst/os_guide/windows_performance.rst:5
msgid "This document offers some performance optimizations you might like to apply to your Windows hosts to speed them up specifically in the context of using Ansible with them, and generally."
msgstr "æ¬æžã§ã¯ãç¹ã« Ansible ããã®ãã¹ãã§äœ¿çšãããããªç¶æ³ãããã³äžè¬çã«äœ¿çšããç¶æ³ã§é«éåããããã«ãWindows ãã¹ãã«é©çšããããã©ãŒãã³ã¹ã®æé©åãããã€ã説æããŸãã"
#: ../../rst/os_guide/windows_performance.rst:10
msgid "Optimize PowerShell performance to reduce Ansible task overhead"
msgstr "Ansible ã¿ã¹ã¯ã®ãªãŒããŒãããã軜æžããããã® PowerShell ã®ããã©ãŒãã³ã¹ã®æé©å"
#: ../../rst/os_guide/windows_performance.rst:11
msgid "To speed up the startup of PowerShell by around 10x, run the following PowerShell snippet in an Administrator session. Expect it to take tens of seconds."
msgstr "PowerShell ã®èµ·åãçŽ 10 åé«éåããã«ã¯ãAdministrator ã»ãã·ã§ã³ã§ä»¥äžã® PowerShell ã¹ãããããå®è¡ããŸããæ°åç§ãããããšãäºæ³ãããŸãã"
#: ../../rst/os_guide/windows_performance.rst:17
msgid "If native images have already been created by the ngen task or service, you will observe no difference in performance (but this snippet will at that point execute faster than otherwise)."
msgstr "ãã€ãã£ãã€ã¡ãŒãžã ngen ã¿ã¹ã¯ããµãŒãã¹ã«ãã£ãŠãã§ã«äœæãããŠããå Žåã¯ãããã©ãŒãã³ã¹ã«éãã¯ãããŸãã (ãã ãããã®ã¹ããããã¯ãã®æç¹ã§ä»ã®å Žåãããé«éã«å®è¡ãããŸã)ã"
#: ../../rst/os_guide/windows_performance.rst:42
msgid "PowerShell is used by every Windows Ansible module. This optimization reduces the time PowerShell takes to start up, removing that overhead from every invocation."
msgstr "PowerShell ã¯ãã¹ãŠã® Windows Ansible ã¢ãžã¥ãŒã«ã«ãã£ãŠäœ¿çšãããŸãããã®æé©åã«ãããPowerShell ã®èµ·åæéãççž®ããåŒã³åºãããšã«ãã®ãªãŒããŒããããåãé€ããŸãã"
#: ../../rst/os_guide/windows_performance.rst:45
msgid "This snippet uses `the native image generator, ngen <https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator#WhenToUse>`_ to pre-emptively create native images for the assemblies that PowerShell relies on."
msgstr "ãã®ã¹ãããã㯠`ãã€ãã£ãã€ã¡ãŒãžãžã§ãã¬ãŒã¿ãŒ ngen <https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator#WhenToUse>`_ ã䜿çšããŠãPowerShell ãäŸåããŠããã¢ã»ã³ããªãŒã®ãã€ãã£ãã€ã¡ãŒãžãäºåã«äœæããŸãã"
#: ../../rst/os_guide/windows_performance.rst:49
msgid "Fix high-CPU-on-boot for VMs/cloud instances"
msgstr "ä»®æ³ãã·ã³/ã¯ã©ãŠãã€ã³ã¹ã¿ã³ã¹ã®ãã·ã¹ãã èµ·åæã®é« CPU ãä¿®æ£"
#: ../../rst/os_guide/windows_performance.rst:50
msgid "If you are creating golden images to spawn instances from, you can avoid a disruptive high CPU task near startup through `processing the ngen queue <https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator#native-image-service>`_ within your golden image creation, if you know the CPU types won't change between golden image build process and runtime."
msgstr "ã€ã³ã¹ã¿ã³ã¹ãçæããããã«ãŽãŒã«ãã³ã€ã¡ãŒãžãäœæããŠããå Žåã¯ããŽãŒã«ãã³ã€ã¡ãŒãžã®ãã«ãããã»ã¹ãšã©ã³ã¿ã€ã ã®é㧠CPU ã¿ã€ããå€ãããªãããšãããã£ãŠããã°ãäœæãããŽãŒã«ãã³ã€ã¡ãŒãžå
㧠`processing the ngen queue <https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator#native-image-service>`_ ãä»ããŠãèµ·åæã«ç Žå£ç㪠CPU 䜿çšçã®é«ãã¿ã¹ã¯ãåé¿ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_performance.rst:55
msgid "Place the following near the end of your playbook, bearing in mind the factors that can cause native images to be invalidated (`see MSDN <https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator#native-images-and-jit-compilation>`_)."
msgstr "Playbook ã®æåŸä»è¿ã«ä»¥äžã眮ãããã€ãã£ãã€ã¡ãŒãžãç¡å¹ã«ãªãå¯èœæ§ã®ããèŠçŽ ã«æ³šæããŠãã ãã (`MSDN <https://docs.microsoft.com/en-us/dotnet/framework/tools/ngen-exe-native-image-generator#native-images-and-jit-compilation>`_ ãåç
§)ã"
#: ../../rst/os_guide/windows_setup.rst:4
msgid "Setting up a Windows Host"
msgstr "Windows ãã¹ãã®ã»ããã¢ãã"
#: ../../rst/os_guide/windows_setup.rst:5
msgid "This document discusses the setup that is required before Ansible can communicate with a Microsoft Windows host."
msgstr "æ¬æžã§ã¯ãAnsible ã Microsoft Windows ãã¹ããšéä¿¡ããåã«å¿
èŠãªã»ããã¢ããã説æããŸãã"
#: ../../rst/os_guide/windows_setup.rst:12
msgid "For Ansible to communicate to a Windows host and use Windows modules, the Windows host must meet these base requirements for connectivity:"
msgstr "Ansible ã Windows ãã¹ããšéä¿¡ããWindows ã¢ãžã¥ãŒã«ã䜿çšããããã«ã¯ãWindows ãã¹ãã以äžã®æ¥ç¶æ§ã«é¢ããåºæ¬èŠä»¶ãæºããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:15
msgid "With Ansible you can generally manage Windows versions under the current and extended support from Microsoft. You can also manage desktop OSs including Windows 8.1, and 10, and server OSs including Windows Server 2012, 2012 R2, 2016, 2019, and 2022."
msgstr "Ansible ã¯ãMicrosoft ã®çŸè¡ããã³æ¡åŒµãµããŒãäžã«ãã Windows ããŒãžã§ã³ãäžè¬çã«ç®¡çã§ããŸãããŸããWindows 8.1ããã³ 10 ãå«ããã¹ã¯ããã OSããªãã³ã« Windows Server 2012ã2012 R2ã2016ã2019ãããã³ 2022 ãå«ããµãŒã㌠OS ã管çã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:17
msgid "You need to install PowerShell 3.0 or newer and at least .NET 4.0 on the Windows host."
msgstr "Windows ãã¹ãã« PowerShell 3.0 以éãšå°ãªããšã .NET 4.0 ãã€ã³ã¹ããŒã«ãããŠããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:19
msgid "You need to create and activate a WinRM listener. More details, see `WinRM Setup <https://docs.ansible.com/ansible/latest//user_guide/windows_setup.html#winrm-listener>`_."
msgstr "WinRM ãªã¹ããŒãäœæããŠã¢ã¯ãã£ãã«ããå¿
èŠããããŸãã詳现ã¯ã`WinRM Setup <https://docs.ansible.com/ansible/latest//user_guide/windows_setup.html#winrm-listener>`_ ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:21
msgid "Some Ansible modules have additional requirements, such as a newer OS or PowerShell version. Consult the module documentation page to determine whether a host meets those requirements."
msgstr "Ansible ã¢ãžã¥ãŒã«ã®äžã«ã¯ãæ°ãã OS ã PowerShell ã®ããŒãžã§ã³ãªã©ãè¿œå ã®èŠä»¶ããããã®ããããŸãããã¹ãããããã®èŠä»¶ãæºãããŠãããã©ããã¯ãã¢ãžã¥ãŒã«ã®ããã¥ã¡ã³ãããŒãžãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:24
msgid "Upgrading PowerShell and .NET Framework"
msgstr "PowerShell ããã³ .NET Framework ã®ã¢ããã°ã¬ãŒã"
#: ../../rst/os_guide/windows_setup.rst:25
msgid "Ansible requires PowerShell version 3.0 and .NET Framework 4.0 or newer to function on older operating systems like Server 2008 and Windows 7. The base image does not meet this requirement. You can use the `Upgrade-PowerShell.ps1 <https://github.com/jborean93/ansible-windows/blob/master/scripts/Upgrade-PowerShell.ps1>`_ script to update these."
msgstr "Ansible ã Server 2008 ã Windows 7 ãªã©ã®å€ããªãã¬ãŒãã£ã³ã°ã·ã¹ãã ã§æ©èœããããã«ã¯ãPowerShell ã® ããŒãžã§ã³3.0 ãš .NET Framework 4.0 以éãå¿
èŠã§ããããŒã¹ã€ã¡ãŒãžã¯ããã®èŠä»¶ãæºãããŠããŸããã`Upgrade-PowerShell.ps1 <https://github.com/jborean93/ansible-windows/blob/master/scripts/Upgrade-PowerShell.ps1>`_ ã¹ã¯ãªããã䜿çšããŠããããæŽæ°ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:28
msgid "This is an example of how to run this script from PowerShell:"
msgstr "ãã®ã¹ã¯ãªããã PowerShell ããå®è¡ããäŸã以äžã«ç€ºããŸãã"
#: ../../rst/os_guide/windows_setup.rst:43
msgid "In the script, the ``file`` value can be the PowerShell version 3.0, 4.0, or 5.1."
msgstr "ãã®ã¹ã¯ãªããã§ã¯ã``file`` ã®å€ã¯ PowerShell ããŒãžã§ã³ 3.0ã4.0ããŸã㯠5.1 ã«æå®ã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:45
msgid "Once completed, you need to run the following PowerShell commands:"
msgstr "å®äºãããã以äžã® PowerShell ã³ãã³ããå®è¡ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:47
msgid "As an optional but good security practice, you can set the execution policy back to the default."
msgstr "ãã¡ãã¯ä»»æã§ãããå®è¡ããªã·ãŒãããã©ã«ãã«æ»ãããšãã»ãã¥ãªãã£ãŒãã©ã¯ãã£ã¹ãšããŠé©åã§ãã"
#: ../../rst/os_guide/windows_setup.rst:53
msgid "Use the ``RemoteSigned`` value for Windows servers, or ``Restricted`` for Windows clients."
msgstr "Windows ãµãŒããŒã«ã¯ ``RemoteSigned`` ã®å€ã䜿çšããWindows ã¯ã©ã€ã¢ã³ãã«ã¯ ``Restricted`` ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_setup.rst:55
msgid "Remove the auto logon."
msgstr "èªåãã°ãªã³ãåé€ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:64
msgid "The script determines what programs you need to install (such as .NET Framework 4.5.2) and what PowerShell version needs to be present. If a reboot is needed and the ``username`` and ``password`` parameters are set, the script will automatically reboot the machine and then logon. If the ``username`` and ``password`` parameters are not set, the script will prompt the user to manually reboot and logon when required. When the user is next logged in, the script will continue where it left off and the process continues until no more actions are required."
msgstr "ãã®ã¹ã¯ãªããã¯ãã€ã³ã¹ããŒã«ãå¿
èŠãªããã°ã©ã (.NET Framework 4.5.2 ãªã©) ããå¿
èŠãª PowerShell ããŒãžã§ã³ã確èªããŠåäœããŸããåèµ·åãå¿
èŠã§ã``username`` ãã©ã¡ãŒã¿ãŒãš ``password`` ãã©ã¡ãŒã¿ãŒãèšå®ãããŠããå Žåã¯ãã¹ã¯ãªãããèªåçã«åèµ·åããåèµ·åãã埩垰ãããšãã«ãã°ãªã³ããŸãã``username`` ãã©ã¡ãŒã¿ãŒããã³ ``password`` ãã©ã¡ãŒã¿ãŒãèšå®ãããŠããªãå Žåã«ã¯ãã¹ã¯ãªããã¯å¿
èŠã«å¿ããŠãŠãŒã¶ãŒã«æåã§åèµ·åãšãã°ãªã³ãä¿ããŸãããŠãŒã¶ãŒã次ã«ãã°ã€ã³ãããšãã¹ã¯ãªããã¯ååã®ç¶ããå®è¡ããã¢ã¯ã·ã§ã³ãå¿
èŠãªããªããŸã§åŠçãç¶ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:67
msgid "If you run the script on Server 2008, then you need to install SP2. For Server 2008 R2 or Windows 7 you need SP1."
msgstr "Server 2008 ã§ã¹ã¯ãªãããå®è¡ããå Žåã¯ãSP2 ãã€ã³ã¹ããŒã«ããå¿
èŠããããŸããServer 2008 R2 ãŸã㯠Windows 7 ã®å Žå㯠SP1 ãå¿
èŠã§ãã"
#: ../../rst/os_guide/windows_setup.rst:69
msgid "On Windows Server 2008 you can install only PowerShell 3.0. A newer version will result in the script failure."
msgstr "Windows Server 2008 ã§ã¯ PowerShell 3.0 ããã€ã³ã¹ããŒã«ã§ããªããããããããæ°ããããŒãžã§ã³ãæå®ãããšã¹ã¯ãªããã倱æããŸãã"
#: ../../rst/os_guide/windows_setup.rst:71
msgid "The ``username`` and ``password`` parameters are stored in plain text in the registry. Run the cleanup commands after the script finishes to ensure no credentials are stored on the host."
msgstr "``username`` ãš ``password`` ã®ãã©ã¡ãŒã¿ãŒã¯ãã¬ãžã¹ããªãŒã«å¹³æã§ä¿åãããŸããã¹ã¯ãªããã®çµäºåŸã«ã¯ãªãŒã³ã¢ããã³ãã³ããå®è¡ããŠããã¹ãäžã«èªèšŒæ
å ±ãä¿åãããŠããªãããšã確èªããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:75
msgid "WinRM Memory Hotfix"
msgstr "WinRM Memory Hotfix"
#: ../../rst/os_guide/windows_setup.rst:76
msgid "On PowerShell v3.0, there is a bug that limits the amount of memory available to the WinRM service. Use the `Install-WMF3Hotfix.ps1 <https://github.com/jborean93/ansible-windows/blob/master/scripts/Install-WMF3Hotfix.ps1>`_ script to install a hotfix on affected hosts as part of the system bootstrapping or imaging process. Without this hotfix, Ansible fails to execute certain commands on the Windows host."
msgstr "PowerShell v3.0 ã§å®è¡ããå Žåã¯ãWinRM ãµãŒãã¹ã®ãã°ã«ãããWinRM ã§äœ¿çšã§ããã¡ã¢ãªãŒéãå¶éããããšããåé¡ããããŸããã`Install-WMF3Hotfix.ps1 <https://github.com/jborean93/ansible-windows/blob/master/scripts/Install-WMF3Hotfix.ps1>`_ ãšããã¹ã¯ãªããã䜿çšãããšãã·ã¹ãã ã®ããŒãã¹ãã©ãããŸãã¯ã€ã¡ãŒãžããã»ã¹ã®äžéšãšããŠã圱é¿ãåãããã¹ãã« hotfix ãã€ã³ã¹ããŒã«ã§ããŸãããã® hotfix ããªãå Žåã«ã¯ãAnsible ã§ã¯ Windows ãã¹ãäžã§ç¹å®ã®ã³ãã³ãã®å®è¡ã«å€±æããŸãã"
#: ../../rst/os_guide/windows_setup.rst:78
msgid "To install the hotfix:"
msgstr "ããããã£ãã¯ã¹ãã€ã³ã¹ããŒã«ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:89
msgid "For more details, refer to the `\"Out of memory\" error on a computer that has a customized MaxMemoryPerShellMB quota set and has WMF 3.0 installed <https://support.microsoft.com/en-us/help/2842230/out-of-memory-error-on-a-computer-that-has-a-customized-maxmemorypersh>`_ article."
msgstr "詳现ã¯ã`\"Out of memory\" error on a computer that has a customized MaxMemoryPerShellMB quota set and has WMF 3.0 installed <https://support.microsoft.com/en-us/help/2842230/out-of-memory-error-on-a-computer-that-has-a-customized-maxmemorypersh>`_ ã¢ãŒãã£ã¯ã«ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:92
msgid "WinRM Setup"
msgstr "WinRM ã®èšå®"
#: ../../rst/os_guide/windows_setup.rst:93
msgid "You need to configure the WinRM service so that Ansible can connect to it. There are two main components of the WinRM service that governs how Ansible can interface with the Windows host: the ``listener`` and the ``service`` configuration settings."
msgstr "WinRM ãµãŒãã¹ãèšå®ã㊠Ansible ãæ¥ç¶ã§ããããã«ããŸããWinRM ãµãŒãã¹ã«ã¯ãæ§æèšå® ``listener`` ããã³ ``service`` ã® 2 ã€ã®äž»èŠã³ã³ããŒãã³ãããããAnsible ã Windows ãã¹ããšã©ã®ããã«é£æºãããã決å®ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:96
msgid "WinRM Listener"
msgstr "WinRM ãªã¹ããŒ"
#: ../../rst/os_guide/windows_setup.rst:97
msgid "The WinRM services listen for requests on one or more ports. Each of these ports must have a listener created and configured."
msgstr "WinRM ãµãŒãã¹ã¯ã1 ã€ä»¥äžã®ããŒãã§èŠæ±ããªãã¹ã³ããŸãããããã®ããŒãããšã«ãªã¹ããŒãäœæããèšå®ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:99
msgid "To view the current listeners that are running on the WinRM service:"
msgstr "WinRM ãµãŒãã¹ã§å®è¡ããŠããçŸåšã®ãªã¹ããŒã衚瀺ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:105
#: ../../rst/os_guide/windows_setup.rst:200
msgid "This will output something like:"
msgstr "ããã«ããã以äžã®ãããªãã®ãåºåãããŸãã"
#: ../../rst/os_guide/windows_setup.rst:131
msgid "In the example above there are two listeners activated. One is listening on port 5985 over HTTP and the other is listening on port 5986 over HTTPS. Some of the key options that are useful to understand are:"
msgstr "äžã®äŸã§ã¯ã2 ã€ã®ãªã¹ããŒãæå¹ã«ãªã£ãŠããŸãã1 ã€ã¯ HTTP ã§ããŒã 5985 ããªãã¹ã³ããŠããããã 1 ã€ã¯ HTTPS ã§ããŒã 5986 ããªãã¹ã³ããŠããŸããç解ããŠãããšäŸ¿å©ãªãªãã·ã§ã³ãããã€ã玹ä»ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:133
msgid "``Transport``: Whether the listener is run over HTTP or HTTPS. We recommend you use a listener over HTTPS because the data is encrypted without any further changes required."
msgstr "``Transport``: ãªã¹ããŒã HTTP ãŸã㯠HTTPS ã®ã©ã¡ãã§å®è¡ããŠããå Žåã§ããããŒã¿ã¯ãããªãå€æŽãªãã«æå·åããããããHTTPS çµç±ã§ãªã¹ããŒã䜿çšããããšãæšå¥šãããŸãã"
#: ../../rst/os_guide/windows_setup.rst:135
msgid "``Port``: The port the listener runs on. By default it is ``5985`` for HTTP and ``5986`` for HTTPS. This port can be changed to whatever is required and corresponds to the host var ``ansible_port``."
msgstr "``Port``: ãªã¹ããŒãå®è¡ããããŒããããã©ã«ãã¯ãHTTP ã®å Žå㯠``5985``ãHTTPS ã®å Žå㯠``5986`` ã§ãããã®ããŒãã¯ãå¿
èŠãªãã®ã«ããããå€æŽã§ãããã¹ãå€æ° ``ansible_port`` ã«å¯Ÿå¿ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:137
msgid "``URLPrefix``: The URL prefix to listen on. By default it is ``wsman``. If you change this option, you need to set the host var ``ansible_winrm_path`` to the same value."
msgstr "``URLPrefix``: ãªãã¹ã³ãã URL ãã¬ãã£ãã¯ã¹ãããã©ã«ã㯠``wsman`` ã§ãããã®ãªãã·ã§ã³ãå€æŽãããå Žåããã¹ãå€æ° ``ansible_winrm_path`` ã¯åãå€ã«èšå®ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:139
msgid "``CertificateThumbprint``: If you use an HTTPS listener, this is the thumbprint of the certificate in the Windows Certificate Store that is used in the connection. To get the details of the certificate itself, run this command with the relevant certificate thumbprint in PowerShell:"
msgstr "``CertificateThumbprint``: HTTPS ãªã¹ããŒã䜿çšããå Žåãããã¯æ¥ç¶ã«äœ¿çšããã Windows 蚌ææžã¹ãã¢ã®èšŒææžã®ãµã ããªã³ãã§ãã蚌ææžèªäœã®è©³çŽ°ãååŸããã«ã¯ãPowerShell ã§è©²åœãã蚌ææžã®ãµã ããªã³ããæå®ããŠæ¬¡ã®ã³ãã³ããå®è¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:147
msgid "Setup WinRM Listener"
msgstr "WinRM ãªã¹ããŒã®èšå®"
#: ../../rst/os_guide/windows_setup.rst:148
msgid "There are three ways to set up a WinRM listener:"
msgstr "WinRM ãªã¹ããŒãèšå®ããã«ã¯ã3 ã€ã®æ¹æ³ããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:150
msgid "Using ``winrm quickconfig`` for HTTP or ``winrm quickconfig -transport:https`` for HTTPS. This is the easiest option to use when running outside of a domain environment and a simple listener is required. Unlike the other options, this process also has the added benefit of opening up the firewall for the ports required and starts the WinRM service."
msgstr "HTTP ã«ã¯ ``winrm quickconfig`` ããHTTPS ã«ã¯ ``winrm quickconfig -transport:https`` ã䜿çšããŸããããã¯ããã¡ã€ã³ç°å¢å€ã§åäœããã·ã³ãã«ãªãªã¹ããŒãå¿
èŠãªå Žåã«ãæãç°¡åã«äœ¿çšã§ãããªãã·ã§ã³ã§ããä»ã®ãªãã·ã§ã³ãšã¯ç°ãªãããã®ããã»ã¹ã«ã¯ãå¿
èŠãªããŒãã®ããã«ãã¡ã€ã¢ãŠã©ãŒã«ãéããWinRM ãµãŒãã¹ãéå§ãããšããå©ç¹ããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:152
msgid "Using Group Policy Objects (GPO). This is the best way to create a listener when the host is a member of a domain because the configuration is done automatically without any user input. For more information on group policy objects, see the `Group Policy Objects documentation <https://msdn.microsoft.com/en-us/library/aa374162(v=vs.85).aspx>`_."
msgstr "ã°ã«ãŒãããªã·ãŒãªããžã§ã¯ã (GPO) ã®äœ¿çšãèšå®ã¯ããŠãŒã¶ãŒãå
¥åããã«èªåçã«è¡ãããããããã®æ¹æ³ã¯ããã¹ãããã¡ã€ã³ã®ã¡ã³ããŒã§ããå Žåã«ãªã¹ããŒãäœæããã®ã«æé©ãªæ¹æ³ã§ããã°ã«ãŒãããªã·ãŒãªããžã§ã¯ãã®è©³çŽ°ã¯ã`Group Policy Objects documentation <https://msdn.microsoft.com/en-us/library/aa374162(v=vs.85).aspx>`_ ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:154
msgid "Using PowerShell to create a listener with a specific configuration. This can be done by running the following PowerShell commands:"
msgstr "PowerShell ã䜿çšããŠãç¹å®ã®èšå®ã§ãªã¹ããŒãäœæããŸããããã¯ã以äžã® PowerShell ã³ãã³ããå®è¡ããããšã§å¯èœã«ãªããŸãã"
#: ../../rst/os_guide/windows_setup.rst:168
msgid "To see the other options with this PowerShell command, refer to the `New-WSManInstance <https://docs.microsoft.com/en-us/powershell/module/microsoft.wsman.management/new-wsmaninstance?view=powershell-5.1>`_ documentation."
msgstr "ãã® PowerShell ã³ãã³ãã®ä»ã®ãªãã·ã§ã³ã確èªããã«ã¯ã`New-WSManInstance <https://docs.microsoft.com/en-us/powershell/module/microsoft.wsman.management/new-wsmaninstance?view=powershell-5.1>`_ ããã¥ã¡ã³ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:171
msgid "When creating an HTTPS listener, you must create and store a certificate in the ``LocalMachine\\My`` certificate store."
msgstr "HTTPS ãªã¹ããŒãäœæãããšãã¯ã``LocalMachine\\My`` 蚌ææžã¹ãã¢ã«èšŒææžãäœæããŠä¿åããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:174
msgid "Delete WinRM Listener"
msgstr "WinRM ãªã¹ããŒã®åé€"
#: ../../rst/os_guide/windows_setup.rst:175
msgid "To remove all WinRM listeners:"
msgstr "WinRM ãªã¹ããŒãåé€ããã«ã¯ã以äžãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:181
msgid "To remove only those listeners that run over HTTPS:"
msgstr "HTTPS ã§å®è¡ããããªã¹ããŒã®ã¿ãåé€ããã«ã¯ã以äžãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:187
msgid "The ``Keys`` object is an array of strings, so it can contain different values. By default, it contains a key for ``Transport=`` and ``Address=`` which correspond to the values from the ``winrm enumerate winrm/config/Listeners`` command."
msgstr "``Keys`` ãªããžã§ã¯ãã¯æååã®é
åã§ãããããç°ãªãå€ãå«ãããšãã§ããŸããããã©ã«ãã§ã¯ã ``winrm enumerate winrm/config/Listeners`` ã³ãã³ãããã®ã®å€ã«å¯Ÿå¿ãã ``Transport=`` ããã³ ``Address=`` ã®ããŒãå«ãã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:190
msgid "WinRM Service Options"
msgstr "WinRM ãµãŒãã¹ãªãã·ã§ã³"
#: ../../rst/os_guide/windows_setup.rst:191
msgid "You can control the behavior of the WinRM service component, including authentication options and memory settings."
msgstr "èªèšŒãªãã·ã§ã³ãã¡ã¢ãªãŒèšå®ãªã©ãWinRM ãµãŒãã¹ã³ã³ããŒãã³ãã®åäœãå¶åŸ¡ã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:193
msgid "To get an output of the current service configuration options, run the following command:"
msgstr "çŸåšã®ãµãŒãã¹èšå®ãªãã·ã§ã³ã®åºåãåŸãã«ã¯ã次ã®ã³ãã³ããå®è¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:238
msgid "You do not need to change the majority of these options. However, some of the important ones to know about are:"
msgstr "ãããã®ãªãã·ã§ã³ã®å€§éšåãå€æŽããå¿
èŠã¯ãããŸããããç¥ã£ãŠããã¹ãéèŠãªãªãã·ã§ã³ã¯æ¬¡ã®ãšããã§ãã"
#: ../../rst/os_guide/windows_setup.rst:240
msgid "``Service\\AllowUnencrypted`` - specifies whether WinRM will allow HTTP traffic without message encryption. Message level encryption is only possible when the ``ansible_winrm_transport`` variable is ``ntlm``, ``kerberos`` or ``credssp``. By default, this is ``false`` and you should only set it to ``true`` when debugging WinRM messages."
msgstr "``Service\\AllowUnencrypted``: ã¡ãã»ãŒãžãæå·åããã« HTTP ãã©ãã£ãã¯ã WinRM ã§èš±å¯ãããã©ãããå®çŸ©ããŸããã¡ãã»ãŒãžã¬ãã«ã®æå·åã¯ã``ansible_winrm_transport`` å€æ°ã ``ntlm``ã``kerberos``ããŸã㯠``credssp`` ã®å Žåã«ã®ã¿å¯èœã§ããããã©ã«ãã§ã¯ããã㯠``false`` ã§ãããWinRM ã¡ãã»ãŒãžããããã°ããå Žåã«éã ``true`` ã«èšå®ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:242
msgid "``Service\\Auth\\*`` - defines what authentication options you can use with the WinRM service. By default, ``Negotiate (NTLM)`` and ``Kerberos`` are enabled."
msgstr "``Service\\Auth\\*``: WinRM ãµãŒãã¹ã§äœ¿çšå¯èœãªèªèšŒãªãã·ã§ã³ãå®çŸ©ããŸããããã©ã«ãã§ã¯ã``Negotiate (NTLM)`` ããã³ ``Kerberos`` ãæå¹ã«ãªããŸãã"
#: ../../rst/os_guide/windows_setup.rst:244
msgid "``Service\\Auth\\CbtHardeningLevel`` - specifies whether channel binding tokens are not verified (None), verified but not required (Relaxed), or verified and required (Strict). CBT is only used when connecting with NT LAN Manager (NTLM) or Kerberos over HTTPS."
msgstr "``Service\\Auth\\CbtHardeningLevel``: ãã£ã³ãã«ãã€ã³ãã£ã³ã°ããŒã¯ã³ãæ€èšŒããªã (None)ãæ€èšŒæžã¿ã ãå¿
èŠãªã (Relaxed)ãæ€èšŒæžã¿ã§å¿
èŠ (Strict) ã®ãããããæå®ããŸããCBT ã¯ãHTTPS ã® NT LAN Manager (NTLM) ãŸã㯠Kerberos ã§ã®æ¥ç¶æã«ã®ã¿äœ¿çšãããŸãã"
#: ../../rst/os_guide/windows_setup.rst:246
msgid "``Service\\CertificateThumbprint`` - thumbprint of the certificate for encrypting the TLS channel used with CredSSP authentication. By default, this is empty. A self-signed certificate is generated when the WinRM service starts and is used in the TLS process."
msgstr "``Service\\CertificateThumbprint``: CredSSP èªèšŒã§äœ¿çšããã TLS ãã£ã³ãã«ã®æå·åã«äœ¿çšããã蚌ææžã®ãµã ããªã³ãã§ããããã©ã«ãã§ã¯ãããã¯ç©ºã§ããèªå·±çœ²å蚌ææžã¯ãWinRM ãµãŒãã¹ã®èµ·åæã«çæãããTLS ããã»ã¹ã§äœ¿çšãããŸãã"
#: ../../rst/os_guide/windows_setup.rst:248
msgid "``Winrs\\MaxShellRunTime`` - maximum time, in milliseconds, that a remote command is allowed to execute."
msgstr "``Winrs\\MaxShellRunTime``: ãªã¢ãŒãã³ãã³ãã®å®è¡ãèš±å¯ããæ倧æéãããªç§åäœã§æå®ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:250
msgid "``Winrs\\MaxMemoryPerShellMB`` - maximum amount of memory allocated per shell, including its child processes."
msgstr "``Winrs\\MaxMemoryPerShellMB``: ã·ã§ã«ã®åããã»ã¹ãªã©ãã·ã§ã«ããšã«å²ãåœãŠãããã¡ã¢ãªãŒã®æ倧éã§ãã"
#: ../../rst/os_guide/windows_setup.rst:252
msgid "To modify a setting under the ``Service`` key in PowerShell, you need to provide a path to the option after ``winrm/config/Service``:"
msgstr "PowerShell ã® ``Service`` ããŒã§èšå®ãå€æŽããã«ã¯ã``winrm/config/Service`` ã®åŸã« ãªãã·ã§ã³ãžã®ãã¹ãæå®ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:258
msgid "For example, to change ``Service\\Auth\\CbtHardeningLevel``:"
msgstr "ããšãã°ã``Service\\Auth\\CbtHardeningLevel`` ãå€æŽããã«ã¯ä»¥äžãè¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:264
msgid "To modify a setting under the ``Winrs`` key in PowerShell, you need to provide a path to the option after ``winrm/config/Winrs``:"
msgstr "PowerShell ã® ``Winrs`` ããŒã§èšå®ãå€æŽããã«ã¯ã``winrm/config/Winrs`` ã®åŸã« ãªãã·ã§ã³ãžã®ãã¹ãæå®ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:270
msgid "For example, to change ``Winrs\\MaxShellRunTime``:"
msgstr "ããšãã°ã``Winrs\\MaxShellRunTime`` ãå€æŽããã«ã¯ã以äžãè¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:276
msgid "If you run the command in a domain environment, some of these options are set by GPO and cannot be changed on the host itself. When you configured a key with GPO, it contains the text ``[Source=\"GPO\"]`` next to the value."
msgstr "ãã¡ã€ã³ç°å¢ã§åäœããŠããå Žåã«ã¯ããããã®ãªãã·ã§ã³ã®äžéšã¯ GPO ã«ãã£ãŠèšå®ããããã¹ãèªäœã§ã¯å€æŽã§ããŸãããGPO ã§èšå®ãããããŒã«ã¯ãå€ã®æšªã« ``[Source=\"GPO\"]`` ãšããããã¹ãã衚瀺ãããŸãã"
#: ../../rst/os_guide/windows_setup.rst:280
msgid "Common WinRM Issues"
msgstr "äžè¬ç㪠WinRM ã®åé¡"
#: ../../rst/os_guide/windows_setup.rst:281
msgid "WinRM has a wide range of configuration options, which makes its configuration complex. As a result, errors that Ansible displays could in fact be problems with the host setup instead."
msgstr "WinRM ã«ã¯ããŸããŸãªèšå®ãªãã·ã§ã³ãããããã®èšå®ãè€éã«ãªãã®ã§ãAnsible ã衚瀺ãããšã©ãŒã¯ãå®éã«ã¯ãã¹ãã®èšå®ã«åé¡ãããå¯èœæ§ããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:283
msgid "To identify a host issue, run the following command from another Windows host to connect to the target Windows host."
msgstr "åé¡ããã¹ãã®åé¡ã§ãããã©ãããå€æããç°¡åãªæ¹æ³ãšããŠãå¥ã® Windows ãã¹ããã次ã®ã³ãã³ããå®è¡ããŠã察象㮠Windows ãã¹ãã«æ¥ç¶ããæ¹æ³ããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:285
msgid "To test HTTP:"
msgstr "HTTP ããã¹ãããã«ã¯ã以äžãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:291
msgid "To test HTTPS:"
msgstr "HTTPS ããã¹ãããã«ã¯ã以äžãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:297
msgid "The command will fail if the certificate is not verifiable."
msgstr "蚌ææžãæ€èšŒã§ããªãå Žåãã³ãã³ãã¯å€±æããŸãã"
#: ../../rst/os_guide/windows_setup.rst:299
msgid "To test HTTPS ignoring certificate verification:"
msgstr "蚌ææžã®æ€èšŒãç¡èŠãã HTTPS ããã¹ãããã«ã¯ã以äžãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:310
msgid "If any of the above commands fail, the issue is probably related to the WinRM setup."
msgstr "äžèšã®ã³ãã³ãã®ããããã倱æããå Žåã«ã¯ãåé¡ã¯ WinRM èšå®ã«é¢é£ããŠããå¯èœæ§ããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:313
msgid "HTTP 401/Credentials Rejected"
msgstr "HTTP 401/èªèšŒæ
å ±ã®æåŠ"
#: ../../rst/os_guide/windows_setup.rst:314
msgid "An HTTP 401 error indicates the authentication process failed during the initial connection. You can check the following to troubleshoot:"
msgstr "HTTP 401 ãšã©ãŒã¯ãæåã®æ¥ç¶æã«èªèšŒããã»ã¹ã倱æããããšã瀺ããŸãã以äžã®é
ç®ã確èªããŠããã©ãã«ã·ã¥ãŒãã£ã³ã°ã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:317
msgid "The credentials are correct and set properly in your inventory with the ``ansible_user`` and ``ansible_password`` variables."
msgstr "``ansible_user`` ããã³ ``ansible_password`` å€æ°ã䜿çšããŠãèªèšŒæ
å ±ãæ£ãããã€ã³ãã³ããªãŒã«é©åã«èšå®ãããŠããã"
#: ../../rst/os_guide/windows_setup.rst:319
msgid "The user is a member of the local Administrators group, or has been explicitly granted access. You can perform a connection test with the ``winrs`` command to rule this out."
msgstr "ãŠãŒã¶ãŒãããŒã«ã«ã® Administrators ã°ã«ãŒãã®ã¡ã³ããŒã§ããããæ瀺çã«ã¢ã¯ã»ã¹ãèš±å¯ãããŠãããããã¯ã``winrs`` ã³ãã³ãã«ããæ¥ç¶ãã¹ãã§é€å€ã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:321
msgid "The authentication option set by the ``ansible_winrm_transport`` variable is enabled under ``Service\\Auth\\*``."
msgstr "``ansible_winrm_transport`` ã§èšå®ããèªèšŒãªãã·ã§ã³ãã``Service\\Auth\\*`` ã§æå¹ã«ãªã£ãŠããã"
#: ../../rst/os_guide/windows_setup.rst:323
msgid "If running over HTTP and not HTTPS, use ``ntlm``, ``kerberos`` or ``credssp`` with the ``ansible_winrm_message_encryption: auto`` custom inventory variable to enable message encryption. If you use another authentication option, or if it is not possible to upgrade the installed ``pywinrm`` package, you can set ``Service\\AllowUnencrypted`` to ``true``. This is recommended only for troubleshooting."
msgstr "HTTPS ã§ã¯ãªã HTTP ã§å®è¡ããå Žåã¯ã``ntlm``ã``kerberos``ããŸã㯠``credssp`` ã䜿çšããŠã¡ãã»ãŒãžã®æå·åãæå¹ã«ããŸããå¥ã®èªèšŒãªãã·ã§ã³ã䜿çšããå ŽåããŸãã¯ã€ã³ã¹ããŒã«ããã ``pywinrm`` ããã±ãŒãžãã¢ããã°ã¬ãŒãã§ããªãå Žåã«ã¯ã``Service\\AllowUnencrypted`` ã ``true`` ã«èšå®ã§ããŸããããã¯ããã©ãã«ã·ã¥ãŒãã£ã³ã°ã®ç®çã§ã®ã¿æšå¥šãããŸãã"
#: ../../rst/os_guide/windows_setup.rst:325
msgid "The downstream packages ``pywinrm``, ``requests-ntlm``, ``requests-kerberos``, and/or ``requests-credssp`` are up to date using ``pip``."
msgstr "ããŠã³ã¹ããªãŒã ããã±ãŒãžã§ãã ``pywinrm``ã``requests-ntlm``ã``requests-kerberos``ããŸã㯠``requests-credssp``ããããã¯ãã®çµã¿åããã ``pip`` ã䜿çšããŠææ°ã®ç¶æ
ã«ãªã£ãŠããã"
#: ../../rst/os_guide/windows_setup.rst:327
msgid "For Kerberos authentication, ensure that ``Service\\Auth\\CbtHardeningLevel`` is not set to ``Strict``."
msgstr "Kerberos èªèšŒã䜿çšããå Žåã¯ã``Service\\Auth\\CbtHardeningLevel`` ã ``Strict`` ã«èšå®ãããŠããªãããšã確èªããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:329
msgid "For Basic or Certificate authentication, make sure that the user is a local account. Domain accounts do not work with Basic and Certificate authentication."
msgstr "Basic èªèšŒã Certificate èªèšŒã䜿çšããå Žåã¯ãããŒã«ã«ã¢ã«ãŠã³ãã§ããããšã確èªããŠãã ããããã¡ã€ã³ã¢ã«ãŠã³ãã¯ãBasic èªèšŒã Certificate èªèšŒã§ã¯æ©èœããŸããã"
#: ../../rst/os_guide/windows_setup.rst:332
msgid "HTTP 500 Error"
msgstr "HTTP 500 Error"
#: ../../rst/os_guide/windows_setup.rst:333
msgid "An HTTP 500 error indicates a problem with the WinRM service. You can check the following to troubleshoot:"
msgstr "HTTP 500 ãšã©ãŒã¯ãWinRM ãµãŒãã¹ã«åé¡ãããããšã瀺ããŸãã以äžã確èªããŠãã©ãã«ã·ã¥ãŒãã£ã³ã°ãè¡ãããšãã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:335
msgid "The number of your currently open shells has not exceeded either ``WinRsMaxShellsPerUser``. Alternatively, you did not exceed any of the other Winrs quotas."
msgstr "çŸåšéããŠããã·ã§ã«ã®æ°ã ``WinRsMaxShellsPerUser`` ãè¶
ããŠããªãããä»ã® Winrs ã¯ã©ãŒã¿ãè¶
ããŠããŸããã"
#: ../../rst/os_guide/windows_setup.rst:338
msgid "Timeout Errors"
msgstr "ã¿ã€ã ã¢ãŠããšã©ãŒ"
#: ../../rst/os_guide/windows_setup.rst:339
msgid "Sometimes Ansible is unable to reach the host. These instances usually indicate a problem with the network connection. You can check the following to troubleshoot:"
msgstr "Ansible ããã¹ãã«å°éã§ããªãããšããããŸãããããã®ã€ã³ã¹ã¿ã³ã¹ã¯éåžžããããã¯ãŒã¯æ¥ç¶ã«åé¡ãããããšã瀺ããŸãã以äžã確èªããŠãã©ãã«ã·ã¥ãŒãã£ã³ã°ãè¡ãããšãã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:341
msgid "The firewall is not set to block the configured WinRM listener ports."
msgstr "ãã¡ã€ã¢ãŠã©ãŒã«ããèšå®ããã WinRM ãªã¹ããŒããŒãããããã¯ããããã«èšå®ãããŠããªãã"
#: ../../rst/os_guide/windows_setup.rst:342
msgid "A WinRM listener is enabled on the port and path set by the host vars."
msgstr "WinRM ãªã¹ããŒãããã¹ãå€æ°ã«ãã£ãŠèšå®ãããããŒãããã³ãã¹ã§æå¹ã«ãªã£ãŠããã"
#: ../../rst/os_guide/windows_setup.rst:343
msgid "The ``winrm`` service is running on the Windows host and is configured for the automatic start."
msgstr "Windows ãã¹ãäžã§ ``winrm`` ãµãŒãã¹ã皌åããŠãããèªåèµ·åããããã«èšå®ãããŠããã"
#: ../../rst/os_guide/windows_setup.rst:346
msgid "Connection Refused Errors"
msgstr "æ¥ç¶æåŠãšã©ãŒ"
#: ../../rst/os_guide/windows_setup.rst:347
msgid "When you communicate with the WinRM service on the host you can encounter some problems. Check the following to help the troubleshooting:"
msgstr "ãã¹ãã® WinRM ãµãŒãã¹ãšéä¿¡ãããšãããã€ãã®åé¡ãçºçããå¯èœæ§ããããŸãããã©ãã«ã·ã¥ãŒãã£ã³ã°ãè¡ãã«ã¯ã以äžã確èªããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:349
msgid "The WinRM service is up and running on the host. Use the ``(Get-Service -Name winrm).Status`` command to get the status of the service."
msgstr "ãã¹ãäžã§ WinRM ãµãŒãã¹ã皌åããŠããã``(Get-Service -Name winrm).Status`` ã³ãã³ãã䜿çšããŠããµãŒãã¹ã®ã¹ããŒã¿ã¹ãååŸããŸãã"
#: ../../rst/os_guide/windows_setup.rst:350
msgid "The host firewall is allowing traffic over the WinRM port. By default this is ``5985`` for HTTP and ``5986`` for HTTPS."
msgstr "ãã¹ãåŽã®ãã¡ã€ã¢ãŠã©ãŒã«ããWinRM ããŒããžã®ãã©ãã£ãã¯ãèš±å¯ããŠãããããã©ã«ãã§ã¯ãHTTP ã§ã¯ ``5985``ãHTTPS ã§ã¯ ``5986`` ãšãªã£ãŠããŸãã"
#: ../../rst/os_guide/windows_setup.rst:352
msgid "Sometimes an installer may restart the WinRM or HTTP service and cause this error. The best way to deal with this is to use the ``win_psexec`` module from another Windows host."
msgstr "ã€ã³ã¹ããŒã©ãŒã WinRM ã HTTP ãµãŒãã¹ãåèµ·åããŠããŸãããã®ãšã©ãŒãçºçããããšããããŸããããã«å¯ŸåŠããæè¯ã®æ¹æ³ã¯ãå¥ã® Windows ãã¹ããã ``win_psexec`` ã¢ãžã¥ãŒã«ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_setup.rst:355
msgid "Failure to Load Builtin Modules"
msgstr "çµã¿èŸŒã¿ã¢ãžã¥ãŒã«ã®èªã¿èŸŒã¿ã«å€±æ"
#: ../../rst/os_guide/windows_setup.rst:356
msgid "Sometimes PowerShell fails with an error message similar to:"
msgstr "PowerShell ã以äžã®ãããªãšã©ãŒã¡ãã»ãŒãžã§å€±æããããšããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:362
msgid "In that case, there could be a problem when trying to access all the paths specified by the ``PSModulePath`` environment variable."
msgstr "ãã®å Žåã``PSModulePath`` ç°å¢å€æ°ãæå®ãããã¹ãŠã®ãã¹ã«ã¢ã¯ã»ã¹ããããšãããšåé¡ãçããå¯èœæ§ããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:364
msgid "A common cause of this issue is that ``PSModulePath`` contains a Universal Naming Convention (UNC) path to a file share. Additionally, the double hop/credential delegation issue causes that the Ansible process cannot access these folders. To work around this problem is to either:"
msgstr "ãã®åé¡ã®äžè¬çãªåå ã¯ã``PSModulePath``ãã¡ã€ã«å
±æãžã®æ±çšåœåèŠå (UNC) ãã¹ãå«ãŸããŠããŸããããã«ãããã«ããã/èªèšŒæ
å ±ã®å§ä»»ã®åé¡ã«ãããAnsible ããã»ã¹ããããã®ãã©ã«ããŒã«ã¢ã¯ã»ã¹ã§ããªããªããŸãããã®åé¡ãåé¿ããã«ã¯ã次ã®ãããããè¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:366
msgid "Remove the UNC path from ``PSModulePath``."
msgstr "``PSModulePath`` ãã UNC ãã¹ãåé€ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:368
msgid "or"
msgstr "ãŸãã¯"
#: ../../rst/os_guide/windows_setup.rst:370
msgid "Use an authentication option that supports credential delegation like ``credssp`` or ``kerberos``. You need to have the credential delegation enabled."
msgstr "``credssp`` ã ``kerberos`` ã®ãããªãèªèšŒæ
å ±ã®å§è²ããµããŒãããèªèšŒãªãã·ã§ã³ã䜿çšããŸããèªèšŒæ
å ±ã®å§è²ãæå¹ã«ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:372
msgid "See `KB4076842 <https://support.microsoft.com/en-us/help/4076842>`_ for more information on this problem."
msgstr "ãã®åé¡ã®è©³çŽ°ã¯ãã`KB4076842 <https://support.microsoft.com/en-us/help/4076842>`_ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:375
msgid "Windows SSH Setup"
msgstr "Windows SSH ã®èšå®"
#: ../../rst/os_guide/windows_setup.rst:376
msgid "Ansible 2.8 has added an experimental SSH connection for Windows managed nodes."
msgstr "Ansible 2.8 ã§ã¯ãWindows 管çããŒãã®å®éšç㪠SSH æ¥ç¶ãè¿œå ãããŸããã"
#: ../../rst/os_guide/windows_setup.rst:379
msgid "Use this feature at your own risk! Using SSH with Windows is experimental. This implementation may make backwards incompatible changes in future releases. The server-side components can be unreliable depending on your installed version."
msgstr "ãã®æ©èœã¯ãèªèº«ã®è²¬ä»»ã§ã䜿ããã ãããWindows ã§ã® SSH ã®äœ¿çšã¯å®éšçãªãã®ã§ãããå®è£
ã¯æ©èœãªãªãŒã¹ã«ãããŠåŸæ¹äºææ§ã®ãªãå€æŽãè¡ãå¯èœæ§ããããŸãããŸãããµãŒããŒåŽã®ã³ã³ããŒãã³ãã¯ãã€ã³ã¹ããŒã«ãããŠããããŒãžã§ã³ã«ãã£ãŠã¯ä¿¡é Œæ§ã«æ¬ ããããšããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:383
msgid "Installing OpenSSH using Windows Settings"
msgstr "Windows èšå®ã䜿çšãã OpenSSH ã®ã€ã³ã¹ããŒã«"
#: ../../rst/os_guide/windows_setup.rst:384
msgid "You can use OpenSSH to connect Window 10 clients to Windows Server 2019. OpenSSH Client is available to install on Windows 10 build 1809 and later. OpenSSH Server is available to install on Windows Server 2019 and later."
msgstr "OpenSSH ã¯ãWinkW 10 ã¯ã©ã€ã¢ã³ãã Windows Server 2019 ã«æ¥ç¶ããããã«äœ¿çšã§ããŸããOpenSSH ã¯ã©ã€ã¢ã³ã㯠Windows 10 ãã«ã 1809 以éã«ã€ã³ã¹ããŒã«ã§ããŸãããOpenSSH Server 㯠Windows Server 2019 以éã«å©çšã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:386
msgid "For more information, refer to `Get started with OpenSSH for Windows <https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse>`_."
msgstr "詳现ã¯ã`Get started with OpenSSH for Windows <https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_install_firstuse>` ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:389
msgid "Installing Win32-OpenSSH"
msgstr "Win32-OpenSSH ã®ã€ã³ã¹ããŒã«"
#: ../../rst/os_guide/windows_setup.rst:390
msgid "To install the `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ service for use with Ansible, select one of these installation options:"
msgstr "Ansible ã§äœ¿çšãã `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ ãµãŒãã¹ãã€ã³ã¹ããŒã«ããã«ã¯ã以äžã®ããããã®ã€ã³ã¹ããŒã«ãªãã·ã§ã³ãéžæããŸãã"
#: ../../rst/os_guide/windows_setup.rst:393
msgid "Manually install ``Win32-OpenSSH``, following the `install instructions <https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH>`_ from Microsoft."
msgstr "Microsoft 瀟ãæäŸãã `install instructions <https://github.com/PowerShell/Win32-OpenSSH/wiki/Install-Win32-OpenSSH>`_ ã«åŸã£ãŠã``Win32-OpenSSH`` ãæåã§ã€ã³ã¹ããŒã«ããŠãã ããã"
#: ../../rst/os_guide/windows_setup.rst:395
msgid "Use Chocolatey:"
msgstr "Chocolatey ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_setup.rst:401
msgid "Use the ``win_chocolatey`` Ansible module:"
msgstr "Ansibleã¢ãžã¥ãŒã« ``win_chocolatey`` ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_setup.rst:411
msgid "Install an Ansible Galaxy role for example `jborean93.win_openssh <https://galaxy.ansible.com/jborean93/win_openssh>`_:"
msgstr "`jborean93.win_openssh <https://galaxy.ansible.com/jborean93/win_openssh>`_ ãªã©ã® Ansible Galaxy ããŒã«ãã€ã³ã¹ããŒã«ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:417
msgid "Use the role in your playbook:"
msgstr "playbook ã®ããŒã«ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_setup.rst:428
msgid "``Win32-OpenSSH`` is still a beta product and is constantly being updated to include new features and bugfixes. If you use SSH as a connection option for Windows, we highly recommend you install the latest version."
msgstr "``Win32-OpenSSH`` ã¯æªã ããŒã¿çã®è£œåã§ãããæ°æ©èœããã°ä¿®æ£ãå«ããŠåžžã«æŽæ°ãããŠããŸããWindows 㧠SSH æ¥ç¶ããå©çšã®æ¹ã¯ãäžèš 3 ã€ã®æ¹æ³ããææ°çãã€ã³ã¹ããŒã«ããããšã匷ãæšå¥šããŸãã"
#: ../../rst/os_guide/windows_setup.rst:431
msgid "Configuring the Win32-OpenSSH shell"
msgstr "Win32-OpenSSH ã·ã§ã«ã®èšå®"
#: ../../rst/os_guide/windows_setup.rst:433
msgid "By default ``Win32-OpenSSH`` uses ``cmd.exe`` as a shell."
msgstr "ããã©ã«ãã§ã¯ã``Win32-OpenSSH`` ã¯ã·ã§ã«ãšã㊠``cmd.exe`` ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_setup.rst:435
msgid "To configure a different shell, use an Ansible playbook with a task to define the registry setting:"
msgstr "å¥ã®ã·ã§ã«ãèšå®ããã«ã¯ãAnsible Playbook ã䜿çšããŠãã¬ãžã¹ããªãŒèšå®ãå®çŸ©ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:447
msgid "To revert the settings back to the default shell:"
msgstr "èšå®ãããã©ã«ãã®ã·ã§ã«ã«æ»ãã«ã¯ã以äžãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:458
msgid "Win32-OpenSSH Authentication"
msgstr "Win32-OpenSSH èªèšŒ"
#: ../../rst/os_guide/windows_setup.rst:459
msgid "Win32-OpenSSH authentication with Windows is similar to SSH authentication on Unix/Linux hosts. You can use a plaintext password or SSH public key authentication."
msgstr "Windows ã§ã® Win32-OpenSSH èªèšŒã¯ãUnix/Linux ãã¹ãã® SSH èªèšŒã«äŒŒãŠããŸãããã¬ãŒã³ããã¹ãã®ãã¹ã¯ãŒããŸã㯠SSH å
¬ééµèªèšŒã䜿çšã§ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:461
msgid "For the key-based authentication:"
msgstr "éµããŒã¹èªèšŒã®äœ¿çš"
#: ../../rst/os_guide/windows_setup.rst:463
msgid "Add your public keys to an ``authorized_key`` file in the ``.ssh`` folder of the user's profile directory."
msgstr "ãŠãŒã¶ãŒã®ãããã¡ã€ã«ãã£ã¬ã¯ããªãŒã® ``.ssh`` ãã©ã«ããŒã«ãã ``authorized_key`` ãã¡ã€ã«ã«å
¬ééµãè¿œå ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:465
msgid "Configure the SSH service using the ``sshd_config`` file."
msgstr "``sshd_config`` ãã¡ã€ã«ã䜿çšã㊠SSH ãµãŒãã¹ãèšå®ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:467
msgid "When using SSH key authentication with Ansible, the remote session will not have access to user credentials and will fail when attempting to access a network resource. This is also known as the double-hop or credential delegation issue. To work around this problem:"
msgstr "Ansible 㧠SSH ããŒèªèšŒã䜿çšããå Žåã¯ããªã¢ãŒãã»ãã·ã§ã³ããŠãŒã¶ãŒã®èªèšŒæ
å ±ã«ã¢ã¯ã»ã¹ã§ããããããã¯ãŒã¯ãªãœãŒã¹ã«ã¢ã¯ã»ã¹ããããšãããšå€±æããããšããããŸããããã¯ãããã«ããããèªèšŒæ
å ±ã®å§è²ã®åé¡ãšããŠãç¥ãããŠããŸãããã®åé¡ãåé¿ããã«ã¯ä»¥äžãè¡ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:469
msgid "Use plaintext password authentication by setting the ``ansible_password`` variable."
msgstr "``ansible_password`` å€æ°ãèšå®ããŠããã¬ãŒã³ããã¹ãã®ãã¹ã¯ãŒãèªèšŒã䜿çšããã"
#: ../../rst/os_guide/windows_setup.rst:470
msgid "Use the ``become`` directive on the task with the credentials of the user that needs access to the remote resource."
msgstr "ãªã¢ãŒããªãœãŒã¹ãžã®ã¢ã¯ã»ã¹ãå¿
èŠãšãããŠãŒã¶ãŒã®èªèšŒæ
å ±ã䜿çšããŠãã¿ã¹ã¯ã§ ``become`` ãã£ã¬ã¯ãã£ãã䜿çšããã"
#: ../../rst/os_guide/windows_setup.rst:473
msgid "Configuring Ansible for SSH on Windows"
msgstr "Windows 㧠SSH çšã« Ansible ã®èšå®"
#: ../../rst/os_guide/windows_setup.rst:474
msgid "To configure Ansible to use SSH for Windows hosts, you must set two connection variables:"
msgstr "Ansible ã Windows ãã¹ãã« SSH ã䜿çšããããã«èšå®ããã«ã¯ãæ¥ç¶å€æ°ã 2 ã€èšå®ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_setup.rst:476
msgid "set ``ansible_connection`` to ``ssh``"
msgstr "``ansible_connection`` ã ``ssh`` ã«èšå®ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:477
msgid "set ``ansible_shell_type`` to ``cmd`` or ``powershell``"
msgstr "``ansible_shell_type`` ã ``cmd`` ãŸã㯠``powershell`` ã«èšå®ãã"
#: ../../rst/os_guide/windows_setup.rst:479
msgid "The ``ansible_shell_type`` variable should reflect the ``DefaultShell`` configured on the Windows host. Set ``ansible_shell_type`` to ``cmd`` for the default shell. Alternatively, set ``ansible_shell_type`` to ``powershell`` if you changed ``DefaultShell`` to PowerShell."
msgstr "``ansible_shell_type`` å€æ°ã«ã¯ãWindows ãã¹ãã§èšå®ãããŠãã``DefaultShell`` ãåæ ãããå¿
èŠããããŸããããã©ã«ãã·ã§ã«ã®å Žå㯠``ansible_shell_type`` 㯠``cmd`` ã«èšå®ããŸãããŸãã¯ã``DefaultShell`` ã PowerShell ã«å€æŽããå Žåã«ã¯ ``ansible_shell_type`` ã ``powershell`` ã«èšå®ããŸãã"
#: ../../rst/os_guide/windows_setup.rst:482
msgid "Known issues with SSH on Windows"
msgstr "Windows ã§ã® SSH ã«é¢ããæ¢ç¥ã®åé¡"
#: ../../rst/os_guide/windows_setup.rst:483
msgid "Using SSH with Windows is experimental. Currently existing issues are:"
msgstr "Windows ã§ã® SSH ã®äœ¿çšã¯å®éšçãªãã®ã§ããçŸåšãæ¢åã®åé¡ã¯æ¬¡ã®ãšããã§ãã"
#: ../../rst/os_guide/windows_setup.rst:485
msgid "Win32-OpenSSH versions older than ``v7.9.0.0p1-Beta`` do not work when ``powershell`` is the shell type."
msgstr "``powershell`` ãã·ã§ã«ã¿ã€ãã®å Žåã¯ã``v7.9.0.0p1-Beta`` ãããå€ã Win32-OpenSSH ããŒãžã§ã³ã¯æ©èœããŸããã"
#: ../../rst/os_guide/windows_setup.rst:486
msgid "While Secure Copy Protocol (SCP) should work, SSH File Transfer Protocol (SFTP) is the recommended mechanism to use when copying or fetching a file."
msgstr "Secure Copy Protocol (SCP) ãæå¹ã§ãããSSH File Transfer Protocol (SFTP) ã¯ããã¡ã€ã«ã®ã³ããŒãŸãã¯ååŸæã«äœ¿çšãããæšå¥šã®ã¡ã«ããºã ã§ãã"
#: ../../rst/os_guide/windows_usage.rst:4
msgid "Using Ansible and Windows"
msgstr "Ansible ããã³ Windows ã®äœ¿çš"
#: ../../rst/os_guide/windows_usage.rst:5
msgid "When using Ansible to manage Windows, many of the syntax and rules that apply for Unix/Linux hosts also apply to Windows, but there are still some differences when it comes to components like path separators and OS-specific tasks. This document covers details specific to using Ansible for Windows."
msgstr "Ansible ã䜿çšã㊠Windows ã管çããå Žåã¯ãUnix/Linux ãã¹ãã«é©çšãããæ§æãã«ãŒã«ã®å€ãã Windows ã«ãé©çšãããŸããããã¹ã»ãã¬ãŒã¿ãŒã OS åºæã®ã¿ã¹ã¯ãªã©ã®ã³ã³ããŒãã³ãã«é¢ããŠã¯ãè¥å¹²ã®éãããããŸãããã®ããã¥ã¡ã³ãã§ã¯ãAnsible ã Windows ã§äœ¿çšããéã®è©³çŽ°æ
å ±ã説æããŸãã"
#: ../../rst/os_guide/windows_usage.rst:14
msgid "Use Cases"
msgstr "ãŠãŒã¹ã±ãŒã¹"
#: ../../rst/os_guide/windows_usage.rst:15
msgid "Ansible can be used to orchestrate a multitude of tasks on Windows servers. Below are some examples and info about common tasks."
msgstr "Ansible ã¯ãWindows ãµãŒããŒã«ããå€æ°ã®ã¿ã¹ã¯ã調æŽããããã«äœ¿çšã§ããŸãã以äžã¯ãäžè¬çãªã¿ã¹ã¯ã«é¢ããäŸãšæ
å ±ã§ãã"
#: ../../rst/os_guide/windows_usage.rst:19
msgid "Installing Software"
msgstr "ãœãããŠã§ã¢ã®ã€ã³ã¹ããŒã«"
#: ../../rst/os_guide/windows_usage.rst:20
msgid "There are three main ways that Ansible can be used to install software:"
msgstr "Ansible ã䜿çšããŠãœãããŠã§ã¢ãã€ã³ã¹ããŒã«ã§ããäž»ãªæ¹æ³ã¯ 3 ã€ãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:22
msgid "Using the ``win_chocolatey`` module. This sources the program data from the default public `Chocolatey <https://chocolatey.org/>`_ repository. Internal repositories can be used instead by setting the ``source`` option."
msgstr "``win_chocolatey`` ã¢ãžã¥ãŒã«ã䜿çšããã®ã¢ãžã¥ãŒã«ã¯ãããã©ã«ãã®ãããªãã¯ãª `Chocolatey <https://chocolatey.org/>`_ ãªããžããªãŒããããã°ã©ã ããŒã¿ã調éããŸãã``source`` ãªãã·ã§ã³ãèšå®ããããšã§ã代ããã«å
éšãªããžããªãŒã䜿çšããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:26
msgid "Using the ``win_package`` module. This installs software using an MSI or .exe installer from a local/network path or URL."
msgstr "``win_package`` ã¢ãžã¥ãŒã«ã䜿çšããŸããããã¯ãããŒã«ã«/ãããã¯ãŒã¯ãã¹ãŸã㯠URL ãã MSI ãŸã㯠.exe ã€ã³ã¹ããŒã©ãŒã䜿çšããŠãœãããŠã§ã¢ãã€ã³ã¹ããŒã«ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:29
msgid "Using the ``win_command`` or ``win_shell`` module to run an installer manually."
msgstr "``win_command`` ã¢ãžã¥ãŒã«ãŸã㯠``win_shell`` ã¢ãžã¥ãŒã«ã䜿çšããŠæåã§ã€ã³ã¹ããŒã©ãŒãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:31
msgid "The ``win_chocolatey`` module is recommended since it has the most complete logic for checking to see if a package has already been installed and is up-to-date."
msgstr "``win_chocolatey`` ã¢ãžã¥ãŒã«ã¯ãããã±ãŒãžããã§ã«ã€ã³ã¹ããŒã«ãããŠããŠææ°ãã©ããã確èªããããã®æãå®å
šãªããžãã¯ãåããŠããããããã®ã¢ãžã¥ãŒã«ã䜿çšããããšãæšå¥šãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:33
msgid "Below are some examples of using all three options to install 7-Zip:"
msgstr "以äžã¯ã3 ã€ã®ãã¹ãŠã®ãªãã·ã§ã³ã䜿çšã㊠7-Zip ãã€ã³ã¹ããŒã«ããããã€ãã®äŸã§ãã"
#: ../../rst/os_guide/windows_usage.rst:83
msgid "Some installers like Microsoft Office or SQL Server require credential delegation or access to components restricted by WinRM. The best method to bypass these issues is to use ``become`` with the task. With ``become``, Ansible will run the installer as if it were run interactively on the host."
msgstr "Microsoft Office ã SQL Server ãªã©ã®äžéšã®ã€ã³ã¹ããŒã©ãŒã¯ãèªèšŒæ
å ±ã®å§è²ã WinRM ã§å¶éãããã³ã³ããŒãã³ããžã®ã¢ã¯ã»ã¹ãå¿
èŠãšããŸãããããã®åé¡ãåé¿ããããã®æè¯ã®æ¹æ³ã¯ãã¿ã¹ã¯ã« ``become`` ã䜿çšããããšã§ãã``become`` ã䜿çšãããšãAnsible ã¯ãããããã¹ãäžã§å¯Ÿè©±çã«å®è¡ãããŠãããã®ããã«ã€ã³ã¹ããŒã©ãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:88
msgid "Many installers do not properly pass back error information over WinRM. In these cases, if the install has been verified to work locally the recommended method is to use become."
msgstr "å€ãã®ã€ã³ã¹ããŒã©ãŒã¯ãWinRM ãä»ããŠãšã©ãŒæ
å ±ãé©åã«è¿ããŸããããã®ãããªå Žåã«ã¯ãããŒã«ã«ã§ã®åäœã確èªãããŠããå Žåã«ã¯ become ã䜿çšããããšãæšå¥šãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:90
msgid "Some installers restart the WinRM or HTTP services, or cause them to become temporarily unavailable, making Ansible assume the system is unreachable."
msgstr "äžéšã®ã€ã³ã¹ããŒã©ãŒã¯ãWinRM ãµãŒãã¹ãŸã㯠HTTP ãµãŒãã¹ãåèµ·åããããäžæçã«å©çšã§ããªããªã£ãããããããã·ã¹ãã ãå°éäžèœã§ãããš Ansible ã«ããæ³å®ãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:93
msgid "Installing Updates"
msgstr "æŽæ°ã®ã€ã³ã¹ããŒã«"
#: ../../rst/os_guide/windows_usage.rst:94
msgid "The ``win_updates`` and ``win_hotfix`` modules can be used to install updates or hotfixes on a host. The module ``win_updates`` is used to install multiple updates by category, while ``win_hotfix`` can be used to install a single update or hotfix file that has been downloaded locally."
msgstr "``win_updates`` ã¢ãžã¥ãŒã«ããã³ ``win_hotfix`` ã¢ãžã¥ãŒã«ã䜿çšãããšããã¹ãã«ã¢ããããŒãã Hotfix ãã€ã³ã¹ããŒã«ã§ããŸããã¢ãžã¥ãŒã« ``win_updates`` ã¯ã«ããŽãªãŒå¥ã«è€æ°ã®ã¢ããããŒããã€ã³ã¹ããŒã«ããããã«äœ¿çšããã``win_hotfix`` ã¯ããŒã«ã«ã«ããŠã³ããŒãããåäžã®æŽæ°ãŸã㯠Hotfix ãã¡ã€ã«ãã€ã³ã¹ããŒã«ããããã«äœ¿çšãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:99
msgid "The ``win_hotfix`` module has a requirement that the DISM PowerShell cmdlets are present. These cmdlets were only added by default on Windows Server 2012 and newer and must be installed on older Windows hosts."
msgstr "``win_hotfix`` ã¢ãžã¥ãŒã«ã«ã¯ãDISM PowerShell ã³ãã³ãã¬ãããååšãããšããèŠä»¶ããããŸãããããã®ã³ãã³ãã¬ããã¯ãWindows Server 2012 以éã§ã®ã¿ããã©ã«ãã§è¿œå ãããŠããããã以åã® Windows ãã¹ãã§ã¯ã€ã³ã¹ããŒã«ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_usage.rst:103
msgid "The following example shows how ``win_updates`` can be used:"
msgstr "次ã®äŸã¯ã``win_updates`` ã®äœ¿çšæ¹æ³ã瀺ããŠããŸãã"
#: ../../rst/os_guide/windows_usage.rst:119
msgid "The following example show how ``win_hotfix`` can be used to install a single update or hotfix:"
msgstr "以äžã®äŸã§ã¯ã``win_hotfix`` ã䜿çšããŠåäžã®ã¢ããããŒããŸã㯠Hotfix ãã€ã³ã¹ããŒã«ããæ¹æ³ã瀺ããŠããŸãã"
#: ../../rst/os_guide/windows_usage.rst:141
msgid "Set Up Users and Groups"
msgstr "ãŠãŒã¶ãŒããã³ã°ã«ãŒãã®èšå®"
#: ../../rst/os_guide/windows_usage.rst:142
msgid "Ansible can be used to create Windows users and groups both locally and on a domain."
msgstr "Ansible ã䜿çšããŠãããŒã«ã«ãšãã¡ã€ã³ã®äž¡æ¹ã§ Windows ãŠãŒã¶ãŒãšã°ã«ãŒããäœæã§ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:145
msgid "Local"
msgstr "ããŒã«ã«"
#: ../../rst/os_guide/windows_usage.rst:146
msgid "The modules ``win_user``, ``win_group`` and ``win_group_membership`` manage Windows users, groups and group memberships locally."
msgstr "``win_user`` ã¢ãžã¥ãŒã«ã``win_group`` ã¢ãžã¥ãŒã«ãããã³ ``win_group_membership`` ã¢ãžã¥ãŒã«ã¯ãWindows ã®ãŠãŒã¶ãŒãã°ã«ãŒããããã³ã°ã«ãŒãã®ã¡ã³ããŒã·ãããããŒã«ã«ã«ç®¡çããŸãã"
#: ../../rst/os_guide/windows_usage.rst:149
msgid "The following is an example of creating local accounts and groups that can access a folder on the same host:"
msgstr "以äžã¯ãåããã¹ãã«ãããã£ã¬ã¯ããªãŒã«ã¢ã¯ã»ã¹ã§ããããŒã«ã«ã¢ã«ãŠã³ãããã³ã°ã«ãŒããäœæããäŸã瀺ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:192
msgid "Domain"
msgstr "ãã¡ã€ã³"
#: ../../rst/os_guide/windows_usage.rst:193
msgid "The modules ``win_domain_user`` and ``win_domain_group`` manages users and groups in a domain. The below is an example of ensuring a batch of domain users are created:"
msgstr "``win_domain_user`` ã¢ãžã¥ãŒã«ããã³ ``win_domain_group`` ã¢ãžã¥ãŒã«ã¯ããã¡ã€ã³ã®ãŠãŒã¶ãŒããã³ã°ã«ãŒãã管çããŸãã以äžã¯ããã¡ã€ã³ãŠãŒã¶ãŒã®ãããã確å®ã«äœæããäŸã§ãã"
#: ../../rst/os_guide/windows_usage.rst:219
msgid "Running Commands"
msgstr "ã³ãã³ãã®å®è¡"
#: ../../rst/os_guide/windows_usage.rst:220
msgid "In cases where there is no appropriate module available for a task, a command or script can be run using the ``win_shell``, ``win_command``, ``raw``, and ``script`` modules."
msgstr "ã¿ã¹ã¯ã«é©ããã¢ãžã¥ãŒã«ããªãå Žåã¯ã``win_shell`` ã¢ãžã¥ãŒã«ã``win_command`` ã¢ãžã¥ãŒã«ã``raw`` ã¢ãžã¥ãŒã«ãããã³ ``script`` ã¢ãžã¥ãŒã«ã䜿çšããŠã³ãã³ããã¹ã¯ãªãããå®è¡ã§ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:223
msgid "The ``raw`` module simply executes a Powershell command remotely. Since ``raw`` has none of the wrappers that Ansible typically uses, ``become``, ``async`` and environment variables do not work."
msgstr "``raw`` ã¢ãžã¥ãŒã«ã¯ãPowershell ã³ãã³ãããªã¢ãŒãã§å®è¡ããã ãã§ãã``raw`` ã¯ãAnsible ãé垞䜿çšããã©ãããŒãäžå䜿çšããŠããªãããã``become``ã``async``ãããã³ç°å¢å€æ°ã¯åäœããŸããã"
#: ../../rst/os_guide/windows_usage.rst:227
msgid "The ``script`` module executes a script from the Ansible controller on one or more Windows hosts. Like ``raw``, ``script`` currently does not support ``become``, ``async``, or environment variables."
msgstr "``script`` ã¢ãžã¥ãŒã«ã¯ãAnsible ã³ã³ãããŒã©ãŒããã®ã¹ã¯ãªããã 1 ã€ãŸãã¯è€æ°ã® Windows ãã¹ãäžã§å®è¡ããŸãã``raw`` ãšåæ§ã«ã``script`` ã¯çŸåšã``become``ã``async``ããŸãã¯ç°å¢å€æ°ããµããŒãããŠããŸããã"
#: ../../rst/os_guide/windows_usage.rst:231
msgid "The ``win_command`` module is used to execute a command which is either an executable or batch file, while the ``win_shell`` module is used to execute commands within a shell."
msgstr "``win_command`` ã¢ãžã¥ãŒã«ã¯ãå®è¡ãã¡ã€ã«ãŸãã¯ããããã¡ã€ã«ã§ããã³ãã³ããå®è¡ããããã«äœ¿çšããã``win_shell`` ã¢ãžã¥ãŒã«ã¯ãã·ã§ã«å
ã®ã³ãã³ããå®è¡ããããã«äœ¿çšãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:235
msgid "Choosing Command or Shell"
msgstr "ã³ãã³ããŸãã¯ã·ã§ã«ã®éžæ"
#: ../../rst/os_guide/windows_usage.rst:236
msgid "The ``win_shell`` and ``win_command`` modules can both be used to execute a command or commands. The ``win_shell`` module is run within a shell-like process like ``PowerShell`` or ``cmd``, so it has access to shell operators like ``<``, ``>``, ``|``, ``;``, ``&&``, and ``||``. Multi-lined commands can also be run in ``win_shell``."
msgstr "``win_shell`` ã¢ãžã¥ãŒã«ããã³ ``win_command`` ã¢ãžã¥ãŒã«ã¯ãã©ã¡ããã³ãã³ãã®å®è¡ã«äœ¿çšã§ããŸãã``win_shell`` ã¢ãžã¥ãŒã«ã¯ ``PowerShell`` ã ``cmd`` ãªã©ã®ã·ã§ã«ã®ãããªãªããã»ã¹å
ã§å®è¡ããããã``<``ã``>``ã``|``ã``;``ã``&&``ã``||`` ãªã©ã®ã·ã§ã«æŒç®åã䜿çšã§ããŸãã``win_shell`` ã§ã¯ãè€æ°è¡ã®ã³ãã³ããå®è¡ã§ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:240
msgid "The ``win_command`` module simply runs a process outside of a shell. It can still run a shell command like ``mkdir`` or ``New-Item`` by passing the shell commands to a shell executable like ``cmd.exe`` or ``PowerShell.exe``."
msgstr "``win_command`` ã¢ãžã¥ãŒã«ã¯ãã·ã§ã«ã®å€éšã§ããã»ã¹ãå®è¡ããã ãã§ãã``cmd.exe`` ã ``PowerShell.exe`` ãªã©ã®ã·ã§ã«å®è¡ãã¡ã€ã«ã«ã``mkdir`` ã ``New-Item`` ãªã©ã®ã·ã§ã«ã³ãã³ããæž¡ããŠã·ã§ã«ã³ãã³ããå®è¡ã§ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:244
msgid "Here are some examples of using ``win_command`` and ``win_shell``:"
msgstr "以äžã¯ã``win_command`` ãš ``win_shell`` ã䜿çšããäŸã§ãã"
#: ../../rst/os_guide/windows_usage.rst:272
msgid "Some commands like ``mkdir``, ``del``, and ``copy`` only exist in the CMD shell. To run them with ``win_command`` they must be prefixed with ``cmd.exe /c``."
msgstr "``mkdir``ã``del``ã``copy`` ãªã©ã®äžéšã®ã³ãã³ãã¯ãCMD ã·ã§ã«ã«ã®ã¿ååšããŸãã``win_command`` ã§ããããå®è¡ããã«ã¯ã``cmd.exe /c`` ãã¬ãã£ãã¯ã¹ãä»ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_usage.rst:277
msgid "Argument Rules"
msgstr "åŒæ°ã®ã«ãŒã«"
#: ../../rst/os_guide/windows_usage.rst:278
msgid "When running a command through ``win_command``, the standard Windows argument rules apply:"
msgstr "``win_command`` ãéããŠã³ãã³ããå®è¡ããéã«ã¯ãWindows ã®æšæºçãªåŒæ°ã«ãŒã«ãé©çšãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:281
msgid "Each argument is delimited by a white space, which can either be a space or a tab."
msgstr "ååŒæ°ã¯ã空çœãŸãã¯ã¿ãã®ããããã§ãã空çœã§åºåãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:284
msgid "An argument can be surrounded by double quotes ``\"``. Anything inside these quotes is interpreted as a single argument even if it contains whitespace."
msgstr "åŒæ°ã¯äºéåŒçšç¬Š ``\"`` ã§å²ãããšãã§ããŸãããããã®åŒçšç¬Šã®å
åŽã«ã¯ã空çœãå«ãŸããŠããŠãã1 ã€ã®åŒæ°ãšããŠè§£éãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:287
msgid "A double quote preceded by a backslash ``\\`` is interpreted as just a double quote ``\"`` and not as an argument delimiter."
msgstr "ããã¯ã¹ã©ãã·ã¥ ``\\`` ãåã«ä»ããäºéåŒçšç¬Šã¯ãåŒæ°åºåãæåã§ã¯ãªãäºéåŒçšç¬Š ``\"`` ãšããŠè§£éãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:290
msgid "Backslashes are interpreted literally unless it immediately precedes double quotes; for example ``\\`` == ``\\`` and ``\\\"`` == ``\"``"
msgstr "ããã¯ã¹ã©ãã·ã¥ã¯ãäºéåŒçšç¬Šã®çŽåã«ãªãéããæåéãã«è§£éãããŸã (äŸ: ``\\`` ==``\\`` ããã³ ``\\\"`` == ``\"``)ã"
#: ../../rst/os_guide/windows_usage.rst:293
msgid "If an even number of backslashes is followed by a double quote, one backslash is used in the argument for every pair, and the double quote is used as a string delimiter for the argument."
msgstr "å¶æ°åã®ããã¯ã¹ã©ãã·ã¥ã®åŸã«äºéåŒçšç¬Šãç¶ãå Žåã¯ããã¹ãŠã®ãã¢ã®åŒæ°ã§ 1 ã€ã®ããã¯ã¹ã©ãã·ã¥ã䜿çšãããäºéåŒçšç¬ŠãåŒæ°ã®æåååºåãæåãšããŠäœ¿çšãããŸãã"
#: ../../rst/os_guide/windows_usage.rst:297
msgid "If an odd number of backslashes is followed by a double quote, one backslash is used in the argument for every pair, and the double quote is escaped and made a literal double quote in the argument."
msgstr "å¥æ°åã®ããã¯ã¹ã©ãã·ã¥ã®åŸã«äºéåŒçšç¬Šãç¶ãå ŽåãåŒæ°ã§ã¯ãã¢ããšã« 1 ã€ã®ããã¯ã¹ã©ãã·ã¥ã䜿çšãããäºéåŒçšç¬Šã¯ãšã¹ã±ãŒããããŠåŒæ°ã®ãªãã©ã«äºéåŒçšç¬ŠãšãªããŸãã"
#: ../../rst/os_guide/windows_usage.rst:301
msgid "With those rules in mind, here are some examples of quoting:"
msgstr "ãããã®ã«ãŒã«ã念é ã«çœ®ããŠãåŒçšã®äŸãããã€ã瀺ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:326
msgid "For more information, see `escaping arguments <https://msdn.microsoft.com/en-us/library/17w5ykft(v=vs.85).aspx>`_."
msgstr "詳现æ
å ±ã¯ãã`escaping arguments <https://msdn.microsoft.com/en-us/library/17w5ykft(v=vs.85).aspx>`_ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_usage.rst:329
msgid "Creating and Running a Scheduled Task"
msgstr "ã¹ã±ãžã¥ãŒã«ãããã¿ã¹ã¯ã®äœæããã³å®è¡"
#: ../../rst/os_guide/windows_usage.rst:330
msgid "WinRM has some restrictions in place that cause errors when running certain commands. One way to bypass these restrictions is to run a command through a scheduled task. A scheduled task is a Windows component that provides the ability to run an executable on a schedule and under a different account."
msgstr "WinRM ã«ã¯ãç¹å®ã®ã³ãã³ããå®è¡ãããšãã«ãšã©ãŒãçºçãããããªå¶éãèšããããŠããŸãããããã®å¶éãåé¿ããæ¹æ³ã® 1 ã€ãšããŠãã¹ã±ãžã¥ãŒã«ãããã¿ã¹ã¯ã䜿çšããŠã³ãã³ããå®è¡ããæ¹æ³ããããŸããã¹ã±ãžã¥ãŒã«ãããã¿ã¹ã¯ãšã¯ãå®è¡ãã¡ã€ã«ãã¹ã±ãžã¥ãŒã«ã«æ²¿ã£ãŠãå¥ã®ã¢ã«ãŠã³ãã§å®è¡ããæ©èœãæäŸãã Windows ã³ã³ããŒãã³ãã§ãã"
#: ../../rst/os_guide/windows_usage.rst:335
msgid "Ansible version 2.5 added modules that make it easier to work with scheduled tasks in Windows. The following is an example of running a script as a scheduled task that deletes itself after running:"
msgstr "Ansible ããŒãžã§ã³ 2.5 ã§ã¯ãWindows ã§ã®ã¹ã±ãžã¥ãŒã«ã¿ã¹ã¯ã®æäœã容æã«ããã¢ãžã¥ãŒã«ãè¿œå ãããŸããã以äžã¯ãå®è¡åŸã«èªåèªèº«ãåé€ããã¹ã¯ãªãããã¹ã±ãžã¥ãŒã«ã¿ã¹ã¯ãšããŠå®è¡ããäŸã§ãã"
#: ../../rst/os_guide/windows_usage.rst:364
msgid "The modules used in the above example were updated/added in Ansible version 2.5."
msgstr "äžèšã®äŸã§äœ¿çšãããŠããã¢ãžã¥ãŒã«ã¯ãAnsible ããŒãžã§ã³ 2.5 ã§æŽæ°ãŸãã¯è¿œå ããããã®ã§ãã"
#: ../../rst/os_guide/windows_usage.rst:368
msgid "Path Formatting for Windows"
msgstr "Windows ã®ãã¹ã®ãã©ãŒããã"
#: ../../rst/os_guide/windows_usage.rst:369
msgid "Windows differs from a traditional POSIX operating system in many ways. One of the major changes is the shift from ``/`` as the path separator to ``\\``. This can cause major issues with how playbooks are written, since ``\\`` is often used as an escape character on POSIX systems."
msgstr "Windows ã¯ãåŸæ¥ã® POSIX ãªãã¬ãŒãã£ã³ã°ã·ã¹ãã ãšã¯å€ãã®ç¹ã§ç°ãªããŸããäž»ãªå€æŽç¹ã®ã²ãšã€ã¯ããã¹ã®åºåãæåã ``/`` ãã ``\\`` ã«ãªã£ãããšã§ããPOSIX ã·ã¹ãã ã§ã¯ã``\\`` ããã°ãã°ãšã¹ã±ãŒãæåãšããŠäœ¿çšãããããããã㯠Playbook ã®èšè¿°æ¹æ³ã«é倧ãªåé¡ãåŒãèµ·ããå¯èœæ§ããããŸãã"
#: ../../rst/os_guide/windows_usage.rst:374
msgid "Ansible allows two different styles of syntax; each deals with path separators for Windows differently:"
msgstr "Ansible ã§ã¯ã2 ã€ã®ç°ãªãã¹ã¿ã€ã«ã®æ§æã䜿çšã§ããŸãããããã Windows ã®ãã¹ã»ãã¬ãŒã¿ãŒã®æ±ããç°ãªããŸãã"
#: ../../rst/os_guide/windows_usage.rst:377
msgid "YAML Style"
msgstr "YAML ã¹ã¿ã€ã«"
#: ../../rst/os_guide/windows_usage.rst:378
msgid "When using the YAML syntax for tasks, the rules are well-defined by the YAML standard:"
msgstr "ã¿ã¹ã¯ã« YAML æ§æã䜿çšããå Žåããã®ã«ãŒã«ã¯ YAML èŠæ Œã«ãã£ãŠæ確ã«å®çŸ©ãããŠããŸãã"
#: ../../rst/os_guide/windows_usage.rst:381
msgid "When using a normal string (without quotes), YAML will not consider the backslash an escape character."
msgstr "éåžžã®æåå (åŒçšç¬Šãªã) ã䜿çšããå ŽåãYAML ã¯ããã¯ã¹ã©ãã·ã¥ããšã¹ã±ãŒãæåãšã¯ã¿ãªããŸããã"
#: ../../rst/os_guide/windows_usage.rst:384
msgid "When using single quotes ``'``, YAML will not consider the backslash an escape character."
msgstr "äžéåŒçšç¬Š ``'`` ã䜿çšããå ŽåãYAML ã¯ããã¯ã¹ã©ãã·ã¥ããšã¹ã±ãŒãæåãšã¯ã¿ãªããŸããã"
#: ../../rst/os_guide/windows_usage.rst:387
msgid "When using double quotes ``\"``, the backslash is considered an escape character and needs to escaped with another backslash."
msgstr "äºéåŒçšç¬Š ``\"`` ã䜿çšããå Žåãããã¯ã¹ã©ãã·ã¥ã¯ãšã¹ã±ãŒãæåãšèŠãªãããå¥ã®ããã¯ã¹ã©ãã·ã¥ã§ãšã¹ã±ãŒãããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_usage.rst:390
msgid "You should only quote strings when it is absolutely necessary or required by YAML, and then use single quotes."
msgstr "æååãåŒçšããã®ã¯ã絶察ã«å¿
èŠãªå Žåã YAML ã§èŠæ±ãããå Žåã®ã¿ãšãããã®å Žåã¯äžéåŒçšç¬Šã䜿çšããŸãã"
#: ../../rst/os_guide/windows_usage.rst:393
msgid "The YAML specification considers the following `escape sequences <https://yaml.org/spec/current.html#id2517668>`_:"
msgstr "YAML ä»æ§ã¯ã以äžã® `ãšã¹ã±ãŒãã·ãŒã±ã³ã¹ <https://yaml.org/spec/current.html#id2517668>`_ ãèæ
®ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:395
msgid "``\\0``, ``\\\\``, ``\\\"``, ``\\_``, ``\\a``, ``\\b``, ``\\e``, ``\\f``, ``\\n``, ``\\r``, ``\\t``, ``\\v``, ``\\L``, ``\\N`` and ``\\P`` -- Single character escape"
msgstr "``\\0``ã``\\\\``ã``\\\"``ã``\\_``ã``\\a``ã``\\b``ã``\\e``ã``\\f``ã``\\n"
"``ã``\\r``ã``\\t``ã``\\v``ã``\\L``ã``\\N``ãããã³ ``\\P`` -- äžæåã®ãšã¹ã±ãŒã"
#: ../../rst/os_guide/windows_usage.rst:398
msgid "``<TAB>``, ``<SPACE>``, ``<NBSP>``, ``<LNSP>``, ``<PSP>`` -- Special characters"
msgstr "``<TAB>``ã``<SPACE>``ã``<NBSP>``ã``<LNSP>``ã``<PSP>`` -- ç¹æ®æå"
#: ../../rst/os_guide/windows_usage.rst:401
#: ../../rst/os_guide/windows_usage.rst:455
msgid "``\\x..`` -- 2-digit hex escape"
msgstr "``\\x..`` -- 2 æ¡ã® 16 é²ãšã¹ã±ãŒã"
#: ../../rst/os_guide/windows_usage.rst:403
#: ../../rst/os_guide/windows_usage.rst:457
msgid "``\\u....`` -- 4-digit hex escape"
msgstr "``\\u....`` -- 4 æ¡ã® 16 é²ãšã¹ã±ãŒã"
#: ../../rst/os_guide/windows_usage.rst:405
#: ../../rst/os_guide/windows_usage.rst:459
msgid "``\\U........`` -- 8-digit hex escape"
msgstr "``\\U........`` -- 8 æ¡ã® 16 é²ãšã¹ã±ãŒã"
#: ../../rst/os_guide/windows_usage.rst:407
msgid "Here are some examples on how to write Windows paths:"
msgstr "Windows ãã¹ã®èšè¿°æ¹æ³ã®äŸã次ã«ç€ºããŸãã"
#: ../../rst/os_guide/windows_usage.rst:423
msgid "This is an example which will fail:"
msgstr "ããã¯å€±æããäŸã§ãã"
#: ../../rst/os_guide/windows_usage.rst:430
msgid "This example shows the use of single quotes when they are required:"
msgstr "ãã®äŸã¯ãå¿
èŠãªå Žåã®äžéåŒçšç¬Šã®äœ¿çšã瀺ããŠããŸãã"
#: ../../rst/os_guide/windows_usage.rst:441
msgid "Legacy key=value Style"
msgstr "åŸæ¥ã® key=value ã¹ã¿ã€ã«"
#: ../../rst/os_guide/windows_usage.rst:442
msgid "The legacy ``key=value`` syntax is used on the command line for ad hoc commands, or inside playbooks. The use of this style is discouraged within playbooks because backslash characters need to be escaped, making playbooks harder to read. The legacy syntax depends on the specific implementation in Ansible, and quoting (both single and double) does not have any effect on how it is parsed by Ansible."
msgstr "åŸæ¥ã® ``key=value`` ã®æ§æã¯ãã³ãã³ãã©ã€ã³ã§ã®ã¢ãããã¯ãªã³ãã³ãã Playbook å
ã§äœ¿çšãããŸããããã¯ã¹ã©ãã·ã¥æåããšã¹ã±ãŒãããå¿
èŠããããPlaybook ãèªã¿ã¥ãããªããããPlaybook å
ã§ã¯ãã®ã¹ã¿ã€ã«ã®äœ¿çšã¯æšå¥šãããŸãããåŸæ¥ã®æ§æã¯ãAnsible ã®ç¹å®ã®å®è£
ã«äŸåããŠãããåŒçšç¬Š (åäžããã³äºé) ã¯ãAnsible ã§ã®è§£ææ¹æ³ã«ã¯åœ±é¿ããŸããã"
#: ../../rst/os_guide/windows_usage.rst:449
msgid "The Ansible key=value parser parse_kv() considers the following escape sequences:"
msgstr "Ansible ã® key=value ããŒãµãŒ parse_kv() ã¯ã以äžã®ãšã¹ã±ãŒãã·ãŒã±ã³ã¹ãèæ
®ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:452
msgid "``\\``, ``'``, ``\"``, ``\\a``, ``\\b``, ``\\f``, ``\\n``, ``\\r``, ``\\t`` and ``\\v`` -- Single character escape"
msgstr "``\\``ã``'``ã``\"``ã``\\a``ã``\\b``ã``\\f``ã``\\n"
"``ã``\\r``ã``\\t``ãããã³ ``\\v`` -- äžæåã®ãšã¹ã±ãŒã"
#: ../../rst/os_guide/windows_usage.rst:461
msgid "``\\N{...}`` -- Unicode character by name"
msgstr "``\\N{...}`` -- ååã«ãã Unicode æå"
#: ../../rst/os_guide/windows_usage.rst:463
msgid "This means that the backslash is an escape character for some sequences, and it is usually safer to escape a backslash when in this form."
msgstr "ããã¯ãããã¯ã¹ã©ãã·ã¥ãããã€ãã®ã·ãŒã±ã³ã¹ã®ãšã¹ã±ãŒãæåã«ãªã£ãŠããããšãæå³ããŠãããéåžžããã®åœ¢åŒã®å Žåã¯ããã¯ã¹ã©ãã·ã¥ããšã¹ã±ãŒãããæ¹ãå®å
šã§ãã"
#: ../../rst/os_guide/windows_usage.rst:466
msgid "Here are some examples of using Windows paths with the key=value style:"
msgstr "key=value ã¹ã¿ã€ã«ã§ Windows ãã¹ã䜿çšããäŸã次ã«ç€ºããŸãã"
#: ../../rst/os_guide/windows_usage.rst:488
msgid "The failing examples don't fail outright but will substitute ``\\t`` with the ``<TAB>`` character resulting in ``tempdir`` being ``C:\\Windows<TAB>emp``."
msgstr "倱æããäŸã§ã¯ãå®å
šã«å€±æããããã§ã¯ãããŸãããã``\\t`` ã ``<TAB>`` ã®æåã§çœ®ãæããŠã``tempdir`` ã ``C:\\Windows<TAB>emp`` ã«ããŸãã"
#: ../../rst/os_guide/windows_usage.rst:492
msgid "Limitations"
msgstr "å¶éäºé
"
#: ../../rst/os_guide/windows_usage.rst:493
msgid "Some things you cannot do with Ansible and Windows are:"
msgstr "ããã§ã¯ãAnsible ããã³ Windows ã§ã§ããªãããšã説æããŸãã"
#: ../../rst/os_guide/windows_usage.rst:495
msgid "Upgrade PowerShell"
msgstr "PowerShell ã®ã¢ããã°ã¬ãŒã"
#: ../../rst/os_guide/windows_usage.rst:497
msgid "Interact with the WinRM listeners"
msgstr "WinRM ãªã¹ããŒãšã®å¯Ÿè©±"
#: ../../rst/os_guide/windows_usage.rst:499
msgid "Because WinRM is reliant on the services being online and running during normal operations, you cannot upgrade PowerShell or interact with WinRM listeners with Ansible. Both of these actions will cause the connection to fail. This can technically be avoided by using ``async`` or a scheduled task, but those methods are fragile if the process it runs breaks the underlying connection Ansible uses, and are best left to the bootstrapping process or before an image is created."
msgstr "WinRM ã¯ãéåžžã®éçšæã«ãµãŒãã¹ããªã³ã©ã€ã³ã§çšŒåããŠããããšã«äŸåããŠãããããPowerShell ãã¢ããã°ã¬ãŒãããããAnsible 㧠WinRM ãªã¹ããŒãšå¯Ÿè©±ãããããããšã¯ã§ããŸããããããã®ã¢ã¯ã·ã§ã³ã¯ãããããæ¥ç¶ã®å€±æãåŒãèµ·ãããŸããããã¯ãæè¡çã«ã¯ ``async`` ãã¹ã±ãžã¥ãŒã«ãããã¿ã¹ã¯ã䜿çšããããšã§åé¿ã§ããŸããããããã®æ¹æ³ã¯ãå®è¡ããããã»ã¹ã«ãã£ãŠ Ansible ã䜿çšããåºç€çãªæ¥ç¶ãå£ãããšè匱ã«ãªããããããŒãã¹ãã©ããããã»ã¹ãã€ã¡ãŒãžãäœæãããåã«ä»»ããã®ãæé©ã§ãã"
#: ../../rst/os_guide/windows_usage.rst:503
msgid "Developing Windows Modules"
msgstr "Windows ã¢ãžã¥ãŒã«ã®éçº"
#: ../../rst/os_guide/windows_usage.rst:504
msgid "Because Ansible modules for Windows are written in PowerShell, the development guides for Windows modules differ substantially from those for standard standard modules. Please see :ref:`developing_modules_general_windows` for more information."
msgstr "Windows çšã® Ansible ã¢ãžã¥ãŒã«ã¯ PowerShell ã§æžãããŠãããããWindows ã¢ãžã¥ãŒã«ã®éçºã¬ã€ãã¯æšæºèŠæ Œã®ã¢ãžã¥ãŒã«ã®éçºã¬ã€ããšã¯å€§ããç°ãªããŸãã詳现ã¯ãã:ref:`developing_modules_general_windows`ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:4
msgid "Windows Remote Management"
msgstr "Windows ãªã¢ãŒã管ç"
#: ../../rst/os_guide/windows_winrm.rst:5
msgid "Unlike Linux/Unix hosts, which use SSH by default, Windows hosts are configured with WinRM. This topic covers how to configure and use WinRM with Ansible."
msgstr "ããã©ã«ã㧠SSH ã䜿çšãã Linux/Unix ãã¹ããšã¯ç°ãªããWindows ãã¹ã㯠WinRM ã§èšå®ãããŠããŸãããã®ãããã¯ã§ã¯ãAnsible 㧠WinRM ãèšå®ãã䜿çšããæ¹æ³ã説æããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:14
msgid "What is WinRM?"
msgstr "WinRM ãšã¯"
#: ../../rst/os_guide/windows_winrm.rst:16
msgid "WinRM is a management protocol used by Windows to remotely communicate with another server. It is a SOAP-based protocol that communicates over HTTP/HTTPS, and is included in all recent Windows operating systems. Since Windows Server 2012, WinRM has been enabled by default, but in most cases extra configuration is required to use WinRM with Ansible."
msgstr "WinRM ã¯ãWindows ãå¥ã®ãµãŒããŒãšãªã¢ãŒãã§éä¿¡ããéã«äœ¿çšãã管çãããã³ã«ã§ããWinRM ã¯ãHTTP/HTTPS ã§éä¿¡ãã SOAP ããŒã¹ã®ãããã³ã«ã§ãæè¿ã®ãã¹ãŠã® Windows OS ã«æèŒãããŠããŸããWindows Server 2012 以éãWinRM ã¯ããã©ã«ãã§æå¹ã«ãªã£ãŠããŸãããã»ãšãã©ã®å Žåã¯ãAnsible 㧠WinRM ã䜿çšããã«ã¯è¿œå ã®èšå®ãå¿
èŠã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:22
msgid "Ansible uses the `pywinrm <https://github.com/diyan/pywinrm>`_ package to communicate with Windows servers over WinRM. It is not installed by default with the Ansible package, but can be installed by running the following:"
msgstr "Ansible 㯠`pywinrm <https://github.com/diyan/pywinrm>`_ ããã±ãŒãžã䜿çšããŠãWinRM ãä»ã㊠Windows ãµãŒããŒãšéä¿¡ããŸããããã©ã«ãã§ã¯ Ansible ããã±ãŒãžãšãšãã«ã€ã³ã¹ããŒã«ãããŸãããã以äžãå®è¡ããããšã§ã€ã³ã¹ããŒã«ã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:30
msgid "on distributions with multiple python versions, use pip2 or pip2.x, where x matches the python minor version Ansible is running under."
msgstr "è€æ°ã® python ããŒãžã§ã³ããããã£ã¹ããªãã¥ãŒã·ã§ã³ã§ã¯ãpip2 ãŸã㯠pip2.x ã䜿çšããŸããx ã¯ãAnsible ãå®è¡ããŠãã python ãã€ããŒããŒãžã§ã³ãšäžèŽããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:34
msgid "Using the ``winrm`` or ``psrp`` connection plugins in Ansible on MacOS in the latest releases typically fail. This is a known problem that occurs deep within the Python stack and cannot be changed by Ansible. The only workaround today is to set the environment variable ``no_proxy=*`` and avoid using Kerberos auth."
msgstr "ææ°ãªãªãŒã¹ã® MacOS äžã® Ansible ã§ãconnection ãã©ã°ã€ã³ ``winrm`` ãŸã㯠``psrp`` ã䜿çšãããšãéåžžã¯å€±æããŸããããã¯ãPython ã¹ã¿ãã¯ã®å¥¥æ·±ãã§çºçããæ¢ç¥ã®åé¡ã§ãããAnsible ã§ã¯å€æŽã§ããŸãããçŸåšã®å¯äžã®åé¿çã¯ãç°å¢å€æ° ``no_proxy=*`` ãèšå®ããKerberos èªèšŒã䜿çšããªãããã«ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:44
msgid "WinRM authentication options"
msgstr "WinRM èªèšŒãªãã·ã§ã³"
#: ../../rst/os_guide/windows_winrm.rst:46
msgid "When connecting to a Windows host, there are several different options that can be used when authenticating with an account. The authentication type may be set on inventory hosts or groups with the ``ansible_winrm_transport`` variable."
msgstr "Windows ãã¹ãã«æ¥ç¶ããéãã¢ã«ãŠã³ãã§èªèšŒããéã«äœ¿çšã§ããããã€ãã®ç°ãªããªãã·ã§ã³ããããŸããèªèšŒã¿ã€ãã¯ãã€ã³ãã³ããªãŒã®ãã¹ããŸãã¯ã°ã«ãŒãã« ``ansible_winrm_transport`` å€æ°ã§èšå®ã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:50
msgid "The following matrix is a high level overview of the options:"
msgstr "以äžã®ãããªãã¯ã¹ã¯ããªãã·ã§ã³ã®æŠèŠã瀺ããŠããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:53
msgid "Option"
msgstr "ãªãã·ã§ã³"
#: ../../rst/os_guide/windows_winrm.rst:53
msgid "Local Accounts"
msgstr "ããŒã«ã«ã¢ã«ãŠã³ã"
#: ../../rst/os_guide/windows_winrm.rst:53
msgid "Active Directory Accounts"
msgstr "Active Directory ã¢ã«ãŠã³ã"
#: ../../rst/os_guide/windows_winrm.rst:53
msgid "Credential Delegation"
msgstr "èªèšŒæ
å ±ã®å§è²"
#: ../../rst/os_guide/windows_winrm.rst:53
msgid "HTTP Encryption"
msgstr "HTTP æå·å"
#: ../../rst/os_guide/windows_winrm.rst:55
#: ../../rst/os_guide/windows_winrm.rst:69
msgid "Basic"
msgstr "åºæ¬"
#: ../../rst/os_guide/windows_winrm.rst:55
#: ../../rst/os_guide/windows_winrm.rst:57
#: ../../rst/os_guide/windows_winrm.rst:59
#: ../../rst/os_guide/windows_winrm.rst:61
#: ../../rst/os_guide/windows_winrm.rst:63
msgid "Yes"
msgstr "å¯"
#: ../../rst/os_guide/windows_winrm.rst:55
#: ../../rst/os_guide/windows_winrm.rst:57
#: ../../rst/os_guide/windows_winrm.rst:59
#: ../../rst/os_guide/windows_winrm.rst:61
msgid "No"
msgstr "äžå¯"
#: ../../rst/os_guide/windows_winrm.rst:57
#: ../../rst/os_guide/windows_winrm.rst:96
msgid "Certificate"
msgstr "蚌ææž"
#: ../../rst/os_guide/windows_winrm.rst:59
#: ../../rst/os_guide/windows_winrm.rst:302
msgid "Kerberos"
msgstr "Kerberos"
#: ../../rst/os_guide/windows_winrm.rst:61
#: ../../rst/os_guide/windows_winrm.rst:272
msgid "NTLM"
msgstr "NTLM"
#: ../../rst/os_guide/windows_winrm.rst:63
#: ../../rst/os_guide/windows_winrm.rst:517
msgid "CredSSP"
msgstr "CredSSP"
#: ../../rst/os_guide/windows_winrm.rst:71
msgid "Basic authentication is one of the simplest authentication options to use, but is also the most insecure. This is because the username and password are simply base64 encoded, and if a secure channel is not in use (eg, HTTPS) then it can be decoded by anyone. Basic authentication can only be used for local accounts (not domain accounts)."
msgstr "Basic èªèšŒã¯ãæãã·ã³ãã«ãªèªèšŒæ¹æ³ã® 1 ã€ã§ãããå®å
šæ§ãæãäœããªããŸããããã¯ããŠãŒã¶ãŒåããã³ãã¹ã¯ãŒããåçŽã« Base64 ãšã³ã³ãŒããããŠããããã§ãå®å
šãªãã£ã³ãã« (äŸ: HTTPS) ã䜿çšãããŠããªãå Žåã¯ã誰ã§ã解èªããããšãã§ããŸããBasic èªèšŒã¯ãããŒã«ã«ã¢ã«ãŠã³ãã«ã®ã¿äœ¿çšããããšãã§ããŸã (ãã¡ã€ã³ã¢ã«ãŠã³ãã«ã¯äœ¿çšã§ããŸãã)ã"
#: ../../rst/os_guide/windows_winrm.rst:76
msgid "The following example shows host vars configured for basic authentication:"
msgstr "以äžã®äŸã¯ãåºæ¬èªèšŒã«èšå®ãããŠãããã¹ãå€æ°ã瀺ããŠããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:85
msgid "Basic authentication is not enabled by default on a Windows host but can be enabled by running the following in PowerShell:"
msgstr "Basic èªèšŒã¯ãWindows ãã¹ãã§ã¯ããã©ã«ãã§ã¯æå¹ã«ãªã£ãŠããŸããããPowerShell ã§ä»¥äžãå®è¡ããããšã§æå¹ã«ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:98
msgid "Certificate authentication uses certificates as keys similar to SSH key pairs, but the file format and key generation process is different."
msgstr "蚌ææžèªèšŒã¯ãSSH ããŒãã¢ã«äŒŒãéµãšããŠèšŒææžã䜿çšããŸããããã¡ã€ã«åœ¢åŒãšéµã®çæããã»ã¹ã¯ç°ãªããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:101
msgid "The following example shows host vars configured for certificate authentication:"
msgstr "以äžã®äŸã§ã¯ã蚌ææžèªèšŒã«èšå®ãããŠãããã¹ãå€æ°ã瀺ããŠããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:110
msgid "Certificate authentication is not enabled by default on a Windows host but can be enabled by running the following in PowerShell:"
msgstr "蚌ææžèªèšŒã¯ãWindows ãã¹ãã§ã¯ããã©ã«ãã§ã¯æå¹ã«ãªã£ãŠããŸããããPowerShell ã§ä»¥äžãå®è¡ããããšã§æå¹ã«ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:117
msgid "Encrypted private keys cannot be used as the urllib3 library that is used by Ansible for WinRM does not support this functionality."
msgstr "WinRM åãã« Ansible ã䜿çšãã urllib3 ã©ã€ãã©ãªãŒããã®æ©èœããµããŒãããŠããªããããæå·åãããç§å¯éµã¯äœ¿çšã§ããŸããã"
#: ../../rst/os_guide/windows_winrm.rst:120
msgid "Certificate authentication does not work with a TLS 1.3 connection."
msgstr "蚌ææžèªèšŒã¯ãTLS 1.3 æ¥ç¶ã§ã¯æ©èœããŸããã"
#: ../../rst/os_guide/windows_winrm.rst:122
msgid ".._winrm_certificate_generate:"
msgstr ".._winrm_certificate_generate:"
#: ../../rst/os_guide/windows_winrm.rst:125
msgid "Generate a Certificate"
msgstr "蚌ææžã®çæ"
#: ../../rst/os_guide/windows_winrm.rst:127
msgid "A certificate must be generated before it can be mapped to a local user. This can be done using one of the following methods:"
msgstr "蚌ææžãããŒã«ã«ãŠãŒã¶ãŒã«ãããã³ã°ããåã«ã蚌ææžãçæããå¿
èŠããããŸããããã¯ã以äžã®ããããã®æ¹æ³ã§è¡ãããšãã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:130
msgid "OpenSSL"
msgstr "OpenSSL"
#: ../../rst/os_guide/windows_winrm.rst:131
msgid "PowerShell, using the ``New-SelfSignedCertificate`` cmdlet"
msgstr "``New-SelfSignedCertificate`` ã³ãã³ãã¬ããã䜿çšãã PowerShell"
#: ../../rst/os_guide/windows_winrm.rst:132
msgid "Active Directory Certificate Services"
msgstr "Active Directory 蚌ææžãµãŒãã¹"
#: ../../rst/os_guide/windows_winrm.rst:134
msgid "Active Directory Certificate Services is beyond of scope in this documentation but may be the best option to use when running in a domain environment. For more information, see the `Active Directory Certificate Services documentation <https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732625(v=ws.11)>`_."
msgstr "Active Directory Certificate Services ã¯ããã®ããã¥ã¡ã³ãã§ã¯å¯Ÿè±¡å€ã«ãªããŸããããã¡ã€ã³ç°å¢ã§å®è¡ããå Žåã«ã¯ãæé©ãªãªãã·ã§ã³ã«ãªããããããŸããã詳现ã¯ã`Active Directory Certificate Services ã®ããã¥ã¡ã³ã <https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc732625(v=ws.11)>`_ ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:138
msgid "Using the PowerShell cmdlet ``New-SelfSignedCertificate`` to generate a certificate for authentication only works when being generated from a Windows 10 or Windows Server 2012 R2 host or later. OpenSSL is still required to extract the private key from the PFX certificate to a PEM file for Ansible to use."
msgstr "PowerShell ã³ãã³ãã¬ãã (``New-SelfSignedCertificate``) ã䜿çšããŠèªèšŒçšã®èšŒææžãçæããå Žåã¯ãWindows 10 ãŸã㯠Windows Server 2012 R2 ãã¹ã以éããçæãããå Žåã«ã®ã¿æ©èœããŸããPFX 蚌ææžãã Ansible ã䜿çšãã PEM ãã¡ã€ã«ã«ç§å¯éµãæœåºããã«ã¯ãOpenSSL ãåŒãç¶ãå¿
èŠãšãªããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:144
msgid "To generate a certificate with ``OpenSSL``:"
msgstr "``OpenSSL`` ã§èšŒææžãçæããã«ã¯ã以äžãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:164
msgid "To generate a certificate with ``New-SelfSignedCertificate``:"
msgstr "``New-SelfSignedCertificate`` ã§èšŒææžãçæããã«ã¯ã以äžãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:192
msgid "To convert the PFX file to a private key that pywinrm can use, run the following command with OpenSSL ``openssl pkcs12 -in cert.pfx -nocerts -nodes -out cert_key.pem -passin pass: -passout pass:``"
msgstr "PFX ãã¡ã€ã«ã pywinrm ã䜿çšã§ããç§å¯éµã«å€æããã«ã¯ãOpenSSL 㧠``openssl pkcs12 -in cert.pfx -nocerts -nodes -out cert_key.pem -passin pass: -passout pass:`` ã³ãã³ããå®è¡ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:199
msgid "Import a Certificate to the Certificate Store"
msgstr "蚌ææžã¹ãã¢ãžã®èšŒææžã®ã€ã³ããŒã"
#: ../../rst/os_guide/windows_winrm.rst:201
msgid "Once a certificate has been generated, the issuing certificate needs to be imported into the ``Trusted Root Certificate Authorities`` of the ``LocalMachine`` store, and the client certificate public key must be present in the ``Trusted People`` folder of the ``LocalMachine`` store. For this example, both the issuing certificate and public key are the same."
msgstr "蚌ææžãçæãããããçºè¡ãã蚌ææžã ``LocalMachine`` ã¹ãã¢ã® ``Trusted Root Certificate Authorities`` ã«ã€ã³ããŒãããã¯ã©ã€ã¢ã³ã蚌ææžã®å
¬ééµã ``LocalMachine`` ã¹ãã¢ã® ``Trusted People`` ãã£ã¬ã¯ããªãŒã«ååšãããå¿
èŠããããŸãããã®äŸã§ã¯ãçºè¡ãã蚌ææžãšå
¬ééµã®äž¡æ¹ãåããã®ã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:207
msgid "Following example shows how to import the issuing certificate:"
msgstr "以äžã®äŸã§ã¯ãçºè¡ãã蚌ææžãã€ã³ããŒãããæ¹æ³ã瀺ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:221
msgid "If using ADCS to generate the certificate, then the issuing certificate will already be imported and this step can be skipped."
msgstr "ADCS ã䜿çšããŠèšŒææžãçæããå Žåã¯ãçºè¡ãã蚌ææžããã§ã«ã€ã³ããŒããããŠããããããã®æé ã¯çç¥ã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:224
msgid "The code to import the client certificate public key is:"
msgstr "ã¯ã©ã€ã¢ã³ã蚌ææžã®å
¬ééµãã€ã³ããŒãããã³ãŒãã¯ä»¥äžã®ãšããã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:241
msgid "Mapping a Certificate to an Account"
msgstr "蚌ææžã®ã¢ã«ãŠã³ããžã®ãããã³ã°"
#: ../../rst/os_guide/windows_winrm.rst:243
msgid "Once the certificate has been imported, map it to the local user account:"
msgstr "蚌ææžãã€ã³ããŒããããããããããŒã«ã«ãŠãŒã¶ãŒã¢ã«ãŠã³ãã«ãããã³ã°ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:264
msgid "Once this is complete, the hostvar ``ansible_winrm_cert_pem`` should be set to the path of the public key and the ``ansible_winrm_cert_key_pem`` variable should be set to the path of the private key."
msgstr "ãããå®äºãããããã¹ãå€æ° ``ansible_winrm_cert_pem`` ã«å
¬ééµã®ãã¹ãèšå®ããå€æ°``ansible_winrm_cert_key_pem`` ã«ç§å¯éµã®ãã¹ãèšå®ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:274
msgid "NTLM is an older authentication mechanism used by Microsoft that can support both local and domain accounts. NTLM is enabled by default on the WinRM service, so no setup is required before using it."
msgstr "NTLM ã¯ãMicrosoft ã䜿çšããŠããå€ãèªèšŒã¡ã«ããºã ã§ãããŒã«ã«ã¢ã«ãŠã³ããšãã¡ã€ã³ã¢ã«ãŠã³ãã®äž¡æ¹ããµããŒãããŠããŸããNTLM ã¯ãWinRM ãµãŒãã¹ã§ããã©ã«ãã§æå¹ã«ãªã£ãŠããããã䜿çšããåã«èšå®ããå¿
èŠã¯ãããŸããã"
#: ../../rst/os_guide/windows_winrm.rst:278
msgid "NTLM is the easiest authentication protocol to use and is more secure than ``Basic`` authentication. If running in a domain environment, ``Kerberos`` should be used instead of NTLM."
msgstr "NTLM ã¯æãç°¡åã«äœ¿çšã§ããèªèšŒãããã³ã«ã§ããã``Basic`` èªèšŒãããå®å
šã§ãããã¡ã€ã³ç°å¢ã§çšŒåããŠããå Žåã¯ãNTLM ã®ä»£ããã« ``Kerberos`` ã䜿çšããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:282
msgid "Kerberos has several advantages over using NTLM:"
msgstr "Kerberos 㯠NTLM ã®äœ¿çšãšæ¯èŒããŠã以äžã®ãããªå©ç¹ããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:284
msgid "NTLM is an older protocol and does not support newer encryption protocols."
msgstr "NTLM ã¯å€ããããã³ã«ã§ãããæ°ããæå·åãããã³ã«ããµããŒãããŸããã"
#: ../../rst/os_guide/windows_winrm.rst:286
msgid "NTLM is slower to authenticate because it requires more round trips to the host in the authentication stage."
msgstr "NTLM ã¯ãèªèšŒã®æ®µéã§ãã¹ããžã®ã©ãŠã³ãããªãããå€ããªããããèªèšŒã«æéãããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:288
msgid "Unlike Kerberos, NTLM does not allow credential delegation."
msgstr "Kerberos ãšã¯ç°ãªããNTLM ã¯èªèšŒæ
å ±ã®å§è²ãèš±å¯ããŠããŸããã"
#: ../../rst/os_guide/windows_winrm.rst:290
msgid "This example shows host variables configured to use NTLM authentication:"
msgstr "以äžã®äŸã§ã¯ãNTLM èªèšŒã䜿çšããããã«èšå®ãããŠãããã¹ãå€æ°ã瀺ããŠããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:304
msgid "Kerberos is the recommended authentication option to use when running in a domain environment. Kerberos supports features like credential delegation and message encryption over HTTP and is one of the more secure options that is available through WinRM."
msgstr "Kerberos ã¯ããã¡ã€ã³ç°å¢ã§å®è¡ããå Žåã«äœ¿çšããæšå¥šã®èªèšŒãªãã·ã§ã³ã§ããKerberos ã¯ãèªèšŒæ
å ±ã®å§è²ã HTTP ã§ã®ã¡ãã»ãŒãžæå·åãªã©ã®æ©èœããµããŒãããŠãããWinRM ã§å©çšã§ããããå®å
šãªãªãã·ã§ã³ã® 1 ã€ã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:309
msgid "Kerberos requires some additional setup work on the Ansible host before it can be used properly."
msgstr "Kerberos ãæ£ãã䜿çšããã«ã¯ãAnsible ãã¹ãäžã§ããã€ãã®è¿œå èšå®äœæ¥ãå¿
èŠã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:312
msgid "The following example shows host vars configured for Kerberos authentication:"
msgstr "以äžã®äŸã¯ãKerberos èªèšŒã«èšå®ããããã¹ãå€æ°ã瀺ããŠããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:322
msgid "As of Ansible version 2.3, the Kerberos ticket will be created based on ``ansible_user`` and ``ansible_password``. If running on an older version of Ansible or when ``ansible_winrm_kinit_mode`` is ``manual``, a Kerberos ticket must already be obtained. See below for more details."
msgstr "Ansible ããŒãžã§ã³ 2.3 以éã§ã¯ã``ansible_user`` ãš ``ansible_password`` ã«åºã¥ã㊠Kerberos ãã±ãããäœæãããŸããå€ãããŒãžã§ã³ã® Ansible ã§å®è¡ããŠããå Žåãã``ansible_winrm_kinit_mode`` ã ``manual`` ã®å Žåã¯ããã§ã« Kerberos ãã±ãããååŸããŠããå¿
èŠããããŸãã詳现ã¯ä»¥äžãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:327
msgid "There are some extra host variables that can be set:"
msgstr "èšå®å¯èœãªè¿œå ã®ãã¹ãå€æ°ããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:340
msgid "Installing the Kerberos Library"
msgstr "Kerberos ã©ã€ãã©ãªãŒã®ã€ã³ã¹ããŒã«"
#: ../../rst/os_guide/windows_winrm.rst:342
msgid "Some system dependencies that must be installed prior to using Kerberos. The script below lists the dependencies based on the distro:"
msgstr "Kerberos ã䜿çšããåã«ã€ã³ã¹ããŒã«ããå¿
èŠãããã·ã¹ãã äŸåé¢ä¿ããããŸãã以äžã®ã¹ã¯ãªããã¯ããã£ã¹ããªãã¥ãŒã·ã§ã³ã«åºã¥ãäŸåé¢ä¿ãäžèŠ§è¡šç€ºããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:371
msgid "Once the dependencies have been installed, the ``python-kerberos`` wrapper can be install using ``pip``:"
msgstr "äŸåé¢ä¿ãã€ã³ã¹ããŒã«ããããã``pip`` ã䜿çšã㊠``python-kerberos`` ã©ãããŒãã€ã³ã¹ããŒã«ã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:380
msgid "While Ansible has supported Kerberos auth through ``pywinrm`` for some time, optional features or more secure options may only be available in newer versions of the ``pywinrm`` and/or ``pykerberos`` libraries. It is recommended you upgrade each version to the latest available to resolve any warnings or errors. This can be done through tools like ``pip`` or a system package manager like ``dnf``, ``yum``, ``apt`` but the package names and versions available may differ between tools."
msgstr "Ansible ã¯ãããŸã§ã``pywinrm`` ãéã㊠Kerberos èªèšŒããµããŒãããŠããŸãããããªãã·ã§ã³æ©èœãããå®å
šãªãªãã·ã§ã³ã¯ã``pywinrm`` ã©ã€ãã©ãªãŒãŸã㯠``pykerberos`` ã©ã€ãã©ãªãŒã®æ°ããããŒãžã§ã³ã§ã®ã¿å©çšã§ããå ŽåããããŸããèŠåããšã©ãŒãçºçããå Žåã¯ãåããŒãžã§ã³ãææ°ã®ãã®ã«ã¢ããã°ã¬ãŒãããããšãæšå¥šãããŸãããã®äœæ¥ã¯ã``pip`` ã®ãããªããŒã«ãã``dnf``ã``yum``ã``apt`` ã®ãããªã·ã¹ãã ããã±ãŒãžãããŒãžã£ãŒã§è¡ãããšãã§ããŸãããããã±ãŒãžåãå©çšå¯èœãªããŒãžã§ã³ã¯ããŒã«ã«ãã£ãŠç°ãªãå ŽåããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:392
msgid "Configuring Host Kerberos"
msgstr "ãã¹ã Kerberos ã®èšå®"
#: ../../rst/os_guide/windows_winrm.rst:394
msgid "Once the dependencies have been installed, Kerberos needs to be configured so that it can communicate with a domain. This configuration is done through the ``/etc/krb5.conf`` file, which is installed with the packages in the script above."
msgstr "äŸåé¢ä¿ãã€ã³ã¹ããŒã«ãããããKerberos ããã¡ã€ã³ãšéä¿¡ã§ããããã«èšå®ããå¿
èŠããããŸãããã®èšå®ã¯ãäžã®ã¹ã¯ãªããã§ããã±ãŒãžãšäžç·ã«ã€ã³ã¹ããŒã«ããã ``/etc/krb5.conf`` ãã¡ã€ã«ãéããŠè¡ãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:398
msgid "To configure Kerberos, in the section that starts with:"
msgstr "Kerberos ãèšå®ããã«ã¯ã以äžã§å§ãŸãã»ã¯ã·ã§ã³ã§è¡ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:404
msgid "Add the full domain name and the fully qualified domain names of the primary and secondary Active Directory domain controllers. It should look something like this:"
msgstr "ãã©ã€ããªãŒããã³ã»ã«ã³ããªãŒã® Active Directory ãã¡ã€ã³ã³ã³ãããŒã©ãŒã®å®å
šãã¡ã€ã³åããã³å®å
šä¿®é£Ÿãã¡ã€ã³åãè¿œå ããŸãã以äžã®ããã«ãªãã¯ãã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:416
msgid "In the section that starts with:"
msgstr "以äžã§å§ãŸãã»ã¯ã·ã§ã³ã§ã"
#: ../../rst/os_guide/windows_winrm.rst:422
msgid "Add a line like the following for each domain that Ansible needs access for:"
msgstr "Ansible ãã¢ã¯ã»ã¹ããå¿
èŠã®ããåãã¡ã€ã³ã«ä»¥äžã®ãããªè¡ãè¿œå ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:429
msgid "You can configure other settings in this file such as the default domain. See `krb5.conf <https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html>`_ for more details."
msgstr "ãã®ãã¡ã€ã«ã§ã¯ãããã©ã«ãã®ãã¡ã€ã³ãªã©ããã®ä»ã®èšå®ãè¡ãããšãã§ããŸãã詳现㯠`krb5.conf <https://web.mit.edu/kerberos/krb5-1.12/doc/admin/conf_files/krb5_conf.html>`_ ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:436
msgid "Automatic Kerberos Ticket Management"
msgstr "Kerberos ãã±ããã®èªå管ç"
#: ../../rst/os_guide/windows_winrm.rst:438
msgid "Ansible version 2.3 and later defaults to automatically managing Kerberos tickets when both ``ansible_user`` and ``ansible_password`` are specified for a host. In this process, a new ticket is created in a temporary credential cache for each host. This is done before each task executes to minimize the chance of ticket expiration. The temporary credential caches are deleted after each task completes and will not interfere with the default credential cache."
msgstr "Ansible ããŒãžã§ã³ 2.3 以éã§ã¯ããã¹ãã« ``ansible_user`` ããã³ ``ansible_password`` ã®äž¡æ¹ãæå®ãããå Žåã¯ãããã©ã«ã㧠Kerberos ãã±ãããèªåçã«ç®¡çããŸãããã®ããã»ã¹ã§ã¯ãåãã¹ãã®äžæçãªèªèšŒæ
å ±ãã£ãã·ã¥ã«æ°ãããã±ãããäœæãããŸããããã¯ããã±ããã倱å¹ããå¯èœæ§ãæå°éã«ããããã«ãåã¿ã¹ã¯ãå®è¡ãããåã«è¡ãããŸããäžæçãªèªèšŒæ
å ±ãã£ãã·ã¥ã¯ãåã¿ã¹ã¯ãå®äºãããšåé€ãããããã©ã«ãã®èªèšŒæ
å ±ãã£ãã·ã¥ã«å¹²æžããããšã¯ãããŸããã"
#: ../../rst/os_guide/windows_winrm.rst:445
msgid "To disable automatic ticket management, set ``ansible_winrm_kinit_mode=manual`` through the inventory."
msgstr "ãã±ããã®èªå管çãç¡å¹ã«ããã«ã¯ãã€ã³ãã³ããªãŒãã ``ansible_winrm_kinit_mode=manual`` ãèšå®ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:448
msgid "Automatic ticket management requires a standard ``kinit`` binary on the control host system path. To specify a different location or binary name, set the ``ansible_winrm_kinit_cmd`` hostvar to the fully qualified path to a MIT krbv5 ``kinit``-compatible binary."
msgstr "èªåãã±ãã管çã«ã¯ãå¶åŸ¡ãã¹ãã·ã¹ãã ã®ãã¹ã«æšæºã® ``kinit`` ãã€ããªãŒãå¿
èŠã§ããå¥ã®å Žæããã€ããªãŒåãæå®ããã«ã¯ããã¹ãå€æ° ``ansible_winrm_kinit_cmd`` ã« MIT krbv5 ``kinit`` äºæãã€ããªãŒãžã®å®å
šä¿®é£Ÿãã¹ãèšå®ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:456
msgid "Manual Kerberos Ticket Management"
msgstr "Kerberos ãã±ããã®æå管ç"
#: ../../rst/os_guide/windows_winrm.rst:458
msgid "To manually manage Kerberos tickets, the ``kinit`` binary is used. To obtain a new ticket the following command is used:"
msgstr "Kerberos ãã±ãããæåã§ç®¡çããã«ã¯ã``kinit`` ãã€ããªãŒã䜿çšããŸããæ°ãããã±ãããååŸããã«ã¯ã以äžã®ã³ãã³ãã䜿çšããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:465
msgid "The domain must match the configured Kerberos realm exactly, and must be in upper case."
msgstr "ãã¡ã€ã³ã¯èšå®ããã Kerberos ã¬ã«ã ã«å®å
šã«äžèŽãã倧æåã§ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:467
msgid "To see what tickets (if any) have been acquired, use the following command:"
msgstr "ååŸãããã±ãã (ååšããå Žå) ã確èªããã«ã¯ã以äžã®ã³ãã³ãã䜿çšããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:473
msgid "To destroy all the tickets that have been acquired, use the following command:"
msgstr "ååŸãããã¹ãŠã®ãã±ãããç Žæ£ããã«ã¯ã以äžã®ã³ãã³ãã䜿çšããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:482
msgid "Troubleshooting Kerberos"
msgstr "Kerberos ã®ãã©ãã«ã·ã¥ãŒãã£ã³ã°"
#: ../../rst/os_guide/windows_winrm.rst:484
msgid "Kerberos is reliant on a properly-configured environment to work. To troubleshoot Kerberos issues, ensure that:"
msgstr "Kerberos ã¯ãé©åã«æ§æãããç°å¢ã§ãªããã°åäœããŸãããKerberos ã®åé¡ããã©ãã«ã·ã¥ãŒãã£ã³ã°ããã«ã¯ã以äžã確èªããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:487
msgid "The hostname set for the Windows host is the FQDN and not an IP address. * If you connect using an IP address you will get the error message `Server not found in Kerberos database`. * To determine if you are connecting using an IP address or an FQDN run your playbook (or call the ``win_ping`` module) using the `-vvv` flag."
msgstr "Windows ãã¹ãã«èšå®ããããã¹ãå㯠FQDN ã§ãããIP ã¢ãã¬ã¹ã§ã¯ãããŸããã* IP ã¢ãã¬ã¹ã䜿çšããŠæ¥ç¶ããå Žåã¯ããšã©ãŒã¡ãã»ãŒãž `Server not found in Kerberos database` ã衚瀺ãããŸãã* IP ã¢ãã¬ã¹ãŸã㯠FQDN ã䜿çšããŠæ¥ç¶ããŠããå Žåã¯ã`-vvv` ãã©ã°ã䜿çšã㊠Playbook ãå®è¡ãããã``win_ping`` ã¢ãžã¥ãŒã«ãåŒã³åºããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:491
msgid "The forward and reverse DNS lookups are working properly in the domain. To test this, ping the windows host by name and then use the ip address returned with ``nslookup``. The same name should be returned when using ``nslookup`` on the IP address."
msgstr "ãã®ãã¡ã€ã³ã§ã¯ãDNS ã®æ£åŒããšéåŒããæ£åžžã«åäœããŠããŸããããããã¹ãããã«ã¯ãWindows ãã¹ãã«åå㧠ping ãæã¡ã``nslookup`` ã§è¿ããã IP ã¢ãã¬ã¹ã䜿çšããŸããIP ã¢ãã¬ã¹ã« ``nslookup`` ã䜿çšãããšãåãååãè¿ãããã¯ãã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:496
msgid "The Ansible host's clock is synchronized with the domain controller. Kerberos is time sensitive, and a little clock drift can cause the ticket generation process to fail."
msgstr "Ansible ãã¹ãã®æèšã¯ãã¡ã€ã³ã³ã³ãããŒã©ãŒãšåæããŸããKerberos ã¯æéã«ææã§ãããããªæèšã®ããã«ããããã±ããçæããã»ã¹ã倱æããå¯èœæ§ããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:500
msgid "Ensure that the fully qualified domain name for the domain is configured in the ``krb5.conf`` file. To check this, run:"
msgstr "ãã¡ã€ã³ã®å®å
šä¿®é£Ÿãã¡ã€ã³åãã``krb5.conf`` ãã¡ã€ã«ã«èšå®ãããŠããããšã確èªããŠãã ãããããã確èªããã«ã¯ã次ãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:508
msgid "If the domain name returned by ``klist`` is different from the one requested, an alias is being used. The ``krb5.conf`` file needs to be updated so that the fully qualified domain name is used and not an alias."
msgstr "``klist`` ã§è¿ããããã¡ã€ã³åãèŠæ±ããããã®ãšç°ãªãå Žåã¯ããšã€ãªã¢ã¹ã䜿çšãããŠããŸãã``krb5.conf`` ãã¡ã€ã«ãæŽæ°ããŠããšã€ãªã¢ã¹ã§ã¯ãªãå®å
šä¿®é£Ÿãã¡ã€ã³åã䜿çšããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:512
msgid "If the default kerberos tooling has been replaced or modified (some IdM solutions may do this), this may cause issues when installing or upgrading the Python Kerberos library. As of the time of this writing, this library is called ``pykerberos`` and is known to work with both MIT and Heimdal Kerberos libraries. To resolve ``pykerberos`` installation issues, ensure the system dependencies for Kerberos have been met (see: `Installing the Kerberos Library`_), remove any custom Kerberos tooling paths from the PATH environment variable, and retry the installation of Python Kerberos library package."
msgstr "ããã©ã«ãã® kerberos ããŒã«ã眮ãæãããããå€æŽãããããå Žå (ããã€ãã® IdM ãœãªã¥ãŒã·ã§ã³ã§ã¯ãããªã£ãŠãããããããŸãã)ãPython Kerberos ã©ã€ãã©ãªãŒãã€ã³ã¹ããŒã«ãããã¢ããã°ã¬ãŒããããããéã«åé¡ãçºçããå¯èœæ§ããããŸããæ¬ã¬ã€ãã®äœææç¹ã§ããã®ã©ã€ãã©ãªãŒã¯ ``pykerberos`` ãšåŒã°ããMIT ãš Heimdal Kerberos ã©ã€ãã©ãªãŒã®äž¡æ¹ã§åäœããããšãç¥ãããŠããŸãã``pykerberos`` ã®ã€ã³ã¹ããŒã«åé¡ã解決ããã«ã¯ãKerberos ã®ã·ã¹ãã äŸåæ§ãæºããããŠããããšã確èªã (åç
§: `Installing the Kerberos Library`_)ãPATH ç°å¢å€æ°ããã«ã¹ã¿ã ã® Kerberos ããŒã«ãã¹ãåé€ããPython Kerberos ã©ã€ãã©ãªãŒããã±ãŒãžã®ã€ã³ã¹ããŒã«ãåè©Šè¡ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:519
msgid "CredSSP authentication is a newer authentication protocol that allows credential delegation. This is achieved by encrypting the username and password after authentication has succeeded and sending that to the server using the CredSSP protocol."
msgstr "CredSSP èªèšŒã¯ãèªèšŒæ
å ±ã®å§è²ãå¯èœã«ããæ°ããèªèšŒãããã³ã«ã«ãªããŸããããã¯ãèªèšŒãæåããåŸã®ãŠãŒã¶ãŒåãšãã¹ã¯ãŒããæå·åããããã CredSSP ãããã³ã«ã䜿çšããŠãµãŒããŒã«éä¿¡ããããšã§å®çŸããŠããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:524
msgid "Because the username and password are sent to the server to be used for double hop authentication, ensure that the hosts that the Windows host communicates with are not compromised and are trusted."
msgstr "ãŠãŒã¶ãŒåãšãã¹ã¯ãŒãããµãŒããŒã«éä¿¡ããŠããã«ãããèªèšŒã«äœ¿çšãããããWindows ãã¹ããéä¿¡ãããã¹ããæŒæŽ©ããŠããããä¿¡é Œã§ããããšã確èªããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:528
msgid "CredSSP can be used for both local and domain accounts and also supports message encryption over HTTP."
msgstr "CredSSP ã¯ãããŒã«ã«ã¢ã«ãŠã³ããšãã¡ã€ã³ã¢ã«ãŠã³ãã®äž¡æ¹ã«äœ¿çšã§ããHTTPã§ã®ã¡ãã»ãŒãžæå·åã«ã察å¿ããŠããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:531
msgid "To use CredSSP authentication, the host vars are configured like so:"
msgstr "CredSSP èªèšŒã䜿çšããã«ã¯ã以äžã®ããã«ãã¹ãå€æ°ãèšå®ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:540
msgid "There are some extra host variables that can be set as shown below:"
msgstr "以äžã®ããã«èšå®ã§ããè¿œå ã®ãã¹ãå€æ°ããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:546
msgid "CredSSP authentication is not enabled by default on a Windows host, but can be enabled by running the following in PowerShell:"
msgstr "CredSSP èªèšŒã¯ãWindows ãã¹ãã§ã¯ããã©ã«ãã§ã¯æå¹ã«ãªã£ãŠããŸããããPowerShell ã§ä»¥äžãå®è¡ããããšã§æå¹ã«ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:556
msgid "Installing CredSSP Library"
msgstr "CredSSP ã©ã€ãã©ãªãŒã®ã€ã³ã¹ããŒã«"
#: ../../rst/os_guide/windows_winrm.rst:558
msgid "The ``requests-credssp`` wrapper can be installed using ``pip``:"
msgstr "``requests-credssp`` ã©ãããŒã¯ã``pip`` ã䜿çšããŠã€ã³ã¹ããŒã«ã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:567
msgid "CredSSP and TLS 1.2"
msgstr "CredSSP ããã³ TLS 1.2"
#: ../../rst/os_guide/windows_winrm.rst:569
msgid "By default the ``requests-credssp`` library is configured to authenticate over the TLS 1.2 protocol. TLS 1.2 is installed and enabled by default for Windows Server 2012 and Windows 8 and more recent releases."
msgstr "ããã©ã«ãã§ã¯ã``requests-credssp`` ã©ã€ãã©ãªãŒã¯ãTLS 1.2 ãããã³ã«ã§èªèšŒããããã«èšå®ãããŠããŸããTLS 1.2 ã¯ãWindows Server 2012 ããã³ Windows 8 ãšããã以éã®ãªãªãŒã¹ã§ã¯ãããã©ã«ãã§ã€ã³ã¹ããŒã«ãããæå¹ã«ãªã£ãŠããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:573
msgid "There are two ways that older hosts can be used with CredSSP:"
msgstr "å€ããã¹ãã CredSSP ã§äœ¿çšã§ããæ¹æ³ã¯ 2 ã€ãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:575
msgid "Install and enable a hotfix to enable TLS 1.2 support (recommended for Server 2008 R2 and Windows 7)."
msgstr "TLS 1.2 ã®ãµããŒããæå¹ã«ãã Hotfix ãã€ã³ã¹ããŒã«ããŠæå¹ã«ããŠãã ãã (Server 2008 R2 ããã³ Windows 7 ã§æšå¥š)ã"
#: ../../rst/os_guide/windows_winrm.rst:578
msgid "Set ``ansible_winrm_credssp_disable_tlsv1_2=True`` in the inventory to run over TLS 1.0. This is the only option when connecting to Windows Server 2008, which has no way of supporting TLS 1.2"
msgstr "ã€ã³ãã³ããªãŒã« ``ansible_winrm_credssp_disable_tlsv1_2=True`` ãèšå®ããŠãTLS 1.0 ã§å®è¡ããããã«èšå®ããŸããããã¯ãTLS 1.2 ã«å¯Ÿå¿ããŠããªã Windows Server 2008 ã«æ¥ç¶ããéã®å¯äžã®éžæè¢ã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:582
msgid "See :ref:`winrm_tls12` for more information on how to enable TLS 1.2 on the Windows host."
msgstr "Windows ãã¹ã㧠TLS 1.2 ãæå¹ã«ããæ¹æ³ã¯ãã:ref:`winrm_tls12`ããåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:588
msgid "Set CredSSP Certificate"
msgstr "CredSSP 蚌ææžã®èšå®"
#: ../../rst/os_guide/windows_winrm.rst:590
msgid "CredSSP works by encrypting the credentials through the TLS protocol and uses a self-signed certificate by default. The ``CertificateThumbprint`` option under the WinRM service configuration can be used to specify the thumbprint of another certificate."
msgstr "CredSSP ã¯ãTLS ãããã³ã«ã§èªèšŒæ
å ±ãæå·åããŠåäœããããã©ã«ãã§ã¯èªå·±çœ²å蚌ææžã䜿çšããŸããWinRM ãµãŒãã¹æ§æã® ``CertificateThumbprint`` ãªãã·ã§ã³ã䜿çšããŠãå¥ã®èšŒææžã®ãµã ããªã³ããæå®ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:593
msgid "This certificate configuration is independent of the WinRM listener certificate. With CredSSP, message transport still occurs over the WinRM listener, but the TLS-encrypted messages inside the channel use the service-level certificate."
msgstr "ãã®èšŒææžæ§æã¯ãWinRM ãªã¹ããŒã®èšŒææžãšã¯ç¬ç«ããŠããŸããCredSSP ã§ã¯ãã¡ãã»ãŒãžãã©ã³ã¹ããŒãã¯åŒãç¶ã WinRM ãªã¹ããŒãä»ããŠè¡ãããŸããããã£ã³ãã«å
ã® TLS æå·åã¡ãã»ãŒãžã«ã¯ãµãŒãã¹ã¬ãã«èšŒææžã䜿çšãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:597
msgid "To explicitly set the certificate to use for CredSSP:"
msgstr "CredSSP ã«äœ¿çšãã蚌ææžãæ瀺çã«èšå®ããã«ã¯ã以äžãå®è¡ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:611
msgid "Non-Administrator Accounts"
msgstr "管çè
以å€ã®ã¢ã«ãŠã³ã"
#: ../../rst/os_guide/windows_winrm.rst:613
msgid "WinRM is configured by default to only allow connections from accounts in the local ``Administrators`` group. This can be changed by running:"
msgstr "WinRM ã¯ãããã©ã«ãã§ãããŒã«ã«ã® ``Administrators`` ã°ã«ãŒãã®ã¢ã«ãŠã³ãããã®æ¥ç¶ã®ã¿ãèš±å¯ããããã«èšå®ãããŠããŸããããã¯ã以äžãå®è¡ããŠå€æŽã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:620
msgid "This will display an ACL editor, where new users or groups may be added. To run commands over WinRM, users and groups must have at least the ``Read`` and ``Execute`` permissions enabled."
msgstr "ããã«ãããACL ãšãã£ã¿ãŒã衚瀺ãããæ°ãããŠãŒã¶ãŒãŸãã¯ã°ã«ãŒããè¿œå ã§ããŸããWinRM ã§ã³ãã³ããå®è¡ããã«ã¯ããŠãŒã¶ãŒããã³ã°ã«ãŒãã«å°ãªããšã ``Read`` ããã³ ``Execute`` ããŒããã·ã§ã³ãæå¹ã«ãªã£ãŠããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:624
msgid "While non-administrative accounts can be used with WinRM, most typical server administration tasks require some level of administrative access, so the utility is usually limited."
msgstr "WinRM ã§ã¯ã管çè
以å€ã®ã¢ã«ãŠã³ãã䜿çšããããšãã§ããŸãããäžè¬çãªãµãŒããŒç®¡çäœæ¥ã§ã¯ãããçšåºŠã®ç®¡çè
æš©éãå¿
èŠãšãªããããå®çšæ§ã¯éãããŠããŸããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:630
msgid "WinRM Encryption"
msgstr "WinRM æå·å"
#: ../../rst/os_guide/windows_winrm.rst:632
msgid "By default WinRM will fail to work when running over an unencrypted channel. The WinRM protocol considers the channel to be encrypted if using TLS over HTTP (HTTPS) or using message level encryption. Using WinRM with TLS is the recommended option as it works with all authentication options, but requires a certificate to be created and used on the WinRM listener."
msgstr "ããã©ã«ãã§ã¯ãWinRM ã¯ãæå·åãããŠããªããã£ã³ãã«äžã§å®è¡ãããšãåäœã«å€±æããŸããWinRM ãããã³ã«ã¯ãTLS over HTTP (HTTPS) ã䜿çšããŠããå Žåããã¡ãã»ãŒãžã¬ãã«ã®æå·åã䜿çšããŠããå Žåã¯ããã£ã³ãã«ãæå·åãããŠãããšã¿ãªããŸããWinRM ã TLS ã§äœ¿çšããããšã¯ããã¹ãŠã®èªèšŒãªãã·ã§ã³ã§åäœãããããæšå¥šããããªãã·ã§ã³ã§ãããWinRM ãªã¹ããŒã§èšŒææžãäœæããŠäœ¿çšããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:638
msgid "If in a domain environment, ADCS can create a certificate for the host that is issued by the domain itself."
msgstr "ãã¡ã€ã³ç°å¢ã®å ŽåãADCS ã¯ãã¡ã€ã³èªäœãçºè¡ãããã¹ãã®èšŒææžãäœæã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:641
msgid "If using HTTPS is not an option, then HTTP can be used when the authentication option is ``NTLM``, ``Kerberos`` or ``CredSSP``. These protocols will encrypt the WinRM payload with their own encryption method before sending it to the server. The message-level encryption is not used when running over HTTPS because the encryption uses the more secure TLS protocol instead. If both transport and message encryption is required, set ``ansible_winrm_message_encryption=always`` in the host vars."
msgstr "HTTPS ã䜿çšããããšãã§ããªãå Žåã¯ãèªèšŒãªãã·ã§ã³ã ``NTLM``ã``Kerberos``ããŸã㯠``CredSSP`` ã§ããã°ãHTTP ã䜿çšããããšãã§ããŸãããããã®ãããã³ã«ã¯ãWinRM ãã€ããŒããç¬èªã®æå·åæ¹åŒã§æå·åããŠãããµãŒããŒã«éä¿¡ããŸããæå·åã¯ãããå®å
šãª TLS ãããã³ã«ã代ããã«äœ¿çšãããããHTTPS ã§å®è¡ããå Žåã«ãã¡ãã»ãŒãžã¬ãã«ã®æå·åã¯äœ¿çšãããŸããããã©ã³ã¹ããŒããšã¡ãã»ãŒãžã®äž¡æ¹ã®æå·åãå¿
èŠãªå Žåã¯ããã¹ãå€æ°ã« ``ansible_winrm_message_encryption=always`` ãèšå®ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:649
msgid "Message encryption over HTTP requires pywinrm>=0.3.0."
msgstr "HTTPã§ã®ã¡ãã»ãŒãžæå·åã«ã¯ 0.3.0 以äžã® pywinrm ãå¿
èŠã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:651
msgid "A last resort is to disable the encryption requirement on the Windows host. This should only be used for development and debugging purposes, as anything sent from Ansible can be viewed, manipulated and also the remote session can completely be taken over by anyone on the same network. To disable the encryption requirement:"
msgstr "æåŸã®æ段ãšããŠãWindows ãã¹ãã®æå·åèŠä»¶ãç¡å¹ã«ããããšãã§ããŸããããã¯ãAnsible ããéä¿¡ããããã®ã¯ãã¹ãŠé²èŠ§ãæäœã§ãããŸãåããããã¯ãŒã¯äžã®èª°ãããªã¢ãŒãã»ãã·ã§ã³ãå®å
šã«ä¹ã£åãããšãã§ãããããéçºããããã°ã®ç®çã§ã®ã¿äœ¿çšããŠãã ãããæå·åãç¡å¹ã«ããã«ã¯ã以äžã®æé ã«åŸããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:661
msgid "Do not disable the encryption check unless it is absolutely required. Doing so could allow sensitive information like credentials and files to be intercepted by others on the network."
msgstr "ã©ãããŠãå¿
èŠãªå Žåãé€ããæå·åãã§ãã¯ãç¡å¹ã«ããªãã§ãã ãããæå·åãã§ãã¯ãç¡å¹ã«ãããšãèªèšŒæ
å ±ããã¡ã€ã«ãªã©ã®æ©å¯æ
å ±ããããã¯ãŒã¯äžã®ä»ã®äººã«ååãããå¯èœæ§ããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:668
msgid "Inventory Options"
msgstr "ã€ã³ãã³ããªãŒãªãã·ã§ã³"
#: ../../rst/os_guide/windows_winrm.rst:670
msgid "Ansible's Windows support relies on a few standard variables to indicate the username, password, and connection type of the remote hosts. These variables are most easily set up in the inventory, but can be set on the ``host_vars``/ ``group_vars`` level."
msgstr "Ansible ã® Windows ãµããŒãã¯ããªã¢ãŒããã¹ãã®ãŠãŒã¶ãŒåããã¹ã¯ãŒããæ¥ç¶ã¿ã€ãã瀺ãããã€ãã®æšæºå€æ°ã«äŸåããŠããŸãããããã®å€æ°ã¯ã€ã³ãã³ããªãŒã§æãç°¡åã«èšå®ã§ããŸããã``host_vars``/``group_vars`` ã¬ãã«ã§èšå®ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:675
msgid "When setting up the inventory, the following variables are required:"
msgstr "ã€ã³ãã³ããªãŒãèšå®ããéã«ã以äžã®å€æ°ãå¿
èŠã«ãªããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:690
msgid "Using the variables above, Ansible will connect to the Windows host with Basic authentication through HTTPS. If ``ansible_user`` has a UPN value like ``username@MY.DOMAIN.COM`` then the authentication option will automatically attempt to use Kerberos unless ``ansible_winrm_transport`` has been set to something other than ``kerberos``."
msgstr "äžèšã®å€æ°ã䜿çšãããšãAnsible 㯠HTTPS ãéã㊠Basic èªèšŒã§ Windows ãã¹ãã«æ¥ç¶ããŸãã``ansible_user`` ã« ``username@MY.DOMAIN.COM`` ã®ãã㪠UPN å€ãããå Žåã¯ã``ansible_winrm_transport`` ã ``kerberos`` 以å€ã«èšå®ãããŠããªãéããèªèšŒãªãã·ã§ã³ã¯èªåçã« Kerberos ã®äœ¿çšãè©Šã¿ãŸãã"
#: ../../rst/os_guide/windows_winrm.rst:696
msgid "The following custom inventory variables are also supported for additional configuration of WinRM connections:"
msgstr "以äžã®ã«ã¹ã¿ã ã€ã³ãã³ããªãŒå€æ°ããWinRM æ¥ç¶ã®è¿œå èšå®ã®ããã«ãµããŒããããŠããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:699
msgid "``ansible_port``: The port WinRM will run over, HTTPS is ``5986`` which is the default while HTTP is ``5985``"
msgstr "``ansible_port``: WinRM ãå®è¡ããããŒãã§ããHTTPS ã®ããã©ã«ã㯠``5986`` ã§ãHTTP ã®ããã©ã«ã㯠``5985`` ã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:702
msgid "``ansible_winrm_scheme``: Specify the connection scheme (``http`` or ``https``) to use for the WinRM connection. Ansible uses ``https`` by default unless ``ansible_port`` is ``5985``"
msgstr "``ansible_winrm_scheme``: WinRM æ¥ç¶ã«äœ¿çšããæ¥ç¶ã¹ããŒã (``http`` ãŸã㯠``https``) ãæå®ããŸããAnsible ã¯ã``ansible_port`` ã ``5985`` ã«æå®ãããŠããªãéããããã©ã«ã㧠``https`` ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:706
msgid "``ansible_winrm_path``: Specify an alternate path to the WinRM endpoint, Ansible uses ``/wsman`` by default"
msgstr "``ansible_winrm_path``: WinRMãšã³ããã€ã³ããžã®å¥ã®ãã¹ãæå®ããŸããAnsible ã¯ããã©ã«ã㧠``/wsman`` ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:709
msgid "``ansible_winrm_realm``: Specify the realm to use for Kerberos authentication. If ``ansible_user`` contains ``@``, Ansible will use the part of the username after ``@`` by default"
msgstr "``ansible_winrm_realm``: Kerberos èªèšŒã«äœ¿çšããã¬ã«ã ãæå®ããŸãã``ansible_user`` ã« ``@`` ãå«ãŸããå ŽåãAnsible ã¯ããã©ã«ã㧠``@`` ã®åŸã«ãŠãŒã¶ãŒåã®äžéšã䜿çšããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:713
msgid "``ansible_winrm_transport``: Specify one or more authentication transport options as a comma-separated list. By default, Ansible will use ``kerberos, basic`` if the ``kerberos`` module is installed and a realm is defined, otherwise it will be ``plaintext``"
msgstr "``ansible_winrm_transport``: 1 ã€ä»¥äžã®èªèšŒãã©ã³ã¹ããŒããªãã·ã§ã³ãã³ã³ãåºåãã®ãªã¹ãã§æå®ããŸããããã©ã«ãã§ã¯ã``kerberos`` ã¢ãžã¥ãŒã«ãã€ã³ã¹ããŒã«ãããŠããŠã¬ã«ã ãå®çŸ©ãããŠããå ŽåãAnsible 㯠``kerberos, basic`` ã䜿çšãããã以å€ã®å Žå㯠``plaintext`` ã«ãªããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:718
msgid "``ansible_winrm_server_cert_validation``: Specify the server certificate validation mode (``ignore`` or ``validate``). Ansible defaults to ``validate`` on Python 2.7.9 and higher, which will result in certificate validation errors against the Windows self-signed certificates. Unless verifiable certificates have been configured on the WinRM listeners, this should be set to ``ignore``"
msgstr "``ansible_winrm_server_cert_validation``: ãµãŒããŒèšŒææžã®æ€èšŒã¢ãŒã (``ignore`` ãŸãã¯``validate``) ãæå®ããŸããAnsible ã®ããã©ã«ãã¯ãPython 2.7.9 以éã§ã¯ ``validate`` ã§ããã㯠Windows ã®èªå·±çœ²å蚌ææžã«å¯ŸããŠèšŒææžã®æ€èšŒãšã©ãŒãçºçããŸããWinRM ãªã¹ããŒã§æ€èšŒå¯èœãªèšŒææžãèšå®ãããŠããªãå Žåã¯ããã®èšå®ã ``ignore`` ã«èšå®ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:725
msgid "``ansible_winrm_operation_timeout_sec``: Increase the default timeout for WinRM operations, Ansible uses ``20`` by default"
msgstr "``ansible_winrm_operation_timeout_sec``: WinRM æäœã®ããã©ã«ãã¿ã€ã ã¢ãŠããå¢ãããšãAnsible ã¯ããã©ã«ã㧠``20`` ã䜿çšããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:728
msgid "``ansible_winrm_read_timeout_sec``: Increase the WinRM read timeout, Ansible uses ``30`` by default. Useful if there are intermittent network issues and read timeout errors keep occurring"
msgstr "``ansible_winrm_read_timeout_sec``: WinRM ã®èªã¿åãã¿ã€ã ã¢ãŠããå¢ãããŸããAnsible ã¯ããã©ã«ã㧠``30`` ã䜿çšããŸãããããã¯ãŒã¯ã®åé¡ãæç¶çã«çºçããèªã¿åãã¿ã€ã ã¢ãŠãã®ãšã©ãŒãçºçãç¶ããå Žåã«æå¹ã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:732
msgid "``ansible_winrm_message_encryption``: Specify the message encryption operation (``auto``, ``always``, ``never``) to use, Ansible uses ``auto`` by default. ``auto`` means message encryption is only used when ``ansible_winrm_scheme`` is ``http`` and ``ansible_winrm_transport`` supports message encryption. ``always`` means message encryption will always be used and ``never`` means message encryption will never be used"
msgstr "``ansible_winrm_message_encryption``: 䜿çšããã¡ãã»ãŒãžæå·åæäœ (``auto``ã``always``ã``never``) ãæå®ããŸããAnsible ã¯ããã©ã«ã㧠``auto`` ã䜿çšããŸãã``auto`` ã¯ã``ansible_winrm_scheme`` ã ``http`` ã§ã``ansible_winrm_transport`` ãã¡ãã»ãŒãžæå·åããµããŒãããŠããå Žåã«éããã¡ãã»ãŒãžæå·åã䜿çšãããããšãæå³ããŸãã``always`` ã¯ãã¡ãã»ãŒãžæå·åãåžžã«äœ¿çšãããããšãæå³ãã``never`` ã¯ãã¡ãã»ãŒãžæå·åã決ããŠäœ¿çšãããªãããšãæå³ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:739
msgid "``ansible_winrm_ca_trust_path``: Used to specify a different cacert container than the one used in the ``certifi`` module. See the HTTPS Certificate Validation section for more details."
msgstr "``ansible_winrm_ca_trust_path``: ``certifi`` ã¢ãžã¥ãŒã«ã§äœ¿çšãããŠãããã®ãšã¯ç°ãªã cacert ã³ã³ãããŒãæå®ããããã«äœ¿çšããŸãã詳现ã¯ããHTTPS 蚌ææžã®æ€èšŒãã»ã¯ã·ã§ã³ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:743
msgid "``ansible_winrm_send_cbt``: When using ``ntlm`` or ``kerberos`` over HTTPS, the authentication library will try to send channel binding tokens to mitigate against man in the middle attacks. This flag controls whether these bindings will be sent or not (default: ``yes``)."
msgstr "``ansible_winrm_send_cbt``: ``ntlm`` ãŸã㯠``kerberos`` ã HTTPS ã§äœ¿çšããå ŽåãèªèšŒã©ã€ãã©ãªãŒã¯ãäžéè
æ»æãç·©åããããã«ãã£ã³ãã«ãã€ã³ãã£ã³ã°ããŒã¯ã³ã®éä¿¡ãè©Šã¿ãŸãããã®ãã©ã°ã¯ããããã®ãã€ã³ãã£ã³ã°ãéä¿¡ãããã©ãããå¶åŸ¡ããŸã (ããã©ã«ã: ``yes``)ã"
#: ../../rst/os_guide/windows_winrm.rst:748
msgid "``ansible_winrm_*``: Any additional keyword arguments supported by ``winrm.Protocol`` may be provided in place of ``*``"
msgstr "``ansible_winrm_*``: ``winrm.Protocol`` ã§ãµããŒããããŠããä»»æã®è¿œå ããŒã¯ãŒãåŒæ°ã¯ã代ããã« ``*`` ã§æå®ã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:751
msgid "In addition, there are also specific variables that need to be set for each authentication option. See the section on authentication above for more information."
msgstr "ããã«ãåèªèšŒãªãã·ã§ã³ã§èšå®ããå¿
èŠãããç¹å®ã®å€æ°ããããŸãã詳现ã¯ãäžèšã®èªèšŒã«é¢ããã»ã¯ã·ã§ã³ãåç
§ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:754
msgid "Ansible 2.0 has deprecated the \"ssh\" from ``ansible_ssh_user``, ``ansible_ssh_pass``, ``ansible_ssh_host``, and ``ansible_ssh_port`` to become ``ansible_user``, ``ansible_password``, ``ansible_host``, and ``ansible_port``. If using a version of Ansible prior to 2.0, the older style (``ansible_ssh_*``) should be used instead. The shorter variables are ignored, without warning, in older versions of Ansible."
msgstr "Ansible 2.0 ã§ã¯ã``ansible_ssh_user``ã``ansible_ssh_pass``ã``ansible_ssh_host``ãããã³ ``ansible_ssh_port`` ã®ãsshããéæšå¥šãšãªãã``ansible_user``ã``ansible_password``ã``ansible_host``ãããã³ ``ansible_port`` ãšãªããŸãããAnsible 2.0 ããåã®ããŒãžã§ã³ã䜿çšããŠããå Žåã¯ã代ããã«å€ãã¹ã¿ã€ã« (``ansible_ssh_*``) ã䜿çšããå¿
èŠããããŸããçãæ¹ã®å€æ°ã¯ãå€ãããŒãžã§ã³ã® Ansible ã§ã¯èŠåãªãã«ç¡èŠãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:761
msgid "``ansible_winrm_message_encryption`` is different from transport encryption done over TLS. The WinRM payload is still encrypted with TLS when run over HTTPS, even if ``ansible_winrm_message_encryption=never``."
msgstr "``ansible_winrm_message_encryption`` ã¯ãTLS äžã§è¡ããããã©ã³ã¹ããŒãæå·åãšã¯ç°ãªããŸããWinRM ãã€ããŒãã¯ã``ansible_winrm_message_encryption=never`` ã§ãã£ãŠããHTTPS ã§å®è¡ãããå Žåã§ã TLS ã§æå·åãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:768
msgid "IPv6 Addresses"
msgstr "IPv6 ã¢ãã¬ã¹"
#: ../../rst/os_guide/windows_winrm.rst:770
msgid "IPv6 addresses can be used instead of IPv4 addresses or hostnames. This option is normally set in an inventory. Ansible will attempt to parse the address using the `ipaddress <https://docs.python.org/3/library/ipaddress.html>`_ package and pass to pywinrm correctly."
msgstr "IPv4 ã¢ãã¬ã¹ããã¹ãåã®ä»£ããã«ãIPv6 ã¢ãã¬ã¹ã䜿çšããããšãã§ããŸãããã®ãªãã·ã§ã³ã¯éåžžãã€ã³ãã³ããªãŒã§èšå®ããŸããAnsible ã¯ã`ipaddress <https://docs.python.org/3/library/ipaddress.html>`_ ããã±ãŒãžã䜿çšããŠã¢ãã¬ã¹ã®è§£æãè©Šã¿ãpywinrm ã«æ£ããæž¡ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:775
msgid "When defining a host using an IPv6 address, just add the IPv6 address as you would an IPv4 address or hostname:"
msgstr "IPv6 ã¢ãã¬ã¹ã䜿çšããŠãã¹ããå®çŸ©ããå Žåã¯ãIPv4 ã¢ãã¬ã¹ããã¹ãåãšåãããã« IPv6 ã¢ãã¬ã¹ãè¿œå ããã ãã§ãã"
#: ../../rst/os_guide/windows_winrm.rst:789
msgid "The ipaddress library is only included by default in Python 3.x. To use IPv6 addresses in Python 2.7, make sure to run ``pip install ipaddress`` which installs a backported package."
msgstr "ipaddress ã©ã€ãã©ãªãŒã¯ Python 3.x ã«ã®ã¿ããã©ã«ãã§å«ãŸããŠããŸããPython 2.7 㧠IPv6 ã¢ãã¬ã¹ã䜿çšããã«ã¯ãããã¯ããŒããããããã±ãŒãžãã€ã³ã¹ããŒã«ãã ``pip install ipaddress`` ãå¿
ãå®è¡ããŠãã ããã"
#: ../../rst/os_guide/windows_winrm.rst:796
msgid "HTTPS Certificate Validation"
msgstr "HTTPS 蚌ææžã®æ€èšŒ"
#: ../../rst/os_guide/windows_winrm.rst:798
msgid "As part of the TLS protocol, the certificate is validated to ensure the host matches the subject and the client trusts the issuer of the server certificate. When using a self-signed certificate or setting ``ansible_winrm_server_cert_validation: ignore`` these security mechanisms are bypassed. While self signed certificates will always need the ``ignore`` flag, certificates that have been issued from a certificate authority can still be validated."
msgstr "TLS ãããã³ã«ã®äžç°ãšããŠã蚌ææžãæ€èšŒããããã¹ãããµããžã§ã¯ããšäžèŽããã¯ã©ã€ã¢ã³ãããµãŒããŒèšŒææžã®çºè¡è
ãä¿¡é ŒããŠããããšã確èªãããŸããèªå·±çœ²å蚌ææžã䜿çšãããã``ansible_winrm_server_cert_validation: ignore`` ãèšå®ããããããšããããã®ã»ãã¥ãªãã£ãŒã¡ã«ããºã ãåé¿ãããŸããèªå·±çœ²å蚌ææžã«ã¯åžžã« ``ignore`` ãã©ã°ãå¿
èŠã§ãããèªèšŒå±ããçºè¡ããã蚌ææžã¯æ€èšŒãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:806
msgid "One of the more common ways of setting up a HTTPS listener in a domain environment is to use Active Directory Certificate Service (AD CS). AD CS is used to generate signed certificates from a Certificate Signing Request (CSR). If the WinRM HTTPS listener is using a certificate that has been signed by another authority, like AD CS, then Ansible can be set up to trust that issuer as part of the TLS handshake."
msgstr "ãã¡ã€ã³ç°å¢ã§ HTTPS ãªã¹ããŒãã»ããã¢ããããäžè¬çãªæ¹æ³ã® 1 ã€ã«ãActive Directory Certificate Service (AD CS) ã䜿çšããæ¹æ³ããããŸããAD CS ã¯ãCSR (Certificate Signing Request) ãã眲åä»ã蚌ææžãçæããããã«äœ¿çšãããŸããWinRM HTTPS ãªã¹ããŒã AD CS ã®ãããªå¥ã®æ©é¢ã«ãã£ãŠçœ²åããã蚌ææžã䜿çšããŠããå ŽåãAnsible 㯠TLS ãã³ãã·ã§ã€ã¯ã®äžéšãšããŠãã®çºè¡è
ãä¿¡é Œããããã«èšå®ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:813
msgid "To get Ansible to trust a Certificate Authority (CA) like AD CS, the issuer certificate of the CA can be exported as a PEM encoded certificate. This certificate can then be copied locally to the Ansible controller and used as a source of certificate validation, otherwise known as a CA chain."
msgstr "AD CS ã®ãããªèªèšŒå± (CA) ã Ansible ã«ä¿¡é Œãããã«ã¯ãCA ã®çºè¡è
蚌ææžã PEM ãšã³ã³ãŒã蚌ææžãšããŠãšã¯ã¹ããŒãããŸãããã®èšŒææžã¯ãAnsible ã³ã³ãããŒã©ãŒã®ããŒã«ã«ã«ã³ããŒããŠã蚌ææžæ€èšŒã®ãœãŒã¹ãšããŠäœ¿çšããããšãã§ããŸã (CA ãã§ãŒã³ãšãåŒã°ããŸã)ã"
#: ../../rst/os_guide/windows_winrm.rst:818
msgid "The CA chain can contain a single or multiple issuer certificates and each entry is contained on a new line. To then use the custom CA chain as part of the validation process, set ``ansible_winrm_ca_trust_path`` to the path of the file. If this variable is not set, the default CA chain is used instead which is located in the install path of the Python package `certifi <https://github.com/certifi/python-certifi>`_."
msgstr "CA ãã§ãŒã³ã«ã¯ãåäžãŸãã¯è€æ°ã®çºè¡è
蚌ææžãå«ããããšãã§ããåãšã³ããªãŒã¯æ°ããè¡ã«å«ãŸããŸããèªèšŒããã»ã¹ã®äžéšãšããŠã«ã¹ã¿ã CA ãã§ãŒã³ã䜿çšããã«ã¯ã``ansible_winrm_ca_trust_path`` ã«ãã¡ã€ã«ã®ãã¹ãèšå®ããŸãããã®å€æ°ãèšå®ãããŠããªãå Žåã¯ãPython ããã±ãŒãž `certifi <https://github.com/certifi/python-certifi>`_ ã®ã€ã³ã¹ããŒã«ãã¹ã«ããããã©ã«ãã® CAã ã§ãŒã³ã䜿çšãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:825
msgid "Each HTTP call is done by the Python requests library which does not use the systems built-in certificate store as a trust authority. Certificate validation will fail if the server's certificate issuer is only added to the system's truststore."
msgstr "HTTP åŒã³åºãã¯ãããããã·ã¹ãã ã«çµã¿èŸŒãŸãã蚌ææžã¹ãã¢ãä¿¡é Œæ©é¢ãšããŠäœ¿çšããªã Python ãªã¯ãšã¹ãã©ã€ãã©ãªãŒã«ãã£ãŠè¡ãããŸãããµãŒããŒã®èšŒææžçºè¡è
ãã·ã¹ãã ã®ãã©ã¹ãã¹ãã¢ã«è¿œå ãããŠããªãå Žåã蚌ææžã®æ€èšŒã¯å€±æããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:833
msgid "TLS 1.2 Support"
msgstr "TLS 1.2 ã®ãµããŒã"
#: ../../rst/os_guide/windows_winrm.rst:835
msgid "As WinRM runs over the HTTP protocol, using HTTPS means that the TLS protocol is used to encrypt the WinRM messages. TLS will automatically attempt to negotiate the best protocol and cipher suite that is available to both the client and the server. If a match cannot be found then Ansible will error out with a message similar to:"
msgstr "WinRM 㯠HTTP ãããã³ã«äžã§åäœãããããHTTPS ã䜿çšãããšããããšã¯ãWinRM ã¡ãã»ãŒãžã®æå·åã« TLS ãããã³ã«ã䜿çšãããããšãæå³ããŸããTLS ã¯ãã¯ã©ã€ã¢ã³ããšãµãŒããŒã®äž¡æ¹ã§å©çšå¯èœãªãæé©ãªãããã³ã«ãšæå·ã¹ã€ãŒããèªåçã«åã決ããããšããŸããäžèŽãããã®ãèŠã€ãããªãå ŽåãAnsible ã¯æ¬¡ã®ãããªã¡ãã»ãŒãžã§ãšã©ãŒã«ãªããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:845
msgid "Commonly this is when the Windows host has not been configured to support TLS v1.2 but it could also mean the Ansible controller has an older OpenSSL version installed."
msgstr "ããã¯ãWindows ãã¹ãã TLS v1.2 ããµããŒãããããã«èšå®ãããŠããªãå Žåã§ãããAnsible ã³ã³ãããŒã©ãŒã«å€ã OpenSSL ããŒãžã§ã³ãã€ã³ã¹ããŒã«ãããŠããããšãæå³ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:849
msgid "Windows 8 and Windows Server 2012 come with TLS v1.2 installed and enabled by default but older hosts, like Server 2008 R2 and Windows 7, have to be enabled manually."
msgstr "Windows 8 ããã³ Windows Server 2012 ã«ã¯ãããã©ã«ã㧠TLS v1.2 ãã€ã³ã¹ããŒã«ãããæå¹ã«ãªã£ãŠããŸãããServer 2008 R2 ã Windows 7 ãªã©ã®å€ããã¹ãã¯æåã§æå¹ã«ããå¿
èŠããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:853
msgid "There is a bug with the TLS 1.2 patch for Server 2008 which will stop Ansible from connecting to the Windows host. This means that Server 2008 cannot be configured to use TLS 1.2. Server 2008 R2 and Windows 7 are not affected by this issue and can use TLS 1.2."
msgstr "Server 2008 ã® TLS 1.2 ãããã«ã¯ãã°ããããAnsible ã® Windows ãã¹ããžã®æ¥ç¶ãåæ¢ããŠããŸããŸããããã¯ãServer 2008 ã TLS 1.2 ã䜿çšããããã«èšå®ã§ããªãããšãæå³ããŸããServer 2008 R2 ãšWindows 7 ã¯ãã®åé¡ã®åœ±é¿ãåãããTLS 1.2 ã䜿çšã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:858
msgid "To verify what protocol the Windows host supports, you can run the following command on the Ansible controller:"
msgstr "Windows ãã¹ãã察å¿ããŠãããããã³ã«ã確èªããã«ã¯ãAnsible ã³ã³ãããŒã©ãŒã§ä»¥äžã®ã³ãã³ããå®è¡ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:865
msgid "The output will contain information about the TLS session and the ``Protocol`` line will display the version that was negotiated:"
msgstr "åºåã«ã¯ TLS ã»ãã·ã§ã³ã«é¢ããæ
å ±ãå«ãŸãã``Protocol`` è¡ã«ã¯ããŽã·ãšãŒããããããŒãžã§ã³ã衚瀺ãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:903
msgid "If the host is returning ``TLSv1`` then it should be configured so that TLS v1.2 is enable. You can do this by running the following PowerShell script:"
msgstr "ãã¹ãã ``TLSv1`` ãè¿ãå Žåã¯ãTLS v1.2 ãæå¹ã«ãªãããã«èšå®ããå¿
èŠããããŸããããã¯ã次㮠PowerShell ã¹ã¯ãªãããå®è¡ããããšã§è¡ãããšãã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:928
msgid "The below Ansible tasks can also be used to enable TLS v1.2:"
msgstr "以äžã® Ansible ã¿ã¹ã¯ã䜿çšã㊠TLS v1.2 ãæå¹ã«ããããšãã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:958
msgid "There are other ways to configure the TLS protocols as well as the cipher suites that are offered by the Windows host. One tool that can give you a GUI to manage these settings is `IIS Crypto <https://www.nartac.com/Products/IISCrypto/>`_ from Nartac Software."
msgstr "TLS ãããã³ã«ããWindows ãã¹ããæäŸããæå·ã¹ã€ãŒããèšå®ããæ¹æ³ã¯ä»ã«ããããŸãããããã®èšå®ã管çããããã® GUI ãæäŸããããŒã«ãšããŠãNartac Software 瀟㮠`IIS Crypto <https://www.nartac.com/Products/IISCrypto/>`_ ããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:966
msgid "WinRM limitations"
msgstr "WinRM ã®å¶é"
#: ../../rst/os_guide/windows_winrm.rst:967
msgid "Due to the design of the WinRM protocol , there are a few limitations when using WinRM that can cause issues when creating playbooks for Ansible. These include:"
msgstr "WinRM ãããã³ã«ã®èšèšäžãWinRM ã䜿çšããéã«ã¯ããã€ãã®å¶éããããAnsible ã® Playbook ãäœæããéã«åé¡ãšãªãããšããããŸããããã«ã¯æ¬¡ã®ãããªãã®ããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:971
msgid "Credentials are not delegated for most authentication types, which causes authentication errors when accessing network resources or installing certain programs."
msgstr "ã»ãšãã©ã®èªèšŒã¿ã€ãã§èªèšŒæ
å ±ãå§è²ãããŠããªãããããããã¯ãŒã¯ãªãœãŒã¹ãžã®ã¢ã¯ã»ã¹ãç¹å®ã®ããã°ã©ã ã®ã€ã³ã¹ããŒã«æã«èªèšŒãšã©ãŒãçºçããããšããããŸããã"
#: ../../rst/os_guide/windows_winrm.rst:975
msgid "Many calls to the Windows Update API are blocked when running over WinRM."
msgstr "WinRM çµç±ã§å®è¡ãããšãWindows Update API ãžã®å€ãã®åŒã³åºãããããã¯ãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:977
msgid "Some programs fail to install with WinRM due to no credential delegation or because they access forbidden Windows API like WUA over WinRM."
msgstr "èªèšŒæ
å ±ã®å§è²ããWUA over WinRM ãªã©ã®çŠæ¢ãããŠãã Windows API ãžã®ã¢ã¯ã»ã¹ã«ãããäžéšã®ããã°ã©ã 㯠WinRM ã§ã€ã³ã¹ããŒã«ã§ããªãå ŽåããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:980
msgid "Commands under WinRM are done under a non-interactive session, which can prevent certain commands or executables from running."
msgstr "WinRM ã®ã³ãã³ãã¯é察話åã»ãã·ã§ã³ã§å®è¡ããããããç¹å®ã®ã³ãã³ããå®è¡ãã¡ã€ã«ãå®è¡ã§ããªãå ŽåããããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:983
msgid "You cannot run a process that interacts with ``DPAPI``, which is used by some installers (like Microsoft SQL Server)."
msgstr "äžéšã®ã€ã³ã¹ããŒã©ãŒ (Microsoft SQL Server ãªã©) ã䜿çšãã ``DPAPI`` ãšå¯Ÿè©±ããããã»ã¹ãå®è¡ããããšã¯ã§ããŸããã"
#: ../../rst/os_guide/windows_winrm.rst:986
msgid "Some of these limitations can be mitigated by doing one of the following:"
msgstr "ãã®å¶éã®äžéšã¯ã以äžã®ãããããå®è¡ããŠè»œæžã§ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:988
msgid "Set ``ansible_winrm_transport`` to ``credssp`` or ``kerberos`` (with ``ansible_winrm_kerberos_delegation=true``) to bypass the double hop issue and access network resources"
msgstr "ããã«ãããåé¡ãåé¿ããŠãããã¯ãŒã¯ãªãœãŒã¹ã«ã¢ã¯ã»ã¹ããããã«ã``ansible_winrm_transport`` ã ``credssp`` ãŸã㯠``kerberos`` (``ansible_winrm_kerberos_delegation=true`` ã䜿çš) ã«èšå®ããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:992
msgid "Use ``become`` to bypass all WinRM restrictions and run a command as it would locally. Unlike using an authentication transport like ``credssp``, this will also remove the non-interactive restriction and API restrictions like WUA and DPAPI"
msgstr "``become`` ã䜿çšãããšããã¹ãŠã® WinRM å¶éãåé¿ããŠãããŒã«ã«ãšåæ§ã«ã³ãã³ããå®è¡ã§ããŸãã``credssp`` ã®ãããªèªèšŒãã©ã³ã¹ããŒãã䜿çšããå Žåãšã¯ç°ãªããé察話åã®å¶éããWUA ã DPAPI ãªã©ã® API ã®å¶éã解é€ãããŸãã"
#: ../../rst/os_guide/windows_winrm.rst:997
msgid "Use a scheduled task to run a command which can be created with the ``win_scheduled_task`` module. Like ``become``, this bypasses all WinRM restrictions but can only run a command and not modules."
msgstr "``win_scheduled_task`` ã¢ãžã¥ãŒã«ã§äœæãããã³ãã³ããå®è¡ããããã«ãã¹ã±ãžã¥ãŒã«ãããã¿ã¹ã¯ã䜿çšããŸãã``become`` ãšåæ§ã«ãWinRM ã®å¶éããã¹ãŠåé¿ããŸãããå®è¡ã§ããã®ã¯ã³ãã³ãã®ã¿ã§ãã¢ãžã¥ãŒã«ã¯å®è¡ã§ããŸããã"
#~ msgid "A WinRM listener should be created and activated. More details for this can be found below."
#~ msgstr "WinRM ãªã¹ããŒãäœæããæå¹ã«ããå¿
èŠããããŸãã詳现ã¯ä»¥äžãåç
§ããŠãã ããã"
#~ msgid "Once completed, you will need to remove auto logon and set the execution policy back to the default (``Restricted `` for Windows clients, or ``RemoteSigned`` for Windows servers). You can do this with the following PowerShell commands:"
#~ msgstr "å®äºããããèªåãã°ãªã³ã解é€ããŠãå®è¡ããªã·ãŒãããã©ã«ã (Windows ã¯ã©ã€ã¢ã³ãã®å Žå㯠``Restricted ``ãWindows ãµãŒããŒã®å Žå㯠``RemoteSigned``) ã«æ»ãå¿
èŠããããŸããããã«ã¯ä»¥äžã® PowerShell ã³ãã³ããå¿
èŠã§ãã"
#~ msgid "The script works by checking to see what programs need to be installed (such as .NET Framework 4.5.2) and what PowerShell version is required. If a reboot is required and the ``username`` and ``password`` parameters are set, the script will automatically reboot and logon when it comes back up from the reboot. The script will continue until no more actions are required and the PowerShell version matches the target version. If the ``username`` and ``password`` parameters are not set, the script will prompt the user to manually reboot and logon when required. When the user is next logged in, the script will continue where it left off and the process continues until no more actions are required."
#~ msgstr "ãã®ã¹ã¯ãªããã¯ãã€ã³ã¹ããŒã«ãå¿
èŠãªããã°ã©ã (.NET Framework 4.5.2 ãªã©) ããå¿
èŠãª PowerShell ããŒãžã§ã³ã確èªããŠåäœããŸããåèµ·åãå¿
èŠã§ã``username`` ãã©ã¡ãŒã¿ãŒãš ``password`` ãã©ã¡ãŒã¿ãŒãèšå®ãããŠããå Žåã¯ãã¹ã¯ãªãããèªåçã«åèµ·åããåèµ·åãã埩垰ãããšãã«ãã°ãªã³ããŸããã¹ã¯ãªããã¯ãã¢ã¯ã·ã§ã³ãäžèŠã«ãªããPowerShell ããŒãžã§ã³ãã¿ãŒã²ããã®ããŒãžã§ã³ãšäžèŽãããŸã§ç¶è¡ãããŸãã``username`` ãã©ã¡ãŒã¿ãŒããã³ ``password`` ãã©ã¡ãŒã¿ãŒãèšå®ãããŠããªãå Žåãã¹ã¯ãªããã¯å¿
èŠã«å¿ããŠãŠãŒã¶ãŒã«æåã§åèµ·åãšãã°ãªã³ãä¿ããŸãããŠãŒã¶ãŒã次ã«ãã°ã€ã³ãããšãã¹ã¯ãªããã¯ååã®ç¶ããå®è¡ããã¢ã¯ã·ã§ã³ãå¿
èŠãªããªããŸã§åŠçãç¶ããŸãã"
#~ msgid "If running on Server 2008, then SP2 must be installed. If running on Server 2008 R2 or Windows 7, then SP1 must be installed."
#~ msgstr "Server 2008 ã§å®è¡ããå Žåã¯ãSP2 ãã€ã³ã¹ããŒã«ãããŠããå¿
èŠããããŸããServer 2008 R2 ãŸã㯠Windows 7 ã§å®è¡ããŠããå Žå㯠SP1 ãã€ã³ã¹ããŒã«ããå¿
èŠããããŸãã"
#~ msgid "When running on PowerShell v3.0, there is a bug with the WinRM service that limits the amount of memory available to WinRM. Without this hotfix installed, Ansible will fail to execute certain commands on the Windows host. These hotfixes should be installed as part of the system bootstrapping or imaging process. The script `Install-WMF3Hotfix.ps1 <https://github.com/jborean93/ansible-windows/blob/master/scripts/Install-WMF3Hotfix.ps1>`_ can be used to install the hotfix on affected hosts."
#~ msgstr "PowerShell v3.0 ã§å®è¡ããå Žåã¯ãWinRM ãµãŒãã¹ã®ãã°ã«ãããWinRM ã§äœ¿çšã§ããã¡ã¢ãªãŒéãå¶éããããšããåé¡ããããŸããããã® Hotfix ãã€ã³ã¹ããŒã«ããªããšãWindows ãã¹ãäžã§ Ansible ã«ããç¹å®ã®ã³ãã³ãã®å®è¡ã«å€±æããŸãããããã® Hotfix ã¯ãã·ã¹ãã ã®ããŒãã¹ãã©ãããŸãã¯ã€ã¡ãŒãžã³ã°ããã»ã¹ã®äžéšãšããŠã€ã³ã¹ããŒã«ããå¿
èŠããããŸãã`Install-WMF3Hotfix.ps1 <https://github.com/jborean93/ansible-windows/blob/master/scripts/Install-WMF3Hotfix.ps1>`_ ãšããã¹ã¯ãªããã䜿çšãããšã圱é¿ãåãããã¹ãã« hotfix ãã€ã³ã¹ããŒã«ã§ããŸãã"
#~ msgid "The following PowerShell command will install the hotfix:"
#~ msgstr "以äžã® PowerShell ã³ãã³ã㯠hotfix ãã€ã³ã¹ããŒã«ããŸãã"
#~ msgid "``CertificateThumbprint``: If running over an HTTPS listener, this is the thumbprint of the certificate in the Windows Certificate Store that is used in the connection. To get the details of the certificate itself, run this command with the relevant certificate thumbprint in PowerShell:"
#~ msgstr "``CertificateThumbprint``: HTTPS ãªã¹ããŒãä»ããŠå®è¡ããå Žåãããã¯æ¥ç¶ã«äœ¿çšããã Windows 蚌ææžã¹ãã¢ã®èšŒææžã®ãµã ããªã³ãã§ãã蚌ææžèªäœã®è©³çŽ°ãååŸããã«ã¯ãPowerShell ã§è©²åœãã蚌ææžã®ãµã ããªã³ããæå®ããŠæ¬¡ã®ã³ãã³ããå®è¡ããŸãã"
#~ msgid "When creating an HTTPS listener, an existing certificate needs to be created and stored in the ``LocalMachine\\My`` certificate store. Without a certificate being present in this store, most commands will fail."
#~ msgstr "HTTPS ãªã¹ããŒãäœæããéã«ã¯ãæ¢åã®èšŒææžãäœæãã``LocalMachine\\My`` ã®èšŒææžã¹ãã¢ã«ä¿åããå¿
èŠããããŸãããã®ã¹ãã¢ã«èšŒææžãååšããªããšãã»ãšãã©ã®ã³ãã³ãã倱æããŸãã"
#~ msgid "While many of these options should rarely be changed, a few can easily impact the operations over WinRM and are useful to understand. Some of the important options are:"
#~ msgstr "ãããã®ãªãã·ã§ã³ã®å€ãã¯ã»ãšãã©å€æŽããå¿
èŠã¯ãããŸããããããã€ãã®ãªãã·ã§ã³ã¯ WinRM ã®æäœã«ç°¡åã«åœ±é¿ãäžãããããç解ããŠãããšäŸ¿å©ã§ããéèŠãªãªãã·ã§ã³ã®äžéšã玹ä»ããŸãã"
#~ msgid "``Service\\AllowUnencrypted``: This option defines whether WinRM will allow traffic that is run over HTTP without message encryption. Message level encryption is only possible when ``ansible_winrm_transport`` is ``ntlm``, ``kerberos`` or ``credssp``. By default this is ``false`` and should only be set to ``true`` when debugging WinRM messages."
#~ msgstr "``Service\\AllowUnencrypted``: ãã®ãªãã·ã§ã³ã¯ãã¡ãã»ãŒãžãæå·åããã« HTTP ã§å®è¡ãããã©ãã£ãã¯ã WinRM ã§èš±å¯ãããã©ãããå®çŸ©ããŸããã¡ãã»ãŒãžã¬ãã«ã®æå·åã¯ã``ansible_winrm_transport`` ã ``ntlm``ã``kerberos``ããŸã㯠``credssp`` ã®å Žåã«ã®ã¿å¯èœã§ããããã©ã«ãã§ã¯ããã㯠``false`` ã§ãããWinRM ã¡ãã»ãŒãžããããã°ããå Žåã«éã ``true`` ã«èšå®ããå¿
èŠããããŸãã"
#~ msgid "To modify a setting under the ``Service`` key in PowerShell:"
#~ msgstr "PowerShell ã® ``Service`` ããŒã§èšå®ãå€æŽããã«ã¯ã以äžãå®è¡ããŸãã"
#~ msgid "To modify a setting under the ``Winrs`` key in PowerShell:"
#~ msgstr "PowerShell ã® ``Winrs`` ããŒã§èšå®ãå€æŽããã«ã¯ã以äžãå®è¡ããŸãã"
#~ msgid "If this fails, the issue is probably related to the WinRM setup. If it works, the issue may not be related to the WinRM setup; please continue reading for more troubleshooting suggestions."
#~ msgstr "倱æããå Žåã¯ãWinRM ã®èšå®ã«åé¡ããããšæãããŸããæåããå Žåã¯ãåé¡ã WinRM ã®èšå®ã«é¢é£ããŠããªãå¯èœæ§ããããããããã«è©³ãããã©ãã«ã·ã¥ãŒãã£ã³ã°ã®æ¹æ³ãã確èªãã ããã"
#~ msgid "If running over HTTP and not HTTPS, use ``ntlm``, ``kerberos`` or ``credssp`` with ``ansible_winrm_message_encryption: auto`` to enable message encryption. If using another authentication option or if the installed pywinrm version cannot be upgraded, the ``Service\\AllowUnencrypted`` can be set to ``true`` but this is only recommended for troubleshooting"
#~ msgstr "HTTPS ã§ã¯ãªã HTTP ã§å®è¡ããå Žåã¯ã``ntlm``ã``kerberos``ããŸã㯠``credssp`` ãš ``ansible_winrm_message_encryption: auto`` ã䜿çšããŠã¡ãã»ãŒãžã®æå·åãæå¹ã«ããŠãã ãããä»ã®èªèšŒãªãã·ã§ã³ã䜿çšããŠããå Žåããã€ã³ã¹ããŒã«ãããŠãã pywinrm ã®ããŒãžã§ã³ãã¢ããã°ã¬ãŒãã§ããªãå Žåã¯ã``Service\\AllowUnencrypted`` ã``true`` ã«èšå®ã§ããŸãããããã¯ãã©ãã«ã·ã¥ãŒãã£ã³ã°ã®ããã«ã®ã¿æšå¥šãããŸãã"
#~ msgid "These indicate an error has occurred with the WinRM service. Some things to check for include:"
#~ msgstr "ãããã¯ãWinRM ãµãŒãã¹ã§ãšã©ãŒãçºçããããšã瀺ããŠããŸãã確èªãã¹ãç¹ã¯ä»¥äžã®éãã§ãã"
#~ msgid "These usually indicate an error with the network connection where Ansible is unable to reach the host. Some things to check for include:"
#~ msgstr "ãããã¯éåžžãAnsible ããã¹ãã«å°éã§ããªããããã¯ãŒã¯æ¥ç¶ã®ãšã©ãŒã瀺ããŠããŸãããã§ãã¯é
ç®ã«ã¯ä»¥äžãå«ãŸããŸãã"
#~ msgid "These usually indicate an error when trying to communicate with the WinRM service on the host. Some things to check for:"
#~ msgstr "ãããã¯éåžžããã¹ãäžã® WinRM ãµãŒãã¹ãšéä¿¡ããããšããéã«ãšã©ãŒã瀺ããŸããããã€ãã®ãã§ãã¯é
ç®ããããŸãã"
#~ msgid "If powershell fails with an error message similar to ``The 'Out-String' command was found in the module 'Microsoft.PowerShell.Utility', but the module could not be loaded.`` then there could be a problem trying to access all the paths specified by the ``PSModulePath`` environment variable. A common cause of this issue is that the ``PSModulePath`` environment variable contains a UNC path to a file share and because of the double hop/credential delegation issue the Ansible process cannot access these folders. The way around this problems is to either:"
#~ msgstr "``The 'Out-String' command was found in the module 'Microsoft.PowerShell.Utility', but the module could not be loaded.`` ã®ãããªãšã©ãŒã¡ãã»ãŒãžã§ powershell ã倱æããå Žåã¯ã``PSModulePath`` ç°å¢å€æ°ã§æå®ããããã¹ãŠã®ãã¹ã«ã¢ã¯ã»ã¹ããããšãããšåé¡ãçºçããå¯èœæ§ããããŸãããã®åé¡ã®äžè¬çãªåå ã¯ã``PSModulePath`` ç°å¢å€æ°ã«ãã¡ã€ã«å
±æãžã® UNC ãã¹ãå«ãŸããŠãããããã«ããã/èªèšŒæ
å ±ã®å§è²åé¡ã®ããã« Ansible ããã»ã¹ããããã®ãã£ã¬ã¯ããªãŒã«ã¢ã¯ã»ã¹ã§ããªãããšã§ãããã®åé¡ãåé¿ããã«ã¯ã以äžã®æ¹æ³ããããŸãã"
#~ msgid "Remove the UNC path from the ``PSModulePath`` environment variable, or"
#~ msgstr "``PSModulePath`` ç°å¢å€æ°ãã UNC ãã¹ãåé€ããŸãã"
#~ msgid "The first step to using SSH with Windows is to install the `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ service on the Windows host. Microsoft offers a way to install ``Win32-OpenSSH`` through a Windows capability but currently the version that is installed through this process is too old to work with Ansible. To install ``Win32-OpenSSH`` for use with Ansible, select one of these installation options:"
#~ msgstr "Windows 㧠SSH ãå©çšããããã®æåã®ã¹ãããã¯ãWindows ãã¹ãã« `Win32-OpenSSH <https://github.com/PowerShell/Win32-OpenSSH>`_ ãµãŒãã¹ãã€ã³ã¹ããŒã«ããããšã§ããMicrosoft 瀟ã§ã¯ãWindows ã®æ©èœãå©çšã㊠``Win32-OpenSSH`` ãã€ã³ã¹ããŒã«ããæ¹æ³ãæäŸããŠããŸãããçŸåšããã®æ¹æ³ã§ã€ã³ã¹ããŒã«ãããããŒãžã§ã³ã¯ãAnsible ã§åäœãããã«ã¯å€ãããŸããAnsible ã§äœ¿çšããããã« ``Win32-OpenSSH`` ãã€ã³ã¹ããŒã«ããã«ã¯ã以äžã®ã€ã³ã¹ããŒã«ãªãã·ã§ã³ã®ãããããéžæããŸãã"
#~ msgid "Install the `openssh <https://chocolatey.org/packages/openssh>`_ package using Chocolatey:"
#~ msgstr "Chocolatey ã䜿çšã㊠`openssh <https://chocolatey.org/packages/openssh>`_ ããã±ãŒãžãã€ã³ã¹ããŒã«ããŸãã"
#~ msgid "Use ``win_chocolatey`` to install the service"
#~ msgstr "``win_chocolatey`` ã䜿çšããŠãµãŒãã¹ãã€ã³ã¹ããŒã«ããŸãã"
#~ msgid "Win32-OpenSSH authentication with Windows is similar to SSH authentication on Unix/Linux hosts. You can use a plaintext password or SSH public key authentication, add public keys to an ``authorized_key`` file in the ``.ssh`` folder of the user's profile directory, and configure the service using the ``sshd_config`` file used by the SSH service as you would on a Unix/Linux host."
#~ msgstr "Windows ã§ã® Win32-OpenSSH èªèšŒã¯ãUnix/Linux ãã¹ãã§ã® SSH èªèšŒã«äŒŒãŠããŸããå¹³æã®ãã¹ã¯ãŒããŸã㯠SSH å
¬ééµèªèšŒã䜿çšããå
¬ééµããŠãŒã¶ãŒã®ãããã¡ã€ã«ãã£ã¬ã¯ããªãŒã® ``.ssh`` ãã£ã¬ã¯ããªãŒã«ãã ``authorized_key`` ãã¡ã€ã«ã«è¿œå ããUnix/Linux ãã¹ããšåæ§ã« SSH ãµãŒãã¹ã§äœ¿çšããã ``sshd_config`` ãã¡ã€ã«ã䜿çšããŠãµãŒãã¹ãèšå®ããããšãã§ããŸãã"
#~ msgid "The ``ansible_shell_type`` variable should reflect the ``DefaultShell`` configured on the Windows host. Set to ``cmd`` for the default shell or set to ``powershell`` if the ``DefaultShell`` has been changed to PowerShell."
#~ msgstr "``ansible_shell_type`` å€æ°ã«ã¯ãWindows ãã¹ãã§èšå®ãããŠãã``DefaultShell`` ãåæ ãããå¿
èŠããããŸããããã©ã«ãã·ã§ã«ã®å Žå㯠``cmd`` ã«ã``DefaultShell`` ã PowerShell ã«å€æŽããŠããå Žå㯠``powershell`` ã«èšå®ããŸãã"
|