I’ve had some issues with OneDrive recently that required lengthy support from Microsoft to resolve. Whilst working on the issue, it was noticed that instances of ID numbers relating to user/machine combinations were identical on different machines and we wondered if this may have something to do with the issues we were seeing. Ultimately, a resolution was found without making any changes to these IDs, but it was noticed that the format of the IDs was similar to the SIDs we used to have to change on target machines after cloning in the days of Windows XP. This was done using a utility called NewSID, but later on, using Acronis bare metal restore, an option was available to change the SID during the cloning procedure.
My understanding is that changing the SID on a cloned machine has been unnecessary for many years as detailed in this article
. This is presumably why Reflect doesn’t do it. I did send this to Macrium support asking for clarification, but their reply wasn’t very helpful and suggested running SysPrep to change the SID. The problem with this method is that it’s a very complex and involved procedure for such a minor tweak – hence the NewSID utility.
Even if it isn’t necessary, as would appear to be the case, it still looks wrong seeing an ID that’s supposed to be unique, appearing identically on different machines and it could be argued that changing the SID offers some advantage from a purely diagnostic point of view. These IDs get used in many different places - For example, we could see them used in the title of OneDrive update tasks in Windows Tasks Scheduler and in the name of the temporary folders used by OneDrive. In these and many other cases, having IDs that are different makes it easier to see what’s going on and it may even be worth considering changing the SID on this point alone, provided that it can be done easily reliably and safely.
The NewSID utility was officially retired years ago and was not supposed to work on Windows 7, but it looks like it’s still available for download here
and, if the contents of the page is to be believed, it was updated last year and is compatible with Windows 7-10!
Anybody tried this or know anything about Sharewarepros?
Then there’s a utility called SIDCHG
that’s supposed to be okay with Windows 10. Anybody had any experience of using this utility?
Any other thoughts and comments on this would be most welcome, in particular, my question about changing SIDs simply to restore them as a unique identifiers, which is, after all, what they’re supposed to be and what you’d have if machines had been built individually.