As Mark Russinovich decided to retire this. Here it still is. I don’t totally agree with the retirement. We, even after using MDT for deployment, would still, rarely run into some weird network issues with a machine. Putting it down to possible SID issues, running NewSID would fix it.<\/p>\n
NewSID v4.10<\/a><\/p>\n HASH starting with 07FA is for the zip file HASH starting with 73E7 is for the newsid.exe file <\/p>\n MD5 Hash created with Chaos MD5<\/a><\/p>\n http:\/\/technet.microsoft.com\/en-us\/sysinternals\/bb897418.aspx<\/a><\/p>\n http:\/\/blogs.technet.com\/b\/markrussinovich\/archive\/2009\/11\/03\/3291024.aspx<\/a><\/p>\n UPDATE: Should point out I’ve never used MD5 HASHes before so prob cocked that up, not sure. But file is clean, do a scan to check.<\/p>\n UPDATE 2: Thanks to Joe for pointing out the HASH above was off.\u00a0 But I realise now the HASH I originally stated (which will state in the comment) is for the zip file.\u00a0 To show it hadn’t been tampered with since downloading it ages ago from Microsoft when it was still available.\u00a0 I’m going to add a HASH for the .exe as well.<\/p>\n","protected":false},"excerpt":{"rendered":" As Mark Russinovich decided to retire this. Here it still is. I don’t totally agree with the retirement. We, even after using MDT for deployment, would still, rarely run into some weird network issues with a machine. Putting it down … Continue reading
\nMD5 Hash 07FA425D722FD5E63BFE6B1BAC26EC5B<\/p>\n
\nMD5 Hash 73E708D1126E7AF86A4EF820C24D80E4<\/p>\n