This factor can compromise the security of the workgroup environment, and in a network with multiple SIDs of the same computer, it can also compromise the security of removable media. Requests from the Windows community have prompted multiple companies to develop programs that can change the computer's SID after cloning the system.
It is a free Win32 program, which means it can be easily run on previously cloned systems. NET Server. Version 4. Version 3. The symptom of this program defect is that when an authorized user updates the account information, an error message reports that access permission is denied. Without this solution, NewSID will exit prematurely. Version 1. It has also been updated to change the SID associated with permission settings for file and printer sharing.
One of the most common methods for performing large-scale Windows deployments typically hundreds of computers in an enterprise environment is based on disk cloning technology.
The system administrator can install the basic operating system and additional software used by the company on the sample computer. After configuring the computer to operate in the company network, you can use automated disks or system replication tools such as Symantec's Ghost , PowerQuest's Image Drive, and Altiris' RapiDeploy to copy the sample computer's drives to dozens or hundreds On the computer.
Then, make final adjustments such as assigning unique names to these cloned computers and then use them by company employees. Another popular deployment method is to use the Microsoft sysdiff utility part of the Windows Resource Kit. This tool requires the system administrator to perform a full installation on each computer usually an unattended script installation , and then sysdiff automatically applies the additional software installation image. Due to reasons such as skipping installations and disk sector copying is more efficient than file copying, clone-based deployment can save tens of hours of time compared to similar sysdiff installations.
In addition, system administrators do not need to understand how to use unattended installation or sysdiff , nor do they need to create and debug installation scripts. This alone can save hours of work. The problem with cloning is that it only has very limited support from Microsoft. Microsoft has stated that it only supports obtaining a clone system before reaching the GUI part of the Windows installer. When the installation reaches this step, the computer will be assigned a name and a unique computer SID.
If the system was cloned after completing this step, all cloned computers will have the exact same computer SID. Please note that only changing the computer name or adding the computer to a different domain does not change the computer SID. If the computer was previously associated with a domain, you can only change the domain SID when changing the name or domain.
To understand the problems that cloning can cause, you first need to understand how to assign SIDs to various local accounts on your computer. The RID starts at a fixed value and increases by 1 for each account created. At this point we spent some time discussing SIDs. After trying a number of actions to sort the sync issue, it was resolved by uninstalling and reinstalling the sync client as before.
It looks like it may be best to uninstall the OneDrive client app before cloning as an unavoidable and necessary step, but it was this experience that had me wonder whether changing the SID could be worth considering simply to introduce a difference - Not a GUID, as you say, but at least not identical to other machines on the network. I personally wouldn't bother with using a third-party utility to change the SID. The other possibility of course is that Mark's article is still generally applicable but that there are some applications for which a unique SID or detection of a SID change actually matters to them, especially applications that may have been released since that article was written a while ago.
In that case, you may find that in your own use case, SID changes aren't necessary if as long as you take some additional steps, but that doesn't guarantee that they won't be necessary for someone else's application set.
But you may also find that in some case where a SID change is necessary, differences in the behavior of a third-party SID change utility compared to sysprep will make the difference between success and failure. CopyProfile has become a nightmare on Windows I've tested it on all releases of Windows 10, and the only one where it worked almost perfectly was Win10 , but even there the Quick Access icons were broken because their paths pointed to the Administrator profile folder, not the user's own folders.
In newer versions, using that has caused things like Windows Search to be completely broken on new profiles. Manually deleting certain cache files before sysprepping has has sometimes worked around that, but that's not confidence-inspiring and shouldn't be necessary.
I think I remember a TechNet article saying that CopyProfile was no longer recommended on newer versions of Windows 10, which would explain the havoc it induces, but I do miss that feature.
It looks like Microsoft's proposed replacement is to export a custom Start menu layout as described here , which is what I've been using since then and which does work. As for getting sysprep just right, I'll typically build it in a VM and then take a VM snapshot just before running sysprep, then sysprep and reboot so I can see what happens when the system goes through the new system setup. If it doesn't configure itself the way I want, then I can revert to that snapshot to get right back to the way the system was before it was sysprepped, and try tweaking my unattend file or whatever.
Merge Selected. Merge into selected topic Merge into merge target Merge into a specific topic ID Post Quoted Reply. Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search.
I'm setting up some Virtual PC images. I want to customize the machine with some pre-installed tools and then use this as a base for creating new machines. When's the appropriate time for use and the contrast between them? Sysprep includes the functionality of NewSID.
It 'preps' the WIndows installation for imaging by stripping machine-specific things like the Machine name and SID from the installation. NewSid seems to have some issues.
I am aware that with Windows Sharepoint Services 3. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more.
0コメント