Script for client DOS connecting to a SBS 2003 Server

Hi all,

Does anyone knows how can I make a logon script to work on a client DOS with
TCPIP - LanManager connecting to a SBS 2003 Server?

I can map drives with no problems with the net use command.
I have change some options on the Group Policy to work just fine the cilent
for DOS.

Any help would be aprecciated,

Thanks in advanced,
Daniel Resende
Support Analist
Belo Horizonte - MG
Brazil

In news:833A71DB-8DC0-4FB9-961A-(E-Mail Removed),
Daniel Resende <(E-Mail Removed)> stated, which I
commented on below:
> Hi all,
>
> Does anyone knows how can I make a logon script to work on a client
> DOS with TCPIP - LanManager connecting to a SBS 2003 Server?
>
> I can map drives with no problems with the net use command.
> I have change some options on the Group Policy to work just fine the
> cilent for DOS.
>
> Any help would be aprecciated,
>
> Thanks in advanced,
> Daniel Resende
> Support Analist
> Belo Horizonte - MG
> Brazil

Actually, if you have a DOS client, it cannot use an Active Directory GPO,
therefore if you have a logon script specified in a GPO, it won't work with
a DOS client. Same goes for Win3.1, Win9x, ME and NT4 machines. To specify a
logon script for these legacy clients,first copy the logon script into the
NETLOGON share, then you would have to go into a user account's properties
in Active Directory that will be logging on from one of these clients,
select the Profile tab, and specify the name of the logon script.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If you are having difficulty in reading or finding responses to your post,
instead of the website you are using, I would suggest to use OEx (Outlook
Express or any other newsreader of your choosing), and configure a newsgroup
account, pointing to news.microsoft.com. This is a direct link into the
Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
account with your ISP. With OEx , you can easily find your post and watch &
track threads, sort by date, poster's name, watched threads or subject.

Not sure how? It's easy and you'll enjoy it
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
=================================

Hi Ace,

Thanks for replying.

I have done what you told me so but still not executing the script .bat
command.

I am using the Net commands below:

a:\NET\net initialize
SET PATH=a:\NET

a:\NET\netbind.com
a:\NET\umb.com
a:\NET\tcptsr.exe
a:\NET\tinyrfc.exe
a:\NET\nmtsr.exe
a:\NET\emsbfr.exe
a:\NET\net start

And than shows me up the message to put the name of the user to logon.
It initiated just fine but the .bat command in the scripts folder isn't
executed.

What could I doing wrong?

Thanks again,
Daniel




"Ace Fekay [MVP]" wrote:

> In news:833A71DB-8DC0-4FB9-961A-(E-Mail Removed),
> Daniel Resende <(E-Mail Removed)> stated, which I
> commented on below:
> > Hi all,
> >
> > Does anyone knows how can I make a logon script to work on a client
> > DOS with TCPIP - LanManager connecting to a SBS 2003 Server?
> >
> > I can map drives with no problems with the net use command.
> > I have change some options on the Group Policy to work just fine the
> > cilent for DOS.
> >
> > Any help would be aprecciated,
> >
> > Thanks in advanced,
> > Daniel Resende
> > Support Analist
> > Belo Horizonte - MG
> > Brazil
>
> Actually, if you have a DOS client, it cannot use an Active Directory GPO,
> therefore if you have a logon script specified in a GPO, it won't work with
> a DOS client. Same goes for Win3.1, Win9x, ME and NT4 machines. To specify a
> logon script for these legacy clients,first copy the logon script into the
> NETLOGON share, then you would have to go into a user account's properties
> in Active Directory that will be logging on from one of these clients,
> select the Profile tab, and specify the name of the logon script.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> If you are having difficulty in reading or finding responses to your post,
> instead of the website you are using, I would suggest to use OEx (Outlook
> Express or any other newsreader of your choosing), and configure a newsgroup
> account, pointing to news.microsoft.com. This is a direct link into the
> Microsoft Public Newsgroups, and it is FREE and DOES NOT require a Usenet
> account with your ISP. With OEx , you can easily find your post and watch &
> track threads, sort by date, poster's name, watched threads or subject.
>
> Not sure how? It's easy and you'll enjoy it
> How to Configure OEx for Internet News
> http://support.microsoft.com/?id=171164
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Windows Server Directory Services
> Microsoft Certified Trainer
> Assimilation Imminent. Resistance is Futile.
> Infinite Diversities in Infinite Combinations.
> =================================
>
>
>

In news:FDE820FF-95E6-4CCC-8C59-(E-Mail Removed),
Daniel Resende <(E-Mail Removed)> stated, which I
commented on below:
> Hi Ace,
>
> Thanks for replying.
>
> I have done what you told me so but still not executing the script
> .bat command.
>
> I am using the Net commands below:
>
> a:\NET\net initialize
> SET PATH=a:\NET
>
> a:\NET\netbind.com
> a:\NET\umb.com
> a:\NET\tcptsr.exe
> a:\NET\tinyrfc.exe
> a:\NET\nmtsr.exe
> a:\NET\emsbfr.exe
> a:\NET\net start
>
> And than shows me up the message to put the name of the user to logon.
> It initiated just fine but the .bat command in the scripts folder
> isn't executed.
>
> What could I doing wrong?
>
> Thanks again,
> Daniel

Sorry for taking too long to reply.

This looks like a TCP/IP network boot disk.
Your script is referencing a:\. Is that correct?
Is that the actual script you are putting in the NETLOGON share?

Seems to me, that if this is a DOS client, the network boot utilities and
such should be part of the DOS client's startup, and not after the fact,
which is what a logon script is for, for the network tools must run on the
DOS client first for it to 'know' the network before it can even get to the
NETLOGON share. Does that make sense?

The DOS client machine MUST BE MADE bootable first prior to it being able to
access anything on the network.

Ace