Newsid on x64 creates VSS problem

THE POST ABOVE IS FOR 32-BIT BOXES. SEE BELOW FOR 64-BIT

**WORKAROUND FOUND**

This worked on our "NewSidded" 64-bit ESX boxes. Good luck! Be SURE to check the directory paths. That was our problem the whole time. We kept registering the system32 folder dlls.

*********************************

            1. Stop the Microsoft Shadow Copy Provider & Volume Shadow Copy Service

 

2. Export the contents of the HKLM\Software\Microsoft\EventSystem key to a .reg file (as a backup).

3. Delete the HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key. (Just delete the Subscriptions subkey; leave the EventClasses key.)

4. Restart the server.

5. Run the "VSSADMIN LIST WRITERS" command.

This causes the VSS entries in the HKLM\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions key to be rebuilt when the writers initialize.

 

If that does not resolve it try this:

 

Check the Registry - HKEY_CLASSES_ROOT\CLSID\{FAF53CC4-BD73-4E36-83F1-2B23F46E513E}\InProcServer32
- check right pane for (Default)
- ensure this is pointing to the correct location à %systemroot%\system32\ES.DLL

 

Try launching each of these consoles:

 

- perfmon /wmi
- msinfo32
- wmimgmt.msc

 

If the above works out without any issues, please run these commands on the server:

 

Net stop vss

Net stop swprv


regsvr32.exe /i %windir%\system32\eventcls.dll

regsvr32.exe /i %windir%\system32\swprv.dll

regsvr32.exe %windir%\system32\vssui.dll

regsvr32.exe %windir%\SysWOW64\vss_ps.dll

regsvr32.exe %windir%\SysWOW64\msxml.dll

regsvr32.exe %windir%\SysWOW64\msxml2.dll

regsvr32.exe %windir%\SysWOW64\msxml3.dll

regsvr32.exe %windir%\SysWOW64\msxml4.dll

regsvr32.exe %windir%\SysWOW64\ole32.dll

regsvr32.exe %windir%\SysWOW64\oleaut32.dll

regsvr32.exe %windir%\SysWOW64\es.dll

regsvr32.exe %windir%\SysWOW64\comsvcs.dll

vssvc /register

net start swprv

net start vss

**********************************************



Edited by typhoon43 - 15 April 2008 at 1:51pm

We are having the same problem on our ESX Cluster. Only affecting the 64-bit images. Has ANYONE found a fix for this yet?

Originally posted by dclanes Hello, Is there anyway to verify whether or not "newsid" was run on a machine. Thanks! DCL

Hi, Esa04.

I assume the technical problem is solely caused by the conflict 32bit programme vs 64bit Windows.

The fact that Microsoft has never supported NewSID, not even on the platforms which Sysinternals created it for, is a different issue and not strictly a techical isue.

Karl


Edited by Karlchen - 01 March 2008 at 3:03am

Hi, Esa04.

Originally posted by Esa04 i find it odd that noone has experience with this issue !

Well, I am not that amazed.

Reasons:

The NewSID webpage states:

Regarding SIDs, Microsoft does not support images that are prepared using NewSID, we only support images that are prepared using SysPrep. Microsoft has not tested NewSID for all deployment cloning options.

It also states

NewSID is a program we developed that changes a computer's SID. It is free and is a Win32 program, meaning that it can easily be run on systems that have been previously cloned. NewSID works on Windows NT 4, Windows 2000, Windows XP and Windows .NET Server.

A win32 programme may simply be not able to perform the required steps on 64bit Windows which NewSid may execute successfully on the listed 32bit Windows platforms.

So in our company it never occurred to us to try out if NewSID worked on Win2003 64bit.

Karl


Edited by Karlchen - 01 March 2008 at 3:00am