wine users - May 2010 - Windows security issues in WMI installation

Hello WINE friends,

I am a WINE newbie seeking your help with WMI installation

So far I have done the following -

1. installed wine-1.1.43 on SUSE 11.2
2. replaced wine's winsxs with my system's [XP] winsxs
3. replaced system32/ dlls except the ntdll, kernel32, user32 & gdi32 dlls
with my system's

After this, when I try installing WMI (as stated below), I get into access
related issues

/home/sanjeev/>su         //installing as root
/home/sanjeev/>wine wmicore.EXE
001f:fixme:ole:CoInitializeSecurity ((nil),-1,(nil),(nil),2,2,(nil),0,(nil))
-stub!
0024:fixme:advapi:LookupAccountNameW L"" L"Everyone" (nil)
0x34d570 (nil) 0x34d56c 0x34d5cc - stub
0024:fixme:advapi:LookupAccountNameW L"" L"Everyone"
0xa017a0 0x34d570 0x130318 0x34d56c 0x34d5cc - stub
0024:fixme:advapi:LookupAccountNameW L"" L"Administrators"
(nil) 0x34d570 (nil) 0x34d56c 0x34d7e4 - stub
0024:fixme:advapi:LookupAccountNameW L"" L"Administrators"
0xa01780 0x34d570 0x1d6808 0x34d56c 0x34d7e4 - stub
0024:fixme:reg:RegSetKeySecurity :(0x1c,4,0xa016f0): stub
0034:fixme:service:svcctl_CreateServiceW Dependencies not supported yet

 
And finally an error dialogue pops up, saying that -

"You do not have access to make the required system configuration
modifications.
Please rerun this installation from an administrator's account."

Can you please suggest me what can be done to overcome this issue?

Appreciate your replies ..
 
Thanks a lot,
Sanjeev

On Tue, May 11, 2010 at 1:21 PM, sanjeev.kulkarni
<wineforum-user at winehq.org> wrote:
> After this, when I try installing WMI (as stated below), I get into access
related issues
>
What is WMI?

Thanks for the reply Chips & eps

WMI (Windows Management Instrumentation) is a vital service running in windows

Windows Apps can do various things using WMI the case here being getting network
info (adapter name, state etc.)

Already there have been discussions regarding WMI installation in WINE forums.

The link below talks of the same stuff but the issue there is different. 
http://www.winehq.org/pipermail/wine-bugs/2009-January/158129.html

Having read that, I went for wine-1.1.43 hoping to succeed; unfortunately
couldn't  :(

Thanks, 
Sanjeev