The Joys of Life without Microsoft Client 
Author Message
 The Joys of Life without Microsoft Client

Has anyone ever tackled the challenge of installing the
"Client for Microsoft Networks" via a VBScript on a W2K Pro(SP1)
machine before.

I am not sure where to start and the really depressing thing is that
we have 8000+ desktops to update, so any pointers or help is
appreciated.

Thanks in Advance

Steve



Fri, 25 Feb 2005 08:56:14 GMT  
 The Joys of Life without Microsoft Client
I've never tried that; here is what may be a start in the right
direction, though.  On Win2K, it looks like the Microsoft Client is
installed via the netmscli.inf file; you may be able to make a call to
that file using a RunDLL32 call.  Here's one which MAY work - it
attempts to call the network device install section of the inf file.

%SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection
MSClient.ndi 128 %SystemRoot%\inf\netmscli.inf

MSClient.ndi is simply one section of the INF file; you may need to
explicitly call the MSClient.ndi.Services section as well.

--
Please respond in the newsgroup so everyone may benefit.
 http://dev.remotenetworktechnology.com


Quote:
> Has anyone ever tackled the challenge of installing the
> "Client for Microsoft Networks" via a vbscript on a W2K Pro(SP1)
> machine before.

> I am not sure where to start and the really depressing thing is that
> we have 8000+ desktops to update, so any pointers or help is
> appreciated.

> Thanks in Advance

> Steve



Fri, 25 Feb 2005 10:39:01 GMT  
 The Joys of Life without Microsoft Client

Quote:
> I've never tried that; here is what may be a start in the right
> direction, though.  On Win2K, it looks like the Microsoft Client is
> installed via the netmscli.inf file; you may be able to make a call to
> that file using a RunDLL32 call.  Here's one which MAY work - it
> attempts to call the network device install section of the inf file.

> %SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection
> MSClient.ndi 128 %SystemRoot%\inf\netmscli.inf

> MSClient.ndi is simply one section of the INF file; you may need to
> explicitly call the MSClient.ndi.Services section as well.

Hi

I am not so sure that this will work. I tried it with the MSClient.ndi section,
and the  MSClient.ndi.Services section, and several of the others as well, no
luck.

--
torgeir



Sat, 26 Feb 2005 07:44:27 GMT  
 The Joys of Life without Microsoft Client

Quote:

> Has anyone ever tackled the challenge of installing the
> "Client for Microsoft Networks" via a vbscript on a W2K Pro(SP1)
> machine before.

> I am not sure where to start and the really depressing thing is that
> we have 8000+ desktops to update, so any pointers or help is
> appreciated.

Hi

If all your computers are SP1, you are out of luck I think. With SP2 or SP3
installed, Snetcfg.exe would have made this an easy install. My experience is
that Snetcfg.exe does not work very well with Win2k pre-SP2.

Snetcfg is a sample tool in the Microsoft Windows Driver Development Kit
(...\src\network\config\netcfg) that must be compiled into an exe from the
source (C/C++?) before it can be used.

The finished compiled Win2k version can be downloaded from
http://www.jsiinc.com/reghack.htm. See Tip 4700 for this (WinXP needs the
version that comes with the WinXP DDK).

Install of "Client for Microsoft Networks" on a Win2k SP2/SP2 computer:

C:\>snetcfg -v -c c -i ms_msclient
Trying to install 'ms_msclient'...
...done
*** You need to reboot your computer for this change to take effect ***

Install of "Client for Microsoft Networks" on a Win2k SP1 computer:

C:\>snetcfg.exe  -v -c c -i ms_msclient
Trying to install 'ms_msclient'...
..failed. Error code: 0x80070002

--
torgeir



Sat, 26 Feb 2005 07:55:03 GMT  
 The Joys of Life without Microsoft Client

That's annoying... the method works with portions of the TS installer.
I suspect this has too many externals which need to be taken into
account.

--
Please respond in the newsgroup so everyone may benefit.
 http://dev.remotenetworktechnology.com
 ----------
 Subscribe to Microsoft's Security Bulletins:
 http://www.microsoft.com/technet/security/bulletin/notify.asp


Quote:

> > I've never tried that; here is what may be a start in the right
> > direction, though.  On Win2K, it looks like the Microsoft Client is
> > installed via the netmscli.inf file; you may be able to make a call
to
> > that file using a RunDLL32 call.  Here's one which MAY work - it
> > attempts to call the network device install section of the inf file.

> > %SystemRoot%\System32\rundll32.exe setupapi,InstallHinfSection
> > MSClient.ndi 128 %SystemRoot%\inf\netmscli.inf

> > MSClient.ndi is simply one section of the INF file; you may need to
> > explicitly call the MSClient.ndi.Services section as well.

> Hi

> I am not so sure that this will work. I tried it with the MSClient.ndi
section,
> and the  MSClient.ndi.Services section, and several of the others as
well, no
> luck.

> --
> torgeir



Sat, 26 Feb 2005 09:22:32 GMT  
 The Joys of Life without Microsoft Client
Thank you all for your assistance.

In a follow up to the mail from Torgeir Bakken, I discovered that the
utility snetcfg will work on W2K SP1. I added the -l command switch to
direct it towards netmscli.inf. Here is the command line I used

C:\snetcfg.exe -v -l %SystemRoot%\inf\netmscli.inf -c c -i ms_msclient

With the result being

Trying to install 'ms_msclient'...
...C:\WINNT\inf\netmscli.inf was copied to C:\WINNT\INF\netmscli.inf
...done

This appears to have installed the client successfully, as I am able
to connect to another PC.

Is there any possible problems this method may create??

Thanks again all

Steve



Sun, 27 Feb 2005 10:49:18 GMT  
 The Joys of Life without Microsoft Client

Quote:

> Thank you all for your assistance.

> In a follow up to the mail from Torgeir Bakken, I discovered that the
> utility snetcfg will work on W2K SP1. I added the -l command switch to
> direct it towards netmscli.inf. Here is the command line I used

> C:\snetcfg.exe -v -l %SystemRoot%\inf\netmscli.inf -c c -i ms_msclient

> With the result being

> Trying to install 'ms_msclient'...
> ...C:\WINNT\inf\netmscli.inf was copied to C:\WINNT\INF\netmscli.inf
> ...done

> This appears to have installed the client successfully, as I am able
> to connect to another PC.

Ahh, so that was it. In SP2 and better it finds the file itself then it looks
like, but not for pre-SP2 Win2k...

Quote:
> Is there any possible problems this method may create??

I think it is safe to use, but it is up to you to test it until you are
satisfied. But then, what is the alternative, manually update 8000+ computers?

--
torgeir



Sun, 27 Feb 2005 11:32:59 GMT  
 
 [ 7 post ] 

 Relevant Pages 

1. Dcom-Clients without Client for Microsoft-Networks

2. cannot resolve unc without microsoft client for networks installed

3. Bring your Microsoft Visual Basic applications to life on the Internet, by using VBnet

4. Bring your Microsoft Visual Basic applications to life on the Internet, by using VBnet

5. Q:The Life of a form (and events called during that life)

6. VBScript - the joys of...

7. Joys of recordcounting

8. How to send HTML email from outlook client without using CDONTS

9. connect to client without file & printer sharing

10. Using chr-Function without Microsoft.VisualBasic-Namespace

11. Send Simple E-Mail Message without E-Mail client

 

 
Powered by phpBB® Forum Software