R
RT
Does anyone know how to map network drives on Windows 2000
without having to lonon to the system?
without having to lonon to the system?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
Pegasus \(MVP\)
RT said:Does anyone know how to map network drives on Windows 2000
without having to lonon to the system?
Mapping drives at boot time is not a good idea:
The drive letters are usually invisible and cannot
be managed in any way. What do you want to
use them for? If no one is logged on, no one can
see them or use them!
G
Guest
Hi
I would of thought running a batch file upon boot would work. Thats what i dislike about Windows 2000 Pro, the only way to capture printers is to run batch files and map the printers on logon. We have some users still using MS-Dos based programs which need a printer to be captured. Had a right laugh when i found out that the older technology was missing from the newer operating system
You need to use the "net use" command.
In DOS you would type: net use x: \\servername\sharename (where X is the drive letter for mapping)
To create a pre-logon batch file please see Microsoft Q243486 Article
Regard
Chris Whit
Stirling Technical Engineering Ltd. - I.T. Department
I would of thought running a batch file upon boot would work. Thats what i dislike about Windows 2000 Pro, the only way to capture printers is to run batch files and map the printers on logon. We have some users still using MS-Dos based programs which need a printer to be captured. Had a right laugh when i found out that the older technology was missing from the newer operating system
You need to use the "net use" command.
In DOS you would type: net use x: \\servername\sharename (where X is the drive letter for mapping)
To create a pre-logon batch file please see Microsoft Q243486 Article
Regard
Chris Whit
Stirling Technical Engineering Ltd. - I.T. Department
P
Pegasus \(MVP\)
See below.
batch files and map the printers on logon. We have some users still using
MS-Dos based programs which need a printer to be captured. Had a right laugh
when i found out that the older technology was missing from the newer
operating system.
====================
I'm not sure what you're laughing about. In the old DOS days, the operating
system was active and available after c:\config.sys had been processed.
Under Win2000, much more is required before the OS is ready, hence a batch
file such as autoexec.bat cannot be executed until much, much later.
Furthermore - should it be executed before anyone logs on, or for all users,
or for some users only?
This is no laughing matter but one that needs some careful design thought.
It was solved by the Task Scheduler - it meets all these requirements
(including the task of running a job before anyone logs on). The tool you
recommended - autoexnt - was developed for Windows NT and is now totally
obsolete.
dislike about Windows 2000 Pro, the only way to capture printers is to runChris White - Stirling said:Hi,
I would of thought running a batch file upon boot would work. Thats what i
batch files and map the printers on logon. We have some users still using
MS-Dos based programs which need a printer to be captured. Had a right laugh
when i found out that the older technology was missing from the newer
operating system.
====================
I'm not sure what you're laughing about. In the old DOS days, the operating
system was active and available after c:\config.sys had been processed.
Under Win2000, much more is required before the OS is ready, hence a batch
file such as autoexec.bat cannot be executed until much, much later.
Furthermore - should it be executed before anyone logs on, or for all users,
or for some users only?
This is no laughing matter but one that needs some careful design thought.
It was solved by the Task Scheduler - it meets all these requirements
(including the task of running a job before anyone logs on). The tool you
recommended - autoexnt - was developed for Windows NT and is now totally
obsolete.
(where X is the drive letter for mapping).You need to use the "net use" command.
In DOS you would type: net use x: \\servername\sharename
G
Guest
Hi Peg
Its the I.T. Industry, alot of things are a laughing matter, if your serious all the time you have to question liking your job
If you cant capture printers in Windows 2000 thats just silly, technology was there... now its gone... strange
Appears in a number of Microsoft games as well so i have found, developments that made progression in previous versions went out of the window and degraded in the newer version
Seriously though if your going to put me on the spot then it isn't helping this person
Regard
Chris Whit
Stirling Technical Engineering Ltd. - I.T. Departmen
Its the I.T. Industry, alot of things are a laughing matter, if your serious all the time you have to question liking your job
If you cant capture printers in Windows 2000 thats just silly, technology was there... now its gone... strange
Appears in a number of Microsoft games as well so i have found, developments that made progression in previous versions went out of the window and degraded in the newer version
Seriously though if your going to put me on the spot then it isn't helping this person
Regard
Chris Whit
Stirling Technical Engineering Ltd. - I.T. Departmen
P
Pegasus \(MVP\)
serious all the time you have to question liking your job.Chris White - Stirling said:Hi Peg,
Its the I.T. Industry, alot of things are a laughing matter, if your
was there... now its gone... strange?If you cant capture printers in Windows 2000 thats just silly, technology
developments that made progression in previous versions went out of theAppears in a number of Microsoft games as well so i have found,
window and degraded in the newer version?
Seriously though if your going to put me on the spot then it isn't helping this person.
You call it "putting you on the spot". I call it "peer review", which, in my
opinion, is one of the great features of newsgroups. I've been "peer
reviewed" more often than I care to think about, and I learned a great deal
in the process.
In general I think it is dangerous poking fun at designers who drop much
loved legacy features, unless one has a solid knowledge of the new systems
and their inner workings.
C
CoWBoY
How would you use task scheduler to map a network drive?
P
Pegasus \(MVP\)
By invoking a batch file such as this one:
net use x: \\SomeServer\SomeShare
net use x: \\SomeServer\SomeShare
C
CoWBoY
I am getting System Error 67 occurred.
I created bat file on root, pointing to the server and shared folder,
scheduled to run on logon. I am on a domain. Didn't work
I created bat file on root, pointing to the server and shared folder,
scheduled to run on logon. I am on a domain. Didn't work
P
Pegasus \(MVP\)
You must ensure that the account used to run the batch
file has sufficient access rights to the share you're connecting
to.
If you use at.exe then you're running the job under the System
account. That account has no access to networked resources.
file has sufficient access rights to the share you're connecting
to.
If you use at.exe then you're running the job under the System
account. That account has no access to networked resources.
C
CoWBoY
ok my batch file name is "drive.bat"
net use y:\\Server\Users
above line is whats in the file.
and schedule properties line "run as" is "mydomain\administrator"
which gives the best access right I guess..
and the domain administrators password entered. Still I get the error 67.
Where I am doing wrong?
net use y:\\Server\Users
above line is whats in the file.
and schedule properties line "run as" is "mydomain\administrator"
which gives the best access right I guess..
and the domain administrators password entered. Still I get the error 67.
Where I am doing wrong?
P
Pegasus \(MVP\)
- Log on to the problem machine under "administrator", making
sure to select the domain logon, not the local logon.
- Run the batch file below in the foreground, to see what happens.
- Run the same batch file as a scheduled job, and check what happens.
- Always include at least one space after "net use y:". You had none.
@echo off
echo Username=%UserName%
net use y: \\Server\Users
pause
sure to select the domain logon, not the local logon.
- Run the batch file below in the foreground, to see what happens.
- Run the same batch file as a scheduled job, and check what happens.
- Always include at least one space after "net use y:". You had none.
@echo off
echo Username=%UserName%
net use y: \\Server\Users
pause
C
CoWBoY
hehehehehhe
SPACE !!!
that was it, when I put the space it worked. !!
Thanks a lot. this will do a lot of good things for me..
SPACE !!!
that was it, when I put the space it worked. !!
Thanks a lot. this will do a lot of good things for me..
P
Pegasus \(MVP\)
There is a universal rule in life: Walk, before trying to run.
When applied to scheduled tasks, this means: Run your
batch file in the foreground and make sure it works, before
scheduling it in the background. If you break this rule
then people will get the impression that you're trying to
live up to your pen name . . .
When applied to scheduled tasks, this means: Run your
batch file in the foreground and make sure it works, before
scheduling it in the background. If you break this rule
then people will get the impression that you're trying to
live up to your pen name . . .