•  

  • Archives

  • Follow me on Twitter

    • « | Home | »

    Using NewSID to change SID


     

    newsid_welcomeAs part of MCITP Self-paced Training Kit: Windows Server 2008 Server Administrator, which was given to me by Microsoft Croatia for learning for MCITP exams, I got 2 Windows Server 2008 installation disks (one is x86, other is x64). I need them for practice tests, and I will use them as virtual machines in Microsoft Virtual PC 2007.

    Update 17.09.2009.

    NewSID is not supported on Windows Server 2008 R2 and Windows7. To change SID, use sysprep as described in tutorial How to change SID on Windows 7 and Windows Server 2008 R2 using sysprep?

     

    Today I had to install three virtual machines (the names should be dcsrv1, boston and binghamton), and the easiest way to do that is to install one operating system, then to copy it’s virtual hard disk image (.vhd) and finally to create 2 new virtual machines that will use existing virtual hard disks. Of course, you can install every single operating system from the DVD, but it takes a while, and this is much quickest process. After getting everything copied, you just need to change Security Identifier (SID) on at least two operating systems, because by coping virtual hard disk of the first operating system you have also copied it’s SID. The best way to do this is to use free software called NewSID (currently in version 4.10), developed by Sysinternals. In this post I’m gonna describe you how to use NewSID to change SID of your operating system. This tool, which packed size is only 68kb can be downloaded at Technet, or you can use NewSID direct download link. Unzip the newsid.exe application, start it and agree with the licence terms. You will see Welcome screen which tells you what NewSID is and tells you to backup your system before using it.

    newsid_welcome

    I skipped backing up my system to speed up the process, and I think you should do it too, except if you are changing SID on production machine. Click on Next. Now we have a window where we have to choose new SID.

    newsid_choose_a_sid

    Here you have three options, to create Random SID, to copy SID from another computer or to manually specify SID. I chose to create random SID, and you should do it too unless you have specific reason to use another option. Click on Next. Now you’ll see the window where you have the possibility to change computer name.

    newsid_rename_the_computer

    I did that following instructions in my book, but this is optional. By clicking Next you’ll see confirmation window, where you can choose to restart or not to restart computer after applying new SID.

    newsid_ready_to_apply_sid

    Click on Next and that’s it. Wait for few minutes, and your PC will have new SID and name.

    newsid_applying_sid

     


     

    By Ilija Brajkovic | March 15, 2009
    Tags: , , , ,
    Category: virtualization | Comments
     Subscribe to RSS feed

    • As I said, NewSID is not supported, and sysprep should be used instead of it.
      I have used PsGetSid on Windows Server 2008 R2, and it worked just fine, you have tutorial on this blog on how to use it, maybe you're doing something wrong.

      Thank you for your comment.

      Ilija
    • Ted
      Hi, I too have used NewSID for years but it does not work on Vista and Win7. My question is does the SID really matter? A domain only looks at the MAC address of the computer for identification, what does the computer SID do? No one at Microsoft seems interested in commenting on this issue. I am in the opinion that Bill Gates gets a spiff ( $ )every time one of us poor IT persons uses sysprep.

      By the way I have tried PsGetSid on Win7 and I get the message that 'PsGetSid' is not recognized as an internal or external command, operable program or batch file. So much for that!
    • Markzz
      I have used NewSID for years and have changed literally 1000's of OS SIDs with it.
      I recently began developing a Windows 2008 R2 SOE image.
      Therefore I performed my typical SID change with NewSID ver4.1.
      After NewSID completed, the server rebooted as expect.
      Unfortunatly it then blue screened. After some further testing I can confirm it's NewSID which is the cause.
      Sysprep is very invasive, I would very much like to use NewSID but can't.
    • @skids
      It works on Windows Server 2008 (as Marin says, it's not recommended, but it worked fine for me), and I wrote this article describing how to do it on Server 2008, not on Vista or Windows 7.
    • skids
      NewSID does not work on Vist or Win 7, only XP and lower. Maybe you should do someresearch before you waste time writing a worthless article like this.
    • It is not recommended to use NewSID on Windows Server 2008 or Windows Vista, especially 64 bit platform. There are known issues (VSS and so on). Try using sysprep with default settings. You can find it here: Start - Run - sysprep .
    blog comments powered by Disqus