Does Minlogon support map network drive?

[ccfang]

Hi all,

I am using Minlogon and custom shell to build my XPE image. I try to
use map network drive wizard to map a network drive. But get "Access
is denied" error always.

I try to look up a solution here. It seems that Minlogon can not
support this function.
I don't want to use Winlogon becasue it taks too long to boot up and I
don't want to have windows welcome screen either. Is there any other
solution?

I already tried to add Primitive: MPRUI and Msxml Libraries , but it
didn't work.
Do I need to implement a special application with CreateProcessAsUser
to do this function?
Is it possible to use original map network drive wizard with user
login prompt?

Thanks,
Justin

 

[KM]

Justin,

Do you mean you just want to map a network share from another PC under
Minlogon? This should work as long as you are queried to manually type in
the password (credentials to get access to the share). Just use "net use
...." command.

Sharing out a resource under Minlogon if a bit trickier if possible at all.

Regards,
KM

 

[Justin_Fang]

Dear KM,

Thanks for your reply.
Yes, I want to map a network share drive under Minlogon. If I use
map network drive wizard, I can input user name/password and access
the share drive. But if I type the computer name (like \\server) on
address bar, the login dialog won't pop up and just show "access is
denied". Do you have any idea?

The reason I choose Minlogon instead of Winlogon is Winlogon takes
too long to boot up and shows window logo. Do you have any idea to
improve it? It seems that minlogon has many limitations. Do you have
any document described the difference between them?
Thank you very much.

Justin

 

[KM]

Justin,

Thanks for your reply.
Yes, I want to map a network share drive under Minlogon. If I use
map network drive wizard, I can input user name/password and access
the share drive. But if I type the computer name (like \\server) on
address bar, the login dialog won't pop up and just show "access is
denied". Do you have any idea?

When you start with the server name it will try to create a "default"
authentication channel first using currently logged in user account or
guest.
As you can imagine under Minlogon it will not work (no user accounts
supported there).

It is safe however to create the authentication channel providing right
credentials at first place.

Btw, why don't you map a share with "net use .." command?

The reason I choose Minlogon instead of Winlogon is Winlogon takes
too long to boot up and shows window logo.
Understood.

Do you have any idea to improve it?

Hard to tell. You could probably remove some Winlogon dependencies from your
image (and leave with some build errors) but whether this is acceptable or
not is totally dependent on your system specs and what you need to be
included in the image. Keep in mind that Minlogon will always be faster than
Winlogon since it is much lighter component implementation.

Most of the Winlogon "logo" screens can be disabled. You can use features
from Autologon to DisableStatusMessages (search NG archive for the info
about the features).
You can certainly disable Winlogon Welcome screen.

It seems that minlogon has many limitations. Do you have
any document described the difference between them?

I don't think there is a detail document describing all the differences
between Winlogon and Minlogon publicly available. At least I haven't seen
one.
You can start here:
http://blogs.msdn.com/embedded/archive/2005/05/16/417659.aspx,
http://msdn2.microsoft.com/en-us/library/ms838653.aspx.


Regards,
KM

 

[Justin_Fang]

Dear KM,

I changed to use Winlogon and remove the logo screen.
Regarding "net use", it is not user friendly. So I don't plan to
use it.
Many thanks for your kindly help.


May I ask you one more question?
I create a component to add HKLM\Software\Microsoft\Windows NT
\CurrentVersion\Winlogon],"LogonType"=dword:00000000
But it doesn't work. Even I set dependence with "Windows API - User
", the value is wrong(1) after boot up.
Although I can change at run time, I really hope to find out the
reason.

Thanks,
Justin

 

[KM]

Justin,

I changed to use Winlogon and remove the logo screen.
Regarding "net use", it is not user friendly. So I don't plan to use it.

Sorry, I didn't realize you need that feature to be user friendly. Typically
that setup is done by an admin. Anyway, if Winlogon works for you you can
make more relevent GUI components working.

May I ask you one more question?
I create a component to add HKLM\Software\Microsoft\Windows NT
\CurrentVersion\Winlogon],"LogonType"=dword:00000000
But it doesn't work. Even I set dependence with "Windows API - User
", the value is wrong(1) after boot up.
Although I can change at run time, I really hope to find out the
reason.

Sorry, I can't understand why you are trying to create a component with that
registry key?
Basically just set/clear the corresponding checkbox on "Windows Logon"
component's settings page in TD. Btw, this is what is likely overwriting the
value from your component.

Regards,
KM

 

[Justin_Fang]

Dear KM,

Yes, the registry key is related to the checkbox setting. Thank you
very much.

Justin