You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#customer intent: As a DevOps Engineer, I want to set up an effective Seccomp profile so that I can run my workloads successfully while making them as secure as possible.
9
10
---
10
11
# Troubleshoot seccomp profile configuration in Azure Kubernetes Service
When you deploy a duplicated or imaged Windows installation, it is required that the System Preparation (Sysprep) tool is used before the capture of the image. Sysprep prepares an installation of Microsoft Windows for duplication, auditing, and customer delivery. For Windows 2000, Windows XP, and Windows Server 2003, Sysprep is included with the latest service pack Deploy.cab. For later versions of Windows, Sysprep is included with the operating system, and Sysprep is located in the folder: `%windir%\system32\sysprep`.
22
+
When you deploy a duplicated or imaged Windows installation, it is required that the System Preparation (Sysprep) tool is used before the capture of the image. Sysprep is a Windows built-in tool located in the folder: `%windir%\system32\sysprep`.
23
23
24
24
## More information
25
25
@@ -29,10 +29,10 @@ The following example displays the SIDs for four local user accounts. Only the l
Cloning or duplicating an installation without taking the recommended steps could lead to duplicate SIDs. For removable media, a duplicate SID might give an account access to files even though NTFS permissions for the account specifically deny access to those files. Because the SID identifies both the computer or domain and the user, unique SIDs are necessary to maintain support for current and future programs. For more information about issues that might occur if you clone an installation of Windows 8 or of Windows Server 2012, go to the [Windows 8 and Windows Server 2012 specific information](#windows-8-and-windows-server-2012-specific-information) section.
38
38
@@ -49,36 +49,17 @@ In addition to the computer SID, many other components and features must be clea
49
49
50
50
We support the following operating systems that are prepared by using the Sysprep utility and then imaged:
51
51
52
-
- Windows NT Workstation 4.0
53
-
- Windows NT Server 4.0 (stand-alone server, not primary domain controllers or backup domain controllers)
54
-
- Windows 2000 Professional
55
-
- Windows 2000 Server (must be imaged before you run DCPromo)
56
-
- Windows 2000 Advanced Server
57
-
- Windows XP Home Edition
58
-
- Windows XP Professional
59
-
- Windows Server 2003, Standard Edition
60
-
- Windows Server 2003, Datacenter Edition
61
-
- Windows Server 2003, Enterprise Edition
62
-
- Windows Server 2003, Web Edition
63
-
- All versions of Windows Vista
64
-
- All versions of Windows Server 2008
65
-
- All versions of Windows 7
66
-
- All versions of Windows Server 2008 R2
67
-
- All versions of Windows 8
68
-
- All versions of Windows Server 2012
69
52
- All versions of Windows 10
53
+
- All versions of Windows 11
54
+
- All versions of Windows Server 2012
70
55
- All versions of Windows Server 2016
71
56
- All versions of Windows Server 2019
72
57
- All versions of Windows Server 1903
73
58
- All versions of Windows Server, version 1909
74
-
- All versions of Windows 11
75
-
76
-
We do not provide support for computers that are set up by using SID-duplicating tools other than the System Preparation tool. For example, this includes the following:
77
-
78
-
-[NewSID](/sysinternals/downloads/newsid)
79
-
- GhostWalker
59
+
- All versions of Windows Server 2022
60
+
- All versions of Windows Server 2025
80
61
81
-
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
62
+
Microsoft doesn't provide support for computers that are set up by using SID-duplicating tools other than the SysPrep tool.
82
63
83
64
> [!NOTE]
84
65
> If an image was created without using Sysprep, we do not support the running of Sysprep after the image is deployed as a way to bring the computer back into compliance. Sysprep must be run before the capture of the image.
@@ -96,7 +77,7 @@ To resolve these issues, use one of the following methods:
96
77
97
78
## References
98
79
99
-
For more information about the Windows System Preparation Tool, visit the following Microsoft websites:
80
+
For more information about the SysPrep tool, visit the following Microsoft websites:
100
81
101
82
- Windows Server 2003 [What Is Sysprep?](/previous-versions/windows/it-pro/windows-server-2003/cc783215(v=ws.10))
102
83
- Windows 8 and Windows Server 2012 [Sysprep Overview](/previous-versions/windows/it-pro/windows-8.1-and-8/hh825209(v=win.10))
Copy file name to clipboardExpand all lines: support/windows/win32/cannot-start-transaction-ms-dtc.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Can't start a transaction in MS DTC
3
3
description: This article describes a problem that may occur intermittently when you try to start a transaction in the MS DTC. A resolution is provided.
4
-
ms.date: 12/19/2023
4
+
ms.date: 06/11/2025
5
5
ms.custom: sap:Distributed Transactions\DTC programming and runtime
0 commit comments